10 steps to a smoother automation system upgrade
When migrating or upgrading your automation system, don’t forget to examine this group of areas outside of the HMI, controllers, and I/O. These suggestions will help you identify and deal with lurking problems early in the process.
If you’re in the process of upgrading your automation system, or contemplating such a task in the near future, your primary focus is probably on the HMI, the controllers, and the I/O—and rightly so as these are critical components to address in a system migration. But there’s much more to an automation system than these hardware components, and these secondary areas can be the source of many problems if due diligence isn’t performed in the planning stages.
One of the best ways to examine all areas of the automation system prior to undertaking a major automation upgrade project is to perform a front end loading (FEL) evaluation. A FEL evaluation is a type of analysis that evaluates all aspects of an automation system upgrade or other project. Among other deliverables, it should include a list of project tasks with durations, and an overall project schedule.
Most end users will work with an outside service provider to produce the FEL evaluation because they often don’t have the available manpower. The right service provider will have produced many FEL evaluations for automation system upgrade projects, and can thus help the end user to produce a thorough study in an optimal manner.
A FEL evaluation will help develop a budget and justify the project. It will also reveal potential problems, and help prepare end users for the daunting task of migrating their obsolete DCS or PLC-based automation system. In short, it should provide a map to success with the destination in mind.
In most cases, the amount of time and effort invested in a FEL evaluation is directly proportional to overall project success. Unfortunately, many end users view this stage as an optional task for an automation system upgrade, and perhaps even a distraction. Scrimping on the FEL evaluation not only increases risks, it also can result in missed opportunities for improvements and enhanced long-term sustainability. By contrast, a thorough FEL evaluation will identify potential problems and help ensure that the project attains its goals.
10 areas outside the lines
When the main architecture is developed for an automation system upgrade, the primary components are always the HMIs, controllers, and I/O. Most of the time and effort in the planning and budgeting stages is spent on these key components, often to the detriment of the balance of the system, those areas that fall outside the lines.
A properly executed FEL evaluation will shed light on 10 important secondary areas, which are listed in Table 1 and discussed below.
Field devices and infrastructure
Field equipment and wiring primarily consists of four parts:
- Wiring, conduit, and cable tray
- Panels, cabinets, marshalling panels, and junction boxes
- Instrumentation, including inline devices, analyzers, transmitters, etc., and
- Mechanical equipment, including motors, valves, drives, and other field devices.
All of these items must be examined to ascertain acceptable physical condition and proper documentation. In addition, instrumentation and mechanical equipment must be examined and/or tested to ensure proper interface with the new automation system’s I/O and digital communication interfaces.
The overall condition of field wiring, including terminations, labeling, and grounding, should be assessed during the FEL process. If any areas are not up to standards and in good working condition, plans and budgets should be developed to rectify any deficiencies and defects.
When the automation system is up and running, the status of various field devices such as motors, valves, and position switches is determined by hardwiring these components to automation system inputs. So, the interfaces between these devices and the inputs must be tested to ensure proper voltage levels and electrical isolation.
Similarly, valves, motors, and status lights are driven by automation system outputs. Again, compatibility must be ensured so that each output can drive or actuate its associated device.
Interfaces to automation system analog I/O can be a particular problem area. A 4-20 mA output on an older automation system may have been able to drive more instruments in a loop connection than the new automation system’s 4-20 mA output. This issue would be minor if uncovered in a FEL evaluation, but major if found during commissioning. Moreover, analog inputs must be examined and sometimes tested for compatibility. For example, an older DCS might have accommodated thermocouple types that are no longer in widespread use, and as such may not be supported by the new automation system.
Most plants have smart instruments and analyzers with their own network connections to the automation system (see Figure 1), another area that must be examined in detail during the FEL evaluation.
Network infrastructure and connectivity
Modern automation systems connect to a variety of other systems and components in various layers including:
- Control layer—ancillary control systems on process skids, emission monitoring systems, building automation systems, etc.
- Enterprise layer—historian, MES, ERP, corporate networks, etc.
- Field device layer—HART, Fieldbus, Profibus, DeviceNet, etc., and
- Other—lab systems, remote access, analyzers, advanced process control devices, etc.
The physical infrastructure, including the fiber/copper backbone, network devices, wireless hardware, and other items, must be examined to ascertain acceptable condition and proper documentation. But this is only the first step, as compatibility issues can abound, even when the new automation system supports the very same protocols as the old automation system.
The main interfaces at each layer should be tested to ensure that communications can take place in an acceptable manner with performance equal to or exceeding the existing system. The new automation system must be able to support all of the existing communication protocols, either directly or through protocol converters. In some cases, it may be more cost effective to upgrade or even replace systems and components that can’t easily be interfaced to the new automation system.
For example, if there is a small cluster of instruments with a different fieldbus protocol than the majority of instruments, it may be better to replace these oddballs, as opposed to adding a protocol converter to connect them to the new automation system.
The older automation system will often have controllers and smart devices such as instruments and drives supplied by the same vendor. If the new automation system is purchased from a different vendor, in almost all cases the digital interface to the smart devices will be more limited in functionality, even if the protocol is nominally the same. Provisions must be made to operate the system with this reduced functionality, or to replace the smart devices.
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.