Transcript Operations Planning and Interfaces

GLAST LAT Project
ISOC CDR, 4 August 2004
GLAST Large Area Telescope:
Gamma-ray Large
Area Space
Telescope
Instrument Science Operations Center
CDR
Section 4.1
Operations Planning & Interfaces
Lori Bator
ONE-SLAC
[email protected]
650-926-5352
Seth Digel
SLAC
[email protected]
650-723-7862
Document: LAT-PR-04500
Section 4.1
1
GLAST LAT Project
ISOC CDR, 4 August 2004
LAT Operations Planning and Command Process
Mission Operations
Center
(MOC)
GLAST Science
Support Center
(GSSC)
Final Science Timeline
Science Plan
(Phase 2)
TDRSS Schedule
Engineering Plan
Mission Timeline
Preliminary and Final
Science Timelines
Command Plan
ISOC
Command Plan
ATS Commands
Mission
Planning
Operations
Plan
Command
Plan Build &
Review
Verification &
Validation
File Uploads
Command Procedures
Feedback
Document: LAT-PR-04500
Section 4.1
2
GLAST LAT Project
ISOC CDR, 4 August 2004
Definitions



Science Plan – Observatory activities
– Phase 1: ISOC maintains LAT science plan
– Phase 2: Plan maintained by GSSC [Phase 2] and includes
guest investigator proposals, coordinated with GBM and
LAT. GSSC assists in overall science plan evaluation and
will manage the proposal process.
Operations Plan – Derived from evaluated performance of the
LAT, the as-flown timeline, the science plan [for Phases 1 and
2], and calibration needs
Command Plan – The translation of the operations plan into
ATS commands, file uploads and real-time operations
procedures for one week of operating the LAT. Tables of
parameter values and flight software are also part of the
command plan.
Document: LAT-PR-04500
Section 4.1
3
GLAST LAT Project
ISOC CDR, 4 August 2004
Operations Planning
Seth Digel
Document: LAT-PR-04500
Section 4.1
4
GLAST LAT Project
ISOC CDR, 4 August 2004
Operations Planning in the ISOC

Describing what goes on in this
box
Mission Operations
Center
(MOC)
Final Science Timeline
GLAST Science
Support Center
(GSSC)
Science Plan
(Phase 2)
TDRSS Schedule
Engineering Plan
Mission Timeline
Preliminary and Final
Science Timelines
Command Plan
ISOC
Command Plan
ATS Commands
Mission
Planning
Operations
Plan
Command
Plan Build &
Review
File Uploads
Verification &
Validation
Command Procedures
Feedback
From the Operations Concept Document (LAT-SS-01378)
Document: LAT-PR-04500
Section 4.1
5
GLAST LAT Project
ISOC CDR, 4 August 2004
ISOC Organization

All ISOC teams are
involved in this activity;
input can also come from
outside the ISOC) – CHS
is the lead
ISOC Manager
Databases
4.1.B.10
Command, H&S
4.1.B.11
FSW
4.1.B.12
Performance V&O
4.1.B.13
Science Products
4.1.B.14
Science Analysis
Software
Commanding
Thermal Control
Calibration
Level 1
CRs, gammas,
diagnostics
Simulation
Health & Safety
Trigger
Performance
Trending
Level 2
Transients, GRBs
Calibration
Configuration
Filter
Standard Source
Monitoring
Pipeline Server
Reconstruction &
Event Classif.
Testbed
IRF Generation
Document: LAT-PR-04500
Transient Source
Analysis
Section 4.1
6
GLAST LAT Project
ISOC CDR, 4 August 2004
Operations Plan





Monthly plan of LAT operations based on the overall science plan
Science activities per se are not typically the driver
– For a scanning sky survey (Phase 1 and likely also most of Phase
2), the ‘science activities’ are the same all the time
– The science plan in Phase 2 will be developed by the GSSC
The subsystems have calibration needs that occasionally will require
special observing modes (or scheduling of more than the usual
number of TDRS contacts)
Most calibration data taking will not require specific orientations for
GLAST
– Occasional exceptions will be, e.g., pointed observation of
‘standard candle’ celestial sources or possibly scans of the Earth
limb and the nadir to characterize the albedo background
So, in general the operations plan may have no impact on the pointing
of GLAST, and will be irrelevant in development of the contact
schedule for TDRSS
Document: LAT-PR-04500
Section 4.1
7
GLAST LAT Project
ISOC CDR, 4 August 2004
Influences on the Operations Plan





[PVO] The calibration requirements of the subsystems,
detailed in LAT-MD-00446 define the basic ‘recurrence time’ of
the calibrations
[CHS] The as-flown timeline is monitored to determine whether
requested calibration observations were made. [N.B. Again,
many of the calibration observations can be made without
interrupting science observations.]
[FSW] Approved software updates and table loads need to be
scheduled
[SP] Routine processing of calibration data - not interpretation
of results, but supports PVO
[SAS] Also supports PVO with, e.g., simulation software for the
LAT
Document: LAT-PR-04500
Section 4.1
8
GLAST LAT Project
ISOC CDR, 4 August 2004
Appropriate Oversight



The organization of the scientific activities of the LAT
collaboration outside of the ISOC is still being defined
– This will be a major subject of the next collaboration
meeting, Sept. 27-29 at SLAC
What seems likely right now: A committee with collaboration
and probably Project Scientist representation will oversee the
science-related activities of the ISOC, i.e., will serve as the
interface between science and operations
Examples of the science-operations interface:
– Acceptance of updated algorithms for the LAT trigger or
event filtering (on board or on the ground)
– Definitions of conditions when the LAT will autonomously
request a repointed observation
Document: LAT-PR-04500
Section 4.1
9
GLAST LAT Project
ISOC CDR, 4 August 2004
Regarding Phases 0 & 1


Phase 0 – turn on and checkout of the LAT – a special case in
almost every respect, although the internal interfaces in the
ISOC will of course remain the same
– Phase 0 does not have a science plan, but calibration
activities will be intense
Phase 1 – the scanning sky survey year – For this year, the
ISOC will also need to define the science plan
– Basically this will mean optimizing the rocking strategy, and
of course assessing/mitigating the impact on the sky
survey from any pointed observations or unusual
instrument modes required for calibration data taking
Document: LAT-PR-04500
Section 4.1
10
GLAST LAT Project
ISOC CDR, 4 August 2004
Command Plan Generation
Lori Bator
Document: LAT-PR-04500
Section 4.1
11
GLAST LAT Project
ISOC CDR, 4 August 2004
Command Plan Generation in the ISOC

Describing what goes on in
these boxes
Mission Operations
Center
(MOC)
Final Science Timeline
GLAST Science
Support Center
(GSSC)
Science Plan
(Phase 2)
TDRSS Schedule
Engineering Plan
Mission Timeline
Preliminary and Final
Science Timelines
Command Plan
ISOC
Command Plan
ATS Commands
Mission
Planning
Operations
Plan
Command
Plan Build &
Review
File Uploads
Verification &
Validation
Command Procedures
Feedback
From the Operations Concept Document (LAT-SS-01378)
Document: LAT-PR-04500
Section 4.1
12
GLAST LAT Project
ISOC CDR, 4 August 2004
Command Plan





Generated by CHS team
Contains all LAT commanding requirements to fulfill a oneweek period of the Operations Plan
– ATS Load commands
– File loads
• Table uploads, configuration changes, FSW loads
– Command procedures
• Commands requested to be sent in real-time
Verify and validate command plan elements on testbed
Sent to GSSC about 2 weeks prior to upload
– GSSC incorporates command plan elements into
Preliminary ScienceTimeline
Changes that don’t impact the observing schedule or TDRS
contacts can be sent up to 4 days prior to upload in time for
GSSC to generate Final Science Timeline
Document: LAT-PR-04500
Section 4.1
13
GLAST LAT Project
ISOC CDR, 4 August 2004
Planning for One Week’s Activities
Monday
Tuesday
July 30
Wednesday
31
Thursday
Friday
August 1
2
GSSC Sends
Preliminary
Activity Timeline
to MOC
6
7
8
Sunday
4
5
11
12
18
19
MOC Requests
TDRSS Contacts
for the Week
9
10
ISOC Sends
Command Plan to
GSSC
ISOC Generates
Command Plan
13
Saturday
3
14
15
16
17
Deadline for
ISOC to Send
Changes* to
Week
20
21
GSSC Sends
Final Activity
Timeline to MOC
27
22
MOC Uploads
ATS
28
23
24
25
26
31
September 1
2
ATS Goes Active
29
30
*Minor changes that don’t affect observing
schedule or TDRS contacts
Document: LAT-PR-04500
Section 4.1
14
GLAST LAT Project
ISOC CDR, 4 August 2004
Typical Month of Planning
Monday
Tuesday
July 30
Wednesday
31
Thursday
August 1
ISOC Begins
Generating
Command Plan
for Week C
Friday
2
WEEK A
ATS Goes Active
6
7
8
ISOC Begins
Generating
Command Plan
for Week D
13
WEEK B
ATS Goes Active
14
15
ISOC Begins
Generating
Command Plan
for Week E
20
ISOC Begins
Generating
Command Plan
for Week G
Document: LAT-PR-04500
16
WEEK C
ATS Goes Active
21
22
ISOC Begins
Generating
Command Plan
for Week F
27
9
23
WEEK D
ATS Goes Active
28
29
30
WEEK E
ATS Goes Active
Saturday
3
Sunday
4
Review
Command Plans
for Week B & C
Send Command
Plan for Week C
Deadline for
ISOC to Send
Changes for
Week B
10
11
Review
Command Plans
for Week C & D
Send Command
Plan for Week D
12
Deadline for
ISOC to Send
Changes for
Week C
17
18
Review
Command Plans
for Week D & E
Send Command
Plan for Week E
19
Deadline for
ISOC to Send
Changes for
Week D
24
25
Review
Command Plans
for Week E & F
Send Command
Plan for Week F
31
5
26
Deadline for
ISOC to Send
Changes for
Week E
September 1
Review
Command Plans
for Week F & G
Send Command
Plan for Week G
Section 4.1
2
Deadline for
ISOC to Send
Changes for
Week F
15
GLAST LAT Project
ISOC CDR, 4 August 2004
Status


Continuing to finalize details of commanding process with
GSSC and MOC
– Weekly GOWG meetings
– Ops TIMs
– Operations Data Products ICD (492-MOC-009)
– Operations Agreement
Documented in ISOC Operations Plan (LAT-SS-01378)
Document: LAT-PR-04500
Section 4.1
16