erp abf cm

8/11/2019 erp abf cm

1/40

AppsPro

Introduction Presentation

About ERP, Oracle ABF, Change Management


2/40

ERP

Enterprise Recourse Planning


3/40

1-3

ERP

ERP Definit ion:

Solution that addresses the enterprise needs taking theprocess view of an organization to meet the organizationalgoals tight ly integrating all functions of an enterprise.

What is ERP?

Facili tates company-wide integrated information systemscovering all funct ional areas

Performs core corporate activit ies and increase customerservice augmenting corporate image.

Why ERP?

Complete integration of system across the departments in acompany as well as across the enterprise as whole

The only solut ion for better project management

Better customer service

Automatic introduction of latest technologies

Expertise database


4/40

1-4

ERP Advantages?

Ease of use. Readymade solutions for most of the problems.

Integration of all functions already established & easilyexpand or update

Easy enterprise wide information sharing.

Suppl iers & customers can be on-line communication. Knowledge transfer between industries guarantees

innovation.

Updatable for new technology.

Documentation is part system.

Constant updates on technology & processes assured. The best solution for integrated systems for a client

with multiple location

ERP


5/40

1-5

Strategic Business Benefits

An enterprise systems solution must address people, process and

technology to support an organizations mission, vision and strategy.

Change Management focuses on support ing the people component of a

change initiative.


6/40

1-6


7/40


8/40

Oracle ABF


9/401-9

What is Oracle ABF

AIM for Business Flows is the latest iterat ion of Oracle Consult ings proven

Appl ication Implementation Method (AIM). It incorporates changes that suppor t the

use of Oracle Business Flows, associated software environments, and preceded

implementation assets, to accelerate the implementation timeline and keep the focus

of an implementation on business processes and benefits, rather than software

features and functions.

A Business Process Focus

Use of pre-defined Oracle Business Flows as the starting point Future Process

Model

Rapid establishment of a software environment, based on Oracle Business

Flows, for use in mapping the customers business to Oracle Business Flows

Early introduction of iterative hands-on user testing cycles


10/40


11/401-11

What is an OracleBusiness Flow ? OracleBusiness Flows are Business Flows opt imized

for Oracle Applications. They represent a leadingpractice approach to employing standard functionality

contained in Oracles E-Business Suite.

Oracle Business Flows help customers relate to how

Oracle EBS solves their business problems.

Oracle Business Flows help customers see themselves

& their business processes in Oracles software.
http://../Documents%20and%20Settings/srahikai.UK-ORACLE-NT/srahikai.UK-ORACLE-NT/srahikai.UK-ORACLE-NT/Local%20Settings/Local%20Settings/DOCUME~1/Local%20Settings/Temporary%20Internet%20Files/Local%20Settings/Temp/BF020_ANALYZE_TO_AGREEMENT.PPT


12/40


13/40


14/401-14

AIM for Business Flows (ABF)

AIM for Business Flows

Processes

Business Process Mapping

Appl ication & Tech Architecture

Module Design & Bui ld

Data Conversion

Documentation

Business System Testing

Performance Testing

Adoption & Learning

Production Migration

AIM for Bu siness Flows Phases

Dfinition

E

laboration

Build

Transition

P

roduction


15/40


16/401-16

ABF Phases: Definition

Tasks and Activi ties

Develop a detailed project plan and work plan Customers Project Team Training

Update or buil d 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 Customers business) Business Requirements Mapping Gaps (V 1.0)

High Level Solut ion Document (V1.0)

Preliminary conceptual architecture for the new

Preliminary Support ing Approach Documents

Set ups for CRP 2.0

Assumptions

Customer will provide adequatepersonnel for the workshops.

These persons w ill have a good

knowledge of the processes and canmake or obtain decisions required as

agreed in Project Plan.

Definition

Elaboration

Build

Transition

Production


17/401-17

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 Customers business) Business Requirements Mapping Gaps (V 1.0)

High Level Solut ion Document (V1.0)

Preliminary conceptual architecture for the new

Preliminary Support ing Approach Documents

Set ups for CRP 2.0

ABF Phases: Definition


Develop a detailed project plan and work plan Customers Project Team Training

Update or buil d Flow Assets

Conduct Business Architecture Workshops

Conduct CRP 1 Workshops

Develop preliminary conceptual architecture

Develop Supporting Approach Documents

(Testing, Conversions, Interfaces, Transition ..)

Assumptions

Customer will provide adequatepersonnel for the workshops.

These persons w ill have a good

knowledge of the processes and canmake or obtain decisions required as

agreed in Project Plan.

Definition

Elaboration

Build

Transition

Production

Business Architecture

Workshops

CRP 1

Business Flows mapped

to Customers business

High Level SolutionDocument

ABF Ph El b ti


18/401-18

ABF Phases: Elaboration

Tasks and Activi ties Detailed Planning of the Phase

Build and setup CRP 2.0 Environment

Conduct CRP 2.0 Workshops Determine disposit ion of each exception/gapUpdate Flow Documentation, revise system

setups and test scripts to reflect required changes

Create functional and technical design documentsfor conversions, in terfaces and extensions , if any.

Update /finalise supporting Approach Documents

Accept phase and solution

Assumptions

Customer will provide personnel forworkshops as in Definition Phase

Customer will adjust business processes asnecessary to match standard Application

Flows or approve a change order for systemextensions

Deliverables Configured test system for CRP 2.0

Accepted Solution with Deliverables:

Future Business Model (V 2.0)

Bus. Requirements Mapping Gaps (v2.0),closed

High Level Solution Document (V 2.0)

Updated Test Scripts

Updated Set Up documents

Approved functional & technical designs for

conversions , interfaces and extensions, if any

Updated Supporting Approach Documents

Definitio

n

Elaboration

Build

Transitio

n

Productio

n

ABF Ph El b ti


19/401-19

ABF Phases: Elaboration

Tasks and Activi ties Detailed Planning of the Phase

Build and setup CRP 2.0 Environment

Conduct CRP 2.0 Workshops Determine disposit ion of each exception/gapUpdate Flow Documentation, revise system

setups and test scripts to reflect required changes

Create functional and technical design documentsfor conversions, in terfaces and extensions , if any.

Update /finalise supporting Approach Documents

Accept phase and solution

Assumptions

Customer will provide personnel forworkshops as in Definition Phase

Customer will adjust business processes asnecessary to match standard Application

Flows or approve a change order for systemextensions

Deliverables Configured test system for CRP 2.0

Accepted Solution with Deliverables:

Future Business Model (V 2.0)

Bus. Requirements Mapping Gaps (v2.0),closed

High Level Solution Document (V 2.0)

Updated Test Scripts

Updated Set Up documents

Approved functional & technical designs for

conversions , interfaces and extensions, if any

Updated Supporting Approach Documents

Definitio

n

Elaboration

Build

Transitio

n

Productio

n

Gap Handling

CRP 2s Update documents

Designs for conversions,

extensions, interfaces

Accepted Solution with

updated documents

Designs for conversions,

extensions, interfacesapproved


20/401-20

ABF Phases: Build


Detailed Planning of the Phase

Build CRP 3.0 Environment

Finalize conversion , interfaces andextensions, if any, and test

Conduct CRP 3.0 System and IntgrationTesting 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 toconduct CRP 3.0 testing as required by

project plan Customer is responsible for testing and testdata

Solution func tionality can be changed onlythrough Change Order process

Definition

Elaboration

Build

Transition

Production


21/401-21

ABF Phases: Build



Build CRP 3.0 Environment

Finalize conversion , interfaces andextensions, if any, and test

Conduct CRP 3.0 System and IntgrationTesting 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 toconduct CRP 3.0 testing as required by

project plan Customer is responsible for testing and testdata

Solution func tionality can be changed onlythrough Change Order process

Definition

Elaboration

Build

Transition

Production Finalize conversions,

interfaces, extensions

CRP 3 = System and

Integration Testing

User Acceptance Testing

Tested Solution

Final designs for

extensions, interfaces

Transition Plan


22/401-22

ABF Phases: Transition



Configure production system

Convert and verify all system data

Perform end user training

Perform production readiness review

Deliverables Converted and verified data

Acceptance test resul ts

Production system validation

Trained End Users Readiness Review

Configured production system

Assumptions

Customer will prepare end usertraining manuals and conduct end user

training prior to production

Definition

Elaboration

Build

Transition

Production


23/401-23

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 adequatelytrained and prepared to adopt new

App licat ions infrast ructure

Customer will decommission legacysystems

Definition

Elaboration

Build

Transition

Production


24/401-24

Phase

Phases are a grouping of tasks that

lead to a major project work product

or milestone

Phases are temporal groupings

Phases cut vertically through

the project

Are natural points to establish

milestones for progress

checkpoint

Phases

Inception ProductionTransitionElaboration Construction


25/40

1-25

Activity

Project Start Up

Review Bid and Contract

Review and Analyze Bid

MaterialReview and Confirm BusinessCase

Identify Stakeholders

Activities are grouping of tasks that

lead to a major project work product

or milestone within a Phase.

Phases are a roll-up of the Activities

Activities a roll-up of tasks

Inception ProductionTransition

Activi ties

Elaboration Construction


26/40

1-26

Task

Inception ProductionTransition

Atask is a unit of work that results in

output of a work product or revision of

an existing work product

Task Examples

Setup of an application

Creation or update of a document

Execution of an activity (i.e TestPlan)

Work Product

Not every work product is given tocustomers

Tasks

Elaboration Construction


27/40

1-27

Process

A processis a grouping of tasks

within a method based ondisciplines or skills.

Processes

Examples:

Finance Management

Quality Management

Risk Management

Inception ProductionTransitionElaboration Construction


28/40

1-28

Active Processes Definition Phase

Business Process Mapping (BF)

App licat ion & Technical Arch. (TA)

Module Design and Build (MD)

Data Convers ion (CV)

Documentation (DO)

Business System Testing (TE)

Performance Testing (PT)

Adoption and Learning (AP)

Production Migration (PM)

BuildDefinition ProductionTransitionElaboration


29/40

1-29

ABF Process Objectives

[BF] Business Process Mapping:The goal of the BF process is

to familiarize the Customer with Oracle Business Flows and conductthe initial mapping of flows to the clients business.

[TA] Application and Technical Architecture: The goal of theTA process is to design an information system architecture that

realizes the business vision.

[MD] Module Design and Build: The MD process focuses onthe 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 newsystem.

[DO] Documentation: The Documentation process augmentsOracle Applications manuals with information about custom

extensions and business procedures.


30/40

1-30

ABF Process Objectives (Cont.)

[TE] Business System Testing:The Business System Testing

process has the goal of refining the business solution through iterativeConference Room Pilots and testing the quality of all elements of the

application system.

[PT] Performance Testing: The Performance Testing processinvolves 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 ProductionMigration (PM) process is to migrate the organization, systems, and

people to the new enterprise system.


31/40

1-31

What is a CRP in ABF ?

Workshops are used as the primary working model

between Customer and Consultants.

Implementation Consultantsare responsible forproviding Oracle Applications knowledge, updating

project flow documentation, planning and

facilitating the workshops.

Customeris responsible for providing Customersprocesses and requirements knowledge and

making necessary timely decisions.


32/40

1-32

CRP Definit ions (for EBS)

Phase CRP Objectives

Definition CRP 1.0 Familiarize the customer with the Business Flowsbeing implementedandmap Business Flows to thecustomers business and identify potential changes.

Elaboration CRP 2.0 Validate customer Chart of Accounts, Multi- OrgStructure, TCA structure and other personalizedsetups identified during CRP 1. Refine mapping of

Business Flows to the customers business andidentify any remaining changes necessary. Theconclusion of CRP 2.0 should result in a frozensolution scope.

Build CRP 3.0 Business System Test of tailored solution includingcustom extensions and sample converted legacydata. Refinement of solution is still an option at thispoint, but the scope of changes should be small bythis time. Significant changes at this point mayindicate the need for an additional CRP 3 iteration.


33/40

1-33

CRP Objectives

CRP 1

- Familiarization

- Initial mapping & identify gaps

- Identi fy setup required for CRP2 instance (e.g. COA, Mult i-Org,

TCA)

CRP 2

- Refine mapping and gaps

- Validate flow setup

- Validate business process (flows)

- Identify & build extensions, interfaces

- Freeze scopeCRP 3

- Business System Test (test extensions, interfaces,

performance)


34/40

Change Management


35/40

1-35

Change Management a working definition

The process (strategies and activit ies) that

supports organizational and personal

transitions from the current state to the desired

future state brought about by technology andbusiness process improvements.


36/40

1-36

Current

State

Transition Period

Future

State

New processes,organizationalstructure,technology, people,and organizationalculture

The States of Change

Processes,organizationalstructure,technology, people,and organizationalculture


37/40

1-37

Why ERP init iatives fail

20% 40% 60% 80% 100%

Peoples Resistance to Change

Limitations of Existing Systems

Lack of Top Management Suppor t

Lack of Executive Champion

Lack of Cross-Functional Team

Inadequate Team and User Skills

IT Staff Involved Too Late

Project Charter Too Narrow

Unrealisti c Expectations

n The Solution:A change management methodology byproviding executives and managers with a structureapproach to that will address people issues and reduceresistance problems


38/40

1-38

5 Attributes to Adoption of Change

Relative Advantage: Is i t better than w hat i t replaces?

Compatibility: Does i t f it my values?

Complexity:How hard easy is i t to do ?

Try-ability: Can I try i t a b it at a t ime?

Observe-ability: Can I see it w ork ing?

A good change management program

must address these attributes


39/40


40/40