oracle abf
Post on 07-Apr-2015
1.229 Views
Preview:
TRANSCRIPT
1-1 Copyright © 2006, Oracle. All rights reserved.
AIM for Business FlowsOverview
1-2 Copyright © 2006, Oracle. All rights reserved.
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 InvolvementCustomisations Testing
1-3 Copyright © 2006, Oracle. All rights reserved.
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
1-4 Copyright © 2006, Oracle. All rights reserved.
Traditional AIM vs ABF
Traditional 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
1-5 Copyright © 2006, Oracle. All rights reserved.
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-6 Copyright © 2006, Oracle. 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, 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-7 Copyright © 2006, Oracle. All rights reserved.
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, reduced risk
• Improved ROI
1-8 Copyright © 2006, Oracle. All rights reserved.
Approach Objectives
• Rapidly deploy an environment using pre-defined Business Flows, 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-9 Copyright © 2006, Oracle. All rights reserved.
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.
1-10 Copyright © 2006, Oracle. All rights reserved.
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.
1-11 Copyright © 2006, Oracle. All rights reserved.
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.
1-12 Copyright © 2006, Oracle. All rights reserved.
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
1-13 Copyright © 2006, Oracle. All rights reserved.
Definition Build ProductionTransitionElaboration
Project Planning
DesignExtensions
PrepareCustom
Test Scripts
Create and test Custom
Extensions
PrepareProduction
Environment
Convert and Verify Data
BeginProduction
MaintainSystem
ProposeFuture
Direction
Perform SystemsIntegration
Test
VerifyProductionReadiness
Prepare for CRP 1Workshop(s)
Conduct CRP 1Workshop(s)
Prepare for CRP 2Workshop(s)
Conduct CRP 2Workshop(s)
Perform User Acceptance
Test
Build RequiredAssets
ConductPhase End
Review
ConductPhase End
Review
Conduct BusinessArchitectureWorkshops
ConductPhase End
Review
SolutionReview &Sign-Off
Prepare for CRP 3Workshop(s)
Conduct CRP 3Workshop(s)
Prepare CRP 2Environment
Prepare CRP 3Environment
Approach Overview – Top Level Flow
1-14 Copyright © 2006, Oracle. All rights reserved.
Definition Phase
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)
Definition Transition ProductionElaboration Build
Tasks & Activities Business Architecture Workshops CRP 1
Deliverables Business Flows mapped to
Customer’s business High Level Solution Document
1-15 Copyright © 2006, Oracle. All rights reserved.
Elaboration Phase
DefinitionDefinition TransitionTransition ProductionProduction Elaboration BuildBuild
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
1-16 Copyright © 2006, Oracle. All rights reserved.
Build Phase
Definition TransitionTransition ProductionProductionElaboration Build
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
1-17 Copyright © 2006, Oracle. All rights reserved.
Transition Phase
Definition Transition ProductionProductionElaboration 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• Fallback Plan
Outputs:• Converted and verified data• Skilled Users• Production Support Infrastructure• Production system ready• GO-LIVE
1-18 Copyright © 2006, Oracle. All rights reserved.
Production Phase
Definition Transition ProductionElaboration 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
1-19 Copyright © 2006, Oracle. All rights reserved.
Gaps and Gap Handling
• Resolution of identified “changes” may include:– change in application configuration– manual workaround– custom extension, or– adopt the standard Business Flow, as defined
• Approved changes should be incorporated in following deliverables/work products:– Future Process Model (i.e. Business Flows)– Business Procedures documentation– Application Setup documents– System Test Scripts
1-20 Copyright © 2006, Oracle. All rights reserved. Slide 1
Copyright © 2005, Oracle. All Rights Reserved
Production Planning and Control
Material Resource Planning, Inventory
Production Planning
Material Resource Planning
Oracle Business Flow: Forecast to Plan
Forecast & Demand Management
Material Resource Planning, Order Management
Enterprise Roles
Demand Planner
Planner
Inventory Planning Manager
Demand Manager
Design to Release
Plan to ScheduleRequisition to Receipt – Direct
PF2028Manage
ProductionForecast
• Apply demand and consume forecast.
PF3001Plan
Non–MRPMaterial
• Plan non–MRP planned materials using Kanban planning, MinMax Planning, etc..
PF1966Generate
Item SafetyStock Levels
• Calculate for all locations where items have maintained safety stock levels.
PF1963Collect
DemandVariability Data
• Collect demand data including forecast confidence levels from relevant sources.
PF1967Collect
ForecastData
• Collect Sales and Shipments Data for statistical forecasts.
PF2011Generate
Sales Forecast
• Generate statistical forecast based on sales history.
PF2038Run
ProductionPlan
• Launch Production Plan
PF2039Analyze
Plan, KPIs and Exceptions
• Analyze Plan, KPI’s, exception messages and counts prior to releasing orders.
PF2040Release Schedule
• Release the production schedule to work areas and procurement.
PF3004Collaborate on Revised Constraints
• Collaborate with internal and external parties to agree on revised constraints.
PF3003Simulate
with Revised Constraints
• Run plan in simulation mode with revised constraints to model potential solutions.
PF3002AdjustPlan
• Make adjustments to the plan based on plan review and new information
PF2021Achieve
ConsensusForecast
• Review forecasts on a regular basis and revise as needed.
PF3005Implement
Revised Constraints
• Implement the revised constraints based on collaboration results.
ExampleOnly
top related