1. Encouraging “System Level” Thinking Christopher Neyman, Erik Johansson, David Le Mignant W. M. Keck Observatory Viswa Velur California Institute of Technology Keck NGAO Team Meeting #10 September 17, 2007 012 Robison Laboratory Top Observing Sequencer d-NIRI Inst. Sequenc er NIR Inst. Sequenc er Etc AO System Sequencer Laser System Sequencer Telescope & Acquisition Sequencer Data Sequencer Vis. Inst. Sequenc er Laser Safety & LTCS Sequencer Atmospheric Tools Sequencer Simulation and PSF estimation Pre- observing tools DRPs, data analysis and display RTC Non- RTC Observi ng tools Calibrati ons tools Health Monitoring and System Optimization Etc.. RTC Non- RTC Etc..

2. 2 Cannot lose track of interaction between systems for successful NGAO design Examples: The electrical/electronics and SW to support all the RTC input (sensor) and output (mirror) devices do not seem to be captured in any WBS – Erik Johansson (Email 9/12/2007) Four people all making the same “system block diagram” with unique perspectives and purposes (David, Erik, Chris, Viswa) –See next slide Interfaces not easily captured in standard plan

3. 3 Draft system block diagrams from unique perspectives ( Examples: ignore details for now ) Top Observing Sequencer d-NIRI Inst. Sequencer NIR Inst. Sequencer Etc AO System Sequencer Laser System Sequencer Telescope & Acquisition Sequencer Data Sequencer Vis. Inst. Sequencer Laser Safety & LTCS Sequencer Atmospheric Tools Sequencer Simulation and PSF estimation Pre- observing tools DRPs, data analysis and display RTC Non- RTC Observin g tools Calibratio ns tools Health Monitoring and System Optimization Etc.. RTC Non- RTC Etc.. Erik’s Viswa’s David’s Chris’s

4. 4 We propose an interdisciplinary “interface” team No one person has all the skills to produce a complete picture Synergy from combination of different perspectives –Sum is more than it’s parts Need exchange of information on regular basis Could continue to do this organically (our current model) Alternative is a designated team –Responsible for defining interfaces But can’t just leave after interfaces defined –System integration Making sure it all works

5. 5 We propose an interdisciplinary “interface” team People with multiple skills and varied experiences (more “Xs” is better) Team composed of key disciplines: Science Science Operations Instrument Controls Lasers Electronics Optics Mechanical Analysis Is this a productive model?