SYSTEM INTEGRATORS
SPEC IT INTO THE JOB YOU ALREADY WON
A small Linux process on the OT side, reading tags your own commissioning already exposed. This is a line item on work you are doing anyway, not a second project running beside it.
WHAT YOU ARE SPECIFYING
Four things to put in the scope of work
The partnership side of this lives on its own page. This one is about delivery: what you write into the proposal, what you install, and what you have to be able to defend at handover.
Hardware
One box and one firewall rule
A small process on a Linux box on the OT side. Outbound only over TLS, no inbound path, no reverse tunnel, and it buffers locally through WAN outages lasting days. What you are specifying is the box, the egress rule and a read-only account. That is the whole footprint.
Scope
The tag list is the deliverable
In the common case there is no new sensor and no extra panel component, because the agent reads what the PLC already publishes over OPC UA or Modbus TCP. The real work is deciding which tags matter on this plant, and you are better at that than we are.
Safety
It reads and never writes
No control action, no setpoint change, no path back into the process. That keeps it outside the control-system validation you are signing off and outside IEC 61511 safety scope. It is the first thing the client’s process safety people will ask about, and it should be the easiest answer you give all week.
Handover
A number you can defend at handover
The health score is a published formula with a per-event deduction table, so it recomputes from the same records on paper. When the client’s engineer asks how it works, you answer out of the handover document instead of forwarding the question to a vendor and waiting.
COMMISSIONING
What the install day actually looks like
- Under an hour on site
- Install the agent, point it at the endpoint, give it a read-only account and the tag list. There is no model to train and no baseline period to sit through before it does anything, because the detectors are thresholds, rates and windows rather than something learned.
- It opens work orders, it does not replace the CMMS
- Production adapters for SAP S/4HANA, Oracle EBS and Microsoft Dynamics 365 write into the system the client already runs, behind the same audit chain. Nobody has to migrate anything for this to earn its place.
- What you need from the client
- A read-only account on the controller or historian, one outbound egress rule, and somebody who can say which failure modes actually cost them money. Where a failure mode has no signal on the controller, no software invents one, and that is far better discovered in scoping than in the acceptance test.
WHAT WE DO NOT HAVE
What you cannot put in a proposal yet
Haltless is pre-launch, with general availability in Q1 2027. Three things an integrator would reasonably expect, and the honest state of each.
No certification track. Training is direct, one integrator at a time. There is no exam and no badge to cite in a tender, and there will not be until enough integrators exist to justify writing a curriculum.
No integrator who has done this before you. There is no reference project to visit and no war story from a previous commissioning, so ask about that early rather than discovering it late.
No standing resale line item. Referral is the model until general availability, with one exception for a fixed-price plant project where owning the line item is the only structure that works. The commercial side is on the partnerships page.
HOW TO START
Bring a job you are scoping
Send the controller, the plant, and the three failure modes the client keeps paying for. We will tell you what the agent could see and what it could not, before you write it into a proposal you have to stand behind.
Contact usCOMMON QUESTIONS
Questions from integrators
Do I need a certification to deploy Haltless?
No, and there is nothing to certify against yet. Training is direct rather than a curriculum, and the technical surface is small: the agent installs in under an hour and reads tags your controllers already publish. When there are enough integrators for a course to be worth writing, we will write one.
Can I carry Haltless as my own line item on a fixed-price project?
Yes, agreed one deal at a time. Referral is the standard model until general availability, but an integrator bundling this into a fixed-price plant project has to own the line item, and that is the exception we write down rather than argue about later. We stay on the technical calls either way.
Does the agent touch the control system?
It reads and never writes. No control action, no setpoint change, no path back into the process, so it sits outside the validation envelope you are signing off and outside IEC 61511 safety scope by design. The conformity assessment is still the client’s to run and yours to support.
What if the client will not allow outbound traffic?
Then it does not run, and we would rather say so in scoping than in week three. The agent is outbound only over TLS and needs one egress path. There is no inbound listener and no reverse tunnel to offer as a workaround, because the plants that ban outbound traffic ban those harder.