Transcript SM&C
CCSDS Spacecraft Monitor & Control Working Group (SM&C WG) SpaceOps 2004 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 2 High Level Goal Standardisation of interfaces for Spacecraft M&C • Reduced cost of Flight Components and Ground 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 3 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 4 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 5 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 6 Service Based Architecture Defines the interface as a “contract” Consumer (client) Lookup unaware of providers implementation Service consumer Popular with distributed and web based systems Space Ops 2004 Service directory Publish Invoke Service provider 7 Service Layering GROUND SEGMENT Application Application FLIGHT SEGMENT Application Application Application Application MOIMS SERVICES GROUND SERVICES SPACE LINK SERVICES SOIS SERVICES MOIMS: Mission Operations Information Management Systems SOIS: Spacecraft On-Board Interface Services Space Ops 2004 8 MOIMS Service Interfaces ServiceClient Client Service Service Client Applications Applications Applications Service Access Points ServiceClient Client Service Service Provider Applications Applications Applications Service Message Protocol MOIMS Application Services MOIMS Application Services MOIMS MOIMS Common Protocol Service MOIMS Common Protocol Service Communications Service Communications Service SLS, SOIS or Other Communications Service Communications Service Interoperable Interface Space Ops 2004 9 Network Adapters ServiceClient Client Service Service Client Applications Applications Applications Service Access Points ServiceClient Client Service Service Provider Applications Applications Applications Service Message Protocol MOIMS Application Services MOIMS Common Protocol Service MOIMS Application Services MOIMS MOIMS Common Protocol Service CORBA SOAP SOIS SLS Adapter Adapter Adapter Adapter CORBA SOAP SOIS SLS Adapter Adapter Adapter Adapter SOIS SLS CORBA SOAP Services Services SOIS SLS CORBA SOAP Services Services Space Ops 2004 10 PUS Adapter ServiceClient Client Service Service Client Applications Applications Applications ServiceClient Client Service Service Provider Applications Applications Applications Service Access Points MOIMS Application Services PUS MOIMS Application Services MOIMS (PUS Adapters) (PUS Adapters) Communications Service Communications Service SLS Communications Service Communications Service Interoperable Interface Space Ops 2004 11 Space System Context Defines reference system Defines operational context Outlines clients of the system Outlines operational areas of the system Spacecraft A1 Agency ground station network Spacecraft B Spacecraft A2 Commercial ground station network Other ground station network Spacecraft control centre Payload operations centre External organisation Space Ops 2004 12 Functional View Uses RASDS methodology Defines areas of functionality Flight Dynamics Time & Location Analysis M&C • Taken from the operational context Defines interactions between functional areas Leads to service identification Space Ops 2004 Data Product Management Automation Schedule Execution Software Management Planning 13 Modularity and Flexibility Offline ground systems Offline ground systems Online ground ground systems systems Online Analysis Analysis M& &C M Spacecraft Spacecraft Onboard Onboard M &MC& C Onboard Automation Flight Flight Dynamics Dynamics Time & Location Planning Planning Automation Onboard Schedule Execution Schedule Execution Onboard Planning Data Product Management Software Software Management Management Time & Location (onboard GPS) Data Product Management Software Management Space Ops 2004 Software Software Management Management 14 Information flow Flight Dynamics Planning Request Planning Key task is to identify the information objects Elaboration of the services will identify these objects Will also define their attributes Schedule Schedule Execution Space Ops 2004 Activity Automation Action M&C Parameter Alert 15 Service Overview Remote Node (Spacecraft, Groundstation, Simulator etc) Remote SM & C Remote Automation Remote Schedule Execution Remote Planning Remote File System Remote Time & Location Remote Software SM & C Proxy Remote Automation Proxy Remote Schedule Proxy Remote Planning Proxy Remote File System Proxy Time & Location Proxy Remote Software Proxy Time & Location Service File Management Service Software Management Service Planning Service Flight Dynamics Service Interaction Service Scheduling Service Automation Service SM&C Service SC M & C Displays Ground Nodes Automation Schedule Execution Planning Analysis Flight Dynamics OB Software Management Operator Notification External Space OpsExternal 2004 Node(s) 16 List of services Common SM&C Protocol Common protocol layer Core SM&C Application Parameters: calibration, monitoring, aggregation, configuration, statistics, … Commands: send, validate, verify, … Events: notify, … Automation Automated procedure/functions: control (e.g. start, stop), progress reporting, … Scheduling Schedule: managing (e.g. load, clear, shift, …), control (e.g. start, suspend, resume, …) Interaction Asynchronous (human) operator notification and interaction, … Planning Plan: managing (e.g. add/delete/modify activity, …), control (e.g. validate plan, generate plan, allocate authority…) Flight Dynamics Orbit/attitude determination/propagation, manoeuvre preparation, … Time Time correlation, set time, … Location Tracking, ranging, and onboard position determination, … Data Product Management File management and transfer, both ground based and onboard Software Management Software versioning, patching, dumping and releasing, … Space Ops 2004 17 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 18