Presentation is loading. Please wait.

Presentation is loading. Please wait.

GLAST LAT Project ISOC 5/17/2004 – Seth Digel1 ISOC Lessons Learned RFA09 Issue –No writeup on lessons learned from visits to other instrument/mission.

Similar presentations


Presentation on theme: "GLAST LAT Project ISOC 5/17/2004 – Seth Digel1 ISOC Lessons Learned RFA09 Issue –No writeup on lessons learned from visits to other instrument/mission."— Presentation transcript:

1 GLAST LAT Project ISOC 5/17/2004 – Seth Digel1 ISOC Lessons Learned RFA09 Issue –No writeup on lessons learned from visits to other instrument/mission operations center Resolution –Members of the ad hoc planning group for the definition of the LAT IOC (now ISOC) made visits to the operations centers for GP- B (launched April, 2004; Stanford Univ., Tom Langenstein & Brett Stroozas), RHESSI (launched 2002; Berkeley Space Sciences Lab., David Smith & Manfred Bester), and Chandra (launched in 1999; MIT & Harvard-Smithsonian Center for Astrophysics, Dan Schwartz & Paul Plucinsky) –Each of these operations centers integrates mission operations with science (instrument) operations, and so they are not directly comparable to the ISOC in terms of complexity or staffing. (The operations center for RHESSI includes the ground station.) LAT ISOC can learn from others but there are no direct models.

2 GLAST LAT Project ISOC 5/17/2004 – Seth Digel2 Lessons Learned –The science operations center for GP-B is co-located with the science team at Stanford. The GP-B data also will be distributed widely to collaborating institutions, but the co- location at Stanford was deliberate to maximize the interaction with the SOC on data issues. Colocation important to maximize science. –The staffing for RHESSI operations is especially spare. The facility itself is also used to run operations for FAST and CHIPS and the routine operations, like scheduling of contacts and pipeline processing, are automated. Testbeds (simulators for the instrument computers) are maintained, and have been found vital for understanding anomalies as well as for testing flight software updates. Testbeds important for flight software updates.

3 GLAST LAT Project ISOC 5/17/2004 – Seth Digel3 Lessons Learned –The Chandra Operations Control Center has a room with about 4 consoles for the ACIS instrument team to monitor and command the instruments. The ACIS team has developed an impressive, flexible facility for trend analysis. The importance of a flexible system that does not require deciding in advance what needs to be monitored routinely was stressed to us. The ground-based calibration data are still actively used, >4 years into the mission. Colocation of the operations (mission and instrument) and the ACIS instrument team has been important, at least in terms of increased efficiency. Instrument team members (like the PI) at Penn State can feel out of the loop or behind the times. Colocation important to keep all science members in the loop.


Download ppt "GLAST LAT Project ISOC 5/17/2004 – Seth Digel1 ISOC Lessons Learned RFA09 Issue –No writeup on lessons learned from visits to other instrument/mission."

Similar presentations


Ads by Google