Sony Pictures Entertainment Inc.
Work Order—Oracle Re-Platform/Upgrade Project - I
Work Order
Oracle Re-Platform/Upgrade Project - I
for
Sony Pictures Entertainment Inc.

Confidential Information—For Internal Purposes Only

Page 1

Sony Pictures Entertainment Inc.
Work Order—Oracle Re-Platform/Upgrade Project - I

Table of Contents

1.0Introduction

2.0Purpose

3.0In Scope

4.0Out of Scope

5.0Service Environment

6.0Assumptions

7.0Approach/Deliverables

8.0Additional Deliverables

9.0Project Status Terminology

10.0Project Organization

11.0Time Reporting

12.0Acceptance Criteria

13.0Delivery and Cost Schedule

14.0Work Order Term

15.0Fees

16.0Payment Milestone

17.0Change Order Process

18.0Appendix A

Confidential Information—For Internal Purposes Only

Page 1

Sony Pictures Entertainment Inc.
Work Order—Oracle Re-Platform/Upgrade Project - I

1.0Introduction

This Work Order is issued under, and shall be governed by the terms and conditions of, the Amended and Restated Consultant Services Agreement between Sony Pictures Entertainment Inc. (“Company” or “SPE”) and TATA America International Corporation (“Consultant”, “TCS” or “Vendor”) with an Effective Date of March 29, 2010 (the “Agreement”). Capitalized terms used herein and not otherwise defined herein shall have the meanings assigned to them in the Agreement.

2.0Purpose

This Work Order is for TCS to provide incremental resources to augment the existing SPE resources needed to execute the Oracle Re-Platform/Upgrade project.

3.0In Scope

With the exception of upgrading database versions, each application in scope will be brought over from the Source (Solaris/Linux) platform to the Target (AIX) platform “AS IS”. The functionality and performance in scope to be delivered is “Like for Like” when comparing the Sourceand Target systems.

Applications in Scope: Please see Section 13 (Delivery and Cost Schedule)

Roles Required:

  1. Off-Shore Project Manager
  2. Database Developer
  3. QA Tester

Activities to be performed:

  1. Unit Testing
  2. Database Object Remediation
  3. QA testing
  4. Integration Testing
  5. UAT support
  6. Performance Testing and Comparison
  7. Go Live Support/Turn Over to Operations (KLO team)

4.0Out of Scope

The following activities are considered out of scope:

  1. Application Enhancements
  2. Merging or Migration of Application Code Base
  3. Break/Fix for any application component not currently working in production
  4. Weblogic to JBoss migration activities

5.0Service Environment

Software Stack / Product and Version
Database Server / Oracle 9i, 10g, 11g
Operating System / AIX 5.3, 6.1, 7.1

6.0Assumptions

  1. The SPE SDM will approve baseline scope, schedule, and budget and subsequent changes in conjunction with the SPE BRM (as needed).
  2. The SPE SDM will attend a monthly Steering Committee meeting
  3. The SPE PM and TCS SDM will co-chair a weekly PMO meeting and jointly escalate issues as needed to the SPE SDM.
  4. The TCS SDM will be the On-Shore coordination point for planning and execution.
  5. The TCS SDM will be the escalation point for the TCS PM and TCS App Leads for application issues.
  6. The TCS SDM and SPE PM will be the escalation point for the TCS PM for program level issues.
  7. The TCS PM will be the escalation point for Off-Shore resources
  8. The TCS PM will be the coordination point for Change Requests (CR’s) and will ensure that all CR’s conform to project standards.
  9. The TCS PM will establish a baseline project plan and track changes against the baseline
  10. The TCS PM will establish and maintain an application-specific issue log
  11. The TCS PM will review project deliverables (described in Section 7) prior to submission for quality control purposes
  12. The TCS PM will provide a weekly project status update to the TCS SDM and SPE PM
  13. TCS resources in this SOW do not include KLO resources unless the level of effort is 7 person days or less and are called out by application and role in this SOW at zero cost.
  14. Upon acceptance of an application into production, TCS will raise a Change Request to Decommission the source system using the CR verbiage consistent with project standards
  15. SharePoint is the official project repository for completed deliverables

7.0Approach/Deliverables

The following table describes the overall project approach, deliverables to be produced by TCS. The tasks below describe the execution aspect of the project and are not intended to be all inclusive of TCS responsibilities, for example active planning and management of applications in scope.

Process / # / Deliverable
DEV / 1 / Submit Non-Production Change Request
2 / Pre/Post Upgrade Task List (v1.0)*
3 / Detailed Migration Task List and Timings (v1.0)*
4 / UAT Acceptance Criteria*
QA/STG / 5 / Integration Testing Results (Expected vs. Actual)
6 / Priority 2 and Higher Issues Resolved (as tracked on Application Issue Log)
7 / UAT by End Users with Sign-Off*
8 / Updated Pre/Post Upgrade Task List and Timings (v2.0)*
9 / Updated Detailed Migration Task List (v2.0)*
10 / Results from Performance Benchmark of Source System
11 / Results from Performance Test of Target System
12 / Benchmark Comparison - with user sign off*
PROD / 13 / Confirm Production Cutover Window*
14 / Submit Production Change Request
15 / Finalized Pre/Post Upgrade Task List and Timings (v3.0)*
16 / Finalized Detail Migration Task List (v3.0)*
17 / Finalize Roll Back Criteria and Go/No-Go Decision Points*
18 / Detail Migration Task List Executed*
19 / Acceptance Sign-Off*
20 / Submit Decommission Change Request
* Upload document or email into an application-specific folder in the SharePoint Library under ADM

Details to be discussed in project kickoff meeting to be held the first week of project start.

8.0Additional Deliverables

The TCS PM is responsible for providing the following information each Friday by 5pm Pacific:

Deliverable / Description
Schedule Update / Compare Baseline Schedule to Actual and provide Estimate to Complete by Application
Issue Log Summary / Priority 1 and Priority 2 Issues, resource assigned, and Estimated Completion Date
Applications Status /
  • Applications Migrated into DEV, QA, STG, and PROD this week
  • Applications Planned to Migrate into DEV, QA. STG, and PROD next week

9.0Project Status Terminology

  1. For reporting project status:

Status Indicator / Definition
RED / AT RISK
YELLOW / CAUTION
GREEN / ON TRACK
  1. For prioritizing application issues:

Priority Level / Definition
Priority 1 (P1) / Critical, Cannot Move Forward
Priority 2 (P2) / Urgent, Must be resolved before Go Live
Priority 3 (P3) / Important, Can be resolved post Go Live

10.0Project Organization

Team / Accountable for / Meets / Members
Oversight Team /
  • Approving Production Cut Over Windows
  • Ensuring Sign-Off on UAT
  • Acceptance of Production System
  • Payment Approval
  • Review/Approval of Change Orders
/ As Needed / SPE Project Sponsor
SPE SDM
SPE BRM (as needed)
SPE PM
Steering Committee /
  • Removing Obstacles
  • Resolving Escalated Issues
  • Escalating Issues to the Oversight team
/ Monthly / SPE SDM (as needed)
SPE PM*
SPE App Lead
TCS SDM
PMO /
  • Reaching decisions that enable the project to stay on schedule and in scope
  • Escalating issues which a decision is needed from the steering committee
/ Weekly / SPE PM*
TCS SDM*
TCS PM
Project Team /
  • The day to day management of progress towards project milestones and for overall project success.
/ Daily / TCS PM
TCS App Lead
Off Shore Team
Extended Team /
  • Providing support in order to accomplish specific project tasks per the project plan
/ As Needed / SPE EIS
SPE TCOE
*Meeting Chair

11.0Time Reporting

The Consultant team shall utilize the Company specified time reporting system to file weekly time sheets. Time sheets shall indicate the activities and the time spent on each activity

12.0Acceptance Criteria

The SPE SDM will confirm the acceptance of each migrated application into production or provide a list of open issues to be resolved before acceptance will be confirmed.

If acceptance of a production rollout for any application is not received within 5 business days or a list of open issues to be resolved has not been provided, the rolled out application shall be deemed acceptable.

13.0Deliveryand CostSchedule

The following applications are planned to be delivered based on the tentative delivery schedule below. A detailed project plan will be provided within first week of project start.

14.0Work Order Term

This Work Order shall begin on May 14 2012 andshall terminate on Dec 14, 2012.

15.0Fees

Company will compensate on fixed price basis as per milestone dates and amount below.

Expenses: Prior written approval by the company is required.

Overtime compensation:[N/A].

Other Compensation: [N/A]

Total cost for this engagement is: $37,957.00USD

16.0Payment Milestone

17.0Change Order Process

Material changes to Scope, Schedule, or Budget will trigger the Change Order process.

Request for changes will be processed using the Change Request Form. The project Steering Committee will review all Change Orders. The project Oversight Team will Approve/Reject all Change Orders. Only Approved Change Orders will be implemented. TCS will maintain an up-to-date log of all change requests. The Change control form and register are included in this SOW as Appendix ‘A’.

AGREED AND ACCEPTED ON ______, 2012

TATA AMERICA INTERNATIONALSONY PICTURES

CORPORATION ENTERTAINMENT INC.

BY:BY:

ITS:ITS:

18.0Appendix A

Change Control Form

Project Title: SPE Oracle Re-Platform/Upgrade Project
Requestor: / Date:
Change Description:
Benefits:
Scope Impact:
Budget Impact:
Schedule Impact:
Reviewed By: / Review Date: / Disposition:
Approved By: / Approval Date

Change Control Register

Client : SPE

Project:

Change Request Number / Date Received / Approved/ Accepted/ Rejected/ Deferred / Start Date / End Date / Estimated Effort
(in PM) / Actual Effort
(in PM)

Confidential Information—For Internal Purposes Only

Page 1