ABF

AIM for Business Flows Overview

Ejaz Hussain Oracle Consultant

Traditional AIM It is known as Ask and Do. It is requirements driven and solution is derived based on the requirements during the project. The approach is taken on a modular basis. AIM for Business Flow It is Show and Tell solution driven approach. Solution Flows are defined before the start of project. It is based on iterative approach based where multiple runs of CRPs are done. It aims at avoiding customizations and prioritizes all changes. There is a strong emphasis on integrated view and focus is on cross module process flows.
AIM For Business Flows 1

Traditional AIM
Requirements driven

AIM For Business Flows (ABF)

Solution Driven

Solution defined during project based Flow solution defined before start of on requirements project Traditional Waterfall approach Iterative approach based on CRPs

Defines customisations where std functionality does not meet reqs Focus on individual modules

Seeks to avoid customisation and prioritises all changes Focus on cross module process flows

AIM For Business Flows

 Use of predefined flows as starting point Approach is solution driven not requirements driven Use of iterative Conference Room Pilots (CRP) with a live system Use of pre-existing delivery assets, if available Customers willingness to adopt basic elements of E-Business Suite best practices as described in flows

AIM For Business Flows

Accelerated implementation timeframes Improved communications Improved quality of resulting business system Reduced number of custom extensions, reduced risk Improved ROI

AIM For Business Flows

Definition Elaboration BF Process TA Process MD Process CV Process DO Process TE Process PT Process AP Process PM Process

Build

Transition Production

A process is a grouping of tasks within a method based on common functions or disciplines which lead to one or more key deliverables

AIM For Business Flows

AIM For Business Flows

CRP Definitions (for EBS)

Phase CRP Objectives 7

Definition

CRP 1.0

Familiarize the customer with the Business Flows being implemented and map Business Flows to the customers business and identify potential changes. Validate customer Chart of Accounts, Multi -Org Structure, TCA structure and other personalized setups identified during CRP 1. Refine mapping of Business Flows to the customers business and identify any remaining changes necessary. The conclusion of CRP 2.0 should result in a frozen solution scope . Business System Test of tailored solution including custom extensions and sample converted legacy data. Refinement of solution is still an option at this point, but the scope of changes should be small by this time. Significant changes a t this point may indicate the need for an additional CRP 3 iteration.

Elaboration

CRP 2.0

Build

CRP 3.0

AIM For Business Flows

CRP 1

CRP 2
-

- Familiarization - Initial mapping & identify gaps - Identify setup required for CRP2 instance (e.g. COA, MultiOrg, TCA) Refine mapping and gaps Validate flow setup Validate business process (flows) Identify & build extensions, interfaces Freeze scope

CRP 3

- Business System Test (test extensions, interfaces, performance)

AIM For Business Flows

General Document Name

CRP1

CRP2

CRP3

High Level Solution Document Financial & Operation Structure Future Business Model Business Requirements Mapping Gaps Test Scripts (test results) Set up Documents Apps Extension Functional Design

v1 v1 v1 v1 v0 v0 v0
AIM For Business Flows

v2 v2 v2 v1 v1 v1

v2 v2

= Sign off

Definition

Elaboration

Build

Transition

Production

Tasks & Activities Business Architecture Workshops CRP 1

Objectives: Plan the project Familiarize customer with Flows Map Flows to the Business Identify potential changes Key Activities: Build/update Delivery Assets Prepare CRP 1 Environments Conduct Business Architecture Workshops Customer Education on CRP Process Conduct CRP 1 Outputs: CRP 1 Results Preliminary Conceptual Architecture Key Configurations (COA, TCA, Multi-Org)
AIM For Business Flows 10

Deliverables Business Flows mapped to Customers business High Level Solution Document

Task CRP1 workshop Future Process Modeling

Deliverables

BF.015 V1

Map Business Requirements

BF.003 baseline (previously known as BR030) BF.040 Change Catalog

BF.016 Setup Document V1 TE.040 System Test Script V1 CV.010 Define Data conversion Requirements and Strategy BF.100 conduct phase end review
AIM For Business Flows 11

Setup Document for CRP2 Test Scripts Data Conversion Phase End Review

Objectives:
Definition Build Transition Production

Elaboration

Tasks & Activities Gap Handling CRP 2s Update documents Designs for conversions, extensions, interfaces

Validate COA, TCA, Multi-Org Setups Refine mapping of Flows Identify remaining changes Design Custom Extensions Determine/freeze scope of solution Key Activities: Prepare CRP 2 Environment Design custom extensions Conduct CRP 2 Solution Review and Sign-off Outputs: Refined Configuration Approved designs for customizations Conversion Data Mapping Updated Test Scripts High-Level Solution Document
AIM For Business Flows 12

Deliverables Accepted Solution with updated documents Designs for conversions, extensions, interfaces approved

Task CRP2 Workshops

Future Process Modeling Setup Document for CRP3 Customizations:

Deliverables BF.040 Conduct Workshop

BF.015 Future Process Model V 2 (FINAL) BF.016 Setup Document V2 MD.050: Functional Extension Design V1 MD.060 Database Extension Designs V1 MD.070 Technical Design V1 TE.040 System Test Scripts V2 CV.050 Define Manual Conversion Procedures BF.100 v2 Conduct Phase End Review
AIM For Business Flows 13

Test Scripts Data Migration Phase End Review

Definition

Elaboration

Build

Transition

Production

Tasks & Activities Finalize conversions, interfaces, extensions CRP 3 = System and Integration Testing User Acceptance Testing

Objectives: Develop, test, and accept custom software Propose a transition strategy Execute performance test Conduct a system test Finalize the solution Key Activities: Create & test custom extensions Prepare CRP 3 Environment Conduct CRP 3 Conduct User Acceptance Test

Deliverables Tested Solution Final designs for extensions, interfaces Transition Plan

Outputs: System Tested Applications User Acceptance Test Results Performance Test Report Transition and Contingency Plan
AIM For Business Flows 14

Task
Key User Training Build Extensions, Interfaces and Conversions

Deliverables
MD.050 V2 MD.060 MD.070 MD.120 Functional Extension Design Database Extension Design V2 Technical Design V2 Create Installation Routines

CRP3 System and Integration Testing Conduct UAT Setup Document for PRODUCTION Security Profiles User Manuals

TE.040 System Test Scripts V3 (FINAL) User Acceptance Testing on Final Solution BF.016 Setup Document V3 (FINAL) BF.170 Security Profiles DO.070 User Guide V1

AIM For Business Flows

15

Definition

Elaboration

Build

Transition

Production

Objectives: Prepare Production Environment Convert and verify legacy data Train user personnel Transition to Production Key Activities: Plan Transition Go-Live Checklist Final System Check Users & Support Ready Convert & Load Data Deploy extensions and interfaces Production Readiness Review Fallback Plan Outputs: Converted and verified data Skilled Users Production Support Infrastructure Production system ready GO-LIVE
AIM For Business Flows 16

Definition

Elaboration

Build

Transition

Production

Objectives: Maintain the Production System Measure System Performance Promote user acceptance Propose and plan future direction Key Activities: Assess effectiveness of system Reinforce adoption of system Recommend Business direction Recommend technical direction Outputs: Effectiveness Assessment Business Direction Recommendations Technical Direction Recommendations

AIM For Business Flows

17

It is Business Process Mapping, the goal is to familiarize the Customer with Oracle Business Flows and conduct the initial mapping of flows to the clients business.

AIM For Business Flows

Technical Architecture Process: Its goal is to design an information system architecture that realizes the business vision.

AIM For Business Flows

Module Design and Build process: It focuses on the design and development of customizations to satisfy functionality gaps.

AIM For Business Flows

Data Conversion: The goal is to convert all legacy data necessary for the operation of the new system.

AIM For Business Flows

The Documentation or DO process augments Oracle Applications manuals with information about customizations and business procedures.

AIM For Business Flows

The Business System Testing or TE process has the goal of refining the business solution through iterative Conference Room Pilots and testing the quality of all elements of the application system

AIM For Business Flows

The Performance Testing or PT process involves the definition, construction, and execution of a performance test

AIM For Business Flows

The Adoption and Learner (AP) process fosters acceptance of the new applications by all users - UAT

AIM For Business Flows

The goal of the Production Migration (PM) process is to migrate the organization, systems, and people to the new enterprise system

AIM For Business Flows