1 / 14

SPACECRAFT DATABASE STANDARDISATION: AN OMG INITIATIVE

SPACECRAFT DATABASE STANDARDISATION: AN OMG INITIATIVE Mario Merri - ESA/ESOC Roger Thompson - Science Systems (Space) Ltd . Janice Champion - Boeing Satellite Systems Gerry Simon - Lockheed Martin , USAF SMC Det 12 VO Peter Shames - Jet Propulsion Laboratory Mike Rackley – NASA / GSFC

daniel_millan
Download Presentation

SPACECRAFT DATABASE STANDARDISATION: AN OMG INITIATIVE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPACECRAFT DATABASE STANDARDISATION: AN OMG INITIATIVE Mario Merri - ESA/ESOC Roger Thompson - Science Systems (Space) Ltd. Janice Champion - Boeing Satellite Systems Gerry Simon - Lockheed Martin, USAF SMC Det 12 VO Peter Shames - Jet Propulsion Laboratory Mike Rackley – NASA/GSFC Jim Wetherbee - OMG Space Domain Task Force

  2. Agenda • Introduction • The need of spacecraft database standardisation • Approach to work • Packaging database • Telemetry database • Command database • Conclusions SpaceOps 2002

  3. Object Management Group (OMG) and Space • OMG: • Founded in April 1989 • international not-for-profit software consortium aiming at setting standards in the area of distributed object computing • Vendor-neutral membership-driven organisation • About 800 members • Fast track standardisation process • More at http://www.omg.org • OMG Space Domain Task Force (DTF) • Established in September of 2000 • Aimed atfostering the emergence of cost effective, timely, commercially available and interoperable space, satellite and ground system domain software components through object technology • More at http://space.omg.org SpaceOps 2002

  4. Space DTF Main Activities • Developed reference architecture • More at http://space.omg.org/ReferenceArchitecture.htm • Produced Requests for Proposals: • RFP-1: Telemetric and Command Data Specification • RFP-2: Monitor and Control Data Access • Evaluated submissions to RFP-1 SpaceOps 2002

  5. Design & Build Integration& Check-out LEOP Operations Data Exploitation Simulators TM/TC Data: XML Exchange Operations:Major Upgrades Anomaly Investigation TM/TC Data Exchange SpaceOps 2002

  6. RFP-1: Problem Statement • TM and TC definitions must be exchanged • within/across organisations • within across systems • but … • single mission supported by different systems and organisations • multiple heterogeneous missions supported by common ground segment infrastructure • implying that TM and TC exchange … • is difficult, costly and error-prone • requires custom translation and ingestion of the TM and TCdata • requires revalidation at each step • Solution • transparent transition from one ground system to another • standardization of the TM and TC data definition format SpaceOps 2002

  7. RFP-1 Objectives • Standardised information model for TM data definitions • Allow exchange of TM/TC Definitions: • between Mission Phases • between Organisations • between Systems • without need for re-implementation or re-validation • Broad Scope within Space Data Systems: • All Phases of Mission Lifecycle • All Segments of Mission Infrastructure (Spacecraft, Payload & Ground) • Limited to Definition and not Transfer of TM/TC data • As Inclusive as Possible: • Support Legacy Missions • Support Existing Standards • Extensible: Mission Specific and Future Standards SpaceOps 2002

  8. RFP-1 Status • 3 submissions received describing in XML the current structure of their Telemetry and Command databases: • European Space Agency (ESA) • Boeing • Lockheed Martin • Agreed way forward: merge forces and work towards a single, combined, XML-based, response • NASA/GSFC and JPL support single submission • Organisation-specific software to be used to convert from the generic format to its own specific one SpaceOps 2002

  9. Approach to RFP-1 Integration • The submission integration work was split as follows: • Boeing: Telemetry • Lockheed Martin: Command, Stream and Algorithm • ESA: Packaging • NASA (GSFC & JPL): Analysis and review • Coordination by e-mail, telecon and (some) meetings • Extremely challenging task • Different organisations’ backgrounds and culture • Different technologies used (e.g. ESA mainly CCSDS packet TM/TC, Boeing and Lockheed Martin mainly TDM TM/TC) SpaceOps 2002

  10. RF Signal Which is demodulated to produce … Symbol Stream Which is Decrypted, Decoded, Frame Synched, & Extracted to produce … Packets or Minor Frames Which may be turned into Messages of various kinds … Packets • Data Elements described as: • Message Descriptors • Containers (data structures) • Message Sets Annotated Packets Minor Frames Other Data Description Context SpaceOps 2002

  11. Packaging Schema SpaceOps 2002

  12. Telemetry Schema SpaceOps 2002

  13. Command Schema SpaceOps 2002

  14. Conclusions • Standardisation of TM and TC definition is possible • for a broad range of common spacecraft operating modes and communication link designs • for a variety of different signaling and data structuring modes (i.e. packetised and TDM data) • for a variety of different commanding approaches • XML seems to be the right technology • Organisations might develop tools to convert TM and TC definition from the XML common format to their own proprietary format • The eventual publication of this standard will provide a common approach for the exchange of this data • significant reduction of cost and riskindevelopment and validation expected SpaceOps 2002

More Related