About the Client
A precision CNC machining manufacturer serving defense and automotive programs — the kind of parts that carry inspection paperwork per lot and program data that never leaves the environment casually. The operation runs lean: a shop floor of machinists and programmers, a small front office, and no dedicated internal endpoint-engineering function.
Surya operates the endpoint estate end to end. That includes building and maintaining the automated build itself — this is the "Surya builds and maintains it" path in practice. Office personas and machine-adjacent floor personas are engineered by Surya, kept current by Surya, and every decision — driver pin, package add, baseline change — is logged for the customer's sign-off. The customer still owns the running estate: security posture, access, and policy authority all stay on their side. What we own is the build itself and the physical logistics behind it.
The Finding
Seventeen months of ticket history on this fleet showed exactly 13 production-floor endpoint events — the machine-adjacent PCs and HMIs tied to CNC controls going down for a reason that stopped a machine.
That number is what reframes the problem.
Floor endpoints fail rarely. Nobody hires a technician to sit and wait for a device that fails less than once a month across the whole shop. But when one does fail, a machine stops, and the machine is the business — parts do not ship, program windows slip, and inspection paperwork backs up behind them. Rare-but-total failure is not a staffing problem. It is a custody problem: hold a configured spare, swap it in minutes, RMA the failed unit from the hub.
Framed that way, the answer is logistics, not headcount.
The Approach
Configuration is treated as the asset. Each floor endpoint has a vendor-locked, machine-tied configuration — specific control software versions, specific driver pins, specific network settings — documented and held per serial. When a spare goes out, the spare that arrives is the spare that was supposed to arrive; the machine it plugs into does not know a swap happened.
A configured spare is staged for each class of floor endpoint that can stop production. When a floor unit fails, the swap runs on the same physics as the laptop fleet: the spare goes to the floor, the failed unit is recovered under serialized chain of custody, and the RMA cycle runs from the RTP hub, not from a corner of the shop.
Drives are sanitized to NIST 800-88 with certificates before anything leaves the environment. Defense and automotive program data lives on these machines; the sanitization certificate is filed against the serial before disposition. That is the same posture the RTP hub runs for every recovered device — the difference here is that the customer's supply-chain paperwork depends on it.
Distance is not a factor. The customer is nowhere near North Carolina; the kit-and-ship model and the staged spares are the whole point. National coverage from one hub is what makes a single-campus operation of this size worth running as a program in the first place.
Beyond the laptops — where the Surya Critical idea came from
This engagement is one of the places Surya Critical came from. When floor endpoints failed, the customer didn't need a service desk — they needed a configured spare in a hand within minutes. That recognition — that the devices which stop an operation deserve the same logistics discipline as the laptop fleet — is exactly the Surya Critical model: customer paper, Surya custody, quoted in a working session. See Surya Critical.
Business Outcomes
Machine downtime bounded by a swap
When a floor endpoint fails, the recovery is a swap from the configured-spare pool — not a procurement cycle, not a courier, not an emergency image build.
A documented, current build without an internal engineering hire
The automated build is engineered and maintained by Surya, versioned, and current. The customer never staffed the role and never carries the key-person risk that used to live there.
Audit-ready custody evidence for the defense/automotive supply chain
Every recovered device is sanitized to NIST 800-88 with a certificate filed against the serial before disposition. Chain-of-custody evidence is the same shape auditors and prime-contractor questionnaires already expect.
One operator across office and floor
The office estate and the machine-adjacent floor endpoints run under the same custody, the same build discipline, and the same RMA loop. One number to call, one inventory of record, one operator responsible for the physical devices that keep parts moving.
Business Outcomes
Machine downtime bounded by a swap
When a floor endpoint fails, the recovery is a swap from the configured-spare pool — not a procurement cycle, not a courier, not an emergency image build.
A documented, current build without an internal engineering hire
The automated build is engineered and maintained by Surya, versioned, and current. The customer never staffed the role and never carries the key-person risk that used to live there.
Audit-ready custody evidence for the defense/automotive supply chain
Every recovered device is sanitized to NIST 800-88 with a certificate filed against the serial before disposition. Chain-of-custody evidence is the same shape auditors and prime-contractor questionnaires already expect.
One operator across office and floor
The office estate and the machine-adjacent floor endpoints run under the same custody, the same build discipline, and the same RMA loop. One number to call, one inventory of record, one operator responsible for the physical devices that keep parts moving.