Client Back Office Project Acceptance DocumentBack office Transition

Summary:This document reviews key points of ownership of critical issues associated with back office implementation. Review and acceptance of these points ensures a clear understanding of ownership of key issues.

Acceptance Criterion

Issue#

Responsibility Detail Lead Time Assigned Group

1 Contact List Listing of key contacts for all teams. Upon initiation of project.

All

2 Data Flows Clear documentation of all data flows.

Upon transition to support.

Implementation Team

3 Business Process Review

Breakdown of documented business processes.

During account transition phase.

Implementation Team

4 Unique Business Processes

Review of any unique business processes where application workarounds are used.

Upon development. All

5 Additional Functionality Define any functionality not currently in process but planned to be in process post go live.

During transition phase.

Implementation Team

6 Additional Phases Determine any additional phases planned post go live

ASAP All

7 Environment Management

Will any of the teams be managing additional development / test environments off line, if so how do

ASAP Implementation Team

document.doc 1

we stay in sync.

8 Network Diagram Review and documentation of network architecture.

ASAP All

9 Interface Audit Joint review of interface coding. Upon completion of coding.

Implementation Team

10 Interface Maintenance Accountability for ongoing maintenance of established interfaces.

ASAP Implementation Team

11 Customization review. technical review of all customizations. This ensures ability to support customizations in the live environment.

As soon a customization is developed.

Implementation Team

12 Set Up Documentation Transition of all set up documentation.

During account transition phase.

Implementation Team

13 Support Documentation Transition documentation of setups, customizations, interfaces, and converted data specific to project.

- Process Flows- Setups- Test Scripts- Training Materials- Alerts

10-business days prior to go live.

Implementation Team

14 Connectivity development and maintenance.

While may be involved in high level discussions re: connectivity from Client branch offices or locations to Client corporate offices, will not be accountable for the set up and/or maintenance of the branch to corporate connection.

Immediate Client and

15 Printers Configured Establish connectivity and setup printers.

Typically 3-4 weeks prior.

document.doc 2

16 First Month-End Close Documented close processes and defined support plan for first month-end and quarter-end close.

ASAP Implementation Team

17 Un-reconciled transactions

Understanding of un-reconciled transactions from conversion process if any.

Post-conversion Implementation Team

18 Issue Management Review open issues log and assign ownership of issues.

Just after go live Implementation Team

19 Account hand-off to Customer Advocacy Manager & Support team.

Primary care of account passes to Support and the Customer Advocacy Manager after a transition period starting one to two weeks before go live and typically ending after 1st month-end close. Dependent on ability of teams to close out other transition related issues.

After 1st Month-End Close.

All

20 Support Transition Overview

Onsite presentation of support center processes and CAM role.

Transition phase

21 Post go live escalation process.

Determine how issues will be escalated internally. I.e. Super User process, internal help desk, etc.

ASAP All

document.doc 3