The development of the Open Charging Network is steered by community needs with the non-profit Share&Charge Foundation curating the development. For this purpose, transparency about the current feature set is required, which the following OCN maturity model (inspired by Gitlab) shall provide. The maturity model and the roadmap of the Open Charging Network development is discussed quarterly during the Share&Charge Foundation and Tech Call.
The maturity model is based on different categories (columns):
Messaging: How messages between OCN Parties are transmitted and secured
Service interfaces: Interfaces that can be used by OCN Parties to connect their services to the OCN
Connection & Community: Tools for the community to test and use the OCN
Maturity is indicated with different-sized black boxes or a heart:
▪ Planned: Requirements are getting defined
◾ Minimal: First implementations are tested
⬛ Viable: Can be used in production
🖤 Lovable: Functionality set is complete and used by community
A reference to the open source repositories is provided in paranthesis after the feature description.
Messaging | Service interfaces | Community & Network tools | |
|---|---|---|---|
Release 1.0.0 (03.03.2020) | ⬛ OCPI 2.2 messaging (OCN-Node) ⬛ Address book for message routing (OCN-Registry) ⬛ Signed OCPI messages (OCN-Notary) ⬛ White-/Blacklisting of OCPI parties (OCN-Node) | ⬛ OCPI 2.2 CPO & eMSP interface (OCN-Node) | ◼ CPO & eMSP testing tools (OCN-Tools & OCN-Demo) |
Release 1.1.0 | ◾ OCN Service Permissions (OCN-Registry) ◾ OCPI 2.2 HubClientInfo Module (OCN-Node) ◾Custom OCN / OCPI message (OCN-Node) | ◾ OCN Service Interface (OCN-Node) | ◾ OCN Service Interface testing tools (OCN-Demo) |
On Roadmap | ◾ Non-OCPI API connections (OCN-Bridge) | ||
Ideas / Requirements / Addons | ▪ Decentralized Identifiers for OCN Registry | ◾ ERC20 Token interface (Settlement & Token Bridge) | ▪ OCPI 2.1.1 bridge ▪ OCN / OCPI 2.2 testkit |
For a detailed list of all current issues across all open source components, please visit this page.