Standards alignment
OpenITS does not replace NTCIP, SAE, or IEEE. It sits above them, giving their state and events a shared, transport-neutral meaning.
Above the device standards
Device-level standards do their job well: NTCIP defines how a controller is polled, SAE J2735 defines V2X message formats, IEEE defines the radios. What has been missing is a layer above them that says what a controller’s state and events mean once they’ve been normalized, independent of which device produced them. OpenITS is that layer. Devices still speak their standards; OpenITS defines the shared model behind the gateway.
Per-domain mapping
Every service domain names the device-level standard it models, so the lineage is explicit. The table below is generated from the model catalog, not hand-maintained:
| Service | Domain | Reference standard |
|---|---|---|
| signal-control | Actuated signal controllers | NTCIP 1202 |
| dms | Dynamic message signs | NTCIP 1203 |
| ess | Environmental sensors / RWIS | NTCIP 1204 |
| rsu | Roadside V2X units | NTCIP 1218 |
| ramp-metering | Freeway ramp meters | NTCIP 1207 |
| perception | Machine-vision / detection | vendor augments |
| traffic-sensor | Volume / speed / occupancy | NTCIP 1209 |
| reversible-lane | Reversible / managed lanes | lane-control |
| cctv | CCTV / PTZ cameras | NTCIP 1205 |
This is a mapping, not a fork: OpenITS reuses the concepts and vocabulary of the underlying standards rather than reinventing them.
ARC-IT annotations
Each model carries ARC-IT alignment annotations, inheriting the US National ITS Architecture’s flow vocabulary. That lets architects trace an OpenITS event back to the information flows their regional architecture already describes.
Why YANG
OpenITS models are written in YANG for one decisive reason: it has no transport opinion. NTCIP bound its data model to SNMP, so replacing the transport would have meant replacing the model. YANG describes structure, types, and constraints (including safety must expressions) without assuming how the data is carried, which is exactly what a transport-neutral standard needs.
The choice of YANG, and the model-driven approach more broadly, is inspired by OpenConfig, which proved vendor-neutral, model-driven management in networking. OpenITS carries that spirit to Intelligent Transportation Systems.