Integrators

EMP Simulator open

OCPI testing against any CPMS: simulate roaming flows, provoke errors, validate payloads.

Open simulator → Got questions? Get in touch

The EMP Simulator mirrors the EMP Backend: instead of receiving CDRs, it sends them. You pick a CPMS target URL, credentials A/B/C, and run defined scenarios — publish tokens, start a session, deliver a CDR, pull tariffs.

Accessible without login at empsim.pipelet.com — any CPMS operator can verify in minutes whether their OCPI implementation handles the standard handshake and payloads cleanly.

What to expect

✓

Any CPMS target

Target URL is freely configurable. Credentials handshake with your own party_id, tokens A/B/C exchanged once, then full OCPI flows.

✓

Predefined scenarios

Token publish, session start/stop, CDR delivery, tariff pull — each scenario as a one-click run with visible request/response logs.

✓

Payload validator

Incoming CPMS responses are validated against the OCPI 2.2 schema. Deviations are flagged immediately.

How EMP Simulator fits into the suite

Integrates with

EMP Simulator https://empsim.pipelet.com

Driver Portal Home charging, charging history, CarData integra Fleet Portal Fleet management, driver management, RFID and bi CPMS Core The new operator UI: sites, charger commands, vo

Frequently asked questions

Is Pipelet available as source code?

Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.

Which OCPP versions are supported?

Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.

Can I use individual modules only?

Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.

What does onboarding look like?

We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.