AIM for Business Flows Overview


Copyright © 2006, Oracle. All rights reserved.

Traditional AIM Traditional AIM Phases 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
•Modeling and Reinventing Processes •Features and Functions Gapping •Passive Involvement

Operations Analysis




Copyright © 2006, Oracle. All rights reserved.

Production Production





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 Elaboration •Business Process Focus •Tools to Manage Business •Show & Tell vs Ask & Do •Baseline Solution at your finger tips •Active Participation •Testing •Validation of solution 1-3 Copyright © 2006. All rights reserved. Oracle. Production Transition Definition Build .

Traditional AIM vs ABF 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 Defines customisations where std functionality does not meet reqs Focus on individual modules Iterative approach based on CRPs Seeks to avoid customisation and prioritises all changes Focus on cross module process flows Ask and Do 1-4 Show and Tell Copyright © 2006. All rights reserved. . Oracle.

What is AIM for Business Flows? • • Latest iteration of Oracle Consulting’s proven Application Implementation Method (AIM) Incorporates changes that: – Promote a business process focus – Supports use of pre-defined Business Flows and “delivery assets”. if available – Employs iterative Conference Room Pilots (CRPs) • Does not restrict tailoring of Flows or system configuration to satisfy client requirements 1-5 Copyright © 2006. All rights reserved. Oracle. .

if available • Customer´s willingness to adopt basic elements of E-Business Suite best practices as described in flows • Flows are reasonably “good fit” 1-6 Copyright © 2006. All rights reserved.What makes an implementation Flow Based? • Use of predefined flows as starting point • Use of iterative Conference Room Pilots (CRP) with a live system • Use of pre-existing delivery assets. Oracle. .

All rights reserved. reduced risk Improved ROI 1-7 Copyright © 2006. .Benefits of Using AIM for Business Flows for the Customer • • • • • Accelerated implementation timeframes Improved communications Improved quality of resulting business system Reduced number of custom extensions. Oracle.

Approach Objectives • • • Rapidly deploy an environment using pre-defined Business Flows. . All rights reserved. Oracle. and pre-tested configurations Start with standard business flows as “Future Process Model” Incorporate user involvement throughout the lifecycle using iterative conference room pilots (CRPs) Employ CRP’s to map business flows to customer business processes and identify gaps Focus on getting the customer rapidly onto Oracle • • 1-8 Copyright © 2006.

Oracle. .g. EBS) • The flows of a solution will be grouped into logical “flow batches” that can and will be defined. 1-9 Copyright © 2006. • 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. tested and developed parallel by independent Flow Teams during the project.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. All rights reserved.

– Customer is responsible for providing Customer’s processes and requirements knowledge and making necessary timely decisions.What is a CRP in ABF ? • Workshops are used as the primary working model between Customer and Consultants. All rights reserved. updating project flow documentation. Oracle. . planning and facilitating the workshops. 1-10 Copyright © 2006. – Implementation Consultants are responsible for providing Oracle Applications knowledge.

0 Familiarize the customer with the Business Flows being implemented map Business Flows to the and customer’s business and identify potential changes.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.0 Validate customer Chart of Accounts. TCA structure and other “personalized” setups identified during CRP 1. Significant changes this point may t a indicate the need for an additional CRP 3 iteration. CRP 2. Elaboration Build 1-11 Copyright © 2006. All rights reserved.CRP Definitions (for EBS) Phase CRP Objectives Definition CRP 1. The conclusion of CRP 2. Oracle.0 should result in a frozen solution scope . Refine mapping of Business Flows to the customer’s business and identify any remaining changes necessary. Multi -Org Structure. CRP 3.

All rights reserved. Oracle. .Summary of ABF General Flow Solution Documents 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 = Sign off v2 v2 v2 v1 v1 v1 v2 v2 1-12 Copyright © 2006.

Approach Overview – Top Level Flow Definition Project Planning Elaboration Prepare CRP 2 Environment Build Create and test Custom Extensions Prepare CRP 3 Environment Transition Prepare Production Environment Production Prepare for CRP 2 Workshop(s) Build Required Assets Conduct CRP 2 Workshop(s) Prepare for CRP 3 Workshop(s) Conduct CRP 3 Workshop(s) Convert and Verify Data Conduct Business Architecture Workshops Design Extensions Prepare for CRP 1 Workshop(s) Conduct CRP 1 Workshop(s) Prepare Custom Test Scripts Solution Review & Sign-Off Perform Systems Integration Test Perform User Acceptance Test Verify Production Readiness Begin Production Maintain System Conduct Phase End Review Conduct Phase End Review Conduct Phase End Review Propose Future Direction 1-13 Copyright © 2006. . Oracle. All rights reserved.

Oracle.Definition Phase Definition Elaboration Build Transition Production Tasks & Activities  Business Architecture Workshops  CRP 1 Deliverables  Business Flows mapped to Customer’s business  High Level Solution Document 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. All rights reserved. Multi-Org) 1-14 Copyright © 2006. . TCA.

All rights reserved. . TCA. interfaces • Validate COA. Oracle. extensions. interfaces approved 1-15 Copyright © 2006. 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 Deliverables  Accepted Solution with updated documents  Designs for conversions. extensions.Elaboration Phase Objectives: Definition Elaboration Build Transition Production     Tasks & Activities Gap Handling CRP 2s Update documents Designs for conversions.

. extensions CRP 3 = System and Integration Testing User Acceptance Testing Deliverables Tested Solution Final designs for extensions. Oracle. interfaces Transition Plan Objectives: • Develop. interfaces. test. All rights reserved. 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    1-16 Copyright © 2006.Build Phase Definition Elaboration Build Transition Production    Tasks & Activities Finalize conversions.

.Transition Phase 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 • Fallback Plan Outputs: • Converted and verified data • Skilled Users • Production Support Infrastructure • Production system ready • GO-LIVE 1-17 Copyright © 2006. Oracle. All rights reserved.

All rights reserved.Production Phase 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 1-18 Copyright © 2006. . Oracle.

Oracle. as defined Approved changes should be incorporated in following deliverables/work products: – Future Process Model (i.Gaps and Gap Handling • Resolution of identified “changes” may include: – change in application configuration – manual workaround – custom extension. . Business Flows) – Business Procedures documentation – Application Setup documents – System Test Scripts • 1-19 Copyright © 2006. or – adopt the standard Business Flow.e. All rights reserved.

Oracle Business Design to Release 1-20 Copyright © 2006. . Oracle. All rights reserved.

Sign up to vote on this title
UsefulNot useful