Draft61850-7-3©1EC:2002 -11-57WG10-12(61850-7-3)R7.10/DraftFDIS 5 Conditions for attribute inclusion This clause lists general conditions that specify the presence of an attribute. Abbreviation Condition M Attribute is mandatory 0 Attribute is optional PICS_SUBST Attribute is mandatory,if substitution is supported(For substitution,see IEC 61850-7-2) GC_1 At least one of the attributes shall be present for a given instance of DATA GC_2(n) All or none of the data attributes belonging to the same group(n)shall be present for a given instance of DATA. GC_CON A configuration data attribute shall only be present,if the (optional)specific data attributes to which this configuration relates,is present as well AC EXT The attribute shall be present,if the common data class is extended with private attributes. Otherwise,the attribute shall not be present. AC_LNO_M Applies to IdNs in CDC LPL only,IdNs shall always be present if the data object belongs to logical node LLNO,otherwise not AC_DLD_M Applies to InNs in CDC LPL only.InNs shall be present if the name space of the LN deviates from the name space defined in ldNs AC_DLN_M Applies to dataNs in all CDCs,dataNs shall be present if the name space of the DATA deviates from the name space defined in ldNs/InNs. AC_DLNDA_M The attribute shall be present,if the name space of the CDC deviates from either the name space defined in IdNs/InNs or the name space defined in dataNs,or both. AC_SCAV That configuration data attribute shall be present for a given data object,if i and f of the analogue value of the data attribute to which this configuration attribute relates are both present.It shall be optional,if only i is present and it is not required,if only f is present. NOTE-If only i is present in a device without floating point capabilities,the configuration parameter may be exchanged offline. AC_ST The attribute is mandatory,if the controllable status class supports status information AC_CO_M The attribute is mandatory,if the controllable status class supports control AC_CO_O The attribute is optional,if the controllable status class supports control AC_SG_M The attribute is mandatory,if setting group is supported AC_SG_O The attribute is optional,if setting group is supported AC_NSG_M The attribute is mandatory,if setting group is not supported AC_NSG_O The attribute is optional,if setting group is not supported AC_RMS_M The attribute is mandatory when the harmonics reference type is rms
Draft 61850-7-3 IEC:2002 – 11 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS 5 Conditions for attribute inclusion This clause lists general conditions that specify the presence of an attribute. Abbreviation Condition M Attribute is mandatory O Attribute is optional PICS_SUBST Attribute is mandatory, if substitution is supported (For substitution, see IEC 61850-7-2) GC_1 At least one of the attributes shall be present for a given instance of DATA GC_2 (n) All or none of the data attributes belonging to the same group (n) shall be present for a given instance of DATA. GC_CON A configuration data attribute shall only be present, if the (optional) specific data attributes to which this configuration relates, is present as well AC_EXT The attribute shall be present, if the common data class is extended with private attributes. Otherwise, the attribute shall not be present. AC_LN0_M Applies to ldNs in CDC LPL only, ldNs shall always be present if the data object belongs to logical node LLN0, otherwise not AC_DLD_M Applies to lnNs in CDC LPL only, lnNs shall be present if the name space of the LN deviates from the name space defined in ldNs AC_DLN_M Applies to dataNs in all CDCs, dataNs shall be present if the name space of the DATA deviates from the name space defined in ldNs/lnNs. AC_DLNDA_M The attribute shall be present, if the name space of the CDC deviates from either the name space defined in ldNs/lnNs or the name space defined in dataNs, or both. AC_SCAV That configuration data attribute shall be present for a given data object, if i and f of the analogue value of the data attribute to which this configuration attribute relates are both present. It shall be optional, if only i is present and it is not required, if only f is present. NOTE – If only i is present in a device without floating point capabilities, the configuration parameter may be exchanged offline. AC_ST The attribute is mandatory, if the controllable status class supports status information AC_CO_M The attribute is mandatory, if the controllable status class supports control AC_CO_O The attribute is optional, if the controllable status class supports control AC_SG_M The attribute is mandatory, if setting group is supported AC_SG_O The attribute is optional, if setting group is supported AC_NSG_M The attribute is mandatory, if setting group is not supported AC_NSG_O The attribute is optional, if setting group is not supported AC_RMS_M The attribute is mandatory when the harmonics reference type is rms
Draft61850-7-3©1EC:2002 -12-57WG10-12(61850-7-3)R7.10/DraftFDIS 6 Common data attribute types 6.1 General Common data attribute types are defined for the use in common data classes(CDC)in clause IEC part 61850-7-1 provides an overview of all part 7 documents (61850-7-2,7-3,and-7-4). Part 61850-7-1 also describes the basic notation used in IEC 61850-7-3 and the description of the relations between these documents (61850-7-2,7-3,and-7-4). NOTE-The common data attribute type"TimeStamp"is specified in IEC 61850-7-2. 6.2 Quality 6.2.1 Overview Quality type shall be as defined in Table 1 Table 1-Quality Quality Type Definition Attribute Name Attribute Type Value Value Range M/O/C PACKED LIST validity CODED ENUM good invalid reserved I questionable M detailQual PACKED LIST M overflow BOOLEAN M outOfRange BOOLEAN M badReference BOOLEAN M oscillatory BOOLEAN M failure BOOLEAN M oldData BOOLEAN M inconsistent BOOLEAN inaccurate BOOLEAN M source CODED ENUM process substituted M DEFAULT process test BOOLEAN DEFAULT FALSE M operatorBlocked BOOLEAN DEFAULT FALSE M NOTE-The DEFAULT value shall be applied,if the functionality of the related attribute is not supported.The mapping may specify to exclude the attribute from the message,if it is not supported or if the DEFAULT value applies. Quality shall be an attribute that contains information on the quality of the information from the server.The different quality identifiers are not independent.Basically,there are the following quality identifiers: ·validity ·source ·test operatorBlocked NOTE-The quality,as used within the scope of 61850,is related to the quality of the information from the server There may be a requirement that the client uses additional quality information within its local database.This is a local issue and not part of the scope of IEC 61850.However,the quality of a client may have an impact on the quality supplied by a server of a client-server relationship at a higher level(see Fig 5)
Draft 61850-7-3 IEC:2002 – 12 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS 6 Common data attribute types 6.1 General Common data attribute types are defined for the use in common data classes (CDC) in clause 7. IEC part 61850-7-1 provides an overview of all part 7 documents (61850-7-2, 7-3, and -7-4). Part 61850-7-1 also describes the basic notation used in IEC 61850-7-3 and the description of the relations between these documents (61850-7-2, 7-3, and -7-4). NOTE – The common data attribute type "TimeStamp" is specified in IEC 61850-7-2. 6.2 Quality 6.2.1 Overview Quality type shall be as defined in Table 1 Table 1 – Quality Quality Type Definition Attribute Name Attribute Type Value / Value Range M/O/C PACKED LIST validity CODED ENUM good | invalid | reserved | questionable M detailQual PACKED LIST M overflow BOOLEAN M outOfRange BOOLEAN M badReference BOOLEAN M oscillatory BOOLEAN M failure BOOLEAN M oldData BOOLEAN M inconsistent BOOLEAN M inaccurate BOOLEAN M source CODED ENUM process | substituted DEFAULT process M test BOOLEAN DEFAULT FALSE M operatorBlocked BOOLEAN DEFAULT FALSE M NOTE – The DEFAULT value shall be applied, if the functionality of the related attribute is not supported. The mapping may specify to exclude the attribute from the message, if it is not supported or if the DEFAULT value applies. Quality shall be an attribute that contains information on the quality of the information from the server. The different quality identifiers are not independent. Basically, there are the following quality identifiers: • validity • source • test • operatorBlocked NOTE – The quality, as used within the scope of 61850, is related to the quality of the information from the server. There may be a requirement that the client uses additional quality information within its local database. This is a local issue and not part of the scope of IEC 61850. However, the quality of a client may have an impact on the quality supplied by a server of a client – server relationship at a higher level (see Fig 5)
Draft61850-7-3©1EC:2002 -13-57WG10-12(61850-7-3)R7.10/DraftFDIS 6.2.2 validity Validity shall be good,questionable or invalid. good:The value shall be marked good if no abnormal condition of the acquisition function or the information source is detected. invalid:The value shall be marked invalid when an abnormal condition of the acquisition function or the information source (missing or non-operating updating devices)is detected. The value shall not be defined under this condition.The mark invalid shall be used to indicate to the client that the value may be incorrect and shall not be used. EXAMPLE-if an input unit detects an oscillation of one input it will mark the related information as invalid. questionable:The value shall be marked questionable if a supervision function detects an abnormal behaviour,however the value could still be valid.The client shall be responsible for determining whether or not values marked "questionable"should be used. 6.2.3 Detail quality The reason for an invalid or questionable value of an attribute may be specified in more detail with further quality identifiers.If one of these identifiers is set then validity shall be set to invalid or questionable.The following table shows the relation of the detailed quality identifiers with invalid or questionable quality. Invalid Questionable DetailQual Overflow X Out of Range X Bad Reference X X Oscillatory X X Failure X Old data X Inconsistent X Inaccurate X overflow:This identifier shall indicate a quality issue that the attribute to which the quality has been associated is beyond the capability of being represented properly (used for measurand information only). EXAMPLE-A measured value may exceed the range that may be represented by the selected data type,e.g.the data type is a 16-bit unsigned integer and the value exceeds 65535. outOfRange:This identifier shall indicate a quality issue that the attribute to which the quality has been associated is beyond a predefined range of values.The server shall decide if validity shall be set to invalid or questionable(used for measurand information only). EXAMPLE-A measured value may exceed a predefined range,however the selected data type can still represent the value,e.g.the data type is a 16-bit unsigned integer,the predefined range is o to 40000,if the value is between 40001 and 65535 it is considered to be out of range. badReference:This identifier shall indicate that the value may not be a correct value due to a reference being out of calibration.The server shall decide if validity shall be set to invalid or questionable (used for measurand information and binary counter information only). oscillatory:To prevent overloading of event driven communication channels it is desirable to detect and suppress oscillating(fast changing)binary inputs.If a signal changes in a defined time(tosc)twice in the same direction(from 0 to 1 or from 1 to 0)then it shall be defined as an
Draft 61850-7-3 IEC:2002 – 13 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS 6.2.2 validity Validity shall be good, questionable or invalid. good: The value shall be marked good if no abnormal condition of the acquisition function or the information source is detected. invalid: The value shall be marked invalid when an abnormal condition of the acquisition function or the information source (missing or non-operating updating devices) is detected. The value shall not be defined under this condition. The mark invalid shall be used to indicate to the client that the value may be incorrect and shall not be used. EXAMPLE – if an input unit detects an oscillation of one input it will mark the related information as invalid. questionable: The value shall be marked questionable if a supervision function detects an abnormal behaviour, however the value could still be valid. The client shall be responsible for determining whether or not values marked "questionable" should be used. 6.2.3 Detail quality The reason for an invalid or questionable value of an attribute may be specified in more detail with further quality identifiers. If one of these identifiers is set then validity shall be set to invalid or questionable. The following table shows the relation of the detailed quality identifiers with invalid or questionable quality. DetailQual Invalid Questionable Overflow X Out of Range X X Bad Reference X X Oscillatory X X Failure X Old data X Inconsistent X Inaccurate X overflow: This identifier shall indicate a quality issue that the attribute to which the quality has been associated is beyond the capability of being represented properly (used for measurand information only). EXAMPLE - A measured value may exceed the range that may be represented by the selected data type, e.g. the data type is a 16-bit unsigned integer and the value exceeds 65535. outOfRange: This identifier shall indicate a quality issue that the attribute to which the quality has been associated is beyond a predefined range of values. The server shall decide if validity shall be set to invalid or questionable (used for measurand information only). EXAMPLE - A measured value may exceed a predefined range, however the selected data type can still represent the value, e.g. the data type is a 16-bit unsigned integer, the predefined range is 0 to 40000, if the value is between 40001 and 65535 it is considered to be out of range. badReference: This identifier shall indicate that the value may not be a correct value due to a reference being out of calibration. The server shall decide if validity shall be set to invalid or questionable (used for measurand information and binary counter information only). oscillatory: To prevent overloading of event driven communication channels it is desirable to detect and suppress oscillating (fast changing) binary inputs. If a signal changes in a defined time (tosc) twice in the same direction (from 0 to 1 or from 1 to 0) then it shall be defined as an
Draft61850-7-3©1EC:2002 -14-57WG10-12(61850-7-3)R7.10/DraftFD1S oscillation and the detail quality identifier"oscillatory"shall be set.If a configured numbers of transient changes is detected,they shall be suppressed.In this time the validity status "questionable"shall be set.If the signal is still in the oscillating state after the defined number of changes,the value shall be left in the state it was in when the oscillatory flag was set.In this case the validity status "questionable"shall be reset and "invalid"shall be set as long as the signal is oscillating.If the configuration is such that all transient changes should be suppressed,the validity status "invalid"shall be set immediately in addition to the detail quality identifier "oscillatory"(used for status information only) failure:This identifier shall indicate that a supervision function has detected an internal or external failure. oldData:A value shall be oldData if an update is not made during a specific time interval.The value may be an old value that may have changed in the meantime.This specific time interval may be defined by an allowed-age attribute. NOTE -"fail silent"errors,where the equipment stops sending data will cause a oldData condition.In this case, the last received information was correct. inconsistent:This identifier shall indicate that an evaluation function has detected an inconsistency. inaccurate:This identifier shall indicate that the value does not meet the stated accuracy of the source. EXAMPLE-The measured value of Power Factor may be noisy (inaccurate)when the current is very small. 6.2.4 Source Source shall give information related to the origin of a value.The value may be acquired from the process or be a substituted value. process:The value is provided by an input function from the process 1/O or is calculated from some application function. substituted:The value is provided by input of an operator or by an automatic source. NOTE 1-Substitution may be done locally or via the communication services.In the second case,specific attributes with a FC SV are used. NOTE 2-There are various means to clear a substitution.As an example,a substitution that was done following an invalid condition may be cleared automatically if the invalid condition is cleared.However,this is a local issue and therefore not in the scope of this standard. 6.2.5 Test Test shall be an additional identifier that may be used to classify a value being a test value and not to be used for operational purpose.The processing of the test quality in the client shall be a local issue.The bit shall be completely independent from the other bits within the quality descriptor. The test identifier should normally be propagated through all hierarchical levels. 6.2.6 Blocked by operator operatorBlocked:This identifier shall be set if further update of the value has been blocked by an operator.The value shall be the information that was acquired before blocking.If this identifier is set then the identifier oldData of detailQual shall also be set
Draft 61850-7-3 IEC:2002 – 14 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS oscillation and the detail quality identifier “oscillatory” shall be set. If a configured numbers of transient changes is detected, they shall be suppressed. In this time the validity status "questionable” shall be set. If the signal is still in the oscillating state after the defined number of changes, the value shall be left in the state it was in when the oscillatory flag was set. In this case the validity status "questionable” shall be reset and “invalid” shall be set as long as the signal is oscillating. If the configuration is such that all transient changes should be suppressed, the validity status “invalid” shall be set immediately in addition to the detail quality identifier “oscillatory” (used for status information only). failure: This identifier shall indicate that a supervision function has detected an internal or external failure. oldData: A value shall be oldData if an update is not made during a specific time interval. The value may be an old value that may have changed in the meantime. This specific time interval may be defined by an allowed-age attribute. NOTE – "fail silent" errors, where the equipment stops sending data will cause a oldData condition. In this case, the last received information was correct. inconsistent: This identifier shall indicate that an evaluation function has detected an inconsistency. inaccurate: This identifier shall indicate that the value does not meet the stated accuracy of the source. EXAMPLE - The measured value of Power Factor may be noisy (inaccurate) when the current is very small. 6.2.4 Source Source shall give information related to the origin of a value. The value may be acquired from the process or be a substituted value. process: The value is provided by an input function from the process I/O or is calculated from some application function. substituted: The value is provided by input of an operator or by an automatic source. NOTE 1 - Substitution may be done locally or via the communication services. In the second case, specific attributes with a FC SV are used. NOTE 2 - There are various means to clear a substitution. As an example, a substitution that was done following an invalid condition may be cleared automatically if the invalid condition is cleared. However, this is a local issue and therefore not in the scope of this standard. 6.2.5 Test Test shall be an additional identifier that may be used to classify a value being a test value and not to be used for operational purpose. The processing of the test quality in the client shall be a local issue. The bit shall be completely independent from the other bits within the quality descriptor. The test identifier should normally be propagated through all hierarchical levels. 6.2.6 Blocked by operator operatorBlocked: This identifier shall be set if further update of the value has been blocked by an operator. The value shall be the information that was acquired before blocking. If this identifier is set then the identifier oldData of detailQual shall also be set
Draft61850-7-3©1EC:2002 -15-57WG10-12(61850-7-3)R7.10/DraftFDIS NOTE-Both an operator as well as an automatic function may block communication updating as well as input updating.In both cases the identifier oldData of detailQual will be set.If the blocking is done by an operator then the identifier operatorBlocked is set additionally.In that case an operator activity is required to clear the condition. EXAMPLE-An operator may block the update of an input,to save the old value,if the auxiliary supply is switched off. 6.2.7 Quality in the client server context Information Source Server Input Client Communication Unit Network Invalid questionable overFlow substituted outOfRange badReference oscillatory questionable failure oldData Figure 1-Quality identifiers in a single client-server relationship The quality identifier shall reflect the quality of the information in the server,as it is supplied to the client.Figure 1 shows potential sources that may influence the quality in a single client server relationship."Information Source"is the (hardwired)connection of the process information to the system.The information may be invalid or questionable as indicated in Figure 1.Further abnormal behaviour of the information source may be detected by the input unit.In that case the input unit may keep the old data and flag it accordingly. In a multiple client-server relationship,as shown in Figure 2,information may be acquired over a communication link (with Client B).If that communication link is broken,client B will detect that error situation and qualify the information as questionable old data. Information Source Server A Input Client A Communication Unit Network Communication Client B Network questionable oldData Figure 2-Quality identifiers in a multiple client-server relationship In the multiple client-server relationship the quality of the server A shall reflect both the quality of the server B(acquired with client B)as well as its own quality.Therefore,handling of prioritisation of quality from different levels may require further specification beyond that included in this standard.For the identifier validity,the value invalid shall dominate over the value questionable.since this is the worst case.For the identifier source,the higher level of the multiple client-server relationship shall dominate over the lower level
Draft 61850-7-3 IEC:2002 – 15 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS NOTE – Both an operator as well as an automatic function may block communication updating as well as input updating. In both cases the identifier oldData of detailQual will be set. If the blocking is done by an operator then the identifier operatorBlocked is set additionally. In that case an operator activity is required to clear the condition. EXAMPLE – An operator may block the update of an input, to save the old value, if the auxiliary supply is switched off. 6.2.7 Quality in the client server context Communication Network Client Server Input Unit Information Source Invalid / questionable overFlow outOfRange badReference oscillatory failure questionable oldData substituted Figure 1 – Quality identifiers in a single client – server relationship The quality identifier shall reflect the quality of the information in the server, as it is supplied to the client. Figure 1 shows potential sources that may influence the quality in a single client – server relationship. "Information Source" is the (hardwired) connection of the process information to the system. The information may be invalid or questionable as indicated in Figure 1. Further abnormal behaviour of the information source may be detected by the input unit. In that case the input unit may keep the old data and flag it accordingly. In a multiple client - server relationship, as shown in Figure 2, information may be acquired over a communication link (with Client B). If that communication link is broken, client B will detect that error situation and qualify the information as questionable / old data. Communication Network Client A Server A Input Unit Information Source questionable oldData Client B Communication Network Figure 2 – Quality identifiers in a multiple client – server relationship In the multiple client-server relationship the quality of the server A shall reflect both the quality of the server B (acquired with client B) as well as its own quality. Therefore, handling of prioritisation of quality from different levels may require further specification beyond that included in this standard. For the identifier validity, the value invalid shall dominate over the value questionable, since this is the worst case. For the identifier source, the higher level of the multiple client – server relationship shall dominate over the lower level