Access Official Technical PDF

Share Summary:LinkedInEmail

For industrial operators, substation and process information often needs to be viewed together to support coordinated monitoring and control. An integrated SCADA approach can bring switchyard automation and process automation into a single operator interface rather than requiring separate screens for each environment. The practical value depends on how well the system fits existing equipment, communications protocols, operating needs and future changes.

These considerations are relevant to new installations as well as retrofit projects, particularly where a site has intelligent electronic devices (IEDs) from multiple manufacturers. A suitable SCADA platform should be assessed not just by its display, but also by its ability to connect to the required devices and support a configuration that reflects the facility’s operating requirements.

What integrated SCADA means for automation teams

Substation automation systems (SAS) gather and present information associated with electrical switchyards and their equipment. Process automation, meanwhile, relates to monitoring and control of industrial processes. An integrated SCADA system can present both domains within one screen or operating environment.

A unified view can help operators navigate information from different parts of a facility without treating electrical and process systems as entirely separate interfaces. It does not mean that the underlying equipment or functions become identical. Rather, the SCADA layer provides a common environment for displaying information from systems that may have distinct purposes, devices and communications requirements.

For engineers and system integrators, this distinction matters. Integration planning still needs to account for the specific equipment, signals and protocols involved. A single interface is useful only when the necessary information can be brought into it and presented in a way that supports the intended operation.

Plan for IEC 61850 and other protocols

IEC 61850 is identified as a relevant standard for the SCADA software described in the source material. The same material also specifies support for industry-standard protocols. In a real project, protocol support should be checked against the communication requirements of the installed IEDs and other connected hardware.

“Supports industry-standard protocols” is not, by itself, a complete integration plan. Before selecting or configuring a system, the engineering team should establish which devices need to communicate with SCADA and which protocols are required for each connection. This helps clarify the scope of integration and makes it possible to identify compatibility questions early.

For sites with equipment from several manufacturers, hardware flexibility can be particularly relevant. A platform described as integrable with IEDs from any make may help address a multi-vendor environment, but project teams should still confirm that the specific devices and communications needs in their installation are covered. Requirements should be validated in the context of the intended system rather than assumed from a broad compatibility statement.

Considerations for SCADA retrofit projects

Retrofits often involve working with equipment already installed at the site. A SCADA system intended for multi-vendor IEDs and retrofit applications may offer a route to bringing existing devices into a common monitoring environment. The source material identifies both new substation automation systems and retrofits involving multi-vendor IEDs as relevant applications.

During project definition, engineers can use questions such as these to make the scope more concrete:

  • Which systems must appear in the operator interface? Define the switchyard and process areas that need to be represented.
  • Which IEDs and other hardware are already in place? Record manufacturers and device types so that integration requirements can be checked.
  • Which communications protocols are needed? Match protocol requirements to the connected equipment and the intended data exchange.
  • What changes are anticipated? Consider whether the configuration may need to accommodate additional devices or changes to the automation environment.
  • How will the solution be configured and maintained? Confirm that the project team can configure the system to suit site requirements.

These steps do not replace detailed engineering or commissioning. They help ensure that decisions about the SCADA layer are based on the actual installation rather than on interface features alone.

Scalability and configuration in practice

A scalable, customizable SCADA platform is intended to accommodate differing project requirements and configurations. For plant managers and operations leaders, the practical question is whether the system can be configured for the information and views their teams need. For integrators, it is whether the configuration can reflect the site’s devices, protocols and automation arrangement.

Ease of configuration is also a project consideration. A system described as easy to configure may reduce complexity during setup, but teams should evaluate this against the skills and processes needed to maintain the resulting configuration. Clear requirements and disciplined documentation remain important when a system is changed or extended.

Certification should be reviewed with similar care. The SCADA software in the source material is described as KEMA certified. Decision-makers should verify the certification details and its relevance to the specific solution and project requirements rather than treating the label alone as a complete technical assessment.

Conclusion: assess the whole integration requirement

Integrated SCADA can provide a common view of switchyard and process automation, while support for IEC 61850, other industry-standard protocols and multi-vendor IEDs can be important in new installations and retrofit work. These capabilities need to be considered alongside the actual devices, communications requirements and operator needs at each site.

For automation engineers, system integrators and plant leaders, the practical next step is to define the systems and equipment that must be connected, verify protocol and device compatibility, and assess configuration and scalability requirements. That project-level discipline helps ensure that a unified interface is supported by an integration plan suited to the facility.

Access Official Technical PDF

About The Author