Can Harmonization be Achieved via Standardization?: New Concrete Opportunities from the CCSDS Mission Operations Services

Transcription

1 Can Harmonization be Achieved via Standardization?: New Concrete Opportunities from the CCSDS Mission Operations Services CCSDS Spacecraft (SM&C) Mario Merri (ESA), Chair GSAW, Los Angeles, USA - 1 Mar 2011

2 2016 2

3 Putting Together Mission X Mission X Spacecraft & Launcher Ground Stations Mission Control System (Command and Control) Flight Dynamics System Mission Planning System Automation System Data Distribution System 3

4 CCSDS MO app store 4

5 CCSDS MO app store CCSDS App Store Welcome to the CCSDS Mission Operations Applications i Store Ground Segment Space Segment please select the segment on the left pane 5

6 CCSDS MO app store CCSDS App Store Ground Segment Ground Station Mission Control System Flight Dynamics System Mission Planning System Automation System Data Distribution System Space Segment SCOS-3000 Category: MCS Released: 1 Jan 2016 Free In-CONTROL Category: MCS Released: 1 Jan 2014 Free You-Control-It Category: MCS Released: 30 Sep 2015 $$$ M&C Suite Category: MCS Released: 30 Sep 2015 $$$ All these applications are CCSDS MO certified 6

7 Assembling Mission X Ground Segment from (Harmonised) Components Ground Station Mission Control System Services Mission Planning System Flight Dynamics System Automation System Data Distribution System Infrastructure 7 Application-Level Components communicate via standardised Services Services are supported by a distributed Infrastructure Reusable components Plug-in via Service Interfaces to the Infrastructure Both Components and Infrastructure are replaceable with minimum impact to rest of system

8 CCSDS Spacecraft M&C (SM&C) Working Group Established December 2003 ESA Chair (Mario Merri); UKSA Deputy Active Participation of 10 Space Agencies One of the Most Active CCSDS s Establishing a Service Oriented Architecture for Mission Operations Planning, Scheduling and Automation Navigation On-board Software / Configuration Management Multiple Prototypes now going operational at NASA/JSC for ISS 8

9 Distributable Mission Operations Functions Spacecraft M&C (Status, Control) Automation (Procedures, Timelines) Planning (Tasks, Goals) Mission Data (Products) Flight Dynamics (Orbit, Attitude) On-board Software Payload/Science Team Mission Control Centre Another Agency Spacecraft Manufacturer Mission Operations Services: Organisational Boundaries Functional Boundaries System Boundaries Long-Term Data Persistence 9

10 Characteristics of Mission Operations Services Service Oriented Architecture (SOA) for Spacecraft Mission Operations Application Level Services for Mission Operations Enable Plug-in Components: Applications & Infrastructure Semantic Interaction: Information not Data Extensible Framework: Common and Generic Elements Distributable: Independent of Deployment Architecture Protocol Agnostic: Independent of Transport Technology Language g g Neutral: Independent of Deployment Language 10

11 SOA: Integrated Systems vs. Modular Components In traditional modular system design, components can be integrated into just one system. With SOA, more loosely coupled components can be assembled into a range of similar systems. 11

12 End-to-End Services and Layering End-to-End Communication: Information Concepts (Invitation: Who, What, Where, When) Standard Pattern of Interaction (Invite, Respond) Mission Operations Transport Layer: Packaging Physical Communications Infrastructure Mission Operations I shall Invite She has my Lady to a Accepted Feast Thou I Graciously art Invited Accept to a Banquet Thou I Graciously art Invited Accept to a Banquet My Lord has I Invited Shall Accept me to afeast I shall Invite my Sweetheart to a Ball My Beau has Invited me to a Ball I ll Invite my Hey, Babe, Hey, Babe, Girlfriend to a Wanna Come Wanna Come Party to a Party? to a Party? My Boyfriend has Invited me to a Party I ll Invite my Girlfriend to a Rave U 12 Come 2 Rave? You Have Mail My Boyfriend has Invited me to a Rave 12

13 Mission Operations Framework Layers Application Layer Consumer/Provider Common Services Functional Services Mapping to implementation language MO Services Layer Directory, Login, M&C, Automation, Scheduling, Time, Abstract service specification defined in terms of the COM &MAL Common Object Model Identify, Definition, Occurrence, Status Generic service specification defined in terms of the MAL Message Abstraction Layer Messaging gabstraction Layer Generic Interaction Patterns, Access Control, Quality of Service Abstract messaging infrastructure Transport Layer Messaging Technology Mapping of the MAL to encoding and transport 13

14 Mission Operations Services Interoperability and Portability Language Binding JAVA Consumer Application SM&C Core Service JAVA C++ Provider Application JAVA SM&C Common JAVA SM&C Core JAVA C++ SM&C Core JAVA C++ SM&C Common JAVA SM&C MAL for AMS JMS JAVA C++ SM&C MAL for AMS JMS AMS JMS AMS JMS Interoperability Requires Wire Protocol Technology Binding: Encoding (e.g. XML) Transport (e.g. FTP) 14

15 MAL Protocol Bridging Consumer Application M&C Service Provider Application M&C Service MAL MAL Bridge MAL MAL Adapter A A MAL Adapter A MAL Adapter B B MAL Adapter B Transport Technology A Transport Technology B Applications hosted in different transport technology ogy environments: ESA / NASA Space / Ground CORBA / JMS Mission Operations Services transparently bridged at MAL layer Supports all Services overlaid on MAL Supports all Applications built on those Services 15

16 Clever Engineering of the MO Services Technology and location independent Application computer language Transport and encoding Interoperable On Ground and/or space Discoverable: not duplicated via directory service Implementing common features in the same way Messages (standard header, construction rules) Interaction patterns (Send, Submit, Request, Invoke, Progress, Publish-subscribe) Data types Error handling Common service template (archiving/retrieval, i i activity i monitoring, events, configuration) Common services (e.g. directory, login, ) 16

17 API Standardisation MO Java MO MAL Language Binding Specification MO Service Specification References References Implements Implements Implements Uses Java Transform MAL Model MO Service Model Generates Generates MAL Java API MO Service Java API Approach Compatible with Model Driven Development and Autocoding Extensible Approach: Only one Magenta Book required per Language 17

18 Specific MO Service Definition Requires: Definition of Information Model (Service Objects) Definition of Service Operations (mapped to Interaction Patterns) Service Configuration (Object Definitions) [for Service Deployment] Does not Require: Message Encoding/Binding d g to Messaging g Technology ogy Standard Technology Binding applies to all MO Services Specific Definition of API Standard Language g Transform applies to all MO Services Definition of Service Discovery, Login, Authentication, etc. Covered by MO Common Service Specifications Specification of dedicated Service History Model Covered by MO Common Object Model 18

19 CCSDS Mission Operations Book Structure and Status MO Concept Mission Operations Services Specifications Technology Mappings Language Mappings M&C MAL Published Books: MO Concept Reference Model Reference Model Green Book Magenta Book Blue Book Service Specifications 52x.y COM Common Object Model MAL Message Abstraction Layer (MAL) Service Specific Encoding (optional) MAL Encoding Application Profile Green Book = Informational Magenta Book = Recommended Practice Blue Book = Standard Language API Draft Books: Java API COM Common Services M&C Services Space Packet Binding Planned Books: Motion Imagery Service JMS Binding C++ API 19

20 Orbital Events Example: Mission Planning and Service Orchestration Flight Dynamics End-Users Operations Other MPS Planning Request Orbital Event Contact Scheduling Activity Scheduling On-board Software Management g Manoeuvres Software Loads Planning Request Service Orbital Event Service Mission Planning Engine Contact Scheduling Service [SLE-Man] Ground Station Complex Scheduling Service On-board Schedule Ground Schedule On-board Schedule Management Ground Schedule Execution 20

21 MAL Prototyping Validation Mandatory CCSDS (ESA-CNES) Prototype Completely automated individual tests! The two implementations interoperated perfectly! NASA/JSC-DLR Prototype DLR s MCS (SCOS 2000) and JSC Simulator (legacy systems!) Conclusion: DLR GSOC and NASA/JSC successfully exchanged actions, parameters and alerts... The interoperability prototype demonstrated that the Message Abstraction Layer is transport and technology agnostic and that space agencies can use the Mission Operations standards for interoperability among existing legacy systems. our findings provide support for the overall viability of the standards. ISS will be first operational user of MO Services Decision: PLATO (Power Level Analysis NASA/JSC) to be a client of the M&C Parameter service. Operational as of

22 Conclusion MO service ss underlying framework (RM, MAL) is ready M&C and Common Services books are in advanced status and will come next, hopefully by the end of the year Next MO services to be tackled depend on the interests and needs of the community Planning?, Flight Dynamics? Suggestions and active participation p of interested groups are welcome MO service standardisation provide the framework that will allow real harmonisation of services (and components) for mission operations 22

23 Let MO Services do the boring part of the job so that YOU can focus on the smart part 23