moims plenary ccsds spacecraft monitoring & control wg (sm&c) workshop #02, 10-14 may 2004...
TRANSCRIPT
MOIMS Plenary
CCSDS Spacecraft Monitoring & Control WG (SM&C) Workshop #02, 10-14 May 2004
Mario Merri, ESA/ESOC, Chairman
MOIMS Plenary p. 2SM&C-WS#02 10-14 May 04
Agenda
Status of activityProgress to dateWhite Book: Initial resultsOutlookIssues and cross-issues
MOIMS Plenary p. 3SM&C-WS#02 10-14 May 04
Membership (May 2004) - A strong team!
Mario Merri (ESA) – chairmanRoger Thompson (BNSC) - deputy chairmanMartin Symonds (BNSC)Brigitte Béhal (CNES)Erwann Poupart (CNES)Harald Hofmann (DLR)Klaus Gnadl (DLR)Alessandro Ercolani (ESA, PoC)Michael Schmidt (ESA, PoC)Ivan Dankiewicz (ESA/SciSys)Sam Cooper (ESA/SciSys)Takahiro Yamada (Jaxa)Amalaye Oyake (JPL)Ashton Vaughs (JPL)Peter Shames (JPL)Donald C. Lokerson (NASA/GSFC)
= has confirmed attendance to this CCSDS workshop
MOIMS Plenary p. 4SM&C-WS#02 10-14 May 04
Progress to Date
High interaction within WG (9 telecons)Initiated cross-fertilisation with SOIS
2 telecons Produced Memorandum of Understanding
Worked on White Book 4 drafts
MOIMS Plenary p. 5SM&C-WS#02 10-14 May 04
WB - 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.)
MOIMS Plenary p. 6SM&C-WS#02 10-14 May 04
WB - 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
Core Set of 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
MOIMS Plenary p. 7SM&C-WS#02 10-14 May 04
WB - 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)
Define a standard approach to service specification
Define minimum set of ground SM&C kernel functionality
Define space-to-ground application-level interface messages
Identify standard Mission Control System interfaces with M&C components: With remote software management With Mission Planning System With the Flight Dynamics System
MOIMS Plenary p. 8SM&C-WS#02 10-14 May 04
WB - Schedule
Dec 03 Formation of WG12 Jan 04 White Book – draft 0.118 Feb 04 White Book – draft 0.25 Apr 04White Book – draft 0.330 Apr 04 White Book – draft 0.4May 04 White Book – Issue 1.0TBD Production of Blue books
MOIMS Plenary p. 9SM&C-WS#02 10-14 May 04
WB - Service Based Architecture
Defines the interface as a “contract”
Consumer (client) unaware of providers implementation
Popular with distributed and web based systems
Service consumer Service provider
Service directory
PublishLookup
Invoke
MOIMS Plenary p. 10SM&C-WS#02 10-14 May 04
WB - Layered Architecture
Helps modularise system
Supports reuse of components
Can only invoke lower layers
Replacement of layers is possible if combined with services
Low-levelservice
Mid-levelservice
High-levelservice
Invoke
Invoke
SLE
Service YSLE adapter
SLE
Service YSLE adapter
CORBA
Service YCORBA adapter
CORBA
Service YCORBA adapter
Remote Service YProvider
Standard service Y
ApplicationX
Standard service Y
SLE
Service YSLE adapter
SLE
Service YSLE adapter
Remote Service YProvider
Standard service Y
ApplicationX
Standard service Y
MOIMS Plenary p. 11SM&C-WS#02 10-14 May 04
WB - Space System Context
Uses RASDS methodology
Defines reference system
Defines operational context
Outlines clients of the system
Outlines operational areas of the system
Highlight “interoperability” interfaces
Spacecraft A2
Agency groundstation network
Commercial groundstation network
Other groundstation network
Spacecraft BSpacecraft A1
Spacecraft controlcentre
Payload operationscentre
Externalorganisation
MOIMS Plenary p. 12SM&C-WS#02 10-14 May 04
WB - Functional View
Defines areas of functionality
Taken from the operational context
Defines interactions between functional areas
Leads to service identification
FlightDynamics
M & C
Planning
AutomationScheduleExecution
Analysis
SoftwareManagement
Time &Location
Data ProductManagement
MOIMS Plenary p. 13SM&C-WS#02 10-14 May 04
WB - List of Functional Areas
M&C Core Monitor and Control functional area
Automation Concerned with control and management of the automation task
Schedule Execution Component responsible for executing the schedule possibly generated by the planning component
Planning Component responsible for the planning of future events in the system
Software Management
Onboard and also ground software version control, patching and release
Flight Dynamics Orbit vector determination, event schedule production etc
Time Time correlation
Location Responsibilities include ranging, tracking, and onboard position determination
Analysis Trending and analysis
Data Product Management
Control, management, persistence and transfer of the data product produced by the other components
MOIMS Plenary p. 14SM&C-WS#02 10-14 May 04
WB - Example: Modularity and FlexibilitySpacecraftOffline ground systems Online ground systems
FlightDynamics
M & C
Planning
AnalysisOnboardM & C
OnboardScheduleExecution
OnboardAutomation
OnboardPlanning
SoftwareManagement
SoftwareManagement
Data ProductManagement
Data ProductManagement
Time &Location
Offline ground systems Online ground systems Spacecraft
OnboardM & C
FlightDynamics
M & C
Planning
Automation
ScheduleExecution
Analysis
SoftwareManagement
SoftwareManagement
SoftwareManagement
Time &Location
(onboard GPS)
MOIMS Plenary p. 15SM&C-WS#02 10-14 May 04
WB - Information flow
Key task is to identify the information objects
Elaboration of the services will identify these objects
Will also define their attributes
FlightDynamics
M & C
Planning
Automation
ScheduleExecution
PlanningRequest
Action
Activity
Schedule
Parameter
Alert
MOIMS Plenary p. 16SM&C-WS#02 10-14 May 04
WB - Service Overview
External Node(s)
Ground Nodes
Remote Node (Spacecraft, Groundstation, Simulator etc)
Time & LocationService
SoftwareManagement Service
OperatorNotification
SM&C Service
Automation Service
Scheduling Service
Interaction Service
Flight Dynamics Service
Planning Service
File ManagementService
RemoteSM & C
RemoteSoftware
AnalysisOB SoftwareManagement
SC M & CDisplays
RemoteFile System
RemoteScheduleExecution
RemoteAutomation
RemoteAutomation
Proxy
SM & CProxy
External
RemoteSchedule
Proxy
RemoteSoftware
Proxy
RemoteFile System
Proxy
RemotePlanning
RemotePlanning
Proxy
Time & LocationProxy
RemoteTime & Location
AutomationScheduleExecution
FlightDynamics
Planning
MOIMS Plenary p. 17SM&C-WS#02 10-14 May 04
WB - List of services
M&C Core Monitoring and Control service
Automation Activity automation management
Scheduling Activity scheduling
Interaction Operator notification and interaction
Planning Constraint and resource planning
Flight Dynamics Orbit determination, flight plan generation, and manoeuvre generation
Time Time correlation
Location Tracking, ranging, and onboard position determination services
Data Product Management
File management and transfer, both ground based and onboard
Software Management Software versioning, patching, and release
MOIMS Plenary p. 18SM&C-WS#02 10-14 May 04
WB - Example: Core SM&C
Ground Node Remote Node
RemoteM & C
SC M & CDisplays
M & CBridge
Bridge hides the specificdetails of the serviceproviders from the serviceconsumers.The actual bridge to usedepends on the service andthe data carriers used.
MOIMS Plenary p. 19SM&C-WS#02 10-14 May 04
WB - Example: Core SM&C
Ground Node On-board Node
Ground Station Network
RemoteM & C
SC M & CDisplays
SLESpace Link
TransportAdapter
TransportAdapter
MOIMS Plenary p. 20SM&C-WS#02 10-14 May 04
WB - Summary
Produce CCSDS White Book Issue date is May 2004
Analysis of operational contextUse of services and layersIdentification of servicesWill lead onto definition of services
In other CCSDS books
MOIMS Plenary p. 21SM&C-WS#02 10-14 May 04
Outlook …
The proposed (chairman) goals for the SM&C Montreal Meeting are:
Finalise the WB and pass it to MOIMS AD/CESG as "Final Draft Informational" document (to become Green Book)
Select 2-3 high priority services identified in the WB and propose them as "CCSDS Proposed Standards" to MOIMS AD/CESG together with their schedule and resource profiles
Ratify MOIMS-SOIS MoU and pass it to MOIMS AD/CESG
Finalise agreement between SM&C and OMG SDTF for public review of the XTCE standard. Propose this to MOIMS AD/CESG as a joint CCSDS-OMG project
MOIMS Plenary p. 22SM&C-WS#02 10-14 May 04
Open Points (from last workshop)
Absence of NASA/Goddard from WG Closed with membership of D. Lokerson
Relationship with OMG Closed by CCSDS-OMG agreement
Handling of OMG XTCE standard Hopefully closed – see proposal for joint CCSDS-OMG project
Potential effort duplication with OMG Space DTF RFP-2 Hopefully closed – see joint CCSDS-OMG joint session (Wed PM)
MOIMS Plenary p. 23SM&C-WS#02 10-14 May 04
Cross-Issues
Coordination with other Areas SOIS: 2 telecons + MoU SEA: ensured by key members (PS, TY) MOIMS/NAV: to be further developed in the context of the draft WB