Unique and up to date
Each RXSWIN must be uniquely identifiable and updated when the manufacturer changes the software relevant to type approval (7.2.1.2.1).
Resources · UNECE R156
What RXSWIN is, and why the auditor will ask for it.
RXSWIN stands for Regulation X Software Identification Number: it identifies the software of a vehicle type that is relevant to a type approval. When that software changes, the RXSWIN must change too.
Readable from the vehicle
It must be readable in a standardised way through an electronic interface, at least through the standard diagnostic port (7.2.1.2.2).
Protected
RXSWIN and software versions must be protected against unauthorised changes (7.2.1.2.3).
With a searchable register
Each RXSWIN needs a register describing the software before and after every update, with versions and validation data (7.1.1.2 and 7.1.2.3).
From the platform · Regulatory coverage
RXSWIN in the R156 matrix
Every R156 requirement about RXSWIN and software versions, with the catalogue documents covering it: configuration procedure, RXSWIN file, software register and readout test.
Each cell tells whether that document covers the requirement and what state it is in. A row with no documents turns red: you know what is missing before the audit.
| Requirement | MAN-SUMS-00 · SUMS manual | PRO-SUMS-03 · Software configuration | PRO-SUMS-08 · Diagnostic access | REC-SUMS-01 · RXSWIN file | REC-SUMS-02 · Vehicle software register | REP-SUMS-01 · RXSWIN readout test |
|---|---|---|---|---|---|---|
| 7.1.1.2Data of every software version, initial and updated | – | – | ||||
| 7.1.1.3Access to RXSWIN information before and after the update | – | – | ||||
| 7.1.1.4Vehicle software versions consistent with the RXSWIN | – | |||||
| 7.1.2.3Searchable record of the software behind each RXSWIN | – | |||||
| 7.2.1.2.1Unique RXSWIN, updated when the software changes | – | – | – | |||
| 7.2.1.2.2RXSWIN readable through a standard electronic interface | – | – | – | |||
| 7.2.1.2.3RXSWIN and versions protected against unauthorised changes | – | – |
ApprovedDraft or in reviewTo updateNot generated yetReal catalogue coverage, example document states.
28 more requirements and 23 more documents in the full matrix.
Explore it in a demoFAQ
Frequently asked questions
One RXSWIN per vehicle or per type?
Per vehicle type and per regulation: the RXSWIN identifies the software relevant to a given type approval of that type. A type can have more than one, one for each regulation affected by the software.
Does every update change the RXSWIN?
Only if the software relevant to type approval changes. That is why every update must be assessed (7.1.1.8–7.1.1.10) and the decision recorded.
How do you prove it to the auditor?
With the RXSWIN file, the vehicle software register and the RXSWIN readout test on the vehicle: in Omolia they are linked to each other and to the documents that mention them.
Contact
Tell us about your programme
Request a demo, a quote or simply information. We will reply within two working days.
- A demo on your vehicle types and regulations
- A proposal sized on your modules and users
- Support for onboarding and data migration