ABF

AIM for Business FlowsOverview

ABF

Ejaz HussainOracle Consultant

AIM For Business Flows 2

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.

Definitions


Traditional AIM vs. ABFTraditional AIM AIM For Business Flows (ABF)

Requirements driven Solution Driven

Solution defined during project based on requirements

Flow solution defined before start of project

Traditional Waterfall approach Iterative approach based on CRPs

Defines customisations where std functionality does not meet reqs

Seeks to avoid customisation and prioritises all changes

Focus on individual modules Focus on cross module process 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◦ Customer´s willingness to adopt basic elements

of E-Business Suite best practices as described in flows

What makes an implementation Flow Based?


• Accelerated implementation timeframes• Improved communications • Improved quality of resulting business system• Reduced number of custom extensions,

reduced risk• Improved ROI

Benefits of Using AIM for Business Flows


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

BF Process TA Process

MD Process

CV ProcessDO

ProcessTE ProcessPT ProcessAP Process

PM Process

Definition

Transition Production

Elaboration Build

ABF Processes


AIM for Business Flows with Accelerators

8

CRP Definitions (for EBS)

AIM For Business Flows

Phase CRP Objectives

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 at this point may

indicate the need for an additional CRP 3 iteration.


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)

CRP Objectives


Summary of ABFGeneral Flow Solution Documents

General Document Name CRP1 CRP2 CRP3

High Level Solution Document v 1 v 2 -

Financial & Operation Structure v 1 - -

Future Business Model v 1 v 2 -

Business Requirements Mapping Gaps v 1 v 2 -

Test Scripts (test results) v 0 v 1 v 2

Set up Documents v 0 v 1 v 2

Apps Extension Functional Design v 0 v 1

= Sign off


Definition PhaseObjectives: • 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 ArchitectureWorkshops• Customer Education on CRP Process• Conduct CRP 1

Outputs:• CRP 1 Results• Preliminary Conceptual Architecture• Key Configurations (COA, TCA, Multi-Org)

Definition Transition ProductionElaboration Build

Tasks & Activities Business Architecture Workshops CRP 1

Deliverables Business Flows mapped to

Customer’s business High Level Solution Document


Definition PhaseTask 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


Elaboration PhaseDefinition Transition Production

Elaboration

Build

Objectives: • 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

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

interfaces

Deliverables Accepted Solution with updated

documents Designs for conversions,

extensions, interfaces approved


Task DeliverablesCRP2 Workshops BF.040 Conduct WorkshopFuture Process Modeling BF.015 Future Process Model V 2

(FINAL)Setup Document for CRP3 BF.016 Setup Document V2Customizations: MD.050: Functional Extension

Design V1MD.060 Database Extension Designs V1MD.070 Technical Design V1

Test Scripts TE.040 System Test Scripts V2Data Migration CV.050 Define Manual Conversion

ProceduresPhase End Review BF.100 v2 Conduct Phase End

Review

Elaboration PhaseTask and Deliverables


Build PhaseDefinition Transition ProductionElaboratio

nBuild 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

Outputs:• System Tested Applications• User Acceptance Test Results• Performance Test Report• Transition and Contingency Plan

Tasks & Activities Finalize conversions,

interfaces, extensions CRP 3 = System and

Integration Testing User Acceptance Testing

Deliverables Tested Solution Final designs for extensions,

interfaces Transition Plan


Task DeliverablesKey User TrainingConfigure UATBuild Extensions, Interfaces and Conversions

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

CRP3 System and Integration Testing

TE.040 System Test Scripts V3 (FINAL)

Setup Document for PRODUCTION BF.016 Setup Document V3 (FINAL)

Security Profiles BF.170 Security ProfilesUser Manuals DO.070 User Guide V1

Build PhaseTask and Deliverables


Transition PhaseDefinition Transition ProductionElaboration Build

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


Production PhaseDefinition Transition

Production

Elaboration Build

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

Thank You!


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.

BF Process


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

TA Process


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

customizations to satisfy functionality gaps.

MD Process


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

CV Process


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

DO 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

TE Process


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

PT Process


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

AP Process


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

PM Process