On test software economics
The Cost of Leaving
Labs don't stay on test software they've outgrown because it's good. They stay because the sequencer was sold bolted to a cabinet, and leaving means buying the hardware twice.
The part nobody quotes
Ask an engineer why his lab still runs a test sequencer that hasn't seen a release in years, and the answer is almost never that he likes it. It's that the software came with the stand. It runs on the supplier's controller, in the supplier's chassis, talking to the supplier's instruments, and every one of those pieces was on the same purchase order. Replacing the sequencer means replacing the stack underneath it, so the question stops being is there something better and becomes can we justify rebuying a test stand. Those are very different conversations, and only one of them has a budget code.
So the stand freezes. Not because the software is adequate, but because the exit is priced like a capital project.
Why the software came with the steel
This wasn't a conspiracy; it was an era. Instrument companies sold hardware, and software was how you made the hardware usable. Bundling the sequencer with the cabinet made the cabinet easier to sell and the software cheaper to support, because the vendor knew exactly what machine it would run on and exactly which instruments would be attached. For a while everyone got something out of it.
What's changed is that none of the technical reasons still hold. A modern test executive doesn't need a particular controller. Instruments expose documented interfaces — SCPI, Modbus, CAN, VISA, plain serial — and any competent software can speak them from an ordinary computer. The bundle survives out of habit and commercial convenience, not necessity. But it still does its original job perfectly: it makes leaving expensive.
What the bundle actually costs
The markup on a specified computer is the least of it. The expensive part is what you give up:
- 01You can't evaluate anything. Trying a different sequencer means provisioning a different stand. So alternatives never get tested, only discussed.
- 02You can't add the instrument you need. If it isn't in the catalog, it isn't supported, and the test you were asked for becomes a project instead of an afternoon.
- 03Your sequences aren't portable. Work that encodes years of process knowledge is locked to a runtime that only exists on one vendor's box.
- 04When the supplier moves on, the whole stand freezes. Not just the software — the hardware it's welded to. This is the one that actually hurts, and it's happening across this industry right now as product lines get acquired and quietly retired.
The real price of bundled test software isn't the markup. It's that you can never try an alternative without filing a capital request.
The math when it's unbundled
Take the hardware out of the transaction and the switching decision changes shape. The software runs on a computer the plant already owns. It drives the cyclers, supplies, DAQ, buses and plant IO already installed, because it treats them as instruments with documented interfaces rather than as a bill of materials. Nothing on the bench gets replaced to accommodate it.
That means you can put a candidate sequencer on one stand, next to the sequencer you're already running, and find out whether it works on your actual hardware with your actual sequences — before committing anything. A pilot stops being a procurement event. The most useful thing about pricing software as software is not that the number is smaller. It's that the number is small enough to be a decision rather than a negotiation.
Time is the other line item
The purchase price of test software is rarely the biggest number in the project. Engineering hours are. Sequence development, and especially sequence debugging, is where the schedule goes — chasing a step that fails intermittently, a frame the device under test ignores, a measurement that arrives later than the sequence expects.
That's the part worth accelerating, which is why EBE Test Stand Executive ships an optional AI assistant for building and debugging sequences. Optional matters. It can be removed entirely, pointed at a model running on your own hardware, or pointed at a provider you already hold an enterprise agreement with. Plenty of labs — defense, aerospace, anything with controlled work on the floor — can't have test data or sequence logic leaving the building, and for them the right configuration is no AI at all. With it off, nothing leaves the test machine, and the sequencer is just a sequencer.
"And what happens if you go away?"
Fair question, and the honest answer is that you should ask it of every software vendor, including the large ones. Being large has not protected this industry's test software from being acquired and shelved.
What matters is what you're left holding. If the software was bundled, the answer is a frozen stand: you own hardware that only one abandoned program knows how to drive. If it wasn't, you own a normal computer and a rack of standard instruments that any competent software can talk to, and the loss is bounded at the software itself.
Beyond that, the things worth demanding are unglamorous and specific. Sequences stored in a format you can open and read without the vendor's runtime — in EBE Test Stand Executive's case, a spreadsheet. Interfaces that are documented protocols rather than proprietary black boxes. Source escrow, so the code survives the company. None of that is exotic, and any vendor who won't discuss it is telling you something.
The cleanest test of how locked in you are: ask your supplier what you would have to buy in order to stop using them.
If the answer includes hardware, that isn't a technical requirement. It's the price of the exit, and you already paid for it once.