Mauro Pecchioli

1
MCS Infrastructure Status and Plans

Mauro Pecchioli TOS-GI
2
Achievements

• Requirements engineering for S2K Multi-mission
  and Multi-domain completed
• S2K Kernel R3.1 delivered on schedule (31/01/04)
• Final merge of R2.4.1 and R3.0 migrations
• General improvements (source code
  re-organisation, rationalisation of dependencies,
  build process improvements)
• Consolidation of numerous subsystems (TM
  processing, packets distribution, MISC server,
  log files)
• Various subsystem upgrades (Commanding,
  Packetiser, OBSM, Packet displays, EXIF servers)
• Servers redundancy management improvements
• Performance improvements (telemetry displays)
• Separate delivery of consolidated and upgraded
  ancillary systems (WEB-RM, TDRS, MCCM)
• S2K-R4.0 Architectural Design Review

3
Evolution Objectives

• Further expand functionality according to user
  needs
• Support advanced services (automation and data
  distribution)
• Architectural consolidation/evolution
• Introduce strictly layered approach (decouple
  MMI, underlying processing models and data
  access)
• Increase architectural openness and flexibility
• Increase robustness and reliability
• Enable performance improvements
• Maintainability/Usability
• Consolidate/re-engineer older subsystems/implement
  ations
• Create an appropriate test-bed and support
  automated testing (non-regression, performance,
  robustness)
• Adopt highly portable standards/technologies
  (e.g. Java, XML)
• Improve documentation quality (both from an
  editorial and technical standpoint).

4
MCS Target Infrastructure Overview
Ancillary Systems
To be decided if covered by infrastructure
Web Clients
MAS
GDBS
MCCM
GDDS
Man-Machine Interface
External Services
Local User Applications
Mission Control Systems Kernel Services
Ground Operations Systems Common Services
Operating System and COTS layer
SCOS-2000 Kernel
5
S2K-R4.0 Main Content (1/2)

• Support of multi-mission client workstations
• Support of multi-domain mission control systems
  (global processes), including redundancy
• Support of the Process Location Service
• Implementation of the System Control subsystem
• Harmonisation/rationalisation of the following
  existing implementations
• client applications interfaces to CPD/CPA
• client applications interface to MISC dynamic
  services
• inter-process communication management
• get/set methods of packet headers
• tasks status monitoring
• reports/printouts generation (all client
  applications)
• Support of hybrid client-server configurations

6
S2K-R4.0 Main Content (2/2)

• Events definition management re-engineering
• Command sources rationalization (decoupled MMIs)
• Repatriation of generic upgrades implemented by
  external users (H/P CCS, DLR System), including
  a.o.
• Multiple TM calibration curves and TM delta
  checks
• Support of on-line database patches via EXIF
• Support of TM configuration checks
• Functional upgrades, including a.o.
• OOL Summary Report generation
• Mimics editor (ILOG Views R5.0)
• Support of special PUS command/sequence
  parameter types
• Management of Sub-schedule ID for time-tagged
  commands
• Integration of TM Frames Replayer
• Integration of the Representative Test
  Environment (test database, data and tools).

7
S2K-R5.0 Main Content (1/2)

• Migration to Solaris 10 and Linux SUSE Enterprise
  9.0
• Final set of multi-domain requirements, primarily
  concentrating on multi-domain client applications
• Automation upgrades (support of system operations
  automation services and harmonised implementation
  of automation services implementation in the
  individual applications)
• Support of system automated regression testing
• New generation packet archive
• New generation files archive, including
  centralised management of all system files in the
  file archive and interface to the Generic File
  Transfer System (GFTS)
• Support of Long Term Archive and of interface to
  the new generation GDDS-R2.0

8
S2K-R5.0 Main Content (2/2)

• Support of reception of CLCW data via SLE R-OCF
  service
• Complete decoupling of TM parameters
  visualisation GUIs and processing models
• Support of generation and verification of SLE
  F-CLTU Throw Events (OPTION)
• Implementation of and migration to a new
  generation run-time database manager (OPTION)
• Implementation of the automatic retransmission of
  command frames failing on-board acceptance
  verification in CLTU mode (OPTION)
• Decoupling of user MMIs and underlying models
  (business logic) for all client applications
  (OPTION).

9
Ancillary Systems Evolution

• A group of experts has been set-up in order to
  identify the high-level requirements for the
  Mission Automation System (MAS), interfacing to
  S2K via a single access point to the automation
  services
• A new generation of the Generic Data Distribution
  System (GDDS R2.0) will be produced, supporting
  in a rationalised manner (single access point)
  all on-line, off-line and file based delivery
  services of parameters, packets and files
• WEB Clients a new generation of lightweight
  remote clients will be produced, relying on data
  access via GDDS R2.0
• The appropriate strategy to deploy the Generic
  Database System (GDBS) will be finalised
  following XASTRO-2 study completion.

10
Summary

• A long term strategy and a medium term plan have
  been established in agreement with the users.The
  schedule is very challenging but feasible. Main
  milestones are