© Copyright 2006 ABB. All rights reserved.
About this manual
Document No: 1MRK 511 193-UEN Issued: July 2006 Revision:
-THIS DOCUMENT HAS BEEN CAREFULLY CHECKED. HOWEVER, IN CASE ANY ERRORS ARE DETECTED, THE READER IS KINDLY REQUESTED TO NOTIFY THE MANUFACTURER AT THE ADDRESS BELOW.
THE DATA CONTAINED IN THIS MANUAL IS INTENDED SOLELY FOR THE CONCEPT OR PRODUCT DESCRIPTION AND IS NOT TO BE DEEMED TO BE A STATEMENT OF GUARAN-TEED PROPERTIES. IN THE INTERESTS OF OUR CUSTOMERS, WE CONSTANTLY SEEK TO ENSURE THAT OUR PRODUCTS ARE DEVELOPED TO THE LATEST TECHNOLOGICAL STAN-DARDS. AS A RESULT, IT IS POSSIBLE THAT THERE MAY BE SOME DIFFERENCES BETWEEN THE HW/SW PRODUCT AND THIS INFORMATION PRODUCT.
Manufacturer:
ABB Power Technologies AB Substation Automation Products SE-721 59 Västerås
Sweden
Telephone: +46 (0) 21 34 20 00 Facsimile: +46 (0) 21 14 69 18 www.abb.com/substationautomation
Page
Chapter
Chapter 1
Introduction ... 1
Introduction to the IEC 61850 Station Engineering guide... 2
About the complete set of manuals for an IED ... 2
About the IEC 61850 Station Engineering guide ... 3
Intended audience ... 3
Related documents... 4
Revision notes ... 4
Chapter 2
IEC 61850 station engineering ... 5
Station engineering in IEC 61850 ... 6
Engineering process in IEC 61850 ... 6
Designation model of IEC 61850 ... 9
IEC 61346 designation model used for IEC 61850... 12
Substation Configuration description Language (SCL)... 14
The Substation section ... 16
The communication section ... 20
The IED section ... 22
Signal engineering ... 24
Buffered Report Control Block (BRCB) ... 25
GOOSE Control Blocks (GoCB) ... 29
Chapter 3
IEC 61850 Station configuration tasks ... 31
IEC 61850 Station configuration tasks... 32
Chapter 4
PCM 600 and CCT tool set for station engineering.... 35
PCM 600 and CCT tool set for station engineering ... 36
PCM 600 views and windows ... 37
PCM 600 the toolbar and the mouse ... 41
PCM 600 options for operation ... 44
PCM 600 access ... 44
Connectivity package support for PCM 600 ... 50
PCM 600 Set up communication link per IED 670... 52
PCM 600 Set up communication link per Generic IEC 61850 IED 52 CCT views and windows... 53
The toolbar and the mouse... 56
Spreadsheet features ... 57
Navigator structure options... 66
Chapter 5
Set up a project in PCM 600 ... 69
Set up a project in PCM 600 ... 70
Managing projects in PCM 600 ... 71
Chapter 6
Set up a project in CCT ... 75
Managing projects in CCT ... 76
Import/export station.SCD files ... 79
Import station.SCD file... 79
Export station.SCD file... 80
Import/export ied.ICD files ... 81
Import ied.ICD file ... 81
Import of a client IED via CCT into a station project ... 82
Export ied.ICD file... 83
Chapter 7
Station configuration with PCM 600 ... 85
Set up a substation for IEC 61850 ... 86
Naming conventions for IEC 61850 ... 87
PCM 600 selection of an IED... 89
PCM 600 Generic IEC 61850 IED ... 91
Set up communication for IEC 61850 ... 94
Import/Export station.SCD files ... 96
ied.CID file generation for IED 670 ... 98
Chapter 8
Signal engineering with CCT... 99
IEC 61850 Attribute Editor ... 100
Data set engineering... 102
Predefined DataSet ... 105
BRCB engineering ... 106
Chapter 1 Introduction
About this chapter
This chapter explains concepts and conventions used in this manual and provides information necessary to understand the contents of the manual.
1
Introduction to the IEC 61850 Station Engineering
guide
1.1
About the complete set of manuals for an IED
The user’s manual (UM) is a complete set of five different manuals:
The Application Manual (AM) contains application descriptions, setting guidelines and setting
parameters sorted per function. The application manual should be used to find out when and for what purpose a typical protection function could be used. The manual should also be used when calculating settings.
The Technical Reference Manual (TRM) contains application and functionality descriptions
and it lists function blocks, logic diagrams, input and output signals, setting parameters and tech-nical data sorted per function. The techtech-nical reference manual should be used as a techtech-nical ref-erence during the engineering phase, installation and commissioning phase, and during normal service.
The Installation and Commissioning Manual (ICM) contains instructions on how to install
and commission the protection IED. The manual can also be used as a reference during periodic testing. The manual covers procedures for mechanical and electrical installation, energizing and checking of external circuitry, setting and configuration as well as verifying settings and per-forming directional tests. The chapters are organized in the chronological order (indicated by chapter/section numbers) in which the protection IED should be installed and commissioned.
The Operator’s Manual (OM) contains instructions on how to operate the protection IED
dur-ing normal service once it has been commissioned. The operator’s manual can be used to find out how to handle disturbances or how to view calculated and measured network data in order to determine the cause of a fault.
The IED 670 Engineering guide (EG) contains instructions on how to engineer the IED 670
products. The manual guides to use the different tool components for IED 670 engineering. It also guides how to handle the tool component available to read disturbance files from the IEDs on the basis of the IEC 61850 definitions. The third part is an introduction about the diagnostic tool components available for IED 670 products and the PCM 600 tool.
en06000097.vsd Application manual Technical reference manual Installation and commissioning manual Operator´s manual Engineering guide
The IEC 61850 Station Engineering guide contains descriptions of IEC 61850 station
engi-neering and process signal routing. The manual presents the PCM 600 and CCT tool used for station engineering. It describes the IEC 61850 attribute editor and how to set up projects and communication.
1.2
About the IEC 61850 Station Engineering guide
The Engineering guide IEC 61850 Station contains the following chapters: • The chapter “IEC 61850 station engineering” is not an introduction to the
IEC 61850 standard, but gives a short definition and task description for those parts of the standard needed to do station engineering and process signal routing. • The chapter “IEC 61850 Station configuration tasks” gives a description of the
principle tasks and steps to do station and signal engineering.
• The chapter “PCM 600 and CCT tool set for station engineering” presents the two tools used for IEC 61850 station engineering. It illustrates views and win-dows and describes CCT options and features. It also describes how to set up a communication link between PCM 600 and the IED.
• The chapter “Set up a project in PCM 600” describes how to set up and manage a project in the PCM 600 tool.
• The chapter “Set up a project in CCT”describes how to set up and manage the CCT tool and the import/export procedure of files.
• The chapter “Station configuration with PCM 600” describes how to set up a substation for IEC 61850 and how to set up communication for IEC 61850, in or-der to fulfil the IEC 61850 requirements for signal engineering.
• The chapter “Signal engineering with CCT” describes the IEC 61850 attribute editor, how the data objects in IEC 61850 are configured to data sets and engi-neering of the different control blocks.
1.3
Intended audience
General
This manual addresses system engineers, project engineers involved n the engineering process for a project, installation and commissioning personnel, who use technical data during engineer-ing, installation and commissionengineer-ing, and in normal service.
Requirements
The system engineer must have a thorough knowledge of protection and/or control systems, pro-tection/control equipment, propro-tection/control functions and the configured functional logics in the IED 670 devices. The installation and commissioning personnel must have a basic knowl-edge in the handling electronic equipment.
1.4
Related documents
1.5
Revision notes
Documents related to the PCM 600 and CCT tool set Identity number
Connection and Installation components 1MRK 013 003-BEN
Test system, COMBITEST 1MRK 512 001-BEN
Accessories for IED 670 1MRK 514 012-BEN
Getting started guide IED 670 1MRK 500 065-UEN
SPA and LON signal list for IED 670 1MRK 500 075-WEN
IEC 61850 Data objects list for IED 670 1MRK 500 077-WEN
Generic IEC 61850 IED Connectivity package 1KHA001027–UEN
Protection and Control IED Manager PCM 600 Installation sheet 1MRS755552
Engineering guide IED 670 products 1MRK 511 179–UEN
Latest versions of the described documentation can be found on www.abb.com/substationautomation
Revision Description
Chapter 2 IEC 61850 station
engineering
About this chapter
This chapter gives a short definition and task description for those parts of the IEC 61850 stan-dard which are needed to do station engineering and process signal routing. A reference to the IEC 61850 parts and clauses is given where needed. The reason for this chapter is to have the common platform about the tasks and the used wording. It can and will not be an introduction to the standard.
1
Station engineering in IEC 61850
The way of engineering and configuring a station according to IEC 61850 standard is described in part 6 of the standard. The title of this part is: “Configuration description language for com-munication in electrical substations related to IEDs”
This chapter contains some explanations about the definitions made by the standard. They may be requested to get a better understanding and as a reference when the different engineering steps made with the tools PCM 600/CCT are described. It is expected, recommended that the reader has a general knowledge about the IEC 61850 standard and especially of the parts 6 and 7.
1.1
Engineering process in IEC 61850
Figure 1: IEC 61850–6: Station engineering process
en06000105.vsd Substationn IED Configurator Vendor A IED Configurator Vendor B IED Configurator Vendor C Vendor A Vendor B Vendor C IED Control Vendor C IED Protection Vendor B IED Control Vendor C IED Protection Vendor B SA Gateway IED HSI Vendor A IED NCC GW Vendor B IED DB System Configurator IED Capablity ied.ICD System Sepcification stat.SSD Substation Configuration stat.SCD Configured IED ied.CID Sta tio n DB ied.ICD
The standard defines two tools and four file types for station engineering. The above figure shows these tools and files in their relation. In the ideal situation from top down the engineering process and the used tools and files have the following relation:
• System Configurator tool (SC)
- Import a station.SSD file when available. If not continue with the next step - Import the ied.ICD files of the products which will be used
- When no station.SSD file is available, configure the primary equipment (Busbar, Transformer, Apparatus, connections etc. to voltage level and bays. Make a single line diagram of the station. Remark: This step and the next one is not direct needed to do signal engineering in a station for IEC 61850 based communication. A minimum configuration of the plant structure is requested only.
- Place the Logical nodes to the primary equipment they belong to within a bay.
- Configure the communication with their subnetworks.
- Place the physical IEDs in the communication subnetwork and define the ac-cess points per IED
- Place the IEDs with their Logical devices and Logical nodes in the plant structure
- Do signal engineering. Configure DataSets, Control Blocks and link the communication path between server and clients or between servers (GOOSE).
- Export the complete station configuration in the station.SSD file for further use by the various IED Configurator tools
• IED Configurator tool (IC)
- Import the station.SCD file and extract the information valid and used for each used IED.
- Do additional engineering steps when necessary (vendor specific) - Check for received GOOSE messages and do GOOSE signal marshalling
when necessary
- Prepare the ied.CID file and download the file to the IED
- Precondition in this case: The IED is fully engineered to its function in the project. The ied.ICD file was exported with the complete configuration to the SC tool as described above.
• SSD file = System Specification Description file
- This file describes the single line diagram of the substation and the required Logical nodes. It is expected that the utility is able to support the project with such a file.
• ICD file = IED Capability Description file
- This file describes the full capability in Logical nodes and Logical devices of an IED without any relation to the substation and communication organiza-tion. This is the basis for the SC tool about the volume and capability of the selected IED for signal engineering. This file is possible in two principle variants. First it is a general description without a direct project specific con-figuration and programming. This file describes the general capability. Sec-ond it is the ied.ICD file of the full engineered IED according to project
specification and requirements. In this case the volume of available Logical nodes and therefore signals will be the final one. Which variant is used must be clarified within the project.
• SCD file = Station Configuration Description file
- An SCD file is given when the substation and communication section con-tains configured values. This file concon-tains all IEDs, a communication config-uration section and a substation section.
• CID file = Configured IED Description file
- The CID file contents is not part of the standard. It is vendor specific. It should contain the result of the engineering process on IED and station level. • As it can be seen there are various possibilities in which order the engineering
will be done. Especially the bay level IED for protection and control may need in most cases project specific adaptations and configuration, which has influence on the volume of used Logical nodes and therefore data objects. The concept allows to re-import an extended ied.ICD file and to add or delete signals in the station. The tools have to support this concept.
2
Designation model of IEC 61850
The description in the following sections will reference to an example station. This is relevant for the description of the object designation and signal addressing requirements.
A substation of any size consists of buildings, a lot of primary equipment, substation control equipment and a lot more. Each item has a name and will be identified by explaining to which part it belongs to. The rules will differ from country to country and by each utility.
Figure 2: Example station for object designation
en06000108.vsd =E1 (e.g. 135 kV) IED NCC Gateway IED Control IED Protection =-SB1 =E1.Q1 =-FP1 IED Control IED Protection =-SB1 =-FP1 IED Control IED Protection =-SB1 =E1.Q3 =-FP1 =E1.Q2 =-SA1 =AA1
=-WH1 (station bus, optical) =- WA1 =- WA2 =DeStat (DemoStation) =Q1 =-QB1 =-QB2 =-QA1 =-QB9 =-QC9 =-BI1 =-BU1 =Q2 =-QB1 =-QB2 =-QA1 =-QB9 =-QC9 =-BI1 =-BU1 =Q3 =-QB1 =-QB2 =-QA1 =-QB9 =-QC9 =-BI1 =-BU1
The IEC 61850 standard is based on the hierarchical addressing and designation model in a sta-tion. It follows in this way the structure of the substation equipment independent of IED struc-ture and organization.
This designation and addressing model is also visible in the IEC 61850 telegrams because the address is presented in MMS as an ASCII string, so the address can be seen directly in a readable form.
The above figure shows a virtual example station. The identification is based on the IEC 61346 concepts. Reasons to use the IEC 61346 model:
• the IEC 61346 has the task to define structuring principles and reference desig-nations.
• the standard is international in the same way as IEC 61850 is
• the standard has made a concept which can be used in all industrial systems in-dependent of a language, project etc.
• the standard use only single characters per level which makes the total designa-tion very short and therefore saves bytes to be transmitted.
• by using this designation model in IEC 61850 it allows to use an easy project in-dependent identification.
The designation of a Logical node and its signals (DO) is needed to identify it to the primary object etc. The hierarchical order in a substation is the path to identify the LN.
Figure 3: IEC 61850: Object identification model based on IEC 61346 (FuncName)
The designation path to get the position of the circuit breaker as an example would be: • DeStat => E1 => Q1 => LD1 => QA1 => XCBR1 => Pos => stVal
• in IEC 61850 = DeStat.E1Q1/LD1QA1XCBR1.Pos.stVal and for the operate signal of the time overcurrent protection: • DeStat => E1 => Q1 => LD2 => P => PTOC => Op • in IEC 61850 = DeStat.E1Q1/LD2P.PTOC.Op en06000110.vsd CSWI MMXU1 XCBR1 =-QB1 =-QB2 =-QB9 =-QC9 =-BI1 =-BU1 RBRF PTRC PDIS PTEF PTOC RREC stVal q t origin FC = ST Station = DeStat Pos =E1 =Q1 LD1 =-QA1 LD2 =B =P
The above model of designation identification is possible when the station configuration is based on the “FuncName” method in IED 61850. This is specified in the Header section of the SCL file. The standard identifies these object or signal designations as the technical key. The standard recommends to use the IEC 61346 based designation model, but it is not a must. But a similar naming structure is requested when an existing identification concept has to be used.
2.1
IEC 61346 designation model used for IEC 61850
Basics of the IEC 61346 standard: • three different views are defined
- the functional view (identified by =) - the product view (identified by -) - the location view (identified by +)
• to separate two levels in a row the character “.” is used. It is allowed to leave the “.” out, when the last character is a digit and the first character of the next level is a letter.
• the transition from one view to another is visible when both identification signs are used in the sequence from > to. E.g. =-QA1 indicates this is a transition from functional view “=” to product view “-”. The functional view is here the bay Q1 and the product is the circuit breaker QA1.
• each level is represented by one character. A second character is used to identify a type within a level, e.g. QB = HV switching equipment of type disconnector, QA = circuit breaker and QC = grounding disconnectors.
The IEC 61346 defines the rules etc. and gives explanations how to organize the structure and the use of the characters but it does not give a model for each industrial area. This has to be done by working groups.
For the substations for electrical energy distribution the German community of interest “IG EVU” has taken this task. Member of the IG EVU are beside others the main vendors and the main utilities of Germany. The papers are available and free of charge via Internet “www.ige-vu.de”. The documents can be found on the page “Veröffentlichungen”.
Figure 4: Extracts of IEC 61346 designation trees
en05000647.vsd
A Objects for overall control
B Switchgear > 420 kV AA Central control system C Switchgear 380 ... 420 kV D Switchgear 220 ... 380 kV E Switchgear 110 ... 220 kV F Switchgear 60 ... 110 kV G Switchgear 45 ... 60 kV H Switchgear 30 ... 45 kV J Switchgear 20 ... 30 kV K Switchgear 10 ... 20 kV L Switchgear 6 ... 10 kV M Switchgear 1 ... 6 kV N Switchgear < 1kV etc...
Function Level 2 and 3
en05000646.vsd A B Detection equipment BI Current transformer BU Voltage transformer F Protective equipment FA Surge arrester FP Protective relay Q HV switching equipment QA Circuit breaker QB Disconnector QC Earthing switch S Controlling equipment B Control unit W Transporting equipment A Busbar
HSignal and control cable, data bus (optical)
3
Substation Configuration description Language
(SCL)
The SCL language is based on XML.
It is of course not needed to know the XML file in its details and do any step which requests XML knowledge, but the organization of the information within the SCL files (ied.ICD and/or station.SCD) might be of interest. Especially to know where the engineering additions like DataSets and Control Blocks belongs to.
The SCL XML file is defined in five sections or descriptions, which are specified in IEC 61850–6 clause 9. These sections are:
• the Header
• the Substation description (section) • the Communication description (section) • the IED description (section)
• the Data Type Templates
The first two sections can be seen as tasks to organize the IEDs within the substation and to es-tablish the communication. These tasks are done by the PCM 600 tool. The Logical nodes as part of the IED are logically linked to the substation section by PCM 600. The signal engineering task and routing of the signals is the task of the CCT tool. Its precondition is that PCM 600 has done the complete organization on the two sections substation and communication.
The DataSets and Control Blocks configured by the CCT tool are located in the IED section be-cause they are logically defined as part of the Logical nodes (see IEC 61850–7–2 clause 9). The CCT needs the correct configured communication section when it comes to GOOSE engineer-ing.
The Data type templates section is requested to give the correct content description of each Log-ical node type to all user of the information. These are the clients. Each IED and vendor may have/has its own Logical node type definitions.
Figure 5: IEC 61850: Principle structure of the SCL XML file
Figure 5 shows a principle structure of the SCL XML file with its five sections. The arrows show the link between the different sections given when an IED is integrated in the substation struc-ture and/or in the communication strucstruc-ture. All available Logical nodes of an IED are linked to the substation section.
en06000111.vsd Id
ToolId Nam eStructure
IED Nam e AccessPoint Address GSE IED Nam e AccessPoint Address GSE
Services Authentication LDevice DAI DOType DAType Enum Type Header He a d e r Substation VoltageLevel Bay LNode IED LD LN IED LD LN Com m unucation Subnetwork Connected AP IED AccessPoint Server GOOSE Control LN0 LN DataSet DOI DataTypeTemplates Report Control Inputs DOI SettingControl LNodeType DOType DAType Enum Type DO DA St at io n IE D SDO BDA FuncName or IEDName
A reference to the GoCB is included in the communication section when the GoCB is config-ured.
The above graphical presentation of the XML file is a standard view of XML editors. It gives a better picture about the structure of the XML contents.
3.1
The Substation section
The substation description in IEC 61850–6 clause 9 describes the organization of the primary equipment in a single line diagram on one side. On the other side it describes the used LNs be-longing to a bay. The second part is of interest for the signal engineering.
In part 6 clause 8.4 of the standard the object and signal designation rules are described. The identification for the signals are therefore also used in the telegrams defined in IEC 61850–8–1 is named “Technical key”. The technical key is used within the SCL description to identify and reference objects. See chapter 2, section 1 "Station engineering in IEC 61850" about the concept based on IEC 61346. PCM 600 generates an “SCL Technical key” independent of the naming given by the project. The PCM 600 generated technical key is based on the definitions given in IEC 61346 and for electrical substations. When a project is using its own naming model this will be used by the SCL description as technical key. PCM 600 allows to select the version which should be used in the SCL files when exporting a station.SCD file.
Signal identification in the communication system
The signal identification rules used by IEC 61850 are described in part 7–2 clause 19.2. and used in part 6 clause 8.4.2
The signal designation consists of four parts:
1. a user defined part identifying the Logical device LD in the process (LDName) 2. a function related part to distinguish several LNs of the same class within the
same LD/IED (LN-Prefix)
3. the standardized LN class name and the LN instance number, which distinguishes several LNs of the same class and prefix within the same LD/IED
4. a signal identification inside a LN consisting of data and attribute name as de-fined in IEC 61850–7–3 and IEC 61850–7–4
Figure 6: Elements of the signal identification as defined in IEC 61850–7–2
The above figure is taken from the standard IEC 61850–6 (figure 5). The standard defines two options how to use part 1 and part 2 above:
1. Function related naming
• identified in the SCL header with NameStructure = FuncName 2. Product related naming
• identified in the SCL header with NameStructure = IEDName Within one SCL project only one option can be used.
Function related naming
Figure 7: IEC 61850–6: Function related naming
The part 1 = LDName of signal identification is build out of the objects Substation (1), Voltage level (2), bay (3) and the LD (4). The LN Prefix in this case is an additional element which be-longs to the LDName part. It identifies the equipment or sub-equipment object in the primary
en06000099.vsd Substation LDCL1 LDCL2 VL1 Bay1 LD2 > LNs Bay2 LD2 > LNs Bayx VL2
Bay1 Bay2 Bayy
LD2 > LNs LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LN LN LN LN LN LN LN 1 2 3 4 5 6 LD3 > LNs 2 3 4 5 6 LDName LNName
LN Prefix LN class LN instance no
Substation section IED section Substation section
1 2 3 4 5
Signal naming using functional naming
Elements of signal identification IEC 61850-7-2
structure. The typical example is the circuit breaker QA1, when the LN classes XCBR, CSWI and CILO are used. It has to be regarded that in this model the IED is not included and the nam-ing is based in the process objects only.
The LNName is in this option the LN class and the LN instance (6) only.
Product related naming
Figure 8: IEC 61850–6: Product related naming
en06000100.vsd IED section Substation LDCL1 LDCL2 VL1 Bay1 Bay2 LD2 > LNs Bayx VL2
Bay1 Bay2 Bayy
LD2 > LNs LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LD1 LN LN LN LN LN LN LN LN LN LN LN A B C A B C B LDName LNName
LN Prefix LN class LN instance no
IED section
Signal naming using product naming
Elements of signal identification IEC 61850-7-2
IED 4 IED 5 IED y
IED 1 IED 2 IED x
A 1 2 3 C C 2 3
The LDName part is build in this option out of the objects IED (A) and LD (B). The link to the primary process is not given in this model.
The LNName is in this option the LN Prefix, the LN class and the LN instance no (C).
The LN prefix allows in this model to identify several versions of a LN class. For example the eight different versions the LN class PDIF.
The link between the IED and the primary process (Substation (1), Voltage level (2), bay (3)) is given in the substation section of the station.SCD file but not in the signal identification in the telegram. The project may decide how to deal with this matter. The IED name may be extended with a short form of the three missing levels. The IEDName must be unique in this designation model.
Remark:
The standard defines the maximum length for the signal naming and for identification parts to 32 ASCII characters each. This has to be regarded for the object identification for part 1 to part 4 (see figure 6). In addition it might be possible that client IEDs have additional restrictions which have to be taken into account.
Most vendor have to use the LN Prefix to identify their versions etc. Therefore the product re-lated naming model (IEDName) will be used.
3.2
The communication section
The organization of the physical IEDs to the communication network is independent of the sub-station structure. The IEC 61850 standard defines the communication network with no relation to an existing media and protocol. The first mapping to an existing media and protocol is done in IEC 61850–8–1 with:
• Ethernet as medium
• MMS (Manufacturing Message Specification) protocol as defined in ISO 9506–1 and IOS 9506–2.
The IEC 61850 standard describes in part 7–2 the Abstract Communication Service Interface (ACSI) in a media and protocol independent form. Part 8–1 specifies the mapping of this ACSI to the existing MMS.
The communication section in the SCL file describes the minimum of what is needed to identify how information is routed between the IEDs in a project. This is.
• the used subnetworks
• the IEDs connected to the different subnetworks • the access points per IED to the subnetworks • the address
• the IP address of the LAN network is as an exception also part of the address el-ements
• and, extended during signal engineering and routing, the link to the GoCB mes-sage in transmission direction.
Figure 9: IEC 61850–6: Communication network
Figure 9 shows the contents of the communication section. Additional information about the server etc. is part of the IED.
The link to the IEDs is done by PCM 600 when the IED is placed and the link to the subnetwork established. The list of “Connected AP” in the communication section of the SCL file includes all IEDs with their APName.
A station as shown in figure 3 the station uses two voltage levels with a set of bays and IEDs per bay. The communication network can be done in several ways for this station. The most typical variants are shown in figure 10.
en06000101.vsd
IED (server)
- Access Point (AP) - Address - GSE; GoCBs Communication AP IED (server)
- Access Point (AP) - Address
- GSE; GoCBs Communication
IED (server)
- Access Point (AP) - Address - GSE; GoCBs Communication AP IED (client)
- Access Point (AP) - Address
- GSE; GoCBs Communication
IED (client)
- Access Point (AP) - Address
- GSE; GoCBs Communication
Figure 10: Communication section: Possible network configuration examples
Both variants fulfil the requirements and performance. Variant 2 may be used, when the avail-ability question is discussed. In this case only one voltage level of the station is lost when a sub-network fails. The client IEDs must be able to handle two access points.
3.3
The IED section
The IED section describes the complete IED as it is needed for IEC 61850 communication and signal engineering. The Data Type Template part of an IED may be seen as part of the IED, even when separated in its own section. The ied.ICD files includes the description of the LNs, their Data Type Templates and the used/supported services. The structure of the IED section follows the definitions made in the IEC 61850 standard.
There are two basic IED types which are used: • station level IEDs
- IEDs located on station level and dealing with the information transmitted from/to the bay IEDs are identified as client IEDs. They are represented by Logical nodes of group “Information (I)”. This are the LNs = ITCI, IHMI and
en06000103.vsd IED 4 IED 5 IED y IED 1 IED 2 IED x
Client IED 2 Client IED 1 Subnetwork 1 VL 1 VL 2
IED 4 IED 5 IED y IED 1 IED 2 IED x
Client IED 2 Client IED 1 Subnetwork 2 Subnetwork 1 VL 1 VL 2
ITMI. They are the receiver of information in monitoring direction and send-er of commands (control). These LNs have no data objects. They are only used to do the link of the report control blocks (BRCBs) from the server IEDs.
• bay level IEDs
- all IEDs on bay level are server IEDs. Signal engineering is done within the server IEDs.
Figure 11: Organization of LDs, LNs, DOs and DAs in an IED
The above figure is a short summary about the logical organization of the signals below the IED. • A server represents the communication interface to the subnetwork (Ethernet).
• one or more Logical device(s) are connected to a server • a set of Logical nodes belong to a LD
en06000104.vsd AP Subnetwork Control
IED
CVMMXU1 SB1.LD1 Server LPHD SXCBR1 SCSWI1 SXSWI1 SCSWI2 SXSWI2 SCSWI3 SXSWI3 SCSWI4 SXSWI4 SCSWI5 LLN0 Mod CBOpCap Origin Data Data Attribute Beh Health NamePlt ctlVal Pos Loc OpCnt BlkOpn BlkCls stVal q t Logical Node ctlModel• the LN LLN0 is a special LN per LD and contains the DataSets, the various con-trol blocks, inputs (from GOOSE messages) etc.
• The LN LPHD is a special LN per LD and contains data objects which describe the status of the physical device (the IED)
• each Logical node represents a function and contains a number of data objects (DO)
• each DO is represented by a number of data attributes (DA)
The data objects are representing information signals which may be routed to station level IEDs. So the signal engineering task is to select the requested signals (DOs) and link them to the client IEDs as receiver. The control services are not directly engineered. They are included in the data objects which handle both directions the command (control) and the response (monitoring). So when routing the DO in monitoring direction the control is then also known by the clients. The organization of the IED from LD down to DAs can be viewed in the CCT tool. This orga-nization concept has to be taken into consideration when DataSets are configured.
The number of data objects and data attributes per DO is defined by the used LN type in this IED. The contents is taken from the Data Type Templates which belong to an IED type.
3.4
Signal engineering
DataSets
IEC 61850 has defined DataSets and report control blocks for signal transmission in monitoring direction. DataSets are also used for GOOSE messages in horizontal direction. Which data ob-jects or single data attributes should be collected in a DataSet is not specified and can be done to rules which may be defined in a project. The following figure shows a DataSet where all po-sition information of the apparatuses of a bay are put into one DataSet.
The vendor of an IED can define DataSets as defaults which are part of the IED and always available. They need to be linked to the client IEDs only when you want to use them as they are. The vendor has to declare when these DataSets can be modified to projects need or not.
Figure 12: IEC 61850–7–2: Example of a DataSet
General rules for DataSet configuration:
• All data objects or their data attributes which are signals in monitoring direction can be selected for a DataSet
• only those data attributes of a data object can/will be selected which have the same function constraint (FC).
• data objects with different FC can be selected for a DataSet. For example DOs with FC = ST and DOs with FC=MX can be member in one DataSet.
• a single data attribute can be selected when it is specified with a trigger option. For example the data attribute stVal of the data object Pos can be selected as a member of a DataSet, because it is specified with the trigger option data change detected (dchg).
The description of the DataSets with name and the list of data object members (FCDAs = Func-tional Constraint Data Attributes) is included in the SCL file in the IED section in the Logical device subsection. As specified in IEC 61850–7–2 clause 9, the DataSets are part of a Logical node. They are most likely included in the LLN0.
3.4.1 Buffered Report Control Block (BRCB)
To be able to transmit the signals configured in a DataSet a BRCB must be configured which handles and specifies how the events will be transmitted to the clients.
en06000106.vsd LD1/SXCBR1.Pos FC=ST LD1/SXSWI1.Pos FC=ST LD1/SXSWI2.Pos FC=ST LD1/SXSWI3.Pos FC=ST LD1/SXSWI4.Pos FC=ST LD1/LLN0.AppPos DATA-SET CVMMXU1 LD1 LPHD SXCBR1 SCSWI1 SXSWI1 SCSWI2 SXSWI2 SCSWI3 SXSWI3 SCSWI4 SXSWI4 SCSWI5 LLN0 Origin stVal q t Pos Pos Pos Pos Pos
The contents of a BRCB is listed in IEC 61850– 7–2 in clause 14, table 23. The BRCB contains a lot of attributes which are of interest to handle and secure the communication between the cli-ent and the server and may be set once as default in a project. Others are of application interest in the way events are handled in a project.
• Buffer time
- This parameter describes how long the report should wait for other expected events before it will send the report to the client. When it is known, that ad-ditional events will be generated as a follow up it is useful to wait for exam-ple 500 ms for additional events stored in the report. This feature reduces the number of telegrams transmitted in case of a burst of changes. But on the oth-er side it increases the ovoth-erall transaction time for events from IED input to presentation on HSI which is normally defined to be one second!
• Trigger options
- The data attributes know three different trigger options (dchg, qchg, dupd). Within the BRCB the two other can be defined (integrity and general inter-rogation). The attribute Trigger option is a multiple choice and allows to mask the supported trigger options in this BRCB.
• Integrity period
- When integrity is selected in the trigger option attribute, it is needed to define an integrity period to force the transmission of all data listed in the DataSet. This is done by the attribute Integrity period. This feature can be used as a background cycle to ensure that the process image in all partners is the same. Nobody is perfect and someone in the long chain from the contact up to the NCC may have lost an event. The background cycle can repair it.
• General interrogation
- A general interrogation is only done on request from a client. Not all Da-ta-sets may contain information which is needed for a general update of the client. For example data with T(ransient) = TRUE are not part of a GI. When the BRCB attribute general interrogation is set to TRUE a GI request from the client will be handled. The report handler will transmit all data defined in the Data-set with their actual values. The IEC 61850 standard defines that all buffered events shall be transmitted first before the GI is started. A running GI shall be stopped and a new GI shall be started, when a new GI request is received while a GI is running.
• Purge buffer
- This BRCB attribute can be used by a client to clean the event buffer from old events. The events are discarded on request of the client. This feature can be used to delete old events not transmitted to the client due to stopped com-munication. After the link is reestablished the client can decide to clean the buffer or to receive the history.
Trigger Options
IEC 61850 has defined in total five different TrgOp. Three of them belonging to data attributes and marked per data attribute in the column TrgOp of the CDC tables in part 7–3. The other two belonging to the configuration of control blocks. The five trigger options are:
- The classical trigger. Whenever a process value has changed its value either binary or a measurement a transmission is done. How it is detected and how the Logical node is informed is not part of the standard.
• qchg = quality change
- Looking to the possibilities of the quality data attribute type (q) any changes in the quality description will be transmitted.
• dupd = data value update
- This trigger option give the possibility to define that a transmission should be done on a condition which can be controlled by the application.
• integrity
- This trigger will force the transmission of all process values defined in the Data-set when a timer value (the integrity period) expires. It can be used for example to do a process signal update in the background (e.g. every 15 min-utes).
• general interrogation
- This trigger is forced by the clients (= station level IED; NCC gateway, sta-tion HMI, ...). Normally a GI is asked for, when the client and the server start or restart a session. When the client is able to receive the actual values and when the Logical device has scanned all process values at least once, an im-age of the actual process signal status can be transmitted to the client.
Link BRCB to a client LN
The BRCB has to know to whom the events shall be transmitted. This is the signal routing en-gineering step. The IEC standard 61850–6 describes that this is given by including the LN of the client IED in the ReportBlockEnabled option.
The selected client IED with the corresponding LN (e.g. ITCI) is included in the SCL structure of the Report Control description of the IED section.
CCT is doing it when the client LN is linked with the name field of the BRCB by the drag-and-drop method.
The description of the BRCB with selected DataSet, configured parameters and selected IEDs is included in the SCL file in the IED section in the LN0 structure for the LD where this LN0 belongs to.
Figure 13: Link BRCB to a client LN en06000107.vsd LD1/SXCBR1.Pos FC=ST LD1/SXSWI1.Pos FC=ST LD1/SXSWI2.Pos FC=ST LD1/SXSWI3.Pos FC=ST LD1/SXSWI4.Pos FC=ST LD1/LLN0.AppPos DATA-SET IED HSI Client 1 IED NCC GW 1 Client 2 IED NCC GW m Client m IED 1 Server 1 Subnetwork ITCI2 ITCI1 IHSI1 LLN0
3.4.2 GOOSE Control Blocks (GoCB)
Figure 14: IEC 61850: Principle operation of GOOSE messages
The Generic Object Oriented Substation Event (GOOSE) class model is used to distribute input and output data values between IEDs on bay level (in horizontal direction) through the use of multicast services. GOOSE messages bypass the server and enables a fast transmission from publisher to one or several subscribers (receivers).
en06000109.vsd S end Data-set Rec e iv e Rec e iv e LN LN LN LN LN S end Data-set Rec e iv e Rec e iv e LN LN LN LN S end Data-set Rec e iv e Rec e iv e LN LN LN LN LN LN Subnetwork LN0 GoCB DataSet Input GoCB GoCB DataSet DataSet Input Input Comm. GSE LD1 Server LN0 GoCB DataSet Input GoCB GoCB DataSet DataSet Input Input Comm. GSE LD1 Server
GOOSE messages are unidirectional, send only messages which request an application specific method to secure that sender and receiver of the message operates safely. This implies that the receiver of the GOOSE message distributes also GOOSE messages and close the loop for com-munication (request — respond on application level). The return message is not a must. It de-pends on the application in which way a confirmation may be done.
The GOOSE message concept will be used for all application functions where two or more IEDs are involved. Typical example is the station-wide interlocking procedure.
The very simplified figure above shows the GOOSE concept for three IEDs which interchange GOOSE messages between each other.
To send GOOSE messages a GoCB must be defined and a DataSet is needed which contains the data objects of single data attributes to be send.
A GOOSE message is forced to be transmitted when a trigger change is detected for a data at-tribute. All members of the Data-set will be copied in the send buffer with their actual value and the message is sent. All subscriber which knows the address of this GOOSE message will re-ceive the telegram. The GOOSE message includes sequence number etc. to verify that all mes-sages are received.
The concept what has to be done in case of a lost message etc. is part of the application and not described in the standard.
The DataSet for GOOSE messages are configured in the way described above. A GoCB has to be defined per GOOSE-DataSet.
GOOSE messages bypass the server and send direct from the communication part on the Ether-net. This is identified for the communication in the SCL communication section in the GSE el-ement, where the name of the GoCB is listed under the ConnectedAP.
Link GoCB to an IED
The IEDs which should receive this GOOSE message must be known and they have to be in-formed in the engineering state that they will receive GOOSE messages. This is given when the external Reference, the name of the IED and the member of the DataSet is included in the LN0 under the structure of the LD of the receiving IED. This part is identified as “Inputs”.
The IEDs which shall receive the GOOSE are selected by CCT. CCT is doing it when the IED itself (the IED icon) is linked with the name field of the GoCB by the drag-and-drop method.
Chapter 3 IEC 61850 Station
configuration tasks
About this chapter
This chapter describes the principle tasks and steps to do station and signal engineering accord-ing to IEC 61850–6 definitions. It gives an overview about the correspondaccord-ing steps to be done by PCM 600 and CCT.
1
IEC 61850 Station configuration tasks
The IEC 61850 standard defines the complete part needed for information communication in a substation. This can be split into the following parts:
• the definition of data objects and their common data classes with their data at-tributes
• the definition of Logical nodes (LN) as the communication interface for a substa-tion funcsubsta-tion (e.g. a protecsubsta-tion funcsubsta-tion)
• the definition of a basic communication structure for substation and feeder equip-ment
• the practical mapping of the communication to an existing protocol the MMS • the definition of the engineering process for a substation control system in a
con-figuration description language for communication in electrical substations
We refer to the IEC 61850 standards in their actual version as a basis for the engineering tasks described inhere by using the PCM 600 and the CCT. The main parts which are of interest are described in a brief form in chapter 2 "IEC 61850 station engineering".
A short form of the complete station and signal engineering sequence can be described as shown in the following figure.
Figure 15: IEC 61850: Station configurator
The procedure can be split into three main parts
1. Configuration of the station structure including IEDs and communication with PCM 600
• configure the plant structure in voltage levels and bays
• place all bay IEDs from ABB and other vendor (using the Generic IEC 61850 IED as a placeholder) in the bays
• do IED engineering for ABB IEDs with PCM 600 to generate the ied.ICD files en06000207.vsd text
IE
C 61850 St
ation Configurator
prepare ied.CID files Vendor X IED prepare ied.CID files Vendor A IED prepare ied.ICD files Vendor A prepare ied.ICD files Vendor X prepare ied.ICD files Vendor B prepare ied.CID files Vendor B IED station.SCD y configure station structure y integrate IEDsy load ied.ICD files
y configure communication subnetwork y export station_PCM.SCD file
PCM 600
y configure DataSets per IED
y configure and link report control blocks y configure and link Goose control blocks y export station.SCD file
CCT
• do the similar tasks for the other bay IEDs with their IED engineering tools and export the ied.ICD files or take the ied.ICD files from a vendors library • import all other ied.ICD files to their position in the station via Generic IEC
61850 IED.
• check the communication subnetwork that all IEDs are connected to the same subnetwork
• give each bay IED its IP address • export the station_PCM.SCD file
2. Signal engineering for the IEC 61850 signals with CCT
• create a project in CCT, if it not already exists for the station • import the station_PCM.SCD file created by PCM 600
• actually import client IEDs with their ied.ICD file to the station configura-tion by CCT
• link the client IEDs to the communication subnetwork and define the access point
• save, close and load the CCT project again; only when client IEDs are added by CCT first time
• check the pre-configured DataSets for report control blocks for your needs and for each IED. Generate additional DataSets for RCBs when requested • generate the needed DataSets for GOOSE messages
• create and configure Buffered Report Control Blocks (BRCB) for each data set used for vertical communication.
• link each DataSet for vertical communication to a BRCB • link the IED clients Logical node (ITCI IHMI) to the BRCBs
• create and configure GOOSE Control Blocks (GoCB) for each DataSet con-figured for GOOSE messages
• link the GOOSE DataSets to a GoCB
• link the IEDs which shall receive the GoCB to the GoCB • update IEC 61850 data flow (CCT specific function)
• export the station.SCD file for further use by the IED configuration tools 3. Preparation of ied.CID files per IED and download them to the IEDs
• import the station.SCD file to all IED configuration tools for further activi-ties
• for ABB bay IEDs use the PCM 600 for IED engineering
• do signal marshalling with the SMT tool in all ABB IED 670s which are in-volved to receive GOOSE messages
• download the updated ied.CID file to the IED 670 with the SMT tool • do similar tasks for all other IEDs with their IED configuration tool
This is a short form of the complete procedure for IEC 61850 with PCM 600 and CCT. The additional tasks for signal engineering for IEC 61850 in an IED 670 are described in the 'Engineering guide for IED 670 products'.
Chapter 4 PCM 600 and CCT
tool set for station
engineering
About this chapter
This chapter explains the presentation of the two tools used for IEC 61850 station engineering. The PCM 600 and CCT tool.
1
PCM 600 and CCT tool set for station engineering
PCM 600 and CCT are state of the art tool sets based on Microsoft.net technology.
The two tools are able to do the station configuration tasks as defined by IEC 61850–6. They are doing it for the IED and subnetwork configuration in a plant structure and in a communication structure by PCM 600. The signal engineering which is defined by the DataSets, the report con-trol blocks and the GOOSE messages is done with the CCT.
PCM 600 is a tool which supports in itself the tasks needed to do IEC 61850 station engineering but it is also the platform for several sets of tool components used to support IED engineering for ABB IED product families. This manual describes the IEC 61850 station configuration task only.
It is requested to use the IED engineering guide manuals in addition when ABB IEDs are part of the IEC 61850 based station project.
The description of the PCM 600 is limited in most cases to the part needed for IEC 61850 station configuration.
The CCT is a tool which is used by ABB as a base product for signal engineering of several pro-tocols. This version of CCT is also limited to the tasks needed to do signal engineering for IEC 61850 protocol. The precondition to use CCT is that the plant structure with the IEDs and the communication structure is build by PCM 600. See chapter 3 "IEC 61850 Station configuration tasks" for a description of the general tasks for IEC 61850 station configuration by using PCM 600 and CCT.
2
PCM 600 views and windows
The PCM 600 tool set runs under the operating system Windows 2000 or Windows XP. It is ex-pected that the user is familiar with the handling and use of the Windows platform. In this chap-ter only those items are explained and shown which are specific to PCM 600 but still based on Microsoft windows methods.
When you start PCM 600 and no project is already selected you will get an empty window with the base menubar and toolbar only. Once you have selected a project, you will be given the pos-sibility to select different views. The start menu of a project may look like the menu shown in the figure below.
Figure 16: PCM 600: base screen example
en06000028.vsd
Project
Explorer
&
Object
Types
Object
Properties
Output & Logging
Place for
selected tool
Menubar & Toolbar
Figure 17: PCM 600: base menubar Possible views: • Project Explorer • Object Properties • Output • Object Type Project Explorer
The Project Explorer window is the skeleton of the project organization. It is used to show the project in two different structures:
• the plant structure
• the communication structure
The plant structure is the most commonly used view and shows the organization of the stations in the geographical order top down from a defined highest level (e.g. the network control center (NCC)) down to each IED logically connected to a bay in the station. The plant structure is used to select the tools per IED.
The communication structure is not needed for normal operation. It is used to view the commu-nication network and links from the PCM 600 to each IED. Only the private commucommu-nication from the PCM 600 to each IED is managed and handled by the PCM 600.
To select the communication structure do a right mouse click on the area next to the Plant Struc-ture tab. Select communication and an additional page will be included which shows the com-munication structure of the PCM 600
en05000580.vsd
Object Properties
The Object Properties window is a standard Microsoft window which allows the user to view and when needed to modify properties of the selected object. In the PCM 600 frame this window is used by some tools like GDE to insert the IP address of the IED selected and some other erties like object naming in the HMI picture and so on. It might be necessary to check some prop-erties for communication to adapt and synchronize the communication network. The shown properties in the object properties window follow the selected object in the Project Explorer or in a tool.
Figure 19: PCM 600: Object properties window
Modifications are only possible in cells with their content shown in bold. Renaming of objects can be done more easily by using the Rename capability in the plant structure, which is made available by pressing the right mouse button.
Output
The Output window is shown on the bottom array of the PCM 600 screen when selected. It is a log script which is used by PCM 600 to list all activities, warnings, error messages etc. which come up during operation of the PCM 600. It might be needed and used when a task does not operate as expected. The information in the output list may provide a clue as to why it does not operate etc. The Output view is not needed for normal operation and can be closed.
Figure 20: PCM 600: Output window
Object Type
Figure 21: PCM 600: Object Type window
The window Object Type can be used to build up a plant structure using drag and drop and se-lecting the object type from the list of possible objects. It is opened in the same place and then the Plant Structure is presented. It is selected by clicking on the Object Types tab at the bottom of the window.
The Object Type window contains some different panes depending on selected structure. For the plant structure view the two panes are selectable by clicking the menubar General or
Transmis-sion IED”.
More details to different views etc. are given in chapter 5 "Set up a project in PCM 600". en05000558.vsd
IED tools
These tools are not used for IEC 61850 station configuration.
Each started IED tool will be visible in the residual screen area surrounded by the three windows
Plant Structure, Object Properties and Output. For normal operation only the Plant Structure is
needed and it is recommended to close the other two windows. More then one tool can be open at the same time for one IED or for some IEDs in parallel. But only one tool at a time is active. The tool is selected either by its tool tab or by selecting the IED.
See the IED engineering guide manuals for more derails.
2.1
PCM 600 the toolbar and the mouse
For each IED 670 tool the PCM 600 basic menubar and toolbar is expanded by additional menu-lists and tool-icons. This is not given and needed for IEC 61850 station configuration. For more details see 'Engineering guide for IED 670 products'.
The right button of the mouse is supported. Clicking the right mouse button opens a context sen-sitive menu. This menu presents all possible actions and selections corresponding to the selected object.
Figure 22: PCM 600: Conditional selection by the right mouse button
Depending on selection as given in this example the alternative choice could be to select New.... In this case a new window will pop up and it shows the same selection possibilities.
Figure 23: PCM 600: New object selection window
The window keeps open after your selection. Depending on the selected object it will show di-rectly the possible choices.
Save tool engineering results
PCM 600 stores additions and changes in the plant and communication structure direct in its da-tabase. This function is not needed for IEC 61850 station configuration.
The PCM 600 stores all changes for which it is responsible directly in the database. This is useful because these changes are only of type organization and have no influence on IED data. Chang-es, additions etc. done within a tool are only moved to the project database when they are saved. This possibility is context sensitive and will be displayed in the PCM 600 base menu bar under File when a tool has the ability to save.
Figure 24: PCM 600: Save tool result window
Cut, copy, paste, drag and drop
PCM 600 supports these functions where possible and useful. Depending on what it is and where it is inserted as a copy a request to rename the object may appear. It is indicated as “copy of... ” until it is given a unique name.
All other possibilities are self explanatory or Microsoft Windows standard.
en05000574.vsd
3
PCM 600 options for operation
The options can be selected from the menulist Tools>Options. A pop up window will be dis-played showing the entry point for the four different options. The four option windows are:
1. Log Configuration
• to organize the log file which is produced during the sessions and shown in the Output view of PCM 600
2. Category Manager
• allows the definition of user groups with different rights to work with PCM 600 according to their need and task.
3. System Settings
• specifies the basic decision about access rights for PCM 600 by the authen-tication method
4. User Manager
• is used to edit the list of persons or users which can use PCM 600 when an authentication method is selected
3.1
PCM 600 access
The set up and the possibilities to organize PCM 600 access can be seen as a branch with three basic alternatives. For each of the three alternatives you have to set up information in the user manager and select a user category out of the list described by the category manager.
Changes in the System Settings, Category Manager and User Manager can only be done by a user of the category type “System Engineer”.
The used alternative is selected in the Authentication. Select the System Settings window to choose the authentication.
Figure 25: PCM 600: Set authentication window
Set Data Access Password
This password is used to control access to the MSSQL$PCMSERVER. It is recommended not to enter a password when several users have access to PCM 600. Only a single user with his own PC may use this.
PCM 600 must be reinstalled and all projects will be lost if this password is not available!
User authentication
The tasks and action in each branch can be sorted like this: 1. Use Authentication
• NO = no selection. Everybody can use the PC where this PCM 600 is in-stalled.
• YES = Authentication is used. Select the method with one of the two choices: 2. PCM Authentication or
3. Windows Authentication Select the User manager.
Figure 26: PCM 600: User profile window
The User Manager window has four input fields. Three of them are used to define the access for a user for either PCM or Windows authentication. The field Real Name might be used to identify the user, when the user name is a short version of his name.
The PCM authentication uses the following inputs to identify a user: • User Name
• Set Password (optional)
• User Category. The user category is defined in the category manager. It belongs to the user name and is not part of the authentication check.
The Windows authentication uses the following inputs to identify a user: • User Name
• Windows Account.
• User Category. The user category is defined in the category manager. It belongs to the user name and is not part of the authentication check.
• Set Password is not used!
PCM authentication
When the PCM authentication method is used a Login window pops up after start of PCM 600. The user has to identify himself with his user name and the password when it is used for access control.
Figure 27: PCM 600: Login window
Rules to set a password: • can not be empty
• is at least 8 characters long
• contains at least one special character (like ! , \, &, etc.) • starts and ends with an alphabetic character
• contains at least one number
• contains at least one uppercase character • contains at least one lowercase character
Windows authentication
In the Windows authentication method each user must have a different account on this PC. Only in this case a selective input is possible. In this case the user has already identified himself to the PC, when he started Windows. So a separate access control is not needed.
A user can change his password, by entering his old password once, and then the new password twice. The system engineer can change passwords without knowledge of the old passwords.
Figure 28: PCM 600: User window with password setting
Category Manager
Different categories of default user are defined for PCM 600: • System Engineer
- has access to all tools and functions
- is the only one who can edit user management • Application Engineer
- has access to all tools for engineering the IEDs
- has access to the system monitoring tools to check during commissioning phase the correct operation of the IED
- has no user management rights • System Monitoring User
- has access to the system monitoring tools to monitor the IEDs during opera-tion
- has no access to the engineering tools - has no user management rights
Figure 29: PCM 600: Category manager window
4
Connectivity package support for PCM 600
PCM 600 is a tool which allows the user to include the engineering tool components for product families of ABB for transmission and distribution. In the way you are using ABB products it might be that you will have several sets installed using the concept of connectivity packages. How to install a new product package or to add an additional communication protocol is de-scribed in the documentation for PCM 600.
To engineer the ABB IED 670 product family you must have enabled the use of these tools and protocols in the connectivity package manager. Please check that before you may start the PCM 600.
Figure 30: Connectivity manager: version selection window
Always use the latest version of a tool package or protocol. This can be easily done in the menubar Set Latest.
In the above Connectivity Package Manager window the following packages are available • Generic IEC 61850 IED connectivity Package
- It will be used to include the ied.ICD file of bay IEDs in the station.SCD file. - It will be used, when the DRH tool is used to read the DR files from all IEDs running the IEC 61850 protocol. See IED engineering guide manual for more details about the disturbance report handler (DRH).
• IEC 61850 Connectivity Package
- This package is needed for IED 670 products, which communicate with PCM 600 on Ethernet, TCP/IP and using elements of the IEC 61850 proto-col.
• LON Connectivity Package
- This package is not needed for IED 670 products. It is used for products us-ing LON to communicate with PCM 600.
• IED 670 Connectivity Package
- This package is needed in the latest revision to engineer IED 670 products. It contains the description of the IED 670 products.
• SPA Connectivity Package
- This package is not needed for IED 670 products. It is used for products us-ing SPA to communicate with PCM 600.
5
PCM 600 Set up communication link per IED 670
The communication between the IED 670 and the PCM 600 is independent of the used IEC 61850 communication protocol within the substation. It can be seen as a second channel for communication.
When an additional link from PCM 600 to the IED 670 is requested see 'Engineering guide for IED 670 products'.
The IP address used for the Ethernet channel with IEC 61850 protocol has to be filled in by the PST tool as part of IED 670 engineering.
5.1
PCM 600 Set up communication link per Generic IEC 61850 IED
A Generic IEC 61850 IED (Gen-IED) can only communicate with the PCM 600 in the same way as the IED 670 products are when using the IEC 61850 protocol. That is only given for the dis-turbance file reading from the relays. The DRH tool is responsible for that task. For more details about the DRH tool see 'Engineering guide for IED 670 products'.
6
CCT views and windows
The CCT tool set runs under the operation system Windows 2000 or Windows XP. It is expected that the user is familiar with the handling and use of the Windows platform. In this chapter only those items are explained and shown which are specific for CCT but still based on Microsoft windows methods.
When you start CCT you will get a screen with the different panels but no contents. Once you have selected a project, you will get the possibilities to select different panels. The typical screen with an open project may look like shown in the figure below.
Figure 31: CCT: Base screen example
CCT has different panels (in PCM 600 called views). The wording panel is taken here because the CCT use it.
Possible panels:
en06000033.vsd
