SMART GUIDE
FROM A TO Z

The dictionary for communication between SCADA systems, controllers, other electrical devices and people. All entries from A to Z.

DICTIONARY
Dic­tio­nary and Ency­clo­pe­dia in one: click on the expla­na­tion to open the entire entry in a new tab. The dark­er tech­nolo­gies have longer entries, while basic expla­na­tions hide behind the lighter summaries.
DICTIONARY
A B C D E F G H I J K L M NO P Q R S T U V W X Y Z

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

In Chap­ters

A

ARP — Address Resolution Protocol

The Address Res­o­lu­tion Pro­to­col (ARP) is a com­mu­ni­ca­tion pro­to­col used for dis­cov­er­ing the link lay­er address (e.g. MAC address) that is asso­ci­at­ed with a giv­en inter­net lay­er address, com­mon­ly IPv4.

The map­ping func­tion pro­vid­ed by ARP is crit­i­cal to the Inter­net pro­to­col suite and has been imple­ment­ed with many com­bi­na­tions of net­work and data link lay­er tech­nolo­gies, such as IPv4, Chaos­net and DEC­net using IEEE 802 stan­dards, FDDI, X.25 and Frame Relay amongst others.

D

DLMS

DLMS/COSEM (or IEC 62056) is the main glob­al stan­dard for smart ener­gy meter­ing, con­trol and man­age­ment. It includes spec­i­fi­ca­tions for media-spe­cif­ic com­mu­ni­ca­tion pro­files, an object-ori­ent­ed data mod­el and an appli­ca­tion lay­er protocol.

DNP3.0

Dis­trib­uted Net­work Pro­to­col 3 (DNP3) is a set of com­mu­ni­ca­tions pro­to­cols used between com­po­nents for automa­tion sys­tems in elec­tric, indus­tri­al and water sectors.

It is a key pro­to­col in SCADA sys­tems, where it is pri­mar­i­ly used for com­mu­ni­ca­tions between a mas­ter sta­tion and RTUs or IEDs.

E

Encryption

Encryp­tion, from ancient Greek Kryp­tós (“hid­den”), is the art of hid­ing writ­ten mes­sages by apply­ing a giv­en math­e­mat­i­cal algo­rithm. Encryp­tion seeks many objec­tives, such as;

  • Con­fi­den­tial­i­ty: the orig­i­nal mes­sage (“plain text”) should not be under­stood by any­body else than the legit­i­mate destination
  • Authen­ti­ca­tion; the receiv­er wants to make sure that the mes­sage comes from an autho­rised source. This is impor­tant, for exam­ple in a GOOSE mes­sage trip­ping a break­er (who sent it? Is the trans­mit­ter real­ly autho­rised to trip a break­er or not?)
  • Integri­ty: the receiv­er wants to make sure that the orig­i­nal mes­sage has not been mod­i­fied by a man-in-the-mid­dle attack

All  encryp­tion algo­rithms can be clas­si­fied under the fol­low­ing two categories;

  • Sym­met­ri­cal encryption
  • Asym­met­ri­cal encryption

Encryp­tion for Smart Grids is defined in IEC62351 series (Sub­sta­tions), IEC 62056 (Smart Meters) and NERC-CIP, among oth­ers. Usu­al­ly a com­bi­na­tion of asym­met­ri­cal and sym­met­ri­cal algo­rithms is used to ben­e­fit from the advan­tages of both categories.

Ethernet

Eth­er­net is a fam­i­ly of wired com­put­er net­work­ing tech­nolo­gies com­mon­ly used in local area net­works (LAN) and also wide area net­works (WAN).

Over time, Eth­er­net has large­ly replaced com­pet­ing wired LAN tech­nolo­gies by pro­vid­ing high­er bit rates, a greater num­ber of nodes, and longer link dis­tances and decent back­ward compatibility.

F

100BASE-TX — Fast Ethernet 

100BASE-TX is the most com­mon Fast Eth­er­net phys­i­cal lay­er, trans­mit­ting data through two twist­ed wire-pairs (one for each direc­tion), which pro­vide full duplex oper­a­tion with 100 Mbit/s of through­put in each direction.

The cabling dis­tance is lim­it­ed to 100 metres (328 ft) for each net­work segment.

FTP — File Transfer Protocol

The File Trans­fer Pro­to­col (FTP) stan­dard defines an appli­ca­tion lay­er net­work pro­to­col to trans­fer files from a serv­er to a client on a com­put­er network.

FTP is based on a client-serv­er mod­el archi­tec­ture using sep­a­rate con­trol and data con­nec­tions between client and server.

FX100 Ethernet

Fast Eth­er­net is the name of the exten­sion to 100 Mbit/s Eth­er­net net­work to 10 Mbit/s. This is the IEEE 802.3u work­ing group that is at the ori­gin. Access tech­nique is the same as in the Eth­er­net Ver­sion 10 Mbit/s, but at a speed mul­ti­plied by 10. trans­port­ed frames are iden­ti­cal. This increase in speed may con­flict with the wiring sys­tem and the pos­si­bil­i­ty or not there such impor­tant tran­sit flows.

H

HTTP — Hypertext Transfer Protocol

The Hyper­text Trans­fer Pro­to­col (HTTP) is a stan­dard­ized appli­ca­tion lay­er pro­to­col for dis­trib­uted and col­lab­o­ra­tive, hyper­me­dia infor­ma­tion systems.

Along­side HTML, HTTP facil­i­tat­ed the devel­op­ment of orig­i­nal World Wide Web, the first inter­ac­tive, text-based web browser.

HTTPS — Hypertext Transfer Protocol Secure

HTTPS (Secure HTTP) is the cyber­se­cured ver­sion of HTTP, Hyper Text Trans­fer Pro­to­col. Its pur­pose is to encrypt the con­tents of a web page so that its trans­mis­sion between client and serv­er ben­e­fits from con­fi­den­tial­i­ty, authen­ti­ca­tion and integri­ty. In fact HTTPS is HTTP (Appli­ca­tion Lay­er) com­bined with TLS (Trans­port Lay­er Secu­ri­ty), an encryp­tion lay­er that makes uses of encryp­tion algorithms.

HSR — High-availability Seamless Redundancy

HSR (High-avail­abil­i­ty Seam­less Redun­dan­cy) is a redun­dan­cy pro­to­col for Eth­er­net net­works requir­ing short reac­tion times and high avail­abil­i­ty, as for exam­ple pro­tec­tion sys­tems at elec­tri­cal substations.

Unlike com­mon redun­dan­cy pro­to­cols like RSTP, HSR reacts to any net­work com­po­nent fail­ures seam­less­ly (with­out recov­ery time) and is invis­i­ble to the application.

I

ICCP/ TASE.2

ICCP (Inter-Con­trol Cen­ter Com­mu­ni­ca­tions Pro­to­col) is a stan­dard pro­to­col for com­mu­ni­ca­tions between con­trol cen­ters, which is part of the IEC 60870–6 stan­dard under the name of TASE.2 Tele­con­trol Appli­ca­tion Ser­vice Ele­ment 2.

It is being used around the world to exchange data over wide area net­works (WANs) between grid oper­a­tors, util­i­ties, vir­tu­al pow­er plants, region­al con­trol cen­ters and oth­er generators.

IEC 60870–5‑104 // IEC104

IEC 60870–5 is a pro­to­col stan­dard for tele­con­trol, telepro­tec­tion, and oth­er telecom­mu­ni­ca­tion func­tions for elec­tric pow­er systems.

IEC 60870–5‑104 (short IEC-104) is a com­pan­ion stan­dard defin­ing how to extend the IEC 60870–5‑101 pro­to­col to gain net­work access using stan­dard trans­port profiles.

IEC 61850 — BRCB/URCB — Buffered/Unbuffered MMS Reports

IEC 61850 dis­tin­guish­es between buffered and unbuffered report­ing. In unbuffered report­ing events will not be logged and report­ed if the asso­ci­at­ed client for the unbuffered report con­trol block is not con­nect­ed. In the case of buffered report­ing the events will be logged for a spe­cif­ic amount of time and sent lat­er when the client is con­nect­ed again

IEC 61850 — GOOSE

The GOOSE (Gener­ic Object Ori­ent­ed Sub­sta­tion Event) pro­to­col is a com­mu­ni­ca­tion mod­el defined by the IEC 61850 stan­dard, which uses fast and reli­able mech­a­nisms to group any for­mat of data (sta­tus, val­ue) into a data set and trans­mit it through elec­tri­cal net­works with­in 4 milliseconds.

It is most com­mon­ly used for data exchanges between IEDs (IED – Intel­li­gent Elec­tron­ic Device) in elec­tri­cal sub­sta­tions over Ethernet.

IEC 61850 — ICD File 

IED Capa­bil­i­ty Descrip­tion (ICD) files are a spe­cif­ic type of Sub­sta­tion Con­fig­u­ra­tion Lan­guage (SCL) file, con­tain­ing a gener­ic descrip­tion of the whole capa­bil­i­ty range of a giv­en device, includ­ing the func­tions and objects it can support.

The ICD file is usu­al­ly sup­plied by the developer/manufacturer.

IEC 61850 — LN Logical Node 

Log­i­cal nodes or LN (abstract data objects) are the main ele­ments of the vir­tu­al object-ori­ent­ed IEC 61850 mod­el, which con­sists of stan­dard­ized data and data attributes.

The abstract data objects can be mapped to any oth­er pro­to­col, as for exam­ple with the MMS or SMV pro­to­col on an Eth­er­net data frame.

IEC 61850 — MMS Protocol

IEC 61850 MMS (Man­u­fac­tur­ing Mes­sage Spec­i­fi­ca­tion) is a client/server based pro­to­col for com­mu­ni­ca­tions between IEDs (IED – Intel­li­gent Elec­tron­ic Device) and high­er lev­el enti­ties (such as RTUs and SCADAs) over Eth­er­net that is part of the IEC 61850 stan­dard for com­mu­ni­ca­tion tech­nol­o­gy in substations.

It is mapped onto TCP/IP and allows to access the serv­er through its IP address in order to write/read data and exchange files.

IEC 61850 — SCL — Substation Configuration Language

The IEC 61850 stan­dard for sub­sta­tion automa­tion spec­i­fies a stadard­ized sub­sta­tion con­fig­u­ra­tion lan­guage (SCL) to trans­fer device descrip­tions and com­mu­ni­ca­tion para­me­ters amongst dif­fer­ent vendors/manufacturers.

SCL files define sev­er­al capa­bil­i­ty sub­sets for the IED to instan­ti­ate its capabilities.

IEC 62439–3

IEC 62439–3:2016 defines the PRP and HSR stan­dards, which pro­vide seam­less failover against fail­ure of any sin­gle com­po­nent in Eth­er­net networks.

PRP and HSR are appli­ca­tion pro­to­col inde­pen­dent, can be used by most Indus­tri­al Eth­er­net pro­to­cols in the IEC 61784 suite and have been inte­grat­ed in the frame­work of IEC 61850 for sub­sta­tion automation.

IEC 62443

IEC 62443 is an Inter­na­tion­al Stan­dard deal­ing with cyber­se­cu­ri­ty in Indus­tri­al Automa­tion and Con­trol Sys­tems (IACS). While IEC 62351 empha­sizes on encrypt­ing com­mu­ni­ca­tions, IEC 62443 empha­sizes on the device itself and intro­duces require­ments such as a gen­er­alised def­i­n­i­tion of user (so that RBAC applies not only to humans but soft­ware process­es as well); or the require­ment that pass­words be stored in hard­ware, which makes the use of TPM ICs nec­es­sary. From its very def­i­n­i­tion IEC 62443 applies nat­u­ral­ly to RTUs and asso­ci­at­ed equipment.

IEC 62439–3

IEC 62439–3:2016 defines the PRP and HSR stan­dards, which pro­vide seam­less failover against fail­ure of any sin­gle com­po­nent in Eth­er­net networks.

PRP and HSR are appli­ca­tion pro­to­col inde­pen­dent, can be used by most Indus­tri­al Eth­er­net pro­to­cols in the IEC 61784 suite and have been inte­grat­ed in the frame­work of IEC 61850 for sub­sta­tion automation.

IEC 62351

IEC 62351 is a series of Stan­dards deal­ing with Cyber­se­cu­ri­ty in elec­tric­i­ty sys­tems. Devel­oped by IEC TC57 WG15, they aim at improv­ing the dif­fer­ent aspects of Cyber­se­cu­ri­ty in the dif­fer­ent RTUs and IEDs deployed in sub­sta­tions, with parts ded­i­cat­ed to encryp­tion and key exchange in tele­con­trol pro­to­cols (e.g. IEC 60870–5‑104 or DNP3.0), 61850, Smart Meter­ing (DLMS-COSEM), RBAC (Role Based Access Con­trol) and Con­for­mance Test­ing among others. 

IED — Intelligent Electronic Device

In the pow­er sec­tor, intel­li­gent elec­tron­ic devices (IED) are micro­proces­sor based pow­er sys­tem equip­ment, such as cir­cuit break­ers, trans­form­ers and capac­i­tor banks, pro­vid­ing con­trol and automa­tion functions.

IEDs receive and process data from sen­sors and oth­er equip­ment to issue con­trol com­mands or adjust tap poi­si­tions in order to pre­vent fail­ures and main­tain the desired volt­age level.

IP Routing

IP rout­ing encom­pass­es dif­fer­ent method­olo­gies to route Inter­net Pro­to­col (IP) pack­ets with­in and across IP net­works by deter­min­ing a suit­able path to trans­fer net­work pack­ets between source and des­ti­na­tion nodes in and across IP networks.

IP Rout­ing pro­to­cols enable routers to build up a for­ward­ing table that cor­re­lates final des­ti­na­tions with next hop addresses.

Interlocking (network protection scheme)

The inter­lock con­sists of one or more switch­es that pre­vent both main pow­er and gen­er­a­tor pow­er from pow­er­ing the dwelling simul­ta­ne­ous­ly. With­out this safe­guard, both pow­er sources run­ning at once could cause an over­load con­di­tion, or gen­er­a­tor pow­er back-feed onto the main could cause dan­ger­ous volt­age to reach a line­man repair­ing the main feed far out­side the building.

M

MAC — Medium Access Control

The Medi­um Access Con­trol (MAC) sub­lay­er pro­vides flow con­trol and mul­ti­plex­ing for the trans­mis­sion medi­um to con­trol the hard­ware that inter­acts with the wired, optic and also wire­less trans­mis­sion media in the IEEE 802 LAN/MAN data link layer.

The MAC is accom­pa­nied by the LLC sub­lay­er, which pro­vides flow con­trol and mul­ti­plex­ing for the log­i­cal link (i.e. Ether­Type, 802.1Q VLAN tag etc.)

 

Modbus RTU & TCP

Mod­bus is a com­mu­ni­ca­tions pro­to­col based on master/slave (RTU) or client/server (TCP/IP) archi­tec­tures that can oper­ate on the 1st, 2nd, 7th lev­el of the OSI Model.

Orig­i­nal­ly designed in 1979 by Mod­i­con for its range of PLCs, it is now a de fac­to stan­dard com­mu­ni­ca­tions pro­to­col in the indus­try, becom­ming the most wide­ly avail­able pro­to­col for the con­nec­tion of indus­tri­al elec­tron­ic devices.

Multi-drop Bus

In order to auto­mate, mon­i­tor and con­trol a sub­sta­tion and its intel­li­gent devices in real time from a cen­tral mon­i­tor­ing sta­tion, the sub­sta­tion must be con­nect­ed to a Super­vi­so­ry Con­trol and Data Acqui­si­tion (SCADA) system.

The SCADA pro­vides grid oper­a­tors with an HMI (Human Machine Inter­face) to visu­al­ize col­lect­ed data and facil­i­tate the sub­sta­tion main­te­nance and operation.

N

Network Redundancy

Net­work redun­dan­cy is a method to ensure net­work avail­abil­i­ty, pro­vid­ing failover when a device or net­work path fails or becomes unavailable.

Redun­dan­cy is usu­al­ly achieved by installing addi­tion­al or alter­na­tive net­work devices, com­mu­ni­ca­tion media or equip­ment with­in the net­work infrastructure.

P

Power Plant Controller — PPC

PPC (Pow­er Plant Con­troller) is a con­trol loop that reg­u­lates the amount of ener­gy inject­ed to the grid by a gen­er­a­tion plant, to make sure that com­plies with both the set­points and the grid codes dic­tat­ed by the TSO. The PPC receives the set­point from the TSO del­e­gate office and receives feed­back from a meter installed at the Point of Injection.

Profibus

PROFIBUS (Process Field Bus) is an open stan­dard for field­bus com­mu­ni­ca­tions in indus­tri­al automa­tion sys­tems that was first pro­mot­ed in Ger­many in 1989.

The now most com­mon­ly found “Profibus DP” pro­vides sim­ple com­mu­ni­ca­tions between Profibus mas­ters and their remote I/O slaves.

PRP — Parallel Redundancy Protocol

PRP (Par­al­lel Redun­dan­cy Pro­to­col) is a redun­dan­cy pro­to­col for Eth­er­net based net­works requir­ing high avail­abil­i­ty and a short switchover time, as for exam­ple pro­tec­tion sys­tems at elec­tri­cal substations.

Unlike com­mon redun­dan­cy pro­to­cols like RSTP, PRP reacts to any net­work com­po­nent fail­ures seam­less­ly (with­out recov­ery time) and is invis­i­ble to the application.

R

RS-232 — TIA/EIA-232

The RS-232 (Rec­om­mend­ed Stan­dard-232) or also known EIA-232 (Elec­tron­ic Indus­tries Alliance-232) is a stan­dard for the ser­i­al trans­mis­sion of data in indus­tri­al applications.

The stan­dard defines the elec­tri­cal char­ac­ter­is­tics and tim­ing of sig­nals, the mean­ing of sig­nals, and the phys­i­cal size and pinout of connectors.

RS-422 — TIA/EIA-422

The RS-422 (Rec­om­mend­ed Stan­dard-422) or also known EIA-422 (Elec­tron­ic Indus­tries Alliance-422) stan­dard defines the char­ac­ter­is­tics of an elec­tri­cal inter­face for ser­i­al com­mu­ni­ca­tions in indus­tri­al con­trol systems.

It was designed to replace the old­er RS-232C stan­dard in order to pro­vide high­er speed (up to 10 Mb/s), bet­ter immu­ni­ty from noise, and longer cable lengths (up to 1,500 meters).

RS-485 — TIA/EIA-485

The RS-485 (Rec­om­mend­ed Stan­dard-485) or also known EIA-485 (Elec­tron­ic Indus­tries Alliance-485) stan­dard defines the char­ac­ter­is­tics of an elec­tri­cal inter­face for ser­i­al com­mu­ni­ca­tions in indus­tri­al con­trol systems.

In con­trast to the old­er RS-232, it allows to bal­ance elec­tri­cal sig­nals and con­nect mul­ti­ple device to the net­work, which can stretch over longer dis­tances and harsh­er environments.

RTU — Remote Terminal Unit

RTU most com­mon­ly stands for Remote Ter­mi­nal Unit, but is some­times also used as an abbre­vi­a­tion for Remote Teleme­try Unit or Remote Tele­con­trol Unit.

RTUs are devices that rely on micro­proces­sors and com­mu­ni­ca­tion inter­faces to auto­mat­i­cal­ly mon­i­tor and con­trol field devices and estab­lish a bridge to the plant con­trol or SCADA (super­vi­so­ry con­trol and data acqui­si­tion) systems.

S

SAIDI/SAIFI

SAI­Di and SAIFI are reli­a­bil­i­ty index­es defined in IEEE 1366 and intend­ed to mea­sure the Qual­i­ty of Ser­vice of elec­tric­i­ty sup­ply. SAIDI (Sys­tem Aver­age Inter­rup­tion Fre­quen­cy Index) mea­sures how often elec­tric­i­ty sup­ply is inter­rupt­ed and how many cus­tomers the inter­rup­tions affect. SAIDI (Sys­tem Aver­age Inter­rup­tion Dura­tion Index) mea­sures the time dura­tion of the inter­rup­tions. Very often SAIDI and SAIFI have to meet max­i­mum val­ues dic­tat­ed by the reg­u­la­tor, and in some coun­tries it is com­pul­so­ry by Law that SAIDI/SAIFI cal­cu­la­tion be sup­port­ed by a SCADA sys­tem (e.g. Spain).

SCADA — Supervisory Control and Data Acquisition

Super­vi­so­ry con­trol and data acqui­si­tion (SCADA) sys­tems col­lect, mon­i­tor and process real-time data to:

  • Auto­mate and con­trol indus­tri­al process­es remote­ly or locally
  • Pro­vide a human-machine inter­face (HMI) to direct­ly inter­act with devices such as relays, sen­sors, gen­er­a­tors, pumps, valves and others
  • Record events and auto­mate reporting

Secure Boot

HTTPS (Secure HTTP) is the cyber­se­cured ver­sion of HTTP, Hyper Text Trans­fer Pro­to­col. Its pur­pose is to encrypt the con­tents of a web page so that its trans­mis­sion between client and serv­er ben­e­fits from con­fi­den­tial­i­ty, authen­ti­ca­tion and integri­ty. In fact HTTPS is HTTP (Appli­ca­tion Lay­er) com­bined with TLS (Trans­port Lay­er Secu­ri­ty), an encryp­tion lay­er that makes uses of encryp­tion algorithms.

SCADA — Supervisory Control and Data Acquisition

Super­vi­so­ry con­trol and data acqui­si­tion (SCADA) sys­tems col­lect, mon­i­tor and process real-time data to:

  • Auto­mate and con­trol indus­tri­al process­es remote­ly or locally
  • Pro­vide a human-machine inter­face (HMI) to direct­ly inter­act with devices such as relays, sen­sors, gen­er­a­tors, pumps, valves and others
  • Record events and auto­mate reporting

SER — SEQUENCE OF EVENTS (SOE) RECORDING

Sequence of events record­ing (SER) is per­formed by micro­proces­sor based sys­tems, which mon­i­tor col­lect­ed data inputs and record the time and sequences of the changes.

Sequence of events recorders rely on exter­nal time sources such as GPS or radio clocks to record the exact time of state of each change.

T

TASE.2/ ICCP

ICCP (Inter-Con­trol Cen­ter Com­mu­ni­ca­tions Pro­to­col) is a stan­dard pro­to­col for com­mu­ni­ca­tions between con­trol cen­ters, which is part of the IEC 60870–6 stan­dard under the name of TASE.2 Tele­con­trol Appli­ca­tion Ser­vice Ele­ment 2.

It is being used around the world to exchange data over wide area net­works (WANs) between grid oper­a­tors, util­i­ties, vir­tu­al pow­er plants, region­al con­trol cen­ters and oth­er generators.

TCP — Transmission Control Protocol

The Trans­mis­sion Con­trol Pro­to­col (TCP) is one of the main pro­to­cols of the Inter­net pro­to­col suite pro­vid­ing reli­able, ordered, and error-checked byte stream deliv­er­ies between host­ing appli­ca­tions com­mu­ni­cat­ing through an IP network.

Locat­ed in the Trans­port Lay­er of the TCP/IP suite, major inter­net appli­ca­tions such as the World Wide Web, email, SSL/TLS and file trans­fers rely on or run on top of TCP.

U

UDP

UDP (acronym for User Data­gram Pro­to­col) is a lay­er 4 trans­port pro­to­col com­mon­ly used in IP net­works. Unlike TCP (Trans­mis­sion Con­trol Pro­to­col), UDP is a con­nec­tion­less pro­to­col, there is no con­nec­tion set­up or con­nec­tion release. This makes it very ade­quate for the trans­port of short, urgent or spon­ta­neous mes­sages, like SNMP; or when retrans­mis­sion is not fea­si­ble, like for exam­ple VoIP. UDP is used in some DNP3.0 pro­files, spe­cial­ly in mobile net­works, at the expense of less effi­cient han­dling of lost packets.

V

VLAN — Virtual Local Area Network

A Vir­tu­al Local Area Net­work (VLAN) is a is a sub­net­work which can group togeth­er col­lec­tions of devices that are con­nect­ed to sep­a­rate phys­i­cal LANs.

VLANs allow net­work admin­is­tra­tors to par­ti­tion a sin­gle switched net­work in order to keep net­work appli­ca­tions sep­a­rate despite being con­nect­ed to the same phys­i­cal net­work, with­out requir­ing new cabling or major changes in the cur­rent net­work infrastructure.

iGrid Solutions and Applications

Automation with IEC 61850 

The IEC 61850 stan­dard is enabling new opor­tu­ni­ties for ven­dor inter­op­er­abil­i­ty and advanced sub­sta­tion automa­tion. Find out how you can take advan­tage of IEC 61850 with easy-to-use and adapt­able solu­tions for a sim­ple migra­tion or retrofit.

IEC 61850 Automation

HV Substation Automation

Pow­er­ful sub­sta­tion automa­tion sys­tems often han­dle numer­ous com­mu­ni­ca­tion pro­to­cols and media with­in one net­work, which can result in expen­sive and com­plex projects.  Avoid these prob­lems with inter­op­er­a­ble tech­nol­o­gy and smart con­fig­u­ra­tion tools.

HV Sub­sta­tion Automation

MV Distribution Grid Automation

It is often dif­fi­cult to find the exact solu­tion you need in a MV appli­ca­tion, lead­ing to high­er costs than nec­es­sary. With our scal­able and adapt­able solu­tions you will be able to only pay for what you real­ly need, with­out com­prim­is­ing on qual­i­ty or security.

MV Dis­tri­b­u­tion Grid Automation

Photovoltaic Power Station

Using an open and scal­able SCADA sys­tem to mon­i­tor and con­trol a PV plant comes with many ben­e­fits on sev­er­al lev­els. Find out how advanced com­mu­ni­ca­tion tech­nol­o­gy affects PV oper­a­tion, main­te­nance, sys­tem design, invest­ment secu­ri­ty, profits…

Pho­to­volta­ic Generation

Protocol Conversion

As com­mu­ni­ca­tion net­works grow in com­plex­i­ty, “plug and play” promis­es become hard­er to keep. Inter­op­er­a­ble pro­to­col con­vert­ers and soft­ware solu­tions with state-of-the-art capa­bil­i­ties and funci­tonal­i­ties can be the bridge to all the func­tions and flex­i­bil­i­ty your net­work needs.

Pro­to­col Con­ver­sion Solutions

Generation Dispatch Control Center

With a gen­er­a­tion dis­patch enter you can auto­mat­i­cal­ly con­trol the gen­er­a­tion of all pow­er plants and make direct bids for ancil­lary ser­vices on one plat­form. Check out the most effi­cient com­mu­ni­ca­tion path between gen­er­a­tion sites, grid oper­a­tors and the pow­er market.

Gen­er­a­tion Dis­patch Center

Smart Metering

A sin­gle device that col­lects, process­es, trans­fers smart meter data and load curves from sev­er­al meters in dif­fer­ent pro­to­cols via ser­i­al or Eth­er­net, whilst pro­vid­ing advanced automa­tion func­tions? Adapt­able designs and a full com­mu­ni­ca­tion pro­to­col suite make it possible. 

 

Smart Meter­ing Solutions

Switchgear & Transformers

Some­times you have pre­ferred gear for a project or it has already been installed, but it is lack­ing the com­mu­ni­ca­tion capa­bil­i­ties to pro­vide the automa­tion func­tions you are look­ing for. With our soft­ware core iGComms any device can be as smart as you want it to be.

Switchgear and Transformers