Release ledger
Canonical Atlas record
TS 22.282
Mission Critical (MC) data
Release evolution
Compare evidence between releases
Use indexed version, Work Item and Change Request evidence to see what changed around this specification. This is an evidence trail, not a clause-by-clause normative diff.
Rel-16 snapshot
Work affecting this release
28 indexed Change Requests · 2 connected Work Items.
Showing 12 CR records from the available cross-release sample. Browse release CR records (JSON) →
CR 0024 — CR_22.282_ setup time requirement for monitoring and control of critical infrastrucuture communication
CR 0015 rev.1 — Addition of capability to support centralised enhanced status monitoring
CR 0015 rev.2 — Addition of capability to support centralised enhanced status monitoring
CR 0018 — TS_22.282 CR_LOCOTROL infromation transmission between engines
CR 0018 rev.1 — TS_22.282 CR_LOCOTROL infromation transmission between engines
CR 0020 rev.1 — Clarification of requirements for delivery and read notifications
CR 0022 — Propose requirements of Automatic Train Operation data communication
CR 0025 — Application of MCData to maritime usage
CR 0025 rev.1 — Application of MCData to maritime usage
CR 0026 — Periodical and non-periodical data communication
CR 0026 rev.1 — IP connectivity for MCData users.
CR 0026 rev.2 — IP connectivity for MCData users.
Version history
Indexed versions
Showing 20 of 20 indexed versions.
Atlas classifications
Meaning and provenance
No Atlas classifications have been attached yet.
Work Items
Standards work connected to TS 22.282
Stage 1 of MCData
Historical association · verification pendingRemoval of 'over LTE' limitation from Mission Critical Specifications
Study on MONASTERY2
(Small) Technical Enhancements and Improvements for Rel-16
Historical association · verification pendingComplete Gap Analysis for Railways Mobile Communication System
Knowledge graph
Related standards
No graph edges indexed yet. The graph API is available at this JSON endpoint.