23
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006 Page : 1 a f STATEMENT OF WORK ARTES Elements 3 “User Terminals (USER SEGMENT)" Page 1
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 1 a
f
STATEMENT OF WORK
ARTES Elements 3
“User Terminals (USER SEGMENT)"
Page 1
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 2 a
f
TABLE OF CONTENTS 1 INTRODUCTION ..........................................................................................................3 2 OBJECTIVES.................................................................................................................3 3 SCOPE OF WORK ........................................................................................................3 4 CONTRACTUAL MILESTONES AND REVIEW MEETINGS..............................4
4.1 1st Milestone: Kick-Off Meeting (KO) ...............................................................4 4.2 2nd Milestone: Baseline Design Review (BDR) ..................................................4 4.3 3rd Milestone: Critical Design Review (CDR) ...................................................4 4.4 4th Milestone: Final Review (FR)........................................................................4
5 APPLICABLE DOCUMENTS TO BE DELIVERED................................................5 5.1 Requirements Specification Document (RSD) ..................................................5 5.2 Strategic Plan (SP) ...............................................................................................5 5.3 Build Standard (BS).............................................................................................6 5.4 Design and Development Plan (DDP) ................................................................7 5.5 End-to-End Validation Document (EVD)..........................................................7 5.6 Design Justification File (DJF) ...........................................................................7
6 LIST OF ITEMS TO BE PRODUCED AND/OR DELIVERED ..............................8 6.1 Deliverable Hardware .........................................................................................8 6.2 Deliverable Software and Content .....................................................................8 6.3 Deliverable Documentation.................................................................................9 6.4 Final Report (FREP)............................................................................................9 6.5 Final Review Data Pack (FDP) .........................................................................10 6.6 Document Confidentiality .................................................................................10
7 MANAGEMENT..........................................................................................................11 7.1 Project Manager ................................................................................................11 7.2 Experts ................................................................................................................11 7.3 Reporting – Minutes of Meetings .....................................................................11 7.4 Reporting – Document Management ...............................................................11 7.5 Electronic Documentation.................................................................................12 7.6 Project Web Page...............................................................................................12 7.7 Distributed Project Collaboration Tool – eProject.........................................12 7.8 Reporting – Monthly Progress Reports ...........................................................13
8 REPORTING AFTER COMPLETION OF THE CONTRACT.............................13 9 ESA TECHNICAL ASSETS .......................................................................................14
ATTACHMENT I: Word Template for Project Web Page...............................................15
ATTACHMENT II: Monthly Progress Report (MPR)......................................................18
ATTACHMENT III: Contract Outcome Data ...................................................................21
Page 2
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 3 a
f 1 INTRODUCTION Proposals in response to this Invitation to Tender can address one of two areas:
• “Integrated Applications” – the development and pilot utilisation of new satellite-based applications;
• “User Terminals” – the development and end-to-end validation of new satellite user terminals.
This Statement of Work applies to User Terminals; a separate document addresses Integrated Applications. For the preparation of your proposal, you are strongly recommended to particularly consider the Letter of Invitation and the Special Conditions of Tender. Offers which do not provide the information required, be it technical or other, may be rated unacceptable. 2 OBJECTIVES User Segment contracts cover the development, implementation and validation of a satcom User Terminal. The contractor shall under this contract develop or enhance user terminals, conceived here as elements of an end-to-end satcom system providing access to applications and services. As such, the user terminals developed as part of the project shall be tested and validated before the conclusion of the contractual activities in the target end-to-end satcom system. The proposed development shall directly enable a satellite communications business opportunity to be exploited and demonstrate the strategic role of satellite communications in the initiative. 3 SCOPE OF WORK For the realisation of the proposed initiative the contractor shall develop or enhance the user terminals within the objectives set out in Section 2. The specific area in terms of type of user terminals, the targeted satcom system, the extent of development and/or integration of hardware and software shall be defined by the tenderer in his proposal. The activities shall include the design, development, manufacturing, testing and validation of the user terminals. The user terminals shall meet the Technical Requirements described in the Applicable Documents defined in Section 5 below.
Page 3
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 4 a
f 4 CONTRACTUAL MILESTONES AND REVIEW MEETINGS The following four Review Meetings represent the sequence of milestone events to be taken into account in establishing the logical organisation of the work. Each of these review meetings will be attended by representatives of the project team and by ESA’s Technical Officer, and they will correspond to contractual milestones. The documentation supporting each Milestone Review Meeting shall be delivered to ESA at least five working days before the meeting takes place. Additionally, ESA reserves the right to witness validation activities and if necessary specific progress meetings may be called for by ESA. 4.1 1st Milestone: Kick-Off Meeting (KO) The purpose of the Kick-Off Meeting (KO) is to clarify any outstanding issues identified by ESA in the proposal, to agree on the project planning and to negotiate the contract. 4.2 2nd Milestone: Baseline Design Review (BDR) Between the KO and the Baseline Design Review (BDR), which should normally cover a period of 4-6 weeks), the contractor shall review and fine-tune his technical specifications. The purpose of the BDR is to approve the final specification. The finalised specification will represent the binding reference for the rest of the project and any deviations require a formal modification to the contract through a Contract Change Notice. The successful completion of the BDR will mark the beginning of the development and design phase. 4.3 3rd Milestone: Critical Design Review (CDR) At the end of the design phase and prior to the beginning of the manufacturing of the prototype of the product, the Critical Design Review (CDR) will be held to present and demonstrate the adequacy of the design and the readiness to proceed with the implementation and subsequent testing. Successful completion of CDR is conditional to proceed with the implementation phase.
4.4 4th Milestone: Final Review (FR) The main purpose of this Final Review (FR) is to accept the developed user terminals through the review of the acceptance test (terminal level) and validation in the end-to-end target system environment. The contractor shall also document the efforts undertaken to commercialise the product and shall describe his future strategies in the finalised version of the Strategic Plan.
Page 4
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 5 a
f 5 APPLICABLE DOCUMENTS TO BE DELIVERED The documents described in this section are part of the contractual deliverables, and an initial version of these documents shall be provided with the proposal. This initial version shall provide a first iteration of the work and not just list the activities that will be performed in the framework of the project. The documents shall constitute a sufficiently clear and self-contained baseline description of the scope of the work. To allow a formal traceability of the different requirements contained in these documents, the Contractor shall associate to each requirement a unique identifier using a suitable methodology. Such methodology shall foresee a suitable set of acronyms (e.g. RS for Requirements Specification, SP for Strategic Plan, BS for Build Standard, DP for Design and Development Plan, VP for End-to-end Validation Plan) to facilitate traceability. The consecutive releases of these documents are the main deliverable documents to be approved by the Agency at the contractual milestone review meetings detailed in Section 4. 5.1 Requirements Specification Document (RSD)
The Requirements Specification Document (RSD) shall identify the system architecture and services for which the user terminals are developed. It shall include system requirements such as air interfaces, performance specifications and any other system analysis relevant for the inclusion of the user terminals into the end-to-end system. Further the RSD shall present and elaborate issues related to the user requirements and their implications in the technical domain, e.g. choice of supported applications, operating system, user interfaces, installation and operational constraints. The RSD shall also detail the full set of the technical requirements of the user terminals to be developed, including as a minimum the functional, performance and interface specifications and for which environmental conditions the requirements are valid. The requirements shall be provided in a form which allows easy verification. The RSD shall be updated and will be reviewed and approved by the Agency at the Baseline Design Review (BDR). The user terminals developed under this activity shall comply with the version of RSD approved by ESA at the BDR. 5.2 Strategic Plan (SP)
The Strategic Plan (SP) is intended to analyse the strategic context of the proposed activity and to eventually demonstrate that the initiative is conceived to lead to an operational exploitation within the context of user terminals for satellite communication systems. Consequently the Strategic Plan shall include:
• Role of this development within the overall system;
Page 5
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 6 a
f • Market analysis identifying the potential commercial opportunities for the product in
the target system; • Assessment of the market positioning through a SWOT (Strengths, Weaknesses,
Opportunities and Threats) analysis of the proposed product and potential competitors, including identification of competitive products, pricing in comparison with competition, sales and profit estimates, short and long term investment planning;
• Assumptions taken to define cost structure, price policy and other elements used in the financial statement
• Identification of the cost structure (investment costs and operational costs) incurred by the Contractor for the user terminal set up, operation and commercial exploitation;
• Formulation of a pricing strategy for the proposed product; • Elaboration of a marketing strategy, clearly identifying the role of the parties forming
the contractual team, and which concrete activities will be carried out during the market development phase;
• Identification of the financial planning through financial statements (e.g. profit and loss account, cash flow) and indicators (e.g. Internal Rate of Return, Net Present Value) with associated sensitivity and/or what-if analysis where applicable. The financial planning shall ultimately prove that the proposed product will become profitable through the ESA contribution;
• Agreements with system manufacturers, and/or system operators, and/or service providers for end-to-end user terminals validation;
• Technical and financial risk assessment; • Identification of co-funding source(s) for the development activities • Description of the planned product industrialisation and commercialisation at the end
of the proposed activities with ESA, including funding The SP shall provide justification for the assumptions. The SP shall also provide a formal set of strategic objectives (specific, measurable and relevant for the proposed initiative) to be achieved by the end of the ESA contract. These objectives shall focus on tangible commercial results (e.g. first sales contracts, commercial agreements, finalisation of strategic alliances, etc.). The status of achievement of such Strategic Objectives shall be regularly reviewed at each release of the SP. Any changes on these Strategic Objectives shall be formally agreed with ESA. 5.3 Build Standard (BS)
The Build Standard (BS) document shall describe in a comprehensive form the standards according to which any hardware unit will be built. Whenever the user terminals are developed using a pre-industrial configuration, the tenderer shall present in his proposal the migration policy he intends to adopt to achieve a fully commercial user terminals product that will eventually meet the user requirements, the technical specifications and its target price. Software developments shall be performed in compliance with the software standard “Software
Page 6
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 7 a
f Engineering Guidelines for the Telecom Applications Projects” published as part of this ITT. 5.4 Design and Development Plan (DDP) The Design and Development Plan (DDP) shall, in a concise and conceptual manner, illustrate the logical execution of the proposed activities from contract award to final review. It shall define and include decision points on which the course of the development will depend. The plan should be presented in form of a flow chart. 5.5 End-to-End Validation Document (EVD) The End-to-End Validation Document (EVD) shall be dedicated to prepare, plan, execute and report all the activities necessary to demonstrate the compliance of the developed user terminals when operating in the target end-to-end system with the requirements identified in the RSD. The System Validation Document shall include the following sections
• Test Plan: this chapter shall define which parameters have to be validated and the associated methods to be used (the test sequence and the test conditions to validate the developed user terminals operating in the target system). Each test shall be assigned a unique identifier. The test plan shall include a simple mechanism to trace conformance of the tests with the requirements identified in the RSD together with the milestone review (i.e. CDR, FR) at which the test will be executed. A paragraph that describes the test facilities shall also be included.
• Test Procedures: this chapter will describe the measurement equipment, test set-up, and
test methods that will be used for executing the tests defined in the test plan. The Test Procedure shall contain for each test a test form where test identifier, test sequence and associated results, pass/fail status, remarks, date and signatures will be recorded during the test execution.
• Test Reports: this chapter shall include a collection of the test forms filled in during the
tests and an overall assessment of the status of compliance with the Technical Requirements.
5.6 Design Justification File (DJF) The Design Justification File (DJF) shall include a detailed design document for all Hardware and Software to be developed, and detail all the trade-off processes performed to justify the design choices.
Page 7
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 8 a
f 6 LIST OF ITEMS TO BE PRODUCED AND/OR DELIVERED 6.1 Deliverable Hardware All hardware developed or procured under this contract is part of the contractual deliverables. However, when the contractor is able to demonstrate that this hardware will, after completion of the contract, be utilised for purposes in line with the ARTES programme objectives, the parties may mutually agree either to conclude a loan agreement or to transfer the ownership to the contractor. 6.2 Deliverable Software and Content The software and content for which ESA will acquire the limited license according to Article 4 Clause 56 of the contract shall be delivered in executable form upon completion of the contract. The same acquisition rule applies to technical data (“information” in the terminology of the General Clauses and Conditions). Licenses of any Commercial Off The Shelf (COTS) software are not required to be delivered. …cont
Page 8
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 9 a
f 6.3 Deliverable Documentation The deliverable documentation given in the following table are required as a minimum and shall be provided during contract as indicated.
Name Deliverable Initial Submission
Updating Final Submission
RSD Requirements Specification Document with the proposal BDR
SP Strategic Plan with the proposal CDR FR BS Build Standard with the proposal BDR CDR
DDP Design and Development Plan with the proposal BDR
DJF Design Justification File BDR CDR FR EVD End-to-End Validation
Document with the proposal BDR, CDR FR
PBC Project detailed bar chart with the proposal as necessary and at reviews
MPR Monthly Progress Report KO + 1 month every month FR DC&MC Document Configuration
and Management Control BDR as necessary FR
MOM Minutes of meeting every meeting attended by the Agency
PWP Project Web Page BDR Current Status as part of the Monthly Progress Report
FR
FREP Final Report FR
COD Contract Outcome Data FR every twelve months FR + 36 months
KO: Kick-Off Meeting BDR: Baseline Design Review CDR: Critical Design Review FR: Final Review 6.4 Final Report (FREP) The Contractor shall deliver, not later than five working days before the FR, a Draft Final Report, on which ESA will provide comments within one week after said review. The Final Report (FREP), which is intended for general publication, is to be written in a very concise form, and will describe the major technical and operational accomplishments of this contract. The FREP shall not contain any confidential/proprietary information or confidentiality/copyright statement other than the following:
“The copyright in this document is vested in [Company]. This document may only be reproduced in whole or in part, or stored in a retrieval system, or
Page 9
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 10 a
f transmitted in any form, or by any means electronic, mechanical, photocopying or otherwise, either with the prior permission of [Company] or in accordance with the terms of ESTEC Contract no ….. “.
Within four weeks after the Final Review the finalised version of the Final Report shall be delivered as follows:
• 2 paper copies and 2 CD-ROMs to the ESTEC Publications Division (EXR-CP), • 3 CD-ROMs to the Agency's Technical Representative
6.5 Final Review Data Pack (FDP) Together with the finalised version of the Final Report, the Contractor shall deliver to the ESA Technical Officer 3 copies of the Final Data Package, consisting of a CD or DVD containing the most recent version of all main deliverables (RSD, SP, BS, DDP, EVD, DJF and all the software developed as part of the contract). The FDP shall contain an index document with links to the different document files. 6.6 Document Confidentiality All deliverable documents produced in the frame of the project will be accessed only by the ESA representative(s) indicated in the contract, with the following exceptions:
• the Final Report and the Project Web Page are intended for public access; • the Contract Outcome Data will, in addition to the ESA representative(s) indicated in the
contract, also be accessed by the ESA Telecom User Support Office
Page 10
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 11 a
f 7 MANAGEMENT 7.1 Project Manager The nominated Project Manager shall be responsible for the management and execution of all work to be performed and for the coordination and control of the work within the industrial team (where applicable). He will be the official point of contact with the Agency during the execution of the work. 7.2 Experts For special cases the Agency reserves the right to be advised by external experts. These experts will be committed to treat any information obtained in the context of this contract on a strictly confidential basis. 7.3 Reporting – Minutes of Meetings (MOM) Formal written Minutes of Meetings attended by ESA shall normally be agreed and made available by the contractor at the end of the meeting. If distributed in manuscript form at the end of the meeting, a typed version shall follow within five working days and be distributed in electronic form to all participants. The minutes shall clearly identify all agreements made and actions accepted together with, where relevant, an update of the Action Item List. To establish a uniform and consistent procedure to identify the Action Items among the different ARTES projects, the Contractor shall keep track of the Action Items adopting the following action identification scheme: Action X.Y where X is the identifier of the meeting (0: Negotiation/Kick Off Meeting, 1: First Review Meeting, 2: Second Review Meeting, etc.), and Y is the Action number starting from 1 at each new meeting. In case the eProject Distributed Project Collaboration Tool (see section 7.7) is adopted, Action items shall be recorded under eProject as “Issues”. 7.4 Reporting – Document Management Configuration and Management Control
(DC&MC) Starting with the first review meeting, the contractor shall create and maintain, for consultation by ESA, a Document Configuration and Management Control recording all documents produced in connection with the contract. The list shall indicate the document title, name of the file,
Page 11
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 12 a
f document reference, type of document, date of issue, revision number, confidentiality level and distribution list. Each deliverable document shall include a Title Page reporting Project Name, Contract Number, Title of the Document, Reference Identifier, Author(s) and related Organisation(s), Date of Issue and Revision Number. All deliverable documents shall include as the second page a Document History Sheet, indicating in short for each submitted revision the corresponding date and the reason for the revision. Each revision shall be formatted in order to easily spot the changed parts with respect to the previous submission. 7.5 Electronic Documentation All documentation shall be delivered in electronic form, using preferably MS Word for Windows©, or Adobe Acrobat© format with all pictures and tables embedded in the document. The documentation shall include in its options the possibility to be printed. 7.6 Project Web Page (PWP) The Contractor shall produce, as part of the first review meeting package, a Project Web Page using the layout enclosed as Attachment I to this document. Every month, starting from the publication of the Project Web page and ending with the conclusion of the contractual activities, the contractor shall provide an updated version of the “Current Status” paragraph of the Project Web Page as part of the Monthly Progress Report. The Current Status paragraph of the Project Web Page will be the opportunity for the project to inform the general public about the status of the progress in the last period. The lack of a recent Current Status will be interpreted by ESA as a sign of the project team not to be able to communicate the progress of their work, and will constitute a non-compliance with contractual obligations. The Contractor shall ensure that the public image of the project is properly portrayed and maintained through the above Web Page. A final version of the Project Web Page shall be provided together with the Final Report. This final version shall include a paragraph summarising the most significant achievements of the project. 7.7 Distributed Project Collaboration Tool – eProject During the execution of the project the contractor and his project team are strongly encouraged to use the web based project planning and collaboration tool “eProject” which has been set up for the ARTES projects and which is accessible from http://artes.eproject.com. This collaborative environment is made available free of charge by ESA for the duration of the project, and it is intended to replace the usual electronic communication tools (e.g. email with attached document and/or ftp) within the project team and in the communication with ESA, as well as for recording and tracking Action Items.
Page 12
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 13 a
f Unless otherwise agreed with ESA and formalised in the minutes of the Kick-Off Meeting, the contractor shall provide at the Kick-Off Meeting the name of the person to be appointed as administrator of the eProject account. The Agency will activate within one week from the Kick-Off Meeting an eProject account dedicated to the project team. During the first part of the project, the eProject environment shall be used on a trial basis by the project team to support information exchange in preparation of the first review meeting. At the first review meeting the Contractor shall inform the Agency whether, on the basis of the results of the trial period, the project team has decided to retain or not the eProject environment for the remaining part of the contract. In case the environment is not retained, the specific eProject account will be deleted by the Agency. An on-line introductory training course on the ARTES eProject cooperative tool is available under http://telecom.esa.int/uso/training/eproject 7.8 Reporting – Monthly Progress Reports (MPR) The Contractor shall provide, within the first five working days of each month, a concise status report following the template provided as Attachment II to this Statement of Work (including information on whether any results or Intellectual Property Rights has been or is expected to be exploited). An electronic copy of this document is available MS Word for Windows© format and can be downloaded from: http://telecom.esa.int/uso/projectsupport/doctemplates This report shall in particular highlight any problems in the development and commercialisation programme and the corrective action taken by the contractor. Within the progress report, the updated Current Status paragraph to be inserted in the Project Web Page shall be provided. To the extent possible, the progress report and annexed documentation should be delivered in MS Word for Windows© format under the eProject environment or as an attachment to email. 8 REPORTING AFTER COMPLETION OF THE CONTRACT In line with the objectives of the ARTES 3 programme elements, ESA support in this initiative is aimed at preparing the future commercial exploitation of the elements developed in the project. To monitor the effectiveness of this element of the ARTES programme and to continuously improve its efficiency, it is critically important for ESA to keep some visibility of the outcome of the commercial exploitation of the project’s results, which will be typically become evident only after the conclusion of the contract with ESA. The contractor shall provide the information concerning the main commercial development of the project (including exploitation of IPR) and the related impact on the company using the “CONTRACT OUTCOME DATA” questionnaire as shown in Attachment III. Such information shall be provided to the ESA technical officer and in copy to the ESA Telecom User Support Office ([email protected]) every 12 months for a period of 3 (three) years starting from the completion date of the contract at no cost to the Agency. The information will
Page 13
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 14 a
f be treated by ESA as strictly confidential, and any disclosure outside the ESA ARTES team will be made only after having received written consent by the Contractor. 9 ESA TECHNICAL ASSETS The Contractor may use the Technical Assets which have been made available by the Agency and agreed at the Negotiation Meeting (if applicable). The nature of the ESA Technical Assets that are available and procedures for obtaining access are discussed further in the Special Conditions of Tender.
Page 14
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 15 a
f
ATTACHMENT I: Word Template for Project Web Page (PWP)
NB: If you are not the single Contractor, please co-ordinate your Project Page with the prime Contractor or project Partner(s). Only the prime contractor is entitled to deliver the project web page to ESA. Instructions for Use: Once completed, save to disk and then send by electronic mail or via eProject to the ESA Technical Officer in charge of the Project. Please note that this template has to be used only for the first submission of the project web page or for major subsequent redesign. For the provision of the last paragraph update on the Current Status, please use the relevant paragraph in the Monthly Progress Report, and not this template. Note: Please include images at 300 dpi resolution, and in Tiff format (for use on the web and in print). Project Web Page Template: Please replace all the text in blue with your own, and then save it to disk. ARTES element:
Which ARTES element your submission refers to (1, 3, 4 or 5)
Document Date:
Today's Date
Project Name: Name Project Code: (if known) ESA Contract number:
Project Team: Prime Contractor Company:
Name (Country Code) WebSite (http://www.com
Company Logo Subcontractor A:
Name (Country Code) WebSite
Company Logo
Page 15
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 16 a
f Subcontractor B:
Name (Country Code) WebSite
Company Logo Project Logo:
Project Logo Project Objectives:
Describe in less than 200 words the objectives of the project. A drawing or picture may be inserted.
(The above is a sample picture)
System Architecture
Describe in less than 300 words the architecture of the system to be developed in the project. A diagram may be included.
Project Plan Describe in less than 100 words the expected plan. Please, do
not use actual dates, but period of time after with respect to milestones.
Key issues Describe in less than 100 words the key issues addressed in the
project. Expected main Benefits
Describe in less than 200 words the expected benefits brought by the project, in particular with respect to potential existing competitor systems.
Page 16
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 17 a
f Current Status Describe in less than 200 words the status of the project (brief
summary of achievements, work currently in progress, activities about to start).
Contact:
Name Email Project Manager: Postal Address: Company
Name Email Additional Contact: Postal Address: Company
Page 17
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 18 a
f
ATTACHMENT II: Monthly Progress Report (MPR)
Project: PROJECT NAME
ESA Contract N.: XXXXX/XX/XX/XX
Date: DD Month YYYY Period Covered: DD Month YYYY- DD Month YYYY Author(s): Project Manager Name (Company) …………… Contributions: Contributor A (Company) Contributor B (Company) …………… Activities Performed during the period Please provide a summary of the activities performed during the reporting period. Although you are free to adopt your own structure, please try to follow these guidelines:
• Be concise • Avoid a report that is too structured (like reporting by WP) • Do not keep reporting past issues adding new things to old ones, which are not
anymore relevant for the time span covered in the report • Consider the Monthly Progress Report as a tool not only to keep ESA informed, but
the whole project team • Be systematic; provide the Monthly Progress Report on time, and not only during the
first months. A good Monthly Progress Report is a key tool to circulate information in your project team, and keep active the responsiveness of your team
Action Items List It is a good practice to keep an updated list of the Action Items open at the meetings with ESA. Our suggestion is to organise this in a spreadsheet as below. In this paragraph you can summarise and comment on the activities affecting the Action Items. N.B.: Projects that use eProject can obtain the table below in automatic mode, using the “MPR Contribution” function under “Report”. The table obtained in this way can be exported in MS Word and easily imported into the MPR document.
Page 18
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 19 a
f
Action Items Status, Ver. DD Month YYYY
Action ID Description Originator Actionee Due Date Status Closure Date Comment
0.1 Adopt MPR Template ESA XXX DD month
YY Closed DD month YY
0.2 Revise PSA ESA YYY DD month YY Open
Deliverables Status List This section is dedicated to provide an updated snapshot of the deliverable status. Deliverable Status List: Documents Please provide a summary table reporting the status of the document deliverable list, following the example below:
Document Deliverables List Type of Document Title Rev. File type First Date of
Publication Last date of Publication
Report Pilot System Architecture X.X MS Word DD Month YYYY DD Month YYYY Report Pilot Utilisation Plan X.X Acrobat PDF DD Month YYYY DD Month YYYY
Web Page Project Web Page MS Word DD Month YYYY DD Month YYYY
Deliverable Status List: HW/SW Items Please provide a summary table reporting any updates (if needed) of the deliverable items (Software and Hardware, developed or procured), following the example below:
HW/SW Deliverables List Item Description Quantity ID Location Value EUR
Problems Encountered Please indicate here any problem areas that you encountered and any corrective measures that will be taken.
Page 19
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 20 a
f Planned Activities for Next Period Please provide a short summary of the activities to be undertaken for the next period Current Status Update for the Project Web Page under the ARTES 3 Web Site Starting with the first Monthly Progress Report after the BDR, you have to provide an updated current status paragraph for your Project Web Page, which will be published on the ESA Telecom Web Site. Please remember that the paragraph that you provide here will be made public! The ESA technical representative of your project will coordinate the updating of the web page Intellectual Property Rights Please state whether any results or Intellectual Property Rights arising from work performed under the Contract has been (or is intended to be) exploited.
Please feel free to improve the present layout according to your needs!!
Page 20
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 21 a
f
ATTACHMENT III: Contract Outcome Data (COD) 1. Company Name: 2. Project Name: 3. ESA Contract number: 4. Date: 5. Reporting Period (months after Contract Close out) 12 24 36 6. Briefly describe how well the Project met its original aims and objectives (wrt the Strategic Plan submitted at the Final Review) 7. New technologies / New Products developed (including New Patents)
Page 21
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 22 a
f 8. Give your assessment of the likely commercial opportunities for this technology (include potential for accessing New Markets) a) Space sector
b) Non space sectors
9. Has the technology developed as a result of this contract, resulted (to date) in (please indicate the amounts):
Item Yes/No Value Cumulated direct Sales Cumulated indirect Sales (including license agreements) Current number of Users (as applicable) Cumulated number of Equipment Produced (as applicable) Cumulated number of Equipment Sold/Deployed (as applicable)
10. If NO, how long before you anticipate a commercial return?
Estimated time to commercial return (months)
11. Were further financial investments necessary after the end of the ESA Contract for this specific Project? If YES please indicate the cumulated value
Cumulated Value 12. Technology Transfer Agreements
Number Estimated Value(€) TT agreements In TT agreements Out
13. Employment generated as a result of ESA Contract
14. International Linkages / Partnerships generated as a result of ESA development activity
in Development phase Who? in Commercial phase Who?
Page 22
Ref. : EUI-T/0002093, Rev.1.6 Date : 29 August 2006
Page : 23 a
f 15. Other information which you consider relevant (e.g. collaborative working, your organization’s internal processes - project design, quality control, etc.) 16. Suggestions to improve ESA Processes/Interfaces 17. Any other comments
Page 23
