abf methodology

Traditional AIM

Traditional AIM Processes Business Process Architecture Business Requirements Definition Business Requirements Mapping Application & Tech Architecture Module Design & Build Data Conversion Documentation Business System Testing Performance Testing Adoption & Learning Production Migration

Traditional AIM Phases

Defi

nitio

n

Ope

ratio

ns A

naly

sis

Des

ign

Build

Prod

uctio

n

Tran

sitio

n

Prod

uctio

n

•Modeling and Reinventing Processes•Features and Functions Gapping•Passive Involvement

Customisations Testing

AIM for Business Flows (ABF)AIM for Business Flows Processes

Business Process Mapping Application & Tech Architecture Module Design & Build Data Conversion Documentation Business System Testing Performance Testing Adoption & Learning Production Migration

AIM for Business Flows Phases

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

•Business Process Focus•Tools to Manage Business•Show & Tell vs Ask & Do•Baseline Solution at your finger tips•Active Participation

•Testing•Validation of solution

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

Ask and Do Show and Tell

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 Process

DO Process

TE Process

PT Process

AP Process

PM Process

Definition Transition ProductionElaboration Build

ABF Processes

ABF Top Level Flow

Definition Build ProductionTransitionElaboration

Project Planning

DesignExtensions

PrepareCustomTest Scripts

Create and test CustomExtensions

PrepareProductionEnvironment

Convert and Verify Data

BeginProduction

MaintainSystem

ProposeFutureDirection

Perform SystemsIntegrationTest

VerifyProductionReadiness

Prepare for CRP 1Workshop(s)

Conduct CRP 1Workshop(s)



Perform User Acceptance Test

Build RequiredAssets

ConductPhase EndReview


Conduct BusinessArchitectureWorkshops


SolutionReview &Sign-Off



Prepare CRP 2Environment


Conference Room Pilots (CRP)• A Conference Room Pilot refers to the approach and activities

surrounding the planning and execution of one or more formal test scripts aimed at validating the application system against the client’s business needs.

• The origin of the term comes from the practice of placing workstations in a conference room and arranging them in a particular order (usually by logical process or Business Flow) for testing. Test scripts were then passed down the line from one tester to the next according to the natural flow of the

business process.

What is a CRP in ABF ?• CRP is a series of workshops where Flow Teams of an implementation

project go through the flows iteratively during the project phases using Oracle Applications (e.g. EBS)

• The flows of a solution will be grouped into logical “flow batches” that

can and will be defined, tested and developed parallel by independent Flow Teams during the project.

• A Flow Team will consist of at least :– 1 Implementation Consultant as a facilitator (preferably 2 functional

consultants per flow team, one of which could be a solution architect)– Customer’s Process Owner– One or more Customer’s key users.

What is a CRP in ABF ?

• Workshops are used as the primary working model between Customer and Consultants.

– Implementation Consultants are responsible for providing Oracle Applications knowledge, updating project flow documentation, planning and facilitating the workshops.

– Customer is responsible for providing Customer’s processes and requirements knowledge and making necessary timely decisions.

CRP Definitions (for EBS)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 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)

CRP Objectives• CRP IS NOT A TRAINING

COURSE!!!!!!

Summary of ABF General 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

ABF Document Naming• The naming of some key deliverables has

changed (not all templates are available yet)– Renamed deliverables:

• BP.080 Future Business Model = BF.015• BR.030 Map Business Requirements = BF.003

Business Flow Family Baseline Functionality • BR.100 Set up Document = BF.016• Current Financial & Operating Structure RD.010 =

BF.010– New deliverables:

• High Level Solution Document (HLSD) = BF.045• Change Catalog = BF.040

How to find ABF templates?

All ABF blank templates are delivered through OPN

Go to this OPN link

To launch the AIM for Business Flows Method Pack:

1. Select "Start" > "Programs" > "Oracle Methods".

2. Select "AIM for Business Flows".

Demo of the Demo of the softwaresoftwareDemo of the Demo of the softwaresoftware

http://www.oracle.com/partners/develop/implementation/global/aim-business-flows.html

What does it mean “to adapt to Oracle Applications leading practices“

Key to a successful ABF implementation and achievement of its benefits is Customer’s willingness to avoid modifications to Oracle Applications and adapt their business processes as much as possible

to the Oracle Business Flows representing leading practices in Oracle Applications.

ABF Top Level Flow

Definition Build ProductionTransitionElaboration

Project Planning

DesignExtensions

PrepareCustomTest Scripts

Create and test CustomExtensions

PrepareProductionEnvironment

Convert and Verify Data

BeginProduction

MaintainSystem

ProposeFutureDirection

Perform SystemsIntegrationTest

VerifyProductionReadiness





Perform User Acceptance Test

Build RequiredAssets



Conduct BusinessArchitectureWorkshops


SolutionReview &Sign-Off





ABF Phases: Definition

Tasks and Activities

– Develop a detailed project plan and work plan– Customer’s Project Team Training– Update or build Flow Assets– Conduct Business Architecture Workshops– Conduct CRP 1 Workshops – Develop preliminary conceptual architecture– Develop Supporting Approach Documents (Testing,

Conversions, Interfaces, Transition ..)

Deliverables Updated Project Plan Flow Educated Customer team Accepted Financial and Operating Structure Doc. Version 1.0 of Future Business Model Document,

(Business Flows mapped to Customer’s business) Business Requirements Mapping Gaps (V 1.0) High Level Solution Document (V1.0) Preliminary conceptual architecture for the new

Preliminary Supporting Approach Documents Set ups for CRP 2.0

Assumptions

– Customer will provide adequate personnel for the workshops.

– These persons will have a good knowledge of the processes and can make or obtain decisions required as agreed in Project Plan.

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

ABF Phases: Definition


– Develop a detailed project plan and work plan– Customer’s Project Team Training– Update or build Flow Assets– Conduct Business Architecture Workshops– Conduct CRP 1 Workshops – Develop preliminary conceptual architecture– Develop Supporting Approach Documents (Testing,

Conversions, Interfaces, Transition ..)

Deliverables Updated Project Plan Flow Educated Customer team Accepted Financial and Operating Structure Doc. Version 1.0 of Future Business Model Document,

(Business Flows mapped to Customer’s business) Business Requirements Mapping Gaps (V 1.0) High Level Solution Document (V1.0) Preliminary conceptual architecture for the new

Preliminary Supporting Approach Documents Set ups for CRP 2.0

Assumptions

– Customer will provide adequate personnel for the workshops.

– These persons will have a good knowledge of the processes and can make or obtain decisions required as agreed in Project Plan.

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n Business Architecture Workshops

CRP 1

Business Flows mapped to Customer’s business

High Level Solution Document

ABF Phases: Elaboration

Tasks and Activities– Detailed Planning of the Phase– Build and setup CRP 2.0 Environment– Conduct CRP 2.0 Workshops– Determine disposition of each exception/gap Update

Flow Documentation, revise system setups and test scripts to reflect required changes

– Create functional and technical design documents for conversions, interfaces and extensions, if any.

– Update /finalise supporting Approach Documents– Accept phase and solution

Assumptions

– Customer will provide personnel for workshops as in Definition Phase

– Customer will adjust business processes as necessary to match standard Application Flows or approve a change order for system extensions

Deliverables Configured test system for CRP 2.0 Accepted Solution with Deliverables:

Future Business Model (V 2.0)Bus. Requirements Mapping Gaps (v2.0),closedHigh Level Solution Document (V 2.0)Updated Test ScriptsUpdated Set Up documents

Approved func & technical designs for conversions, interfaces and extensions, if any

Updated Supporting Approach Documents

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

ABF Phases: Elaboration

Tasks and Activities– Detailed Planning of the Phase– Build and setup CRP 2.0 Environment– Conduct CRP 2.0 Workshops– Determine disposition of each exception/gap Update

Flow Documentation, revise system setups and test scripts to reflect required changes

– Create functional and technical design documents for conversions, interfaces and extensions, if any.

– Update /finalise supporting Approach Documents– Accept phase and solution

Assumptions

– Customer will provide personnel for workshops as in Definition Phase

– Customer will adjust business processes as necessary to match standard Application Flows or approve a change order for system extensions

Deliverables Configured test system for CRP 2.0 Accepted Solution with Deliverables:

Future Business Model (V 2.0)Bus. Requirements Mapping Gaps (v2.0),closedHigh Level Solution Document (V 2.0)Updated Test ScriptsUpdated Set Up documents

Approved func & technical designs for conversions, interfaces and extensions, if any

Updated Supporting Approach Documents

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

Gap Handling CRP 2s Update documents Designs for conversions,

extensions, interfaces

Accepted Solution with updated documents

Designs for conversions, extensions, interfaces approved

ABF Phases: Build


– Detailed Planning of the Phase– Build CRP 3.0 Environment– Finalize conversion, interfaces and extensions, if

any, and test– Conduct CRP 3.0 System and Intgration Testing and

User Acceptance Testing– Plan transition to production– Accept phase and tested solution

Deliverables

Configured test system for CRP 3.0 Final functional & technical designs for conversions,

interfaces and extensions, if any Tested Solution Environment or UAT Transition plan

Assumptions

– Customer will provide adequate personnel to conduct CRP 3.0 testing as required by project plan

– Customer is responsible for testing and test data– Solution functionality can be changed only through

Change Order process

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

ABF Phases: Build


– Detailed Planning of the Phase– Build CRP 3.0 Environment– Finalize conversion, interfaces and extensions, if

any, and test– Conduct CRP 3.0 System and Intgration Testing and

User Acceptance Testing– Plan transition to production– Accept phase and tested solution

Deliverables

Configured test system for CRP 3.0 Final functional & technical designs for conversions,

interfaces and extensions, if any Tested Solution Environment or UAT Transition plan

Assumptions

– Customer will provide adequate personnel to conduct CRP 3.0 testing as required by project plan

– Customer is responsible for testing and test data– Solution functionality can be changed only through

Change Order process

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

Finalize conversions, interfaces, extensions

CRP 3 = System and Integration Testing

User Acceptance Testing

Tested Solution Final designs for extensions,

interfaces Transition Plan

ABF Phases: Transition


– Detailed Planning of the Phase– Configure production system – Convert and verify all system data– Perform end user training– Perform production readiness review

Deliverables Converted and verified data Acceptance test results Production system validation Trained End Users Readiness Review Configured production system

Assumptions

– Customer will prepare end user training manuals and conduct end user training prior to production

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

ABF Phases: Production


– Commence Production– Decommission legacy systems– Support Production– Discuss and advise future direction

Deliverables Production System Post Production Support

Assumptions

– Customer personnel are adequately trained and prepared to adopt new Applications infrastructure

– Customer will decommission legacy systems

Defi

nitio

n

Elab

orati

on

Build

Tran

sitio

n

Prod

uctio

n

ABF Method Highlights• Business process focus• Predefined Future Process Model as a starting point• Follows Dynamic Systems Development Method (DSDM) principles• Early introduction of hands-on testing• Iterative scoping and testing cycles• Requirements mapped to Business Flows• Delivery assets: pre-seeded documents,set ups, test scripts, etc

PLUS All the proven methodology of Classical AIM

(Applications Implementation Method) BUT

You have to know what you are doing