CHAPTER 3: IEC 61850 COMMUNICATION MODEL IMPLEMENTATION CONFORMANCE STATEMENT (MICS)UR FAMILY – COMMUNICATIONS GUIDE 3-2933.5 Model implementation conformance statement (MICS)This model implementation conformance statement (MICS) details the information model supported by a particular URdevice, including implemented logical devices, logical nodes, data objects, and data attributes. It is the top-level IEC 61850data model. The information model also contains implemented control blocks and datasets.The information model of a UR device depends in general on the device's order code, and it can vary widely from productto product and from option to option. The complete information model for a particular UR device with a particular ordercode, as it exists with factory default settings, is embodied in the device's IED capability description (ICD) file. A device's ICDfile can be obtained from the device itself or from the EnerVista UR Setup software.This section contains an outline of the information model of the UR family of devices; the information model of a particularUR device consists of the subset of what is shown here that is relevant to that UR device.In order to contain the size of this chapter, the following repetitious data objects and data attributes are omitted from thisoutline. These are nonetheless implemented in the device.Table 3-7: Common data objects and attributesS58 SetFile YesS59 DeleteFileS60 GetFileAttributeValues YesS61 GetServerDirectory (FILE-SYSTEM) YesTime (clause 5.5)T1 Time resolution of internal clock 1 μs ≈ 2**-20 sT2 Time accuracy of internal clock SNTP, IRIG-B, PTPT3 Supported TimeStamp resolution 1 μs ≈ 2**-20 sName DescriptionBeh The data object Beh is mandatory in every logical node.The value of Beh.stVal in LLN0 of the Master logical device is test/blocked if the FlexLogic operand ANY MAJOR ERROR isOn, otherwise test/blocked if the TEST MODE FUNCTION selection is Isolated, otherwise test if the TEST MODEFUNCTION selection is Forcible, otherwise on.In all other logical nodes, the value of Beh.stVal is off if the function modeled by the logical node has a FunctionDisabled/Enabled setting and that setting is selected Disabled, otherwise is the same as the value of Beh.stVal in theMaster LLN0.NamPlt Although optional, the data object NamPlt is instantiated in every logical node except LPHD1. This data object containsin its d data attribute a natural language description of the UR element the containing logical node is modelling. It isincluded below only in the Master logical device, as there it contains several important data attributes not found in theothers.t The data attribute t (TimeStamp) is mandatory in every status, measurand and control data object, and reflects the URdevice UTC time at last value change of the status, measurand, control, or q values of the containing data object.q The data attribute q (Quality) is mandatory in every status, measurand and control data object, and reflects the qualityof the status, measurand and control values of the containing data object.q is fixed at zero in cases where the value is an internal UR device mode or status, and thus the value is known to begood, is unaffected by test mode, cannot be operator blocked and cannot be substituted.Otherwise, q is set according to the following table. Note that the value of Beh.stVal of the logical node containing theQuality data attribute is as described a few paragraphs earlier in this section.d This textual description is in every logical node. When in a NamPlt data object, the description refers to the logical node,otherwise it describes the data object it is in. These data attributes are readable via MMS services and reconfigurablevia SCL file download.dataNs The data name space is included in data objects that extend those specified by the logical node class in the standard.Where the extended data object is defined in IEC 61850 7 4, its value is "IEC 61850-7-4:2007A". Otherwise, it has thevalue "GE Multilin UR Namespace:2015A" and is defined in the GE Namespace subsection of this section. These dataattributes are readable via MMS services.Client / subscriber Server / publisher Comments