{"id":3564,"date":"2026-08-12T13:00:00","date_gmt":"2026-08-12T13:00:00","guid":{"rendered":"https:\/\/xinya-ee.com\/?p=3564"},"modified":"2026-09-19T11:16:47","modified_gmt":"2026-09-19T03:16:47","slug":"ev-charging-site-commissioning-handover","status":"publish","type":"post","link":"https:\/\/xinya-ee.com\/fr\/blog\/ev-charging-site-commissioning-handover\/","title":{"rendered":"Mise en service d'un site de recharge pour v\u00e9hicules \u00e9lectriques : Dossier pour un transfert clair"},"content":{"rendered":"<div class=\"b2b-article\">\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>EV charging commissioning<\/strong> should create a clear record of what was installed, what the responsible project process checked, and what operations need after handover. A vehicle beginning to charge is useful functional evidence, but it is not by itself the complete electrical, operational, or local-approval record.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/03\/EC2402.webp\" alt=\"XYDF DC charging equipment used as commissioning and handover context\" loading=\"lazy\" \/><figcaption>Equipment context only; commissioning requirements and approval must be confirmed for the actual project.<\/figcaption><\/figure>\n<nav class=\"b2b-toc\" style=\"background:#f5f8fa;padding:16px 20px;border-radius:8px;margin:0 0 24px\">\n<h2 id=\"contents\" style=\"margin:42px 0 14px;scroll-margin-top:96px\">Contenu<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"#part-1-what-is-the-purpose-of-commissioning-and-handover\">Part 1. What is the purpose of commissioning and handover?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-2-which-installed-condition-records-should-be-collected\">Part 2. Which installed-condition records should be collected?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-3-how-should-teams-plan-functional-checks-and-evidence\">Part 3. How should teams plan functional checks and evidence?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-4-what-information-should-operations-receive-at-handover\">Part 4. What information should operations receive at handover?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-5-when-should-a-change-trigger-a-review\">Part 5. When should a change trigger a review?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-6-how-should-project-responsibilities-be-recorded\">Part 6. How should project responsibilities be recorded?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-7-what-should-buyers-request-before-a-charging-project-is-released\">Part 7. What should buyers request before a charging project is released?<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-1-what-is-the-purpose-of-commissioning-and-handover\">Part 1. What is the purpose of commissioning and handover?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Commissioning connects the installed charging arrangement to the project requirements and responsible operating process. Handover makes the resulting information usable by the people who will operate, maintain, and escalate issues after the project team steps back.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">The aim is not to create one universal checklist. Local rules, utility requirements, equipment, site conditions, and contract scope determine the final process. The common principle in infrastructure guidance is that additional demand, installed equipment, and associated responsibilities should be assessed and documented rather than assumed.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Separate acceptance from operational readiness. Acceptance asks whether the defined contract tests and documents meet their criteria; readiness asks whether trained operators, portal access, support routes, tariffs, communications, service arrangements, and unresolved defects permit dependable use. Record each decision, approver, date, conditions, and permitted exceptions.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-2-which-installed-condition-records-should-be-collected\">Part 2. Which installed-condition records should be collected?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Begin with a record that identifies what is actually in place. A procurement specification may describe intent, while the handover pack needs to identify the installed configuration and the information needed to operate it safely through the responsible process.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Build an equipment baseline at charger level: manufacturer and model, serial number, connector arrangement, installed firmware and configuration revision, charger or station identifier, and its mapped backend asset ID where a management system is used. These <strong>handover records<\/strong> let a maintainer distinguish the accepted state from a hardware or software change without assuming that all units share one configuration.<\/p>\n<div style=\"width:100%;overflow-x:auto;-webkit-overflow-scrolling:touch\">\n<table style=\"width:100%;min-width:720px;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Record area<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Why it matters at handover<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Project question<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Equipment identity<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Links supplied equipment to the project record<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Which product and connector arrangement was installed?<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Site and distribution information<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Provides the electrical context for future work<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Which drawings and labels are controlled documents?<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Applicable approvals and inspections<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Keeps evidence within its local process<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Who holds the current records?<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Operating and fault contacts<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Gives users a clear escalation path<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Who responds to which issue?<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">As-built changes<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Separates installed condition from early design assumptions<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">What changed during delivery?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p style=\"margin:0 0 16px;line-height:1.7\">The drawing set should show the final single-line arrangement and controlled revisions, not only the tender design. Cross-reference feeder and protective-device labels, isolation points, earthing or bonding arrangements, meter and communications equipment, charger positions, and underground or concealed cable routes. Record deviations and accessible inspection evidence so future work does not depend on memory.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not convert this list into a claim that every project requires the same documents. The responsible project parties and local authority determine what is required and who may sign it.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-3-how-should-teams-plan-functional-checks-and-evidence\">Part 3. How should teams plan functional checks and evidence?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Plan checks around the agreed scope, then preserve the evidence in the handover record. The check sequence may include the installed arrangement, isolation and safety process, connector and user interaction, communications where applicable, and the project&#8217;s defined fault-response path. The exact tests belong to qualified personnel and the applicable local process.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For electrical verification, the record should identify the circuit and equipment tested, method, instrument and calibration status, date, competent person, measured or observed result, acceptance criterion, and disposition. Depending on the jurisdiction and design, <strong>site acceptance testing<\/strong> may address supply and phase checks, protective-conductor continuity, earthing and bonding, insulation resistance, protective-device operation, and RCD or GFCI functions. Values and pass limits must come from the applicable design, manufacturer instructions, and local rules; they should not be copied from a generic checklist.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Functional evidence should cover the agreed EV-to-EVSE combinations and user paths, capturing authorization, start, power delivery, normal stop, energy or meter record, alarms, and the matching charger and backend timestamps. Include defined fault cases and recovery evidence where these can be tested safely. A passed session shows that scenario worked; it does not prove every vehicle, connector, load condition, or failure mode.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Where OCPP is in scope, verify the configured charger identity, connection to the intended charging-station management system, status and transaction messages, remote actions required by the contract, loss-and-restoration behavior, and clock or time-zone alignment. The <a href=\"https:\/\/openchargealliance.org\/protocols\/open-charge-point-protocol\/\" target=\"_blank\" rel=\"noopener\">Alliance de recharge ouverte<\/a> defines OCPP as communication between charging stations and management systems; it does not make a successful connection proof of the site&#8217;s electrical acceptance.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\"><a href=\"https:\/\/www.networkrail.co.uk\/wp-content\/uploads\/2023\/11\/NR-GN-CIV-200-13-Electric-Vehicle-Charging-Points-and-Associated-Infrastructure.pdf\" target=\"_blank\" rel=\"noopener\">Network Rail&#8217;s EV infrastructure guidance<\/a> treats supply assessment and project coordination as part of the infrastructure work. The <a href=\"https:\/\/iaeimagazine.org\/electrical-fundamentals\/electric-vehicle-charging-infrastructure-stations-equipment-and-planning\/\" target=\"_blank\" rel=\"noopener\">IAEI planning article<\/a> likewise frames EV charging as an electrical-infrastructure planning task. These sources support a documented process, not a universal test sequence.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/03\/EG40P-column1-2.webp\" alt=\"XYDF charging equipment used to illustrate functional-check planning context\" loading=\"lazy\" \/><figcaption>Equipment context only; the test method, electrical work, and approval path are project specific.<\/figcaption><\/figure>\n<blockquote>\n<p style=\"margin:0 0 16px;line-height:1.7\">Important: A successful first charging session is not a substitute for the complete responsible commissioning process. Electrical safety, protection, approvals, records, and operating instructions must be addressed according to the actual project and local requirements. <a href=\"https:\/\/iaeimagazine.org\/electrical-fundamentals\/electric-vehicle-charging-infrastructure-stations-equipment-and-planning\/\" target=\"_blank\" rel=\"noopener\">IAEI infrastructure planning guidance<\/a> provides the planning context.<\/p>\n<\/blockquote>\n<p style=\"margin:0 0 16px;line-height:1.7\">La <a href=\"https:\/\/xinya-ee.com\/fr\/blog\/ev-charger-emc-requirements-project-acceptance\/\">EMC requirements for project acceptance<\/a> article is related where electromagnetic-compatibility evidence belongs within the defined project scope. It should not be treated as proof that every installation has the same requirement or that a particular charger has been accepted.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">IEC 61851-1 describes general requirements for conductive EV charging systems, but a standard&#8217;s scope and a project test record are not a product certificate. Any compliance or certification claim needs its own applicable edition, assessment scope, issuer, and traceable evidence.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-4-what-information-should-operations-receive-at-handover\">Part 4. What information should operations receive at handover?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Operations need information they can use on the first normal day and the first abnormal day. That normally means the operating boundary, access rules, any known restrictions, a fault-reporting route, and the current controlled records. The <a href=\"https:\/\/xinya-ee.com\/fr\/blog\/ev-charger-factory-testing-incoming-inspection\/\">factory testing and incoming inspection guide<\/a> covers an earlier manufacturing-quality stage and should not be confused with site handover.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Keep the handover language specific. \u201cContact support\u201d is less useful than identifying the appropriate contact path for user issues, site access, electrical incidents, and changes to the operating model. Where manuals or training are part of the contract, record their version and owner rather than assuming a generic document applies.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For a networked site, the <strong>charging station handover<\/strong> should name the organization that owns each portal account and assign role-based access for operators, maintainers, billing staff, and administrators. Record how access is reviewed and revoked, along with approved tariffs, operating hours, support service levels, communications ownership, and the escalation route. Avoid shared administrator credentials in the handover pack.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Agree how long charger and backend logs are retained, who may export them, the export format, and which clock source and time zone apply. This makes transaction, alarm, and support records correlatable after an incident. The U.S. Department of Energy&#8217;s <a href=\"https:\/\/afdc.energy.gov\/fuels\/electricity_infrastructure_development.html\" target=\"_blank\" rel=\"noopener\">Alternative Fuels Data Center infrastructure guidance<\/a> also treats network, software, operation, and maintenance choices as part of deployment planning rather than afterthoughts.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Maintain one open-item register with severity, affected asset, operational consequence, temporary control, owner, deadline, and closure evidence. The authorized signatory should state which items block acceptance or operational release and which may be deferred; a signature should never hide an unresolved safety-critical defect.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-5-when-should-a-change-trigger-a-review\">Part 5. When should a change trigger a review?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">A change can affect the basis of the handover. Examples include a modified supply, replacement hardware, altered parking layout, a connector change, a new operating scope, or a changed site access arrangement. The change may require review before the equipment returns to service, depending on the project&#8217;s responsible process and local requirements.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Firmware updates, protection-setting changes, cable repair or replacement, network or backend migration, and civil work that affects foundations, drainage, vehicle impact protection, or buried services are specific re-commissioning triggers to assess. Define the affected tests from the change and its risk: a portal configuration update may require communications and transaction checks, while cable or protective-setting work can require renewed electrical verification. Preserve the previous and new baselines, impact assessment, test results, approvals, and return-to-service decision.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use a controlled question: what changed, who must assess the impact, what record changes, and who authorizes the return to the agreed operating state? That approach avoids treating commissioning as a one-time event disconnected from later site changes.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-6-how-should-project-responsibilities-be-recorded\">Part 6. How should project responsibilities be recorded?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Before handover, make the roles visible. The buyer or owner defines the project need, qualified electrical professionals handle their assigned design and verification duties, installers provide the information within their scope, and operations accepts the ongoing operating responsibilities defined by the project.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Jurisdiction and contract scope determine the legal roles, so a generic article cannot assign them. Instead, the project record should name the contacts, evidence owner, escalation path, and person authorized to control changes.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use separate sign-off fields when responsibilities differ: installer completion, electrical verification, network or backend acceptance, owner acceptance, and operational release. Each signatory should be accepting a named scope and revision, not an undefined statement that \u201cthe site is complete.\u201d<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-7-what-should-buyers-request-before-a-charging-project-is-released\">Part 7. What should buyers request before a charging project is released?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Ask for project information that enables a supplier and the responsible project team to define the scope, not a blanket assurance that equipment is \u201capproved.\u201d The following inputs give the conversation a usable technical and operational boundary.<\/p>\n<div style=\"width:100%;overflow-x:auto;-webkit-overflow-scrolling:touch\">\n<table style=\"width:100%;min-width:640px;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">L'acheteur doit fournir ou demander<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Pourquoi c'est important<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Site scope and vehicle\/connector context<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Defines the intended operating use<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Equipment identity and proposed layout<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Connects the requirement to the physical arrangement<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Electrical and as-built record expectations<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Clarifies documentation ownership<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Applicable local process and approval path<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Prevents unsupported compliance assumptions<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Functional-check and evidence expectations<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Makes acceptance scope discussable<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Operations, maintenance, and escalation contacts<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Creates a usable handover path<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Change-control contacts and trigger events<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Keeps later alterations traceable<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p style=\"margin:0 0 16px;line-height:1.7\">Once these inputs are available, buyers can review the <a href=\"https:\/\/xinya-ee.com\/fr\/chargeur-rapide-cc\/\">Cat\u00e9gorie des chargeurs rapides DC<\/a> in the context of the actual project. A request sent through the <a href=\"https:\/\/xinya-ee.com\/fr\/contacter\/\">page de contact<\/a> should include the site scope, operating conditions, local-process requirements, and documents expected. XYDF should respond to the documented request; this guide does not claim that a named product is commissioned, certified, or approved for a location.<\/p>\n<figure style=\"clear:both;float:none;margin:24px 0;\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/xinya-ee.com\/wp-content\/uploads\/2026\/03\/dc-charger60-240kw.webp\" alt=\"XYDF DC charging equipment used for project handover discussion\" loading=\"lazy\" \/><figcaption>Product context only; final equipment, installation, and approval suitability depend on verified project requirements.<\/figcaption><\/figure>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"frequently-asked-questions\">Foire aux questions<\/h2>\n<h3 style=\"margin:28px 0 12px\">What should be checked before an EV charging site is energized?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The responsible project process should address the installed arrangement, electrical safety and protection requirements, applicable records, and the defined operating boundary. Qualified professionals and local requirements determine the final checks.<\/p>\n<h3 style=\"margin:28px 0 12px\">Which documents belong in a handover pack?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The pack should identify the installed condition, controlled site records, responsible contacts, applicable approvals or inspections, operating information, and changes made during delivery. The exact documents depend on the project and jurisdiction.<\/p>\n<h3 style=\"margin:28px 0 12px\">Who signs off an EV charging installation?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The authorized parties are determined by the local process, contract scope, and responsible professional roles. A supplier or article cannot replace the project&#8217;s required approvals or sign-off path.<\/p>\n<h3 style=\"margin:28px 0 12px\">Is a successful charging session enough for commissioning?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. It can be part of functional evidence, but it does not by itself establish the complete electrical, safety, approval, record, and operational handover requirements.<\/p>\n<h3 style=\"margin:28px 0 12px\">What changes may require a new review?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Changes to supply, equipment, layout, connector arrangement, operating scope, or access conditions can affect the basis of the original handover. The responsible project team should assess the change before return to service.<\/p>\n<h3 style=\"margin:28px 0 12px\">What should operations receive at handover?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Operations should receive the agreed operating boundary, current controlled information, fault and escalation contacts, access rules, and any restrictions or change-control path defined by the project.<\/p>\n<h3 style=\"margin:28px 0 12px\">Can a supplier claim that a charger is locally approved?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Not without project-specific evidence. Buyers should verify the applicable requirements, records, approvals, and suitability through the responsible local process instead of relying on a generic product statement.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"references\">R\u00e9f\u00e9rences<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.networkrail.co.uk\/wp-content\/uploads\/2023\/11\/NR-GN-CIV-200-13-Electric-Vehicle-Charging-Points-and-Associated-Infrastructure.pdf\" target=\"_blank\" rel=\"noopener\">Network Rail guidance on EV charging points and associated infrastructure<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/iaeimagazine.org\/electrical-fundamentals\/electric-vehicle-charging-infrastructure-stations-equipment-and-planning\/\" target=\"_blank\" rel=\"noopener\">IAEI article on EV charging infrastructure planning<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.iea.org\/reports\/global-ev-outlook-2025\" target=\"_blank\" rel=\"noopener\">Perspectives mondiales des v\u00e9hicules \u00e9lectriques 2025 de l'AIE<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/afdc.energy.gov\/fuels\/electricity_infrastructure_development.html\" target=\"_blank\" rel=\"noopener\">U.S. Department of Energy Alternative Fuels Data Center: developing charging infrastructure<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/openchargealliance.org\/protocols\/open-charge-point-protocol\/\" target=\"_blank\" rel=\"noopener\">Open Charge Alliance : Open Charge Point Protocol<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>EV charging commissioning should create a clear record of what was installed, what the responsible project process checked, and what operations need after handover. A vehicle beginning to charge is useful functional evidence, but it is not by itself the complete electrical, operational, or local-approval record. Equipment context only; commissioning requirements and approval must be [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":872,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,7],"tags":[],"product-features":[],"class_list":["post-3564","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-commercial"],"_links":{"self":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/3564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/comments?post=3564"}],"version-history":[{"count":2,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/3564\/revisions"}],"predecessor-version":[{"id":4787,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/posts\/3564\/revisions\/4787"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/media\/872"}],"wp:attachment":[{"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/media?parent=3564"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/categories?post=3564"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/tags?post=3564"},{"taxonomy":"xinya_product_feature","embeddable":true,"href":"https:\/\/xinya-ee.com\/fr\/wp-json\/wp\/v2\/product-features?post=3564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}