~r:ll ~ji - WikiLeaks

~r:ll ~ji S()NY )~~~".':"l(~~)

Statement of Work For

SPIDR-Stellent to SPIDR ll-Alfresco Migration for

Sony Pictures Entertainment Inc

Version 1.0

Submitted to

Sony Pictures Entertainment Inc.

By

ORMC Bangalore Sony India Software Center Pvt Ltd.

Project Code: 5100WEB025133 Statement of Work No - GDC-2313

Aug 14,2012

Confidential Information

This document contains confidential information. The contents of this document may not be transmitted or reproduced for use or distributed without express permission of Sony India

Software Center Pvt Ltd.

of26

CONFIDENTIAL INFORMATION SONY INDIA SOFTWARE CENTERPVT LTD.

Revision History

1.0 July 13, 2012 Final version

2 Aug 14,2012 Anitha Puttanna Changes done after discussion with SPE

2.1 Aug 14, 2012 Barun Kumar Final version

of26

CONFIDENTIAL INFORMATION SONY INDIA SOFTWARE CENTER PVI LTD.

EXHIBIT A WORK ORDER

This Statement of Work (SOW) is issued pursuant to the supplementary agreement dated 19 July 2012, by and between Sony Pictures Entertainment Inc. (the "Company" or "SPE") and Sony India Software Center Pvt Ltd, (the "Consultant" or "ORMC")

This Section is divided into the following sub sections:

I. Project Background and Scope - This section talks about the background information about this engagement, In Scope, Out of Scope and Technical Environments

II. Roles and Responsibilities - Describes Roles and Responsibilities of the over all engagement for ORMC and SPE consultantslManagers.

III. Engagement Model- Describes over all timelines for different phases in the engagement, Transition approach in detail with deliverables and entry and exit criteria, The deliverables associated with each of other phases, Organization Structure and Resource Loading.

IV. Communication and Infrastructure Plan - This section gives mode of communication and channels used for communication between ORMC and SPE project teams

V. Project Schedule - This section represents the high level project schedule

VI. Price!Commercial- Describes the Pricing Model/Rate card for the consultants and additional discounts and investment from ORMC to SPE for this engagement

VII. SPE Manager - This section lists the name ofSPE Manager.

VIII. Escalation Matrix - This section lists the escalations points for ORMC and SPE.

Page 4 of26

CONFIDENTIAL INFORMA nON SONY INDIA SOFTWARE CENTERPVf LTD.

1 PROJECT REQUIREMENTS AND SCOPE

1.1 Requirements

• Sony Pictures Entertainment (SPE) has the Enterprise Content Management Program (ECM) launched in 2002. The program has been successful and being used by all SPE LOB's. In 2009 Stellent as an ECM platform was planned to be retired and move to Alfresco. Towards this SPIDR II (based on Alfresco) was launched to replace SPIDR I (Stellent). SPIDR II is a Flex based front end with Alfresco as the document repository.

• The Stellent repositories store over 9 million documents and users interface with Stellent in one or more of the following ways:

o mySPE portal application: SPE Employee Intranet (BEA WebLogicPortal 10.3)

o mySPEJ portal application: Intranet for Sony Pictures Entertainment Japan (BEA WebLogicPortaI8.1.6)

o SPIDR I web application: Custom in-house document repository (JSP/Java application)

o Backend API with custom in-house LOB applications (i.e. SPIRITWORLD)

,~!m!:73 content types with about 9 million documents need to be migrated to Alfresco. Similarly screens (Flex user interface) for 73 content types are to be developed. The expectation is to complete this in 18 months.

• The high level scope contains o Getting relevant content out ofStellent is in scope for mySPE and mySPEJ.

SPE to decide on the destination for these content and responsible for the subsequent movement of the same. Development ofSPIDR II Flex user interface for approximately 73 SPIDR IIStellent content types

o Migration of approximately 9 million documents from Stellent to Alfresco o Application integrations with SAP, Ariba, GPMS, Kofax, Webscan

• . Internal portal! systems like SPIRTWORLD are currently connected to Stellent through Web Service and in Alfresco the c?mmunication will be through REST services.

• Third party systems like; SAP, Ariba, GPMS, Kofax and Webscan are currently connected to Stellent and post migration the end points need to connect to Alfresco through REST services.

• As part of migration: o Considered a phased approach since the volume of documents is

approximately 9 million o Analyze which document types I LOB's should be migrated in each phase

PageS of26

CONFIDENTIAL INFORMATION SONY INDIA SOFTWARE CENTER PVT LTD.

o Improve the migration process (more automation and scalability) for the large number of documents

o Migration should take into account rollback options

• SPIDR II is a long term solution so look at further improvements in the Flex UI to increase performance and scalability for the large number of document types.

In order to receive early return on investment we would like to implement this solution in multiple phases. Initial phases will target migration of simple document types.

1.2 In Scope The proposed Stellent to Alfresco migration is broken into 5 stages as listed below:

• Migrotlon Design Approach • Architecture • Design Improvements to Performance (FLEX). Migration.lntegr(lfion

"Instanatlon and Configuration "10M integration "Multiple environments setup for Dev> Test, QA, St(lging, frodudion

·Sh<>rtTerm Post MigratronSupport "Knowfedgetronsiifon to tn-e SPE ECM Sfmft teQm members

ARCIDTECTURE & DESIGN SCOPE ' After migration from Stenent to Alfresco the ECM setup would look like as shown below. Only SPIDR II and Alfresco Share would exist in Content Applications and all External systems would be connected to Alfresco through REST.

Page 6 of26


~~

Ii

I ~;

1 . :ij€i~~[~~~l~~~] I [;:~:~~~t;?J i~~_~~~,_~J

,

' .•... ', .. [ .. : •.. ,i ; ...... ' (-:;...==::::~: ,,-_~eposllo: __ : ~F~ Index ! g:"~)foiage'l

--~---t ................................................. ..,. .............................................................. ~ ..... ! .... , •• , ........................................................... • ...... ·.·.·.·.·,,· ... ·.·u.·.· ... · ........ ,v.· ... ·,·.· ........ ·•· ... ·.··· ............... -......................................................... "/, ......... , ................................ ,._ ......................... ~ As Flex UI has grown in size, we need to look at ways to optimize the Flex application (by modularizing, architectural changes or improvements).

INFRASTRUCTURE SCOPE . The content migration from SPIDR I to SPIDR II is planned to be on Alfresco 4.x Analysis needs to be carried out to size the infrastructure, support in the set up of Alfresco and configuration of Alfresco environments. There are other products and tools that need to be used like Lucene(for search), antivirus, encryption. These need to be also set up and configured with. Alfresco. IDM integration needs to be configured and supported.

Estimated 4 to 5 new Alfresco content repository servers to be setup in each environment: Development, QA, Staging and Production to support a minimum of 9 million documents. Each environment will have at least 2 clustered Alfresco server nodes with the exception of the Development environment

Page 7 of 26


BUILD AND DEVELOPMENT SCOPE SPIDR II needs to be enhanced to provide all the functionality currently supported by SPIDR 1. . Enhance the Flex VI for perfonnance and scalability and support the new migrated content types. Application integration (webscript API) support needs to be provided for the LOB applications as well as applications like Kofax, Ariba, SAP.

CONTENT MIGRATION SCOPE Stellent to Alfresco migration of73 (approx 9 million documents) wi11 be done using Talend (current solution) or with refinements. There is a possibility of using other tools to increase speed and automation of migration. The prioritization of migration areas would be decided at the initiation of the project.

SUPPORT AND TRAINING SCOPE ORMC to provide 2 weeks of Post Go-Live (Hypercare) support per phase. Subsequently the knowledge will be transferred to the current ECM support team.

PROJECT MANAGEMENT

Refer section 1.10 for Project Management Responsibilities

Following Project Management documents will be prepared and used for this project

Page 8 of26


• Project Initiation Document • Project Management Plan • Change Management Plan • Stakeholder Communication Plan • Migration / Data conversion Strategy

The above documents will be prepared and used in consultation and agreement with SPE.

1.3 Out of Scope Activities Following are the activities identified as out of scope as per the current project requirement: a. This SOW is based on RFP document (SPE ECM Stellent-Alfresco Migration RFP

for Professional Services.docx) shared with us. Any requirements not contained in the said document are not in scope.

b. User Interface design is not considered in scope and would be received from SPE during the initiation phase. Usability testing for the same is to be performed by SPE. The Wire frames are assumed to be provided as per the project plan prepared at the beginning of the project in agreement with SPE and any delay may impact the schedules ofthe project

c. User Manuals or Training Manuals are not in scope d. Performance Testing is not in scope. e. Any development/fixes that are required in the LOB applications that need to

interface with Alfresco system. ORMC would provide interfaces/services and some samples for integration.

f. Internationalization of SPIDR II (except for Content Type in SPEJ Contracts in Japanese)

g. Upgrade of Alfresco3.x to Alfresco 4.x.

1.4 Skill Requirements

• One (1) Project Manager • One (1) Business Analyst • One (1) Solution Architect • One (1) Alfresco Architect • One (1) Flex Lead • One (l) Migration Lead • One (1 ) Test Lead • Two (2) Flex Developers • Eight (6) Migration Team Members • Three (3) Test Members

Below chart depicts the indicative resource loading plan

Page 9 of26


1. 5 Term of the Engagement

• ORMC plans to complete the assignment in an elapsed duration of Eighteen months or until earlier termination, whichever comes first.

• ORMC will utilize its offshore capability along with some onsite travel to execute this engagement.

• ORMC proposes a peak team of Eighteen resources for the execution of the project.

1. 6 Terms and Conditions

• In good faith ORMC will try best to fulfill all resource requirements in about 2 to 4 working weeks from the date affinal confirmation.

• Scope and Requirements o Current estimate is based on RFP document and information received

from the customer. Any changes in requirements would impact effort and cost estimate which can be arrived with mutual consent of SPE and ORMC

• Change Management o Any changes after finalizing the basic design will be tracked and impact

will be analyzed before incorporating them in the scope. Any impact on additional cost & schedule will be discussed with SPE.

• Preparation of user manual is not included in the scope. • Service Pricing

o In case there is no variance in terms of requirements mentioned in RFP, price estimation for detailed design and subsequent phases as mentioned in RFP will be within +1- 10% of the price mentioned. In case of any change in the requirements beyond RFP or any additional requirement not contained in the RFP, ORMC will re-estimate the manpower and pricing estimations in consent with the Customer.

o Go live support is included in the manpower and price estimation. Deployment will be carried out by the SPE Web Deployment Group and ORMC would support the deployment activity. VAT will be performed by SPE. ORMC Bangalore will only provide necessary support to fix any defects reported during this period

o Ongoing Production Support & Maintenance is not included in manpower and price estimation.

Page 10 of26


o Place of work will be SPE office in USA (Culver City)and Bangalore. In case if an Engineer has to travel to any other place in relation to the project, such additional expenses incurred on these travels would be charged at actual.

o Onsite expenses included (as mentioned in section 5.2). However, in case SPE requires any offshore member to travel and work at onsite in addition to travel mentioned in section 5.2, all such onsite expenses (including but not limited to Air fare, per diem allowance, accommodation, visa and local conveyance) will be charged at actual.

o Prices are exclusive of any applicable tax, including but not limited to withholding tax, any value added tax, consumption tax, goods and service tax, Corporate Income tax and all export charges and similar charges levied on the Customer in connection with the Services and such tax andlor charges shall be borne by the customer.

o Notwithstanding anything contained in this SOW, in case the contract is terminated prematurely anytime before the scheduled timelines, SPE and ORMC will mutually agree on recalculated total efforts consumed till the period of termination and SPE agrees to make the payment to ORMC accordingly

o All necessary licenses for development environment will be provided by SPE

o SPE will be responsible for integration with mySPE, mySPHE, mySPT, SPIRIRTWORLD etc,

o During hypercare, support for fixing defects is covered for 2 weeks after System Integration Testing sign-off.

• Payment Conditions o 45 days from the date of receipt ofInvoice

** Please refer appendix for additional terms and conditions

1. 7 Assumptions ORMC has considered following assumptions. Any variations in these assumptions may have a direct impact on the effort, cost, and the agreed upon scope, and hence may be handled through the change control process. • SPE is currently working on the priorities of the 9million documents to be migrated.

This prioritization will help to plan the phases and needs to be completed at the initiation ofthe project.

• Knowledge Transfer from SPIDR II application team will be provided as per agreed project plan.

• High level functional requirements are already captured and ready in document format. However, ORMC will detail out these functional requirements based on further discussions and inputs from SPE during requirements analysis phase. Any change in the requirements from the Detailed Design stage onwards would undergo a Change Management Review Process.

Page 11 of26


• Testing of content migration and validation will be based on a sampling basis. The migration logging framework will capture counts of migration (source count, migrated count success/unsuccessful) to aid in the validation process.

• All deliverables will be submitted in electronic fonn - reports or documents created during the engagement will be created using Adobe PDF andlor MS Word. During the Analyze Requirements & Plan Stage, the other fonnat of documents to be used can be concluded.

• SPE will provide necessary software's and licenses for the execution of the project. • It is assumed that documents are not stored as BLOB/CLOB in the database. • The proposed implementation shall cover the following offices and locations on an

onsite - offshore model.

• Key Business / IT users, Process Owners and Stakeholders from various businesses should be made available at the project site as per the project deployment plan. The deployment plan will be detailed during the project preparation phase.

• English will be the business language of this project and all associated activities • SPE will provide ORMC Bangalore's onsite"staffwith appropriate facilities necessary

(work space, SPE network, Telephone, Access, Software Tools) to complete the defined scope of work in support of the project timeframes. Facilities include:

• Each environment (e.g., development, system test, integration test, VAT, production) is assumed to be the responsibility of SPE to acquire and establish prior to start of the project. Versions of the operating systems, software / application updates and database will be consistent with the requirements of any corresponding software products.

• SPE must review project deliverables and comments must be provided to ORMC Bangalore as per the table below (SPE business days), to maintain the proposedl expected schedule. Delays may impact deliverables.

Operational Queries 1 business day Tactical Queries 1 business day Managerial Queries 3 business days

• SPE has responsibility for developing the User Acceptance Test Plan and scripts, and conducting User Acceptance Tests. ORMC Bangalore will support the ''User Acceptance Test" effort. SPE will be responsible for providing ORMC with all the required information to create scenarios and system test cases

• A milestone is considered to be complete when SPE has signed off all deliverables for that milestone. If signoff is not received within 3 SPE business days of the date the

Page 12 of26

CONFIDENTIAL INFORMA nON SONY INDIA SOFTWARE CENTER PVT LTD.

deliverables have been presented, then ORMC Bangalore will consider the deliverable to be accepted.

• Standard work duration is assumed to be 8 hours per day, 5 business days per week • Access to systems would be given as per the predefmed project plan

1.8 Technical Environment Specification

Hardware and Software Environment The development will be carried out on Windows machine. The integration and final testing will be carried out on development boxes provided by SPE, which will have a similar configuration as that of production. The deployment environment is based on current SPE standard and is tabulated below:

JBoss Platfonn 5 or above Oracle IOgor above Flex Flex 4 Browser compatibility IE 7.0, Firefox 3.0

The following development software/tools/IDEs are planned to be used:

Version Control Document Storage and sharing Collaboration and Communication

IDE

Problem logging and tracking

CONFIDENTIAL INFORMATION

SVN SharePoint Microsoft Live Meeting, oes, Email Eclipse, TOADIPLSQL Developer, Flex builder Quality Center

Page 13 of26

SONY INDIA SOFTWARE CENTER PVT LTD.

ROLES & RESPONSIBILITIES

1. 9 General Roles and Responsibilities

ORMC has considered the following stage wise deliverables. "Primary" - Owns the activity and is responsible for the monitoring and completion of the activity "Secondary" - Supports the Primary by providing inputs as necessary for smooth execution ofthe activity

Analysis Project Plan Secondary Primary (SPE will help to sign off

User Requirements Primary Secondary Specification (URS) (SPE will help to

provide requirements & off

VI Wireframes Primary Secondary (SPE will provide VI

Content Type Primary Secondary Prioritization __

Design System Secondary Primary Detailed Design Architecture Design (SPE will review and

approve said

Basic Concept Secondary Primary Design (SPE will review and

approve said

Functional Secondary Primary Specifications (SPE will review and

approve said do

VAT Scripts/ Test , Primary Secondary Cases Technical Secondary Primary Specification (SPE will review said

Vnit Test Plan Secondary Primary (SPE will review said

Migrate & test Code Secondary Primary

Page 14 of26


Migration Secondary Primary Rehearsals (SPE will review said

documents) Test Plan Secondary Primary Defect fixes - Primary_ System Integration Secondary Primary Testing (SPE to provide

integration details with other apps like mySPE, mySPHE etc)

V ser Acceptance Primary Secondary Testing (VAT) (ORMCwill

support UAT) Deploy Execute Migration Secondary Primary

(SPE to provide integration details with other apps like mySPE, mySPHE etc)

Support Post Go Secondary Primary Live

Transition Support Post Go Secondary Primary Live Transition to Secondary Primary Support Team

Project As mentioned under Secondary Primary Management Section 1.2 Activities

1.10 ORMC Team Roles and Reftponsibilities

The below table describes in detail the roles and responsibilities of the ORMC Team. Though this table describes the general roles and responsibilities as a direction for the consultant the same can be changed based on the needs of the projects and will be discussed and mutually agreed between ORMC and SPE management.

ORMC Program Manager


• Overall in charge of offshore and onsite delivery and success of project and monitor program progress and take corrective action

• Communication with stakeholders • Escalation of issues and their resolution • Monitor adherence to Quality process

Page 15 of26


Test Team • Responsible for Independent testing and Quality control of functions developed

• Preparation of System Integration Test (SIT) Scenarios and SIT cases

• Execution of test cases and report test results to Team Lead • Content Migration validation (by sampling)

Quality Assurance • Quality Plarming • Conduct Training to team members on prescribed quality

processes • Carry out Audits • Participate in Project review meetings • Facilitate Metrics collection andpIocess imj)1'ovement activities

1.11 SPE Team Roles and Responsibilities

The below table in detail describes the roles and responsibilities of the SPE Team in Steady State based on our current understanding. Though this table describes the general roles and responsibilities as a direction for the team members the same can be changed based on the needs of the projects and will be discussed and mutually agreed between ORMC and SPE management.

SPE Project Manager

SPESME (BA)

SPE Technical Lead

CONFIDENTIAL INFORMA nON

• Approve the work to be perfoffi1ed • Act as a single point of contact throughout the execution

of the project • Oversee the project • Sign off change requests and deliverables • Coordinate communication between SPE teams and

internal departments • Report project status to the SPE Management • Work closely with ORMC Project Manager to drive the

project and resolve any issues • Participate in project review sessions • Review deliverables • Attend meetings with ORMC team and participate in

discussions • Review completeness and correctness of the deliverables • Explain new enhancements requirements to ORMC team • Prioritize content types to be migrated in consultation

with LOB's • Provide domain and technical information about the

application and related sub-system requirements • Provide technical leadership and development standards • Participate in design sessions • Sign off design document

Page 17 of26


• Help with scope definition • Environment set-u

2 ENGAGEMENT MODEL

The project is planned to be divided into following stages with accepted deliverables in each phase. Since the project has 6 major phases, some of the stages will overlap phases.

Page 18 of26


2.1 Organization Structure

Organization structure and communication structure is critical for success of this engagement.

Project Manager and Team Lead will be point contact for all communication and will report to SPE's Project Manager.

3 COMMUNICATION AND INFRASTRUCTURE PLAN

• Primary channel of communication would be over email, phone, meetings between SPE and ORMC team.

• Existing Site-to-Site VPN network connection between SPE and ORMC facility in Bangalore, India will be used for working on this engagement.

• ORMC team will send weekly status report to SPE project management team tracking overall status of engagement.

• Weekly status meetings will be held and minutes of meeting (MoM) will be captured and circulated to the entire project team. The MoM will also capture all the action items and the SPE Project Manager will be responsible for tracking it to closure.

• Offshore team will communicate with the Onsite Technical Lead for issues, clarifications (if any).

ORMC Project Manager would be the window to SPE on all project related matters like proposal, SLA, resource requirement. In case of any communication delays or issues, the following issue and escalation management process will be adopted.

Page 19 of26

CONFIDENTIAL INFORMA nON SONY INDIA SOFTWARE CENfER PVf LTD.

3.1 Issue and Escalation Management

Any project related issues are logged into Issue log. These issues will be classified in tenus of criticality and discussed internally or with SPE to identifY the time frame to resolve, person responsible for addressing this. Any delays in closure of the issue need to be escalated to next level. Below tables defines the criteria and escalation route.

Project Level Escalations: For issues at the Project Level, below escalation hierarchy is to be followed. These are the issues related to quality or delivery or project issues.

SPE Managers -7 ORMC Bangalore Project Manager -7 ORMC Bangalore Senior Management ORMC Bangalore Project Manager -7 Respective SPE Managers

ORMC Project manager to carry out the root cause analysis, where ever required, and the action plan has to be shared with SPE team.

3.2 Project Progress Reporting

Project progress reporting is done against the established plans and procedures. Progress reports to be prepared in the agreed template by the project leads/ managers and shall be sent to SPE on a weekly basis. The brief description of areas that would be covered in progress reports shall be as given under

• Project SQERT (Scope, Quality, Effort, Risk and Time) health indicators • Open action items from previous meeting/s (Minutes of Meeting) • Planned Vs Actual activities carried-out during the reporting period • Planned activities for the next reporting period • In-Process Prediction status with respect to effort • Milestone status (deliverables completion, sign-off etc) • Change Management Status (Count of Change Request, accepted by Change Control

Board, completed) • Issues Resolution and Risk monitoring • Escalation, if any • Status on No of review defects, No of testing defects (SIT), No ofDAT defect etc • Report on non-Engineering activities like meetings, CAR, Training, internal audits etc • During the initiation phase, teams would agree upon metrics that depicts the project

health which would be tracked and monitored thorough out the project.

Page 20 of 26


IJpdot<?s manager general project work! StCltu~ of

Working sessk-.ns

AH8quired Internet Technical O('S Ie-ad! Prc.ject mornings Telecom/Erna Menger

Project

Page 21 of26


4 PROJECT SCHEDULE AND RESOURCE LOADING

4.1 High Level Work Plan

Month 2 3 4 5 6 7 8 , 10 11 12 13 14 15 16 17 18 19

g:!~I:d wt:m mK~;H fHfJ@E !l:sil[t ~:;E~E!] rnr~Jg~ (Migration TJft~( clure PI, UI

Planning)

Constructi on& Migration

Tesflng& UAT

Deployme nf

Post Deployme nt/Tronstiti on

4.2 Resource Loading

2() .: ................................................................................................................................................................................................................... .

..............................

........................

2 ~···I······I·····I·····I·······I·······I·····I·····I······1······1·····1·····1······1······1····1·····-11::~·····I .. ·· .. ;~;::·············· o :.- ~ - ,.: ..... . ,":::!...:- -~.,:.-= .. : ..... ::: ,'- .:. .~ .. :<... .~ • ., ..... => •. ' ....• • .....• • ":.. . .. :'.. ..-.... . ........... ,' ••• __ ...... ; ............ :

1\11 M2 M3 1>.14 ,,15 M6 M7 MS M9 Min 1.111 Mil M13 Mil MiS MiG M17 MIS MI,)

Month

Page 22 of26


5 PRICE/COMMERCIAL

The base fixed price cost ofthis project is US $ 1,152,774.00

We have considered 10 MM ofOnsite expenses. In case ORMC consultants are required to undertake additional travel (in addition to that mentioned in Section 5.2), such additional travel expenses (inclusive of hotel, air fare, per diem, insurance, visa, local conveyance and other misc expenses) will be charged to SPE on actual basis.

Payment Schedule:

Month 1 59,668

Month 2 59,668 Month 3 59,668

Month 4 59,668 Month 5 59,668

Month 6 59,668

Month 7

Month 8

Month 9 59,668

Month 10 59,668

Month 11 59,668

Month 12 59,668

Month 13 59,668

Month 14 59,668

Month 15 59,668

Month 16 59,668

Month 17 59,668

Month 18 59,668

Total 1,074,024

Travel Cost 78,750

Total Cost 1,152,774

Page 23 of26


6 SPE PROJECT TEAM

Project Manager (Director): Nick Ramani Project Sponsors: Barbara Cross and Jason Soaltro Program Directors: Barbara Cross and Haaleh Morshedizadeh

7 ESCALATION MATRIX

By:

The escalation of issues from SPE and ORMC will be based on the following escalation levels:

Ravikumar Krishnamoorthy

Ramnath Thippasandra

Anitha Puttanna

• Any issue that remains unresolved beyond 15 business days

• Any issue that remains unresolved beyond 10 business days

• Resource Issues • Engagement Issues • Billing/Overtime Issues • Contractual matters • Performance issues

[email protected] .com +91 9980122116 (Cell)

ramnath.tb,ipPM§!1dra@@.sQm:..~om +91- 9901988133 (Cell)

[email protected] +91- 9845287416 (Cell)

The escalation of issues from ORMC will be based on the following escalation levels:

Kunal Mittal High. Dependencies (310) 562-5050 (Work)

• Delays in response Pankaj Mishra High • Compliance to tenus

and conditions • Performance on service

delivery and resources

ACCEPTED tbis 1st day of August 2012:

(310) 244-2782 (Work)

Sony Pictures Entertainment Inc.

----~----------_1~--

Name:

By: -=~~---.-:~_--=::::::::::~

Name: C:;?k~~V\ A .L .. \ 'oy---------------------Title: ______________ _ Title: f\}{> -4-«0

Date: ---------------- Date: ~ 14 \ ( 2--Page 24 of26


8 APPENDIX:

SUMMARY TERMS AND CONDITIONS:

Scope of work

1 to be Approximately 9 Million

2 Content types 73

3 No. of report formats l4 (Report Parser)

4 Phase wise to be distributed as per below

Solution Approach

Data Migration

2 IT UI development

3 Application Integration

4 Interface / wireframe

Testing

1 Testing of content Migration

2 UAT support

3 Performance testing

Lead Time & Duration

1 Duration of detail requirements I release

2 Duration ofUAT / release

3 Post go live support / release

4 KT duration I release


Talend based ETL

Template based and Modular Flex development

Scripts only

Current VI design

On sampling Basis. Around 2% of documents. The documents to be tested will be mutually agreed between ORMC and SPE ORMC will only support VAT i.e. fix bugs that arises out ofUAT. SPE is responsible tor creating DAT test scenarios &

VAT Performance testing to be conducted by the TCS team. ORMC will provide necessary

on

2 weeks/phase or mutually agreed upon time which does not affect cost 2 weeks/phase or mutually agreed upon time which does not affect cost 2 weeks/phase or mutually agreed upon time which does not affect cost 3 business days spread over 1 weeki phase

Page2S of26

SONY INDIA SOFTWARE CENfERPVT LTD.

5 Resolving of clarifications I queries 3 SPEI ORMC business days related to requirements I technical areas

6 Resolving of issues raised to Alfresco I 3rd Party by SPE

3 business days

7 Resolving ofInfrastructure issues 3 business days bySPE

8 Project kickofflead time 2 to 4 weeks

9 Project plan preparation by ORMC Within 1 month (from start of project) and confirming the same by SPE

10 On-site duration 10 MM spread over 18 months

11 Prioritization of content types Beginning of the project

Other Expectations from SPE

1 ~ecessarylicenses SPE to provide

2 VPN tokens, any connectivity issues SPE to provide VP~ tokens and resolve connectivity issues

3 Provide minimum prerequisites as SPE to provide the details as per agreed per the agreed project plan timelines in Project plan (finalized after 1

month of project kick off) 4 Infrastructure SPE to procure and make them available at

readiness( development, QA, the beginning of project. production servers) Not in Scope

1 End user training SPE to do end user training

2 Upgrade of Alfresco 3.x to 4.x Not considered

3 Use Manuals I Training Manuals UserManualsl Training Manuals not in scope. Support Manuals is in scope

4 Performance Testing Performance testing to be conducted by the TCS team. ORMC will provide necessary support on request

Page 26 of26


~r:ll ~ji - WikiLeaks

Documents

Transcript of ~r:ll ~ji - WikiLeaks