NB/T 31067-2015Communications for monitoring and control of wind power plants - Information models (English PDF)

Foreword

This document was issued on 2 April 2015 by the National Energy Administration of the PRC and takes effect on 1 September 2015.

It is a NB/T standard: recommended rather than compulsory, but it is the text a Chinese reviewer applies when assessing a submission.

It is classified under ICS 27.180, Chinese classification F11.

This standard was drafted in accordance with the rules given in GB/T 1.1-2009 Directives for standardization - Part 1: Structure and drafting of standards.

Attention is drawn to the possibility that some of the elements of this standard may be the subject of patent rights. The issuing body of this standard shall not be held responsible for identifying any or all such patent rights.

This standard is used together with NB/T 31068-2015, NB/T 31069-2015 and NB/T 31070-2015, which together form a series of standards.

IEC 61400-25 is divided into six parts: IEC 61400-25-1 Wind turbines - Part 25-1: Communications for monitoring and control of wind power plants - Overall description of principles and models; IEC 61400-25-2 Part 25-2: Information models (identically adopted as NB/T 31067-2015); IEC 61400-25-3 Part 25-3: Information exchange models (identically adopted as NB/T 31068-2015); IEC 61400-25-4 Part 25-4: Mapping to communication profile (identically adopted as NB/T 31069-2015); IEC 61400-25-5 Part 25-5: Conformance testing (identically adopted as NB/T 31070-2015); IEC 61400-25-6 Part 25-6: Logical node classes and data classes for condition monitoring.

For ease of use, the following editorial changes have been made to this standard: a) "IEC 61400-25-2:2006" has been changed to "this standard"; b) the informative summary elements of IEC 61400-25-2:2006 (including the cover, table of contents and foreword) have been deleted; c) the introduction of IEC 61400-25-2:2006 has been retained, and a national foreword has been added to this standard.

This standard was proposed by the China Electricity Council.

This standard is under the jurisdiction of the Energy Industry Wind Power Standardization Technical Committee.

Main drafting organizations of this standard: Beijing Yueneng Technology Co., Ltd., Beijing Corona Science and Technology Co., Ltd., Datang Jiaonan Wind Power Co., Ltd., Huadian Fuxin Energy Co., Ltd., China Electric Power Research Institute, Beijing Guangyao Energy Technology Co., Ltd., and Northeastern University.

Main drafters of this standard: Zhao Zigang, Zhu Zhiliang, Zhu Yongfeng, Zhang Jian, Chen Xiaoqing, E Chunliang, Feng Cheng, Li Yujun, Ji Haifeng, Huang Zhijun, Chen Jinhong, Wang Chengzhou, Qu Chunhui, Chi Yongning and Wu Jingbo.

Opinions or suggestions arising during the implementation of this standard should be fed back to the Standardization Management Center of the China Electricity Council (No. 1, Lane 2, Baiguang Road, Beijing, 100761).

Introduction

The IEC 61400-25 series defines communications for monitoring and control of wind power plants. The series has chosen a modelling approach based on abstract definitions of classes and services, so that the specifications are independent of specific protocol stacks, implementations and operating systems. The mapping of these abstract classes and services to specific communication profiles is not within the scope of this part, but is described in NB/T 31069-2015 of this series.

To achieve interoperability, all data in the information model need a strict definition with regard to syntax and semantics. The semantics of the data are mainly provided by the names assigned to the logical nodes and the data they contain, as defined in IEC 61400-25-2. The more that is defined, the easier interoperability becomes.

It should be noted that data with full semantics are only one element of interoperability. Since data and services are hosted by devices (such as intelligent electronic devices, IED), a suitable device model also requires compatible domain-specific services (see IEC 61400-25-3).

This standard specifies in detail the abstract definitions of logical device classes, logical node classes, data classes and abstract common data classes. These abstract definitions are mapped to concrete object definitions, that is, to a specific protocol.

This standard defines compatible logical node names and data names whose associated semantics are fixed.

NOTE: Performance of the IEC 61400-25 series is an application-specific characteristic. The IEC 61400-25 series does not require a particular performance level, which is outside its scope. However, there is no inherent limitation in the communication technology that prevents high-speed applications (millisecond-level response).

1 Scope

NB/T 31067-2015 is the Chinese identical adoption of IEC 61400-25-2:2006, and it defines the information models used for communication in the monitoring and control of wind power plants. It is the part of the IEC 61400-25 family that fixes what the data actually is, so that a SCADA system can talk to turbines from any manufacturer without a custom driver for each. The standard builds on the IEC 61850 modelling approach. It sets out the scope, the normative references, the terms and the abbreviations - some two hundred and twenty of them, used to compose data names - and then the general principles of the information model: logical devices, logical nodes, data objects and common data classes, and how they are named and structured. The heart of the document is the definition of the wind power plant logical nodes: the common nodes for the device and its physical properties, and the wind-specific nodes for the turbine as a whole, the rotor, the transmission, the generator, the converter, the nacelle, the yaw system, the tower, the meteorological measurement, the alarm handling and the plant-level functions. For each logical node the standard tables every data object it contains, with its common data class, its meaning and whether it is mandatory or optional. The common data classes specific to wind power follow, and the annexes give the value definitions and the mapping of statuses. Note that a few terms in the Chinese text are rendered differently from the IEC original; the IEC meaning governs.

This series of standards specifies general requirements for communication between the components of a wind power plant (such as wind turbines) and actors (such as SCADA systems). Communication internal to the individual components of the wind power plant is outside the scope.

The series applies to a communication environment supported by a client-server model and defines the following three areas, each modelled separately to ensure extensibility of the implementation: 1) the wind power plant information model; 2) the information exchange model; 3) the mapping of the information model and the information exchange model to standard communication profiles.

The wind power plant information model and the information exchange model together form an interface between client and server. As an interpretation framework for accessing wind power plant data, the information model provides the client, through the server, with uniform, component-based wind power plant data. The information exchange model reflects the complete set of functions available at the server. The series gives general applicability to access between different clients and servers from different manufacturers and suppliers.

As shown in Figure 1, the server defined by this series comprises the following aspects: information provided by wind power plant components, such as "wind turbine rotor speed" or "total power generated in a given period of time", which is modelled and can be accessed effectively; services for exchanging the modelled information values, defined in NB/T 31068-2015 of this series; and the mapping to a communication profile, providing a protocol stack for obtaining the exchanged values from the modelled information (NB/T 31069 of this series).

Figure 1 - Communication model concept: the client and the server each contain the information exchange model (get, set, report, log, control, publish, subscribe, etc.) defined in NB/T 31068-2015 and the wind power plant information model (rotor speed, stop status, total power generation, etc.) defined in NB/T 31067; the information is exchanged through the mapping to a communication profile (read, write, etc.) defined in NB/T 31069-2015. The actor (e.g. SCADA) and its application on the client side, and the wind power plant component (e.g. a wind turbine) and its application on the server side, are outside the scope.

This series only defines how information is modelled, exchanged and mapped to specific communication protocols; it does not contain recommendations on how and where to implement the communication interface, the application program interface or the implementation. However, the objective of the series is to obtain information related to a single wind power plant component (such as a wind turbine) through the corresponding logical devices.

This standard specifies in detail the information models of devices and functions related to wind power plant applications, and in particular the compatible logical node names and data names for communication between wind power plant components, including the relationships among logical devices, logical nodes and data. The names defined in this series are used to build hierarchical object references applied to communication with wind power plant components.

This standard specifies in detail the common attribute types and common data classes related to wind turbine applications, in particular the following common data classes: setpoint value; status value; alarm; command; event counting; state timing; alarm set status.

Devices implementing the information model of this standard shall select one or more logical nodes according to the application requirements.

NOTE 1: This series focuses on general, non-vendor-specific information. Information items whose vendor-specific implementations vary widely may be specified in bilateral agreements or by user groups.

NOTE 2: This standard does not provide guidance material.

2 Normative references

The following documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including all amendments) applies.

DL/T 860.71-2006 Communication networks and systems in substations - Part 7-1: Basic communication structure for substation and feeder equipment - Principles and models (IEC 61850-7-1:2003, IDT).

DL/T 860.72-2004 Communication networks and systems in substations - Part 7-2: Basic communication structure for substation and feeder equipment - Abstract communication service interface (ACSI) (IEC 61850-7-2:2003, IDT).

DL/T 860.5-2006 Communication networks and systems in substations - Part 5: Communication requirements for functions and device models (IEC 61850-5:2003, IDT).

DL/T 860.73-2004 Communication networks and systems in substations - Part 7-3: Basic communication structure for substation and feeder equipment - Common data classes (IEC 61850-7-3:2003, IDT).

DL/T 860.74-2006 Communication networks and systems in substations - Part 7-4: Basic communication structure for substation and feeder equipment - Compatible logical node classes and data classes (IEC 61850-7-4:2003, IDT).

GB/T 4880 (all parts) Codes for the representation of names of languages [ISO 639 (all parts)].

GB 3100-1993 SI units and recommendations for the use of their multiples and of certain other units (ISO 1000:1992, EQV).

GB/T 2659-2000 Codes for the representation of names of countries and regions (ISO 3166-1:1997, EQV).

RFC 2445 Internet Calendaring and Scheduling Core Object Specification (iCalendar).

3 Terms and definitions

For the purposes of this part, the terms and definitions given in Part 1 of this series and the following apply.

3.1 conditional: a common data class attribute provided by this series, where the corresponding attribute is true under certain conditions.

3.2 mandatory: content that this series requires to be defined.

3.3 optional: content that this series allows to be defined selectively.

4 Abbreviations

CDC: common data class.

DC: data class.

IED: intelligent electronic device.

LCB: log control block.

LD: logical device.

LN: logical node.

LPHD: logical node physical device information.

RCB: report control block.

SBO: select before operate.

WPP: wind power plant.

WT: wind turbine.

XML: extensible markup language.

The following abbreviations are used to build the data class names in logical nodes. For example, "RotPos" is composed of two words, "Rot" standing for rotor and "Pos" standing for position, so the compound word means "rotor position".

A: current; AC: alternating current; Ack: acknowledge; Acs: access; Act: actual value; Alm: alarm; An: analogue; Ane: anemometer; Ang: angle; Alt: altitude; At: active; Atv: valid (active); Av: average; Avl: availability; Az: azimuth.

Bec: beacon light; Bl: blade; Blk: blocked (locked); Brg: bearing; Brk: brake; Cab: cable; Calc: calculation; Ccw: counter-clockwise; Ch: characteristic; Chg: change; Chrg: charge (load); Cl: cooling; Cm: command; Cnv: converter.

Ct: counter; Ctl: control; Cw: clockwise; d: description; Dat: data; Db: deadband; DC: direct current; Dcl: DC link; Dec: decrease; Dehum: dehumidifier; Del: delta algorithm; Det: detection; Dir: direction (given in the table as instructions); Disp: displacement; Dly: daily; Dmd: demand; Drv: drive; Dn: down.

Egy: energy; Elev: elevator; Emg: emergency; En: enable (start); Ent: entry; Ety: empty (idle); Evt: event; Ex: external; Exp: expire (end); Ext: excitation; Flsh: flash; Flt: fault; Ftr: filter; Gbx: gearbox; Gra: gradient; Gri: grid; Gn: generator.

Gs: grease; Hi: high; Hly: hourly; Hor: horizontal; Ht: heating; Htex: heat exchanger; Hum: humidity; Hy: hydraulic; Hz: frequency; Ice: icing; Id: identifier; Idl: idling; Inc: increase; Inj: injective mapping; Inl: online; Inlet: inlet; Inst: instantaneous; Intl: internal.

Lev: level; Log: log; Lift: lifting crane; Lim: limit; Lo: low; Lu: lubricating oil; Lum: luminance; Man: manual; Max: maximum; Met: meteorological; Min: minimum; Mly: monthly; Mod: mode; Mthd: method; Mul: multiplier; Mx: measurement; Nac: nacelle.

Num: number (size); Of: offline; Oil: oil filling; Op: operation; Oper: operator; Ov: over (end); Per: period; PF: power factor; Ph: phase; Pmp: pump; Pl: plant; Plu: pollution; Pos: position; Pres: pressure; Prod: production; Pt: pitch; Ptr: pointer; Pwr: power; q: quality.

Rdy: ready; Rep: report; Rms: root mean square; Rng: range; Roof: roof; Rot: rotor (wind turbine); Rs: reset; React: reactive; Rtr: rotor (generator); Sdv: standard deviation; Sev: severity; Seq: sequence; Shf: shaft (main shaft); Smk: smoke; Smp: sampling; Sp: setpoint.

Spd: speed; Src: source; St: status; Sta: stator; Stdby: standby; Stop: stop; Str: start; Sw: switch; Sys: system; t: timestamp; Tm: timer; Tmp: temperature; Tot: total; Tow: tower; Tra: transient; Trf: transformer; Trg: trigger; Torq: torque; Tur: wind turbine.

Un: under; Urg: urgent; V: voltage; VA: apparent power; Val: value; Vals: values; Ver: vertical; Vib: vibration; Vis: visibility; Wd: wind; Wly: weekly; Wup: end (as given in the table); Xdir: X axis; Ydir: Y axis; Yly: yearly; Yw: yaw.

5.1 General provisions - Overview of logical node classes

This standard defines the following two groups of common logical node classes: 1) system specific logical nodes; 2) wind power plant specific logical nodes.

System specific logical nodes shall contain all common information of the physical host device and the information specific to wind power. Wind power plant specific logical nodes shall inherit at least all mandatory information of the system logical nodes.

The structure of all logical node classes defined in this standard is inherited from the abstract logical node class (LN) defined in 9.1.1 of DL/T 860.72-2004 (see Figure 2). Except for the logical node physical device information (LPHD), all other logical node classes defined in this part (logical node zero LLN0 and the wind power plant specific logical nodes) shall inherit at least the mandatory information of the common logical node (common LN).

Figure 2 - Logical node relationship diagram: LPHD and the wind power plant common logical node derive from the abstract LN class of DL/T 860.72-2004, 9.1.1; LLN0 and the wind power plant specific logical nodes (e.g. WTUR) derive from the wind power plant common logical node.

All system specific logical node classes listed in Table 1 are mandatory. Logical node zero (LLN0) represents the common information of the logical device, and the logical node physical device (LPHD) represents the common information of the host logical device of the physical device (see DL/T 860.71-2006, 8.2).

Table 1 - System specific logical nodes: LLN0, logical node zero, mandatory (M).

Table 1 - System specific logical nodes: LPHD, logical node physical device information, mandatory (M).

Wind power plant information shall be classified in wind power plant specific logical nodes. In principle, the classification of wind power plant information into different logical nodes is arbitrary and the modelling method is flexible; from the standardization point of view, however, all wind power plant information should be classified in a clear and identical way. Table 2 lists the logical nodes into which wind power plant information is decomposed.

Table 2 - Wind power plant specific logical nodes: WTUR, wind turbine general information, mandatory (M); WALM, wind power plant alarm information, optional (O).

Table 2 - Wind power plant specific logical nodes: WMET, wind power plant meteorological information, optional (O); WAPC, wind power plant active power control information, optional (O); WRPC, wind power plant reactive power control information, optional (O).

A wind power plant consists of several parts, including one or more wind turbines. Table 3 lists the logical nodes into which a wind turbine is decomposed. Each wind turbine model shall include the mandatory logical nodes listed in Table 3. Although some logical nodes are optional in application, this series strongly recommends deviating as little as possible from the logical nodes listed in Tables 2 and 3.

Table 3 - WTUR: wind turbine general information, mandatory (M).

Table 3 - WROT: wind turbine rotor information, mandatory (M).

Table 3 - WTRM: wind turbine transmission (drive train) information, optional (O).

Table 3 - WGEN: wind turbine generator information, mandatory (M).

Table 3 - WCNV: wind turbine converter information, optional (O).

Table 3 - WTRF: wind turbine transformer information, optional (O).

Table 3 - WNAC: wind turbine nacelle information, mandatory (M).

Table 3 - WYAW: wind turbine yaw information, mandatory (M).

Table 3 - WTOW: wind turbine tower information, optional (O).

Table 3 - WALM: wind power plant alarm information, mandatory (M).

Table 3 - WSLG: wind turbine state log information, optional (O).

Table 3 - WALG: wind turbine analogue log information, optional (O).

Table 3 - WREP: wind turbine report information, optional (O).

As shown in Tables 2 and 3, information is modelled with a set of logical node classes, classified by decomposing the physical wind turbine into logical nodes. One example in practice is alarm information: all alarm information shall be collected in a single logical node.

Historical information shall be modelled by separate logical nodes for recording events (status, alarm, command, event counting, state timing) and for recording analogue time series (long-term, demand and transient records).

Apart from the common information of all wind turbines (independent of manufacturer), in practice most information depends on the wind turbine concept, manufacturer and installation site, as well as on the technology and state of the wind turbine. Therefore, as a modelling rule, the data class attribute names representing wind power plant specific logical node information focus on the most common modern wind turbine concept, namely three blades, variable speed, active pitch (electric or hydraulic) and gearbox drive. If a wind turbine system or component produces additional information, new data classes or specialized data classes may be defined for new logical nodes, and additional user-specific logical nodes may also be defined.

The semantics and semantic definitions of the data class names are listed in alphabetical order and defined in 6.3. The units and multipliers related to data classes are given in Annex B.

The modelling method, including the general table structure of logical nodes, is described in 6.2.2 of IEC 61400-25-1.

The standardized names of logical node classes use capital letters. Data names at the first level of the hierarchy (below the logical node level) begin with a capital letter; data names and attribute names at the second and subsequent levels use lower-case letters.

5.2 Use of logical node classes

The logical node classes defined in this standard (such as WROT and WTUR) and the logical node classes defined in other referenced standards (such as XCBR and MMXU in 5.12.1 and 5.10.7 of DL/T 860.74-2006) shall be instantiated in the actual system. Figure 3 describes an example of the logical nodes used in an actual wind turbine.

Figure 3 - Example of use of logical nodes: WROT at the rotor; WTRM at the transmission; WGEN1 and WGEN2 at the generators; WCNV at the converter; WNAC at the nacelle; WYAW at the yaw system; WTOW at the tower; WTRF at the transformer; WTUR, WREP, WSLG and WALM at the wind turbine controller; WMET at the meteorological mast; WAPC and WRPC at the wind power plant controller; MMXU measuring units and XCBR circuit breakers at the wind turbine breaker and the utility grid breaker (see IEC 61850-7-4 for details).

The logical node instances described in Figure 3 represent information from the wind turbine "WTUR", the yaw system "WYAW", the converter "WCNV" and so on. Instance names such as "WGEN1" and "WGEN2" represent different generators. Figure 3 also illustrates the power system interface, including the measuring unit "MMXU" and the circuit breaker "XCBR". MMXU, XCBR and other logical nodes related to the power system are specified in DL/T 860.73-2004.

5.3 Extended information models

The information models described in Clause 6 of this standard may be extended with additional logical nodes and data in a specific implementation. If a different topology is adopted (such as several generators and gearboxes) or several sensors (such as temperature or current sensors) are used for monitoring, the user may freely assign additional data names to the related information. Any data may be added to any logical node.

The extension rules for logical nodes, data classes and data attributes are defined in Annex A of DL/T 860.74-2006. The namespace concept defined in Clause 14 of DL/T 860.71-2006 allows any extension name to be defined, and namespaces are distinguished by a unique identifier.

6.1.1 Wind power plant logical node classes - Wind power plant common logical node class

The wind turbine specific compatible logical node classes defined in this standard are instantiations of the wind turbine common logical node class defined in Table 4.

Table 4 - Logical node name: the logical node name, inherited from the logical node class (see 9.1.1 of DL/T 860.72-2004).

Table 4 - Mandatory logical node information (to be inherited by all logical nodes except LPHD): NamPlt, attribute type LPL, name plate (inherited from DL/T 860.74-2006), mandatory (M).

Table 4 - Optional logical node information: Mod, attribute type INC, mode (inherited from DL/T 860.74-2006), optional (O).

Table 4 - Beh, attribute type INS, behaviour (inherited from DL/T 860.74-2006), optional (O).

Table 4 - Health, attribute type INS, health (inherited from DL/T 860.74-2006), optional (O).

Table 4 - Loc, attribute type SPS, local operation (inherited from DL/T 860.74-2006), optional (O).

Table 4 - EEHealth, attribute type INS, external equipment health (inherited from DL/T 860.74-2006), optional (O).

Table 4 - EEName, attribute type WDPL, external equipment name plate, optional (O).

Table 4 - OpCntRs, attribute type INC, operation counter reset (inherited from DL/T 860.74-2006), optional (O).

Table 4 - OpCnt, attribute type INS, operation counter (inherited from DL/T 860.74-2006), optional (O).

Table 4 - OpTmh, attribute type INS, operation time (inherited from DL/T 860.74-2006), optional (O).

Table 4 - Statistical information: CalcExp, attribute type SPS, calculation period expired, optional (O).

Table 4 - CalcStr, attribute type SPC, start the calculation at the time operTm (if set) or start the calculation immediately, optional (O).

Table 4 - CalcMthd, attribute type ING, calculation method of statistical data; allowed values: PRES, MIN, MAX, TOTMIN, TOTMAX, AVG, SDV; optional (O).

Table 4 - CalcPer, attribute type ING, calculation period of statistical data, in seconds, optional (O).

Table 4 - CalcSrc, attribute type ORG, object reference to the source logical node, optional (O).

NOTE to Table 4: If statistical information is supported, all five statistical data shall be available.

If the calculation method is not PRES, the data CalcMthd shall be included in any logical node representing analogue or digital information. The data CalcExp, CalcStr, CalcPer and CalcSrc shall be included in any logical node representing statistical data (MIN, MAX, etc.).

The instantiation of the wind power plant common logical node class shall inherit all the information required by the wind power plant specific logical nodes (see Table 2). For optional logical node information, the instantiation may take one of three forms: the specific information item is not inherited; the specific information item is inherited and set as optional; the specific information item is inherited and defined as mandatory.

6.1.2 Logical node zero (LLN0)

The logical node zero class is used to write the common information address of the logical device, see Table 5. Table 5 - LLN0 class: the logical node shall inherit all mandatory data from the wind power plant common logical node class (see 6.1.1), mandatory (M).

Logical node zero represents the specific information of the logical device. The name plate of logical node zero represents the root namespace of the logical device (logical device namespace, ldNs). The value for the IEC 61400-25 series is "IEC 61400-25:2006". The namespace also applies to names inherited from other standards. Each logical device has only one logical device namespace; for example, only one version is available for a single logical device.

6.1.3 Physical device information (LPHD)

The physical device information class shall model the common issues of the physical device, see Table 6. Logical node name: inherited from the logical node class (see DL/T 860.72-2004).

Table 6 - PhyNam, attribute type WDPL, physical device name plate (see 7.4.2.2), mandatory (M).

Table 6 - PhyHealth, attribute type INS, physical device health (inherited from DL/T 860.74-2006), mandatory (M).

Table 6 - OutOv, attribute type SPS, output communication buffer overflow (inherited from DL/T 860.74-2006), optional (O).

Table 6 - Proxy, attribute type SPS, indication that the logical device is a proxy (inherited from DL/T 860.74-2006), mandatory (M).

Table 6 - InOv, attribute type SPS, input communication buffer overflow (inherited from DL/T 860.74-2006), optional (O).

Table 6 - NumPwrUp, attribute type INS, number of power-ups (given in the Chinese text as number of uninterruptible power supplies) (inherited from DL/T 860.74-2006), optional (O).

Table 6 - WrmStr, attribute type INS, number of warm starts (inherited from DL/T 860.74-2006), optional (O).

Table 6 - WacTrg, attribute type INS, number of watchdog resets detected (inherited from DL/T 860.74-2006), optional (O).

Table 6 - PwrUp, attribute type SPS, power-up detected (inherited from DL/T 860.74-2006), optional (O).

Table 6 - PwrDn, attribute type SPS, power-down detected (inherited from DL/T 860.74-2006), optional (O).

Table 6 - PwrSupAlm, attribute type SPS, power supply alarm (inherited from DL/T 860.74-2006), optional (O).

Table 6 - RsStat, attribute type SPC, reset device statistics (inherited from DL/T 860.74-2006), optional (O).

6.2.1 Wind power plant specific logical nodes - Wind turbine general information (WTUR)

The data classes representing wind turbine general information are composed of logical nodes, see Table 7. The logical node is mandatory, that is, all defined mandatory data classes shall comply with this series. The WTUR logical node shall inherit all mandatory data from the wind power plant common logical node class (see 6.1.1).

Table 7 - Common information: AvlTmRs, attribute type TMS, wind turbine availability time (vendor specific), optional (O).

Table 7 - OpTmRs, attribute type TMS, operation time (vendor specific), optional (O).

Table 7 - StrCnt, attribute type CTE, number of wind turbine starts (vendor specific), optional (O).

Table 7 - StopCnt, attribute type CTE, number of wind turbine stops (vendor specific), optional (O).

Table 7 - TotWh, attribute type CTE, total (net) active energy, mandatory (M).

Table 7 - TotVArh, attribute type CTE, total (net) reactive energy, optional (O).

Table 7 - DmdWh, attribute type BCR, active energy demand (default demand direction: energy flowing from the substation busbar into the wind turbine), optional (O).

Table 7 - DmdVArh, attribute type BCR, reactive energy demand (default demand direction: energy flowing from the substation busbar into the wind turbine), optional (O).

Table 7 - SupWh, attribute type BCR, active energy supply (default supply direction: energy flowing from the wind turbine into the substation busbar), optional (O).

Table 7 - SupVArh, attribute type BCR, reactive energy supply (default supply direction: energy flowing from the wind turbine into the substation busbar), optional (O).

Table 7 - Status information: TurSt, attribute type STV, wind turbine status, mandatory (M).

Table 7 - Analogue information: W, attribute type MV, active power (given in the table as active electrical energy), mandatory (M).

Table 7 - Var, attribute type MV, reactive power (given in the table as reactive electrical energy), optional (O).

Table 7 - Control information: SetTurOp, attribute type CMD, wind turbine operation command, mandatory (M).

Table 7 - VArOvW, attribute type CMD, wind turbine command giving reactive power priority over active power, optional (O).

Table 7 - VArRefPri, attribute type CMD, wind turbine reactive power setpoint priority command, optional (O).

Table 7 - DmdW, attribute type SPV, wind turbine active power setpoint, optional (O).

Table 7 - DmdVAr, attribute type SPV, wind turbine reactive power setpoint, optional (O).

Table 7 - DmdPF, attribute type SPV, wind turbine power factor setpoint, optional (O).

6.2.2 Wind turbine rotor information (WROT)

The data classes representing wind turbine rotor information are composed of logical nodes. The logical node is mandatory, that is, at least all mandatory data classes defined in Table 8 shall comply with this series.