Capturing Recurring Production Test Budgets

The key strategic shift is from project software to factory software. R&D test tools are paid for while a program is being designed and qualified, then spending can fall off. Production test sits in the line’s daily workflow, where every board, servo, or subsystem must be checked before shipment. That makes the budget repeat with unit volume, and it rewards software that can log pass fail results, tie them to serial numbers, and stay stable across many stations.1 2 3 4

• On the line, test software is less about helping an engineer debug one prototype and more about helping operators run the same procedure thousands of times. NI built this market around TestStand, which manages operator interfaces, parallel execution, reports, database logging, and deployment across fleets of testers.2 3 4
• Nominal is trying to carry the same test logic forward from prototype into production. Its Connect product is positioned as an edge layer for hardware test apps, and the page describes operators validating parts, logging against part numbers, and pulling work instructions from Manufacturo. That creates a clean chain from qualification data to per unit manufacturing records.1 5 6
• The budget owner changes with the workflow. Early test spend usually comes from engineering teams proving a design works. Once a product is released, manufacturing and quality teams own throughput, yield, traceability, and rework cost, so test software becomes part of the cost to build each unit, not a one time development expense.1 2 4

If Nominal keeps programs as they move from lab benches to production cells, it can turn a finite engineering tool sale into a recurring seat and station footprint tied to output. That would move it closer to NI’s historic stronghold, where the winning product becomes part of the factory’s standard operating stack.1 2 3 5