OPSGIB

1
General Infrastructure

• Y.Doat
• ESOC - OPS-GIB
• 15th 16th June 2004

2
Infrastructure

• Monitoring Control (STC2, MCM).
• Telemetry, Telecommand (TMP, TCE, TMTCS).
• Intermediate Frequency Modulation System (IFMS).
• NCTRS / NIS (Network Interface System).
• EMS (ESTRACK Management System).
• ESA SLE gateway.
• Software Packages (GSSC, SLE API).

3
Station Equipment
Station Equipment
GSTS
STC Local WS
MCM/IFMS/TMTCS Local Display
Station Computer
MCM
GSSC/GMMI
FEC
Server
TMTCS
IFMS
GSSC/GMMI
GSSC/GMMI
STC Remote WS
TC
TCS
SLE API
Uplink Modulator
TM
TPS
TCDS
NCTRS
Ranging, Doppler, Meteo, AGC
PSS
4
Monitoring and Control

• Centralised ground station monitoring and control
  system.
• Used for pre-pass configuration, monitoring and
  control during the pass.
• Local or remote operator position.
• Monitoring cyclic, on-change and on-request.
• Flexible tailoring capability.

5
MC Environment (STC2, MCM) (Current )
Remote operator WS
GFCC LAN
LAN Time Server
Station MC LAN
FEC
MCM
IFMS
TMP
TCE
NCTRS
SSU
SSU
SSU
SSU
6
Monitoring and Control (Future )
TMTCS
Local MC Server
Corba
IFMS
IEEE
MCM
Basic MC
Remote MC-WS
TMTCS
Local MC Server
Corba
IFMS
IEEE
MCM
Basic MC
7
TMTC System (Future )

• Run in a single box.
• SLE Services
• 1st phase RAF, RCF and CLTU.
• 2nd phase FSP, OCF.
• SLE Service Management via the STC2.
• SLE Service Management based on the SICM tool
  generating SIC Files.

8
TMTC Environment (Future )
TM TC
LAN
Op. LAN
Router
V.11 or ??
TC Verification
Router
LAN Time Server
Station MC LAN
NCTRS
STC2
SCOS2000
9
NCTRS (Current )

• Ground-Station network front-end enabling
  communication between
• Mission Control System kernel (MCS).
• Mission Planning System (MPS).
• Flight Dynamic System (FDS).
• And the ground-station equipments using
• PCM Services (SDID based).
• ESA Services (OSI based).
• Space Link Extension (SLE based).
• Initiated activity Multi-mission support.

10
NCTRS Environment (Current )
SLE Services
MCS
MPS
FDS
ESA PCM Services
11
NIS Network Interface System(Future )

• NCTRS Replacement
• Functionality
• SLE interfaces to Ground-Station
• Routing of TM/TC for MCS at ESOC.
• Configuration
• Multi- or Single-mission
• Independent from MCS.

12
NIS Environment(Future)
NIS
CLTU, FSP
ESTRACK
TC Files
RAF, RCF, ROCF
TC
MCS
TM Files
TC Files
TM
TM Files
CLTU, FSP
External Users
TC Files
RAF, RCF, ROCF
TM Files
13
EMS Role (Future)

• Planning and SchedulingBased on the User
  Requests, the EMS prepare the schedule based on
  the facilities and their status.
• Schedule executionThe schedule is downloaded to
  the facility for execution.
• Ground facility monitoringThe EMS monitors the
  execution of the schedule and logs the execution
  steps.

14
EMS Environment (Future)
Flight Dynamics
EMS
External Provider
User Requests
External Requests
Utilization Manager
Operational Requests
Facilities
MISSION A
Spacecraft Control
TM, TC, TRK
15
S/w Package ESA SLE API

• Implement RAF, RCF and CLTU.
• Planned extensions FSP, OCF.
• Maintained under Solaris8, Linux, Win-2000,
  Open-VMS.
• Validated / not maintained under Win-NT.
• Systems concernedNCTRS, Simulator, Future TM/TC
  System.

16
S/w Package GSSC-GMMI (Current/Future)

• Implement
• MC Protocol subsystem and STC2 using OSI.
• Generic man-machine interface.
• Plans
• MC ProtocolOn-going migration to CORBA.
• Man-machine interface Web technology study.
• O.S. Solaris 2.5.1 and Solaris 8.
• Systems concerned IFMS, TM/TC, MCM.

17
S/w Package Configuration Report System (CRS)
(Future)

• Implement
• Configuration Reporting Mechanism
• XML File.
• Plans
• First implementation on IFMS.
• Possible use on TMTCS and MCM.
• O.S. Solaris 8.

18
Conclusion

• Monitoring and Control enhancement /
  replacement.
• ESTRACK Management System (EMS) Development
• Network Interface System (NIS)Development
• Software reusability to be promoted.