EGOS Workshop 811 November 2005

1
EGOS WorkshopOrbitML A STEP TOWARDS FLIGHT
DYNAMICS SYSTEMS HARMONISATION E. Rivero and F.
Martinez GMV S.A. Isaac Newton 11, Tres Cantos,
28760, Spain.

• EGOS Workshop 8-11 November 2005

2
Overview

• Flight Dynamics Systems (FDS) from EGOS
  perspective
• An effective reusable FDS framework
• FDS interfaces standardisation and OrbitML
• Conclusions

3

• FDS from EGOS perspective

• EGOS Workshop 8-11 November 2005

4
FDS from EGOS perspective

• EGOS framework aim is the harmonisation of ESA
  Ground Operations Systemsincluding FDS? In
  principle YES.
• Create a reusable framework for future missions
• Apply a common S/W development approach
• Platforms and O.S.
• Languages
• Methodology (O-O)
• Test Tools
• Project control and documentation
• Standards
• Definition of a Ground Operations System
  Reference Architecture with clear boundaries and
  interfaces between subsystems

5
FDS from EGOS perspective

• A reusable framework
• Integration in EGOS
• Reference Architecture
• Following common s/w
• development approach
• as far as possible
• -Harmonisation efforts
• at internal level

6
FDS from EGOS perspective

• Similar situation faced at GMV in 1999 (at a
  lower level)

GMV FD experience Clear requirements Latest
tech. trends
FDS1
FDS2
FDS3
Consistent set of products
Initial disharmony
7

• An effective reusable FDS framework

• EGOS Workshop 8-11 November 2005

8
An efficient FDS reusable framework

• Step 1 Definition of driver requirements

• Minimise development, training and maintenance
  effort by increasing internal harmonisation (s/w
  reuse, common operational approach)
• Modernise s/w development approach

ESOCs ORATOS Next Generation

• Generic framework for development, integration
  and operation of FD applications
• Multi-satellite, multi-mission, multi-user
• Portability
• Expandability easy integration of third-party
  s/w
• Free of third party licenses

The focusSuite experience
9
An efficient FDS reusable framework

• Step 2 Define methodology

• Knowledge management system
• S/W development environment S.O., languages,
  methods.
• H/W platform
• Validation approach

ESOCs ORATOS Next Generation
EGOS

• Identification of reusable (NAPEOS, PEPSOC) and
  newly required computational modules
• Define s/w and h/w target environments
  Unix,Linux,Windows, FORTRAN 90-95, C, C, TclTk,
  any h/w platform
• Validation approach regression test tool

The focusSuite experience
10
An efficient FDS reusable framework

• Step 3 Execution

• Knowledge capture
• Define future architecture and internal
  interfaces
• Define external interfaces
• Re-implementation and validation

ESOCs ORATOS Next Generation
EGOS

• Client-server architecture assuring a clear
  separation between computational modules and an
  advanced HMI
• Architecture allows for easy integration of new
  computational modules
• Next stage external interfaces based on OrbitML
  (Galileo FDF)

The focusSuite experience
11
FDS interfaces standardisation and OrbitML

• EGOS Workshop 8-11 November 2005

12
FDS interfaces standardisation and OrbitML
Current standardisation efforts
Other agencies (CNES, DLR, NASA, JAXA...)
MPS
MCS
EGOS
CCSDS
FDS

• Different scope and approach but same technology
  XML
• Easy translation OrbitML to/from CCSDS
• OrbitML is being introduced in ESA
• EGOS
• OPS-GN extension to Navigation data and
  on-going development of FORTRAN, C and C APIs
  for data access
• GALILEO FDF

13
FDS interfaces standardisation and OrbitML

• OrbitML goal standard for FD data exchange
• OrbitML design drivers
• Heritage from European FD packages
• improved consistency and portability
• Readability
• Suitability for automation
• Exhaustive. Covers the whole s/c FD spectrum,
  including
• Orbit and attitude determination prediction
  (tracking, ranging)
• Events generation
• Navigation
• Databases (s/c, stations, transponders, etc)
• Extensibility to other space applications

14
FDS interfaces standardisation and OrbitML

• OrbitML design sequence
• Analyse FD concepts
• Identify physical magnitudes
• Define basic datatypes
• Define composite datatypes
• Generate the OrbitML structure top-down
• OrbitML validation based on XML Schema
• Schema provides lexical/semantic validation
• OrbitML basic datatypes
• Compliant with XML Schema
• string, boolean, long, double, dateTime, ...
• Not limited to XML Schema
• Specialisation
• Extension

15
FDS interfaces standardisation
16
FDS interfaces standardisation and OrbitML
17
FDS interfaces standardisation and OrbitML

• Present and future of OrbitML

• OrbitML specification complete v1.1
• http//www. OrbitML .com
• Documentation available
• On-line validation against OrbitML Schema
• OrbitML partially integrated in focusSuite
• CCSDS support (ESOC contract for OPS-GF)
• OrbitML to be extended to other disciplines
• Mission planning
• Data processing
• Geodetic applications
• OrbitML API finalisation and specification v1.2
  (ESOC contract for OPS-GN)

18
Conclusions

• EGOS Workshop 8-11 November 2005

19
Conclusions

• EGOS guidelines can be applied to FDS in what
  respects
• Common development approach (S.O., languages,
  platforms, methods, etc)
• Integration in Reference Architecture
• External interfaces
• Additionally, FDS internal harmonisation is
  desirable. Having common external interfaces is a
  first step.
• OrbitML is a mature FD data representation
  current baseline for FDS-MCS interface
• OrbitML projects on-going EGOS, OPS-GN, GALILEO