ProjectName - Documentum
Statement of Work
Version: v1

Project: **Project Name** - Documentum

Statement of Work

Project Sponsor / Aalia Morgan / VendorProject Manager / Ranjay Sodhi
Cost Unit (or CAR) / Date Sign-off Required / 05/22/2008
Business Unit / Specialty / Vendor Engagement Manager / Tania Verma
Author: / Date: / Signature:
Joe Blog / Jack Smith / 05/14/2008
Approval(s):
______
BIM, CompanyName
VP , CompanyName
______
Laurel Dimaggio
General Manager, VendorLimited

This Statement of Work (“SOW”) is entered into on 15-May-2008 by and between CompanyName (“CompanyName ”), with an office at and Vendor Limited (“Vendor” or “Vendor”), with an office at 890 Trivalley st, Mountain view, PA pursuant to the terms of the Affiliate Accession Agreement between CompanyName and Vendor dated January 1, 2015 as amended (the “Agreement”). All capitalized terms used herein, unless otherwise defined, shall have the meaning ascribed to such terms in the Agreement. The terms & condition of the Agreement are incorporated by reference herein .

Document history:

Revision / Date / Author / Comments

Table of Contents

1Project Justification and Description......

1.1Background

1.2Business Objectives and Benefits

1.3General Information

2Technical Solution......

2.1Scope

2.2Project Approach and Recommendation

3Business assumptions......

3.1Key Stakeholders

3.2Prerequisites

3.3Assumptions

4Major risks and sensitivity analysis......

4.1Main Risks

5Milestones and deliverables......

5.1Organization

5.2Execution Schedule

5.3Milestones

5.4Deliverables

5.5Resource Roles and Responsibilities

Vendor Roles and Responsibilities

CompanyName Roles and Responsibilities

5.6Communication Management Approach

5.7Change Management Approach

5.8Main Project Completion Criteria

5.9Specific Warranties & Maintenance

6Commercials......

6.1Charges and payment schedule

6.2Payment Terms & Conditions:

1Project Justification and Description

1.1Background

The core role of the My Company (COMPANY) group in US Medical and Regulatory Affairs is to provide in-depth scientific and medical information to healthcare professionals. This project will aide in providing timely and accurate materials which comply with all legal and regulatory requirements.

COMPANY group has recognized the need to automate the document review, approval and publishing processes. Documentum has been identified as the platform of choice because of its ability to dynamically aggregate business functions and content to shorten time to knowledge.

This SOW considers the necessary end to end development and testing to be undertaken to rollout a **Project Name** s Documentum webtop application.

1.2Business Objectives and Benefits

The key benefits of the Non Promotional Docs Tools application will be:

  • Manage the educational tools (documents) and review process through Document management solution
  • Eliminating manual activities
  • Implement reliable tracking, version control and audit trail features for transparency and quick access to information
  • Provide timely availability of high quality and technically accurate educational tools
  • Ensure alignment with medical strategies and compliance with legal and regulatory requirements

1.3General Information

Project Sponsor: / Ken **
Future System Owner: / Ken **
Project Short Name: / **Project Name** - Documentum
Project Category: / Application Development
Project Type: / Application Development
Validation Required: / No

2Technical Solution

2.1Scope

In Scope
  • The functional requirements of Non Promotional Docs Tool will be limited to the requirements mentioned in “NonPromotionalDocTool_Requirements_v1.0” attached below.Requirement related to SciOps portal integration has not been considered in scope.
  • Publishing approved documents to a shared network folder
  • Requirements gathering for Non Promotional Docs Tool project from CompanyName business.Requirements specifications document would be delivered at the end requirements gathering phase.
  • Design of Non Promotional Docs Tool. Vendor would deliver a design document at the end of design phase.
  • Development of Non Promotional Docs Tool.
  • System testing of Non Promotional Docs Tool. System tested code would be delivered at the end this project phase.
  • One week of UAT support
  • Production deployment support
  • Four weeks of warranty support
  • UAT. This will be executed by Vendor if the UAT SoW is signed. Indicative costs for this effort is presented later in this SoW .

Out of Scope
  • Integration of Non Promotional Docs Tool Documentum application with portal (Plumtree SciOps, etc).
  • Development or building Documentum infrastructure in all environments (Development /QA /Production)
  • Performance tuning and Server management in any of the environments
  • The requirements related to SciOps portal mentioned in requirement document “NonPromotionalDocTool_Requirements_v1.0” will be considered out of scope.
  • Installation and administration of Documentum products in the Development/QA /Production environment.
  • Training documentation (This can be provided at additional cost)
  • Creation of Test data
  • Third-party software issues – any problems arising due to limitations or issues in 3rd-party software (not developed by Vendor) like Operating System, Database.
  • Any costs to procure Database and File system space
  • Any Costs to Procure Weblogic Application Server
  • Any data cleansing – programmatic or in any other form
  • Server sizing, capacity planning, performance analysis and testing
  • Ongoing application or hosting support costs for this year or subsequent years are not included in the estimate and will be addressed under separate contract if required by business.
  • Any other activities not mentioned in the in-scope section

2.2Project Approach and Recommendation

Once Statement Of Work (SOW) prepared by Vendoris approved by CompanyName , following are the project activities taken as part of this project.

  1. Requirements Gathering
  2. Design
  3. Build/Development
  4. Deploy to QA environment and engage Business to get feedback
  5. Make recommended bug fixes.
  6. UAT sign off by CompanyName
  7. Support CompanyName for production deployment/Go Live
  8. 4 weeks ofwarranty support from Offshore
  9. This project will not be executed or tracked through EWS PMO.

3Business assumptions

3.1Key Stakeholders

Ken Jones , Abhay Sharma Nadig , Bie Huimin , Devol Caston

3.2Prerequisites

CompanyName to provide Vendor access to identified resources for Development, QA and Production environments

3.3Assumptions

Assumption / Degree of Criticality
UAT sign off will be provided by CompanyName before production launch. In case the UAT is delayed beyond the stipulated timeframe, the same will be handled as Change Request (CR) and standard change management procedure will be followed.
UAT Sign off will treated as acceptance to move the changes to production if UAT is delayed beyond the stipulated timeframe. / High
CompanyName will provide all required clarification within 3 working days, otherwise the deliverables will be deemed as accepted. / High
Any changes required to be implemented after the sign-off of the requirements will be treated as CR. Standard change management procedure will be followed. / High
Deliverables need to be signed-off within 3 working days. In case sign-off is not obtained it will be deemed as approved.. / High
The Documentum WebTop application will be a standalone application with no integration with SciOps Portal. WebTop will be the user interface for the same. / High
The templates for creating the educational tools will be defined and provided by CompanyName / Medium
CompanyName would provide necessary development, testing and deployment environment as well as any software required for development / High
CompanyName will provide all Documentum product suite licenses required for this Development. This is not included in the proposed cost.
Vendor would provide only standard desktops. Any special hardware / software required for the project will either be provided by CompanyName or be chargeable to CompanyName
Documentum infrastructure will be available and will be supported and maintained by CompanyName during this engagement / High
Link cost is not included in the project cost; existing CompanyName link would be used / High
It is assumed that CompanyName will make available all the necessary SMEs, Business users and relevant IT team during Requirements Analysis and Design phase to help Vendor team in understanding the requirement / High
It is assumed that CompanyName will provide sufficient Test data during Requirement Analysis Phase / Medium

4Major risks and sensitivity analysis

4.1Main Risks

1. Risk
2. Potential effect on project success / Impact
(H/M/L) / Perceived
Probability (H/M/L) / Recommended Risk Response
Delay in SOW approval / H / L / Time line pushback
Changes in the requirement / H / L / Sign off on requirements; Time line and cost revision / approval.
Delay in UAT Sign-off / H / M / Time line pushback/Cost Revision

5Milestones and deliverables

5.1Organization

Organization / Role / Responsibility / Potential Impact if responsibility not fulfilled
Vendor / Project Management, implementation / Application will not be completed
Business / Project oversight, approval / Project Delay
Vendor /
  • Development
  • System Testing
  • UAT Support
/ Application will not be completed timely.

5.2Execution Schedule

The following table shows the project execution schedule:

5.3Milestones

Dates may shift based on project deliverables, risk factors, and client timelines.

Milestone Description / Responsible / Milestone Date
Provide Statement of Work / Vendor / May 16,2015
Sign Statement of Work / Business / May 22, 2015
Development Start Date / Vendor / June 9, 2015
Requirement Understanding Complete / Vendor / June 23, 2015
Design Complete / Vendor / July 7, 2015
Development and Unit testing Complete / Vendor / August 18, 2015
System Testing complete / Vendor / September 5, 20158
UAT Kickoff / Business / September 8, 20158
UAT Complete / Business / September 19, 20158
Fixes and Deployment in Production / Vendor / September26, 2015
Warranty Support completion / Vendor / October 24, 2015

5.4Deliverables

The following is the list of deliverables identified for this SOW along with the responsibilities identified for Vendor and CompanyName .

Phase / Deliverable / Responsibilities
Vendor / CompanyName
(Sign Off Required)
Requirements Analysis
  • Requirement Specification Document
/ Yes / Yes
Design
  • Design Document
  • System Test Scripts
/ Yes
Yes / Yes
System Testing
  • System Tested Code
/ Yes

5.5Resource Roles and Responsibilities

Vendor Roles and Responsibilities

Following table illustrates the responsibilities/activities of the identified Vendor team:

Role / Responsibilities
Project Manager /
  • Accountable for the project execution and the deliverables (Cost, Schedule & Quality)
  • Communication with all the stake holders
  • Status reports & project reviews
  • Project planning & delivery
  • Participation in Business requirements gathering, solution architecture and review activities
  • Change control & Configuration management

Analyst /
  • Analysis of High Level Requjirement provided by business
  • Low level Requirements gathering and Gap Analysis.
  • Preparation of requirements / gap analysis document
Participation in solution architecture and
review activities , testing and deployment
Technical Architect /
  • Analysis of Low level Requirements gathering and Gap Analysis.
  • Architecture review , designing and Preparation of detailed design specifications
  • Participate in the Review of system test scripts and deliverables

Senior Programmers /
  • Create Design Specifications
  • Developing the application
  • Perform unit testing of the system
  • Perform integration testing
  • Prepare test scripts for system testing
  • Participate in the review process

CompanyName Roles and Responsibilities

Role / Responsibilities
CompanyName Project Manager /
  • Single point of contact from CompanyName for entire project related activities
  • Facilitate communication between CompanyName and Vendor
  • Plan and organize infrastructure and software access for Vendor resources
  • Coordinate the timely reviews of Vendor deliverables

CompanyName Business Team /
  • Provide Functional Requirement documents to Vendor and facilitate understanding of the proposed project requirements
  • Work with Vendor team to clarify all queries related to the System
  • Participate in reviews
  • Perform User Acceptance Testing

5.6Communication Management Approach

Vendor will follow the following Communication Management approach for executing this project. One senior Business Analyst will be stationed at CompanyName East Hanover, US site for coordination with CompanyName Business and IT Team at the initial phase of the project.

5.7Change Management Approach

Vendor will follow the following Change Management approach for during this project.

5.8Main Project Completion Criteria

The final software delivery would follow the following acceptance procedure.

  • The final software delivery would be tested using the acceptance test plan provided by CompanyName
  • UAT review comments, attributed to Vendor, will be tracked to closure. CompanyName would provide sign-off/closure report for all such comments.
  • CompanyName would provide an acceptance sign-off for the deliverable. Acceptance can be conditional upon required fixes for nonconformance. This acceptance will be required before production rollover.
  • If acceptance sign-off is not received within one week from closure of UAT or before production roll-over, the delivery will be deemed accepted.

5.9Specific Warranties & Maintenance

After the Application is deployed in Production, Vendor would provide 4 weeks of warranty support for the developed application from Offshore. Vendor would fix the issues/bugs in Production as part of Warranty support. Change in Requirement will be out of scope.

6Commercials

6.1Charges and payment schedule

Vendor proposes to execute the project at a Fixed Cost of XXX.XXX USD (One hundred XXXXXfifty four US Dollars). This does not include cost for Software Licensing, Hosting and Infrastructure charges. Neither does it include any ongoing application or hosting support or maintenance cost for this year or subsequent years.

Table below indicates milestone linked invoicing schedule:

Payment Milestone / Payment Percentage
At the time of signing of Contract / 10
After Approval of Requirements Specification Document / 20
After Approval of design document / 30
After delivery of System Tested Code / 30
Completion of UAT / 10

6.2Payment Terms & Conditions:

  • All rates are in USD
  • Vendor standard work hrs are 8 hrs at Onsite and 8.75 hrs at offshore
  • Payment of invoices is due 30 days from invoice date.
  • Payment details will be provided with the invoice issued once the PO number has been created.
  • CompanyName would provide necessary development, testing and deployment environment as well as any software required for development
  • CompanyName would provide necessary office space, hardware and software for all personnel traveling to onsite for this engagement
  • Vendor would provide only standard desktops with office productivity software
  • Link cost is not included in the cost proposal, existing CompanyName link would be used

CompanyName Vendor Confidential Page: 1 / 14© Kuebiko Global. (