Standards and Claim Boundaries
ChargeLink Native contains protocol implementations, test inventories and evidence contracts that reference published standards. It distinguishes five levels that must never be collapsed into one another in a report:
- Implementation coverage — which messages and behaviours the software implements.
- Executable test coverage — which inventory cases have a native execution binding.
- Live-stack readiness — which lanes have been run against a real peer or plant.
- Interoperability evidence — recorded sessions with named external devices.
- Formal conformance — an accredited laboratory's result under the applicable certification scheme. ChargeLink does not produce this.
Standards referenced by the product
| Standard | Use in ChargeLink | Limits |
|---|---|---|
| ISO 15118-20:2022 | Protocol implementation (SupportedAppProtocol, CommonMessages, DC), Annex B PKI, Annex C EVCCID, EVCC message timeouts | DC EIM in both roles with a simulated plant, Scheduled control mode, one charging schedule per session, no pause/resume. The TLS 1.3 handshake offers and accepts only the named groups secp521r1 and x448 (secp256r1 only with the engineering legacy option). AC/BPT: reference responder. Plug & Charge: fixture-driven. Engineering evidence, not conformance. |
| ISO 15118-2:2014 | Protocol implementation (MsgDef), native EXI round trip, reference responder | Reference-responder listener for engineering and test development; no standards-encoded EVCC sessions against third-party chargers |
| DIN 70121:2014 | Protocol implementation, native EXI round trip, reference responder | Live session limited to the reference request encodings |
| ISO 15118-4, ISO 15118-21, ISO/PAS 15118-23 | Test-case identifiers and requirement references for the protocol-first inventories and conformance packages | 797 + 297 + 86 identifiers with execution bindings; traceability only, no normative text |
| ASAM XIL 2.1 | Framework/MAPort/EESPort model and reference bridge | Deterministic reference; not used by the VeriStand bench |
| FMI 2.0 | Plant model packaging for VeriStand | Delivered FMU |
Read the machine-readable statement with chargelink --json standards matrix (every family reports claim_status: blocked for external claims, with the evidence required listed per family), chargelink --json coverage blockers and chargelink --json claim readiness --target protocol-complete --protocol iso15118-20.
What a ChargeLink result may be called
| You may say | You may not say |
|---|---|
| "Engineering evidence of an ISO 15118-20 DC EIM session between ChargeLink and <device> on <date>, run ID <id>, TLS 1.3 mutual, plant simulated." | "Certified", "conformant", "compliant with ISO 15118-20", "passed conformance testing". |
| "Conformance-readiness campaign: N cases pass, M fail, K blocked, with evidence manifest <hash>." | "Equivalent to <vendor tool>", "accredited result". |
| "Isolation check simulated by the plant model." | "Measured isolation". |
Every artifact's claim_boundary and the blocked_claims lists in conformance_traceability.json exist so that reports can quote the product's own limits. Certification claims require the applicable accredited process and laboratory.
Licensed standards text
ChargeLink packages contain identifiers, requirement references and ChargeLink-authored execution bindings. They never contain licensed normative text, and the package scanner rejects such content. Obtain the standards from their publishers.