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

GLAST LAT Project ISOC CDR August 4, 2004

LAT-PR-04500 Section 8 Management 1

GLAST Large Area Telescope:GLAST Large Area Telescope:

Instrument Science Operations Center Instrument Science Operations Center CDRCDR

Section 8 Management, Cost, Schedule & Risk

William CraigStanford Linear Accelerator CenterISOC Subsystem Manager

[email protected]

Gamma-ray Large Gamma-ray Large Area Space Area Space TelescopeTelescope



TopicsTopics

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



Ground System/Ops OrganizationGround System/Ops Organization

Ken LewisObservatory Ops Lead

Spectrum Astro

Doug Spiegel/OmitronMOC Manager

John Nagy/OmitronFOT Lead

Beth PumphreyTest Lead

GSFC

Dennis SmallMOC Lead

GSFC

Bill CraigLAT IOC/LOF Lead

SLAC

Richard DuboisLAT IOC/SAS Lead

SLAC

Scott BarthelmyGCN Lead

GSFC

Jay NorrisGSSC Lead

GSFC

Michael CorcoranHEASARC GLAST Lead

GSFC

Ken LehtonenGround System/Ops Manager

GSFC

Leslie AmbroseMOMS/NENS Support

GSFC

Jay HeberleUSN Support

USN

Stan RubinNISN Support

GSFC

Ross Cox/ASRCErnest Canevari/ASRC

Bruce Wagner/ITMI

Howard Dew Ground Sys Engineer

GSFC

Bob SodanoMission Director

GSFC

Mark WoodardFD Engineer

GSFC

Robert Preece/UAHImplementation Lead

Bill PaciesasGBM IOC Lead

UAH

Dave HarmonQA Engineer

Tybrin



ISOC Elements & FunctionsISOC Elements & Functions

ISOC Manager

4.1.B.10Command, H&S

4.1.B.11 FSW

4.1.B.12 Performance V&O

4.1.B.13Science Products

4.1.B.14 Science Analysis

Tools

Commanding

Health & Safety

Configuration

Thermal Control

Trigger

Filter

Testbed

Calibration

PerformanceTrending

Standard SourceMonitoring

IRF Generation

Level 1CRs, gammas,

diagnostics

Level 2Transients, GRBs

Pipeline Server

Simulation

Calibration

Reconstruction &Event Classif.

Transient SourceAnalysis

Database



Staffing profileStaffing 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.



ISOC Staffing PlanISOC Staffing Plan

ISOC Staffing by Job Function

0

10

20

30

40

50

60

1 5 9 13 17 21 25 29 33 37 41 45 49 53

Months since March 04

FTE

SupportScientistTechnicianSoftwareEngineeringManagement

Plan matches actuals through July 04



ISOC Management ProcessISOC 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



Requirements TraceabilityRequirements 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

Mission System Specification

433-SPEC-0001

Science Requirements

Document433-SRD-0001

LAT-SC Interface Requirements

Document433-IRD-0001

LAT Performance Specification

LAT-SS-00010

LAT Environmental Specification

LAT-SS-00778

LAT ISOC Performance Specification

LAT-SS-00015

ACD Subsystem Specification

LAT-SS-00016

TKR Subsystem Specification

LAT-SS-00017

CAL Subsystem Specification

LAT-SS-00018

Trigger & Dataflow Subsystem

SpecificationLAT-SS-00019

SASSubsystem


ISOCSubsystem


PowerSubsystem


MechanicalSubsystem


Mis

sion

LAT

LAT

Subs

yste

m

Science Rqmts

Mission Rqmts

Interface Rqmts

Interface Rqmts

TCS Performance Specification

LAT-SS-00715

Operations Data Products (ICD)

LAT-SC Interface Control

Documents

Ground System Requirement Documents

433-RQMT-0006

Science Data Products (ICD)



Document StatusDocument Status

Document Number

Last Revision Date

Estimated Completion Date Author Title

MD-2513 6/23/2004 8/15/2004 L. Bator Lat ISOC Verification and Validation Plan

MD-04443 7/30/2004 7/30/2004W. Craig, D. Lung

LAT Instrument Science Operation Center Management and Development Plan

SS-00015 7/22/2004L. Bator, J. Martin

LAT ISOC Performance Specification-Level II(B) Specification

SS-00021 7/14/2004 7/30/2004

L. Bator, W. Craig, S. Digel, D. Lung, J. Martin

LAT ISOC Subsystem Specification Level III Specification

SS-01378 7/30/2004 7/30/2004

L. Bator, W. Craig, S. Digel, D. Lung, J. Martin LAT Operations Plan

SS-01783 Draft 11/1/2004 L. Bator LAT Operations Facility Level 4 specificationNot assigned 9/15/2004 S. Culp

ISOC Ground Software and Operations Tools Description

Not assigned 4/15/2005 J. Martin ISOC Test Plan



Document Status (2)Document Status (2)

Not assigned 10/1/2005 L. Bator Instrument Operations Handbook

Not assigned 11/1/2004R. Cameron ISOC Team Coordination Plan

Not assigned 2/15/2004 W. Craig ISOC/I&T Transition Document

Not assigned 9/1/2004 S. Culp ISOC Configuration Management Plan

Not assigned 9/1/2006 L. Bator On-orbit Operations Procedures

Not assigned 12/1/2006 L. Bator Launch and Early Orbit Operations

Not assigned 1/15/2005 FSW Telemetry and Command Handbook

Document Number

Last Revision Date

Estimated Completion Date Author Title



Test PhilosophyTest 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.



Summary of ISOC Software CapabilitiesSummary of ISOC Software Capabilitiesfor GRTs & ETEsfor GRTs & ETEs

Date What Release Required ISOC capabilities15-Apr-05 GRT 2 ISOC 1

(1 Apr 05)receive real-time HK data from MOC, provide basic LAT P&S (Planning & Scheduling)

15-Jun-05 GRT 3 “ level 0 data processing on science data, IOC processes science level 0 data into level 1 products

1-Sep-05 GRT 4 ISOC 2 (15 Aug 05)

receive level 0 data from MOC

15-Nov-05 GRT 5 “ provide level 1 and 2 data products to GSSC, provide more complex LAT P&S, provide LAT file uploads to GSSC, provide simulated science data

11-Feb-06 ETE 1 ISOC 3(15 Dec 05)

provide Level 1 data products to GSSC, receive Level 0 files from MOC (post-test)

15-Feb-06 GRT 6 “ contingencies added

15-Apr-06 ETE 2 “ provide instrument commands and file loads, support memory dumps of instrument

1-May-06 GRT 7 “ clean-up and regression tests

1-May-06 Mission Sims “ full ISOC capabilities to support Mission Sims (from May 2006 through launch)

15-Jun-06 ETE 3 “ support basic observatory operations

25-Aug-06 ETE 4 “ instrument turn on

14-Oct-06 ETE 5 “ regression test and contingencies

1-Feb-07 ETE 6 “ final ETE at launch facility



SW Dev Slack Times

ISOC Development ScheduleISOC Development Schedule

LaunchMission Simulations

ISOC testing at NRL

Environmental tests at NRL

ISOC SW ReleasesISOC Simulation Testing

ISOC Demos

ISOC Verif. with Test Bed

Plotting/Trending DevDB/Web/E-logbook DevMission Planning DevDiagnostic Tool Dev

End-to-End Tests

Ground Readiness Tests

ISOC CDR

Mar-07

Feb-07

Jan-07

Dec-06

Nov-06

Oct-06

Sep-06

Aug-06

Jul-06

Jun-06

May-06

Apr-06

Mar-06

Feb-06

Jan-06

Dec-05

Nov-05

Oct-05

Sep-05

Aug-05

Jul-05

Jun-05

May-05

Apr-05

Mar-05

Feb-05

Jan-05

Dec-04

Nov-04

Oct-04

Sep-04Phase / Milestone

Aug-04

2 3 4 5 6 7

ITOS setup/configuration

1 2 3 4 5 6

1 32

ISOC takes over LAT operationISOC used to I/F with LAT (front-door only)

4



ISOC Software Release ScheduleISOC 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



ISOC Cost ProfileISOC Cost Profile

FY04 FY05 FY06 FY07 FY08ISOC Management 158.11 557.18 554.94 638.92 667.36

CHS Team 405.99 1450.14 1484.14 1536.09 1186.11FSW Team 0.00 346.68 1240.70 1284.12 906.47PVO Team 83.90 652.51 1264.75 1309.02 1222.87SDP Team 12.63 467.00 703.94 728.58 754.08SAS Team 364.49 1483.90 2095.21 1839.66 1825.76SAC Team 0.00 270.17 1716.84 1979.31 2252.82

Total (Functional Units) 1025.12 4957.42 7343.68 7336.40 6562.65Total (With SAC) 1025.12 5227.58 9060.52 9315.71 8815.46

The ISOC budget presented here is completely ‘off project’ and is primarily funded by SLAC’s research

division.



Procurement plansProcurement 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.



ISOC Risk StatusISOC Risk Status

Number Date Rank Originator Description Mitigation

ISOC-0001 5/15/04 1 B. Craig ISOC lacks accepted architecture and plan for software implementation.

Trade study between possible front ends to be completed by 6/15/04. Hires into s/w architecture position. Successful CDR retires risk

ISOC-0002 5/15/04 3 B. Craig No response to PDR RFAs

Schedule and track RFA’s weekly. 3 remain as of 8/02

ISOC-0003 5/17/04 2 B. Craig Inadequate staffing plan for ISOC.

Draft staffing plan complete. Culp, Lemon, Steele hired, S/W developers needed in Sep/Oct

ISOC-0004 5/21/04 4 B. Craig No facility location identified for ISOC

Long-term solution identified, short term space to be requested from SLAC management.



RFA 3 – ISOC Risk StatusRFA 3 – ISOC Risk Status

Number Date Rank Originator Description Mitigation

ISOC-0005 5/21/04 2 B. Craig No requirements levied on I&T and Flt S/W subsystems

Mechanism in place with I&T and FSW Final disposition after joint requirements review.

ISOC-0006 5/21/04 1 B. Craig ISOC will be unable to hold schedule due to staffing delays and unscoped work

Definition of work plan follows architecture development. Additional support supplied as requested but need to balance new hires vs transfers from other subsystems.



Issues and ConcernsIssues 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



SummarySummary

• 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.

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

Documents

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