Open OCPP Trace is an open, vendor-neutral specification for exchanging, storing, and analyzing OCPP traces. It defines a common format so that different OCPP tools can share traces without being tied to any single implementation.

Status: Early design phase. The specification is not yet stable and is subject to breaking changes.

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.

• Define a stable, versioned format for OCPP traces.
• Remain neutral with respect to vendors and implementations.
• Enable interoperability between independent OCPP tools.
• Provide schemas that allow traces to be validated automatically.
• Support conformance testing against the specification.

This organization maintains the specification and its supporting material:

• Specification — the format definition and semantics.
• Schemas — machine-readable schemas for validation.
• Examples — reference traces demonstrating the format.
• Conformance tests — checks that verify format compliance.

Tool implementations are out of scope here and remain in their own repositories.

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.