Anda di halaman 1dari 7

1

ASAP IMPLEMENTATION
METHODOLOGY
How to use the Template
Blue text is always intended as instructions, guidelines, explanations, hints, and tips. It has to be removed when the
document is finalized. To provide a consistent representation of this document to the customer, chapters should not be
deleted or inserted. Required additions should be made as sub-chapters to existing chapters.
Chapters that are not relevant should be marked as such (that is, add not relevant or not applicable).
Be sure to delete these instructions when you have finished!

FINAL CUTOVER CHECKLIST


SAMPLE DOCUMENT

PROJECT IDENTIFICATION
Delete Project Identification table if not applicable for the document!
Project Name

CPI Project Number

<Project Name>
Customer Name

Customer Number

<Customer Name>
SAP Project Manager

Customer Project Manager

<SAP Project Manager>

<Customer Project Manager>

Author

Document Location (repository/path/name)

<Author>

<Document location>

Version

Status

Date (YYYY-MM-DD)

Document Classification

0.1

Final

<Date>

Confidential

REVISION HISTORY
Delete Revision History section below if not applicable for the document!
Version

Date

Description

0.1

February 4, 2010

<Text here>

0.2

REVIEW AND APPROVAL


Delete Review and Approval section below if not applicable for the document!

Name
Customer Project Manager

Date (YYYY-MM-DD)

Name
SAP Project Manager

Date (YYYY-MM-DD)

Name
Key Stakeholder

Date (YYYY-MM-DD)

Name
Key Stakeholder

Date (YYYY-MM-DD)

3
TABLE OF CONTENT
Introduction..................................................................................................................................................... 4
Technical Infrastructure Acceptance Criteria............................................................................................ 4
Functional Functional System Design Acceptance Criteria....................................................................4
Development Development System Design Acceptance Criteria............................................................5
Authorizations System Security Acceptance Criteria..............................................................................5
Data Cleansing Data Cleansing Acceptance Criteria................................................................................5
Data Conversion Data Conversion Acceptance Criteria..........................................................................6
Training Training Acceptance Criteria....................................................................................................... 6
Organizational Readiness Organizational Readiness Acceptance Criteria............................................6
Project Management Deployment Acceptance Criteria............................................................................7

INTRODUCTION
The Final Cutover Checklist reviews points of readiness, and provides the basis for approval to proceed with
the cutover. It is intended to capture all of the signatures that are needed in order to approve the
organization to go live with the new system.
The Final Cutover Checklist contains the acceptance and approval criteria for each key area that has been
identified as part of the overall Migration process. The items listed should be checked and completed by the
AIM Company organization in order to successfully go live. This document complements the Cutover
Checklist. The Cutover Checklist details all of the activities, dependencies, dates, times, resources and
status in depth related to the entire cutover process. This checklist serves as an additional validation list for
approving all of the work completed as part of the overall deployment.
The following key areas have been defined:
Technical (Infrastructure)
Functional (System Design)
Development (System Design)
Authorizations (System Security)
Data Cleansing
Data Conversion
Training
Organization (Readiness)
Project Management, (Deployment)
TECHNICAL INFRASTRUCTURE ACCEPTANCE CRITERIA
The acceptance criteria for the hardware infrastructure, system performance and SAP BASIS functions
for the SAP technical environment are as follows:
Acceptance Criteria
1. Volume and stress tests have been completed and results are successful;
2. The SAP landscape is consistent with SAP Support Pack levels;
3. Cutover test runs (min. of 3 cycles) have been completed and results documented;
4. Infrastructure system & connectivity testing are complete
5.

Authority

Name

Technical PM

First Last

Signature

Date

FUNCTIONAL FUNCTIONAL SYSTEM DESIGN ACCEPTANCE CRITERIA


The acceptance criteria for the functional SAP HR system are as follows:

Acceptance Criteria
1. Configuration work is complete and meets requirements as defined;
2. Integration/Regression testing is complete and results successful;
3. Customer Acceptance Testing, (CAT) is complete and results successful.
4.

Authority

Name

Functional PM

First Last

Signature

Date

DEVELOPMENT DEVELOPMENT SYSTEM DESIGN ACCEPTANCE CRITERIA


The acceptance criteria for development for the SAP system are as follows:
Acceptance Criteria
1. SAP Development work is complete and meets requirements as defined;
2. Bid Management Development work is complete and meets requirements as defined;
3. Payroll interface is complete and meets requirements as defined;
4. Interface testing is complete and results successful;
5. SAP Development testing is complete and results successful;
6. AIM Development work is complete and meets requirements as defined;
7. AIM Regression testing is complete and results successful.
8.
Authority

Name

Technical
Project Lead

First Last

Signature

Date

AUTHORIZATIONS SYSTEM SECURITY ACCEPTANCE CRITERIA


The acceptance criteria for authorizations for the SAP HR system are as follows:
Acceptance Criteria
1. User accounts are established and meet requirements as defined;
2. User account testing is complete and results successful;
3.

Authority

Name

HCM Program
Manager
Portfolio
Program
Manager

First Last

Signature

Date

First Last

DATA CLEANSING DATA CLEANSING ACCEPTANCE CRITERIA


The acceptance criteria for data cleansing for the SAP HR system are as follows:
Acceptance Criteria
1. Employee Master Data to be converted is clean, accurate and has been validated;

6
2. Organizational Structure data to be converted is clean, accurate and has been
validated;
3. Position/Job Slot data to be converted is clean, accurate and has been validated;
4. Job Bid Management data to be converted is clean, accurate and has been validated;
5. Qualifications data to be converted is clean, accurate and has been validated.

Authority

Name

ERP Integration
PM

First Last

Signature

Date

DATA CONVERSION DATA CONVERSION ACCEPTANCE CRITERIA


The acceptance criteria for data conversion for the SAP HR system are as follows:
Acceptance Criteria
1. Data conversion programs are complete and meet requirements as defined;
2. Data conversion program testing is complete and results successful;
3. Data conversion process is defined, sequenced, timed, tested and documented for final
cutover.

Authority

Name

Technical
Project Lead

First Last

Signature

Date

TRAINING TRAINING ACCEPTANCE CRITERIA


The acceptance criteria for the planning, design, development and delivery of all training courses for the
SAP HR system are as follows:
Acceptance Criteria
1. End user training materials are complete and meet requirements as defined;
2. Work instructions are complete and meet requirements as defined;
3. Initial end-users have been identified and trained.

Authority

Name

Training Lead

First Last

Signature

Date

ORGANIZATIONAL READINESS ORGANIZATIONAL READINESS ACCEPTANCE CRITERIA


The acceptance criteria for the organizational readiness and overall Business Process Implementation
planning, and delivery applicable to the SAP HR system is as follows:

7
Acceptance Criteria
1. Change Management activities complete for areas affected by transition.

Authority

Name

Change
Management
PM

First Last

Signature

Date

PROJECT MANAGEMENT DEPLOYMENT ACCEPTANCE CRITERIA


The acceptance criteria for the overall structure of acceptance for all of the above areas, and the overall
management of issues and risks associated with the cutover process applicable to the SAP HR system
are as follows:

Acceptance Criteria
1. Designated management identified and available for immediate decision making;
2. Signoff on items listed above has been obtained.
3.
Authority

Name

HCE Program
Manager
Portfolio
Program
Manager

First Last
First Last

Signature

Date

Anda mungkin juga menyukai