Cold storage operators can modernize legacy refrigeration controls without replacing their PLCs by keeping those controllers in place for local, real-time logic and adding a secure supervisory software layer above them that standardizes data, alarms, and control across sites. This approach preserves proven equipment and operator familiarity while giving companies the visibility and consistency that older, site-by-site control environments struggle to deliver. The work succeeds when it starts with an accurate inventory of existing assets, follows recognized security practices, and relies on open communication standards.
Many cold storage portfolios grew through acquisition, which means one company might run ammonia systems controlled by several generations of PLCs, each programmed by a different integrator. Replacing all of that hardware at once is expensive, disruptive, and risky in buildings that must hold temperature every hour of the year. A layered approach lets operators improve what they have.
Why Full Replacement Is Rarely the Right First Move
PLCs that have run a refrigeration plant reliably for years carry a great deal of embedded knowledge. Their logic reflects equipment quirks, past incidents, and local operating preferences. Ripping them out risks losing that knowledge and introduces commissioning errors during a cutover.
There is also a people problem. The U.S. Bureau of Labor Statistics outlook for heating, air conditioning, and refrigeration mechanics and installers projects employment in the occupation to grow 11 percent from 2025 to 2035, with about 40,600 openings each year. Facilities already compete for skilled technicians, and a large controls replacement program pulls those same people away from daily operations.
Common pain points with legacy control environments
- Site-by-site logic: Each facility runs its own programming, naming conventions, and setpoints, which makes comparison difficult.
- Limited remote access: Older systems often require someone on site to diagnose a problem.
- Alarm overload: Inconsistent thresholds generate nuisance alarms that operators learn to ignore.
- Knowledge locked in people: When an experienced technician leaves, the reasons behind key settings often leave too.
- Security gaps: Legacy devices were rarely designed with modern network threats in mind.
A Layered Model for Modernization
The Purdue model offers a practical way to think about where new capability belongs. It places sensors and actuators at Level 0, PLCs and remote terminal units at Level 1, and HMIs and SCADA at Level 2, with operations and business systems above. Industrial automation control companies such as CrossnoKaye note that legacy operational technology does not need replacing to stay useful, because the model can be extended with secure supervisory and enterprise layers above the existing controllers.
In practice, that means the PLC keeps doing what it does well: reading sensors, running interlocks, and controlling compressors, valves, and fans in real time. The new layer collects data from those controllers, normalizes it into a common structure, and gives authorized people a consistent view and consistent controls across every site.
| Key point
The PLC remains the local authority for real-time control and safety interlocks. The modernization layer adds standardization, visibility, and governed access above it, so a network outage never leaves the plant without control. |
What stays and what changes
| Element | Legacy approach | Layered modernization |
| — | — | — |
| Real-time control logic | Runs in site PLCs | Continues to run in site PLCs |
| Data structure | Unique to each site and integrator | Normalized into a common model across sites |
| Alarm thresholds | Set locally, often inconsistent | Standardized, with site-specific exceptions documented |
| Remote access | Limited or ad hoc | Permissioned, logged, and role-based |
| Setpoint changes | Made at the HMI with little record | Tracked with an audit trail |
| Knowledge retention | Held by individual technicians | Captured in shared standards and system history |
Step 1: Build an Accurate Asset Inventory
Modernization fails when teams do not know exactly what they have. Before adding any new software layer, operators need a complete list of controllers, firmware versions, network connections, HMIs, and field devices at each facility.
Federal guidance treats this as a foundation. Guidance on OT asset inventory issued by CISA, NSA, and partner agencies urges operators to build an asset inventory to support risk identification, vulnerability management, and incident response. The agencies also stress that operational technology in critical infrastructure is a frequent target for malicious cyber actors.
A good inventory for a cold storage site typically records:
- Every PLC, its make, model, firmware, and program version.
- Communication protocols and network paths between controllers, HMIs, and any remote access points.
- Connected field devices such as ammonia detectors, pressure transducers, and variable frequency drives.
- Who has access to each system and how changes are currently approved.
Step 2: Choose a Supervisory Layer Built for Security
Any software that connects to plant controllers becomes part of the plant’s risk profile. Operators should evaluate it with the same seriousness they apply to pressure vessels and relief valves.
Joint guidance on secure OT product selection from CISA, NSA, and international partners warns that many OT products are not designed or developed securely. The guidance encourages owners and operators to look for elements such as configuration management, logging in the baseline product, open standards, secure-by-default settings, strong authentication, vulnerability handling, and upgrade tooling.
Questions to ask before connecting a new layer
- Does it require changes to existing PLC logic, or can it read and write through defined, limited points?
- How does it authenticate users, and can access be restricted by role and site?
- Does it log every control action and setpoint change?
- How are vulnerabilities reported and patched?
- What happens at the plant if the connection to the supervisory layer drops?
Operators should also align their program with the ISA/IEC 62443 series of standards for industrial automation and control system security, which many engineering teams already use as a reference for zones, conduits, and access control.
Step 3: Rely on Open Communication Standards
A mixed PLC fleet only works with a common software layer if the two can talk reliably. Proprietary, one-off integrations become their own form of technical debt. Open protocols reduce that risk and make it easier to add or replace components later.
OPC UA has become one of the most widely adopted options for this kind of interoperability. The OPC Foundation’s 2025 General Assembly highlights report membership of 1,019 companies and more than 427 domain-specific information models, which shows how broadly the industry has invested in shared data structures. For cold storage operators, that breadth makes it more likely that both older and newer controllers can feed a common model.
Step 4: Standardize Gradually, Site by Site
Once the supervisory layer is connected and secure, standardization can begin. Most operators start with naming conventions and alarm definitions, because consistent labels make every later step easier. They then move to shared setpoint standards and operating procedures, documenting any site-specific exceptions and the reasons behind them.
A phased rollout also builds trust with operators. Technicians who see that the new layer respects existing PLC logic, improves alarm quality, and gives them better information tend to become its strongest advocates.
Signs the modernization is working
- Operators resolve more issues remotely without a site visit.
- Nuisance alarms decline as thresholds become consistent.
- Engineers can compare performance across facilities using the same data definitions.
- New technicians onboard faster because standards are documented in the system.
The Bottom Line
Legacy PLCs remain valuable assets in cold storage, and modernization does not require removing them. By inventorying existing equipment, adding a secure supervisory layer that respects local control, building on open communication standards, and standardizing gradually, operators can gain portfolio-wide visibility and consistency while protecting the reliability their facilities depend on.




