What we do
Edge-to-cloud platforms on open standards: OCPP for charging infrastructure, unified namespace architectures for manufacturing data, MQTT and industrial protocol integration, and the telemetry pipelines that make field data usable. Plus the analytics layer, built by people who have published degradation models against real telemetry.
The unified namespace, done properly
A unified namespace is the difference between a factory’s data being an asset and being an archaeology project: one coherent topic hierarchy, consistent payloads, every system publishing into a structure the next system can trust. The discipline is in enforcement, which is why we built and open-sourced a validator that checks topics and payloads against the declared structure, so data quality is caught at the topic level instead of discovered in the dashboard.
Charging infrastructure and OCPP
EV charging is industrial IoT with a revenue meter attached, and OCPP is its lingua franca. We work across the protocol span: charge point management integration, telemetry capture, and the operational analytics above it. Our public work leads here: an open-source degradation model built on OCPP telemetry flagged 25 of 25 degrading units in field data, with detection landing around two weeks in, methodology published and checkable.
Telemetry you can act on
Field data arrives late, duplicated, gappy and occasionally lying, and analytics built on the assumption of clean input produce dashboards nobody trusts. Our pipelines treat data quality as a first-class engineering problem: validation at ingestion, gap and duplicate handling with explicit semantics, lineage so a suspicious number can be traced to its source, and models validated against the ugly reality of production telemetry rather than a curated sample.
Questions we hear before engagements
Can you retrofit existing equipment?
Yes; brownfield is the normal case. Protocol bridging from legacy PLCs and serial equipment into a modern namespace is standard work, and our embedded practice handles the physical interfacing.
Which protocols do you support?
MQTT and Sparkplug, OPC UA, OCPP, Modbus and the industrial serial family, plus the automotive CAN world through our gateway work. Protocol choice follows the equipment, not fashion.
How is security handled?
Per-device identity, certificate-based provisioning, encrypted transport, and network segmentation designed with the same seriousness as the rest of our infrastructure practice.
Who owns the data and the platform?
You do. Open standards and open-source foundations are the anti-lock-in position, and the namespace design is documentation you keep.
Related capability
If your system has to be right, let’s talk.
Start the conversation →