OrbitML The Spacecraft Flight Dynamics Markup Language

1
OrbitMLThe Spacecraft Flight Dynamics Mark-up
Language
6th NASA-ESA Workshop on Product Data Exchange

• Fran Martínez
• Alberto Agueda
• September 15th, 2003

2
Contents

• Introduction to OrbitML
• OrbitML scope
• OrbitML design logic
• OrbitML datatypes and magnitudes
• OrbitML structure
• OrbitML present and future
• Conclusions

3
Introduction to OrbitML

• Flight Dynamics core activity in space missions
• XML helps in many disciplines lets use it for
  FD OrbitML
• OrbitML design drivers
• Heritage from European FD packages
• improved consistency and portability
• Readability
• Suitability for automation
• Extensibility to other space applications
• Navigation
• Data Processing
• Mission Planning

4
OrbitML scope

• OrbitML goal standard for FD data exchange
• OrbitML covers the whole s/c FD spectrum,
  including
• Orbit and attitude determination prediction
• Events generation
• Geodetic Applications
• Navigation
• OrbitML handles related concepts
• Satellites, transponders, ground stations,
  physical models, ...

5
OrbitML design logic

• OrbitML design driver Readability
• OrbitML data generated by SW tools
• Easy to compress (XML text file)
• XMILL, XGRIND, ...
• OrbitML is a rich source of FD metadata
• Data model
• hierarchy through XML
• data typing through XML DTD/Schema
• extended by OrbitML
• Data relationship
• basic by XML and DTD/Schema
• extended by OrbitML

6
OrbitML design logic

• OrbitML data model derived from GMVs wide
  experience in FD and S/C operations
• Exploit the heritage from FD SW packages most
  commonly used throughout Europe
• Foresee extensibility (e.g. navigation, mission
  planning, )
• OrbitML data types definition includes
• Data type (string, double, boolean, ...)
• Format (lexical representation)
• Space value (possible values)

7
OrbitML design logic

• OrbitML design sequence
• Analyse FD concepts
• Identify physical magnitudes
• Define basic datatypes
• Define composite datatypes
• Generate the OrbitML structure top-down
• OrbitML datatypes
• Compliant with XML Schema
• Ensure compliance with future versions
• Design with UML notation
• OrbitML ? Object Oriented
• Object Oriented ? OrbitML

8
OrbitML datatypes and magnitudes

• OrbitML validation based on XML Schema
• DTD does not support strong datatyping
• Schema provides lexical/semantic validation
• OrbitML basic datatypes
• Compliant with XML Schema
• string, boolean, long, double, dateTime, ...
• Not limited to XML Schema
• Specialisation
• Extension
• OrbitML physical magnitudes
• Represent generic physical concepts
• Include units, frame, format, scale, ...
• Define default values

9
OrbitML datatypes and magnitudes
10
OrbitML datatypes and magnitudes

• OrbitML higher level magnitudes
• Represent complex physical magnitudes
• Ease the definition of FD concepts
• Aggregation
• State vector time, position, velocity
• Extension (Inheritance)
• Time specialisation of dateTime
• OrbitML defines FD complex concepts
• Satellite, station, site, transponder, ...
• Event, orbit, attitude, ...
• Standard Identifiers PRN, COSPAR, DOMEX,

11
OrbitML structure XML Schema View
12
OrbitML structure UML View
13
OrbitML present and future

• Present
• OrbitML specification complete
• http//www.OrbitML.com
• Documentation available
• On-line validation against OrbitML Schema
• OrbitML partially integrated in focusSuite
• CCSDS support (ESOC contract)
• XML specification for OPM and OEM
• Reuse of OrbitML schema elements
• Extension to OrbitML
• CCSDS/XML conversion tools
• Reuse of OrbitML API elements
• Based on xerces-c/SAX
• Proof of design reusability

14
OrbitML present and future

• Future
• OrbitML to be extended to other disciplines
• Geodetic applications
• Navigation
• Mission planning
• Data processing
• OrbitML API formaliation
• Xerces-c/SAX
• Stylesheet converters
• OrbitML implementations
• Fully integrate into focusSuite
• Other FD packages (e.g. NAPEOS)

15
Conclusions

• OrbitML
• First comprehensive implementation for FD
• Uniform layer for exchange of data between
• (modules of) applications
• departments within the same space agency
• different space agencies
• Provide common validation means
• Exchange data along with their units
• OrbitML standard for FD data exchange