January 16, 2012

Statement of work - M-2

Prepare for the consultation industrial

A. Scope

The purpose of this guide is to help the people in charge of projects or contracts who are responsible for writing the Statement of Work (CCTP) as part of procurement contracts, orders or agreements.

The product to be delivered may be a piece of equipment, a software package, a service or a document, at any stage of its production (design, manufacturing, implementation, validation or utilisation).

Within a contract, the Statement of Work constitutes one of the main elements relating to technical components, and comprises three parts which set out:

  • What is expected of the product to be supplied;
  • The services to be performed by the contract holder;
  • The full complement of expected supplies.

 

This section is based on the CNES Management System document (SMC) "CNES-SMC-P-12-316 Cahier des clauses techniques Particulières "CCTP" Guide d'élaboration et modèle".

B. Fundamentals

1. General rules

A CCTP includes the following elements, presented (or not) in separate documents:

  • The Technical Specification defining the characteristics and performances required for the product ;
  • A summary of the services expected from the holder ;
  • The full complement of the supplies and the associated constraints and/or limits.

 

These three volumes together make up the CCTP.

2. Recommendations and guide

The following is recommended when preparing the work statement:

  • Examine the directives received and the objectives set for the programme ;
  • Examine the general directives and applicable reference bases ;
  • Identify the causes for inevitable expenditures and grade them in order of importance ;
  • Prepare a technical or functional flow chart for the relevant phase ;
  • Identify the organisations or managers to be consulted ;
  • Be sure to write the work statement according to the requirements to be met, not according to methods ;
  • Remember to select, in the list of tasks and/or supplies, those which, in the contract, will generate events entailing an entitlement to payment.

 

The following is recommended when writing the work statement:

  • Be sure to break down the subject into logical elements ;
  • Identify the tasks for which a standardisation or common practice already exists ;
  • Identify the tasks requiring a particularly detailed and precise presentation ;
  • Identify the tasks presenting technical or technological difficulties which could call for specific researches or developments.

 

C. Typical content

1. General

1.1 Description of the service to be performed

1.2 Description of the context

  • Purpose
  • Industrial organisation: Determination of the identity and responsibilities of all participants in a product supplier chain, along with the interfaces among them.

 

1.3 Documentation

  • Applicable documents;
  • Standardisation documents imposed for a project.

 

2. Terminology - Acronyms

(To be completed as needed)

3. Technical specification or technical characteristics

3.1 Technical specification

The Technical Specification groups together the technical characteristics required for the product to be supplied; it specifies the requirements relating to:

  • the operation context and associated constraints ;
  • the performance and efficiency requirements within this context ;
  • the minimum verifications required and the means to obtain them.

 

The Technical Specification must be sufficient for a designer to be able to develop the design of a product that unambiguously meets it. (Refer to E-2).

3.2 Technical characteristics

Document stating the technical requirements relating to the expected service.

4. Description of the tasks to be performed

  • Work breakdown structure (OT) (refer to M-6): this is more particularly based on the product tree.
    It consists in a prioritised representation of the activities and resources required to conduct a project.
  • Work packages: Group of interrelated tasks defined at the lowest level in the OT.
  • Special cases:
    • for software or IT systems:
    • SSI
    • QA
    • maintenance
    • expected performance
    • for services
    • expected skills for each activity
    • service contract
    • work units
    • process
    • result indicators

     

 

5. Specific requirements

Depending on the circumstances, the CCTP might provide for:

  • requirements relating to personnel qualification,
  • requirements relating to the quality management system.

 

6. Implementation schedule

  • General schedule: ordered set of activities and events associated with performance durations.
  • Detailed schedule (by work package).

 

7. List of supplies

The supplies shall be defined by their title, accompanied if need be by a brief description, as well as by the expected delivery date (or the milestone or review date).

  • Equipment.
  • Software: besides the information mentioned above, the scheme governing the associated rights, and in particular the rights granted to CNES, shall be described in details. This will also apply to software that is wholly or partially integrated into the supply, and which was available before the service.
  • Technical documentation (definition, production, inspection, utilisation documentation...).
  • Other (Studies, Reports, Databases, Plans, Know-how, Photos, Films...).
  • The general ownership schemes pertaining to the supplies will be referred to in the deed of commitment.

 

8. Service progress monitoring

  • Progress reports: Frequency, Content;
  • Progress meetings: Frequency - Convening - Agenda - Progress ;
  • Milestone review: Convening - Agenda - Progress - Report.

 

9. Conditions of service acceptance

9.1 Definition of a technical acceptance plan

  • Roles and responsibilities ;
  • Test logic and sequencing ;
  • Return of results ;
  • Success criteria.

 

9.2 Acceptance conditions

  • Condition of the product on delivery (packaging, wrapping, bundling...) ;
  • Delivery conditions: locations and time criteria ;
  • Accompanying documents ;
  • Supply limits (exclusions...).

 

Activities / documentation

Published in: