SCADA systems

For a large Natural Gas distributor in The Netherlands, I architected a solutions for the connection of a SCADA system to PLC's in the field. SCADA systems are systems for process management that are used in factories, distribution systems and energy plants. Using computer technology, physical actions in processes are controlled and monitored.

In factories, energy plants or distributed systems, many physical controls are used. These controls can be:

  • valves in gas pipes;
  • electronic switches;
  • thermometers;
  • pressure sensors;
  • etc.

In the past, people needed to manually open or close valves, or had to check thermometers visually. Today, most of these physical controls are connected to electronics, so they can be controlled remotely.

SCADA stands for “Supervisory Control And Data Acquisition". SCADA systems have 3 purposes:

  1. Setting values to physical controls (like closing a valve).
  2. Performing measurements (like the gas temperature in a gas pipe).
  3. Managing alarms coming from controls (for instance when a temperature is getting below 0°C, an alarm is raised).

Usually, computer screens in the control room display an overview of the complete system, with it's status. The SCADA system is able to zoom-in to a location to show more details.

PLC's 

The physical controls "in the field" are usually connected to PLC's (Programmable Logic Controllers). PLC's are simple computer systems without keyboards or video screens, but with many I/O channels. The I/O channels can be outputs or inputs. Channels can be binary (on/off) or analogue (output or input of a voltage between for instance 0 and 5 volts). The I/O channels are connected to the physical controls. PLC's can be programmed to perform some actions when an event occurs. For instance, the PLC can shut-off a valve if some temperature raises to 100°.

Connections

Although PLC's can make some rudimentary decisions, more complex decisions should be made by humans. Therefore PLC's are connected to SCADA systems, which are usually located in a control room in a central building.

PLC's can be located all over a factory plant, or for instance in a natural gas distribution system, across an entire country. Connecting all PLC's to the central SCADA system is not a trivial task. The requirements for the connections are very high. In an electric energy grid, for example, the command for switching off an electric switch should not only be transferred in a few milliseconds, but it must be 100% certain at any time that commands are received by the PLC in the field.

Because SCADA systems are used for several decades now, and because setting-up connectivity is such a complex matter, old, but robust technology is still used frequently. Connections frequently are setup using serial lines, modems, X25 connections, and for more modern setups, TCP/IP WAN links. Special protocols, like IEC870 are used for communication between SCADA systems and PLC's.

Security

Traditionally SCADA systems were closed systems using proprietary technology. The SCADA systems are located in secured control rooms. Therefore, security issues were rare, and not much effort was done to secure the connections between the SCADA systems and the PLC's "in the field".

These days, companies start using more open communication protocols (like TCP/IP over a WAN) and COTS systems (running on for instance Microsoft Windows). This urges the companies to put more effort in securing their SCADA environments. The market for secured SCADA products is still immature at the moment. I expect that the coming years projects will be started to raise the level of security in SCADA systems.

Here is a nice article about the security issues.


This entry was posted on Tuesday 27 November 2007

Earlier articles

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

The history of UNIX and Linux

The history of Microsoft Windows

The history of Novell NetWare

The history of operating systems - MS-DOS

The history of Storage

The history of Networking

The first computers

History of servers

Tips for getting your ITAC certificate

Studying TOGAF

Is your data safe in the cloud?

Proof of concept

Who needs a consistent backup?

Measuring Enterprise Architecture Maturity

Human factors in security

Master Certified IT Architect

ITAC certification

Open group ITAC /Open CA Certification

Human factors in security

Google outage

SAS 70

TOGAF 9 - What's new?

DYA: Development without architecture

Spam is big business

Why IT projects fail

Power and cooling

Let system administrators participate in projects

The 7 Habits of Highly Effective People

Archimate

A meeting with John Zachman

ITAC - IT Architect certification

Personal Information is Personal Property

The Irresistible Forces Meet the Movable Objects

Hardeningscheck and hack testing for new servers

Knowledge management

Information Lifecycle Management - What is ILM

LEAP: The Redmond trip

LEAP: The last Dutch masterclasses

What do system administrators do?

Is software ever finished?

SCADA systems

LEAP - Halfway through the Dutch masterclasses

Securing data: The Castle versus the Tank

Non-functional requirements

LEAP - Microsoft Lead Enterprise Architect Program

Reasons for making backups

Log analysis - Use your logging information

Archivering data - more than backup

Patterns in IT architecture

Layers in IT security

High performance clusters and grids

Zachman architecture model

High Availability clusters

Monitoring by system administrators

What is VMS?

IT Architecture certifications

Storage Area Networks (SAN)

Documentation for system administrators

Rootkits

Presentations: PowerPoint sheets are not enough

99,999% availability

Linux certification: RHCE and LPI

IT Infrastructure model

Sjaak Laan


Recommended links

Ruth Malan
Gaudi site
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan