Title: CryoSat Mission Preparation: A Cost Savings and Quality Improvement Case Study
1CryoSat Mission Preparation A Cost Savings and
Quality Improvement Case Study
- Jim Cater
- Klaus Dieter Mau
- Nic Mardle
- David Quigley
2CryoSat Mission
- Mission objectives - Ice altimetry with high
spatial resolution for - Ice Sheet Interiors (Conventional LRM Mode)
- Sea Ice (High Resolution SAR Mode)
- Ice Sheet Margins (High Res. SARInMode)
- Overall Ice Sheets (LRM and SARInMode)
3CryoSat Instrument Layout
4CryoSat Mission Complexity
- The CryoSat spacecraft database consists of
approximately - 7,000 telemetry parameters and
- 1,700 commands
- The Flight Operations Manual contains over 450
individual procedures
5MOIS Background
- MOIS provides an integrated suite of tools for
procedure - Design development
- Validation
- Execution
- Maintenance
- MOIS generates
- Manuals
- Procedures
- Languages
- Reports
- Real-time procedure scheduling and automation
engine
6Procedure Development
- Procedure flow designed graphically using the
MOIS Flowcharter. - Logic constructs include
- If
- Repeat-Until
- While
- Case
- Wait
7Procedure Development (cont.)
- Procedure details guided by spacecraft data
- Telemetry and commands selected from DB
- Calibration and limit data provided to developer
- Procedure calls selected from Library
- Enforced variable type usage
8EADS-Astrium Configuration
9MOIS Execution Environment
10SCOS-2000 Execution Environment
11Scope of MOIS Usage
Hot Spots 2 Unfocused effort on coding and
validation of Operations and Test Sequences 4
Delivery of Flight Operations Manual 5
Procedures tend to be control system dependent 6
Inefficiencies due to incompatibility of
systems 7 Black boxes become black holes
12Hot Spot 2
- MOIS minimised control system coding and
validation - EADS-Astrium developed and validated procedures
within MOIS - ESOC generated SCOS-2000 command sequences
directly from MOIS procedures - Minor repackaging and modifications required for
SCOS-2000 specific operations
13Hot Spot 3
- MOIS reduced formal delivery overhead and
complexity - FOM generated directly from MOIS Procedures,
which had been validated using the EADS-Astrium
EGSE and MOIS Validator - 20 full and partial deliveries of FOM data during
development life-cycle - SVT-0 had zero procedural issues
14Hot Spot 4
- Although the MOIS database was not used as the
transfer mechanism - The MOIS procedures were developed,
consistency-checked and validated using a
SCOS-2000 compliant DB - EADS-Astrium delivered this DB with the FOM
- Base DB enhanced with ESOC specific data
- Number of DB issues greatly reduced
15Hot Spot 5
- MOIS demonstrated the potential for abstracting
satellite control procedures from the underlying
system - CGS language scripts not used
- Minimal changes needed for SCOS-2000 less than
5 of sequences caused problems - Engineers concentrate on enhancing operations
rather than transcribing data
16Hot Spots 6 7
- Interface documentation was minimised
- No multi-level format definitions
- Procedure Rules and Guidelines (How-to)
- Ops management had tools to provide objective
evidence of - Development status
- Validation status
- Delivery status
17CryoSat-2
- Potential for further efficiencies
- Easy identification of procedural impacts due to
variations between the two satellites. - Improved process for new procedures
- Enhanced set of development guidelines
- Potential use of MOIS execution environment at
ESOC - Potential use of MOIS by EADS-Astrium AIV
- Paper AIAA-2006-5710 Smart- 1 Ground Operations
Automation Session 31 Wednesday.
18Conclusions
- Efficient and effective flight procedure
development and maintenance. - Efficient and effective testing of flight
procedures when MOIS execution environment is
used. - Greater consistency between procedures and
telemetry and telecommand definitions. - Minimal conversion of procedural data required
for different control systems. - Efficient and effective re-use of operations
knowledge between similar satellites.