1. MOIMS MO & Nav Functions, Services & Interfaces CCSDS Ref Arch Discussion 20 Oct 2015

2. Approach Use provided MO services (Nestor) & Nav service (Nav WG) diagrams Edit them minimally for clarity and consistency so traceability is clear – For now the diagrams remain in their original, and inconsistent, styles Show how they relate to each other and to CSS services Attempt to clarify and discriminate among: – Data structures and formats – Functions (and groupings) – Service interfaces

3. Automation M&C TM Processing Parameter Processing TC Processing Schedule Execution Prodedure Execution Manual Execution Event Driven Execution On Board Schedule Management Comman Verification Command Releaser Procedure Processing Procedure Generation CSTSCSTS SM TM TC Planning Engine Planning Request Processing Schedule Generation FDS MO Automation Services Mission Automation Planning Schedule MO Scheduling Services S/C Schedule P&S MO Scheduling Services MO Automation Services Procedure Data MO M&C Services Activity / Parameter / event / Packet Monitoring S/C Schedule Report SOCs / PIs MO Planning Services MO Mission Data Product Distribution Services MO Scheduling Services MO Automation Services MO NAV Services ODMTDM FDS MO Navigation Services ODM, EVM, SMM SMM, ADM,ODM, CDM Planning Requests Mission Schedule Monitored Data MO NAV Services ODM, ADM, PRM MO M&C Services MO File Mngmt Services CSTSCSTS MO Planning Services Ground Station Resource Planning Original from Nestor

4. MO Automation Services MO M&C Services TM Processing Parameter Processing TC Processing Schedule Execution Procedure Execution Manual Execution Event Driven Execution On Board Schedule Management Command Verification Command Releaser Procedure Processing Procedure Generation CSTS/SLECSTS/SLE SM TM TC Planning Engine Planning Request Processing Schedule Generation FDS MO Automation Data Mission Automation Planning Schedule MO Scheduling Data S/C Schedule P&S Services Procedure Data Activity / Parameter / event / Packet Monitoring S/C Schedule Report SOCs / PIs MO Planning Data MO Mission Data Product Distribution MO Scheduling Data MO Automation Data ODM TDM FDS ODM, EVM, SMM SMM, ADM, ODM, CDM Planning Requests Mission Schedule Monitored Data (MD) NAV Data ODM, ADM, PRM MO M&C Data MO File Data SMSM MO Planning Data Ground Station Resource Planning MO Data Services Tracking Data (TD) NAV Data Comm Service Request NAV Data MO Scheduling Data MO M&C Data MO Automation Data Modified for Consistency MO Automation Data NAV Data Mission Planning Service Request

5. Notes on Revised MOC with MO Services diagram Provides view of the MO, FDS, & CSS interactions, showing major interfaces (“grey boxes” show groups of functions, exchanged data structures are shown as green boxes) All data transfers are shown as data, not as “services”; data exchange structures and formats must be standardized for interoperability Service Interfaces are explicitly shown associated with the functions that provide them Five MOIMS Service groups shown: Navigation (FDS), Monitor & Control (M&C), Automation, Planning & Scheduling (P&S), MO Data Services Data archiving, auditing, and Robotics etc are not shown for now CSS Services (SM, CSTS, SLE) are shown explicitly as service providers Not all of the service requests nor data flows to/from the SOC / PI are shown (mission planning & automation requests, commands, science data, archival data, etc, etc) FDS to MO interactions are shown on a separate Nav WG chart (with edits) NOTE: most of the service interfaces could continue to be mission specific (as now), or converted to an MO Service framework, or just use TGFT- like services, or …

6. Trk Stn SchedScienceMission S/C Team S/C NOTE: Exchanges may be predicted future data or reconstructed actual data, depending on the message type Messages ADM = Attitude Data Message CDM = Conjunction Data Message EVM = Events Message NHM = Navigation H/W Message ODM = Orbit Data Message PRM = Pointing Request Message SMM = Spacecraft Maneuver Message TDM = Tracking Data Message Functions Att Det = Attitude Determination function Cmd Gen = Command Generation function Mission S/C Team = Spacecraft Team function Mnvr = Maneuver Design function Orbit Det = Orbit Determination function S/C = Spacecraft Sched = Scheduling function Science = Science function Trk Stn = Tracking Station SMM, ADM, PRM SMM TLM Data NHM ODM, EVM PRM ADM ODM EVM, SMM ODM TDM CCSDS Navigation Working Group Technical Program SMM Orbit Det Mnvr Att Det Navigation CDM Conjunction Assessment ODM Cmd Gen Commands PRM SMM, ADM, ODM Version 4.2 Richon idea CDM SMM EVM ADM Original from Nav WG

7. Trk Stn Fncs Science Mission S/C Ops Fncs S/C Fncs SMM, ADM, PRM TLM Data NHM PRM ADM ODM EVM, SMM ODM TDM SMM Orbit Det Mnvr Att Det Navigation CDM Conjunction Assessment ODM Cmd Gen Commands PRM SMM, ADM, ODM CDM SMM EVM ADM Uses Generic File Transfer Sched SMM ODM, EVM CSTSCSTS SLE SM M&C FDS Navigation Working Group w/ GFT Services N.B. Nav stds are all interoperable data format specs P&S Mission S/C Ops Team Processes Flight Dynamics Team Processes

8. Notes on Revised Flight Dynamics (FDS) Services diagram Provides view of the separate FDS to MO interactions, showing major interfaces (“circles” are functions, types of data structures are named on connectors) All data transfers are shown as data, not as “services”; data exchange formats must be standardized for interoperability Service Interfaces are explicitly shown associated with the functions that provide them, but they may not offer explicit service interfaces Navigation (FDS) services are shown, using the functions and data structure standards defined in the Nav WG diagram (Richon v 4.2) CSS Services (SM, CSTS, SLE) are shown explicitly as service providers All of the elements are re-named, where needed, to produce a consistent functional view; teams and processes are separately indicated NOTE: most of the service interfaces could continue to be mission specific (as now), or converted to an MO Service framework, or just use TGFT- like services (as shown)

9. NOTE: Exchanges may be predicted future data or reconstructed actual data, depending on the message type Messages ADM = Attitude Data Message CDM = Conjunction Data Message EVM = Events Message NHM = Navigation H/W Message ODM = Orbit Data Message PRM = Pointing Request Message SMM = Spacecraft Maneuver Message TDM = Tracking Data Message Functions Att Det = Attitude Determination function Cmd Gen = Command Generation function Mission S/C Team = Spacecraft Team function Mnvr = Maneuver Design function Orbit Det = Orbit Determination function S/C = Spacecraft Sched = Scheduling function Science = Science function Trk Stn = Tracking Station CCSDS Navigation Working Group Terms

10. Trk Stn ScienceMission S/C Team S/C SMM, ADM, PRM TLM Data NHM PRM ADM ODM EVM, SMM ODM TDM SMM Orbit Det Mnvr Att Det Navigation CDM Conjunction Assessment ODM Cmd Gen Commands PRM SMM, ADM, ODM CDM SMM EVM ADM MO Navigation Services Sched SMM ODM, EVM CSTSCSTS SM M&C FDS Navigation Working Group w/ MO Services Nav WG with mods From Nestor