ABF

AIM for Business Flows

Overview
Ejaz Hussain
Oracle Consultant
Definitions
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 2
Traditional AIM vs. ABF
Traditional AIM AIM For Business Flows (ABF)

Requirements driven 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 Seeks to avoid customisation and

functionality does not meet reqs prioritises all changes

Focus on individual modules Focus on cross module process flows

AIM For Business Flows 3

What makes an implementation Flow Based?

◦ 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
◦ Customer´s willingness to adopt basic elements of E-
Business Suite best practices as described in flows

AIM For Business Flows 4

Benefits of Using 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 5

ABF Processes
Definition Elaboration Build Transition Productio
n
BF Process
TA Process
MD
Process
CV Process
DO Process
TE Process
PT Process
AP Process
PM Process

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 6

AIM for Business Flows with
Accelerators

AIM For Business Flows 7

 CRP Definitions (for EBS)
Phase CRP Objectives8

Definition CRP 1.0 Familiarize the customer with the Business Flows
being implemented and map Business Flows to the
customer’s business and identify potential changes.

Elaboration CRP 2.0 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 customer’s business and
identify any remaining changes necessary. The
conclusion of CRP 2.0 should result in a frozen
solution scope.

Build CRP 3.0 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.

AIM For Business Flows

CRP Objectives
 CRP 1
- Familiarization
- Initial mapping & identify gaps
- Identify setup required for CRP2 instance (e.g. COA, Multi-
Org, TCA)
 CRP 2
- 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 9

 Summary of ABF
General Flow Solution Documents
General Document Name CRP1 CRP2 CRP3

High Level Solution Document v1 v2 -

Financial & Operation Structure v1 - -

Future Business Model v1 v2 -

Business Requirements Mapping Gaps v1 v2 -

Test Scripts (test results) v0 v1 v2

Set up Documents v0 v1 v2

Apps Extension Functional Design v0 v1

= Sign off
AIM For Business Flows 10
Definition Phase
Definition Elaboration Build Transition Production Objectives:
• Plan the project
Tasks & Activities • Familiarize customer with Flows
 Business Architecture Workshops • Map Flows to the Business
 CRP 1 • Identify potential changes

Key Activities:
• Build/update Delivery Assets
Deliverables • Prepare CRP 1 Environments
 Business Flows mapped to • Conduct Business Architecture
Customer’s business Workshops
 High Level Solution Document • 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 11

Definition Phase
Task and Deliverables
Task Deliverables

CRP1 workshop BF.040 Change Catalog

Future Process Modeling BF.015 V1

Map Business Requirements BF.003 baseline (previously

known as BR030)
Setup Document for CRP2 BF.016 Setup Document V1

Test Scripts TE.040 System Test Script V1

Data Conversion CV.010 Define Data conversion

Requirements and Strategy
Phase End Review BF.100 conduct phase end review

AIM For Business Flows 12

Elaboration Phase
Objectives:
Definition
Elaboration Build Transition Production
• Validate COA, TCA, Multi-Org
Setups
Tasks
Tasks && Activities
Activities • Refine mapping of Flows
 Gap
Gap Handling
Handling
 CRP • Identify remaining changes
CRP 2s
2s
 Update
Update documents
documents
• Design Custom Extensions
 Designs
Designs for
for conversions,
conversions, extensions,
extensions, • Determine/freeze scope of
interfaces
interfaces solution

Key Activities:
• Prepare CRP 2 Environment
Deliverables
• Design custom extensions
 Accepted Solution with updated
documents • Conduct CRP 2
 Designs for conversions, • Solution Review and Sign-off
extensions, interfaces approved
Outputs:
• Refined Configuration
• Approved designs for
customizations
• Conversion Data Mapping
• Updated
AIM Test Scripts
For Business Flows 13
Elaboration Phase
Task and Deliverables
Task Deliverables
CRP2 Workshops BF.040 Conduct Workshop
Future Process Modeling BF.015 Future Process Model V 2
(FINAL)
Setup Document for CRP3 BF.016 Setup Document V2
Customizations: MD.050: Functional Extension
Design V1
MD.060 Database Extension
Designs V1
MD.070 Technical Design V1
Test Scripts TE.040 System Test Scripts V2
Data Migration CV.050 Define Manual Conversion
Procedures 14
AIM For Business Flows
Build Phase
Objectives:
Definition
Elaboration Build Transition Production
• Develop, test, and accept custom
Tasks
Tasks &
& Activities
Activities software
 Finalize
Finalize conversions,
conversions, • Propose a transition strategy
interfaces,
interfaces, extensions
extensions • Execute performance test
 CRP
CRP 33 == System
System and
and • Conduct a system test
Integration
Integration Testing
Testing • Finalize the solution
 User
User Acceptance Testing
Acceptance Testing

Key Activities:
Deliverables • Create & test custom extensions
Deliverables
 Tested
Tested Solution
Solution • Prepare CRP 3 Environment
 Final
Final designs for
designs for extensions,
extensions, • Conduct CRP 3
interfaces
interfaces • Conduct User Acceptance Test
 Transition
Transition Plan
Plan
Outputs:
• System Tested Applications
• User Acceptance Test Results
• Performance Test Report
• Transition and Contingency Plan

AIM For Business Flows 15

Build Phase
Task and Deliverables
Task Deliverables
Key User Training
Configure UAT
Build Extensions, Interfaces and MD.050 Functional Extension
Conversions Design V2
MD.060 Database Extension
Design V2
MD.070 Technical Design V2
MD.120 Create Installation
Routines

CRP3 System and Integration TE.040 System Test Scripts V3

Testing (FINAL)
AIM For Business Flows 16
Setup Document for PRODUCTION BF.016 Setup Document V3 (FINAL)
Transition Phase Objectives:
• Prepare Production Environment
Definition Elaboration Build • Convert and verify legacy data
Transition Production
•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 17
Production Phase
Objectives:
Definition Elaboration Build Transition • Maintain the Production System
Production • 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 18

Thank You!
BF Process
 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 client’s business.

AIM For Business Flows

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

AIM For Business Flows

MD Process
 Module Design and Build process:
 It focuses on the design and development of

customizations to satisfy functionality gaps.

AIM For Business Flows

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

AIM For Business Flows

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

AIM For Business Flows

TE Process
 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

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

AIM For Business Flows

AP Process
 The Adoption and Learner (AP) process
fosters acceptance of the new applications by
all users, and

AIM For Business Flows

PM Process
 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