SMP Gateway User Manual • 7
2 Principles of Operation
Electrical power utilities face a number of challenges when attempting to automate their
substations. They have legacy devices that they want to continue using. They want to integrate
new devices. They may want to add one or more control centers. They may want to use a local
HMI in order to keep a close watch on all events that occur in the substation.
There are a number of problems to contend with: connectivity, protocol incompatibilities,
interoperability problems, security considerations, logistics for migration, downtime, and not the
least of which, total project cost.
The SMP Gateway has been specifically designed to address all these issues. It is the ideal product
to ensure a smooth, safe and cost-effective approach to substation modernization. Indeed, you can
use a step-by-step approach. You decide which steps to take, in which order, and when.
2.1 Logical Architecture
The SMP Gateway is designed to meet all the requirements for power substation automation. It
has an open architecture that allows you to easily add new protocols, devices, local area networks,
wide area networks, and control centers.
In this section, we will describe the logical architecture of the SMP Gateway and we will see how
it implements all the functions required of a substation gateway.
2.1.1 Masters and Slaves
A typical automation system consists of a SCADA system, located in a control center, which is
connected to devices located in the substation. The SCADA regularly polls the devices in order to
retrieve device readings and statuses. The operator uses the SCADA system to perform control
functions on selected devices.
Since it is the control system that initiates data acquisition and control, it is considered to be the
master system. Since the substation device responds to data acquisition and control requests, it is
considered the slave system.
To Next Page
Loading...
