Planning a 2027 Shutdown? What Should Be Reviewed Now?
A planned manufacturing shutdown can be one of the best opportunities to complete major technology upgrades that would be difficult, risky or impossible to carry out while production is running.
PLC migrations, SCADA upgrades, industrial network changes, historian modernisation, server replacements and wider control-system work often require equipment or production systems to be temporarily unavailable. A shutdown creates the window to make those changes, but it also creates a hard deadline.
For manufacturers planning shutdown activity in 2027, the success of the work will depend heavily on what happens before the shutdown begins. The physical installation or system cutover may take place over a matter of days, but the engineering, testing, documentation, validation and contingency planning required to make that window successful should begin months earlier.
At Réalta Technologies, we approach shutdown projects around one central principle: the shutdown itself should be the execution phase, not the point at which major technical questions are still being answered.
The more that can be engineered, configured, tested and agreed in advance, the lower the risk when the production clock starts ticking.
Why shutdown projects are different
Most engineering projects have some flexibility in their schedules. Shutdown projects often do not.
Once production stops, a fixed window begins. Automation engineers, IT and OT teams, validation specialists, operations, quality, vendors and contractors may all need to complete interdependent activities before manufacturing can restart.
A delay in one area can therefore affect the complete shutdown programme.
A server that is not configured correctly may delay a historian cutover. A network dependency that was missed during planning may prevent a new PLC from communicating. A validation document that is not ready may mean a technically functioning system still cannot be released for production.
This makes shutdown planning fundamentally different from normal project scheduling.
The objective is not simply to determine how long each technical task should take. The project team also needs to understand the dependencies between those tasks, the sequence in which they must happen and what needs to occur if something does not go according to plan.
Start with the manufacturing requirement
Before deciding what technology will be changed during the shutdown, manufacturers should first define the operational problem they are trying to solve.
Is the existing PLC reaching end of life? Is the SCADA platform no longer supported? Is a historian running on ageing server infrastructure? Is an industrial network becoming difficult to maintain? Are recurring reliability problems creating production risk?
It is also important to understand whether the shutdown represents a one-off upgrade or part of a wider modernisation programme.
Replacing a legacy PLC like-for-like may solve an immediate obsolescence problem, but the same shutdown could also provide an opportunity to improve network architecture, equipment connectivity, data availability or the operator experience.
At Réalta Technologies, our starting point is therefore the manufacturing requirement and the existing architecture. Once those are understood, the shutdown scope can be designed around what genuinely needs to change.
Review legacy PLCs and control hardware early
PLC migrations are among the most common activities planned around shutdown periods.
Legacy controllers may still operate reliably, but manufacturers need to consider more than whether the PLC is functioning today. Availability of spare parts, software support, engineering expertise, cybersecurity and compatibility with newer systems all affect long-term risk.
Before a shutdown, manufacturers should establish exactly which PLCs, remote I/O, communication modules, HMIs and field devices are involved in the migration.
The current control logic also needs to be understood.
That means confirming whether the latest PLC code is available, whether offline backups match the running system, whether undocumented changes have been made and whether the existing hardware communicates with other equipment that may not be obvious from the PLC programme itself.
A migration is considerably easier to control when the engineering team has a verified picture of the current state before development begins.
Do not treat SCADA as an isolated upgrade
A SCADA upgrade may appear to be a software project, but it can have dependencies across a much wider manufacturing environment.
Operator stations may communicate with PLCs, historians, databases, printers, reporting systems, Active Directory, alarm infrastructure and other applications. Changes to one part of the environment can therefore affect several others.
Before a 2027 shutdown, manufacturers should review the complete SCADA architecture rather than only the screens operators use.
The review should consider server infrastructure, operating systems, communication drivers, user accounts, security, alarms, historical data, reporting, integrations and any applications that rely on SCADA information.
Where SCADA and PLC upgrades are happening together, the relationship between the two projects should also be tested before site installation.
The shutdown should not be the first time the new PLC logic and supervisory application are expected to operate together.
Review industrial network dependencies
Modern manufacturing systems depend heavily on connectivity.
PLCs, SCADA, historians, servers, robots, drives, vision systems and other equipment may all communicate through industrial networks. Even relatively small network changes can therefore have wider implications.
Before carrying out a shutdown upgrade, manufacturers should confirm the existing network topology and identify every system that depends on the infrastructure being changed.
IP addresses, switch configurations, firewall rules, VLANs, domain dependencies, remote connections and communication paths should all be reviewed.
This is particularly important where new infrastructure is replacing older systems while existing equipment needs to continue operating.
Where possible, network changes should be staged, configured and tested in advance. The less configuration that needs to be created from scratch during the shutdown, the better.
Understand what needs to happen to the historian
Historians can easily become critical manufacturing systems without everyone recognising how many other applications depend on them.
Process historians may support engineering analysis, batch reporting, dashboards, investigations, production reporting and regulatory processes. Other applications may also read directly from historian servers or depend on existing interface configurations.
A historian upgrade therefore needs careful planning. A challenge often encountered with historians during a shutdown is that it has to remain online despite a site shutdown. Some systems (environment monitoring system, building monitoring systems) continue to generate data which should be historised, even during a shutdown.
Manufacturers should understand where the data comes from, how interfaces are configured, which applications consume the information, how much historical data needs to be migrated and what will happen to incoming data while the historian is unavailable.
The goal should not simply be to bring the new historian online. The project also needs to protect historical data and ensure that live manufacturing information continues to reach its destination after cutover.
A practical example: delivering a critical upgrade inside a two-week shutdown
The importance of preparation can be seen in a recent Réalta Technologies project for an Irish pharmaceutical manufacturing site.
The site’s PI System was critical to operations and supported batch release through RtReports. However, the environment was running on ageing software, hardware and operating systems and needed to be modernised.
The upgrade had to take place within a two-week plant shutdown.
The existing environment included more than 50 interfaces, including OPC DA, RDBMS and FTBatch connections. Even while production was stopped, incoming operational data remained important and needed to be preserved.
The project was therefore designed around three major requirements: no data loss, less than 24 hours of data unavailability and a fully validated system before the shutdown ended.
Réalta Technologies approached the project through extensive preparation, execution and validation planning.
Work began months before shutdown. Documentation was reviewed and migrated, new infrastructure was prepared, validation documents were developed, archive data was copied and the system configuration was frozen ahead of execution.
A detailed shutdown schedule was then built by working backwards from the required restart date, identifying critical-path activities and including contingency for unforeseen technical issues.
During cutover, interface buffering was used to protect incoming process data while the existing PI System was unavailable. The replacement infrastructure was then brought online, historical information restored and data flow from every interface verified before validation was completed.
The final result was nine hours of data unavailability, zero data loss and a fully validated PI System before the end of the shutdown window.
The important point is that those results were not achieved by moving faster during the shutdown. They were achieved by completing as much planning, engineering and preparation as possible before it began.
Use backward planning from the production restart
One of the most effective ways to plan a shutdown is to work backwards.
Start with the point at which the system must be available for production.
Before that can happen, commissioning may need to be complete. Before commissioning, validation or Site Acceptance Testing may be required. Before those activities, the system needs to be installed, configured and technically functional.
The same logic continues backwards through cutover preparation, Factory Acceptance Testing, engineering, design approval and procurement.
This approach makes dependencies much easier to identify.
It also helps manufacturers distinguish between activities that genuinely need to occur during the shutdown and activities that can be completed beforehand.
Every task moved out of the shutdown window reduces pressure on the execution team.
Complete as much engineering as possible before site installation
The shutdown should not become an engineering workshop.
PLC programmes should be substantially complete. SCADA applications should be configured. Server infrastructure should be prepared. Network configurations should be defined. Historian architecture should be designed. Documentation should be available for review.
There will always be some site-specific configuration and troubleshooting during execution, but major design decisions should already have been made.
For control system projects, this can include developing new logic against simulated I/O, configuring operator screens using test data and reproducing expected communication behaviour before the new system reaches the production environment.
The objective is to turn the shutdown primarily into a controlled implementation exercise.
Factory Acceptance Testing should remove uncertainty
Factory Acceptance Testing, or FAT, is one of the most important opportunities to reduce shutdown risk.
A FAT allows manufacturers and project teams to test the system before it reaches site.
For PLC and SCADA projects, this may include verifying control sequences, alarms, user access, HMI navigation, equipment states, data recording, communications and expected failure conditions.
The FAT should be based on the functionality that matters during production, not simply a demonstration that individual components operate.
Client operations, automation, engineering, quality and validation representatives should be involved where appropriate so issues can be identified while there is still time to resolve them without affecting the shutdown.
A strong FAT should mean that when equipment is installed on site, the project team is confirming expected behaviour rather than discovering fundamental problems for the first time.
Define the cutover strategy in detail
The point at which the existing environment is turned off and the new system becomes operational is one of the highest-risk parts of a shutdown project.
That transition needs a clearly defined cutover plan.
The plan should identify which systems are stopped, in what order, how existing configurations and data are backed up, when new infrastructure becomes active and how successful cutover will be confirmed.
Responsibilities also need to be explicit.
When multiple teams are working simultaneously, there should be no uncertainty about who has authority to proceed to the next stage, who is responsible for testing and who communicates the current system status to the wider shutdown team.
For complex projects, a central communication structure with frequent checkpoints can significantly improve coordination.
Build contingency into the schedule
Even the strongest shutdown plan cannot anticipate every problem.
Hardware may behave differently when connected to existing equipment. Network communications may expose an unexpected dependency. A backup may take longer to restore than expected. A piece of legacy equipment may respond differently from the test environment.
A shutdown programme that allocates every available hour to planned work leaves no room to solve these issues.
Contingency needs to be deliberately included within the schedule.
The project team should also distinguish between problems that prevent production restart and issues that can safely be resolved afterwards.
This helps ensure attention remains focused on the genuine critical path rather than allowing lower-priority issues to delay the complete shutdown.
Agree the rollback strategy before you need it
Not every migration goes according to plan.
Before execution starts, manufacturers should understand the point at which continuing with the new system becomes riskier than returning to the previous environment.
That requires a rollback strategy.
Backups need to be available and verified. Previous configurations should be recoverable. The team should understand how long rollback would take and the latest point in the schedule at which that decision can realistically be made.
The purpose of a rollback plan is not to assume failure.
It is to prevent decision-making under pressure if a serious issue occurs.
Validation cannot start at the end
In regulated manufacturing, a technically successful upgrade is not necessarily a production-ready system.
Validation requirements need to be integrated into the shutdown programme from the beginning.
Documentation, test protocols, traceability, approvals and system configurations should be prepared as far as possible before shutdown.
Validation teams should also understand the technical execution strategy so that test activities can follow the system’s implementation sequence.
This becomes particularly important where several workstreams are occurring in parallel.
At Réalta Technologies, Compliance, Validation & Quality is considered alongside the engineering work rather than as a final activity added after commissioning.
The objective is to reach the end of the shutdown with a system that is not only functioning technically, but is also properly documented, tested and ready for release.
Plan commissioning around real operating conditions
Commissioning confirms that a system works in the environment in which it will actually operate.
That may require physical equipment, live communications, field instruments and other systems that cannot be fully reproduced during FAT.
Manufacturers should therefore identify commissioning requirements early.
Which devices need to be exercised? Which communication paths need to be tested? Which failure conditions need to be verified? Does equipment need utilities, product or other site services before meaningful testing can begin?
Operations teams should also be involved.
The people who will use the system every day are often best positioned to identify whether equipment behaviour, operator interfaces and alarm responses make sense in practice.
Do not forget the systems around the main project
Shutdown planning can become too focused on the main piece of technology being replaced.
A PLC migration may depend on an older HMI. A SCADA upgrade may rely on a SQL database. A historian replacement may affect dashboards. A network change may influence OEM equipment that was never considered part of the original project scope.
This is why dependency mapping is so important.
Manufacturers should review not only the system being changed, but also the systems that consume its information or depend on its availability.
The objective is to avoid discovering a hidden dependency only after the existing environment has been turned off.
Prepare the people as well as the technology
Shutdown execution is also a resource-planning challenge.
Specialists may be required from automation, infrastructure, networking, validation, operations, quality, cybersecurity and external vendors.
Their availability needs to be confirmed before the shutdown begins.
Manufacturers should also consider coverage outside normal working hours. If execution is running continuously or across extended shifts, the project needs appropriate technical support throughout the period.
In some projects, teams operating across multiple time zones can extend technical coverage and reduce the time lost between shifts.
Clear communication is equally important.
Everyone involved should know the shutdown plan, current system status, critical risks and escalation process.
What should manufacturers be reviewing now?
If a major automation or digital manufacturing shutdown is planned for 2027, the review should already be underway.
Manufacturers should be establishing the current state of the systems involved, identifying obsolete or unsupported infrastructure, confirming dependencies, defining the target architecture and agreeing which work genuinely needs to happen during shutdown.
PLC and SCADA engineering should then progress alongside infrastructure preparation, network planning, validation documentation and FAT development.
The closer the project moves towards shutdown, the less unresolved design work should remain.
By the time production stops, the technical team should understand exactly what needs to happen, in what order and how success will be measured.
How Réalta Technologies supports shutdown projects
Réalta Technologies supports manufacturers across the full lifecycle of automation, control system and Data Infrastructure modernisation.
Our teams work across Advanced Automation, Data Infrastructure, Digital Transformation, Software Development, Compliance, Validation & Quality and Managed Services & Support, allowing us to consider both the system being upgraded and the wider architecture around it.
Depending on the project, that can include PLC and SCADA modernisation, historian upgrades, industrial network changes, IT/OT integration, server infrastructure, FAT execution, validation support, cutover planning, commissioning and post-implementation support.
The objective is not simply to complete the technical work within the shutdown.
It is to reduce uncertainty before the shutdown begins and ensure the upgraded environment can be operated, maintained and supported once production restarts.
The key takeaway
A successful shutdown is usually won before production ever stops.
The installation and cutover may receive most of the attention, but the real work begins much earlier with architecture, engineering, testing, documentation, validation and contingency planning.
Manufacturers planning PLC migrations, SCADA upgrades, network changes, historian work or other major system modernisation during a 2027 shutdown should use the months ahead to remove as much uncertainty as possible.
Understand the current environment. Confirm every dependency. Complete the engineering. Test the system. Prepare the validation strategy. Define the cutover and rollback plans. Build contingency into the programme.
Then, when the shutdown begins, the team can focus on controlled execution rather than unresolved design decisions.
If your organisation is planning automation, control system or Data Infrastructure work during a 2027 manufacturing shutdown, Réalta Technologies can help assess the existing environment, develop the upgrade strategy and support the project from initial engineering through FAT, validation, cutover and commissioning.
Ireland: +353 21 243 9113 | US: +1 302 509 4401
For significant PLC, SCADA, historian or infrastructure upgrades, planning should generally begin months before the shutdown itself. The required lead time depends on the complexity of the project, procurement requirements, validation scope and number of systems involved. The objective should be to complete as much engineering, configuration, documentation and testing as possible before production stops.
Typical activities include PLC migrations, SCADA upgrades, control hardware replacement, server and operating-system upgrades, historian modernisation, industrial network changes, equipment integration and wider automation infrastructure work.
PLC migrations can require existing control systems to be unavailable while hardware, software and communications are changed. A planned shutdown provides a controlled window in which this work can be completed without interrupting normal production.
A FAT should verify the functionality required from the new system before it reaches site. Depending on the project, that can include PLC sequences, HMI and SCADA functionality, alarms, user access, communications, data recording, equipment states and expected failure conditions.
Factory Acceptance Testing normally takes place before site implementation and verifies that the developed system performs as expected in a controlled test environment. Commissioning takes place within the actual manufacturing environment and confirms that the installed system operates correctly with real equipment, networks, field devices and surrounding systems.
A rollback plan provides a controlled route back to the previous system if a critical technical problem prevents the new environment from being safely brought into service. It should define the backups required, the restoration process and the point at which a rollback decision would need to be made.
Validation should be planned alongside the technical project from the beginning. Documentation, protocols, traceability and approval requirements should be prepared before shutdown so validation execution can follow the technical implementation without becoming a bottleneck at the end of the programme.
Manufacturers should understand the existing historian architecture, all incoming interfaces, applications that consume historian data, historical data migration requirements, buffering capability and how live process information will be protected during cutover.
The most effective approach is to move as much work as possible outside the shutdown window. Infrastructure can be prepared, software configured, applications developed, documentation completed and systems tested before execution begins. The shutdown can then focus primarily on cutover, physical installation, site testing, validation and commissioning.
Réalta Technologies supports projects across Advanced Automation, Data Infrastructure, system integration, Compliance, Validation & Quality and lifecycle support. This can include initial assessment, architecture, PLC and SCADA engineering, historian modernisation, network and infrastructure work, FAT, cutover planning, validation, commissioning and post-implementation support.

Turning Data into Action: Réalta Technologies Hosts Industry and Sport Event at Thomond Park
Réalta Technologies recently hosted Turning Data into Action at Thomond Park, a unique event bringing together industry and sport to explore how data, AI, and

PI System Upgrade Case Study for Pharmaceutical Manufacturing | Réalta Technologies
Réalta Technologies successfully upgraded a pharmaceutical client’s PI System, replacing outdated hardware and operating systems with a modern, compliant, and high-performance infrastructure without losing a

Power BI, Tableau, and SEEQ: Data Visualisation Tools for Modern Manufacturing
Explore how Power BI, Tableau, and SEEQ compare when it comes to visualising data in manufacturing environments. This blog highlights their strengths, weaknesses, and real-world
