Rollout and

Merger/Demerger
Process
Document describes about various Process and
Deliverables in Rollout and Merger/Demerger
Methodology.

Purpose - CMMI Documentation | Chain.Sys -16-July-

2012
 Project Management as per PMI

Processes /Knowledge Areas Initiation Planning Execution Controlling Closing

Project Kick Off Activities
Business Process Study
Configuring the Instance
Conference Room Piloting
User Training & UAT
Cut Over Plan
GO Live
Post Production Support

Roll out and Merger/Demerger Process:

 Project Kick Off Activities

Pre Kick off @ Office | Pre Kick off @ Client | Kick Off

Business Process Study

BP Study | Data Gathering | Gap Analysis | Confirmation

Configuring the Instance

Instance Configuring | Review by SME’s

Conference Room Piloting

CRP Test Script | Testing | CRP 1 | Feed Back | CRP 2

User Training & Acceptance Testing

Document Preparation |Training | Acceptance Test

Reviewing Work Space Entry

Cut Over Plan

Cut over Period | Master Data Migration |OPG Balance

Migration Reviewing Work Space Entry

GO Live

Go Live | Post Production Support

 Project Kick off Activities: Project Kick Off Activities
Diagram:
Abstract: Pre Kick off @ Office | Pre Kick off @ Client | Kick Off

The Kickoff Meeting is the first meeting with the project team and the client of the project. This meeting would follow definition
of the base elements for the project and other project planning activities. This meeting introduces the members of the project
team and the client and provides the opportunity to discuss the role of each team member. Other base elements in the project
that involve the client may also be discussed at this meeting.

Activities Pre Kick off Activities @ Client:

: Finalization of Project Plan.

Pre Kick off Activities @ Office: Identification of Core Team from Client.
Identification of Project Manager/Team Members. Clarification of Deliverables.
Budget allocation for the project. Clarification of Payment Terms.
Project Awareness program for the team. Signing of Project Plan.
Responsibility Handbook/Communication Matrix. System Readiness.
Reporting formats (Project plan status/weekly/Change Project Kick off Activities @ Client:
request).
Introduction of Team & Project Kick off.
Preparation of Project Plan.

Resume Preparation for Team. Vision Instance Creation.

OBA Methodology Training. Key Project Activities Finalization.

Instance strategy- Clone and Backup. Organisation & COA.

AppLOAD -- Overview and Training. Data Migration Strategy – Freezing.

Project Process
Business management tool training
Study (Time sheet Entry).
Activities: Training Strategy.
Team to travel to Client Place. Business Process Study
Abstract: Diagram:
Technical Strategy.
BP Study | Data Gathering | Gap Analysis | Confirmation
 Business Process Study Activities involves in Existing Business Process Study, Data Gathering, GAP Analysis and getting
Confirmation from clients.

Activities:

Business Process Study and Data Gathering:

Schedule, confirm, and prepare for process definition sessions by business area.

Identify the core business processes (level 1 if you are using Oracle Business Models) and
write a summary description of each process.

Conduct interviews using the questionnaires and other sources of information to clarify
questions you have identified.

Gather any other current business materials that may enhance team understanding and
documenting of current business process requirements.

Identify any issues regarding the current business analysis.

Review the Current Business Baseline with users and business area management.

Secure acceptance of the Current Business Baseline from business area management.

Secure acceptance of the Century Date compliance approach described.

Configuring the Instance:

Configuring the Instance
Abstract: Diagram:
Instance Configuring | Review by SME’s
Configuring the instance involves in Configuring the Module, Options and Master.

Activities:

Creation of OBA Instance: Map Business Requirement:

Creation of new responsibility, User Logins. Fit issues into a Requirement Essay

Configuring the Setups and documenting. Perform process research; look for and document
alternatives
Configuring Module wise setups and assigns the approval
responsibilities. Identify current versus proposed process steps and
assess the feasibility of proposed alternatives
Opening the various modules Periods.
Document alternatives. Record possible alternative
Performing unit testing for Business Process wise. alternatives for application gaps
Review by SME’s and approving on the Instance. Document major operating and policy decisions

Secure acceptance of the Mapped Business

Requirements.

Conference Room Piloting:

Conference Room Piloting
Abstract: Diagram:
CRP Test Script | Testing | CRP 1 | Feed Back | CRP 2
A key project implementation strategy that tests normal business case scenarios in a proposed new system to uncover people,
process and system issues, generate resolutions, and define action steps needed to complete the implementation.

Activities:
CRP Process:
CRP, Test, PROD Instance Creation:
Demonstration of Process.
Cloning of OBA Instance and Creating CRP Instance and Test Instance.
Review of CRP Issues and Status.
Development of Custom Objects:
Freezing of MD50|MD70. CRP Sign-Off by Client Project Manager.

Development of Objects |Testing the customization In Test Instance. Customization Sign off.
CRP Instance Testing:
Appload - Testing of Data Loading in Test Instance
Test Scripts for CRP - Update scripts as required.
Functional Testing by Consultants in Test Instance.
Appload - Testing of Data Loading in CRP Instance.
Migration of changes in CRP Instance.
Migration of Custom Objects in CRP Instance.
Cloning of CRP Instance after Master Data and necessary setup changes.
Running Test cycle in CRP Instance.
Review of CRP instance configuration and Open Issues.
User Training & Acceptance Testing:
User Training & Acceptance Testing
Diagram:
Abstract: Document Preparation |Training | Acceptance Test
Reviewing Work Space Entry
UAT tests are created to verify the system’s behaviour is consistent with the requirements. These tests will reveal defects
within the system. The work associated with UAT begins after requirements are written and continues through the final stage
of testing before the client/user accepts the new system.

Activities:
Cloning of Prod Instance for UAT:
Training:
Testing the CSI.
Preparation of Training Manual.
Testing by Client.
Review of Training Manual by Project Manager, SME.
Review of UAT Instance.
Conducting Training.
Signing of UAT Completion.
Training and Training Sign-off.

UAT Instance Creation:

Prepare and Update Test Scripts for CRP

Update and Review the Production Instance with Changes Tracked.

Migrate the Patches In Prod Instance.

Migrate the Customization in Prod Instance.

Extraction of Master Data for a cutover date.

Loading of Master Data through Appload in Production Instance.

Cloning of Prod Instance for UAT

Cut Over Plan:
Cut Over Plan
Testing the CSI. Diagram:
Abstract: Cut over Period | Master Data Migration |OPG Balance
Testing by Client.
Migration Reviewing Work Space Entry
Review of UAT Instance
Cutover contingency Plan: The general checklist is used to plan and estimate the transition phase.

Activities:

Cutover Plan:

Responsibility AND user Matrix.

Close the books.

Data Extractions - Master - Incremental Data.

Data Extractions - Open Transactions.

Loading of Master Data - Through Appload in Production Instance.

User Creation.

Responsibility creations.

Go Live: GO Live
Diagram:
Abstract: Go Live | Post Production Support
The Kickoff Meeting is the first meeting with the project team and the client of the project. This meeting would follow definition
of the base elements for the project and other project planning activities. This meeting introduces the members of the project
team and the client and provides the opportunity to discuss the role of each team member. Other base elements in the project
that involve the client may also be discussed at this meeting.

Activities:

Client Go-Live.

Post Go-Live Support.

 Overview of the Project Deliverables
Project Management Plan:
 Project Plan (mostly in Microsoft Excel/Microsoft Projects).

 Scope, Objectives, Approach.

 Project Task, Deliverables & Milestones.

 Control and Reporting.

 Work Management.

 Project Resources (Men, Hardware, and Database management).

 Identified Risks & Mitigation Plan.

 Change Request and Problem Report Log Management.

 Minutes of Meeting.

 Acceptance Certificate.

 Project Team Contact Listing.

 Key Task and Responsibilities of Implementation Team.

 Overview of the Project Deliverables
Overview Training to client:
The Overview Training covers a Birds Eye view of

 Basic Modules of ERP.

 Integration between Modules.

 Menu, Sub Menu, Function.

 Responsibilities and Users.

 Icon Buttons.

 Concurrent Processes.

 Accounting.

 Reports.

 Workflow Notifications.

 Database, Forms, Reports.

 Different Instances.

 Implementation Approach.
 Overview of the Project Deliverables
Organisation/COA Structure:
 Interview organization management to obtain a clear understanding of current and proposed
entity structure.

 Develop a chart showing the current organization structure. - Organization Legal Entity
Structure Chart.

 Develop a business organization overview and listing. - Business Organization Listing and
Overview.

 Define and chart the Financial Operating environment. - Financial Operating Environment.

 Define the financial and management reporting environment. - Financial and Management
Reporting Environment.

 Review the Current Financial and Operating Structure with project management and secure
approval.

 Review the Current Financial and Operating Structure with appropriate organization
management and secure acceptance for the deliverable.
 Overview of the Project Deliverables
MD050 – Functional Design
The essential content of MD050 are as follows

 Review Mapped Business Requirements (BR.030).

 Write the topical essay.

 Document forms.

 Document reports

 Document concurrent programs.

 Describe the technical approach.

 Review the high-level design with analysts and key users.

 Obtain approval for the Application Extensions Functional Design by the requester.
 Overview of the Project Deliverables
MD070 –Technical Design
The essential content of MD070 are as follows

 Review Application Extensions Functional Design (MD.050).

 Describe the high-level approach.

 Define detailed program logic for modules (forms, reports, and programs).

 Document integration issues. Integration Issues

 List installation requirements.

 Document any additional information that may be helpful during the implementation of the
customization.

 Update Application Extensions Functional Design (MD.050), as needed.