Gerd Enderlein, DLRGSOC

1
DLR-SMCS A GenericMCS and Central Check-out
System for the DLR Missions CHAMP, GRACE, and
theTerraSAR-X CCS

• Gerd Enderlein, DLR/GSOC
• Heinz Wacker, DLR/GSOC
• Robert Messaros, Siemens Austria
• Heinz Cech, Siemens Austria

2
A new Satellite Monitoring Control System
(SMCS) and TerraSAR CCS

• DLRs Objectives
• One single generic system for SMCS and TerraSAR
  CCS, which can be configured for all DLR/GSOC
  satellite missions
• Integrated TC/TM/MMI/CCS modules in one software
  package
• Improved MMI for GSOC operations concept
• Compatibility with existing and future
  (NCTRS/SLE) GSOC multi mission system
  infrastructure
• Compatibility with the legacy multi mission
  system
• Operating System (Linux, Unix)
• Computer platform workstation vs. PC
• User friendly and standardized configuration
• Flexible usage of SMCS in MC, EGSE simulator
  environment
• Maintenance aspects

3
A new Satellite Monitoring Control System
(SMCS) and TerraSAR CCS

• Operations Concept for computer/platform
  configuration
• Option for
• Hybrid Server / Client Configuration or
• Homogeneous Server / Client Configuration
• Hybrid Sun Server/Solaris PC Clients/Linux
• For mission operation systems
• Homogeneous Server / Client Configuration (Linux)
• For mission operation systems
• For AIT
• Stand-alone PC (SCOS in-a-box) for
• database configuration
• simulator applications

4
Major Functional SCOS-2000 Extensions - General

• Operations Concept
• Automatic Configuration Check
• Generic Data Quality Checks
• Selection from TQD (Telemetry Query Display) out
  of OOL display
• Critical Command Handling (acknowledgement in
  manual stack MMI)
• Command Handling (editable ASCII parameter, ...)
• TMPRINT extension (Selective Parameter Files
  Snapshot Files)
• MMI improvements (header information in
  monitoring displays, baptizing of manual stacks,
  ...)
• Test Mode for Packetiser
• Fast off-line Processing Tool
• ODL (legacy command definition) to Manual Stack
  Converter

5
Major Functional SCOS-2000 Extensions
CHAMP/GRACE

• In present GSOC infrastructure
• CLCW I/F Packetiser ? Command Releaser
• Command releaser interface to legacy multi
  mission environment (NASCOM format)
• GCRS Task To Handle CLTUs in NASCOM Blocks and
  Connect to GSOCs Transmission Server
• CAP (CHAMP application packet) I/F in CTM and TMR
  task to handle CAP and connect to GSOC legacy
  multi mission system
• I/F to access externally generated raw data from
  file
• Integration of CHAMP application packet
  extraction in Packetiser (normal NCTRS interface)
• TCP/IP transfer frame interface in Packetiser on
  transfer frame level
• to legacy multi mission system and
• offline file access
• Routing/distribution of extracted CAPs to
  external users

6
Major Functional SCOS-2000 Extensions
CHAMP/GRACE

• CHAMP/GRACE Mission specific
• CLCW I/F Provider
• GPS based Time Correlation
• Special command handling
• Variable packets
• Special non-standard payload command fields
  (length, check-sum) and decalibration functions.
• MIB Converter
• Simulator to feed offline CHAMP data to
  Packetiser

7
Major Functional SCOS-2000 Extensions - TerraSAR

• TSX-CCS Mission specific
• Interface Manager IFMGR adaptations
• Source Packet Interface
• Power SCOE TSX Converter
• Interface task for encryption of TC Segments
• Fractions of seconds in time tags (manual stack)

8
A new Satellite Monitoring Control System (SMCS)

• Current missions at GSOC using SCOS-2000
• Jan 2004 CHAMP) (launched 15-July-2000)
• Sep 2004 GRACE) (launched 17-mar-2002, 2
  sats.)
• July 2003 TerraSAR-X (launch planned for April
  2006)
• includes the integration of SCOS-2000 in EGSE
• ) full operational
• SCOS-2000 planned to be the baseline for all
  new satellite missions operated from GSOC

9
Key Issues for Migration of GSOC MCS/CCS
Infrastructure to SCOS-2000
Key Points
Performed Actions
Integration in GSOC GS Infrastructure Migration
of legacy MIB Data Mission specific (CHAMP,
GRACE and TSX) functionality Compliance with
DLR/GSOC Operations SUN-WS/PC Platforms
Performance ? Availability ? Test and
Verification Training

• Enhancement and modification of SCOS-2000
• TC-Releaser and TM-Receiver (CTM/GCRS)
• TM and TC MIB Converters
• (semi) automatic TM/TC MIB Validation
• Adaptation of Generic Packetiser/TC Releaser
• SCOS-2000 functional extensions (ECRs)
• Legacy MIB Conversion and MIB Configuration
• SCOS-2000 functional extensions (ECRs)
• SCOS-2000 Configuration
• Implementation of Hybrid (Solaris/Linux)
  solutionand Homogenous (Linux) solution
• Starting with early SCOS-2000 CHAMP prototype
  installation up to current SCOS-2000 2.3e
• Tutorial Courses for Main features / Learning by
  Doing

10
TM/TC Ground Segment Overview (CMP/GRC)
- current environment
FDS
MPS
ExternalUsers
WebServices
Data storage
Off-line TM processing System (leg.)
NRTadd-ons (leg) TTC image, ..
External command I/FODL (text)?Manual Stack
Conversion
SMCS/ SCOS-2000 (client)
SMCS/SCOS-2000 (server)
TM Client
TM Distribution
Ground Stations Infra-structure
TM Receiver (CTM)
R/T TM Pre-processing (CHAMP Application Level)
TC Releaser (GCRS)
R/T TC Post-processor (CLTU, NASCOM-IF)
TC source
TC Handler
11
TM/TC Ground Segment Overview (CMP/GRC)
- new environment
FDS
MPS
ExternalUsers
WebServices
Data storage
Off-line TM processing System (leg.)
NRTadd-ons TTC image, ..
External command I/FODL (text)?Manual Stack
Conversion
SMCS/SCOS-2000 (server)
SMCS/ SCOS-2000 (client)
TM Client
TM Distribution
Ground Stations Infra-structure
Generic Packetiser
SLE / NCTRS
TC source
TC Releaser
TC Handler
Legacy display system (SATMON)
12
TerraSAR CCS Overview
13
Migration of Legacy MIB
FRAMTEC based TM-MIB Files
CHAMP SCOS-2000 TM MIB Files (ASCII)
TM-MIB Converter
SCOS-2000 Server
Manually created TM MIB Files
SCOS-2000 MIB Import Programs
MIB
Manually created TC MIB Files
export
TC-MIB Converter
Legacy TC MIB (MS Access)
CHAMP SCOS-2000 TC MIB Files (ASCII)
ASCII
14
Conclusion

• Main objectives
• PC based SCOS-2000 (Linux)
• Mission specific customisation
• Scalability and flexibility (hybrid systems)
• Operational environment using SCOS-2000 in
  homogeneous configuration (Linux) for a better
  performance
• Smooth integration in operational GSOC
  infrastructure
• SCOS-2000 in Check-out system (TerraSAR-X EGSE)
• Implementation NCTRS SLE I/F at GSOC
• Next steps
• MIGRATION to Release 3.1
• Implementation of TerraSAR-X specific changes
• Generic Framework Task for Power
  SCOE/Encryption/new modules
• New Extensions of SCOS-2000 for DLR Operation
  Concept
• Connection of the legacy SATMON (using EXIF)
• The harmonisation of mission operation tools
  leads to increased efficiency and creates new
  opportunities for future co-operations.