Draft61850-7-1©1EC:2002 -26-57WG10-12(61850-7-1)R2-02/Draft FDIS LN Reference Logical node Data DATA Reference XCBR1 XCBR1 DA Reference Data-Attribute XCBR1.Pos ctlVal -- XCBR1.Pos.ctlVal operTim control XCBR1.Pos.operTim origin XCBR1.Pos.oriqin ctlNum XCBR1.Pos.ctINum stVal XCBR1.Pos.stVal 9 XCBR1.Pos.q --t status XCBR1.Pos.t --stSeld XCBR1.Pos.stSeld ---subEna XCBR1.Pos.subEna subVal XCBR1.Pos.subVal substitution subQ XCBR1.Pos.subQ subID XCBR1.Pos.subID pulseConfig XCBR1.Pos.pulseConfig ctlModel XCBR1.Pos.ctlModel sboTimeout XCBR1.Pos.sboTimeout sboClass configuration, XCBR1.Pos.sboClass d description, XCBR1.Pos.d dataNs and extension XCBR1.Pos.dataNs cdcNs XCBR1.Pos.cdcNs 白一 Mode Figure 10-XCBR1 information depicted as a tree XCBR1 is the root at the level of logical nodes.The object reference XCBR1 references the complete tree below.The XCBR1 contains data,e.g.,Pos and Mode.The data Pos (position) is precisely defined in IEC 61850-7-4(see excerpt of the description): Description of data Data Name Semantic This Data is accessed when performing a switch command or to verify the switch status or po- Pos sition.When this Data is also used for a hand-operated switch,the (optional)Ctlval attribute in Part IEC 61850-7-3 does not exist. The content of the position is a list of some 20 data attributes.The attributes are derived from the common data class DPC(double point control).The data attributes defined in the DPC are partly mandatory and others are optional.Only those data attributes are inherited by a data object that are required for a specific application.For example,if the position does not require the support of substitution then the data attributes subEna,subVal,subQ,and subID are not required in the data object position. The information exchange services that access the data attributes make use of the hierarchi- cal tree.The controllable data attribute is defined with XCBR1.Pos.ctlVal.Controlling the cir- cuit breaker operates on exactly that data attribute.The status information could be refer- enced as a member (XCBR1.Pos.stVal)of a data set named "AlarmXCBR".The data set could be referenced by a reporting control block named "Alarm".The report control block could be configured to send a report to a specific computer each time a circuit breaker changes its state(from open to close or from close to open). Version Draft FDIS R2-02 2002-09-30:(08:00)
Draft 61850-7-1 IEC:2002 – 26 – 57/WG10-12(61850-7-1)R2-02 /Draft FDIS Version Draft FDIS R2-02 2002-09-30 : (08:00) substitution status XCBR1 XCBR1.Pos XCBR1.Pos.ctlVal XCBR1.Pos.operTim XCBR1.Pos.origin XCBR1.Pos.ctlNum XCBR1.Pos.stVal XCBR1.Pos.q XCBR1.Pos.t XCBR1.Pos.stSeld XCBR1.Pos.subEna XCBR1.Pos.subVal XCBR1.Pos.subQ XCBR1.Pos.subID XCBR1.Pos.pulseConfig XCBR1.Pos.ctlModel XCBR1.Pos.sboTimeout XCBR1.Pos.sboClass XCBR1.Pos.d XCBR1.Pos.dataNs XCBR1.Pos.cdcNs Pos ctlVal operTim origin ctlNum stVal q t stSeld subEna subVal subQ subID pulseConfig ctlModel sboTimeout sboClass d dataNs cdcNs Mode XCBR1 control configuration, description, and extension Logical node Data-Attribute Data LN Reference DATA Reference DA Reference Figure 10 – XCBR1 information depicted as a tree XCBR1 is the root at the level of logical nodes. The object reference XCBR1 references the complete tree below. The XCBR1 contains data, e.g., Pos and Mode. The data Pos (position) is precisely defined in IEC 61850-7-4 (see excerpt of the description): Description of data Data Name Semantic ... ... Pos This Data is accessed when performing a switch command or to verify the switch status or position. When this Data is also used for a hand-operated switch, the (optional) CtlVal attribute in Part IEC 61850-7-3 does not exist. ... ... The content of the position is a list of some 20 data attributes. The attributes are derived from the common data class DPC (double point control). The data attributes defined in the DPC are partly mandatory and others are optional. Only those data attributes are inherited by a data object that are required for a specific application. For example, if the position does not require the support of substitution then the data attributes subEna, subVal, subQ, and subID are not required in the data object position. The information exchange services that access the data attributes make use of the hierarchical tree. The controllable data attribute is defined with XCBR1.Pos.ctlVal. Controlling the circuit breaker operates on exactly that data attribute. The status information could be referenced as a member (XCBR1.Pos.stVal) of a data set named “AlarmXCBR”. The data set could be referenced by a reporting control block named “Alarm”. The report control block could be configured to send a report to a specific computer each time a circuit breaker changes its state (from open to close or from close to open)
Draft61850-7-1©1EC:2002 -27-57WG10-12(61850-7-1)R2-02/Draft FDIS 6.3 Example of an IED composition Figure 11 shows examples of different logical nodes composed into an IEDs.The logical nodes involved are PTOC (Time overcurrent protection),PDIS (Distance Protection,PTRC (Trip Conditioning)and XCBR(Circuit Breaker).Case (1)shows a protection device with two functions,which are hardwired with the circuit breaker.Case (2)shows a protection device with two functions where the trip is communicated via a trip message over a network to the circuit breaker LN.Case(3)shows the two protection functions in dedicated devices,which may operate both in a fault and where the trips are transmitted as trip messages via the net- work independently to the circuit breaker LN(XCBR). IED IED IED IED PTOC PDIS PTOC PDIS PTOC PDIS TRC PTRC PTRC PTRC Trip Trip XCBR Network wired Trip IED ED Circuit Breaker ★★ XCBR XCBR Circuit Breaker Circuit Breaker ① ② ③ Figure 11-Example of IED composition In cases (2)and(3)the IED that hosts the XCBR LNs may also be connected with the real circuit breaker via a network. The IED composition is very flexible to meet current and future needs. 6.4 Information exchange models 6.4.1 Introduction The information contained in the hierarchical models of IEC 61850-7-4 can be communicated with services defined in IEC 61850-7-2.The information exchange methods (depicted in Fig- ure 12)fall mainly into three categories: the output model. the input model.and model for the online management and selfdecription. Several services are defined for each model.The services operate on data,data attributes, and other attributes usually contained in logical nodes.The numbers in the circles are used in the next clause as references for the description. Version Draft FDIS R2-02 2002-09-30:(08:00)
Draft 61850-7-1 IEC:2002 – 27 – 57/WG10-12(61850-7-1)R2-02 /Draft FDIS Version Draft FDIS R2-02 2002-09-30 : (08:00) 6.3 Example of an IED composition Figure 11 shows examples of different logical nodes composed into an IEDs. The logical nodes involved are PTOC (Time overcurrent protection), PDIS (Distance Protection, PTRC (Trip Conditioning) and XCBR (Circuit Breaker). Case (1) shows a protection device with two functions, which are hardwired with the circuit breaker. Case (2) shows a protection device with two functions where the trip is communicated via a trip message over a network to the circuit breaker LN. Case (3) shows the two protection functions in dedicated devices, which may operate both in a fault and where the trips are transmitted as trip messages via the network independently to the circuit breaker LN (XCBR). Network PTOC PDIS PTRC XCBR IED Circuit Breaker PTOC PDIS PTRC XCBR PTOC PDIS wired Trip Trip IED IED IED PTRC PTRC XCBR IED IED Trip Circuit Breaker Circuit Breaker 1 2 3 Figure 11 – Example of IED composition In cases (2) and (3) the IED that hosts the XCBR LNs may also be connected with the real circuit breaker via a network. The IED composition is very flexible to meet current and future needs. 6.4 Information exchange models 6.4.1 Introduction The information contained in the hierarchical models of IEC 61850-7-4 can be communicated with services defined in IEC 61850-7-2. The information exchange methods (depicted in Figure 12) fall mainly into three categories: — the output model, — the input model, and — model for the online management and selfdecription. Several services are defined for each model. The services operate on data, data attributes, and other attributes usually contained in logical nodes. The numbers in the circles are used in the next clause as references for the description
Draft61850-7-1©1EC:2002 -28-57WG10-12(61850-7-1)R2-02/Draft FDIS NOTE 1 Services operate actually on instances of data.To increase the readability the term"instance of" has been omitted in most places throughout part IEC 61850-7-1. Services for the output model may have an impact on an internal process only,may produce an output signal to the process via a process interface,or may change a state value of a data attribute triggering a report. NOTE 2 The terms "input"and "output"are relative to the direction from the IED to the process (output) and from the process to the IED (input). Ouput model ① various control services Control response DATA Output (Signal) to process GOOSE/GSSE ③ local Online Management IED Online Selfdescription Reporting/Logging 6 Reportirig ⑤ various services DATA ④ Input (Signal) from process GOOSE SMV H GOOSE/SMV control Input model Figure 12-Output and Input model(principle) Several services are defined for the input model.The services communicating input informa- tion may carry information directly from the process interface or may have been computed in- side an IED. There are also several services that may be used to remotely manage the IED to some(re- stricted)degree,e.g.,to define a data set,to set a reference to a specific value,or to enable sending specific reports by a report control block.The information models (logical nodes and data classes)and the service models (e.g.,for reporting and logging)provide means to re- trieve comprehensive information about the information model and the services that operate on the information models (Selfdescription). The following description of the output and input models are conceptual only.Details on the information and services involved in the models are defined in part IEC 61850-7-4,IEC 61850-7-3,and1EC61850-7-2. 6.4.2 Output model 6.4.2.1 Control model concept The concept of the control model is depicted in Figure 13.The example is a circuit breaker logical node (XCBR)with the data attribute XCBR.Pos.ctlVal.(shown in Figure 14).Before the control service request determines the change of the position of a real device some con Version Draft FDIS R2-02 2002-09-30:(08:00)
Draft 61850-7-1 IEC:2002 – 28 – 57/WG10-12(61850-7-1)R2-02 /Draft FDIS Version Draft FDIS R2-02 2002-09-30 : (08:00) NOTE 1 Services operate actually on instances of data. To increase the readability the term “instance of” has been omitted in most places throughout part IEC 61850-7-1. Services for the output model may have an impact on an internal process only, may produce an output signal to the process via a process interface, or may change a state value of a data attribute triggering a report. NOTE 2 The terms “input” and “output” are relative to the direction from the IED to the process (output) and from the process to the IED (input). IEDIED Output (Signal) to process Online Management Online Selfdescription GOOSE / SMV Input (Signal) from process various control services Input model Ouput model DATA DATA DATA DATA Reporting Reporting 4 Reporting/Logging GOOSE/SMV control GOOSE/SMV control various services 5 7 6 1 GOOSE / GSSE local local 3 Control response 2 Figure 12 – Output and Input model (principle) Several services are defined for the input model. The services communicating input information may carry information directly from the process interface or may have been computed inside an IED. There are also several services that may be used to remotely manage the IED to some (restricted) degree, e.g., to define a data set, to set a reference to a specific value, or to enable sending specific reports by a report control block. The information models (logical nodes and data classes) and the service models (e.g., for reporting and logging) provide means to retrieve comprehensive information about the information model and the services that operate on the information models (Selfdescription). The following description of the output and input models are conceptual only. Details on the information and services involved in the models are defined in part IEC 61850-7-4, IEC 61850-7-3, and IEC 61850-7-2. 6.4.2 Output model 6.4.2.1 Control model concept The concept of the control model is depicted in Figure 13. The example is a circuit breaker logical node (XCBR) with the data attribute XCBR.Pos.ctlVal.(shown in Figure 14). Before the control service request determines the change of the position of a real device some con
Draft61850-7-1©1EC:2002 -29-57WG10-12(61850-7-1)R2-02/Draft FDIS ditions have to be met,e.g.,the output can be generated only if the local/remote switch isis in the position "remote".The chain of certain conditions to be met are possibly: local/remote switch of the logical device(modelled as the"Loc"data of the LLNO). local/remote switch of the circuit breaker CXBR.Loc, mode information of the circuit breaker XCBR.Mod, check conditions of the device,and other attributes of the controllable date,e.g.,pulse configuration,control model,sbo class,and sbo timeout as defined in the common data class DPC(controllable double point in part IEC 61850-7-3. LLNO.Loc XCBR.Mod XCBR.Loc (local remote) XCBR.Beh (for complete LD) OFF. i BLOCKED. TEST/BL control Service Request service request ON,TEST test blocked Figure 13-Output model(step 1)(conceptual) After all conditions have been met and all checks are positive the output signal can be condi- tioned and control the real equipment(the circuit breaker-not shown). The output signal may issued over a wired interface to the circuit breaker or may be commu- nicated over a bus interface. XCBR.Pos.ctlVal Set control attributes ●ontro value attrib. Service Signal Output(Signal) Request ON Conditioning to process test blocked State Machine Control/Setpoint resp. status Input (Signal) from process Command termination 2 XCBR.Pos.stVal Figure 14-Output model(step 2)(conceptual) The state change of the real circuit breaker causes a change in the status information mod- elled with the data attribute XCBR.Pos.stVal.The status change issues a control service re- sponse.A command termination completes the control transaction. Version Draft FDIS R2-02 2002-09-30:(08:00)
Draft 61850-7-1 IEC:2002 – 29 – 57/WG10-12(61850-7-1)R2-02 /Draft FDIS Version Draft FDIS R2-02 2002-09-30 : (08:00) ditions have to be met, e.g., the output can be generated only if the local/remote switch is is in the position “remote”. The chain of certain conditions to be met are possibly: – local/remote switch of the logical device (modelled as the “Loc” data of the LLN0), – local/remote switch of the circuit breaker CXBR.Loc, – mode information of the circuit breaker XCBR.Mod, – check conditions of the device, and – other attributes of the controllable date, e.g., pulse configuration, control model, sbo class, and sbo timeout as defined in the common data class DPC (controllable double point in part IEC 61850-7-3. control service request local remote local remote LLN0.Loc (local / remote) (for complete LD) XCBR.Loc OFF, BLOCKED, TEST/BL. ON, TEST XCBR.Mod XCBR.Beh Service Request test 1 ... blocked Figure 13 – Output model (step 1) (conceptual) After all conditions have been met and all checks are positive the output signal can be conditioned and control the real equipment (the circuit breaker – not shown). The output signal may issued over a wired interface to the circuit breaker or may be communicated over a bus interface. Service Request test blocked State Machine Check conditions Signal Conditioning value Output (Signal) to process Input (Signal) from process Control/Setpoint resp. Command termination 2 ON OFF XCBR.Pos.ctlVal Control attrib. Set control attributes status XCBR.Pos.stVal Figure 14 – Output model (step 2) (conceptual) The state change of the real circuit breaker causes a change in the status information modelled with the data attribute XCBR.Pos.stVal. The status change issues a control service response. A command termination completes the control transaction
Draft61850-7-1©1EC:2002 -30-57WG10-12(61850-7-1)R2-02/Draft FDIS 6.4.2.2 GSE model concept The generic substation event(GSE-GOOSE and GSSE)provides the peer-to-peer informa- tion exchange between the input data values of one IED to the output data of many other IEDs(multicast).The GOOSE and GSSE messages received by an IED are used to compute data values to be used for output or other internal purposes. NOTE 1 The GOOSE and GSSE data values are defined in the input model described in 6.4.3. GSE Handling local GOOSE Values Values Output(Signal) ③ Test Reliability Test Application to process Processing Detection ConfigRev Quality GSSE RXD Reset Figure 15-GSE output model(conceptual) The condition to be met and the checks to run before the values are used as output signals are outside the scope of IEC 61850. NOTE 2 Many GOOSE and GSSE messages may be transmitted in certain cases,e.g.,fault detected by a protection relay.A SCSM usually filters these messages at the data link layer to prevent flooding the IEDs. 6.4.2.3 Attributes of data and control blocks Many data attributes of the hierarchical information model can be set with a Set-service,e.g.. SetDataValues and SetDataSetValues.Setting the values of data attributes is usually con- strained by the application only. The various control blocks,e.g.,the setting group control block(SGCB),the buffered report control block(BRCB)and log control block(LCB),have control block attributes that can usu- ally be set to a specific value.The services to set these attributes are defined with the control blocks in part IEC 61850-7-2.Setting the values of the control block attributes is constrained by the state machine of the corresponding control block. The control blocks behave depending on the values of the attributes set.The values may also be configured using the SCL file or by other local means. All control block attributes can be read by another IED 6.4.2.4 Settings data and setting group control block A special treatment of output data values is required for settings data contained in several logical nodes as defined in part IEC 61850-7-4,e.g.,the settings for the voltage controlled overcurrent protection logical node PVOC(see Figure 16).The settings data (e.g.AVCrv. TmACrv,TmMult,...)have as many values as setting groups are defined.Each setting group has a consistent set of values. Version Draft FDIS R2-02 2002-09-30:(08:00)
Draft 61850-7-1 IEC:2002 – 30 – 57/WG10-12(61850-7-1)R2-02 /Draft FDIS Version Draft FDIS R2-02 2002-09-30 : (08:00) 6.4.2.2 GSE model concept The generic substation event (GSE – GOOSE and GSSE) provides the peer-to-peer information exchange between the input data values of one IED to the output data of many other IEDs (multicast). The GOOSE and GSSE messages received by an IED are used to compute data values to be used for output or other internal purposes. NOTE 1 The GOOSE and GSSE data values are defined in the input model described in 6.4.3. GSSE GOOSE Values Test ConfigRev GSE Handling RXD Values Test Quality Reliability Detection Reset Application Application Output (Signal) to process Processing local remote local 3 Figure 15 – GSE output model (conceptual) The condition to be met and the checks to run before the values are used as output signals are outside the scope of IEC 61850. NOTE 2 Many GOOSE and GSSE messages may be transmitted in certain cases, e.g., fault detected by a protection relay. A SCSM usually filters these messages at the data link layer to prevent flooding the IEDs. 6.4.2.3 Attributes of data and control blocks Many data attributes of the hierarchical information model can be set with a Set-service, e.g., SetDataValues and SetDataSetValues. Setting the values of data attributes is usually constrained by the application only. The various control blocks, e.g., the setting group control block (SGCB), the buffered report control block (BRCB) and log control block (LCB), have control block attributes that can usually be set to a specific value. The services to set these attributes are defined with the control blocks in part IEC 61850-7-2. Setting the values of the control block attributes is constrained by the state machine of the corresponding control block. The control blocks behave depending on the values of the attributes set. The values may also be configured using the SCL file or by other local means. All control block attributes can be read by another IED. 6.4.2.4 Settings data and setting group control block A special treatment of output data values is required for settings data contained in several logical nodes as defined in part IEC 61850-7-4, e.g., the settings for the voltage controlled overcurrent protection logical node PVOC (see Figure 16). The settings data (e.g. AVCrv, TmACrv, TmMult, ...) have as many values as setting groups are defined. Each setting group has a consistent set of values