Forward Deployed on the Line

The FDE title is leaving the software CoE and showing up in job specs with hard hats implied: embed on the customer programme, configure the factory stack, build what the cell did not know to ask for, pull the edge work back into the platform. Hadrian, Orbital, Teradyne, a dozen quieter industrial shops, the motion is the same one Palantir named, aimed at metal. Enterprises will copy the title into OT the way they copied it into IT. They will staff a touring band, measure utilisation, and wonder why yield did not move.

I am going to keep writing the software version of this design. This is the version with gravity. If you only read one FDE piece, read both. The triad does not change. The exit condition does: a technician can keep the path when the FDE leaves the cell.

What FDE is on a line (and is not)

Not a sales engineer in PPE. Not a shutdown contractor. Not a data scientist who visits the historian. A Forward Deployed Engineer on the line is a builder who lives in the process long enough to change how the cell runs, then leaves a system the process owner can operate.

The last mile is the unofficial pinout, the MES field nobody trusts, the PLC comment from 2009, the fixture that is tribal knowledge. You cannot product-manage that from a central PLM backlog. You have to stand in it. That is why the useful industrial FDE jobs say the quiet part: you will build products at the edge the customer did not know to ask for, and the best of them become the platform.

If the artifact is a deck, it was not an FDE engagement. If the artifact is a laptop that dies when they fly home, it was theatre. Same rule as software. Heavier consequences.

The triad, with grease

• Process owner, names yield, cycle time, the qualification lot. Stays after the FDE leaves. Without this person you are automating a ghost cell.
• FDE, translates the cell into a running path: connectors, skills, evals, the boring integration to MES/PLM/the historian. Lives in the operator's tools.
• Platform, identity, model route (including the air-gapped one), logging, golden skill paths, the eval harness. Does not take tickets for "please AI my line." Makes the FDE faster and safer.

Ratio still holds: one platform pod per eight to twelve FDEs; one FDE per serious residency, not per "initiative." Four plants on one FDE is a visitor. Visitors do not change operating models. They take photos for the showcase.

Residency against a named physical outcome

Ninety to a hundred and eighty days. Written exit. Not "explore AI on line 3."

• "Invoice" becomes "first-pass yield on cell B no longer depends on one technician's Saturday notebook."
• "Validation cycle time from four days to two, with the twin-diff in CI, not in a slide."
• "Toolpath that fails DfM in the skill before it reaches the machine."

Rotation after the harness exists. Rotation as the default is how you train people to start and never finish, and how you leave a cell with a half-built snowflake the platform team inherits as a safety incident.

What they ship

• A harness in the real system of record, MES, PLM, historian, not a CSV on a laptop.
• Skills the technician's agent will invoke, filesystem folders, paths scoped to the cell repo, allowed-tools on the dangerous bits. The FDE should be deletable. The skill should not.
• Evals from real scrap and real regressions , the ladder, not a vibe.
• A stop a human will hit, physical, obvious, rehearsed.
• Observability the center can see, traces, torque, temperature, who approved what. If it cannot be audited it cannot scale in a plant.

Reuse is the metric. Later residencies start from the last skill, not from zero. If reuse is zero you funded artisanal snowflakes with better PPE.

Where they sit

Solid line to a deployment lead measured on production outcomes. Dotted into the plant for the residency. Hard contract with platform for golden paths. If they report to "innovation," you have decided they will not own the line. Compensation like product, not like billable hours. Career path: residency → lead who designs two or three triads → platform or the technical operator who stays in the business. Burning people as "more plants" is how you get SWAT forever.

Vendors will offer you their FDEs. Sometimes that is how you learn the motion. If the only people who can change the cell leave when the SOW ends, you rented a demo.

Failure modes

SWAT in a hard hat. Heroics, screenshot, gone. The technician cannot extend it.

Staff-aug on a shutdown. Extra hands. No exit condition. Operating model unchanged.

No process owner. IT sponsors. Operations watches. Six months later the skill is a ghost because nobody who runs the cell was in the room.

Platform as bottleneck. Every residency waits on identity, data, or a model route. You rebuilt the monolith in OT.

Twin theatre. The FDE is measured on how pretty the Omniverse scene is. Yield is someone else's KPI.

Stand up two cells, not a programme

Two residencies. Pain already felt. Process owners who will stay. Platform pod with one job: make those two boring to ship, auth, logs, route, eval harness, the air-gap story if you need it. 120 days. Exit in a paragraph. Then productize whatever got copied. That is the beginning of the skill library on the line. Add FDEs only as fast as you have owners and platform pull.

Forward deployed on the line is not a new profession. It is FDE with mass: triad, residency, skills that survive the FDE, evals that can fail metal, a stop a technician will use. Copy the title without that OS and you will get a touring band in hi-vis.

Related: The FDE Frontier, The Last Mile Was Always Atoms, and The Lab Next to the Line.