Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial process control systems depend on more than controllers and instrumentation. The facilities that house them, the utilities that support them, and the cybersecurity and maintenance programs around them all shape operational readiness. The U.S. Department of Energy’s FY 2019 budget request for the National Nuclear Security Administration (NNSA) provides a historical example of how these connected needs were reflected in plans for a complex, mission-critical enterprise.

The request is not a general industrial automation program, and its projects serve specialized national-security missions. However, its descriptions of control-system upgrades, infrastructure work, and cybersecurity investment illustrate planning considerations that are relevant to engineers, integrators, and operations leaders working in demanding industrial environments.

Industrial process control systems need an infrastructure plan

NNSA’s FY 2019 request proposed $15.091 billion across four main areas: Federal Salaries and Expenses, Weapons Activities, Defense Nuclear Nonproliferation, and Naval Reactors. The budget overview emphasized sustaining and modernizing the nuclear stockpile and aging infrastructure, alongside nonproliferation, incident response, and support for Navy nuclear propulsion.

Within Weapons Activities, the request included funding for Infrastructure and Operations, described as supporting facility and capability needs. The overview also identified efforts to address deferred maintenance and recapitalize structures, capabilities, and systems. This framing matters for automation planning: a control system may be technologically current, but its long-term usefulness is linked to the condition of the building, electrical services, process equipment, and other supporting assets.

For plant teams, the practical lesson is to connect controls projects to the wider asset plan. When developing a modernization scope, consider whether the facility and its supporting infrastructure can accommodate the intended equipment and operating requirements. A controls upgrade may need to be coordinated with electrical, mechanical, safety, and facility work rather than managed as an isolated software or hardware replacement.

A process control system upgrade begins with the function it serves

One specific project in the request was an upgrade to the Function Test Stations at the Savannah River Site. The planned work would replace and modernize the Process Control System that operates the stations’ valves and pump trains. The budget document listed a total estimated project cost of $5.73 million, with $920,000 requested for FY 2019 and the remainder planned for later years.

The description is brief, but it points to a useful scoping principle: define a control-system project in terms of the equipment and operations it must support. In this case, the system’s stated role was to operate valves and pump trains at the test stations. That functional context helps distinguish a process-control modernization from a broader facility renovation or a cybersecurity initiative.

For engineering teams, a clear project definition can make interfaces and dependencies easier to identify. Relevant questions include which process equipment is controlled, what parts of the existing system are being replaced, and what supporting infrastructure or operational functions must be addressed. The source does not specify controller models, communications protocols, or performance targets, so these should not be inferred from the budget description.

Infrastructure projects can affect automation readiness

The same request listed projects that addressed the environment around operational and technical systems. At Sandia National Laboratories, proposed work included a replacement data center facility because the existing primary data center in California was described as outdated and deteriorating and unable to meet current sponsor requirements and future enterprise direction. At Pantex, a project proposed a redundant electrical feed for a data center, including transfer switches, switchboards, an uninterruptible power supply, feeder cable, substation replacement, and a computer-room air conditioner.

These examples show why automation and information technology planning often intersect with facility engineering. Control and data systems rely on supporting services, but the budget descriptions do not establish specific uptime outcomes or technical performance benefits. They do show that facility condition, power arrangements, and environmental provisions were included in the planned scope of selected projects.

Other proposed work addressed laboratory and production spaces, including control and fume-hood replacements in laboratory refurbishment projects. Such projects were presented as part of broader infrastructure and safety work, rather than as standalone automation initiatives. That distinction is useful when coordinating projects across operations, engineering, facilities, and safety teams.

Cybersecurity was treated as an enterprise concern

The NNSA overview described investment in Information Technology and Cybersecurity, including continued cybersecurity recapitalization efforts. It also discussed a Department-wide cybersecurity crosscut concerned with protecting the DOE enterprise from cyber threats and supporting coordinated activities such as incident response and identity, credentials, and access management.

For industrial organizations, the relevant planning insight is the emphasis on coordination across an enterprise, not a claim that the budget addressed any particular plant-floor architecture. The source does not specify industrial network segmentation, control-system security tools, or site-level implementation details. It does, however, frame cybersecurity as both an operational protection concern and a shared organizational responsibility.

That perspective can help teams avoid treating cybersecurity as a final-stage add-on to an automation project. When controls, data systems, facilities, and corporate services have shared dependencies, project planning should make those interfaces visible and assign responsibility for them.

Build modernization around people and lifecycle needs

The request also emphasized workforce capacity. NNSA sought funding for federal staff responsible for program and project management and oversight, while describing efforts to recruit, develop, and retain the skills needed for current and future missions. The document noted that major modernization work requires a skilled federal workforce, particularly for life-extension programs and major project management.

For industrial operators and system integrators, this is a reminder that modernization involves more than installing equipment. Project delivery and ongoing operation require people who understand the system, its interfaces, and the organization’s requirements. Workforce planning, training, project oversight, and maintenance responsibilities should therefore be considered alongside technical scope.

Practical takeaways for automation decision-makers

  • Define the control function. Describe which equipment and operations a project serves before selecting a modernization scope.
  • Include supporting assets. Review facility, power, and other infrastructure dependencies that may affect control-system work.
  • Coordinate cybersecurity. Identify shared responsibilities and interfaces rather than treating security as separate from project planning.
  • Plan for delivery and operation. Account for the workforce and oversight needed to implement and sustain changes.
  • Separate documented facts from assumptions. Budget descriptions can show project intent, but they do not provide technical specifications or prove achieved performance.

Conclusion

NNSA’s FY 2019 budget request offers a dated but useful case study in modernization planning for a complex operational enterprise. Its proposed Function Test Station control-system upgrade sat within a broader portfolio that also addressed facility infrastructure, data-center support, cybersecurity, and workforce needs. For industrial automation decision-makers, the central implication is straightforward: reliable modernization depends on aligning control-system scope with the assets, services, security responsibilities, and people that support it.

Access Official Technical PDF

About The Author