Twelve months ago, Nigel only advised. It read a test engineer's National Instruments code and suggested fixes, never touching the keyboard itself. This week, Emerson said Nigel now writes that code directly, and claims the change cuts the time and effort to build a test system by up to 50 percent across the workflows it benchmarked internally (Emerson, 2026).

A Year From Advisor to Author

Emerson launched Nigel as an advisor in July 2025, built to read existing LabVIEW and TestStand code and answer plain language questions about it (Emerson, 2025). It stopped short of writing anything. The July 28, 2026 release changes that boundary. Nigel now generates LabVIEW code from prompts and builds TestStand sequences on its own, a distinction Emerson's test and measurement president Ritu Favre summarized as a move from AI advisor to AI author (Emerson, 2026).

That is not a small rewrite of a chatbot. LabVIEW and TestStand sit underneath validation work for automotive electronics, aerospace and defense hardware, and semiconductor fabrication (Emerson, 2026). Code an engineer once typed line by line now originates from a prompt, and the engineer's job shifts to reviewing rather than authoring.

Five Applications, One Test Lifecycle

Nigel now reaches past LabVIEW and TestStand into InstrumentStudio, FlexLogger, and VeriStand, though the release draws a real line there. LabVIEW and TestStand get full code and sequence authorship. The other three get what Emerson calls AI-driven workflows and context-aware intelligence in interactive measurement, sensor datalogging, and hardware-in-the-loop testing (Emerson, 2026), assistance rather than authorship. Emerson still frames the whole set as one continuous AI layer running from initial code through system validation and deployment, rather than a single point tool bolted onto LabVIEW.

Consolidating five applications under one AI authorship layer raises the switching cost of leaving the NI LabVIEW+ Suite. An engineering organization that adopts Nigel across its test lifecycle is not adopting a feature. It is adopting a dependency that spans design, measurement, and deployment inside a single vendor's stack.

The Regulatory Pitch

Emerson tied the authorship expansion to alignment with the European Union's Cyber Resilience Act, along with built-in security and governance controls (Emerson, 2026). That pairing targets the exact objection a validation engineer in a regulated industry would raise first: if an AI system writes the sequence that certifies a part, who stands behind that sequence when an auditor asks.

Certification bodies do not accept a prompt history as a design record.

Emerson's answer, based on the release, is traceability and human sign-off built into the workflow rather than bolted on after the fact. Whether that satisfies aerospace and defense quality systems built around human-authored code is a question the release does not answer, and one that will surface the first time an AI-authored test sequence sits inside a certification audit.

An engineering organization that adopts Nigel across its test lifecycle is not adopting a feature. It is adopting a dependency that spans design, measurement, and deployment inside a single vendor's stack.

Unknowns and Uncertainties

Emerson's 50 percent figure comes from internal benchmarking across workflows the company selected as representative, and the release does not specify the sample size, the industries measured, or whether an outside party reviewed the methodology (Emerson, 2026). Nor does it describe what the audit trail for an AI-authored TestStand sequence looks like in practice, beyond the general reference to security and governance. Whether other test and measurement vendors follow Emerson into code-authoring AI, and whether certification bodies in aerospace and defense adjust their standards to address AI-authored validation code, remain open.

Glossary: The NI Stack

Emerson's LabVIEW+ Suite carries five applications. Nigel AI operates across all five, with full code and sequence authorship in LabVIEW and TestStand and context-aware AI workflows in the other three. A quick reference for readers outside test and measurement:

LabVIEW: the graphical programming environment engineers use to build test and measurement applications, wiring code visually rather than writing text-based syntax.

TestStand: a sequencing engine that orchestrates test steps, calling code written in LabVIEW or other languages and managing execution, reporting, and results.

InstrumentStudio: an interactive front panel for configuring and running instruments during test development, without writing code first.

FlexLogger: data logging software for sensor-based measurements, built to get data acquisition running fast without custom programming.

VeriStand: real-time testing software for hardware-in-the-loop work, where a physical system such as an engine controller is tested against a simulated environment.

All five run on National Instruments hardware, PXI chassis and data acquisition devices among them. That pairing is why adopting the NI stack has always meant a hardware and software commitment together, and why Nigel's authorship layer now sits on top of a dependency most buyers took on for other reasons first.