INTEGRAL Mission Control System IMCS: an example of flexible integrated solutions supporting a compl

1
INTEGRAL Mission Control System (IMCS) an
example of flexible integrated solutions
supporting a complex and evolving Ground Segment

• SpaceOps 2002 Houston

2
Introduction

• Speaker
• Gianpiero Di Girolamo
• European Space Agency
• ESOC Darmstadt (Germany)
• Directorate of Technical Operation Support
• Ground Data System Division
• gianpiero.di.girolamo_at_esa.int

• Presentation
• Introduction
• IMCS Overview
• IMCS Main Servers
• IMCS Secondary Servers
• Diagram
• Main Server Failure
• Secondary Server Failure
• Conclusions

3
(No Transcript)
4
Main Servers

• IMCS hardware and software have been classified
  according following criteria
• Main application, namely those providing the
  basic and essential functionalities to guarantee
  S/C control and Safety
• NCTRS TM/TC Interface
• VC0 Telemetry Distribution
• VC0 Telemetry Archiving (Short Term)
• VC0 Telemetry Retrieval
• TM/TCSpacon
• Manual TC preparation
• Manual Commanding
• Automated Commanding
• IMCS Internal File Transfer System

5
Secondary Servers

• A second group of functions, indicated as
  Auxiliary, comprises those subsystem devoted to
  carry off-line tasks (IOBSM, IMPS) or non RT
  critical task (Long Term archiving) and/or tasks
  not essential for the direct monitoring and
  control of the spacecraft.
• Within IMCS following tasks belongs to this
  group
• Mission Planning (Timeline Validation and
  Generation)
• VC0 TM Long Term Archiving
• MADDS-A (VC0VC7 TM Frame Distribution)
• MADDS-B (VC0VC7 TM Frame Consolidation)
• IOBSM
• IMCS External File Transfer System

6
File (IFTS)
Raw TM Frames
(VC07)
F I R E W A L L
ISDS
Secondary SERVER
IFTS
RT TM to ISDC
RT TM to IFRD
7
LEOP Scenario Main Server Recovery
VC0VC7 TM
VC0 VC7 TM
VC0 TM
IFTS
TC
TC
INCTRB
F I R E W A L L
8
LEOP Scenario Main Server Recovery
VC0VC7 TM
VC0 VC7 TM
VC0 TM
IFTS
IMCA
TC
TC
IMCB
VC0 TM
VC0 VC7 TM
F I R E W A L L
9
Main Server Failure Recovery Procedure

• The failure recovery procedure comprises
  following steps
• Client N (with commanding capability) no action
• NCTRS operator connects TC link on INCTRB
  
  
  
  time lt 1 minute
• Each Client set IMCB as Prime server (pushing a
  button) time 30
  seconds
• External IFTS needs to be restarted on IDDB and
  on all External instances time 5 minutes
• Data archiving not affected
• Data distribution needs to be stopped on IDDA and
  restarted on IDDB time 1 minute
• Turn-around time
• Kernel function less then 1 minute (if well
  coordinated)
• Auxiliary functions 5 minutes

10
Secondary Server Failure
VC0VC7 TM
VC0 VC7 TM
IDDA
VC0 TM
IFTS
TC
IMCA
TC
INCTRB
F I R E W A L L
11
Secondary Server Failure
VC0VC7 TM
VC0 VC7 TM
VC0 TM
IFTS
TC
IMCA
TC
IMCB
INCTRB
F I R E W A L L
12
Secondary Server Recovery

• The failure recovery procedure comprises
  following steps
• IDDB is rebooted with IDDA identity time lt 1 hour
• Applications will be re-started on successful
  re-boot
• IFTS time 5 minutes
• MADDS time 5 minutes
• Data Archiving and Distribution outage lt1 hour
• Total turn-around time ca. 1 hour
• Data completeness is affected since long-term
  archive would have a gap
• This is considered acceptable by INTEGRAL MOC
• We are currently studying solutions to
  consolidate TM on the Long-Term archive in the
  occurrence on such situation

13
Conclusions

• The move from centralised architecture as those
  previously in use at the ESA MOC to the highly
  distributed architecture based on the new
  SCOS-2000 infrastructure represented also a
  fundamental change in the definition of a
  redundancy concept.
• The consolidated concepts defined and
  consolidated over more than a decade onto the
  centralised SCOS-1 based MCS although had
  constituted a solid basement had to be reviewed
  and amended in order to fit with the new
  architecture and, in the particular case of the
  INTEGRAL mission, with the complexity of the
  System External interfaces.
• The big challenge IMCS has undertaken as first
  SCOS-2000 Client Mission is to define and pioneer
  a redundancy concept which will be of great
  benefit for the upcoming missions.