OEM AND MACHINE BUILDERS
SHIP YOUR MACHINES WITH THE EVIDENCE
You specified the controller. Haltless reads it, scores the machine on a published formula, and signs the record. No new sensors, no change to your bill of materials.
- Protocols
- OPC UA, Modbus TCP, CSV and JSON file watch
- Footprint
- One Linux box on the OT side
- Direction
- Outbound only, no inbound path
- Writes to the process
- None, by design
WHY AN OEM CARES
Four things this changes for a machine builder
Most monitoring pitches to an OEM are about selling your customer something extra. This one is mostly about what happens after the machine leaves your factory and something goes wrong.
Warranty claims stop being an argument
When a customer says the machine failed and you say it was run outside spec, both of you are recalling. A tamper-evident chain of what the machine was actually doing, signed and verifiable offline, replaces that conversation with a record. It is the same evidence either way, which is what makes it worth having.
Aftermarket service you can price
Condition monitoring is the service contract most builders want to sell and few can staff. Detectors that run without a data scientist, and a health score your own service team can explain to the customer, make that offer something you can quote rather than something you have to build.
Nothing added to the bill of materials
The edge agent reads the tags your PLC already publishes over OPC UA or Modbus TCP. In the common case there is no new sensor, no extra panel component and no change to a machine you have already certified.
A number your customer can check
You will be asked how the score works, by an engineer who does not trust vendors. A published formula and a per-event deduction table mean you can answer instead of forwarding the question. A black box makes your machine look like the black box.
HOW IT SHIPS
What this looks like on your line
You keep the controller choice
OPC UA and Modbus TCP are in production, with CSV and JSON file watch for machines that only drop files. MQTT, native Siemens S7 and EtherNet/IP via CIP are the next committed protocol work.
One Linux box, outbound only
The agent is a small process on a Linux box on the OT side. Outbound only, no inbound path, no reverse tunnel, and it buffers locally through WAN outages lasting days. Your customer’s IT team will ask about exactly this.
It reads and never writes
No control action, no setpoint change, no path back into the process. That keeps it outside your machine’s control-system validation and out of IEC 61511 safety scope, which is the answer your compliance people need before anything else.
WHAT WE DO NOT HAVE
What an OEM programme does not include yet
Haltless is pre-launch with general availability in Q1 2027. These are the things a mature OEM programme would have and this one does not.
- No white-label or OEM branding. The portal says Haltless, and there is no theming layer to put your name on it.
- No embedded licensing tier. Per-machine pricing quoted per deal, not a per-unit royalty built into your machine cost.
- No reference OEM to call. Nobody has shipped a machine with this yet, and we will say so rather than describe a pilot as a deployment.
HOW TO START
Bring one machine
Pick a machine you already have on a test floor, tell us the controller and the three tags you would want watched, and we will tell you what the score would look like. That is a short conversation, and it answers more than a demo would.
COMMON QUESTIONS
Questions from machine builders
Can I white-label Haltless under my own brand?
Not today. There is no theming layer and no OEM branding, so your customer sees Haltless. If white-label is a requirement rather than a preference, this is not ready for you yet, and that is worth knowing before a first call rather than after.
Does adding this affect my machine’s certification?
It should not. The agent reads and never writes: no control action, no setpoint change, no path back into the process. It sits outside the control-system validation envelope and outside IEC 61511 safety scope by design. Your own conformity assessment is still yours to run.
Do I need to add sensors to my machines?
In the common case, no. Haltless reads tags your PLC already publishes, so the data usually exists before the platform arrives. Where a failure mode has no signal on the controller at all, no software can invent one, and we will tell you that rather than sell around it.
How is this priced for a machine builder?
Per machine, quoted per deal, the same as any other customer. There is no per-unit royalty or embedded licence tier yet, because Haltless is pre-launch and a unit price set before the first machine ships would be a number invented for a page.