The Paths to OnPing Migration

1 Phases of OnPing Migration

Doing a Migration from one SCADA platform to another must be handled with care. At Plow we have done this enough times that we have a good method for going through it.

The install takes place in three different paths.

The Data Path, The Integration Path and The Training Path.

All of these pieces happen at the same time but are best looked at individually.

2 The Data Path

2.1 Creating Device Lists

In order for SCADA to work we need Data! That means gathering lists of devices, logins, IPs and addresses that we will pull.

This process can take anywhere from hours to weeks depending on how organized the input data is.

2.2 Migration Strategy

Each SCADA install requires different migration strategies. Individual Cell modems are by far the simplest. If we are installing our lumberjack on site we will need to coordinate with field personnel to get them distributed and installed. We can do this, the customer can or a 3rd party can.

If we are polling the device remotely the question is, on our sim or the customers. If it is the customers sim, we only need an IP and the device lists. If we are providing the sim, we need to again get those distributed out to the field.

In addition to the physical part of the migration, milestones need to be established about handoffs from existing SCADA.

  • Is there an “All at once” switch over date or a phased migration?
  • Is a period of shared access desirable/possible?
  • Are there any pieces of data being created by the SCADA itself?

Answering these questions is an investigation and requires time.

2.3 Critical Alarms and Infrastructure

Shutins, Alarming, Remote Kills and Remote starts are all key elements of a Control System. Understanding where and how these are set up is important in order to properly migrate a site.

We will work with your people to identify desired behavior on well kills, water line kills and other critical components.

2.4 Data Verification

In addition to making sure all the critical points are in correctly, we need to make sure that where possible values are cross checked with known values and expected ranges.

2.5 Historical Import

If available, we can add historical data so you have a single source of truth for your scada information.

3 The Integration Path

Getting the data into the system is only part of the project. We also need to make sure the data is properly integrated with other systems and displayed in ways that make sense to everyone involved.

3.1 Pumper/Operator Screens

We usually create a set of “Routes” that pumpers use to navigate through and see the data they need to see. We will work with individuals you select to make sure these screens are set up to everyone’s liking. Though every set of operators are different generally these screens focus on.

  • Key Values
  • Easy to read Alarming
  • Field Naming schemes

3.2 Engineers/Backoffice Screens

Creating visuals that work for operators and that work for engineers is a notoriously hard problem. By allowing different screens to be built for different users, we can side step the problem elegantly.

Engineering screens usually focus on dense information presentation.

Tables, graphs, rollups.

3.3 Accounting and Production

OnPing leans heavily on Scout for the presentation of data to Accounting and production systems but we do allow easy inspection of what values are being sent and when. We can set up verification tables and other things to help with this.

4 The Training Path

Effective training isn’t just about classes, it is about making sure that people with concerns about how the system will work are able to get answers to their questions.

We like to get people from different parts of the company involved early and have them as part of the processes.

Also, we of course will provide classes and training! Further we can do one on ones or breakout sessions for OnPing training.