| Previous | Table of Contents | Next |
The specification addresses the need for a standardized information model capable of supporting TM/TC definitions across the
broadest possible range of space domain activities. The goal is to allow TM/TC definitions to be exchanged between different
organizations and systems, often at the boundaries of mission phases, without the need for customized import/export, re-validation,
or even re-implementation of mission databases.
The scope of this specification is limited to satellite telemetry and commanding data constructs necessary to support satellite
and payload data design:
• Telemetry data definitions including support for CCSDS packets as well as TDM frames.
• Data manipulation algorithms to support packaging and unpacking of individual data items.
• Commanding data definitions including command identification, argument specification, and validation criteria.
• Data representation definitions.
• Data properties including such things as its default value, validity criteria, and data dependencies.
• The definition of extensible formats such that blocks of information (whether frames of data that are not decommutated or object references or object method calls) can be portrayed in this architecture.
The scope of this specification does not extend to:
• Data distribution mechanisms.
• Command and data protocol specifications.
• RF or analog stream characterization.
• Data groupings including aggregation and coherent data sets.
• Data Representation (visualization properties).
• Scheduling configuration properties.
• Orbital properties. The specification addresses only the definition of TM/TC data, and not the transfer of live or historical
TM/TC data.