SCADA Systems: 10 Best Upgrade Practices

1. Establish the starting point

We often pull up to the system for the first time and discover that it is not 100%. For example, systems having accessibility problems, meters offline, broken diagram links, or false representations. It is therefore essential to document the existing system. Include even the most minor details in your documentation, such as diagrams, screens, or peripheral software added to enhance functionality. Furthermore, these details will help facilitate the following few practices. 

2. Define the finish line

We now understand what the existing system can and cannot do with our first practice. Now, we can begin to paint a picture of how the new system might look. 

Here comes the fun part…

Customers can use this process to envision the type of system they desire and determine how it will function. Everyone encounters times when technology doesn’t work the way they expect. For instance, you may need to introduce a new navigation button for data access or add functionalities that don’t currently exist. Defining your goals is the first step in determining your path to reach them.

3. Agree on the big picture

After knocking out the first two steps, we can agree that we are making a move from A to H. If you’ve ever moved furniture, you know how challenging it is to carry a couch around the room to find its proper place. The time and energy it takes can take a toll. In addition, most people understand that some projects have limited resources. In this regard, we want to ensure that we utilize all the resources available to us and strive to accomplish our mutually shared goals.

Nevertheless, we understand that concept and reality do not always align. In that case, we can return and take corrective action if necessary.

4. Tasks List

Since we know what we will do, it is time to consider how we will do it. First, we must obtain the necessary hardware, software, or personnel to execute our plan. Developing a task list will enable us to address these items early. We often have to work with the IT department to allow network access or port access. However, the IT team may not always be involved depending on the project. 

Consequently, the IT team plays the role of stakeholders whose interests weren’t considered in practices 1-3. Thus, establishing a task list will enable us to ensure that we address their concerns and issues.

5. Plan a schedule

We are approaching the point where the tires meet the pavement. Planning a schedule allows us to set realistic expectations regarding when customers can control their systems.

Imagine working on your car, for example…

How would you feel if your car’s repair shop gave you a schedule for several months in the future? I suspect you may decide to go with someone else who can complete the work sooner. Plans enable our customers to focus on themselves, even when other obligations require their attention. Further, creating and agreeing on a timeline ensures that each party is informed and accountable.

6. Review the progress

Next, when reviewing SCADA Systems, it’s imperative to keep everyone up to date on the progress. In the event of an impedance, staying up to date allows us to analyze how it affects the project’s completion and where to focus efforts. Therefore, monitoring a project’s progress is crucial to ensuring its completion on schedule and nothing is overlooked. 

7. The Devil is in the details

Usually, the small things are most noticeable, so we dive into the details. Unfortunately, nothing compares to a fully functioning system, and the one link to the main meter that everyone checks is not working. Consequently, the system as a whole opens up to concern and scrutiny. We suggest looking over ALL the small details to ensure the system is working correctly.

8. Celebrate the small stuff

As you can see, projects such as these involve many moving parts. However, you cannot underestimate the importance of opening ports unless the entire system stops communicating. So, it’s important to celebrate all milestones, no matter how big or small. All milestones contribute to achieving the big picture you envision in the long run.

9. Manage the exceptions

We all would like the ability to predict the future and be aware of what lies ahead. Planning everything is nice, but only focus on what you can control. Then, spend time adapting to the changes tasks require. Sometimes, this even means redefining or relocating a job. It truly is a process, and we must remember to treat it as such.

10. Train, Train, Train!

Lastly, our final step is to train your team. Now that the system upgrade is complete, you want to ensure that somebody on site knows how to operate it. Failure to do so will be disastrous. In short, training acts as a test drive of the new system’s operation and capabilities. Our goal is to ensure that each operator is self-sufficient and qualified to train others. Training is one of the most critical aspects of an upgrade. What good is a new system if no one knows how to use it?