SOLUTIONS

Markets, and the standards
they actually run on.

Below is the standard each market runs on, what state our work in it is in, and a link to the thing itself rather than a description of it. Where we have not built something, it says so.

THE COMMON THREAD

A databus, not a message bus.

Most systems built on DDS® use it as a pipe: a payload goes in one end and comes out the other, and everything that made it data rather than a message is left behind. We model the standard instead. Topics are typed from the specification's own files, identity becomes the key so each device is an instance with its own lifecycle, and quality of service follows from what each topic means.

That is one argument, and every entry below is a different proof of it.

Defense & Government

Shipping

Ship a MIL-STD-3071 device without putting a DDS® specialist on the team.

MIL-STD-3071 — the Tactical Microgrid Standard

Every forward base runs on a microgrid, and the generators, batteries and loads come from different vendors. The standard gives them one language, but a compliant device means learning DDS® first and then hundreds of pages of rules on heartbeats, controller failover, rate limits and reply codes. Get one wrong and the device fails to interoperate, usually with no visible error.

Nexus TMS SDK implements it. All 37 topics come from the files published with the standard, unmodified; every requirement in the code cites the clause it implements; replies go out inside the standard's 0.1-second limit. Generator, storage, loads and primary and standby controllers with failover run in simulation today.

Robotics & Intralogistics

Building

VDA5050 without the polling, the resends and the last-will stand-ins.

VDA5050 3.0 — fleet manager to AGVs and AMRs  ·  ROS 2

VDA5050 is JSON over MQTT through a broker, and because MQTT publishes most of its topics at QoS 0, a good deal of the specification is application-layer reliability written out in prose: an order base that cannot be revoked, resend-until-acknowledged, polling to recover state, a last-will message standing in for liveliness.

We are modelling the 3.0 revision natively — all 253 fields of the eight official schemas, keyed on manufacturer and serial number so each robot is an instance with its own lifecycle, with quality of service derived per topic instead of applied uniformly to an opaque payload. The claim is deliberately narrow: it removes the transport workarounds, so what is left is domain logic. Base and horizon semantics stay exactly as written, because a robot may already be driving the base. A ROS 2 RMW layer on the same principle is in progress.

Neither is published, and we are not claiming VDA5050 or ROS 2 support. When they are public they will appear here, the way Nexus TMS did. Compliance belongs at the bridge in any case: the specification names MQTT, and DataBridgeX already speaks it.

Industrial Automation

Bridged

Get context-carrying data out of the plant you already have, without writing protocol code.

OPC UA · Modbus · Siemens S7 · MQTT · SQL — connected, not reimplemented

The data is already there, inside controllers, instrumentation, databases and applications, each in its own protocol. On its own it tells you what a value was, not what was happening when it changed. A historian records; a protocol gateway translates. Neither gives you context.

DataBridgeX brings those systems into one set of data pathways and attaches the context you define, so a torque reading becomes a torque reading during Test Run 14, Phase 2. Six connectors ship today. We do not implement these standards — we connect to them, which is the honest description of a bridge.

Working to a standard we have not listed?

Tell us which one. The modelling work is the same whichever specification it starts from.