Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OPS Forum Earth Observation Family: Reuse of mission control system 11.11.2005

1,207 views

Published on

CryoSat-1 was the first EO mission to use the 'mission family' concept.

Published in: Technology, Spiritual
  • Be the first to comment

  • Be the first to like this

OPS Forum Earth Observation Family: Reuse of mission control system 11.11.2005

  1. 1. Earth Observation Family: an insurance for the reuse strategy for the Mission Control System Damiano Guerrucci and Vemund Reggestad (OPS-GDA) 11-Nov-2005
  2. 2. Outline <ul><li>Part 1 </li></ul><ul><ul><li>Mission family concept and benefit </li></ul></ul><ul><ul><li>EEMCS Status </li></ul></ul><ul><ul><li>Cryosat and GOCE </li></ul></ul><ul><li>Part 2 </li></ul><ul><ul><li>EEMCS Evolution </li></ul></ul><ul><ul><li>EEMCS Maintenance </li></ul></ul><ul><ul><li>Aeolus </li></ul></ul>
  3. 3. EE Mission Family: the History <ul><li>Cryosat was the first mission in the family </li></ul><ul><ul><li>The “delta” approach (against S2k) applied for requirement definition </li></ul></ul><ul><li>Goce applied the delta approach against Cryosat </li></ul><ul><li>During the development of these first missions: </li></ul><ul><ul><li>a subset of common functionality was identified, which was not available in the S2K </li></ul></ul><ul><ul><li>This subset of functionality was isolated into the Earth Explorer Mission Control System (EEMCS) Family Kernel as a middle layer between S2K and the mission specific development </li></ul></ul><ul><li>This provides a clean layered software architecture for the Mission Control Systems of each member of the family </li></ul><ul><li>Thanks to this, Aeolus has been defined as delta against the EEMCS </li></ul>S2K Cryosat Cryosat GOCE Cryosat GOCE EEMCS Cryosat GOCE EEMCS Aeolus
  4. 4. Why Mission Families? <ul><li>Missions with a similar profile require the development of similar mission-specific features </li></ul><ul><ul><li>E.g. Frequent, short passes </li></ul></ul><ul><ul><li>Re-use of family-specific interfaces (both internal and external) </li></ul></ul><ul><li>However, these features are not always included in SCOS-2000 as they are not stable or generic enough </li></ul><ul><li>If these features are grouped and shared by mission within the same family, then … </li></ul><ul><ul><li>Larger re-use of Software </li></ul></ul><ul><ul><ul><li>Cost, quality, schedule and risk benefits </li></ul></ul></ul><ul><ul><li>Testing synergy with other members of the family </li></ul></ul><ul><ul><li>Re-use of all associated data and processes </li></ul></ul><ul><ul><ul><li>E.g. procedure, training, test plans, expertise </li></ul></ul></ul><ul><ul><li>Seamless transition of expertise between one mission to the next </li></ul></ul>
  5. 5. “ Extended Delta” approach – the present <ul><li>Software Requirement Engineering (3 layers): </li></ul><ul><ul><ul><li>SCOS-2000 </li></ul></ul></ul><ul><ul><ul><li>EEMCS </li></ul></ul></ul><ul><ul><ul><li>Mission specific </li></ul></ul></ul><ul><li>Architectural phase (3 layers): </li></ul><ul><ul><ul><li>SCOS-2000 and interfaces are, wherever possible, kept untouched </li></ul></ul></ul><ul><ul><ul><li>EEMCS </li></ul></ul></ul><ul><ul><ul><li>Mission specific </li></ul></ul></ul><ul><li>Development phase: </li></ul><ul><ul><li>3 workspaces plus repatriation layers for: </li></ul></ul><ul><ul><ul><li>EEMCS to S2K functionality </li></ul></ul></ul><ul><ul><ul><li>Mission specific to EEMCS functionality </li></ul></ul></ul><ul><li>Testing and validation phase: </li></ul><ul><ul><li>Re-use/adaptation of master test plan </li></ul></ul><ul><ul><li>EEMCS is tested concurrently by several missions focused mainly on mission specific features </li></ul></ul><ul><li>Maintenance phase: </li></ul><ul><ul><li>the SCOS-2000 kernel is maintained under independent arrangements (OPS-GI) </li></ul></ul><ul><ul><li>EEMCS and Mission Specific systems maintained in a combined maintenance </li></ul></ul>S2K Cryosat Cryosat GOCE Cryosat GOCE EEMCS Cryosat GOCE EEMCS Aeolus
  6. 6. <ul><li>EEMCS5 </li></ul><ul><ul><li>Based on S2K-R3.1 </li></ul></ul><ul><ul><li>Used by CGMCS5 ready for Cryosat Launch </li></ul></ul><ul><li>EEMCS6 </li></ul><ul><ul><li>Based on S2K-R4.0 </li></ul></ul><ul><ul><li>Used by CGMCS6 for GOCE and Cryosat </li></ul></ul><ul><li>Full set of documentation available </li></ul>EEMCS Current Status
  7. 7. <ul><li>The EEMCS kernel is dynamic: </li></ul><ul><ul><li>Port to new infrastructure </li></ul></ul><ul><ul><li>adding new mission-family-specific features </li></ul></ul><ul><ul><li>Repatriated generic features to infrastructure </li></ul></ul>EEMCS: A living kernel SCOS-2000 EE Kernel (EEMCS) Cryosat Goce Aeolus I/F I/F … .
  8. 8. <ul><li>Multi-mission DBS: </li></ul><ul><ul><li>Same application used for Cryosat and GOCE </li></ul></ul><ul><ul><li>Will be enhanced for Aeolus </li></ul></ul><ul><li>This decision is due to the limitations of the MS Access to control changes </li></ul><ul><li>It is a very configurable application with easy maintenance for the missions </li></ul>EEMCS: Database system
  9. 9. <ul><li>EEMCS TMS Functionality: </li></ul><ul><ul><li>Independent TM processing for playback TM </li></ul></ul><ul><ul><li>TM replayer </li></ul></ul><ul><ul><li>Generic Time correlation function and timestamping </li></ul></ul><ul><ul><li>Processing of high-priority TM </li></ul></ul><ul><ul><li>TM Gap detection and consolidation </li></ul></ul>EEMCS: Telemetry System <ul><li>Time correlation solution: </li></ul><ul><ul><li>All functionality in the kernel </li></ul></ul><ul><ul><li>High configurability for algorithm </li></ul></ul><ul><ul><li>Enable/disable of features depending on mission </li></ul></ul>
  10. 10. EEMCS: Commanding System <ul><li>Verification based on playback TM </li></ul><ul><li>Command ID and parameter ID types </li></ul><ul><li>Hazardous commands </li></ul><ul><li>Service 11 advanced modelling: </li></ul><ul><li>S2K customisation for service 11 packets </li></ul><ul><li>Global enable/disable status </li></ul><ul><li>New dump model display (compare TM dump vs. ground model, and update) </li></ul><ul><li>Configurable features to adapt to the different missions </li></ul>
  11. 11. <ul><li>Mission Planning System: </li></ul><ul><ul><li>Simple mission planning approach implemented </li></ul></ul><ul><ul><li>Initial example of mission planning infrastructure </li></ul></ul><ul><ul><li>Merge of the different input files to generate the onboard, ground and station schedules </li></ul></ul><ul><li>OBSM System: </li></ul><ul><ul><li>S2K OBSM customised for Cryosat and GOCE </li></ul></ul><ul><ul><li>Command generation and TM dump processing implemented in a fully generic way </li></ul></ul><ul><ul><li>MDF file drives the full functionality </li></ul></ul><ul><ul><li>It can be adapted to most of onboard devices just by configuration </li></ul></ul>EEMCS: MPS/OBSM
  12. 12. The Cryosat experience <ul><li>Despite the Cryosat launch failure, … </li></ul><ul><ul><li>EEMCS system successfully proved in operational scenarios in more than 20 simulations </li></ul></ul><ul><ul><li>EEMCS tuned for the LEOP phase </li></ul></ul><ul><ul><li>Validated software support procedures and practices available for next EE missions </li></ul></ul><ul><li>A possible Cryosat-II will benefit from the EEMCS Kernel approach: </li></ul><ul><ul><li>EEMCS kernel for S2K-R5.0 will be developed by Aeolus </li></ul></ul><ul><ul><li>Only mission specific parts needs porting to new Kernel </li></ul></ul><ul><ul><ul><li>Porting activity easier due to minimal size of mission specific code. </li></ul></ul></ul>
  13. 13. EEMCS Evolution and Development <ul><li>The concept of “Master EEMCS” is established: </li></ul><ul><ul><li>A EEMCS embedded in the MCS of a given mission (usually the last one under development) will be elected “Master EEMCS” </li></ul></ul><ul><li>At any time, there shall be only one “Master EEMCS” </li></ul><ul><ul><li>The “Master EEMCS” will be given a unique version number </li></ul></ul><ul><ul><li>Includes a version of the EEMCS documentation </li></ul></ul><ul><li>Future mission shall start their development from the “Master EEMCS” and possibly takeover the master-ship </li></ul>One Master development Line time EEMCS5 CGMCS5 (Cryosat) EEMCS6 CGMCS6 (GOCE) EEMCS7 AMCS1 EEMCS8 AMCS2 EEMCS9 xMCS1 EEMCS10 xMCS2 EEMCS11 xMCS3
  14. 14. Family Combined Maintenance Concept <ul><li>Single combined maintenance contract for the family </li></ul><ul><ul><li>Covers both kernel and mission-specific </li></ul></ul><ul><ul><li>Cost model driven </li></ul></ul><ul><ul><li>Synergy increases when several missions use same EEMCS version (economic incentive) </li></ul></ul><ul><li>EEMCS only maintained as a part of a specific MCS </li></ul><ul><ul><li>Stand alone maintenance complexity avoided </li></ul></ul><ul><li>Delivers EEMCS patches to development line </li></ul>Cryosat EEMCS5 time GOCE EEMCS6 Porting from 5 to 6 Synergy
  15. 15. Projects Interactions – as we think it Combined maintenance xMCS Contract EEMCS9 xMCS1 EEMCS10 xMCS2 EEMCS11 xMCS3 AMCS Contract EEMCS7 AMCS1 EEMCS8 AMCS2 CGMCS Contract EEMCS5 CGMCS5 (Cryosat) EEMCS6 CGMCS6 (GOCE) S2K3.1 R4.0 R5.0 Rx Ry Aeolus EEMCS Cryosat EEMCS 5 GOCE EEMCS 6 Release Patch Patch Release
  16. 16. EEMCS: pros and cons <ul><li>Flexibility and fast reaction in satisfying mission needs </li></ul><ul><li>Bridging Infrastructure schedule </li></ul><ul><li>S2K updates done once and transparent to mission </li></ul><ul><li>Stabilisation of generic requirements and improvement of implementation before their inclusion in the Infrastructure </li></ul><ul><li>Avoids proliferation of mission specific codes covering same needs (e.g. DBS, FTS) </li></ul><ul><li>Unique starting point for a wider number of missions </li></ul><ul><li>Force a generic approach at requirement definition and implementation phases </li></ul><ul><li>Additional intermediate interactions between missions and infrastructure projects </li></ul><ul><li>Centralised across mission information system required </li></ul><ul><li>Increased response time from infrastructure to missions under maintenance (releases, patches) </li></ul>
  17. 17. Some EE Family Statistics Impact on requirements Impact on cost
  18. 18. Conclusions <ul><li>Concept of Mission-Family developed and proven beneficial </li></ul><ul><ul><li>“ Delta” approach </li></ul></ul><ul><ul><li>Reuse of functionality across missions via EEMCS isolation, evolution and maintenance </li></ul></ul><ul><li>EEMCS concept fully deployed and defined </li></ul><ul><ul><li>for Cryosat, Goce and Aeolus </li></ul></ul><ul><ul><li>to follow the evolution of the infrastructure </li></ul></ul><ul><ul><li>shaped to keep industrial competition </li></ul></ul><ul><li>Several other advantages </li></ul><ul><ul><li>Cost, quality, schedule and risk </li></ul></ul><ul><ul><li>Testing synergy with other member of the family </li></ul></ul><ul><ul><li>Re-use of all associated data and processes </li></ul></ul><ul><ul><ul><li>E.g. procedure, training, test plans, expertise </li></ul></ul></ul><ul><ul><li>Seamless transition of expertise between one mission to the next </li></ul></ul><ul><li>Aeolus is the first mission where the full mission-family concept is applied to all phases </li></ul><ul><ul><li>Started development from a very mature system </li></ul></ul><ul><ul><li>Has currently the “EEMCS Master” </li></ul></ul>

×