Standards and Claim Boundaries
ChargeLink 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 test cases ChargeLink can execute.
- Live-session evidence — which sessions have run against a real DUT 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. Charger and vehicle role. | DC EIM in both roles; the plant-coupled charger runs Scheduled and Dynamic control mode as offered by the runtime profile, 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 --allow-legacy-tls-named-groups). AC: reference responder. BPT and Plug & Charge: not provided. Engineering evidence, not conformance. |
| MCS (ISO 15118-20 over 10BASE-T1S) | ISO 15118-20 DC with the MCS energy service, EIM, Scheduled control mode, in the charger and the vehicle role | In this release, the MCS charger connects to a ChargeLink vehicle and the MCS vehicle to a ChargeLink charger. Connector signals are simulated. See the MCS runbook. |
| ISO 15118-2:2014 | Protocol implementation (MsgDef), charger reference responder, vehicle DC EIM session | Charger role: reference responder for your vehicle. Vehicle role: in this release, the DC EIM session (iso2-evcc) connects to a ChargeLink charger. |
| DIN 70121:2014 | Protocol implementation, charger reference responder, vehicle DC session | Charger role: the session is limited to the reference request encodings. Vehicle role: in this release, the DC session (din-evcc) connects to a ChargeLink charger. |
| IEC 61851-23 / IEC 61851-24 System A (CHAdeMO) | Station and EV roles of the CAN-based DC scheme, with timing and state rules whose values follow IEC 61851-24 (System A) | In this release, the station connects to a ChargeLink EV and the EV to a ChargeLink station. Simulated plant; no power stage. See the CHAdeMO runbook. |
| 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 executable test cases; traceability only, no normative text |
| ASAM XIL 2.1 | Framework, MAPort and EESPort interfaces for XIL integration | 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 (charger role) 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 test procedures. They never contain licensed normative text. Obtain the standards from their publishers.