CCSDS Spacecraft Monitor & Control Working Group (SM&C WG)

1. CCSDSSpacecraft Monitor & Control Working Group(SM&C WG) SpaceOps 2004

2. Membership • ESA • Mario Merri (chairman), Michael Schmidt, Alessandro Ercolani • Ivan Dankiewicz, Sam Cooper • BNSC • Roger Thompson (deputy chairman), Martin Symonds • NASA/JPL • Amalaye Oyake, Peter Shames • NASA/GSFC • Donald Custis Lokerson • CNES • Brigitte Béhal, Erwann Poupart • DLR • Harald Hofmann • JAXA • Takahiro Yamada Space Ops 2004

3. High Level Goal • Standardisation of interfaces for Spacecraft M&C • Reduced cost of Flight Components andGround Segment Infrastructure • Enable “plug and play” Architecture with components from different Agencies, Systems and Suppliers • Enable Mission Economies through: • Interoperability with partner systems and infrastructure • Risk Reduction through re-use of systems and operational concepts: increased reliability • Facilitation of Generic Software Infrastructure (On-board and Ground-based) • Application of a common M&C Approach throughout all mission phases • Application of a common M&C Approach to other domains (Ground Stations, Control and Test Centres, etc.) Space Ops 2004

4. Scope • Operational concept: • definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of both ground and space segments. • Set of Application Services: • definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Product Management, Flight Dynamics, Mission Planning, Automation, and Performance Evaluation. • Application-layer information: • definition of the standard information set to be exchanged for SM&C purposes. Space Ops 2004

5. Objectives • Define a common SM&C operational concept • Define a reference on-board and on ground architecture in close coordination with other CCSDS groups (e.g. SOIS, SEA) • Identify standard Mission Control System interfaces with M&C components: • with remote software management • with Mission Planning System • with the Flight Dynamics System • … • Define a standard approach to service specification • Define application-level service access points • Define SM&C Common protocol layer Space Ops 2004

6. Schedule Dec 03 Formation of WG (1st meeting) Apr 04 SM&C Service Framework (WB – draft 0.4) Dec 04 Green Book advanced concept papers on • Common SM&C Protocol Service • Core SM&C Application Service Space Ops 2004

7. Service Based Architecture • Defines the interface as a “contract” • Consumer (client) unaware of providers implementation • Popular with distributed and web based systems Space Ops 2004

8. Service Layering MOIMS: Mission Operations Information Management Systems SOIS: Spacecraft On-Board Interface Services Space Ops 2004

9. Interoperable Interface MOIMS Service Interfaces Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ProviderApplications Service Access Points Service Message Protocol MOIMS MOIMSApplication Services MOIMSApplication Services MOIMS Common Protocol Service MOIMS Common Protocol Service SLS, SOIS or Other CommunicationsService CommunicationsService CommunicationsService CommunicationsService Space Ops 2004

10. SOAP Adapter SOIS Adapter CORBA Adapter SLS Adapter SLS Adapter SOAP Adapter SOIS Adapter CORBA Adapter SLS Services SOAP SOIS Services CORBA SOIS Services SOAP SLS Services CORBA Network Adapters Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ProviderApplications Service Access Points Service Message Protocol MOIMS MOIMSApplication Services MOIMSApplication Services MOIMS Common Protocol Service MOIMS Common Protocol Service Space Ops 2004

11. PUS Adapter Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ClientApplications Service ProviderApplications Service Access Points PUS MOIMS MOIMSApplication Services (PUS Adapters) MOIMSApplication Services (PUS Adapters) SLS CommunicationsService CommunicationsService CommunicationsService CommunicationsService Interoperable Interface Space Ops 2004

12. Space System Context • Defines reference system • Defines operational context • Outlines clients of the system • Outlines operational areas of the system Space Ops 2004

13. Functional View • Uses RASDS methodology • Defines areas of functionality • Taken from the operational context • Defines interactions between functional areas • Leads to service identification Space Ops 2004

14. Modularity and Flexibility Space Ops 2004

15. Information flow Key task is to identify the information objects Elaboration of the services will identify these objects Will also define their attributes Space Ops 2004

16. Service Overview Space Ops 2004

17. List of services Space Ops 2004

18. Summary • Work done: • drafted CCSDS White Book • analysed operational context • identified services • used layered architecture • Future work: • CCSDS Green Book • CCSDS standard specifications of each service Space Ops 2004