Scribd Logo
Upload

Welcome to Scribd!

  • 25 views

    TST Document CP ROUND1: Project Scope

    Uploaded by

    Jesús Eduardo Mora Pérez
    This document outlines the scope, timeline, and deliverables for a project to integrate Veeva ODS data into several systems at Novo Nordisk. Key activities include requirements analysis, data modeling, interface development, testing, and training. The proposed timeline is 6 months from November 2016 to April 2017. Deliverables include specifications, design documents, scripts, test plans, and status reports.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    TST Document CP ROUND1: Project Scope

    Uploaded by

    Jesús Eduardo Mora Pérez
    25 views8 pages
    This document outlines the scope, timeline, and deliverables for a project to integrate Veeva ODS data into several systems at Novo Nordisk. Key activities include requirements analysis, data modeling, interface development, testing, and training. The proposed timeline is 6 months from November 2016 to April 2017. Deliverables include specifications, design documents, scripts, test plans, and status reports.

    Original Title

    122822_tst-document-offline-7

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the scope, timeline, and deliverables for a project to integrate Veeva ODS data into several systems at Novo Nordisk. Key activities include requirements analysis, data modeling, interface development, testing, and training. The proposed timeline is 6 months from November 2016 to April 2017. Deliverables include specifications, design documents, scripts, test plans, and status reports.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    25 views8 pages

    TST Document CP ROUND1: Project Scope

    Uploaded by

    Jesús Eduardo Mora Pérez
    This document outlines the scope, timeline, and deliverables for a project to integrate Veeva ODS data into several systems at Novo Nordisk. Key activities include requirements analysis, data modeling, interface development, testing, and training. The proposed timeline is 6 months from November 2016 to April 2017. Deliverables include specifications, design documents, scripts, test plans, and status reports.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 8

    Statement of Work

    PARENT framework

    Vava Integration Project

    SOW #35

    To TEXT

    Novo Master Service Agreement Update with CWS#

    This Statement of Work (“SOW”) is entered into between NO DISK INC., a Delaware
    corporation (“NO DISK”) and

    TST Document CP ROUND1

    ESSAY

    The purpose of this project is to integrate Veeva ODS data feed into direct impact to CDM,
    DW (GreenPlum), DW (FMA) and DW (Orion) systems as well as External/Internal systems
    like Concur, Concur Corrections, AGS, Beghou, SAM and ZS having indirect impact which
    source data from CDM, DW (GreenPlum), DW (Orion) and DW(FMA) in form of Extracts.

    This SoW covers engagement details, in scope, out of scope, assumptions and estimated cost
    for this piece of work.

    TST REDLINE ADDED CP ROUND1

    1.1 Project Scope

    Key In-Scope activities for the Project are:

    1. Requirement Analysis for identified source and target integrations

    2. Data profiling of Vava ODS source data to assist the data model design

    3. Design and Development of all identified backend objects to retrofit existing functionality
    4. Create scheduled jobs identified integration streams

    5. System Integration testing (SIT) and User Acceptance Testing (UAT) Support

    6. Warranty support for 4 weeks

    7. To provide Application Training to end users (2 sessions during the Warranty Support)

    8. TST REDLINE ADDED CP ROUND1

    1.2 Timeline

    The proposed 6 month engagement start date is 01st November 2016 and end date is 30th
    April 2017

     TST REDLINE ADDED CP ROUND1

    123

    1.3 Out of Scope

    1. It is expected that data from source is already cleansed so no data cleansing efforts

    are considered

    2. Test Data creation for SIT and UAT is not in scope; data from live systems would be

    used for SIT and UAT

    3. Automated testing of data loads, user concurrency and load balancing is considered

    as out of scope

    4. TST REDLINE ADDED CP ROUND1

    5. TEST

    6. Real time data processing is considered out of scope


    7. Any front end report modification/validation using Veeva ODS data is not covered in this

    estimation (There will be separate estimation provided for this)

    8. Any integrations not mentioned in the URS shall be considered as out of scope

    9. Performing UAT is out of scope, however, UAT support will be provided

    1.4 General Assumptions

    1. Data feeds & all other interfaces will be in English

    2. Environment will be frozen for any changes during system testing

    3. Trial and error methods (business logic and table structure changes) will not be accepted
    during implementation and changes will be treated as a Change Request and estimation will
    be provided accordingly

    4. NNI proposed test management tool will be used for defect reporting and tracking

    1.5 Dependencies

    1.5.1 General Dependencies

    1. The required environments access will be provided to Cognizant team members


    before start of the project

    2. All infrastructure, database, network access and application licenses should be in


    place before the project starts.

    3. Access to offshore team via VPN/RDC

    4. All measures are assumed to be available in the data source and for those which may
    need to be calculated, the Business Logic and Calculation Formulas need to be
    provided by the SMEs / Business Analysts

    5. Cognizant team will seek Vava implementation partner team’s involvement to


    understand data feeds

    6. Cognizant has access to all existing artifacts, source code, data and documents that
    will help understand the overall requirement
    7. Administrative support to be provided for all the respective technologies during
    project execution
    1.5.2 Data Dependencies

    1. Database connectivity to be provided to the Cognizant team

    2. Database Administrative support will be provided to the team during the project
    execution

    3. Data refresh frequency needs to be provided for each dashboard before design
    phase.

    4. Relationship between the data source system (Flat Files) has to be provided before
    commencement of design.

    5. Requirement specifications to be provided before the commencement of the design

    1.6 Project Execution Methodology

    1.7 RACI Matrix

    1.8 Technology Details

    ☒ option1
    ☐ option2
    ☐ option3
    ☐ option4

    This project contains below technology landscape.

    Informatica PowerCenter

     GreenPlum

     Siperian

     Oracle

     Tidal

    1.9 Communication & Status Reporting

    Cognizant intends to keep Novo Nordisk constantly updated on the status of this engagement

    with up to date and actionable information. Cognizant would work with No Disk to determine
    the necessity, frequency, target audience of various communication plans required for each

    engagement.

    There will be regular status calls and the attendees will include:

     Novo Nordisk’s Project Manager

     Cognizant Project Manager

     Cognizant Technical Lead

     TST REDLINE ADDED CP ROUND1

     TEST

     
    SECTION 2: PROJECT MANAGEMENT, INCL. SUPPLIER REQUIREMENTS AND
    QUALIFICATIONS

    The following personnel have been designated as project managers with regard to the
    services contemplated herein:

    ☒ choice1
    ☐ choice2
    ☐ choice3
    ☐ choice4

    SECTION 3: DELIVERABLES

    1. Source System Interface Specifications

    2. Functional Specifications Document

    3. Data Model updates

    4. High Level Design Document

    5. Detailed Design Document

    6. Data Migration scripts

    7. Detailed Test Case/Test plan (Unit/Integration)

    8. Test Case Scripts

    9. Standard Operating Procedures Manual

    10. Weekly Status Report (including Budgets)

    You might also like