Planning a controls upgrade

Describe why the upgrade is needed

Separate the business reason from the proposed technical solution. Obsolete hardware, recurring faults, poor operator information and additional process requirements call for different responses. Describe the present problem and the behaviour you want afterwards. This lets the project team investigate the right scope rather than assuming a wholesale replacement is necessary.

• Current operational issue and frequency
• Impact on production or maintainability
• Required changes to operation
• Expected maintenance or production window

Inventory the dependencies

The controller is only one part of the installation. I/O, drives, operator panels, communications modules and external databases may all interact with it. Identify these interfaces and any version constraints. Record which equipment has current configuration backups and which will require further investigation.

• Controller, I/O and communications hardware
• Operator terminals and SCADA servers
• Drives, motion systems and third-party machines
• Business, historian or database connections

Agree the scope of software change

Migrating existing logic and redesigning the control sequence are different tasks. List functions to retain, functions to improve and parts of the program that are not understood. Include settings, recipes and operator access behaviour in the review. Define the evidence needed to show the new installation does what the plant requires.

• Retained functions and new requirements
• Existing faults and undocumented behaviours
• Sequence and mode descriptions
• Acceptance tests and measurable outcomes

Plan installation and recovery

The cutover plan should state the preparation work, the sequence of site activities and the decision points. If a test fails, the team needs a known path to diagnose, correct or recover. The practical rollback depends on the equipment and extent of the physical change; it must be planned rather than assumed.

• Offline preparation and pre-build checks
• Installation order and responsible people
• Pre-change state and recovery materials
• Time reserved for verification and handover

Build a useful request for quotation

Provide the inventory, process description, upgrade objectives and timing constraints together. Ask for assumptions and exclusions to be stated in the proposal. Confirm documentation, commissioning and training expectations so that quotations can be compared on the same scope.