glast lat projectisoc cdr, 4 august 2004 document: lat-pr-04500section 3.11 glast large area...

GLAST LAT Project ISOC CDR, 4 August 2004

Document: LAT-PR-04500 Section 3.1 1

GLAST Large Area Telescope:GLAST Large Area Telescope:

Instrument Science Operations CenterInstrument Science Operations CenterCDRCDR

Section 3.1 Section 3.1 Command, Health and Safety DesignCommand, Health and Safety Design

Lori BatorLori BatorONE-SLACONE-SLACISOC Lead EngineerISOC Lead [email protected]@slac.stanford.edu

(650) 926-5352(650) 926-5352

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



TopicsTopics

Overview of CHS CHS System ISOC S/W Architecture CHS Team Internal Coordination External Interfaces Documents Status



Overview of CHSOverview of CHS

Commanding– Generation and validation of commands and command

sequences– Passing commands on to the GSSC (and to MOC for early

orbit operations and contingency commanding) – Verifying these commands were executed – Logging and archiving of all commands – Configuration and control of command plans, procedures

and command database Health and Safety

– Receive and archive Level 0 data from the MOC– Monitor data to ascertain and track the health and safety of

the instrument – Continuous knowledge of the configuration of the LAT– Configuration and control of telemetry database



CHS System CHS System

ITOS used for command, health and safety functions– HK data limit checking– Telemetry and command definition file validation– Command load verification and validation

Other tools (discussed in section 5)– Level 0 receipt and archiving– HK trending– Data transmission– Mission planning and generation of file uploads– Anomaly tracking and notification– Relational database queries for trending and analysis– Configuration management tools



Architecture DriversArchitecture Drivers

Drivers– Minimize V&V burden and total cost– Maintain all science capabilities– Simplify interfaces and allow early testing

Recognized that neither of the previously considered options were particularly attractive– ITOS/Commercial packages don’t accommodate

complexities of science data– Homegrown system doesn’t have heritage

• Most of additional code needed duplicates that in existing packages

– Studied hybrid solutions



ITAR Issues Using ITOSITAR Issues Using ITOS

Workstations running ITOS – Password protected– File access controlled through permissions

User access to ITOS data display and analysis is through a non-ITAR controlled web interface

No impact on collaboration SLAC has developed an official policy on ITAR issues that

specifically addresses the use of ITOS within the ISOC. Availability of non-ITAR web interfaces to the data address all concerns based on Stanford and SLAC openness policies and the use of ITOS within the ISOC is approved.



CHS Team (1/3)CHS Team (1/3)

CHSTeam Lead

InstrumentPhysicist

(part time PVO)

SoftwareEngineer

Operator #1 Operator #2




Weekday, day-time operations– Operator shift coverage

• 5 am to 2 pm to cover MOC shift times on East Coast• 9 am to 6 pm to cover ISOC internal coordination needs

– On-call support• Operators for real-time commanding or anomaly

support• Software engineer for emergency software support• Team Lead and Instrument Physicist for anomalies

Instrument Physicist– Monitor HK data for impact on science– Monitor and maintain configuration of instrument– Schedule instrument commanding




Software Engineer Responsibilities– Maintain ITOS configuration and other CHS tools– Maintain configuration control of command and telemetry

database Operator Responsibilities

– Generate command plans– Interface with MOC and GSSC– Monitor CHS system processes– Monitor real-time contacts during the shift– Monitor automated report generation– Respond to notification of alerts and anomalies– Serve as backup for Software Engineer to address system

problems



Internal Team CoordinationInternal Team Coordination

With PVO – Health and status of LAT– Calibration requirements and scheduling – Weekly schedule of command activities– LAT commanding history– Interpretation of diagnostic data

With FSW – Verification and validation of command plans– Configuration control of state of instrument– Configuration control of FSW– Configuration control of telemetry and command database– Interpretation of diagnostic data

With Science Products– Health and status of LAT– “Quick look” data– Retransmission requests– Interface with GSSC and MOC



External InterfacesExternal Interfaces

Defined by – Operational Data Products ICD (492-MOC-009)– Mission Operations Agreement for Roles and Responsibilities

Element level Operation Agreements GSSC

– Science planning (phase 2)– Commanding (phase 1 and 2)

MOC– Level 0 data– Real-time HK downlink– Mission planning products

• As-flown timeline • Planned TDRSS schedule• Orbit elements

– Database updates– Commanding (phase 0 and contingency)



Ops Data Products: ISOC – MOCOps Data Products: ISOC – MOC

MOC ISOC

Anomaly Reports

As-flown Timeline

Flight Dynamics Products

Integrated Observatory Timeline

Level 0 Data

Data Retransmission Request

LAT Incident Reports

LAT Instrument Loads

LAT Instrument Commands

LAT T&C Database Updates

LAT Instrument Procedures

PDB Updates

LAT Alerts

RT HK Telemetry



Ops Data Products: ISOC – GSSCOps Data Products: ISOC – GSSC

GSSC ISOCLAT Timelines

LAT Instrument Loads

LAT Instrument Commands

Science Plan



DocumentsDocuments

Instrument Operations Handbook (ECD: Oct 2005)– First iteration is for use with I&T – in work

On-orbit Operations Procedures (ECD: L – 6 months) Launch and Early Orbit Operations (ECD: L – 3 months) LAT Telemetry and Command Handbook (ECD: Jan 2005)

– Document created using FSW development tools All documents will have intermediate drafts



Current StatusCurrent Status

ITOS installed on one workstation– Demo in section 5

Other CHS tools exist or are in development – Described in section 5

Technical writer hired to produce ISOC documentation, including CHS documents

Software engineer hired to implement ISOC databases– Telemetry and command descriptions have been defined by

FSW



Backup SlidesBackup Slides



ITOS/Astro RT TradeITOS/Astro RT Trade

PRO CON

Either • Provide basic instrument health and safety functions• Telemetry display• EU conversion• Limit checking and

monitoring• Command and telemetry

database access

• Have learnable interfaces and scripting• AstroRT uses LabView for

display and Perl scripts for automation

• ITOS displays are reportedly easy to create, uses STOL for input

• ITAR issues• Requires use of ITOS- or

AstroRT- specific interfaces and scripting languages

• Limitations on ability to work with science and instrument diagnostic data



ITOS/Astro RT TradeITOS/Astro RT Trade

PRO CON

AstroRT • LAT is using AstroRT for LAT flight software testing

• Commercial product costing $$$ upfront and for support throughout program life

ITOS • MOC and GBM using ITOS

• Able to have ITOS changes made for us

• None that don’t also exist for AstroRT

glast lat projectisoc cdr, 4 august 2004 document: lat-pr-04500section 3.11 glast large area...

Documents

glast lat projectisoc

lat configuration

chs system itos

command database health

itos data display

command sequences

commands configuration

use of itos