Incident Report for Data Management Systems
The HST Mission Office requested an easy accessible report that documents all activities
that affect schedules or operations of the HST Data Processing and Distribution Systems
(HST DMS).
The HST Incident report is located at:
http://www.stsci.edu/institute/center/performance/incident
The report covers the major systems used for development, test and operations within the
HST DMS. It is designed to give users an easy location to check for planned or
unplanned activities that have impact on schedules within this environment.
All ESS, ODM and CPT staff working on those systems are required to initiate an
incident report for any anomaly or scheduled activity that interrupts normal activity, In
addition, we are asking branches to identify members of staff who will take the
responsibility to update the comments section and verify for accuracy.
Priorities: The URGENT tab should only be used for failures that will interrupt
operations for extended periods of time. High priority should be used for incidents
requiring shorter outages of major functional areas, for example; an activity that will
cause delayed processing of all science data. Medium, an activity that affects only less
critical functions and Low, an activity where systems continue to work but there are
issues that must be addressed. (Key for priorities is listed below)
Please send comments and questions to gibbs, pgrant.
Priority Key
Low - does not cause extended stoppage of daily operations/development or a workaround is available.
Medium - Affects 1 functional area in operations/development. It should not extend
beyond a business day.
High - Multiple functional areas are affected. Major failure or extended downtime
planned (over a business day).
Urgent - Most of the Data Management systems are unavailable in OPS or development
schedule is severely at risk because of major planned or unplanned activity.
What is an incident?
An incident is any occurrence that interrupts the production pipelines.
For development an incident should be recorded for occurrences that causes a delay in
posted deliverable schedules. For eg new requirements, system downtime.