A calibration change can alter how vehicle software behaves while leaving its executable unchanged. If the organisation tracks only code versions, it may struggle to explain why two apparently identical installations respond differently. Parameter sets deserve the same clarity of identity, applicability and approval that teams expect for application software.
The management problem is to connect the calibration to the configuration it belongs to. That includes the executable, the descriptions used to interpret parameters and the evidence supporting the change. A familiar filename is insufficient when several teams can produce and modify sets.
Define the supported combination
Identify the software versions and hardware configurations for which a calibration is valid. Record relevant dependencies on other parameter sets or functions. A value that is acceptable in one software context may have a different meaning or range in another.
ASAM XCP supports ECU measurement and calibration, with parameter descriptions associated through A2L information. The technical ability to access a parameter does not establish that a change is appropriate for a production configuration. Release governance must provide that decision and preserve its evidence.
Control the transition from experiment
Development work may involve temporary parameter changes made to explore behaviour. Distinguish these from candidates approved for release. Record the starting configuration, intended question and changes introduced, so useful experimental results do not become detached from the state that produced them.
Define the route by which an experimental set becomes a released artefact. It should include review of applicability, test evidence and unresolved concerns. A copy into a shared folder should not silently change the status of a set from an investigation aid to a production delivery.
Preserve measurement interpretation
Measurement descriptions should correspond to the executable and calibration under test. If a tool uses a mismatched description, it may display a plausible value that is incorrectly interpreted. Investigations need the relationship between the data, its descriptions and the test configuration.
Keep conversion and parameter meaning changes visible. A renamed field can draw attention while a changed scale or convention may pass unnoticed. Review such changes with consumers of measurement data and service information. Their interpretation is part of the delivered behaviour even if the executable interface appears unchanged.
Make field reconstruction possible
Service and engineering teams should be able to identify the calibration installed in a relevant vehicle or determine the limits of that information. Connect its identity to the release record and retain the approved artefact. Avoid assuming that the intended campaign configuration proves the actual field state.
When a later issue appears, compare complete configurations before attributing the behaviour to code. Calibration discipline can prevent an investigation from chasing the wrong change. It also makes supplier exchanges clearer because both sides can refer to the same parameter set and supporting evidence. The objective is reproducible understanding of vehicle behaviour, with a controlled path from engineering adjustment to supported installation.
Sources & further reading
Measurement and calibration protocol and its relationship to A2L descriptions.
Prepared 2026-10-13. Source references retained from that edition. Corrections and feedback.
