Ray · For EV charger OEMs
Your data. Our intelligence.
Your chargers report to the operator's CMS. Ray gives you your own line to them: component health, OCPP messages and remote fixes, in one cloud platform.
01 · The OEM blind spot
Your chargers talk to the CMS. Not to you.
Once a charger is installed, its data goes to the operator's CMS. When something goes wrong, the people who built the charger are the last to know.
01
OCPP data goes to the CMS, not to you
The charger reports to whichever CMS the operator chose. You can't see what your own charger is saying.
02
OCPP only tells part of the story
It shows status and fault codes, not why a power module overheated or a contactor failed. Enough to monitor, not to diagnose.
03
You need component data to build better chargers
Root causes, failure patterns and real-world performance improve your next design. Without them, you're guessing.
Ray gives you a direct line to every charger you've built: its OCPP messages and its component data, sent straight to you.
02 · What Ray understands
Ready for every part of your charger.
Ray comes with a ready data model for each key component. Send the metrics, and Ray knows what they mean.
Power modules
Health, output, temperature and faults.
AC and DC contactors
Open or closed state, confirmation and wear.
Input power supply
Voltage, current, frequency and quality.
Output power
Delivered power, voltage and current.
Guns and connectors
Connection state, temperature and usage.
Cabinet
Internal temperature, humidity and cooling.
Door
Open or closed, and tamper events.
03 · How it works
Collect. Send. Understand. Act.
STEP 01
Collect
Your charger gathers metrics from its components.
STEP 02
Send
Stream them to Ray's secure WebSocket backend, in an OCPP-like message format.
STEP 03
Understand
Ray turns the data into health dashboards, alerts and diagnosis.
STEP 04
Act
Diagnose remotely, fetch logs, change settings or push an OTA update.
Ray gets data straight from the charger, so it works whichever CMS your customers use.
04 · What Ray does
Monitor, diagnose and fix from anywhere.
OCPP message monitoring
Your charger sends a copy of its OCPP messages to Ray, so you see what the CMS sees and know exactly where a session failed.
Charger health monitoring
Contactors, power modules, temperatures, electrical parameters, faults and alarms, down to the component.
Connectivity health
Network stability, CMS connection, disconnects, retries, latency and communication failures.
Remote operations
Remote diagnostics, configuration and parameter updates, log retrieval, remote commands and OTA firmware updates.
05 · From alert to fix
Know the fault before you leave the office.
STEP 01
Alert
Contactor 2 did not confirm it closed.
STEP 02
Diagnose remotely
Check its logs, OCPP messages and component data.
STEP 03
Fix
Push a configuration change or update over the air, or send an engineer who already knows the fault and has the right part.
06 · You collect, we make sense of it
You build the charger. We build the platform that watches it.
You
– Build great chargers
– Collect component data
– Send it to Ray
We
– A ready data model for every component
– Processing, health scoring and fault detection
– Dashboards and alerts
– Remote commands and OTA delivery
– Cloud, uptime and security
07 · What OEMs get
Fewer site visits. Better chargers.
Fewer site visits
Diagnose remotely; travel only when a part needs replacing.
Faster fixes
Engineers arrive knowing the fault, with the right part.
Lower warranty cost
Catch failing parts early, before they cause bigger damage.
Better uptime for your customers
Operators see fewer failures on your hardware.
Better next-generation chargers
Real-world component data feeds your design and testing.
08 · Who it's for
Built for the people who build chargers.
09 · FAQ
Questions OEMs ask.
What do we need to build?
Data collection on the charger and sending it to Ray. Everything after that is Ray.
Which components does Ray support?
Power modules, AC and DC contactors, input and output power, guns, cabinet, door and more.
Does it work with any CMS?
Yes. The Ray platform has nothing to do with the CMS. Ray receives data directly from the charger.
Does Ray replace the CMS?
No. The CMS runs the business: sessions, payments and drivers. Ray is the OEM's view of the hardware. Both run side by side.