Adoption and Update of Wind Power Plant Communications Standard 61400-25

The NIST PAP 16 team (Wind Plant Communication) will gather use cases and requirements from wind industry stakeholders with a focus on those requirements associated with integrating bulk wind assets into wind plant operation and utility command and control systems. Special attention will be given to those use cases and requirements that differ from those developed by the IEC TC 88 61400-25 working group to quickly identify the gaps that are preventing ubiquitous application of the standard in the US. The PAP Team will seek out recent ARRA funding awardees involved in wind plant projects to ensure that their requirements are discovered and they are made aware of the existing portfolio of standards available.

The PAP 16 team will provide specific recommendations to the IEC TC 88 working group responsible for maintaining the 61400-25 standard to address the gaps identified.

Click HERE for the PAP Proposal [WORD document].

The standard IEC 61400-25-2 (Wind) mainly extends the information models of IEC 61850-7-4, 7-410 (DER) and 7-420 (Hydro). All objects of all four standards build a huge set of standard information models. ALL models ca be used on generic IEC 61850-8-1 compliant communication stacks. Even new models not yet standardized but defined by anybody (!) can be configured and run on compliant communication stacks - the extended models just have to follow the well defined name space concept.

So, if you need a Logical Node, e.g., LN FIZL = Fizzli Puzzli, for your Puzzli application: just define the Data Objects you need: Fipu1, Fipu2, ... of common data class SPS (single point status) ... and you are done. Define the corresponding SCL file and run it with a communication stack. You need to know what the LN and its Data Objects mean - and you have to bind it to your Puzzli application. Here is how a client sees the corresponding server:

The value of the name space of the LN nameplate FIPU1.EX.LPL.LnNs is "NIST-PAP16_2010-06-26_Fizzli-Puzzli-LN" - indicates that this is a standard conformant Extension (Functional Constraint FC=EX).

The LN instance in SCL notation is:

<LN lnType="FIPU_1" lnClass="FIPU" inst="1">
  <DOI name="LPL">
    <DAI name="lnNs">
      <Val>NIST-PAP16_2010-06-26_Fizzli-Puzzli-LN</Val>
    </DAI>
    <DAI name="vendor">
      <Val>NettedAutomation GmbH</Val>
    </DAI>
    <DAI name="swRev">
      <Val>0.1</Val>
    </DAI>
    <DAI name="d">
      <Val>This is a NIST specific extension of the IEC 61850/61400-25 information model.</Val>
    </DAI>
  </DOI>
</LN>

DataTypeTemplate for new LN class:

<LNodeType id="FIPU_1" lnClass="FIPU">
  <DO name="Fipu1" type="SPS_0" />
  <DO name="Fipu2" type="SPS_0" />
  <DO name="Fipu3" type="SPS_0" />
  <DO name="Fipu4" type="SPS_0" />
  <DO name="LPL" type="LPL_1" />
</LNodeType>

<DOType id="LPL_1" cdc="LPL">
  <DA name="vendor" bType="VisString255" fc="DC" />
  <DA name="swRev" bType="VisString255" fc="DC" />
  <DA name="d" bType="VisString255" fc="DC" />
  <DA name="lnNs" bType="VisString255" fc="EX" />
</DOType>

So, NIST or any other organization can quickly identify the gaps in the information models and define any model that is needed for the application of the standard in the US (!!). Most use cases known so far may be implemented by extending the models or defining new models - private models, models defined by any other organization, or by IEC or ANSI or ...