1 / 20

GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 8

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 8 Management, Cost, Schedule & Risk William Craig Stanford Linear Accelerator Center ISOC Subsystem Manager bcraig@slac.stanford.edu. Topics. Organization/Staff

ilyssa
Download Presentation

GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 8

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gamma-ray Large Area Space Telescope GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 8 Management, Cost, Schedule & Risk William Craig Stanford Linear Accelerator Center ISOC Subsystem Manager bcraig@slac.stanford.edu

  2. Topics • Organization/Staff • Management Process • Requirements Traceability • Document Status • Test Philosophy • Procurement Plans • Schedule • Issues and Concerns

  3. Ken Lehtonen Ground System/Ops Manager GSFC Howard Dew Ground Sys Engineer GSFC Dave Harmon QA Engineer Tybrin Jay Heberle USN Support USN Beth Pumphrey Test Lead GSFC Ross Cox/ASRC Ernest Canevari/ASRC Bruce Wagner/ITMI Leslie Ambrose MOMS/NENS Support GSFC Bob Sodano Mission Director GSFC Stan Rubin NISN Support GSFC Ken Lewis Observatory Ops Lead Spectrum Astro Mark Woodard FD Engineer GSFC Dennis Small MOC Lead GSFC Bill Craig LAT IOC/LOF Lead SLAC Richard Dubois LAT IOC/SAS Lead SLAC Bill Paciesas GBM IOC Lead UAH Jay Norris GSSC Lead GSFC Scott Barthelmy GCN Lead GSFC Robert Preece/UAH Implementation Lead Doug Spiegel/Omitron MOC Manager Michael Corcoran HEASARC GLAST Lead GSFC John Nagy/Omitron FOT Lead Ground System/Ops Organization

  4. ISOC Elements & Functions

  5. Staffing profile • The staffing profile for the ISOC has been developed and the budget for activities agreed upon with SLAC management. • See chart on next page for staffing by function • The large jump in FY05 reflects the CD4 milestone (delivery to NRL for environmental test) and the end of the construction phase of the project; at this point most LAT staff (e.g. SAS, FSW etc) are in the ISOC. • We have hired a software engineer (Steve Culp) who has developed an architecture for the ISOC operations software. • We have hired a software engineer (Jim Lemon) who will implement the ISOC databases • We have hired a technical writer (Lee Steele) who will develop the remaining ISOC documents including the Operations handbook. • We will need additional software developers/physicists later in CY 04. We have no current unfilled slots.

  6. ISOC Staffing Plan Plan matches actuals through July 04

  7. ISOC Management Process • The ISOC has established the following meetings in support of ISOC development and coordination: • Weekly ISOC staff meeting to track schedule, RFAs and any coordination issues. • Weekly ISOC-FSW coordination meeting, attended by ISOC staff and the FSW manager, to work issues of joint importance and ensure that jointly held requirements are executed in the most efficient manner. • Bi-weekly meetings between ISOC manager and GLAST project scientist to work overall science planning and mission issues. • Database development meetings as required. • Regular interaction with I&T including shared personnel. • Participate in: • Weekly GOWG meeting with GSFC • Address ICDs, timeline, and operation issues • Weekly FSW and I&T working group meetings • Coordinate script development and test activities

  8. Requirements Traceability • Formal process established and in-place for requirement traceability, flow down and decomposition for the LAT ISOC • Established ICDs in placed with GLAST-MOC and GSSC

  9. Document Status

  10. Document Status (2)

  11. Test Philosophy • Schedule constructed to test as early as possible • LAT testbed allows frequent and meaningful tests while instrument is being assembled • Frequent demonstrations and simulations precede major software releases. • Six end to end tests during Observatory I&T to provide confidence in final major release of software.

  12. Summary of ISOC Software Capabilitiesfor GRTs & ETEs

  13. ISOC Development Schedule Phase / Milestone Aug-04 Sep-04 Oct-04 Nov-04 Dec-04 Jan-05 Feb-05 Mar-05 Apr-05 May-05 Jun-05 Jul-05 Aug-05 Sep-05 Oct-05 Nov-05 Dec-05 Jan-06 Feb-06 Mar-06 Apr-06 May-06 Jun-06 Jul-06 Aug-06 Sep-06 Oct-06 Nov-06 Dec-06 Jan-07 Feb-07 Mar-07 ISOC CDR ITOS setup/configuration ISOC Verif. with Test Bed Diagnostic Tool Dev Mission Planning Dev DB/Web/E-logbook Dev Plotting/Trending Dev ISOC Demos ISOC Simulation Testing ISOC SW Releases 1 4 2 3 Ground Readiness Tests 3 4 7 2 6 5 End-to-End Tests 6 5 4 3 1 2 Environmental tests at NRL ISOC testing at NRL ISOC takes over LAT operation ISOC used to I/F with LAT (front-door only) Mission Simulations Launch SW Dev Slack Times

  14. ISOC Software Release Schedule • New software architecture in place, centralizing all software releases; eliminating the various separate software release schedule as in the PDR schedule • The schedule has been coordinated with GSFC Ground System plans • ISOC Software Release 1 (April 1, 2005) • Support Ground Readiness Test (GRT) 2 and 3 • ISOC Software Release 2 (August 15, 2005) • Support GRT 4 and 5 • ISOC Software Release 3 (December 15, 2005) • Support End-to-End 1, ETE 2, ETE 3, GRT 6, GRT 7, and Mission Sim • ISOC Software Release 4 (July 25, 2006) • Support remaining ETE’s 4, 5, and 6

  15. ISOC Cost Profile The ISOC budget presented here is completely ‘off project’ and is primarily funded by SLAC’s research division.

  16. Procurement plans • The large disk and CPU farms needed for pipeline storage and processing are supplied by SCS. • The handful of ISOC workstations will be procured in phases but will all be in place for the final software release • Third party software is largely in place already • STK will be purchased in CY2004 • Final build/buy decisions on other tools by November ’04. • No issues foreseen with H/W or purchased S/W.

  17. ISOC Risk Status

  18. RFA 3 – ISOC Risk Status

  19. Issues and Concerns • Frontloaded software support needed. • Need to limit hires to account for expected transfers from other subsystems. • Database architecture not as well developed as we would like • Need to deliver I&T databases soon while retaining an overall structure that makes sense for the ISOC • Requirement completeness, • late start adds risk of missing requirements • Many software elements need to interoperate smoothly • Early testing reduces problem, and certainly easier than writing the code anew

  20. Summary • Great effort from ISOC staff over past 3 months to respond to PDR, devise and firm up an architecture for the ISOC. • Help from GSFC (particularly Canevari, Teter & Greer) has made a large impact and significantly improved our approach • Although issues remain we are poised to build a system that meets all requirements while meeting schedule.

More Related