Draft61850-7-3©1EC:2002 -16-57WG10-12(61850-7-3)R7.10/DraftFDIS EXAMPLE -Let A be the higher level and B the lower level.The quality from server B is invalid.If now the communication fails (questionable,oldData)between server B and client B,the quality will remain invalid and not become questionable,since the last information was not correct.Server A therefore will report the information as invalid. 6.2.8 Relation between quality identifiers Validity and source have a prioritised relation.If source is in the "process"state,then validity shall determine the quality of the origin value.If source is in the "substitute"state,then validity shall be overruled by the definition of the substituted value.This is an important feature.since substitution is used to replace invalid values with substituted values that may be used by the client like good values. EXAMPLE 1-If both questionable and substituted are set this means that the substituted value is questionable. This may happen if,in a hierarchical configuration,a substitution is performed at the lowest level and the communication fails on a higher level. EXAMPLE 2-If an invalid value is substituted,the invalid field will be cleared and the substituted field will be set to indicate the substitution. The quality identifier operatorBlocked is independent of the other quality identifiers. EXAMPLE-An oscillating input may cause the invalid field to be set.Due to the continuing changes in the value many reports are generated,loading the communication network.An operator may block the update of the input.In this case the field operatorBlocked will also be set. An example for the interaction between the quality identifiers and the impact of multiple client server relation is shown in Figure 3.In this example it is assumed that a bay level device acts as a client of the process level server and as a server to the station level client. NOTE-This is one example of a multiple client-server relationship;other multiple client-server relationships may exist,but the behaviour will not change In case A.the input is blocked,the quality of the information is marked as questionable and oldData. In Case B,a substitution is done at process level.Now,the quality of the information to the next higher level(the bay level)is marked as substituted (but good). In case C.the communication between process and bay level fails.Between Bay level and station level the information is still marked as substituted.In addition,questionable and oldData is set to indicate that the (substituted)information may be old. In case D,a new substitution is made at bay level.Now the quality of the information to the next higher level is marked as substituted (and good)and is independent from the first substitution
Draft 61850-7-3 IEC:2002 – 16 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS EXAMPLE – Let A be the higher level and B the lower level. The quality from server B is invalid. If now the communication fails (questionable, oldData) between server B and client B, the quality will remain invalid and not become questionable, since the last information was not correct. Server A therefore will report the information as invalid. 6.2.8 Relation between quality identifiers Validity and source have a prioritised relation. If source is in the “process” state, then validity shall determine the quality of the origin value. If source is in the “substitute” state, then validity shall be overruled by the definition of the substituted value. This is an important feature, since substitution is used to replace invalid values with substituted values that may be used by the client like good values. EXAMPLE 1 – If both questionable and substituted are set this means that the substituted value is questionable. This may happen if, in a hierarchical configuration, a substitution is performed at the lowest level and the communication fails on a higher level. EXAMPLE 2 – If an invalid value is substituted, the invalid field will be cleared and the substituted field will be set to indicate the substitution. The quality identifier operatorBlocked is independent of the other quality identifiers. EXAMPLE – An oscillating input may cause the invalid field to be set. Due to the continuing changes in the value many reports are generated, loading the communication network. An operator may block the update of the input. In this case the field operatorBlocked will also be set. An example for the interaction between the quality identifiers and the impact of multiple client – server relation is shown in Figure 3. In this example it is assumed that a bay level device acts as a client of the process level server and as a server to the station level client. NOTE – This is one example of a multiple client – server relationship; other multiple client - server relationships may exist, but the behaviour will not change. In case A, the input is blocked, the quality of the information is marked as questionable and oldData. In Case B, a substitution is done at process level. Now, the quality of the information to the next higher level (the bay level) is marked as substituted (but good). In case C, the communication between process and bay level fails. Between Bay level and station level the information is still marked as substituted. In addition, questionable and oldData is set to indicate that the (substituted) information may be old. In case D, a new substitution is made at bay level. Now the quality of the information to the next higher level is marked as substituted (and good) and is independent from the first substitution
Draft61850-7-3©1EC:2002 -17-57WG10-12(61850-7-3)R7.10/DraftFDIS
Draft 61850-7-3 IEC:2002 – 17 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS
Draft61850-7-3©1EC:2002 -18-57WG10-12(61850-7-3)R7.10/DraftFDIS CaseA Case B Station CL=Client Level CL CL SE=Server validity quest substituted (oldData) Bay Se Se Level CL CL validity quest substituted (oldData) Process Se Se Level Substitution Input is blocked Input is blocked Case C Case D Station Level CL CL substituted. substituted validity quest (oldData) Bay Se Se) Substitution Level CL Communication failure failure Process Se Se Level Substitution Substitution Input is blocked Input is blocked Figure 3-Interaction of substitution and validity
Draft 61850-7-3 IEC:2002 – 18 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS Input is blocked validity = quest (oldData) validity = quest (oldData) Input is blocked Substitution Station Level Bay Level Process Level Communication failure substituted, validity = quest (oldData) Input is blocked Substitution Communication failure substituted Substitution Input is blocked Substitution substituted substituted Station Level Bay Level Process Level Case A Case B Case C Case D CL Se CL Se CL Se CL Se CL Se CL Se CL Se CL Se CL = Client SE = Server Figure 3 – Interaction of substitution and validity
Draft61850-7-3©1EC:2002 -19-57WG10-12(61850-7-3)R7.10/DraftFDIS 6.3 Analogue value Analogue value type shall be as defined in Table 2. Table 2-Analogue value AnalogueValue Type Definition Attribute Name Attribute Type Value Value Range M/O/C INT32 integer value GC 1 FLOAT32 floating point value GC1 Analogue values may be represented as a basic data type INTEGER (attribute i)or as FLOATING POINT (attribute f).At least one of the attributes shall be used.If both i and f exist,the application has to insure that both values remain consistent.The latest value set by the communication service shall be used to update the other value.As an example,if xxx.f is written,the application shall update xxx.i accordingly. i:The value of i shall be an integer representation of the measured value.The formula to convert between i and f shall be: f*10umits muluplier =(i scaleFactor)+offset It shall be true within acceptable error when i,scaleFactor,offset and f are all present. f:The value of f shall be the FLOATING POINT representation of the measured value.f shall represent the technological value in SI units,see Annex A. NOTE -The reason for both INTEGER and FLOATING POINT representation is so that IEDs without FLOATING POINT capabilities shall be enabled to support analogue values.In this case the scaleFactor and offset may be exchanged offline between clients and servers. 6.4 Configuration of analogue value Configuration of analogue value type shall be as defined in Table 3. Table 3-Configuration of analogue value ScaledValueConfig Type Definition Attribute Name Attribute Type Value Value Range M/O/C scaleFactor FLOAT32 M offset FLOAT32 M This data attribute type shall be used to configure the INTEGER value representation of the analogue value.The formula for conversion between integer and floating point value is given in clause 6.3. scaleFactor:The value of scaleFactor shall be the scaling factor. offset:The value of offset shall be the offset
Draft 61850-7-3 IEC:2002 – 19 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS 6.3 Analogue value Analogue value type shall be as defined in Table 2. Table 2 – Analogue value AnalogueValue Type Definition Attribute Name Attribute Type Value / Value Range M/O/C i INT32 integer value GC_1 f FLOAT32 floating point value GC_1 Analogue values may be represented as a basic data type INTEGER (attribute i) or as FLOATING POINT (attribute f). At least one of the attributes shall be used. If both i and f exist, the application has to insure that both values remain consistent. The latest value set by the communication service shall be used to update the other value. As an example, if xxx.f is written, the application shall update xxx.i accordingly. i: The value of i shall be an integer representation of the measured value. The formula to convert between i and f shall be: f i scaleFactor offset units multiplier ∗10 = ( ∗ ) + . It shall be true within acceptable error when i, scaleFactor, offset and f are all present. f: The value of f shall be the FLOATING POINT representation of the measured value. f shall represent the technological value in SI units, see Annex A. NOTE – The reason for both INTEGER and FLOATING POINT representation is so that IEDs without FLOATING POINT capabilities shall be enabled to support analogue values. In this case the scaleFactor and offset may be exchanged offline between clients and servers. 6.4 Configuration of analogue value Configuration of analogue value type shall be as defined in Table 3. Table 3 – Configuration of analogue value ScaledValueConfig Type Definition Attribute Name Attribute Type Value / Value Range M/O/C scaleFactor FLOAT32 M offset FLOAT32 M This data attribute type shall be used to configure the INTEGER value representation of the analogue value. The formula for conversion between integer and floating point value is given in clause 6.3. scaleFactor: The value of scaleFactor shall be the scaling factor. offset: The value of offset shall be the offset
Draft61850-7-3©1EC:2002 -20-57WG10-12(61850-7-3)R7.10/DraftFDIS 6.5 Range configuration Range configuration type is used to configure the limits that define the range of a measured value and shall be as defined in Table 4. Table 4-Range Configuration RangeConfig Type Definition Attribute Name Attribute Type Value Value Range M/O/C hhLim AnalogueValue M hLim AnalogueValue M ILim AnalogueValue M IlLim AnalogueValue M min AnalogueValue M max AnalogueValue M hhLim,hLim,ILim,IlLim:These attributes shall be the configuration parameters used in the context with the range attribute as defined in clause 7.9.2. min:The min (minimum)attribute shall represent the minimum process measurement for which values of i or f are considered within process limits.If the value is lower,q shall be set accordingly(validity questionable,detailQual outOfRange). max:The max(maximum)attribute shall represent the maximum process measurement for which values of i or f are considered within process limits.If the value is higher,q shall be set accordingly (validity questionable,detailQual outOfRange). 6.6 Step position with transient indication Step position with transient indication type is e.g.used step controlled transformers and shall be as defined in Table 5. Table 5-Step position with transient indication ValWithTrans Type Definition Attribute Name Attribute Type Value Value Range M/O/C posVal INT8 -64.63 M transInd BOOLEAN 0 The posVal shall contain the step position,the transInd shall indicate that the equipment is in a transient state. 6.7 Pulse configuration Pulse configuration type is used to configure the output pulse generated with a command and shall be as defined in Table 6 Table 6-Pulse configuration PulseConfig Type Definition Attribute Name Attribute Type Value Value Range M/O/C cmdQual ENUMERATED pulse persistent M onDur INT32U M offDur INT32U M numPls INT32U M
Draft 61850-7-3 IEC:2002 – 20 – 57/WG10-12(61850-7-3)R7.10/DraftFDIS 6.5 Range configuration Range configuration type is used to configure the limits that define the range of a measured value and shall be as defined in Table 4. Table 4 – Range Configuration RangeConfig Type Definition Attribute Name Attribute Type Value / Value Range M/O/C hhLim AnalogueValue M hLim AnalogueValue M lLim AnalogueValue M llLim AnalogueValue M min AnalogueValue M max AnalogueValue M hhLim, hLim, lLim, llLim: These attributes shall be the configuration parameters used in the context with the range attribute as defined in clause 7.9.2. min: The min (minimum) attribute shall represent the minimum process measurement for which values of i or f are considered within process limits. If the value is lower, q shall be set accordingly (validity = questionable, detailQual = outOfRange). max: The max (maximum) attribute shall represent the maximum process measurement for which values of i or f are considered within process limits. If the value is higher, q shall be set accordingly (validity = questionable, detailQual = outOfRange). 6.6 Step position with transient indication Step position with transient indication type is e.g. used step controlled transformers and shall be as defined in Table 5. Table 5 – Step position with transient indication ValWithTrans Type Definition Attribute Name Attribute Type Value / Value Range M/O/C posVal INT8 -64 … 63 M transInd BOOLEAN O The posVal shall contain the step position, the transInd shall indicate that the equipment is in a transient state. 6.7 Pulse configuration Pulse configuration type is used to configure the output pulse generated with a command and shall be as defined in Table 6. Table 6 – Pulse configuration PulseConfig Type Definition Attribute Name Attribute Type Value / Value Range M/O/C cmdQual ENUMERATED pulse | persistent M onDur INT32U M offDur INT32U M numPls INT32U M