Exchange, store, and analyze OCPP traces in one shared format — so different tools can work with the same data without being tied to any single implementation.
Why this project exists
OCPP traces are produced and consumed by many tools — charge point simulators, CSMS test suites, diagnostic utilities, and log analyzers — but each tool captures traces in its own format. This fragmentation makes it hard to move data between tools, reproduce issues across environments, or build shared analysis and conformance tooling.
Open OCPP Trace addresses this by providing a single interchange format that any tool can read and write.
Goals
- Stable, versioned format — a well-defined format for OCPP traces.
- Vendor neutrality — independent of any vendor or implementation.
- Interoperability — traces flow between independent OCPP tools.
- Automatic validation — schemas let traces be validated by machines.
- Conformance — implementations can be tested against the specification.
Scope
This organization maintains the specification and its supporting material. Tool implementations remain in their own repositories.
Specification
The format definition and semantics.
Schemas soon
Machine-readable schemas for validation.
Examples soon
Reference traces demonstrating the format.
Conformance tests soon
Checks that verify format compliance.
Contributing
The specification is being designed in the open, and feedback is welcome. If you build or maintain OCPP tooling, your input on the format and its requirements is especially valuable. Open an issue to discuss use cases, propose changes, or report gaps.