Why ROCOM Security & Safety
The Standard — Parts
Part 1 — Overview & Scope Part 1 — Architecture Reference Model Part 2 — Conformance Part 2 — Service Levels L0–L3 Part 5 — Transport Profile
Supplements
All Supplements Sup-001 — Orchestrator API Annex A — Engineering Practice Sup-003 — BMS Infrastructure
Reference
Principles & Architecture Specification Modules (YAML) Changes
About
Governance Contribution Process
Action
Get Started

Changes — Correction Proposals & Supplements

What Is a Change Record?

The Rocom specification evolves through a structured change process with three mechanisms, modeled after standards bodies like DICOM and IEC:

Correction Proposals

Each CP below shows its current status. A PROPOSAL is under review and is not yet normative text. A MERGED has been accepted and incorporated into the specification. SUPERSEDED has been replaced by a later change.

CPTitleStatusDatePart
CP-004—RESERVED—General
CP-009Priority and Preemption ModelMERGED2026-08-31General
CP-008Resource Authority ModelMERGED2026-08-30General
CP-007Agent Identity Model (issuer-agnostic, UDI-aligned)MERGED2026-08-28Part 3
CP-006CostModel generalization — cost_factors arrayMERGED2026-08-22Part 3
CP-005Pin VDA 5050 version to 2.1MERGED2026-08-21Part 5
CP-001Split architecture figure from Part mapMERGED2026-08-12Part 1
CP-002Remove FILE scaffolding from CONFORMANCE.md; fix requirement formatMERGED2026-08-12Part 2
CP-003GOVERNANCE.md — funding, held-in-trust, Advisory BoardMERGED2026-08-12Part 7

Supplements

SupTitleStatusDate
Sup-001Orchestrator Service InterfaceMERGED2026-08-12
Sup-002Annex A — Engineering Practice NotesMERGED2026-08-18
Sup-003BMS Infrastructure ContractMERGED2026-08-21
Sup-004Governance Structure: Board and Working GroupsADOPTED2026-09-26
Sup-005Certification Provider RequirementsADOPTED2026-09-26
Sup-006—RESERVED—
Sup-007Versioned Policy References and Namespaced ExtensionsDRAFT2026-10-24
Sup-008Informative Vendor / System / API Reference RegisterDRAFT2026-11-03