Instrument Control Systems Seminar, 20 October 2014 Instrument Development Process Hans Dekker

Nasmyth Architecture Change Request meeting, 17 September 2014 Contents  The Role(s) of ESO  Role of ESO Contact Person.  Ticket based support system (Jira).  Phases of the instrument development.  Documents to provide, guidelines for writing documentation

Nasmyth Architecture Change Request meeting, 17 September 2014 ESO Role(s) Consortium Interactions with ESO have two flavours: Consortium ESO/Customer Consortium ESO/Partner Statement of Work Technical Specification, ICD with Observatory Progress reports and meetings Review meetings (PDR, FDR, IRR, PAE, PAC) Verification at System level MOU (as other partners in the consortium) Workpackage description Subassembly specification, internal ICD WP progress reports to Consortium Project Office Verification at subassembly level Detector System Handling Carriage Modifications Infrastructure Cryo/Vac controller ESPRESSO ERIS MOONS FOREMOST ….

Nasmyth Architecture Change Request meeting, 17 September 2014 ESO Role(s) II Interactions with ESO Consortium ESO/Customer Consortium ESO/Partner PIESO Project scientist Project Manager ESO Project Responsible System EngineerESO Contracts Dept Project Manager System Engineer ESO WP manager(s) PI NO FORMAL CONNECTION Informal internal communications, meetings, reporting, …. ESO Contact is responsible for contract follow-up But also information “scout”

Nasmyth Architecture Change Request meeting, 17 September 2014 ESO Contact Person Normally Member of INSY (Instrument Systems)  Official channel of communication e.g. in case of RFW, delays, ICD modifications,..  Helps you to find e.g. standards, suppliers, persons at ESO with specific know-how

Nasmyth Architecture Change Request meeting, 17 September 2014 JIRA JIRA EXAMPLE Problem Information exchange/orientation (informal) Create Issue on JIRA Comments and discussion phase Recommendation by CRE review Board Decision by Change Control Board (CCB) Modification/amendment of contractual documents High energy consumption during warmup Longer warmup time? More efficient heaters? Lightweight cold structure? Use more than one SCP? RFW on JIRA Change in spec and verification matrix: warmup 7 days instead of 48 hours Change ICD: LPO will install additional SCP

Nasmyth Architecture Change Request meeting, 17 September 2014 Project Phases SOW Spec ICD ADs LIFE CYCLE DOCUMENT Pre-Phase A: Demonstrate the need for the product and identify a possible concept Phase A: Show the technical and managerial feasibility of the project -> budget, manpower, schedule Phase B: Provide one (or more) realistic technical concepts for the design + confirm Phase A estimates Phase C: Design the product so that it can be manufactured Phase D: Manufacture the components, assemble them and verify the product’s compliance with the specifications Phase E: Bring the product in its operational condition and verify its compliance with the specifications under operational conditions SOW

Nasmyth Architecture Change Request meeting, 17 September 2014 Documents to provide

Nasmyth Architecture Change Request meeting, 17 September 2014 Guidelines for good documents Use document templates (provided by ESO or project office) or ask ESO contacts for examples of “good” documents Write document during the design phase (not just for one single review) -> documents should be “live” documents that grow and mature in the course of the project Know, understand and apply all ADs Avoid where possible writing multiple documents within one discipline Allocate sufficient time for internal review process (pre-review) to check interfaces with other workpackages Reviews can be fun and productive when understood as an opportunity to answer following questions, within the consortium and together with ESO/customer: - what do we want to build and why? - how will we organize our work? - how much will the instrument cost, how long will it take? - which areas of risk (technology, schedule, cost,…) do we see and how do we tackle them? - what will be the performance and how do we verify it (in Europe and on the telescope)? - what are the interfaces with the telescope, how do we install and maintain the instrument? - how do we calibrate and operate the instrument, what will be its impact on telescope operations and data flow ?