DeltaV 16.LTS: What the Release Changes

Emerson announced DeltaV version 16.LTS on January 20, 2026. The release updates the DeltaV Distributed Control System and its integrated Safety Instrumented System. Emerson presents it as a long-term support release built around software-defined control, new field connectivity, broader data access, and cybersecurity.

The announcement is several months old. Its value now is not novelty. Engineers can examine which changes affect architecture, migration planning, validation, and lifecycle cost. The release does not remove the need for site-specific compatibility checks.

What Emerson Announced

Emerson's January 20, 2026 announcement identifies version 16.LTS as a consolidated long-term support release. It covers both the DCS and integrated SIS environment.

The confirmed capabilities include access to the DeltaV IQ Controller, the DeltaV Flex System subscription model, PROFINET over Ethernet-APL support on the DeltaV PK Controller, Continuous Historian Elite, and DeltaV Live Enterprise View. Emerson also states that the release maintains ISA System Security Assurance Level 1 certification.

These are platform capabilities, not automatic project outcomes. Availability can depend on licensing, hardware, operating-system support, network design, and the exact upgrade path.

Software-Defined Control Changes the Resource Model

The DeltaV IQ Controller is described as fault-tolerant, modular, and server-based. That shifts part of the control-system discussion from fixed controller hardware toward managed compute resources.

For engineering teams, the first question is workload placement. They need to know which control functions run on each resource, how capacity is allocated, and what happens during a host or network failure. A fault-tolerant design still needs tested failure domains.

Teams should document processor loading, redundancy boundaries, time synchronization, storage dependencies, and maintenance access. They should also test restoration after a failed node. Virtualized or server-based control does not eliminate hardware. It changes where hardware dependencies appear.

DeltaV Flex Alters Commercial Planning

Emerson describes DeltaV Flex as a subscription model that provides DeltaV DCS capability and allows utilization to scale. This may reduce large upfront purchases for some projects. It also introduces recurring commercial and entitlement dependencies.

Procurement should model cost across the expected plant life. The review should include expansion, standby capacity, support, test systems, disaster recovery, and license behavior during network or account problems.

Exit planning matters as well. Plants should understand how configurations, historian data, and engineering records remain accessible if a subscription changes. Contract terms should align with the much longer service life of process equipment.

DeltaV version 16.LTS supports a software-defined control architecture with scalable, fault-tolerant IQ Controllers deployed in a server-based environment.

Ethernet-APL and PROFINET Reach Further Into the Field

Version 16.LTS adds native PROFINET over Ethernet-APL support on the DeltaV PK Controller. Ethernet-APL is designed to bring Ethernet communication into demanding process environments through a physical layer suited to long cable runs and hazardous-area applications.

The engineering benefit is richer device communication without a separate protocol conversion layer. However, a native controller interface does not complete the design. Segment power, trunk and spur limits, hazardous-area protection, device profiles, redundancy, shielding, and commissioning tools still require review.

Brownfield plants should inventory existing instruments and marshaling. Replacing a functioning field layer may not be justified only because a new protocol is available. The strongest projects connect the change to diagnostics, maintainability, or future expansion.

Historian Elite Expands the Data Boundary

Continuous Historian Elite builds on Emerson's AspenTech portfolio. Emerson positions it as a data foundation that can move contextualized process information toward enterprise analytics and AI applications.

That can reduce duplicated data engineering. It can also widen the attack surface and governance burden. Plants should classify the data, define ownership, and separate read-only consumers from control authority.

Sampling, compression, timestamp quality, context, and retention rules affect whether higher-level analysis is useful. An enterprise dashboard cannot correct poor instrument maintenance or inconsistent tag definitions.

Enterprise View Is Read-Only, but Still Needs Controls

DeltaV Live Enterprise View provides read-only access to displays outside the control room. Read-only presentation reduces direct control risk, yet it still exposes operational information.

Teams should define who may view each area, how identity is managed, and whether remote access crosses trust zones. Session logging, certificate lifecycle, patching, and account removal belong in the deployment plan.

Web application integration also deserves review. An embedded tool may look like part of the operator interface even when it comes from another security and support boundary. Visual integration should not imply shared authority.

Interpreting the Security Claim

Emerson states that DeltaV 16.LTS maintains ISA System Security Assurance Level 1 certification. The announcement links this assurance to secure-development and system-security requirements.

Certification is useful evidence about the product development and system design process. It does not certify a plant's final architecture. Site configuration, network segmentation, user management, backups, patch governance, and incident response remain local responsibilities.

Upgrade teams should compare the target security baseline with the installed system. They should document unsupported operating systems, third-party applications, remote-access paths, and compensating controls before migration.

A Practical Upgrade Assessment

Build the installed baseline

Record controllers, I/O families, workstations, servers, software revisions, interfaces, historians, SIS components, and custom applications. Include spare holdings and vendor dependencies.

Map compatibility

Check every hardware and software component against current Emerson documentation. Confirm operating systems, virtualization platforms, device integration files, and licensing. Do not infer compatibility from an earlier DeltaV release.

Define the cutover method

Choose staged migration, shutdown replacement, or another approved approach. Establish rollback points and configuration backups. Test communications to package units and third-party systems.

Validate operations and safety

Verify control modules, alarms, graphics, historian collection, reports, batch functions, and security roles. SIS work requires the site's functional-safety lifecycle and management-of-change process.

Plan support after startup

Assign ownership for patching, backups, subscription administration, certificates, server capacity, and recovery testing. A successful cutover is only the start of the support period.

What the Release Means for Plants

DeltaV 16.LTS broadens the platform's options for compute, field networking, enterprise data, and licensing. Those options can support phased modernization when each one solves a defined operational problem.

The main risk is treating the release as a single product replacement. It is an architecture decision involving control, IT infrastructure, cybersecurity, commercial terms, and long-term maintenance.

Teams planning spares or migration scope can review Emerson DeltaV equipment and the broader Emerson range. Final compatibility and licensing decisions should follow current Emerson documentation and a site-specific assessment.