ISO 13526-2010 amd1-2015 PDF

Full title and description

ISO 13526:2010/Amd 1:2015 — Space data and information transfer systems — Tracking data message — Amendment 1. This amendment updates and clarifies the Tracking Data Message (TDM) format specified in ISO 13526:2010 (which adopts the CCSDS TDM recommended standard), providing precision on range observables, clock-bias reporting, participant ordering and Delta-DOR session conventions to improve interoperability of spacecraft tracking data exchanges between agencies and ground stations.

Abstract

This amendment to ISO 13526:2010 revises the Tracking Data Message (TDM) specification to remove ambiguities and to align descriptive and data-entry conventions with operational needs. Key changes clarify whether two‑ and three‑way range observables represent round‑trip or half‑round‑trip light time, define the intended sign and participant ordering for CLOCK_BIAS entries, specify rules for Delta‑DOR clock‑bias entries per VLBI session, and correct ordering/labeling inconsistencies. The amendment is short (technical change) and intended to be applied together with the base 2010 standard.

General information

• Status: Published (amendment to ISO 13526:2010)
• Publication date: 16 June 2015
• Publisher: International Organization for Standardization (ISO)
• ICS / categories: 49.140 — Space systems and operations
• Edition / version: Edition 1 (ISO 13526:2010) with Amendment 1 (2015)
• Number of pages: Main standard: ~80 pages; Amendment 1: 3 pages (technical amendment)

Scope

The amendment applies to ISO 13526:2010's Tracking Data Message (TDM) format for exchanging spacecraft tracking data between space agencies and ground stations. It clarifies formatting and semantic rules for range and clock observables, participant labeling, and session-level conventions (notably for Delta‑DOR/VLBI sessions), ensuring consistent interpretation and processing of tracking data used for spacecraft tracking, navigation and mission support.

Key topics and requirements

• Clarification of RANGE observable semantics for two‑way and three‑way tracking: explicit statement whether observables use round‑trip light time or half the round‑trip light time.
• Revised guidance for CLOCK_BIAS entries: clear definition of participant ordering and the observable sign convention (observable calculated as participant_2 minus participant_1, e.g., UTC – station_time).
• Delta‑DOR (differential one‑way ranging) session rules: provision of a single CLOCK_BIAS per daily VLBI session with time‑tagging and exception handling if station clocks reset mid‑session.
• Corrections to ordering and labeling of participants in clock bias data to reduce ambiguity in automated processing.
• Small editorial and technical amendments intended to improve interoperability with CCSDS TDM implementations and mission operations software.

Typical use and users

Applied by space agencies, mission operations centres, and ground station operators exchanging tracking data in interagency cross‑support contexts. Typical users include spacecraft navigation teams, tracking-data analysts, ground-segment engineers, telemetry/telecommand system integrators and software developers implementing TDM readers/writers in mission data systems.

Related standards

This amendment directly amends ISO 13526:2010 and aligns the ISO text with the CCSDS Tracking Data Message recommended standard (CCSDS 503.0 family). It is used alongside other CCSDS space data and information transfer standards and with ISO standards addressing space systems and operations where coordinated tracking and data exchange practices are required.

Keywords

Tracking Data Message, TDM, ISO 13526, CCSDS 503.0, range observable, clock bias, Delta‑DOR, VLBI, spacecraft tracking, ground station interoperability, amendment 2015

FAQ

Q: What is this standard?

A: ISO 13526:2010/Amd 1:2015 is an amendment to the international standard that defines the Tracking Data Message (TDM) format for exchanging spacecraft tracking data between agencies and ground stations.

Q: What does it cover?

A: The amendment clarifies how specific tracking observables are represented and interpreted in TDM files — notably RANGE for two‑ and three‑way data, CLOCK_BIAS entry conventions and Delta‑DOR session rules — and fixes ordering/labeling ambiguities to improve consistent machine interpretation.

Q: Who typically uses it?

A: Space agencies, ground‑station operators, mission operations and navigation teams, avionics and mission‑software developers, and any organization exchanging or processing interagency tracking data.

Q: Is it current or superseded?

A: This is a published amendment to ISO 13526:2010 issued on 16 June 2015. It is intended to be applied together with the 2010 edition of ISO 13526. Users should confirm whether a newer edition of ISO 13526 or further amendments have been published since 2015 when implementing or procuring compliance.

Q: Is it part of a series?

A: Yes — ISO 13526 is part of space data and information transfer systems standards and adopts the CCSDS Tracking Data Message recommended standard conventions (CCSDS 503.0 family). It is typically used alongside other CCSDS and ISO standards governing space data transfer, telemetry and mission operations.

Q: What are the key keywords?

A: Tracking Data Message, TDM, range observable, clock bias, Delta‑DOR, CCSDS, spacecraft tracking, ground station, interoperability.