Translating ISO 15118-20:2022 electric-vehicle charging documents is not the same as translating a consumer guide about charging a car. Engineers and localization teams searching for ISO 15118-20 translation, EVCC–SECC communication log translation, Plug & Charge terminology, bidirectional charging message translation or EV charging protocol documentation translation need to preserve message direction, system role, authorization state and power-flow meaning. A small error in a technical sentence can make an implementation note describe the wrong controller or suggest a vehicle supports a capability the source never established.
ISO 15118-20:2022 addresses second-generation network-layer and application-layer communication between an electric vehicle and charging equipment. The ISO catalogue describes electric vehicle communication controller (EVCC) and supply equipment communication controller (SECC) exchanges, including bidirectional energy transfer and communication relevant to different charging arrangements. The 2022 edition has a 2026 amendment. A translator must identify the actual edition and amendment cited by the source; a translated engineering note is not itself proof of technical conformity, tested interoperability or permission to export energy to a grid.
Quick translation decisions: retain EV, EVSE, EVCC and SECC as different actors; preserve requests versus responses; distinguish electrical power direction from the direction of messages; keep AC, DC, conductive, wireless and automatic connection contexts separate; do not turn an optional or negotiated capability into a universal feature; preserve authorization and certificate-status wording; keep timestamps, units, identifiers and error codes unchanged; tie examples to their source version; and send safety, protocol or legal implications back to a responsible subject expert rather than guessing.
The task: translate technical evidence without changing machine behaviour
The real reader problem
Imagine a vehicle manufacturer, charge-point operator and software supplier exchanging a bilingual integration report. The English log says a vehicle announced a service and the charging station responded with a negotiated parameter. A careless translation calls both actions ‘charging approval’. The engineer reading the target text may then look for a power-delivery fault when the defect actually sits in authorization or capability discovery. This article treats translation as a sequence-preservation problem: first identify the speaker, then the message, then the electrical effect, and only afterward choose words.
What the standard covers and what it does not prove
The ISO catalogue identifies ISO 15118-20:2022 as communication between EV and EVSE, and explicitly mentions bidirectional power-transfer message sequences, wireless-related requirements, automatic connection and charging-control information. That scope tells us which families of terms matter. It does not mean every vehicle, charger, country or software release implements every feature. Nor does a translated screenshot establish compliance. A claim about conformity requires the actual normative text, relevant amendments, test evidence, implementation profile and local rules. This boundary should be visible even in a marketing translation.
Why translation errors can survive software testing
A system may exchange perfectly valid protocol messages while the user-facing explanation, test report or maintenance instruction misdescribes them. Translation errors can also hide in release notes that never reach protocol parsers: a mislabeled parameter, a reversed actor, or a statement about export limits that has lost a negative. Functional tests cannot automatically detect all such semantic changes. Review the software behavior and the explanatory language as different evidence sources. The translation team should mark which assertions were verified against logs, which came from a specification and which remain untested expectations.
Three layers that must not collapse
Keep the physical layer of energy transfer, the communication layer of messages and the business layer of permissions distinct. A charger can be connected physically without a completed authorization exchange; a message can be accepted without proving energy will immediately flow; a contractual export arrangement can exist without a vehicle supporting the needed implementation. When these layers are merged into an attractive but inaccurate phrase such as ‘the station enables vehicle-to-grid charging’, readers lose the ability to diagnose failures. An accurate translation retains qualifiers and conditions that connect one layer to another.
A useful document intake sheet
Before translating, ask for the document type, system architecture, hardware model, firmware version, source language, target locale, interface profile, protocol release, cited ISO edition and intended reader. Include whether the material is a message trace, service manual, procurement specification, test evidence, UI string or public FAQ. Capture the owner of each claim and the person authorized to approve target-language terminology. A bilingual glossary is valuable only when it is anchored to this context; ‘controller’ or ‘schedule’ can mean several things in the same project.
The limits of examples in this guide
All sample messages, timestamps, status phrases and log extracts below are invented teaching examples, not verbatim clauses or normative message definitions from ISO 15118-20. They demonstrate how to preserve distinctions while reviewing translation. Exact schemas and compliance criteria belong to licensed standard text and implementer specifications. When a customer provides a real log, its exact wire identifiers take precedence over any pedagogical paraphrase. Do not turn an illustrative ‘request accepted’ sentence into an assumed official protocol status value.
Translation terminology: 28 decisions engineers actually need
1. EV versus EVSE
An electric vehicle is the participating vehicle; electric vehicle supply equipment is the external equipment involved in supplying or managing charging energy. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Replacing both nouns with ‘charger’ erases which side originates an action and can reverse responsibility for a failed operation. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Read each sentence with an actor column: vehicle or infrastructure. Keep the acronym visible at first occurrence and tie every verb to the same actor. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
2. EVCC
The electric vehicle communication controller is the vehicle-side communication participant in the account of the exchange. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A translation that calls it a charger controller relocates an internal vehicle function into the station and distorts diagnostic instructions. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Check actor labels against diagrams and log headers; use EVCC consistently even if the translated full phrase varies with local engineering usage. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
3. SECC
The supply equipment communication controller is the equipment-side communication participant, distinct from the power electronics as a whole. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating SECC as ‘station server’ may suggest a remote backend rather than the specific peer in a local exchange. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Ask whether a log line was generated by SECC, EVCC or an operator backend, and keep those entities separate in the target report. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
4. Request
A request expresses what one party asks the other party to do or report within a particular interaction. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Words meaning command, guarantee or approved decision can falsely upgrade a request before the response has been evaluated. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Retain request-response pairing in tables and preserve the sender and the requested object; never translate a request as a completed energy transfer. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
5. Response
A response reports an answer or state in relation to an earlier request; it is not automatically a physical outcome. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A generic translation like ‘confirmation’ can overstate success where a response merely supplies information, rejects an option or describes limitations. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Compare the response against the corresponding request and status; preserve negative, conditional or unavailable outcomes explicitly. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
6. Bidirectional power transfer
The phrase concerns the possible direction of electrical energy transfer between vehicle and equipment in supported arrangements. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
It can be misread as two-way network communication, which occurs independently of whether power is exported from the vehicle. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Translate the energy direction in concrete terms; identify charging into the vehicle and discharging out of it, if the source distinguishes them. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
7. Vehicle-to-grid and vehicle-to-load
These terms point to different destinations or usage settings for exported energy and can be relevant to commercial claims. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Treating every bidirectional feature as grid export implies infrastructure, authorization and regulatory support that may not be present. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Keep the exact source term, destination and applicable mode; request clarification if a report only says ‘bidirectional capable’. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
8. AC charging
Alternating-current charging involves an AC supply arrangement, with energy conversion and communication details depending on system design. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A translator who expands AC as ‘automatic charging’ can corrupt wiring instructions and technical comparisons. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Preserve AC as alternating current and verify whether the source actually compares it with DC or uses a specific charging service label. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
9. DC charging
Direct-current charging uses a DC power-transfer context with different equipment and control implications from AC arrangements. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Describing all DC charging as fast charging invents a performance classification and may change a stated operating mode. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Translate DC literally as direct current, retaining voltage, current, power and thermal qualifications exactly where the source includes them. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
10. Conductive charging
Conductive describes energy transfer using electrical contacts in the relevant arrangement rather than wireless energy delivery. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A literal translation suggesting good electrical conductivity of materials misses the actual system classification. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Find the associated connector, equipment configuration and test mode; use one approved term for conductive charging throughout the document. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
11. Wireless charging
Wireless here concerns the relevant communication and/or wireless power-transfer context stated in the technical source. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
The word wireless alone does not tell the reader whether a signal, power, or both are transmitted without a cable. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Make the noun explicit: wireless communication, wireless charging or a named service. Preserve the exact scope rather than generalizing. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
12. Automatic connection device
An automatic connection device refers to an equipment arrangement in which connection is performed automatically in the system scope. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating it as a network auto-connect option confuses physical connection functionality with communications discovery. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Keep any device abbreviation aligned with hardware diagrams and ask which connection action is automatic before localizing a support statement. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
13. Plug & Charge
Plug & Charge is commonly used for certificate-based authorization experiences within compatible charging ecosystems. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A user-facing promise that charging ‘always starts just by plugging in’ can conceal enrollment, credential and compatibility conditions. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Preserve the feature name where it is an established label; describe the required authorization path without guaranteeing universal availability. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
14. Authorization
Authorization concerns permission or acceptance within a defined charging or contractual process, not necessarily the delivery of energy. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Approval, authentication, identification and payment are related but different operations; combining them can hide the failed step. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Ask which process actually succeeded: credential validation, service authorization, contract check or energy-delivery transition. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
15. Certificate
A digital certificate carries identity and trust information used in relevant security and authorization workflows. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating it as a paper conformity certificate turns cryptographic credential maintenance into a legal document problem. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Retain key distinctions among provisioned credentials, certificate chains, validity periods and test certificates when the source includes them. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
16. TLS
Transport Layer Security is a security technology associated with protected communication channels in relevant implementations. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Calling TLS an encryption algorithm or an authorization result can conceal the separate roles of transport protection and service access. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Preserve the acronym and describe only the security property actually supported by the source evidence, not an unverified security guarantee. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
17. Session
A session is a bounded interaction whose meaning depends on the implementation and log context. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating session as a charging transaction can collapse a communication exchange with the commercial billing event or energy-delivery interval. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Retain session identifiers and boundaries; if several sessions are shown, preserve their distinction and chronology. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
18. Service discovery
Service discovery is about learning what services or capabilities may be available in the interaction. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A phrase like ‘service activated’ falsely implies use rather than announcement or selection. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Identify whether the text concerns discovery, selection, negotiation, authorization or execution and carry that stage into the translation. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
19. Negotiation
Negotiation in an engineering log concerns exchange and agreement of parameters under system rules, not a human price bargain. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A financial idiom can mislead engineers into thinking tariff agreement rather than equipment parameter selection. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Translate the object of negotiation explicitly: offered capability, charging parameter, schedule, or limit as supplied in the source. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
20. Schedule
A schedule in charging control may describe planned or constrained power behavior over a period. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Calling it a timetable for the driver’s appointment changes a machine-control element into a booking concept. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Preserve time basis, interval length, unit and power direction; validate each table row against the diagram or trace. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
21. Power limit
A power limit constrains an amount of power under a stated condition and may vary with direction or operating state. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Confusing power with accumulated energy changes kW to kWh and turns a constraint into a delivered quantity. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Do a unit and direction pass before linguistic polish; never convert kW into kWh merely to make the wording familiar. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
22. Energy request
A vehicle may express requested energy or related charging needs in system communication; this is not an observation of delivered energy. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating requested energy as consumed energy can falsify efficiency or billing claims. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Keep requested, offered, scheduled, measured and delivered quantities separately labeled and retain units. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
23. State and status
A state field or status message describes a system condition at a particular point or transition. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Words such as fault, warning, unavailable and suspended are not interchangeable, nor is a temporary state necessarily a failure. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Build a state glossary from the project’s actual enumeration and do not invent a friendlier target-language label. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
24. Timestamp
Log chronology depends on the time base, zone, precision and synchronization assumptions recorded by the system. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Reformatting timestamps into ambiguous day-month order or silently changing UTC can corrupt the cause-and-effect sequence. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Keep raw timestamps in technical exhibits; use an explanatory local time only when the conversion is explicit and verified. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
25. Identifier
Identifiers such as session tokens, equipment IDs and message correlation IDs are machine references, not prose. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Translating characters, normalizing punctuation or trimming leading zeros can break the linkage between a report and original log. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Copy identifiers byte-for-byte, check them mechanically and never let spell-check ‘correct’ a protocol string. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
26. Error code
A defined code is an exact diagnostic object whose meaning depends on the particular implementation or specification. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Replacing an unknown code with a guessed English description creates a false diagnosis and may misdirect repairs. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Keep the code intact and add only an approved localized explanation tied to the same firmware and documentation version. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
27. Optional capability
A system may support a feature conditionally or negotiate it; documentation often separates mandatory requirements from optional functions. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
Dropping ‘may’, ‘if supported’ or ‘when enabled’ makes a narrower claim read like universal interoperability. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Underline modality words in the source and review them against every target-language sentence before publication. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
28. Conformance
Conformance is a claim about meeting applicable requirements supported by a defined assessment and scope. In an EV charging translation, this is a distinct technical concept, not a decorative variation of ordinary language. A reader should be able to recover the same system boundary from either language.
A translated implementation plan or training example is not a certificate and must not be called proof of certification. This matters because an implementer may use a translated note to choose what to inspect or test next. A smooth but over-general translation is less useful than a precise one that retains the original limit.
Record the specific standard edition, amendment, product variant, test method and evidence owner before making a formal statement. If the document uses the term in more than one place, record the approved wording in the project glossary and confirm it survives headings, figure captions and release notes.
Fourteen worked translation cases, with mistakes and recoveries
Worked case 1: The two controllers swapped
A support ticket states that the EVCC transmitted a request and the SECC returned a response after evaluating the service options.
The first target draft assigns both steps to the charger. A reader then searches the station software for a vehicle-originated field that the station never created. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: write the vehicle-side controller as sender of the request and the equipment-side controller as sender of the response. Put the actor labels beside the raw trace and have an integration engineer approve them. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 2: An export claim from a compatibility flag
A procurement document says a model may negotiate a bidirectional power service when supported by the connected system.
The marketing version announces that every customer can sell energy back to the national grid. That assertion adds commercial and infrastructure claims absent from the source. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: preserve ‘may’ and ‘when supported’. Distinguish protocol capability, installed equipment, grid arrangements and jurisdictional approval before any external promise is printed. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 3: Kilowatts became kilowatt-hours
A translated test case describes a power limit of 7 kW during a defined interval.
The translator uses ‘7 kWh’ because that unit looks familiar from consumer battery descriptions, turning a rate constraint into an energy quantity. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: restore kW and retain interval boundaries. If energy over time must be discussed, calculate it separately with the relevant assumptions and show it is a derived number. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 4: An acceptance confused with action
A log note reports that a proposed service was accepted during negotiation, but the energy-transfer phase had not started.
A summary headline reads ‘the station began charging’. The timeline then appears to contradict a later observation that current remained zero. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: say ‘service selected’ or ‘proposal accepted’ only if those match the actual response. Name the later transition into power delivery separately. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 5: Plug & Charge overpromised
A support article explains certificate-based charging in a compatible ecosystem, subject to enrollment and software configuration.
Localization drops the condition and promises a frictionless start on all public charge points. Customers may rely on a payment or authorization path that does not exist. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: preserve compatibility and credential prerequisites. Write a customer instruction that includes an alternative method when the particular product supports one. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 6: The wrong time zone
A session trace uses UTC and a local operator report uses the time at the charging site.
The translation copies numerical clock times without zone labels. Two entries appear to contradict each other by several hours. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: label the original time base, show any converted display times with offsets and keep original timestamps in the supporting trace. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 7: Wireless signal or wireless power
An equipment description discusses wireless communication and a different paragraph discusses a wireless charging arrangement.
The translated brochure says the vehicle charges wirelessly when the original paragraph only described data communications. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: attach ‘wireless’ to its precise noun. Verify which hardware configuration actually transfers power without a conductive connector. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 8: A fault code turned into a diagnosis
A maintenance ticket contains a vendor-defined error code and a tentative engineer hypothesis about one failed test.
The translation replaces the code with the hypothesis as though it were the defined meaning. Subsequent repair staff lose the traceable original field. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: keep the code, mark the explanation as a hypothesis and refer to the vendor’s firmware-specific error reference. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 9: AC and DC merged
A bilingual technical table has separate AC and DC capability columns for two equipment variants.
A localized table renders both as ‘electric charging’, hiding which configurations are actually offered to customers. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: retain the AC/DC headings and each variant’s values. Review table structure, not just isolated sentences. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 10: A request reported as measured delivery
A vehicle-side message expresses desired charging energy and later measurement shows a different delivered amount.
The translated investigation calls the request a measured energy quantity, producing a fictional performance discrepancy. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: preserve ‘requested’ versus ‘measured’, keep units and dates, and name the measurement source for every reported total. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 11: A conditional sequence flattened
A work instruction says one message is sent if a prerequisite service has been selected; otherwise the process follows another path.
The translator turns the conditional sequence into a fixed list. Testers then classify valid branches as non-compliant deviations. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: preserve ‘if’, ‘otherwise’, order and decision points. Compare the translation against the message-sequence diagram. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 12: A security feature treated as universal
A draft release note says a particular profile supports a secure communication method in the tested configuration.
A target-language announcement says all versions are secure and all third-party stations interoperable. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: specify the exact profile, environment and tested claim. Avoid absolute security or interoperability language unsupported by evidence. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 13: Different contract and protocol states
A document describes an authorization outcome in the communication exchange and a separate commercial contract activation.
Localization translates both as ‘account enabled’, obscuring which team must fix a customer failure. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: use ‘protocol authorization’ and ‘contract/account status’ as distinct concepts. Let the technical and commercial owners sign off on their respective claims. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
Worked case 14: False failure from a screenshot
A training slide shows an incomplete trace and a status message before the session proceeds.
A translator invents the headline ‘charging failed’ from the visible fragment without seeing the next messages. The immediate problem is not simply stylistic: it changes what someone could infer about the technical state, source of evidence or practical next action.
Correction: mark the excerpt as partial and request the rest of the trace. Do not infer end-state outcomes from one screenshot. The final reviewer should compare the corrected wording with the original log or requirement, not just with the preceding translation draft. These cases are fictional teaching examples, not official ISO protocol messages.
A twelve-stage translator and engineering review checklist
Step 1: Build a scope register
List vehicle, charger, firmware and network components, source version, target locale, audience and document purpose. Keep the document’s actual scope available while translating each term. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 2: Freeze exact strings
Extract raw message labels, codes, identifiers, certificate references and field names as protected tokens. Validate them with a character-level comparison after export. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 3: Create an actor map
For every step, identify whether EVCC, SECC, EVSE, the human operator or a backend system is the subject. Translate verbs only after this is decided. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 4: Preserve message chronology
Make a request-response table that retains source order, correlation, timestamps and conditions. The translated narrative should reproduce that timeline without improvising skipped steps. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 5: Perform an energy-direction audit
Mark into-vehicle charging and out-of-vehicle discharge distinctly. If a sentence merely refers to bidirectional support, do not expand it to a grid-export commitment. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 6: Audit all units
Check power, energy, voltage, current and time units and the quantity each number measures. Do not substitute numbers or change decimal conventions inside raw logs. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 7: Lock capability qualifiers
Search the source for may, shall, must, only, when supported, not supported, pending and optional. Ensure the same strength or limitation survives in the target language. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 8: Verify authorization stages
Separate identity, credential validation, permission, contract state and energy-delivery state. A successful credential check is not automatically a successful charging session. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 9: Review tables and diagrams
Verify table headers, arrows, callouts, sign conventions and branching diagrams. Visual labels often reveal the actor reversal that prose review misses. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 10: Run a back-check with a domain reviewer
Ask an engineer to explain in plain language what the target sentence instructs or reports, without showing the source. If the explanation differs, repair the translation. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 11: Test published UI strings in context
If the text appears in an app or station interface, check it against real screen states and available space. Keep fault messages intelligible without masking technical detail. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Step 12: Release with traceability
Store the source revision, translator and reviewer names, glossary edition, unresolved queries and approvals. Do not describe a localization sign-off as a protocol conformance certificate. Record the outcome in the bilingual issue log, noting who checked the evidence and what remained uncertain. A step is complete only when its source-to-target relationship can be inspected again after publication.
Frequently asked questions
What is the main translation risk in ISO 15118-20 material?
Reversing EVCC and SECC responsibility, changing message states, misreading bidirectional power as general communications or silently upgrading conditional capability into guaranteed support. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Does the 2022 standard mean every electric vehicle supports vehicle-to-grid charging?
No. The standard addresses relevant message and sequence requirements; implementation, hardware, network arrangements, supported profiles, approvals and market rules still matter. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Can a translator change EVCC and SECC abbreviations into local-language abbreviations?
Normally retain the standard technical abbreviations and explain them at first use. A project glossary can prescribe a local expansion, but source identifiers should remain intact. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Is Plug & Charge the same as free charging?
No. It concerns a compatible authorization experience; tariffs, contracts and payment obligations are separate business questions. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
How should errors be translated?
Preserve exact status and code fields, then add an approved human-readable explanation when the source supports it. Do not invent causal diagnoses. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
What is the difference between kW and kWh?
kW describes a rate of power; kWh describes an amount of energy. They cannot be substituted without changing technical meaning. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
What if the source’s protocol edition is unclear?
Ask the document owner. Retain any existing citation but flag ambiguity. Do not assume that a later amendment automatically applies to an older log. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Can artificial intelligence produce the first draft?
It may assist under controlled conditions, but the result needs independent checking of actors, units, qualifiers, tokens, sequencing and evidence. A fluent sentence is not necessarily an accurate one. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Should a translated product page claim compliance?
Only when the claim is traceable to an appropriately scoped assessment and current authorized wording. Translation does not establish compliance. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Where does this article belong in the wider learning system?
It is a narrow applied case about EV charging communication. General translation principles remain with the existing Master Art of Translation; vocabulary and English-meaning skills remain with their protected learning hubs. For a live project, the controlling source is the approved document set and the applicable technical requirements, not a generic example on the internet.
Sources, boundaries and connected learning
Official catalogue reference: ISO 15118-20:2022 (including the catalogue’s listing of its 2026 amendment). This guide paraphrases publicly described scope and uses invented teaching cases rather than copying normative ISO clauses.
For the larger principles behind precise technical meaning, continue with Master Art of Translation — The Complete System and its Technical Translation System. For learning words and distinctions, use the protected Vocabulary Learning Hub and How English Works: Translation and Meaning. This article is a specialised case, not a replacement hub.