'. PHP_EOL; } elseif ( strpos( $page_path, "deutsch") !== false) { echo ''. PHP_EOL; } elseif ( strpos( $page_path, "francais") !== false) { echo ''. PHP_EOL; } elseif ( strpos( $page_path, "italiano") !== false) { echo ''. PHP_EOL; } ?>

Inputs for Developing Control System Migration Strategies

by | Jun 30, 2016 | Services, Consulting & Training

Jim Cahill

Jim Cahill

Chief Blogger, Social Marketing Leader

Emerson's Scott Turner

Author: Scott Turner

When considering replacing your existing control system with a new control system it is important to plan the project up front. At Emerson on a typical Greenfield project, we would write a Project Execution Strategy. This is pretty standard because the implementation method of Greenfield projects is well understood and reasonably consistent between projects.

For a Brownfield project, this is generally not the case. The Project Execution Strategy (or Migration strategy when it is a migration) for a Brownfield project is often very specific to the associated plant or platform.

A key decision with Brownfield projects, which requires factoring into the plan, is how to cut over operations from the old control system to the new one. For example, you may wish to shut down production for a period of time long enough to perform a full cut over. That may not be a luxury you can afford so you may need to cut over one unit at a time whilst production is reduced—or a multitude of other options.

In-Plant-CollaborationAs you can appreciate from the above point alone, planning the replacement of your existing control system is a complex activity, which should only be completed through collaboration with experienced engineers and consultants who specialise in this type of a project. A robust Brownfield Project Execution strategy is highly dependent on the quality of information available to the author.

I would therefore like to make some suggestions on what information you, as a customer, should make available to your engineer or consultant when he or she is planning to write the strategy. These are my suggestions:

  1. Standards which you would like the project to consider, for example quality standards or internal technical standards
  2. An export of your existing control system configuration
  3. Copies of the original specifications provided with your control system (updated to the current status if possible)
  4. Photos of the internals of all the control system cabinets which are clearly identified based on location
  5. Details of any serial packages or interfaces to higher level systems
  6. Floor plans of the rooms which contain control equipment and floor plans of rooms which may be used in the future to locate equipment
  7. A description of the room ambient conditions where you plan to locate the new control system equipment. For example, is it humid or does it reach high temperatures?
  8. Your current thoughts on shutdowns. For example, how long you are prepared to shut down for, or if you can shut down most of the plant
  9. The timelines you would like for the project and time lengths of typical plant shutdowns
  10. Details of the spare parts you hold for your existing control system
  11. Photos of the operators control room and desk
  12. Details of any gateways you use or barriers which may need to be replaced or interfaced to
  13. I/O counts for the control system and if part of the scope, safety systems
  14. Network diagram of the existing control system
  15. Cabinet general arrangement drawings
  16. Power distribution details
  17. Identification of equipment you are concerned about the reliability of any other risks to the project which you can foresee
  18. Mapping lists for serial packages
  19. A process overview of the plant
  20. A description of the level of expertise within your business to adjust and maintain the existing control system
  21. A list of requirements for the new control system
  22. A description of any other projects or significant activities which may be happening at the same time as the control system replacement project
  23. Training requirements, if known, on the new control system
  24. Details of any unusual instruments which the system will need to interface to
  25. Details of any equipment or instruments which are referenced in the control system software and hardware but are no longer in use

I imagine that there are many further inputs, which a customer could provide that I have not listed here. If you have any suggested information please feel free to inform the readers by adding it as a comment. Remember the better the quality of input information the more concise and accurate the execution strategy will be and the easier it will be for you, the customer, to make an informed decision on how to proceed.

Please feel free to let me know your thoughts in the comments section below.

From Jim: You can connect and interact with other project experts in the Plan & Design and Implement & Build groups in the Emerson Exchange 365 community.

Popular Posts


Follow Us

We invite you to follow us on Facebook, LinkedIn, Twitter and YouTube to stay up to date on the latest news, events and innovations that will help you face and solve your toughest challenges.

Do you want to reuse or translate content?

Just post a link to the entry and send us a quick note so we can share your work. Thank you very much.

Our Global Community

Emerson Exchange 365

The opinions expressed here are the personal opinions of the authors. Content published here is not read or approved by Emerson before it is posted and does not necessarily represent the views and opinions of Emerson.