Apa Itu OCPI and Reference File Download Link
https://eu2.contabostorage.com/00f3241116844f24b628f46d81abb929:st1/folder7/7262/1656286921_ocpi_certificationtests_emsp_v1_1_-_Standar_Format.xlsx
2026-05-30 22:32:04 - Admin
<style> body { font-family: Arial, Helvetica, sans-serif; line-height: 1.6; margin: 0; padding: 0 20px; background-color: #f9f9f9; color: #333; } h1, h2, h3 { color:#004080; } a { color:#0066cc; } .container { max-width: 800px; margin: 40px auto; background:#fff; padding:30px; box-shadow:0 0 10px rgba(0,0,0,0.1); } table { width:100%; border-collapse:collapse; margin:20px 0; } th, td { border:1px solid #ddd; padding:8px; text-align:left; } th { background:#f2f2f2; } .note { background:#e7f3fe; border-left:4px solid #2196F3; padding:10px; margin:20px 0; } </style><div class="container"> <h1>Apa Itu OCPI?</h1> <p>OCPI stands for <strong>Open Charge Point Interface</strong>. It is an opensource protocol that enables the exchange of information between electricvehicle (EV) charging stations, emobility service providers (EMSPs), and other stakeholders in the charging ecosystem. By standardising how data such as session details, tariffs, and status updates are shared, OCPI makes it possible for drivers to use any compatible charger using a single account, while operators can manage their networks more efficiently.</p> <h2>Why OCPI Matters</h2> <p>The rapid growth of electric mobility creates a need for seamless roamingjust as mobilephone users can switch between networks without changing SIM cards. OCPI provides the roaming agreement for EV charging, ensuring that:</p> <ul> <li><strong>Drivers</strong> can locate, start, and pay for charging at any participating station.</li> <li><strong>Operators</strong> can share usage data and settle payments without building custom integrations.</li> <li><strong>Utilities</strong> gain insight into load patterns for better grid management.</li> </ul> <h2>Core Concepts</h2> <h3>Roles</h3> <table> <thead> <tr><th>Role</th><th>Description</th></tr> </thead> <tbody> <tr><td>CSO (Charge Station Operator)</td><td>Owns and manages physical charging points.</td></tr> <tr><td>EMSP (EMobility Service Provider)</td><td>Offers charging services to EV drivers, handling authentication, billing, and roaming.</td></tr> <tr><td>Hub</td><td>Optional intermediary that aggregates data from multiple CSOs and EMSPs.</td></tr> </tbody> </table> <h3>Key Modules</h3> <ul> <li><strong>Locations</strong> Information about each charger: address, connectors, capabilities, and status.</li> <li><strong>Tariffs</strong> Pricing rules, including timeofday rates, energybased fees, and extra services.</li> <li><strong>Sessions</strong> Realtime data on each charging transaction: start/stop time, energy delivered, and cost.</li> <li><strong>CPOEMSP Commands</strong> Remote actions such as starting/stopping a charge or reserving a connector.</li> </ul> <h2>How OCPI Works</h2> <p>OCPI operates over HTTPS using a RESTlike API. Both parties expose a set of endpoints; the direction of data flow is defined by the role (CPO EMSP). A typical workflow looks like this:</p> <ol> <li>The CPO publishes <em>Location</em> data, allowing the EMSP to display available chargers in its app.</li> <li>An EV driver selects a charger, and the EMSP sends an <em>Authorize</em> request to the CPO.</li> <li>The CPO confirms the drivers eligibility and unlocks the connector.</li> <li>During charging, the CPO streams <em>Session</em> updates to the EMSP.</li> <li>When the session ends, the CPO sends a final <em>Session</em> record, and the EMSP handles billing.</li> <li>Both parties periodically exchange <em>Tariff</em> updates to keep pricing current.</li> </ol> <h2>Version History</h2> <p>OCPI was first released in 2015. Since then, several versions have been published, each adding features and improving security:</p> <ul> <li><strong>v1.0 (2015)</strong> Basic location, tariff, and session exchange.</li> <li><strong>v2.0 (2017)</strong> Introduced token management, more detailed status codes, and improved authentication.</li> <li><strong>v2.1 (2020)</strong> Added support for reservations, multitariff handling, and optional hub architecture.</li> <li><strong>v2.2 (2023)</strong> Enhanced security with OAuth2, better error handling, and optional fields for future extensions.</li> </ul> <h2>Benefits for Stakeholders</h2> <h3>For Drivers</h3> <ul> <li>One account works across many networks.</li> <li>Transparent pricing displayed before charging.</li> <li>Realtime status (available, occupied, outoforder).</li> </ul> <h3>For Operators</h3> <ul> <li>Reduced integration cost a single API replaces multiple proprietary ones.</li> <li>Faster onboarding of new partners.</li> <li>Clear settlement process based on standardized session records.</li> </ul> <h3>For Grid Managers</h3> <ul> <li>Aggregated load data enables demandresponse programs.</li> <li>Better forecasting of peak charging periods.</li> </ul> <div class="note"> <strong>Note:</strong> OCPI is not a mandatory standard; it is voluntary and governed by the <a href="https://www.e-mobilitynews.com/ocpi-foundation" target="_blank">OCPI Foundation</a>. Participation is open to any organization willing to implement the specification. </div> <h2>Getting Started with OCPI</h2> <p>Organizations interested in adopting OCPI can follow these steps:</p> <ol> <li><strong>Read the Specification</strong> The latest version is available on the official GitHub repository.</li> <li><strong>Choose a Role</strong> Decide whether you will act as a CPO, an EMSP, or a hub.</li> <li><strong>Implement the API</strong> Use existing opensource libraries (e.g., <code>ocpi-lib</code> for Node.js or <code>ocpi-java</code> for Java) or develop a custom solution.</li> <li><strong>Set Up Security</strong> Configure TLS certificates and OAuth2 tokens as described in the security chapter.</li> <li><strong>Test Interoperability</strong> Join a compliance test program or exchange test data with a partner.</li> <li><strong>Go Live</strong> Enable realtime data exchange and begin processing transactions.</li> </ol> <h2>Common Misconceptions</h2> <ul> <li><strong>OCPI is only for Europe.</strong> While it originated in European markets, the protocol is global and has adopters in North America, Asia, and Oceania.</li> <li><strong>OCPI replaces OCPP.</strong> OCPP (Open Charge Point Protocol) governs communication between a charger and its management system, whereas OCPI handles communication between different business entities. They complement each other.</li> <li><strong>OCPI is a proprietary product.</strong> It is an open, royaltyfree standard maintained by an industry consortium.</li> </ul> <h2>Future Outlook</h2> <p>As EV adoption accelerates, the need for seamless crossnetwork charging will become more critical. Upcoming enhancements being discussed by the OCPI community include:</p> <ul> <li>Support for ultrafast DC chargers (up to 350kW).</li> <li>Integration with smartgrid APIs for realtime load balancing.</li> <li>Standardised data fields for carbonintensity and renewableenergy sourcing.</li> </ul> <p>These developments aim to keep OCPI at the heart of a truly interoperable, sustainable charging ecosystem.</p></div>