SB Architecture

Substation Automation Architectures Substation Automation
SA Architectures Substation Automation available in todays Architecture Structures Available Marketplace

in the Market Today Session 15
Session 19
Marquette University SA Seminar November 8-10, 1999
Substation Automation
Topics to cover Below is a list of topics covered in this presentation: Definition of the Master Controller Types of Master Controllers RTU-Based Master Controller PLC-Based Master Controller PC-Based Master Controller Data Concentrator Master Controller
Master Controller - Definition Master Controller: A device that collects data from IEDs within the substation and generates a database that can be accessed by SCADA, a HMI, Remote Access and a WAN. The database will contain both real-time and historical data. The database will be in an open format to allow users to generate applications using the data. Protocol Conversions can be performed as a function of the Master Controller or inserted between an IED and the Master Controller.
Marquette University SA Seminar November 8-10, 1999 3
Master Controller - Definition
The Master Control may have the capability of interfacing directly with hardware I/O to gather some of the data or may rely entirely on interfacing with IEDs to generate the database. The Master Controller may interface directly with SCADA or may pass data off to a separate device that interfaces with SCADA. The Master Controller may interface directly with a HMI or may pass data off to a separate device that interfaces with the HMI. The Master Controller may interface directly with a WAN or may pass data off to a device that interfaces with a WAN.
Master Controller - Definition The Master Control will have the ability to run applications generated by the user. These applications will access the database and allow for automation of the substation. The Master Controller will have a hardware component and a software/firmware component. The hardware may use open technologies such as a PC or may be vendor specific such as an RTU or PLC. The software/Firmware can be open such as with the PLC or vendor specific such as with the RTU or Standalone Device.
Master Controller - Types There are four basic architectures that are available to use as a Master Controller:
RTU-Based Master Controller PLC-Based Master Controller PC-Based Master Controller Data Concentrator Box Master Controller
Each of the Master Controller architectures will be discussed in the following sections. Advantages and disadvantages for each Master Controller architecture will be discussed.
Master Controller - RTU-Based RTU-Based Master Controller: A CPU or group of CPUs within the RTU polls the hardware I/O in the RTU and also the IEDs within the substation. Data from both the hardware points and the IEDs is combined into a global database. A Port from the RTU is connected to SCADA for access to the database. A Port from the RTU can be connected to a PC for the WAN and HMI interfaces. Parts of the RTU can be IEDs. Distributed RTUs with CT and PT AC analogs can act as IEDs to the Master RTU.
Master Controller - RTU-Based
Application programs can be written and loaded into the RTU CPU. Some RTUs support ladder logic while others allow for compiled C code. The HMI interface is via a PC running an open HMI package such as US Data ECS or Wonder Ware. Typically the driver on the PC that allows the HMI to retrieve data from the RTU can be purchased from either the HMI vendor or RTU vendor. WAN interface would typically use the database within the HMI instead of the RTU database. Remote Access of the system would be via the PC and HMI.
Master Controller - RTU-Based Typically the SCADA Interface would be a Port or dedicated CPU within the RTU. A UART board would then be added if the SCADA protocol were bit-oriented. Finally, a SCADA modem would complete the SCADA Interface. IEDs would be polled by either communication ports on the RTU or by adding dedicated processor cards to the RTU. A port or CPU card would be required for each protocol needed to interface with IEDs (or if the IEDS dont support multidropping, one port or card per IED).
Master Controller - RTU-Based
Power Supply
RTU as Master Controller

SCADA Interface
RTU CPU Terminal Blocks Interposing Relays Terminal Blocks
Remote Access
HMI WAN
Power Bus I/O Bus Digital Input Cards Digital Output Cards Analog Input Cards
Smart Switch
IED IED
Transducers
IED
IED
10
Master Controller - RTU-Based Below are list of advantages and disadvantages for this system: A If a RTU already exists within the substation that can support this architecture, this is a very inexpensive way to interface with IEDs and add a HMI. A Allows the user to feel knowledgeable about the Master Controller if the RTU is already being used by the utility. A Allows for the stocking of fewer spare parts if the RTU is already being used by the utility. A Allows for a known SCADA interface to remain the interface to SCADA.
Master Controller - RTU-Based A RTUs can process internal I/O faster than most other automation systems and can process IED data at about the same rate as other systems. A Some IED manufacturers are developing RTU protocol interfaces so that protocol converters within the RTU are not required. D Use of vendor hardware makes it difficult to upgrade for performance reasons at a later date. D Developing applications can be difficult. Ladder logic emulation is not always true and complete. Downloading C code can cause the RTU to perform incorrectly (even with RTU only functions).
Master Controller - RTU-Based D Can be an expensive approach if the RTU does not already exist and there are numerous IEDs to be polled. D The RTU will probably not retrieve much, if any, historical data from the IEDs such as fault records and demand values. D The RTU will probably not support the transparent mode. If required, the user will have to add a smart switch and run two cables to each IED. This will only work for IEDs that support communication with multiple ports. D There may be limitations on the number of IEDs the RTU can poll (a limited number of ports/ CPU cards per system).
Master Controller - PLC-Based PLC-Based Master Controller: A CPU or group of CPUs within the PLC polls the hardware I/O in the PLC and also the IEDs within the substation. Data from both the hardware points and the IEDs is combined into a global database. A Communications Card (or box) is added to provide the interface to SCADA. A Port from the PLC CPU can be connected to a PC for the WAN and HMI interfaces. PLCs can be distributed for the hardware I/O to reduce wiring costs.
Master Controller - PLC-Based
Application programs can be written and loaded into the PLC CPU. PLCs support ladder logic and also allow for compiled C code. HMI interface is via a PC running an open HMI package such as US Data ECS or Wonder Ware. Typically the driver on the PC that allows the HMI to retrieve data from the PLC can be purchased from either the HMI vendor or PLC vendor. WAN interface would typically use the database within the PLC database via a WAN card (UCA 2.0, Modbus over TCPIP). Remote Access of the system would be via the PC and HMI.
Master Controller - PLC-Based Typically the SCADA Interface would be a communications card or dedicated box. A UART board would then be added if the SCADA protocol were bitoriented. Finally, a SCADA modem would complete the SCADA Interface. IEDs that communicate with the same protocol as the PLC can reside directly on the PLC Bus and be polled by the PLC CPU. IEDs using other protocols would be polled by a communications card or box to perform the protocol conversion. Each different non-PLC protocol would require a separate port on the box or a separate communications card.
Master Controller - PLC-Based
Power Supply
PLC as Master Controller

SCADA Interface
PLC CPU Terminal Blocks Interposing Relays Terminal Blocks Protocol Converter
WAN
HMI Remote Access
Power Bus I/O Bus Digital Input Cards Digital Output Cards Analog Input Cards
Smart Switch
IED IED
Transducers
IED
IED
17
Master Controller - PLC-Based Below are list of advantages and disadvantages for this system: A If a PLC already exists within the substation that can support this architecture, this is a very inexpensive way to interface with IEDs and add a HMI. A Allows for a very efficient way of creating and running user applications. A Uses technology that is standard for the factory automation industry and has been for many years. A PLCs now have substation hardened modules and can be powered from the substation battery.
Master Controller - PLC-Based A PLCs can process internal I/O faster than most other automation systems and can process IED data at about the same rate as other systems. A HMI packages have developed interfaces to PLC databases many years ago and have a large installed based. PLCs also offer panels that can be used as HMIs. A PLC hardware can be purchased through local distributors. A PLC expertise can be found locally through system integrators. These integrators can aid the utility is creating automation applications.
Master Controller - PLC-Based A PLC vendors tend to be very stable. A utility should not have to worry about a PLC vendor going out of business. A PLC Vendors typically have 24 hour product support and local third party integrator support is available. A Protocol Converters are not needed for IEDs that use the same protocol as the PLC. Many IED manufacturers are implementing PLC protocols within the IED. A PLCs can directly support WAN and WEB applications with UCA 2.0 modules, Modbus over TCP/IP modules and modules with embedded web pages. A Some PLCs meet the same ambient (-40 to 70 C) and surge requirements as protective relays (ANSI C37.90.1)
Master Controller - PLC-Based D Use of vendor hardware makes it difficult to upgrade for performance reasons at a later date. (But still easier than a RTU). D Adding additional IEDs to a system may force the user to upgrade the CPU in the PLC. D Can be an expensive approach if the PLC does not already exist and there are numerous IEDs to be polled. D The PLC will probably not retrieve much, if any, historical data from the IEDs such as fault records (although it is possible).
21
Master Controller - PLC-Based D The PLC will probably not support the transparent mode. If required, the user will have to add a smart switch and run two cables to each IED. This will only work for IEDs that support communication with multiple ports. D There may be limitations on the number of IEDs the PLC can poll (a limited number of ports/ CPU cards per system).
22
Master Controller - PC-Based PC-Based Master Controller: A computer uses communication ports to poll IEDs for real-time and historical data. Data from the IEDs is combined into a global database. A Communications Card is added to provide the interface to SCADA. The WAN and HMI interfaces typically run on the same PC. Remote Access of the system would be via the PC and HMI.
Master Controller - PC-Based Application programs can be written and loaded into the PC. Standard programs such as Visual Basic, C and Microsoft Access can be used to manipulate the data. HMI interface is via a PC running an open HMI package such as US Data ECS or Wonder Ware. Typically the driver on the PC that allows the HMI to retrieve data from the PC Database has to be purchased from the Master Controller vendor.
24
Master Controller - PC-Based Typically the SCADA Interface would be a communications card or dedicated box. A UART board would then be added if the SCADA protocol were bitoriented. Finally, a SCADA modem would complete the SCADA Interface. IEDs using different protocols would each be polled by a communications card or box to perform the protocol conversion.
25
Master Controller - PC-Based
IED IED I/O Bus
PC as Master Controller
PLC/RTU CPU
SCADA Interface
PC
Remote Access HMI
Digital Input Cards Digital Output Cards Analog Input Cards
Terminal Blocks Interposing Relays Terminal Blocks
WAN
IED
IED
Transducers
IED
IED
26
Master Controller - PC-Based Below are list of advantages and disadvantages for this system: A Very open hardware platform. The PC can be purchased and serviced locally without interface with the SA Master Controller Vendor. A Allows the user to upgrade the hardware locally without interface with the SA Master Controller Vendor. A Allows third party integrators the chance to generate IED drivers for the customer. A Allows third party integrators the chance to develop automation applications for the customer.
Master Controller - PC-Based A Allows the user to determine the most cost effective way to support I/O. A Has the HMI, WAN and Remote Access connections as part of the Master Controller so there are fewer pieces. A Can interface directly to IEDs without extra hardware components required for protocol conversion. A Utilizes third party software. This allows for system upgrades without going to the Master Controller vendor. A System typically brings back historical data from IEDs to be stored on the hard drive. A Transparent mode typically supported.
Master Controller - PC-Based A Users familiar with the hardware and the interfaces of the system. A Configuration of the system is typically more userfriendly. A Allows data transfer to PLC for PLC applications. D PC may be more prone to be damaged by surges. D PC is prone to users playing with the system. D Users may be constantly wanting to upgrade systems (more RAM, larger hard drive, back-up systems). D Transparent mode IED vendor software may not run on the operating system that the Master Controller requires.
Master Controller - PC-Based D Typically an inverter is required to power PC from substation battery. D PC may not be as reliable as other systems (hard drive failures). D PC cannot handle extended temperature requirements. D PC may disappear from the substation.
30
Master Controller - Stand-Alone Stand-Alone Master Controller: A vendor specific hardware box (or boxes) that concentrates data from multiple IEDs into one database. The Standalone box typically has multiple communications ports (8-32). Software drivers can be loaded into the box so that different ports can poll IEDs using different protocols. The box may have the capability of time-synching all IEDs that it polls. The box will typically dedicate at least one port to SCADA.
Master Controller - Stand-Alone The box will typically have at least one port dedicated to a PC. The box will typically have an Ethernet port for a dedicated WAN. The box will allow remote access and configuration via a port. The box may have the option of providing a limited quantity of hardware I/O as an option. The box may allow for networking multiple boxes into one system. The box may be mounted beside the IED.
Master Controller - Stand-Alone The box may have direct interfaces to PLCs (either via a communications port or via the I/O bus of the PLC). The box may have the capability to perform some data manipulations (Boolean, ladder logic). The box may have an LCD for local display of data and configuration. The box typically will support transparent operation via the remote access interface.
33
Master Controller - Stand-Alone Stand-Alone Box Master Controller
IED IED PLC CPU
PC
HMI
Stand-Alone Box
WAN Remote Access
IED
SCADA Interface
IED
IED
34
IED
Master Controller - Stand-Alone Below are list of advantages and disadvantages for this system: A Allows for databases in the PC and PLC via transfer of the database from the box. A Typically fairly cost effective. A The Stand-Alone box vendor typically supports a lot of IED and SCADA protocols as this tends to be the vendors core business. A The Stand-Alone box vendor typically has a good relationship with all IED vendors because they usually dont view the vendor as competitive.
Master Controller - Stand-Alone A Usually designed to be substation hardened with the substation battery as input power. A Allows the user to determine the most cost effective way to support I/O A Allows data transfer to PLC for PLC applications. A Supports functions such as time synch and transparent mode operation. A Typically brings back historical data. D Typically these boxes are more difficult to configure. D The hardware is vendor specific.
Master Controller - Topology Topology:The physical manner in which IEDs transfer data to the Master Controller and the physical manner the Master Controller interfaces with the PC and/or WAN. Listed below are different topologies available: Point-to-Point Master-Slave Token Ring Ethernet
37
Master Controller Point-to-Point Point-to-Point:The Master Controller is cabled to one and only one IED on a given communications port. The Master Can poll the IED for data and the IED will respond. Typically point-to-point communication paths are RS-232 using either hard-wire shielded cable or fiber optics. Typical baud rates for point-to-point communications are 9600 baud but can operate up to 19,200 baud. A serial port on the both the Master Controller and IED would be the physical connection.
38
Master Controller Point-to-Point A This Topology is fairly fast in getting the data from the IED as their is a maximum of one IED per port. A This topology is very deterministic in that the port is spending all resources on gathering data from the one IED. D This is not a very cost effective topology as it requires one communication port and one cable per IED. A This is secure and easy to trouble-shoot as there is only one IED per port therefore a failure in one IED should not affect other IEDs in the system. D All data for the system is only available at the Master Controller.
Master Controller Master-Slave Master-Slave:The Master Controller is cabled to one or more IEDs on a given communications port. The Master Controller initiates all conversations. IEDs communicate to the Master only when directed. Typically Master-Slave communication paths are RS-485 using either hard-wire twisted-pair shielded cable or fiber optics. If fiber-optics is used, RS-232 can also function. Typical baud rates for Master-Slave communications are 9600 baud but can operate up to 115 Kbaud. A serial port on the both the Master Controller and IED would be the physical connection.
Master Controller Master-Slave D A Slave IED can not communicate with another Slave IED. The Slave is only allowed to communicate with the Master. D As more IEDs are added to the port, the update time or poll time for each IED becomes slower. The Master polls the first IED and then continues in the loop up to the last IED. The loop is then repeated. As the loop grows larger (additional IEDs added) it will take the Master Controller more time to complete the loop. A This topology is fairly deterministic. This is especially so if the protocol used on the topology limits the response length of each IED.
Master Controller Master-Slave D A failure in one IED on the loop can bring down the entire loop or could cause occasional communication errors between the Master Controller and other IEDs. This can make this topology difficult to debug. A This is a cost effective topology in that multiple IEDs share a communication port. It also requires inexpensive hardware both in the Master Controller and IED to support this topology. D All data for the system is only available at the Master Controller.
42
Master Controller Token Ring Token Ring:The Master Controller is cabled to one or more IEDs on a given communications port. The node that holds the token controls the conversation. The Master Controller can pass the token to other nodes (IEDs). When the node receives the token it is free to control the network and start a conversation with any node Typically the Master Controller will only allow certain nodes to hold the token. Typically the Master Controller will allow a node to keep the token for only a certain amount of time. If the node has not returned the token, then Master Controller will force the node to return the token
Master Controller Token Ring Typical baud rates for Token Ring communications are 9600 baud but can operate up to 1 Mbaud. The path from Master Controller to IEDs is physically cabled in a ring from Master Controller to IEDs and then back to Master Controller. This allows the Master Controller two paths to access the IEDs. RS-485 is the typically found with token ring networks A serial port on both the Master Controller and IED would be the physical connection.
44
Master Controller Token Ring D One Slave can only request or pass data to another slave when it holds the token. D Can be difficult to implement in software because multiple nodes can be the Master. A Can get critical data across the network because token nodes can control the conversation. A Simulates pier-to-pier in that at least token nodes can transmit and receive data from any other node. A Fairly secure topology in that if the Master fails, another node can assume the position of the Master. It is a ring so there is two paths between any two nodes.
Master Controller Ethernet Ethernet:The Master Controller is cabled to one or more IEDs via a coaxial cable, twisted-pair or fiber. There is no Master with a Ethernet Topology Each node on the network has an address. A node can request data from any other node. It simply waits until there is no traffic on the network and transmits. A node can transmit as long as required. All other nodes will be holding until the network is traffic-free. Two nodes can transmit at the same time. This is referred to as a collision.
46
Master Controller Ethernet Typical baud rates for Ethernet communications are10 Meg. Fast Ethernet can operate at 100 Meg. The path from Master Controller to IEDs is physically cabled in a star from Master Controller to IEDs.
47
Master Controller Ethernet D Not very deterministic. Allows for collisions with very little collision detection. D Adding nodes to the network can require hubs which are additional pieces of hardware. D Requires additional hardware for each node. A A very standard technology. Most computers are networked together using Ethernet A Very good at passing large amounts of data (fault records).. A Operates at very high baud rates.
PLC Architecture with MB+ LAN
DNP3.0 or L&G 8979 Gateway (Loadable)
Gateway to RTUs (DNP 3.0) Outside the substation fence

Ethernet MMS gateway with ICCP option
Local or remote access to all Substation IEDS
Modem
Modicon NW BM85D002 BRIDGE MUX
OO
OO
CURRENT INPUTS HI IA LO IB IC
SEL-2020 COMMUNICATIONS PROCESSOR

LED TEST ALARM 1 2 3 4 5 6
SEL
7 8 9
SCHWEITZER ENGINEERING ENGINEERING LABORITORIES LABORATORIES SCHWEITZER

PULLMAN WASHINGTON USA 10 11 12 13 14 15 16
..... ....
b b
Bitronics, Inc. Lehigh Valley, Pa Made in USA POWER STATUS
STATUS TARGETS
OO
OO
Doble
PowerPlex
Digital transducer VOLTAGE INPUTS
NORMAL FAIL PICKUP RECLOSER OUT
A B C N SYSTEM RESET
DPU
TIME 2000R INSTANTANEOUS FREQUENCY NEGATIVE SEQUENCE TARGET RESET
Network Partner V1.0
C E
POWER
POWER
I1
INST A B C Q FAULT TYPE N RS 79 LO FAULT TEST
133 I1
A 133 I1 A 133 A
I1
133 I1
A 133 I1 A 133 A
SCHWEITZER ENGINEERING SEL-221 DISTRIBUTION RELAY LABORATORIES PHASE OVERCURRENT RELAY WITH VOLTAGE CONTROL
NEGATIVE SEQUENCE OVERCURRENT RELAY GROUNDG OVERCURRENT RELAY MULTIPLE SHOT RECLOSING RELAY SELECTANLE SETTING GROUPS CIRCUIT BREAKER MONITOR FAULT LOCATOR
OO OO
Direct MB+ Devices

O O
OO
SEL
SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA A INST B C Q N RS LABORATORIES FAULT TYPE

79
LO FAULT TEST
SCHWEITZER ENGINEERING SEL-221 DISTRIBUTION RELAY LABORATORIES

PHASE OVERCURRENT RELAY WITH VOLTAGE CONTROL NEGATIVE SEQUENCE OVERCURRENT RELAY GROUNDG OVERCURRENT RELAY MULTIPLE SHOT RECLOSING RELAY SELECTANLE SETTING GROUPS CIRCUIT BREAKER MONITOR FAULT LOCATOR
OO
OO
SEL
SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA INST A B C Q N LABORATORIES

FAULT TYPE
OO
RS 79
LO FAULT TEST
SCHWEITZER ENGINEERING SEL-221 DISTRIBUTION RELAY PHASE OVERCURRENT RELAY WITH VOLTAGE CONTROL LABORATORIES NEGATIVE SEQUENCE OVERCURRENT RELAY
GROUNDG OVERCURRENT RELAY MULTIPLE SHOT RECLOSING RELAY SELECTANLE SETTING GROUPS CIRCUIT BREAKER MONITOR FAULT LOCATOR
SEL
SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA LABORATORIES
OO
OO
Relays MB
Legacy Relays
49
Presenter
Bob McFetridge Senior Program Manager Schneider Electric Phone: (919) 217-6448 E-Mail: bmcfetri@modicon.com
50

SB Architecture

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SB Architecture

Uploaded by

Copyright:

Available Formats

Substation Automation Architectures Substation Automation

SA Architectures Substation Automation available in todays Architecture Structures Available Marketplace

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

RTU as Master Controller

Marquette University SA Seminar November 8-10, 1999

PLC as Master Controller

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Remote Access HMI

Digital Input Cards Digital Output Cards Analog Input Cards

Terminal Blocks Interposing Relays Terminal Blocks

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

WAN Remote Access

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Marquette University SA Seminar November 8-10, 1999

Gateway to RTUs (DNP 3.0) Outside the substation fence

Local or remote access to all Substation IEDS

SEL-2020 COMMUNICATIONS PROCESSOR

SCHWEITZER ENGINEERING ENGINEERING LABORITORIES LABORATORIES SCHWEITZER

Modicon NW BM85D002 BRIDGE MUX

Modicon NW BM85D002 BRIDGE MUX

NORMAL FAIL PICKUP RECLOSER OUT

Network Partner V1.0

Direct MB+ Devices

SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA A INST B C Q N RS LABORATORIES FAULT TYPE

SCHWEITZER ENGINEERING SEL-221 DISTRIBUTION RELAY LABORATORIES

SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA INST A B C Q N LABORATORIES

SCHWEITZER ENGINEERING PULLMAN WASHINGTON USA LABORATORIES

Marquette University SA Seminar November 8-10, 1999

You might also like