Scope
We map your vehicle models, charger models, sites and back-office platform, then agree on the pairs that actually need testing. Usually fewer than you expect.
An OS Technologies service
Plug&Proveby OS Technologies Inc.Proof before the first truck arrives
Plug&Prove is independent interoperability testing for EV charging. We put your actual vehicles and your actual chargers through a real session, capture what happens at protocol level, and hand you evidence — not opinions.
Independent third partyBench + on siteWritten evidence
Why it matters
A failed commissioning is not a technical problem
It is a schedule problem, a budget problem, and a contract problem. When a bus will not start a charging session on go-live morning, nobody in the room can say whose fault it is — and every day the fleet sits idle is a day you pay for twice. Plug&Prove moves that discovery to a moment when it is still cheap to fix.
- The fault is isolated to the vehicle, the station or the back office — with a capture to prove it
- Your suppliers stop pointing at each other, because the evidence is neutral
- Commissioning windows shrink, and so does the number of return visits
- You hold a written record you can attach to a purchase order or a claim
1
day of idle fleet can cost more than the whole test campaign
11+
charging standards in our coverage
3
layers checked: vehicle, station, back office
2020
testing charging interoperability since
What you get
Evidence, not opinions
- 01Compatibility matrix
Every vehicle model against every charger model you plan to deploy, with a pass, fail or conditional verdict for each pair.
- 02Session captures
The raw protocol exchange for each test, timestamped and replayable — so a finding can be re-examined months later, by anyone.
- 03Root-cause report
For each failure: where in the session it broke, which side deviated from the standard, and what has to change.
- 04Prioritised fix list
What blocks go-live, what can wait, and what is cosmetic — so your team knows what to escalate to which supplier first.
How it runs
Four steps, no surprises
Bench
Controlled testing with instrumented equipment, before anything reaches a site. Most incompatibilities surface here, where fixing them costs a phone call.
Field
On-site validation with your real vehicles on your real infrastructure — because cable length, grounding and firmware versions all change the answer.
Report
The matrix, the captures and the prioritised findings, walked through with your team and your suppliers.
The technical layer
What we watch inside a session
A DC charging session is a long negotiation between two computers that have never met. Most field failures are not electrical — they happen in one of these steps, and without instrumentation there is nothing to see but a red light on a charger.
01
Link-upSLAC / ISO 15118-3
Powerline matching between vehicle and cable. Attenuation, retries, and the tricky case of a vehicle matching the charger in the next stall.
02
DiscoverySDP · TCP/TLS
The vehicle finds the charging controller and opens a secure channel. Certificate chains and TLS versions are a frequent, and silent, failure point.
03
App handshakesupportedAppProtocol
The two sides agree which protocol version they will speak. A mismatch here ends the session before any energy is discussed.
04
AuthorisationEIM · Plug&Charge
External identification, or a contract certificate presented by the vehicle. This is where most fleet deployments meet their first real wall.
05
ParametersChargeParameterDiscovery
The vehicle states what it wants, the station what it can give. Limits, schedules and the negotiated ramp all come from here.
06
Safety checksCableCheck · PreCharge
Insulation verification and voltage matching before the contactors close. Timeouts in this phase are a classic source of intermittent failures.
07
Energy transferCurrentDemand loop
The actual charge, with metering. We watch for derating, dropped setpoints and the difference between what was promised and what was delivered.
08
ShutdownPowerDelivery · WeldingDetection
A clean stop, contactor welding detection and session close — the part everyone forgets to test until a charger locks a cable in place.
09
Back officeOCPP 1.6 · 2.0.1 · 2.1
What the station reports to your platform: transaction records, meter values and status notifications. Billing disputes start here.
Standards in our coverage
If a standard you depend on is not on this list, ask — coverage moves with the industry, and we would rather tell you plainly than stretch.
Who calls us
When Plug&Prove is the right call
Before a fleet deployment
You have chosen vehicles and chargers but nothing has been installed. This is the cheapest possible moment to find out they disagree.
During a stalled commissioning
Equipment is on site, sessions fail intermittently, and each supplier says the problem is on the other side.
As a neutral third party
You need an assessment that neither the vehicle manufacturer nor the charger vendor wrote, to support a decision or a claim.
Plug&Proveby OS Technologies Inc.Tell us what you are deploying
Vehicle models, charger models, sites, timeline. We will tell you which pairs are worth testing and what a campaign would involve.