Delivering Business Process Flows A Value Added Paradigm

1
Delivering Business Process Flows A Value
Added Paradigm

• Rob Pierson
• Manager, DARC Corporation

2
Agenda

• Introduction
• Current Oracle Climate
• Project Method
• Business Flow Definition
• Pilot Approach

3
Introduction

• Providing a low risk implementation strategy
• Emphasizing business process flows
• Discuss a non-traditional approach to Oracle
  implementations

4
Current Oracle Climate

• Project Motivations
• Incremental Improvements
• Risk Reduction Support
• Total Cost of Ownership (TCO)
• Business Enablers

5
Current Oracle Climate

• E-Business Suite
• Suite vs. module licensing
• Major version releases
• Patching strategies

6
Current Oracle Climate

• Impact ROI analysis replaces risk analysis
• Projects are no longer justifiable to eliminate
  risk
• Compelling TCO Arguments
• Business case needed to drive business redesign

7
Current Oracle Climate

• Impact Projects are Internally Led
• IT business staff responsible for delivering
  success
• Consultants used piecemeal
• Emphasis on knowledge transfer
• Reduced budgets elongated timelines
• Poorly executed methodologies

8
Current Oracle Climate

• Question How can Oracles E-Business Suite be
  strategically deployed with todays IT
  constraints?
• Answer Execute internally led projects grounded
  in the business flow design approach

9
Project Method - Mobilization

• Objectives
• Identify model a key business process
• Establish the business case
• Promote knowledge transfer
• Drive the organizational buy-in

10
Project Method - Mobilization

• Approach
• Fixed budget timeline, variable scope
• Oracle business flows
• Shared workplan tasks
• Shared deliverables

11
Project Method - Mobilization

• Project Organization
• Greater focus on senior management roles
• Greater use of steering committee
• Smaller execution team
• Fewer but more highly skilled consultants

12
Project Method - Mobilization
13
Project Method - Mobilization

• Deliverables
• Business Case
• Return on Investment
• Oracle e-Business Suite
• Next project phase

14
Project Method Reqts

• Gather 80 of requirements key issues
• Investigate solution scalability
• Map transactions and workflows
• De-emphasize LOVs, detailed requirements

15
Project Method Business Flows
16
Project Method Business Flows

• Combination of flow diagrams, Oracle setups,
  workflow
• Create TO Be process diagrams
• Identify business transactions in each block
• Map business transaction to Oracle transactions

17
Project Method Business Flows

• Combination of flow diagrams, Oracle setups,
  workflow (cont.)
• Determine setup needed to support transactions
• Determine data for transactions and setups

18
Project Method Business Flows
19
Project Method Business Flows

• Combination of flow diagrams, Oracle setups,
  workflow (cont.)
• Analyze seeded workflows
• Determine custom workflow needs
• Determine data for custom workflows

20
Project Method GAP Analysis

• Prioritize requirements
• Variable scope concept
• Defer to future projects/application versions

21
Project Method Instance Management

• Determine application version required to support
  business process
• Identify production application version
• Determine patching strategy
• Determine regression testing approach

22
Project Method Release Management

• Clone production patch to required levels
• Be prepared with patch instance
• Additional instances may be required I.e.
  training, testing
• Evaluate separate production upgrade initiative

23
Project Method CRP

• Demonstrate Business Flows
• Address hot button issues
• Refine business case
• Refine ROI
• Continue to manage buy-in

24
Conclusion

• Organizations are struggling with top level
  support
• Keep projects smaller and emphasize buy-in
  concept
• Position the organization for ongoing change
• Stay abreast of ongoing Oracle e-Business Suite
  developments