Transcript Neyman

NGAO interface control documents:
Christopher Neyman
W. M. Keck Observatory
Keck NGAO PD phase Meeting #6
March 19, 2007
Videoconference
Outline
•
•
•
•
•
•
Interface control process
Tracking changes
How interfaces are reviewed and approved
Interface control documents
Timeline
Discussion
2
Interface requirements are the basis of the IC process
• Interfaces “standard section” of all Keck requirements documents
– Other sections Overall, Optical, Mechanical, Electrical, Safety, etc.
• Use Contour data base and interface “field” on existing requirements
• Build a collection linked to requirements on both sides of interface
– i.e. Optical AO  Optical Instrument
( f/# must be that same on both sides)
• Include explicit “interface” sections and implicit interfaces in other
sections (Optical, Mechanical, Electrical, Safety, Software, etc.)
3
Tracking changes to interface requirements
• “Tags” and email notifications for tracking changes to either “side”
– Neyman (IC lead)
– Design team leads on each side of interface
– Set notifications in Contour for yourself (easy Johansson/Neyman help)
• Already beta tested this process in Contour
– Some setup time required
– Minimal maintenance afterwards
4
Formal review of interfaces after requirements changes
for build to cost
• Verify that requirements on “both sides” are equivalent
• Key that design teams communicate
• Already good across team
– Instruments  AO optical  WFS
– Laser  Multi command sequencer software
– And so forth.
• Should require minimal work if requirements review is successful
• Formal procedure same as requirements review
– see E. Johansson presentation
5
Interface documents organized from Contour reports
•
Organized into about ~20 documents
– First cut in graph at bottom
•
Use MOSFIRE document as template
– Keck standard from Sean Adkins
•
Review for Build to Cost changes
6
Time line for ICD process/review
•
March – Middle April (4/14)
–
–
–
–
•
Teams review all requirements (see E. Johansson presentation)
Finalize Interface review teams
Finalize N2 diagrams and number of ICD documents
Create interface collections with links, tags, and email notifications
Middle April (4/14) – May 1
– Interface teams review interfaces
•
•
(Design team leads (2) + Sys. Eng. team (1))
May
– Produce Draft ICD documents from Contour reports
7
Discussion
• Any questions?
8