ANNEX B TERMS OF REFERENCE FOR THE PROVISION OF

Transcription

1 ANNEX B TERMS OF REFERENCE FOR THE PROVISION OF IMS/ED SPECIFIC SOFTWARE AND OTHER SERVICES FOR SENSOR CALIBRATION IN THE IMS NETWORK ON A CALL-OFF BASIS Annex B Terms of Reference (v5.6) September 2013 Page 1 of 19

2 TABLE OF CONTENTS I. INTRODUCTION... 3 II. SCOPE OF WORK... 3 II.1 Calibration Toolbox... 4 II.1.1 Introduction... 4 II.1.2 Stage 1: Design phase... 6 II.1.3 Stage 2: Development of the Software... 9 II.2 Maintenance, Support, Development and Enhancement II.2.1 Task 1: Software Development II.2.2 Task 2: Database Development II.2.3 Task3: Documentation II.2.4 Task 4: Support and Enhancements of the Calibration Software Toolbox III. METHODOLOGY, STANDARDS, AND TECHNOLOGY IV. ORGANIZATION OF WORK IV.1 Initiating Work IV.2 Completion and Acceptance IV.3 Invoicing and Payment V. TERM OF CONTRACT AND OPTIONAL EXTENSION VI. WARRANTY OF THE SOFTWARE VII. REQUIREMENTS FOR THE STAFF OF THE CONTRACTOR VII.1 Skills and experience for each (key) staff of the Contractor VII.2 Skills and experience of Project Manager and Senior Software Developer VII.3 Skills and experience that should be available among the (key) staff of the Contractor VIII. RESOURCES PROVIDED BY THE COMMISSION Annex B Terms of Reference (v5.6) September 2013 Page 2 of 19

3 I. INTRODUCTION The Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization (hereinafter be referred to as the Commission ) operates a global verification regime to monitor compliance with the Comprehensive Nuclear-Nuclear-Test-Ban Treaty. It provides timely data, assessments and other products and services to Signatory States of the Treaty. The Commission operates and maintains the International Monitoring System ( IMS ) network. Thereby, the Engineering and Development Section (the ED section) is among others responsible for evaluation of quality of the IMS seismic/infrasound stations to ensure proper functioning of the sensors, calibration, sensor orientation and polarity parameters in compliance with the IMS division requirements. (a) The Commission desires to engage a contractor (hereinafter referred to as the Contractor ) to provide software engineering support and other services (hereinafter referred to as the Contract ) in accordance to these Terms of Reference (hereinafter referred to as the ToR ). (b) The Contractor is required to supplement the work already carried out by the ED section by providing engineering services, such as software development, database structure design and tuning, hard- and software system engineering and integration, analysis of various problems observed at specific IMS stations, development and validation of solutions. (c) The ToR defines the scope of work and technical framework of the Contract, as well as all minimum and optional technical requirements the Contractor and their services shall meet. II. SCOPE OF WORK The scope of Work shall include provision of specific, task-dependent deliverables such as, but not limited to software source code, software documentation and database design enhancements. The end result of the services will be a significant improvement in the efficiency of the ED section to evaluate the status of the IMS seismic/infrasound stations. (a) All documents shall be delivered to the Commission in electronic form, in PDF and MS Word format. The Commission shall retain the ownership of copyrights of all documentation delivered to the Commission under the Contract. (b) For software development, Open Source technologies shall be preferred. The source code for the developed software should be delivered to the Commission upon completion of each task and shall become the property of the Commission as of the delivery date. The source code of the software developed under the Contract shall follow the PTS software standards and guidelines. Annex B Terms of Reference (v5.6) September 2013 Page 3 of 19

4 This section breaks down the scope of Work into separate tasks. This section lists the tasks as foreseen at the time of this writing. The Commission reserves the right to add and remove tasks from the list below as dictated by changes in its business case. This may require an amendment of the Contract. II.1 CALIBRATION TOOLBOX II.1.1 Introduction This section breaks down the scope of Work into two stages, subdivided into tasks. This section lists the tasks as foreseen at the time of this writing. The Commission reserves the right to add and remove tasks from the list below as dictated by changes in its business case. This may require an amendment of the Contract. Stage 1: Design phase In Task 0, a 2-days kick-off meeting shall be held at the Commission s premises in Vienna, Austria, in order to clarify all functional and non-functional requirements related to the design phase; In Task 1, the Contactor shall produce a design document and a requirements document for the software to be developed in the tasks described under Stage 2 and for the Calibration Database. Stage 2: Development of the software The development of the software shall be done within the following three consecutive tasks: In Task 0, a 1-day kick-off meeting shall be held at the Commission s premises in Vienna, Austria, in order to clarify all functional and non-functional requirements related to the development phase; In Task 1, the Contractor shall produce a Calibration Reporting Module; In Task 2, the Contractor shall produce an Interactive Seismic Calibration Analysis Module, integrated with the PTS Calibration Reporting Module. Annex B Terms of Reference (v5.6) September 2013 Page 4 of 19

5 CALIBRATION FRAMEWORK Calibration Documentation platform Central WIKI PTS Evaluation Dashboard Library of technical functions Documentation Repository PTS Statistical dashboard Station Statistics Evaluation dashboard Autogeneration of Station calibration report PTS Scheduled Calibration Dashboard Magnitude Residual Noise Spectra Response estimation Group Statistics Calibration Schedule interface Retrieving Waveforms Yearly Report Storing Calibration Definitions Response Conversion tool PTS CALIBRATION REPORTING MODULE (Dev. Stage 2 - Task 1) INTERACTIVE SEISMIC CALIBRATION ANALYSIS MODULE (Dev. Stage 2 -Task 2) CALIBRATION DATABASE CAMT SCHEDULING SOFT OTHER RESSOURCES READ ONLY PTS DATABASES C&C TEXT MESSAGES SSI CALIBRATION MODULE IRS REPORTS OTHER DATA SOURCES Figure 1 - Overview of the Calibration Framework (a) The Project Manager or a Senior Software Developer that will lead the project on behalf of the Contractor should be available to attend the initial kick-off meetings at the beginning of both Stages, and be available, if requested, to be present during final delivery and installation of the deliverables, at the end of each Stage and Task. (b) In the frame of the following tasks, the Contractor shall be ready to provide database and web programming services such as, but not limited to: creating and/or modifying database structures, generating various reports by querying from databases as per need and generated relevant web-based reports. The contractor is free to propose a programming language and reporting tools. They have to be agreed during the kickoff meetings. Annex B Terms of Reference (v5.6) September 2013 Page 5 of 19

6 II.1.2 Stage 1: Design phase II Task 0: Kick-Off Meeting II Purpose All functional and non-functional requirements related to the design phase will be specified and clarified. The kick-off meeting will involve discussions with selected staff at the Commission s Headquarters and the Contractor will be provided sufficient background information from applicable files and sources to begin work. The kick-off meeting shall last two (2) consecutive days and will include a presentation of IMS stations, given by the Commission to the Contractor. At the end of two (2) working months after the acceptance of the Work Order by the Commission, the Contractor is expected to fully understand the nature and Scope of Work and to identify any further necessary background information it may require. II Work schedule for Task 0 Step 1 Step 2 Step 3 Within 10 working days after receipt of the Work Order for Stage 1 - Task 0 by the Contractor 10 working days after completion of Step 1 Within 15 working days after Step 2 Step 3a Within 15 working days Stage 1 - Task 0 will be performed at the premises of the Commission in Vienna, Austria, through a kick-off meeting with the Contractor; this meeting will last 2 days and shall be attended by the Contractor s Project Manager and a Senior Software Engineer. During this time all functional and non-functional requirements related to the design phase will be specified and clarified. A user group will be made available to the contractor to clarify any issues regarding the desired functionality of the system. The Commission will also make available IT staff that will provide details about the Commission s IT infrastructure. Contractor submits Software Requirements document to Commission Evaluation of the product by the Commission If the product does not meet requirement, the Contractor shall bring it within specifications. Task 0 completed Annex B Terms of Reference (v5.6) September 2013 Page 6 of 19

7 II Task 1: Design of the software II Purpose The purpose of the design phase is to implement a design document and requirements document for the software to be developed in the tasks described under Stage 2 and for the Calibration Database. CALIBRATION TOOLBOX Calibration Documentation platform Central WIKI - use of calibration software - equipment specific informtion Documentation Repository PTS Evaluation Dashboard Evaluation dashboard (calls to Analysis Module) Autogeneration of Station calibration report Library of technical functions called to support evaluation of calibration results / generation of calibration reports Magnitude Residual PTS Statistical dashboard Generation of station/channel specific statistics Drawing statistics on calibration status of IMS network (group of stations, per country, ) Generation of Yearly Report PTS Scheduled Calibration Dashboard Calibration Schedule interface Interactive / editable interface on current status of calibration - Retrieve calibration status bit - Retrieve CALIB in datastream - Populate calib DB Storing calibration definitions - as agreed with SO (exhaustive) - CALIBRATE_START messages Noise Spectra Response estimation (based on calibration data) Interface to IMS2.0 to retrieve relevant waveforms Response Conversion tool: - Convert Responses - Retrieve Responses from SSI PTS CALIBRATION REPORTING MODULE (Task 1) INTERACTIVE SEISMIC CALIBRATION ANALYSIS MODULE (Task 2) CALIBRATION DATABASE CAMT SCHEDULING SOFT OTHER RESSOURCES READ ONLY PTS DATABASES C&C TEXT MESSAGES SSI CALIBRATION MODULE IRS REPORTS OTHER DATA SOURCES Annex B Terms of Reference (v5.6) September 2013 Page 7 of 19

8 II Definition The Design of the software and of the Calibration Database should be implemented based on: - the requirements described under Stage 2 of this ToR ; - details of the implementation discussed with the PTS during meetings. The Design of the Calibration Database should take into account both: - Interactions with the Calibration Framework - Foreseen Interactions with identified Tiers software, such as the CAMT software and the SSI Calibration Module. The Design of the software should take into account any foreseen Interactions with identified Tiers software, such as the CAMT software and the SSI Calibration Module. II Deliverables and Outcome The following deliverables are expected for Stage 1 - Task 1: - Software mockup; - Database design document; - Software design document; - Software requirements document; - Technical architecture of the Calibration Framework and of its interactions with external software. II Work schedule for Task 1 Step 1 Step 2 Step 3 Within 2 calendar months (estimate) after the acceptance of the Work Order for Stage 1 - Task 1 by the Commission After 1 calendar months after Step 1 within 15 working days after Step 2 Step 3a within 15 working days The following documents should be finalized and submitted to the PTS: - Database design document - Software design document - Software requirements document - Technical architecture of the Calibration Framework and of its interactions with external software Review meetings using online tools (Skype, etc.) will take place at regular intervals (fortnightly) to be agreed between the Commission and the Contractor during which the contractor shall demonstrate the progress on Stage 1. A mock-up of the software to be delivered. The work will be performed at the Contractor s premises; review meetings using online tools (Skype, etc.) will take place at regular intervals (fortnightly) to be agreed between the Commission and the Contractor during which the contractor shall demonstrate the progress on Task 1. Evaluation of the product by the Commission If the product does not meet requirement, the Contractor shall bring it within specifications. Task 1 completed Annex B Terms of Reference (v5.6) September 2013 Page 8 of 19

9 II.1.3 Stage 2: Development of the Software II Requirements for the software: The Contractor shall develop a web-based Calibration Framework that facilitates the integration of a number of modules that will fulfill, notably, reporting, configuration, monitoring and signal processing tasks as defined below. Development of new modules and their integration into the Calibration Framework should be straightforward and should not require involvement of the Contractor after the expiration of the Contract. Integration of new modules into the Calibration Framework should not require recompiling of the whole Framework; The Calibration Framework will need to interface with the existing Calibration Oracle database (hereinafter referred to as the Calibration Database ) in order to retrieve calibration related information and populate the Calibration Database with newly obtained calibration related information; The Calibration Framework will need to interface with several sources of data such as PTS databases, IRS database, ASCII and binary files as represented in the figure above. The server side components of the Calibration Framework will be hosted on an Apache HTTP server with a Tomcat Servlet Container. However, the Contractor may propose a different technology, if he sees fit. The technical architecture for the Calibration Framework (Modules) shall be defined in the design phase. II Task 0: Kick-off meeting II Purpose A consolidated work plan will be discussed and derived from the deliverables of Stage 1. II Work schedule for Task 0 Step 1 Within 10 working days after the acceptance of the Work Order for Stage 2 - Task 0 by the Commission 5 working days after completion of Step 2 Step 1 Step 3 within 15 working days after Step 2 Step 3a within 15 working days Stage 2 Task 0 will be performed at the premises of the Commission in Vienna, Austria, in the form of a kick-off meeting with the Contractor; this meeting will last 1 day and shall be attended by the Contractor s project manager and a software developer. During this time a work plan will be discussed and derived based on the design documentations and software mock-up from Stage 1. Contractor submits the consolidated work plan to the Commission Evaluation of the product by the Commission If the product does not meet requirement, the Contractor shall bring it within specifications. Stage 2 - Task 0 completed Annex B Terms of Reference (v5.6) September 2013 Page 9 of 19

10 II Task 1: Producing a Calibration Reporting Module II Purpose The purpose of Task 1 is to: Upgrade the existing Calibration Database based on database designs from Stage 1. Create a Calibration Reporting Module that will help to reduce to a minimum the time spent by the ED section on recurring procedural and technical tasks, like, but not limited to, facilitation of calibration reporting for any period of time, station, operator and station hardware type that may help to identify potential hardware or configuration issues. II Definition The Calibration Reporting Module shall be comprised of 4 components, as listed below: a. Scheduled Calibration Dashboard The Scheduled Calibration Dashboard should be an Interactive and Editable interface presenting the current status of the scheduled calibration. The following functionalities shall be supported by the Scheduled Calibration Dashboard: providing an interactive view of the calibration status of the IMS Seismic stations; Retrieving calibration related information from the data-stream (CALIB value, status bit ); Facilitating local storage of calibration and, generally, station configuration information a Calibration Scenario Definition interface that will allow to create and manage accurate, reusable and editable definition of calibration scenarios for seismic stations, and to export those into IMS2.0 format; The Calibration Dashboard should be understood as an interactive tool to display and populate the Calibration Database, based on incoming data and other sources of information, like station configuration files and calibration related IMS2.0 Command & Control messages. b. Evaluation Dashboard The Evaluation Dashboard should be an Interactive interface used to evaluate the results of calibration for a particular station or channel. The following functionalities shall be supported by the Evaluation Dashboard: Making calls to the Analysis Module functions (see description in Task 2); Providing an interactive view of the calibration status of a set of channels for a particular station; consistency checking mechanism making available on-demand and/or on a regular basis in a single display station/channel specific information extracted from various sources, like databases and textual configuration files. Auto-generation of Station Calibration reports, further editable by PTS staff. Annex B Terms of Reference (v5.6) September 2013 Page 10 of 19

11 c. Statistical Dashboard The Statistical Dashboard should be an Interactive interface used to display calibration statistics based on shared characteristics of IMS Seismic Stations, allowing to create statistics for any period of time, any seismic station, operator, a predefined and user-defined group of stations, type of hardware based on the information available in a database or a file. The following functionalities shall be supported by the Statistical Dashboard: Generation of station/channel specific statistics; Drawing statistics on calibration status of IMS network (group of stations, per country, ) Generating the yearly calibration report, in cooperation with the existing CAMT software, in agreement with the design documents from Stage 1. d. Calibration Documentation Platform The Calibration Documentation Platform is meant to: Provide calibration relevant equipment specific information to the relevant parties; Provide easy instructions on how to use calibration station specific software; Host a web tool to support relevant calculations. The Calibration Support Platform shall be developed as a web application on the Commission s server network. II The following functionalities shall be supported by the Calibration Documentation Platform: Central WIKI, meant to contain equipment specific information and guidelines for the use of calibration software components; Providing a Documentation Repository. The Calibration Reporting Module will make use of the following data sources to compile the data required: The DOTS database containing station information for all installed stations and information on treaty codes and station codes. The IDC database containing station information, station codes, site and channel names, type of the equipment installed, calibration values of the stations in operation; IRS database containing station specific reports and other information; The Calibration Database; and Station configuration data. Access to relevant sources of data will be made available by the Commission to the Contractor. II Deliverables and Outcome The following deliverables are expected for Task 1: the software, as described during the design phase (Stage 1), including the actual source code and compilation, configuration and installation instructions; the relevant manuals; fortnightly status reports; Annex B Terms of Reference (v5.6) September 2013 Page 11 of 19

12 assistance to Commission s IT staff to install the software on the Commission s infrastructure; The acceptance conditions are as follows for Task 1: the functionality of the delivered product, to be evaluated by the PTS within 15 days after delivery of the product by the Contractor; delivery of the periodic reports on time is an acceptance condition. The Commission will review the report within 15 working days and may request revisions or additional information. If the Commission does not formally accept the report or request a revision/additional information within this period, the report is automatically accepted. The PTS may request the Contractor to send a representative for a few days to participate to the evaluation of the functionality of the delivered product. Special attention will be given to the following features: the software meets minimum requirements as defined in the Design Phase (Stage 1) and in the ToR and the software requirement document; the outcome of Task 1 should demonstrate a clear mechanism of integration for the modules further developed in Task 2. II Work schedule for Task 1 This work schedule applies to Task 1. Step 1 Step 2 Step 3 Within 10 working days after the acceptance of the Work Order for Stage 2 - Task 1 by the Commission Within 10 working days after the completion of Step 1 2 calendar months (estimate) after completion of Stage 2 Task 0 Step 4 within 15 working days after Step 3 Step 4a within 15 working days Provide software requirements document that includes Stage 2 Task 1 software details. Provide mock-up of the software described under Stage 2 Task 1 in the ToR, the design documents from Stage 1, and the Requirement document. Delivery of the completed product described under Stage 2 - Task 1 in the ToR, the design documents from Stage 1, and the Requirement document. The Contractor must be presented at the Commission s premises for two days at the completion of the Work in order to present the Deliverable of Task 1, and to receive feedback on them. Evaluation of the product by the Commission If the product does not meet requirements, the Contractor shall bring it within specifications. Stage 2 - Task 1 completed Annex B Terms of Reference (v5.6) September 2013 Page 12 of 19

13 II Task 2: Producing an Interactive Seismic Calibration Analysis Module II Purposes: The purpose of Task 2 is to produce an Interactive Seismic Calibration Analysis Module, namely a Library of technical functions that support the evaluation of calibration results and the generation of calibration reports in the Calibration Reporting Module (developed under Task 1): to facilitate the analyses of calibration results and the diagnose the discrepancies; to facilitate the production of quality calibration reports. II Definition Interactive Seismic Calibration Analysis Module shall provide a set of analytical and statistical functions as described below: Magnitude and Orientation Residuals: computation and plotting of relevant magnitudes and orientation residuals and other relevant indicators from IDC data using existing tools; Response estimation based on calibration data; Noise Spectra; Interface to IMS2.0 to retrieve relevant waveforms; A Response Conversion tool to convert responses and retrieve responses from SSI. The functionalities of the Analysis Module should provide the ability to call the relevant functions: from the Calibration Reporting Module components; via external command line tools/scripts. A further enhancement of the software would be: statistical and correlation analysis of waveform data. The Interactive Seismic Calibration Analysis tool will make use of the data sources described in Task 1 (section II ). II Deliverables and Outcome The following deliverables are expected for Task 3: the software, as described in the definition of Task 3, including the actual source code and compilation instructions; the relevant manuals; fortnightly status reports; assistance to Commission s IT staff to install the software on the Commission s infrastructure; The acceptance conditions are as follows for Task 3: the functionality of the delivered product, to be evaluated by the PTS within 15 days after delivery of the product by the Contractor; Annex B Terms of Reference (v5.6) September 2013 Page 13 of 19

14 delivery of the periodic report on time is an acceptance condition. The Commission will review the report within 15 working days and may request revisions or additional information. If the Commission does not formally accept the report or require revisions/additional information within this period, the report is automatically accepted. The PTS may request the Contractor to send a representative for a few days to participate to the evaluation of the functionality of the delivered product. Special attention will be given to the following features: the software meets minimum requirements as defined in the Design Phase (stage 1) and in the ToR and the software requirement document. If it is found while the delivered product is being evaluated by the PTS (as defined above) that the Calibration Framework Core needs further developments to allow a smooth integration of the Help Module, then those developments should be a part of Task 2. II Work Schedule for Task 2 This work schedule applies to Task 2. Step 1 Step 2 Step 3 Step 4 Within 10 working days after the acceptance of the Work Order for Stage 2 - Task 2 by the Commission Within 10 working days after the completeion of Step 1 within 3 calendar months (estimate) after Step 2 within 15 working days after Step 3 Step 4a within 10 working days Provide updated software requirements document that includes Stage 2 - Task 2 software details. Provide mock-up of the software. Delivery of the completed product described under Stage 2 - Task 2 in the ToR, the design documents from Stage 1, and the Requirement document. The Contractor must be presented at the Commission s premises for two days at the completion of the Work in order to present the Deliverable of Task 2, and to receive feedback on them. Evaluation of the product by the Commission If the product does not meet requirement, the Contractor shall bring it within specifications. Stage 2 - Task 2 completed Annex B Terms of Reference (v5.6) September 2013 Page 14 of 19

15 II.2 MAINTENANCE, SUPPORT, DEVELOPMENT AND ENHANCEMENT The Commission may ask for services related to the sensor calibration program in the IMS network. These services include computer systems engineering, software development, integration of new modules developed by the PTS, software problem investigation, software maintenance and documentation. The WOs will be based on one (1) or more of the tasks described in this section and on the approved work plan for each of the task(s) to be completed. II.2.1 Task 1: Software Development The Contractor shall be ready to provide software development services such as, but not limited to: further development of the calibration toolbox software (see above sections II.1.1), software integration, designing and/or developing of other software and troubleshooting of the existing software used by the IMS division within the frame of the calibration and orientation projects. If needed, remote access to the relevant infrastructure (servers, VLANs, databases) in the PTS network should be given to the Contractor. «Infrastructure» comprises, but is not limited to software, servers, VLANs and databases. The Contractor may be asked to implement output from an external hardware device into a software application. As orientation of seismic sensors (alignment to geographic North) is a part of calibration, such external devices may include e.g. Attitude & Heading Reference System (AHRS) modules. The Contractor may be asked to develop a software packages that allows to display the output of AHRS modules and to track the motion of the AHRS module, or to use an AHRS module as a heading lock device or heading lock gyro. II.2.2 Task 2: Database Development The Contractor shall be ready to provide database development services such as, but not limited to: creating and/or modifying database structure, generating various reports by querying from databases as per need. II.2.3 Task3: Documentation The Contractor shall assist the Commission to write and collect documentation related to calibration project, and to manage the library of documentation. All documents shall be delivered to the Commission in electronic form, in PDF and Microsoft Word formats. The Commission shall retain the ownership of copyright of all technical drawings and documentation delivered to the Commission under the Contract as well as the delivered software and its source code. Annex B Terms of Reference (v5.6) September 2013 Page 15 of 19

16 II.2.4 Task 4: Support and Enhancements of the Calibration Software Toolbox The Contractor shall be available to provide support and enhancements for the software tool delivered as an outcome of Tasks 1 and 2 of Stage 2. Furthermore, the Contractor shall be available to demonstrate the current functionality of the software, implement software patches or enhancements, provide training or other services associated with operating the tool. III. METHODOLOGY, STANDARDS, AND TECHNOLOGY The Contract shall follow the Release Early, Release Often (RERO) software development philosophy which emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers, testers and users. Each new delivery shall include a description of what changes were made relative to the previous release, along with a list of files that were modified by each change. Each release shall also include a list of outstanding items to be done, including know defects. In line with RERO, updated source code shall be delivered frequently, e.g., once every one or two weeks. The software deliveries shall be one of the subjects of discussion during the biweekly meetings (see further below). The software shall follow the IDC Coding Standards and shall compile and run under the Linux operating system family (RHEL/CentOS/SL 5.x + 6.x, or compatible). All documentation shall adhere to the IDC Documentation Standards. Both Standards will be made available to the Contractor upon request after signature of the Contract. All deliverable material, comments, meetings, presentations and other communications with the Commission shall be written and/or be conducted in the English language. Electronic versions of the deliverables shall be provided in a format to be agreed at the kick-off meeting. Hard copies of the deliverables shall be provided in three copies. IV. ORGANIZATION OF WORK The Commission will initiate the Work in the form of Work Orders (WO). These WOs shall include the exact scope of Work and the required deliverables to be performed and delivered by the Contractor. IV.1 INITIATING WORK (a) Before the issuance of a WO to the Contractor and upon receipt of a written request, containing elaborations and definitions as to the nature of the particular Work(s), the Contractor shall provide, at a minimum, within one (1) week of receiving the written request, the following information in the form of a Work Plan for each Work identified in the written request: Work plan and key schedule to accomplish the Work; Assumptions, constraints, and key risks that could affect the completion of the Work and proposed methods to manage the risks; Annex B Terms of Reference (v5.6) September 2013 Page 16 of 19

17 (b) (c) (d) (e) (f) Number of man-days to be allocated to the Work; Place of work (on-site / off-site); Commencement date and completion date of the Work. After review of the Work Plan for the Work identified in the written request, and only after acceptance by the Commission, the WO will be issued to the Contractor. Each WO shall be based on one (1) or more of the tasks described in Section 2 above and on the approved Work Plan for each of the Work to be completed. The Commission will forward WOs to the Contractor with adequate advanced notice and containing all necessary details, expected deliverables, and minimum requirements for satisfactory performance. The Contractor shall perform Work only after receipt of the WO. During the performance of the Work under a WO, the Contractor shall respond within two working days to any comments from the Commission on work-in-progress with a plan to resolve issues. Upon signature of the Contract, the Contractor shall draft a WO work plan template for review and acceptance by the Commission. IV.2 COMPLETION AND ACCEPTANCE (a) At the end of a particular Work under the WO, the Contractor shall submit to the Commission the deliverables within the period of performance stated in the respective WO. The deliverables may include: Updated Software Design Documents; Updated Software User Guide; Developers Guide. Updated source code for software and common libraries, including documentation; The functionality of the delivered product, to be evaluated by the PTS within 20 days after delivery of the product by the Contractor. (b) If requested by the Commission in a WO, upon completion of the Work(s) under the WO, the Contractor may be required to provide an oral presentation (including slides/handouts as required) to the Commission at its Headquarters in Vienna. IV.3 INVOICING AND PAYMENT The deliverables, after being evaluated and accepted as satisfactory by the Commission, will form the basis for invoicing and payment of a particular Work performed under a WO. Annex B Terms of Reference (v5.6) September 2013 Page 17 of 19

18 V. TERM OF CONTRACT AND OPTIONAL EXTENSION The Commission shall have the right, but not the obligation, to call-off Work in the form of WOs from signature of the Contract until 18 months thereafter ( Initial Call-off Period ). The volume of Work under the Initial Call-off Period will be limited to 200 man-days. This is an upper limit only, and the Commission reserves the right, at its sole discretion, to call-off less man-days or no man-days at all. At the end of the Initial Call-off Period, or the depletion of the maximum number of mandays, whichever occurs first, the Commission shall have the option to extend the Call-off Period twice for 18 months each at the terms and conditions set out in this Contract. The effort under each extension will be limited to 200 man-days as well. VI. WARRANTY OF THE SOFTWARE The Contractor shall be responsible for fixing software defects found during the utilization of the software two years after the acceptance by the Commission of the Work under relevant Tasks during the Initial Call-off Period or each extension of the Call-off Period as defined in Section 5. The Contractor shall fix the software defects after written notification from the Commission with the description of the problem within one week or upon mutually agreed time. VII. REQUIREMENTS FOR THE STAFF OF THE CONTRACTOR VII.1 Skills and experience for each (key) staff of the Contractor Each of the Contractor s staff performing the Work must have at least the following qualifications: 1. A university degree in Computer Science or other scientific/technical subject with a high computational content; 2. At least 2 years of recent professional experience developing applications of similar scope using state of the art technologies; 3. Strong experience in object oriented development and design patterns, exposure to project management methodologies and incremental software development techniques; 4. Working knowledge of written and spoken English; Because of the amount and complexity of the domain knowledge related to the calibration project, Contractor staff continuity throughout the contract is essential to the Commission. VII.2 Skills and experience of Project Manager and Senior Software Developer 1. A university master s degree in Computer Science or other scientific/technical subject with a high computational content; 2. At least 5 years of recent professional experience developing applications of similar scope using state of the art technologies; 3. At least 2 years of recent professional experience in computer systems engineering; 4. Professional experience of database programming using Oracle databases; 5. Fluency in written and spoken English Annex B Terms of Reference (v5.6) September 2013 Page 18 of 19

19 VII.3 Skills and experience that should be available among the (key) staff of the Contractor 1. Professional experience in Digital Signal Processing; 2. Ability to write quality Software Documentation in English language; VIII. RESOURCES PROVIDED BY THE COMMISSION For designated Contractor Personnel, and to the extent necessary for the Contractor to fulfil the requirements of these ToR when carrying out Work approved by the Commission on site, the Commission will provide/make available: (a) (b) (c) (d) (e) Infrastructure, including office space and standard office supplies, hardware and software. Access to , telephone and facsimile. Physical access to selected areas of the Vienna International Centre; however, strict conditions and limitations on access and use of any accessed code or documentation described above will apply as contained in the Contract. Access will be granted only upon request and approval by the relevant internal bodies. Relevant documentation to the Contractor. Qualified staff to assist and cooperate in responding to information requests from the Contractor in order to allow the Contractor to carry out the Work. All other resources, be it for onsite or offsite Work, are to be provided by the Contractor. Annex B Terms of Reference (v5.6) September 2013 Page 19 of 19