ABF Overview

1-1 Copyright Oracle, 2007. All rights reserved.
AIM for Business Flows

Method Overview

Agenda
Installing the ABF Desktop Method Pack
Navigating the ABF Method Pack
Method Overview
ABF Project Flow: Definition Phase
ABF Project Flow: Elaboration Phase
ABF Project Flow: Build Phase
ABF Project Flow: Transition Phase
ABF Project Flow: Production Phase
Planning an ABF Project
Agenda
Method Overview
Method Pack Description
Easy to Install
Single downloadable installation file
One click installation (self extracting process)
Designed to accept updates

Self Contained

Easy to use
Minimal learning curve (Standardized across method offerings)
No requirement to understand underlying file structure
HTML interface to all materialsonly two clicks away
Tight integration between all method offering components
Installation Process
Installing the AIM for Business Flows Desktop Method
Pack is a three (3) step process:
Step 1 Obtain the self-extracting zip executable file
Step 2 Double-click on the ABF14.exe file
Step 3 Follow instructions displayed during installation
Note the following tips during installation process
Be patientlet the process complete
It is okay to reinstallprefer this versus stopping process
The method offering will display in your default browser
For desktops with XP, you may need to adjust your Pop-up
blocker settings
(The install process will not complete until you close the browser
window)

Post Installation
Congratulations, you now have AIM for Business Flows
Method Pack installed on your desktop!

All method components are located in a protected, pre-
designated directory structure on C:\Method, which you
have access to through an HTML user interface

Launching AIM for Business Flows Desktop Method
Pack:
1. Click start
2. Click All Programs
3. Place cursor on Oracle Methods
4. Slide cursor over to AIM for Business Flows 1.4 and left
mouse click

Agenda
Working with Templates
Online Walkthrough of the ABF Method
Agenda
Method Overview
What is AIM for Business Flows?
Latest iteration of Oracle Consultings proven
Application Implementation Method (AIM)
Incorporates changes that:
Promote a business process focus
Employs Conference Room Pilots (CRPs)
Iterative Approach
Does not restrict tailoring of Flows or system
configuration to satisfy client requirements
Approach Objectives
Rapidly deploy an environment using Standard
Business Flows, and pre-tested configurations
Standard => Future Process Model
Incorporate user involvement throughout the
lifecycle using iterative conference room pilots
(CRPs)
Employ CRPs to map business flows to customer
business processes and identify gaps
Flows are reasonably good fit
Customers willingness to adopt basic elements
of E-Business Suite best practices as described in
flows

Definition Build Production Transition Elaboration
Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Approach Overview Top Level Flow
Method Structure Fundamentals
A task is a unit of work that results in output of a single
work product or revision of an existing work product
(deliverable)

A phase is a chronological grouping of tasks in an
approach. Services are delivered by phase to reduce
project risk. Phases allow checkpoints against project goals
and measurement of quality.

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

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 WS
Customer Education on CRP Process
Conduct CRP 1

Outputs:
CRP 1 Results
Preliminary Conceptual Architecture
Key Configurations (COA, TCA, Multi-Org)
Definition
Transition
Production
Elaboration Build
Elaboration Phase
Definition 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
Build Phase
Definition Transition Production Elaboration
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
Conduct CRP 3
Conduct User Acceptance Test

Outputs:
System Tested Applications
User Acceptance Test Results
Performance Test Report
Transition and Contingency Plan
Transition Phase
Definition
Transition
Production Elaboration 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
Production Phase
Definition 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
ABF Processes
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 Production Elaboration Build
ABF Process Objectives
[BF] Business Process Mapping: The goal of the BF process is
to familiarize the Customer with Oracle Business Flows and conduct
the initial mapping of flows to the clients business.
[TA] Application and Technical Architecture: The goal of the
TA process is to design an information system architecture that
realizes the business vision.
[MD] Module Design and Build: The MD process focuses on
the design and development of custom extensions to satisfy gaps in
functionality.
[CV] Data Conversion: The goal of the Data Conversion process
is to convert all legacy data necessary for the operation of the new
system.
[DO] Documentation: The Documentation process augments
Oracle Applications manuals with information about custom
extensions and business procedures.
ABF Process Objectives (Cont.)
[TE] Business System Testing: The Business System Testing
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.
[PT] Performance Testing: The Performance Testing process
involves the definition, construction, and execution of a performance
test.
[AP] Adoption and Learning: The Adoption and Learner (AP)
process fosters acceptance of the new applications by all users
[PM] Production Migration: The goal of the Production
Migration (PM) process is to migrate the organization, systems, and
people to the new enterprise system.
Agenda
Method Overview
Definition Phase Objectives
Objectives of the Definition Phase include:
Define Project Scope clearly
Verify Senior Executive Buy-in
Facilitate Informed Project Startup Decisions
Build Consensus around scope, objectives and
approach
Familiarize Client with Business Flows
Perform initial mapping
Develop preliminary conceptual architecture
Determine high-level requirements
Obtain Approval to proceed to next phase

Key Activities Definition Phase
Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Project Planning
Define and Confirm Scope*
Review Project Approach*
Define Management Strategies and Processes*
Prepare Project Management Plan (PMP)*
Obtain Client Approval of PMP*
Orient and Train Project Team

Performed in Project Startup
Phase when using PJM 4.1
*
Build Required Delivery Assets
ABF is aware ofand leverages pre-defined/pre-
seeded delivery assets to accelerate the
implementation
Business Flows
Core Functionality Definitions
Application Setup Documents
System Test (Demo) Scripts
Inventory available delivery assets
Determine degree of fit
Identify missing delivery assets
Identify delivery assets requiring modification
Build/Modify delivery assets, as necessary

Conduct Business Architecture
Workshops
Workshops for identifying key setup parameters
that apply across the entire EBS:
Multi-Org Structure
Chart of Accounts (COA) Structure
Trading Community Architecture (TCA)
Other Workshops to consider:
Other Key Flexfields (Asset Category, Inventory Itm)
SysAdmin Security
Territory Manager (CRM Flows)
Roles, Groups, Team (CRM Flows)
Architecture Review and Performance Mgmt
Assessment Workshop
Prepare for CRP 1 Workshops
Review status of CRP 1 Environment preparation
Ensure tailoring of environment is completed, if
required
Conduct test to verify proper configuration
Determine number of Business Flow streams/
number of workshops per stream
Identify demo/test scripts to be conducted during
each workshop
Identify participants (including Client personnel)
Schedule Workshops and participants
Gather and review demo/test scripts
Conduct CRP 1 Workshops
CRP 1 typical duration ~ 2 weeks
Initial session to orient participants and familiarize
client with baseline Flows
Recommend assignment of facilitator and scribe,
if possible
Hands-On session day + Review results
Execute test scripts as scheduled on the pre-
configured system
Familiarize client with Business Flows
Map standard Flows to clients business
Document potential changes needed (Change
Catalog)
Review all changes identified at end of each
workshop session
High-Level Solution Document [Initial]
Prepare it based on CRP 1 results
Describes Business Flows and associated
functionality to be implemented
Future Process Model (diagrams)
Narrative description of processes
Explicitly identifies any standard functionality that
will not be implemented
Conduct Phase-End Review
Review proposed business process changes or
other modifications
Document/present options for filling gaps
Prepare MoSCoW prioritization of proposed
changes
Must Have
Should Have
Could Have
Wont Have
Obtain client approval/signoff

Active Processes Definition Phase
Business Process Mapping (BF)
Application & Technical Arch. (TA)
Module Design and Build (MD)
Data Conversion (CV)
Documentation (DO)
Business System Testing (TE)
Performance Testing (PT)
Adoption and Learning (AP)
Production Migration (PM)
Build Definition Production Transition Elaboration
Key Deliverables of the Definition Phase
Skilled Project Team
Mapped Business Data
Preliminary Conceptual Architecture
Project Readiness Roadmap
CRP 1 Workshop Results
Test Script results
Change Catalog
Updated Business Flows
Updated Application Setups
Updated Test Scripts/Scenarios
Phase-End Review Results
Agenda
Method Overview
Elaboration Phase Objectives
Objectives of the Elaboration Phase include:
Conduct CRP 2 to refine the solution
Validate decisions on Multi-Org, COA, and TCA
structures
Refine the technical architecture design
Develop Performance Testing models and scenarios
Design the security architecture
Develop designs for Custom Extensions
Develop Test Scripts
Design Performance Test Scripts and Programs
Develop User Learning Plan

Key Activities Elaboration Phase
Production Definition Build Transition Elaboration
Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Begin with a freshly installed,unconfigured
Applications environment
Hosted or Onsite
Configure environment to incorporate:
Clients Multi-Org structure
Clients Chart of Accounts (COA) Structure
Clients Trading Community Architecture (TCA)
Other changes identified during CRP 1
Oracle Accelerator Pre-Production instance with
Setup Tool an option
Prepare for and Conduct CRP 2
Workshops
Ensure Key Delivery Assets are updated with
changes, including:
Business Flows
Test Scripts/Business Flow Scenarios
Application Setup Documents
Business Procedure Documentation (Tutor
Procedures)
Plan and schedule CRP 2 Workshops
Execute CRP 2 Test Scripts/Scenarios
Document needed changes
Objective identify all remaining changes so
scope can be frozen
Design Custom Extensions & Prepare Test
Scripts
Define and Estimate Application Extensions and
Interfaces
Review alternative solutions with client and obtain
approval to proceed with selected option
Create Functional Design
Design Database Extensions
Create Technical Design
Review Functional and Technical Designs
Obtain client acceptance
Develop Unit Test Scripts
Develop Link Test Scripts

Solution Review and Sign-Off
Finalize High-Level Solution Document
Review proposed business system with
client/Project Steering Committee
Obtain Client acceptance of the proposed solution
and approval to proceed.

Review proposed business process
changes or other modifications
Document/present options for filling gaps
Prepare MoSCoW analysis of proposed
changes
Must Have
Should Have
Could Have
Wont Have
Active Processes Elaboration Phase
Documentation (DO)
Key Deliverables Elaboration Phase
CRP 2 Results
Conceptual Architecture
Application and Database Server Architecture
Platform and Network Architecture
Application Extension Definition and Estimates
Approved Designs Custom Extensions
Conversion Program Designs
Updated System Test Script
System Integration Test Script
User Learning Plan
High-Level Solution Document [Final]
Solution Acceptance & Signoff
Agenda
Method Overview
Build Phase Objectives
Objectives of the Build Phase include:
Prepare the Development Environment
Develop, test and accept custom software
Create, test and accept database extension and
installation routines
Propose a transition strategy
Finalize the solution
Conduct CRP 3 (System Test)
Conduct Performance Test
ABF V1.3 Top Level Flow
Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Create and Test Custom Extensions
Create:
Prepare Development Environment (MD.090)
Create Database Extensions (MD.100)
Create Application Extension and Interface
Modules (MD.110)
Create Installation Routines (MD.120)
Test:
Perform Unit Test (TE.070)
Perform Link Test (TE.080)
Perform Installation Test (TE.090)
Begin with a freshly installed,unconfigured
Applications environment
Hosted or Onsite
Configure environment to incorporate:
All changes confirmed in CRP 2
New changes identified in CRP 2 and approved
Oracle Accelerator Pre-Production instance with
Setup Tool an option
Employ Data Conversion programs to load legacy
data
Employ installation routines to install custom
extensions

Prepare for and Conduct CRP 3
Workshops
Ensure Key Delivery Assets are updated with
changes from CRP 2
Update Test Scripts to include business
processes involving custom extensions and
converted legacy data
Plan and schedule CRP 3 Workshops
Consider how best to integrate custom extensions
Execute CRP 3 (System Test) Scripts
Validate Business Procedure Documentation
Document needed changes (minor changes OK)
Objective System Test/Validate the system

Perform Systems Integration Test
Test Oracle E-Business Suite integration with
other application systems
Conducted in a Production-like environment
Objective validate the operation of the business
system across and between application systems
Includes testing of operating routines and
procedures, as well as programs
Perform User Acceptance Test
Consulting Role is to support users in performing
their acceptance test.
Also involves scheduling participants, resources,
support staff
Conducted in production-like environment
Scope dependent on acceptance criteria defined in
the Project Management Plan (PMP)
Scope may change if users are participating
substantially in CRP 3/Systems Integration Test
Conducted in accordance with standards and
procedures established in Testing Requirements
and Strategy (TE.010)
Review results of:
CRP 3
Systems Integration Test
User Acceptance Test
Performance Test

Active Processes Build Phase
Documentation (DO)
Key Deliverables Build Phase
System-Tested Applications
Validation-Tested Conversion Programs
Link Tested custom modules
User Acceptance Test Results
Integration-Tested System
Performance Test Report
Transition and Contingency Plan
Agenda
Method Overview
Transition Phase Objectives
Objectives of the Transition Phase include:
Install data conversion programs and automated
utilities
Convert and verify legacy data
Train user personnel
Prepare the Production environment and configure the
Applications
Implement the Production Support Infrastructure
Verify that all aspects of the system are ready for
transition
Begin Production use of the system

Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Prepare Production Environment
Install database and application software
Setup applications per System Tested
configuration
Oracle Accelerator Pre-Production environment
with Setup Tool an option
Consider extent of manual setups required
Backup/restore of pristine User Acceptance Test
environment is another option
Manual configuration using Application Setup
Documents is always an option
Convert and Verify Data
Convert and migrate production legacy data to the
new applications environment
Verify legacy data cleanup completed
Define cutoff and cutover strategy
Define the data conversion and verification
sequence
Conversion order and pre and post conversion
activities are delineated in the Transition and
Contingency Plan (PM.030)
Verify and audit the converted data to ensure that
defined audit requirements are met

Verify Production Readiness
Formal verification that clients systems, host
facilities, Networks, and people are ready for
production
Consists of checklists and (optionally) a quality
assurance review to verify production readiness
Production System test verifies setups and
connectivity of printers, etc.
Begin Production
Confirm that all aspects of the system are
operational and production status is achieved
Employ the Production Schedule - First Week
component of the Transition and Contingency
Plan (PM.030) to provide focused attention on
limited areas until they are stabilized
Anticipate issues and quickly remedy them
Establish guidance for which problems should be
resolved first
Communicate to entire organization when
production status achieved
Active Processes Transition Phase
Documentation (DO)
Key Deliverables Transition Phase
Converted and verified data
Skilled users
Production Support Infrastructure
Production System
Agenda
Method Overview
Production Phase Objectives
Objectives of the Production Phase include:
Provide agreed upon level of user support
Measure system performance and enhance system
Maintain the Production system
Decommission legacy systems
Propose and plan future business and technical
direction
Build upon and improve organizational knowledge and
skills for the new environment
Improve organizational effectiveness through
continuous improvement
Devote attention to post-implementation issues like
improving productivity, etc.
Project
Planning
Design
Extensions
Prepare
Custom
Test Scripts
Create and test
Custom
Extensions
Prepare
Production
Environment
Convert and
Verify Data
Begin
Production
Maintain
System
Propose
Future
Direction
Perform Systems
Integration
Test
Verify
Production
Readiness
Prepare for CRP 1
Workshop(s)
Conduct CRP 1
Workshop(s)
Prepare for CRP 2
Workshop(s)
Conduct CRP 2
Workshop(s)
Perform User
Acceptance
Test
Build Required
Assets
Conduct
Phase End
Review
Conduct
Phase End
Review
Conduct Business
Architecture
Workshops
Conduct
Phase End
Review
Solution
Review &
Sign-Off
Prepare for CRP 3
Workshop(s)
Conduct CRP 3
Workshop(s)
Prepare CRP 2
Environment
Prepare CRP 3
Environment
Maintain System
Begin execution of System Management
Procedures
Focus on necessary and preventative actions
Regular backups
Defragment table spaces, etc.
Propose Future Direction
Propose Future Business Direction
Future business improvement opportunities
Future upgrades
Industry trends
Propose Future Technical Direction
Identify innovations and advancements in software
and technology, which offer efficiencies and cost
savings
Active Processes Production Phase
Documentation (DO)
Key Deliverables Production Phase
Effectiveness Assessment
Business Direction Recommendations
Technical Direction Recommendations
Agenda
Method Overview
Regarding this Lesson
The work products mentioned in the lesson are
included in the Project Management Method (PJM)
PJM includes tasks to define the strategy,
policies, and procedures for each of the 13 PJM
processes, including:
Bid Transition
Scope Management
Financial Management
Work Management
Risk Management
Issue/Problem Mgmt.
Staff Management
Communication Mgmt.
Quality Management
Configuration Mgmt.
Infrastructure Mgmt.
Procurement Mgmt.
Org. Change Mgmt.
What is Project Management Method
(PJM)?
Oracles Standard Approach to Project
Management

Standard global method for managing projects
Aligned with PMI and PM BOK
Appropriate for use on all types of Oracle
Consulting Engagements

PJM 4.1 Structure
Relationship of PJM 4.1 to Oracles Execution
Methods (including ABF)
Project Management Plan (PMP)
Integrates all PJM Processes
Sets expectations and communicates how the
project will be conducted
Establishes guidelines for execution of all tasks
on the workplan
Requires acceptance and sign-off by the client
Perhaps the single most important
work product produced by the
project manager!
PMP in PJM 4.1
Project Workplan
The work plan shows:
Project tasks organized within phases
Dependencies
Resource requirements and time allocations
Project
Scope
Work Plan Proposal
Creating the Work Plan
Use Estimation Workbook as starting point
Identify ABF tasks required for project completion
Identify resources and teams
Assign resources to tasks
Determine time allocation to resources by tasks
Level tasks and resource commitment
Repeat procedure
Flow Through Estimating Process
Plan & Conduct
Interviews
Define
Scope, etc.
Prepare Risk
Analysis
Enter Data
Review
Results
What If
Analysis
Generate
Workplan
Online Walkthrough of the Estimation
Workbook

ABF Overview

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ABF Overview

Transféré par

Droits d'auteur :

Formats disponibles

1-1 Copyright Oracle, 2007. All rights reserved.

AIM for Business Flows

Vous aimerez peut-être aussi