Instrument Development Process Hans Dekker Instrument Control Systems

Instrument Development Process Hans Dekker Instrument Control Systems Seminar, 20 October 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 Statement of Work Technical Specification, ICD with Observatory Progress reports and meetings Review meetings (PDR, FDR, IRR, PAE, PAC) Verification at System level ESPRESSO ERIS MOONS FOREMOST …. Consortium <-> ESO/Partner MOU (as other partners in the consortium) Workpackage description Subassembly specification, internal ICD WP progress reports to Consortium Project Office Verification at subassembly level Nasmyth Architecture Change Request meeting, 17 September 2014 Detector System Handling Carriage Modifications Infrastructure Cryo/Vac controller

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

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

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

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 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 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 ? Nasmyth Architecture Change Request meeting, 17 September 2014