Ex AOC Systems Engineering Ex AOC MTR October

Ex. AOC Systems Engineering Ex. AOC MTR October 21 -22, 2004 HIA (Victoria) Les Saddlemyer

Outline Gemini style ICD overview Ex. AOC FPRD Co. DR documentation outline Test & Integration Plan

ICDs (Interface Control Documents) § Provides definition of how entities will interface; agreed upon by teams on both sides of ‘connection’ and system engineering. § Optical § Mechanical § Electrical § Software § Services § Special (e. g. dedicated network, shared memory)

Gemini ICDs Hierarchical 1. 5. 3 Cass. Rotator assembly ISS 1. 9 Science Instruments 1. 9. d GMOS 1. 9. x Ex. AOC (If given AURA’s blessing? !) 1. 9. x. 1 Ex. AOC AO module 1. 9. x. 2 “ Coronagraph module 1. 9. x. 3 “ Science Instrument 1. 9. x. 4 “ Calibration Module N 2 diagram -> 1. 9. x. 1/1. 9. x. 4 “Ex. AOC AO to Calibration Module ICD”

ICD No. ICDs: “General” 1 a, /1 b/1 c ICD Title The System Command Interface The Baseline Attribute/Value Interface Baseline DHS Interface 2 Systems Status and Alarm Interfaces 3 5 Bulk Data Transfer Wavefront Sensing Information Interface 7 a ICS Subsystem Interfaces 9 EPICS Time Bus Driver 10 10 EPICS Synchro Bus Driver 12 Interlock System 16 The Parameter Definition Format G 0013 Gemini Environmental Requirements G 0014 Gemini Observatory Optomechanical Coordinate Systems G 0015 Gemini Facility Handling Equipment and Procedures for Instrumentation

1. 9 ICDs: N 2 1. 1. 1/1. 9 1. 6/1. 9 Science Instruments Interface Control Documents Overview and Guide Telescope Structure to Science Instruments Interface Control Document A&G System to Science Instruments 1. 1. 11/1. 9 Science Instrument to Telescope Control System 1. 1. 13/1. 9 Interlock System to Science Instruments Interface Control Document 1. 4. 4/1. 9 SCS to Science Instrument Interface 1. 9/1. 10 Science Instruments to On Instrument WFS Science and facility instruments to facility handling equipment interface control document 1. 9/2. 7 1. 9/3. 1 1. 9. x/3. 1 1. 9/3. 2 1. 9. x/3. 2 Science Instrument to Observatory Control System Ex. AOC to Observatory Control System Science Instrument to Data Handling System Ex. AOC to Data Handling System

ICD: Ex. AOC internal (so far …) ICD 1. 9. x ICD Overview and Guide ICD 1. 9. x. 1/1. 9. x. 2 AO to Coronagraph ICD 1. 9. x. 2/1. 9. x. 3 Coronagraph to Science Inst. ICD 1. 9. x. 2/1. 9. x. 4 Coronagraph to Cal. Module ICD 1. 9. x. 1/1. 9. x. 4 AO to Cal. Module

FPRD (Functional and Performance Requirements Document) Functional: what the instrument does and Performance: how well it does it. -> Translation between science requirements (OCDD) and technical requirements, to which designs are to be based. § High level specifications (e. g. “… shall achieve a contrast ratio of …”) § Obvious details (e. g. “Ex. AOC will accept and use the oftical feed of the telescope …”) § Gritty details (e. g. “… will use fasteners sized for a safe working load …”).

Ex. AOC FPRD “Every feature of Ex. AOC should be traceable to a requirement in this document …”

Co. DR Documentation (Conceptual Design Review) Four main sections, with contributions by everyone. Each section has a ‘champion’. Science Technical Management Appendices (James Graham) (Les Saddlemyer) (David Palmer) (Les Saddlemyer) KEY: Lots of review by everyone, including crossdiscipline.

Co. DR: Science Section (James Graham) 1. Overview 2. Science Drivers 3. Simulations

Co. DR: Technical Section (Les Saddlemyer) 1. 2. 3. 4. 5. 6. Overview (BM) System Design (BM) AO module (BM) Coronagraph Module (BO) Science Instrument(s) (RD & JL) Calibration Module (KW) 7. Mechanical Design (CL) 8. Control Systems (WD) 9. Control Software (JD) 10. Optical Issues (BB) 11. Test, Integration and Commissioning (BM & LS) 12. Trade Studies (LS)

CODR: Management Section (Dave Palmer) 1. Project Definition 2. Project Organization 3. Work Break-Down Structure 4. Schedule 5. Resources 6. Project Teams 7. Track Records

CODR: Appendices (Les Saddlemyer) Supporting documents, studies, references etc. 1. OCDD 2. FPRD 3. Test, Integration and Commissioning Plan 4. Trade Studies 5. Simulation results 6. Etc. 7. Etc. 8. Etc.

Test, Integration and Commissioning Plan (TI&C) 1. Module (AO, coronagraph, science instrument(s), calibration module and SW) developed at separate Institutes. 1. Requires interface simulators (e. g. artificial stars and cameras. Nice if can be installed on assembled Ex. AOC for testing/debugging). 2. Requirement for components control SW and HW (duplicates) to be delivered to each Institute. 3. Acceptance tests before shipment. 4. Re-test after shipping to I&T location

TI&C Plan 2. Integrate in single location (UCSC? ), one major module at a time. Module team members follow each to T&I. 1. Major structure (incl. control SW & HW) 2. Coronagraph 3. AO 4. Calibration Module 5. Science Camera

TI&C Plan 3. Full-up system: 1. Reliability testing 2. Flexure testing 3. Performance/characterizing 4. Re-work 5. Gemini acceptance testing

TI&C Plan 4. Commissioning 1. Shipping 2. Re-assemble 3. Post-ship verification (summit or base? ) 4. Integrate w/Gemini systems (summit) 5. Daytime testing/flexure/calibration 6. Nighttime commissioning

Conclusion • Documentation, documentation, … • Guides and well-defined interfaces exist • Keep in mind ‘big picture’ when working on major modules