BAS/EUVE/0063/95
One-Shift to Zero-Shift Transition Plan (V1)
B. Stroozas, 24 Jul 1995
1. Science Instrument Support Team Philosophy
With the recent move to single-shift payload operations in the ESOC,
and with the concept of zero-shift operations to support the Extended
Mission, has come a change in philosophy for the ISO Science Instrument
Support (SIS) team. For future payload operations the ESOC will not be
staffed as it has conventionally been in the past. In future operations
all telemetry monitoring will be done autonomously; wherever possible,
all other payload duties will also be streamlined and automated. The goal
is to minimize payload operations costs and reduce -- and, if possible,
eliminate -- the needs for human intervention. As these changes take
affect the roles of the SIS team members will be more and more oriented
to support development and test-bed activities.
Working in this automated environment the Payload Controllers (PCs)
will be present at CEA during normal business hours (M-F, 9am-5pm) and
will be responsible for the following:
- support payload anomaly identification and resolution
- payload commanding
- supervision of the work of the student assistant Payload Controller
Aides (PCAs; see below)
- any other miscellaneous duties
The ACE system will remain in effect during off-shift hours.
The PCAs will be present at CEA during normal work hours on weekends
(9am-5pm) and during regular business hours as school schedules permit.
Under the supervision of the PCs the PCAs will perform the following
duties:
- any remaining daily and weekly checklist tasks
- assisting in anomaly identification and resolution
As mentioned above, daily staff work will be focused more on development
and test-bed efforts as the zero-shift transition progresses; those
activities deemed useful to SIS operations (e.g., those that reduce manual
work and/or enhance the system abilities) will be incorporated into daily
operations.
2. Zero-Shift Operations
The concept of zero-shift operations is a goal of CEA/EUVE. Moving
to zero shifts provides for numerous opportunities for innovation and
advanced software technology applications, for cost savings due to reduced
operations man-power needs, and as a proof-of-concept for the benefit of
future NASA missions. The recent transition from three shifts to
one makes the zero-shift transition the next logical step in the progression
of streamlining and automating satellite mission operations.
The definition of zero-shift operations is based on the following points:
- The primary focus is on ensuring the health and safety (H&S) of the
science payload instruments; secondary focus is on ensuring the
quantity and quality of the science data.
- Autonomous software replaces human intervention wherever practicable.
- No human is required to monitor or command the payload or ground systems
during normal operations.
The actual transition to zero-shift operations will be accomplished via
a phased approach. Phase 1 will require that software completely take over
all monitoring of real-time telemetry although, personnel will still be
required on a daily basis (including weekends) to handle specific daily and
weekly support tasks. Phase 2 will require that software handle all
necessary operations and that human intervention will only be necessary for
anomaly investigation and resolution. In addition to addressing operations
needs for human and software support this plan will ultimately also address
requirements for such issues as facilities, hardware, on-call support, and
remote access. The overall system design will support ISD's Autonomous Data
Aquisition -- Turn-key Inter-Network Archive (ADA-TINA) concepts.
Successful zero-shift operations will ensure that all necessary functions
be handled by software and that human intervention only be required to
investigate and correct anomaly situations. During nominal operations the
systems in the ESOC should be able to operate indefinitely without requiring
human support.
3. Assumptions and Baseline Requirements
The zero-shift transition is based on the following assumptions and
baseline requirements:
- THERE WILL BE NO COMPROMIZING OF PAYLOAD H&S.
- The 24-hour on-call ACE support will be maintained. The ACE will be
required to respond to all pages. All H&S issues will be dealt with
immediately; all non-H&S issues (e.g., software and/or systems
problems), including all commanding for payload observation
configurations and recoveries, may be deferred until the next day
(although efforts will be made to get *all* problems addressed
immediately). The payload will never be left in an "unsafe"
condition.
- We will continue to try to maximize the science data return. However,
as a cost savings measure Roger has indicated his willingness to
relax response times when there is no H&S risk. This may potentially
sacrifice science data collection by up to 30%. Any affected targets
will be rescheduled to complete our observation requirements as set
forth in the NRA.
- All CEA-scheduled tests requiring real-time support will be scheduled
only during normal work hours; test times will be approved in advance
by both the Science Instrument Support and Observation team leaders.
We will attempt to require the same for all similar non-CEA-scheduled
(i.e., GSFC-scheduled) tests. For any tests conducted during
off-shift hours the SIS team leader will schedule any required
software or systems support in advance with the respective
supervisors.
- The 20-hour rule will remain in effect.
4. Current One-Shift Operations
In current one-shift operations the PCA is tasked during the daily
shift with the visual monitoring of real-time passes and the specific
daily/weekly checklist tasks that support console duty. PCAs work
regular business hours (9am-5pm) to cover all weekend shifts, and as
many regular weekday shifts as their school schedules allow. The PC
is available during all weekday shifts (M-F, 9am-5pm) to tend to commanding
duties, anomaly resolution, supervision of PCAs, and other activities
(e.g., development and test-bed support). During off-shift hours the
PCs rotate as ACEs who respond to all pages from the monitoring software,
from PCAs, or from the message center (e.g., PACOR).
5. Zero-Shift Operations, Phase 1
The goal of the Phase 1 zero-shift transition will be to eliminate the
need for all visual monitoring of real-time telemetry passes. This will
cut the PCA workload during the weekday and weekend shifts; PCA operations
support will then only be required for the few hours each day required to
attend to the daily/weekly duties that support the console work. The roles
of the PC will be essentially the same as for the current single-shift
operations. Again, as tasks are automated the roles of SIS personnel will
be shifted to support development and test-bed activities.
It is estimated that Phase 1 can be accomplished by Nov 1995. The major
need for this transition (see below) is an expansion of eworks to include
additional engineering monitors that ensure adequate H&S checks throughout
the day.
6. Zero-Shift Operations, Phase 2
The primary goal of the Phase 2 zero-shift transition is to eliminate all
daily/weekly checklist tasks that support console work. This will eliminate
the need for any day-to-day activity and, therefore, any weekend support of
the payload. The primary focus of SIS staff -- both PCs and PCAs -- will
then be on development and test-bed activities instead of daily operations,
and all SIS personnel will work only during normal business hours.
A secondary goal of Phase 2 is to eliminate the need for manual commanding
of the payload. By relying on ATCs we can virtually eliminate the need for
human interaction except in anomaly or special commanding situations.
The timeframe for the Phase 2 zero-shift transition is TBD and is highly
dependent on the software development efforts, which are expected to be
significant. The Phase 2 needs and wants are being worked out in detail
(see below).
7. Needs (N) and Wants (W) for Phased (1/2) Zero-Shift Transition
The following lists some of the things that the SIS team deems as needs
(N) and wants (W) in support of the phased transition to zero-shift
operations. An item noted "N1" is deemed as a need for Phase 1; "W2" a want
for Phase 2; a "want" for Phase 1 often becomes a "need" for Phase 2. The
listing below is tentative and incomplete; further details will appear in
future revisions of this plan.
Simulations
- N1 -- 1-2 month simulation to verify and validate Phase 1 plan
- N2 -- 1-2 month simulation to verify and validate Phase 2 plan
Expansion of eworks
- N1 -- include additional monitors to maintain H&S
- N1 -- no pages for target-specific configuration (i.e., eworks knows
when to page based on the payload configuration)
- N2 -- verify correct observation configuration for science
- W2 -- verify proper execution of proper commands (echoes, etc.)
- W2 -- verify proper telescope pointing
Absolute Time Commands (ATCs)
- W1/N2 -- should provide for manual generation of ATCs, automatic
validation of ATC map files, and flag warning/error conditions
- W2 -- should automatically generate ATCs based on standard observation
configuration files (e.g., via HSTS)
Ground System Monitoring Software
- W1/N2 -- should monitor telemetry arrival, archival, etc. (want for
Phase 1 since people still here every day; need for Phase 2 since
weekend coverage not in effect)
- W1/N2 -- elimination of daily/weekly tasks (e.g., carousel maintenance,
PACOR backup, etc.)
- W2 -- streamlined/reorganized operations to minimize needs for
facilities, network, hardware, software, etc.
- W2 -- makes use of additional TBD RAID box capabilities
Mail comments to bretts@cea.berkeley.edu