3353 Peachtree Road NESuite 600, North Tower

Atlanta, GA 30326404-446-2560 | www.nerc.com

Phasor Measurement Unit Data Definition File InformationVersion 1.0

May 1, 2012

Table of Contents

Table of Contents........................................................................................................................... ii

Introduction...................................................................................................................................1

PMU DDF Filename........................................................................................................................1

PMU Data Validator.......................................................................................................................1

Database Layout............................................................................................................................ 1

Importing Your Registry.................................................................................................................2

Field Names................................................................................................................................... 2

Preparing for Validation.................................................................................................................3

Field Values....................................................................................................................................1

PMU and PDC Ranges....................................................................................................................1

ii Phasor Measurement Unite Data Definition File Information – May 2012

Unit Data Definition

Introduction

Independent System Operators (ISOs) and Reliability Coordinators (RCs) share reliability data for the responsible management of the bulk power system (BPS). As Phasor Measurement Units (PMU’s) and Phasor Data Concentrators (PDCs) are deployed across this system, the North American Electric Reliability Corporation (NERC) Data Exchange Working Group (DEWG) has recommended guidelines for defining this data. The first version of the PMU Data

Unit Data Definition

Definition File (PMU DDF) template was accepted at the April 19, 2012 DEWG meeting in Albany, NY.

PMU DDF Filename

The PMU DDF filename is to take the following format: <NERCNETID>_PMU_YYYYMMDD.XLS. For NYISO, the published file would be NYISO_PMU_20120501.XLS.

PMU Data Validator

The PMU Data Validator is a utility to check individual files against the rules put forth in the PMU DDF template. Many of the test requirements were outlined at NERC DEWG meetings.

Database Layout

When viewing the queries, similar tests are grouped together with a "QA" prefix. For example, QA0600 grouping check valid field entries for several fields. The next identifier in the query name is simply to help sort the order in which the queries should be executed. Finally, the query name will have a short description of the test. Any tables created from queries will have the same name as the query except for the "tbl" prefix. Tables with "LOOKUP" prefixes contain valid field entries. Queries with "QRY_LIST" prefixes simply query the LOOKUP table and sort valid field names used in combo boxes on the forms.

2 Phasor Measurement Unite Data Definition File Information – May 2012

Unit Data Definition

Importing Your Registry

You may import your registry on your own or use one of the import buttons on the Validator Display. There is one button to import a text file and another to import a Microsoft excel file. Regardless, your registry must be imported into a table called REGISTRY_TARGET with all the appropriate field names listed below. During import, please be sure an ID field is created which is type AUTONUMBER. This will assign a primary key to each record in your registry and is a key

Unit Data Definition

element throughout the validation process. A copy of this table is created in PREREQ_REGISTRY TARGET and several validation tests are performed on PREREQ_REGISTRY_TARGET.

Field Names

The following field names are required:

ID, NERCNET_ID, SOURCE, SUBSTATION, STN, BASEKV, BUS, MEASUREMENTNAME, CHNAM, DEVTYPE, DEVNAME, ICCPOBJECTID, DATATYPE, MEASUREMENTTYPE, CALCULATED, UNITS, SOURCE_PHASE_ANGLE, PDC_ID, PMU_ID, COMMDATE, DECOMMDATE, SAMPLETIMEPERSECOND, DATUM, LAT, LONG, GUID, COMMENT.

Table 1: Field Names

Field Name Data Type

ID Autonumber added during import.

NERCNET_ID Text. Each ISO or RC has a unique NERCNET ID. List provided below.

SOURCE Text

SUBSTATION Text

STN Text – 16 char value as seen in c37.118 stream.

BASEKV Number

BUS Text

MEASUREMENTNAME Text

CHNAM Text – 16 char value as seen in c37.118 stream.

DEVTYPE Text - Device type.

DEVNAME Text – Device name.

ICCPOBJECTID Text

DATATYPE Text

MEASUREMENTTYPE Text

CALCULATED Text

UNITS Text

4 Phasor Measurement Unite Data Definition File Information – May 2012

Unit Data Definition

SOURCE_PHASE_ANGLE Text

PDC_ID Number

PMU_ID Number

COMMDATE Date/Time – Commission date.

Unit Data Definition

DECOMMDATE Date/Time – Decommission date.

SAMPLETIMEPERSECOND Number – Scan rate.

DATUM Text – Corresponds to latitude and longitude datum.

LAT Number

LONG Number

GUID Text

COMMENT Text

The ID field should be added during import, as type autonumber, to be used as the primary key. Some fields should only contain specific values as displayed below.

Preparing for Validation

After importing your registry into the REGISTRY_TARGET table with the appropriate field names, you are ready to validate it. The PMU Registry Validator performs various tests against your data and sends the results to the screen. The results can be found in the REGISTRY_OUTPUT table.

6 Phasor Measurement Unite Data Definition File Information – May 2012

Unit Data Definition

Field Values

Some fields must contain specific values. This section displays the valid data entries for these fields:

Table 2: Valid Data Entries

Unit Data Definition

NERCNET_ID

DEVTYPE DATATYPE MEASUREMENTTYPE CALCULATED UNITS SOURCE_PHASE_ANGLE POLAR_RECTANGULAR DATUM

DUKE LINE PHASOR ANGLE YES DEGREE

A_B_C POLAR NAD27

EES GEN ANALOG ACTIVE_POWER NO MW B_C_A RECTANGULAR NAD83

ERCOT CB DIGITAL REACTIVE_POWER MVAR C_A_B WGS84

FRCC TR FREQ_DFREQ VOLTAGE HZ

HQT BUSBAR PHASEA_CURRENT STATUS

IESO PHASEB_CURRENT AMPS

ISONE PHASEC_CURRENT KV

MISO PHASEA_VOLTAGE MVA

NBSO PHASEB_VOLTAGE

NYISO PHASEC_VOLTAGE

PJM POSSEQ_VOLTAGE

SOCO POSSEQ_CURRENT

SPC NEGSEQ_VOLTAGE

SPP NEGSEQ_CURRENT

Phasor Measurement Unite Data Definition File Information – May 2012 8

Unit Data Definition

TVA ZEROSEQ_VOLTAGE

WECC ZEROSEQ_CURRENT

APARENT_POWER

Unit Data Definition

PMU and PDC Ranges

Each device using the c37.118 protocol is to share a device ID. In order to prevent multiple devices from having the same ID, please adhere to the ranges in the table below.

Table 3: PMU and PDC Ranges for Device ID

NERCNET ID NAME MIN MAX

EES Entergy Electric System 1001 3000

ERCOT ERCOT – ISO 3001 5000

FRCC Florida Reliability Coordinating Council 5001 7000

HQT Hydro-Quebec TransEnergy 7001 9000

IESO Independent Electricity System Operator (Ontario) 9001 11000

ISONE ISO New England 11001 13000

MISO Midwest ISO 13001 15000

NYISO New York ISO 15001 17000

PJM PJM Interconnection 17001 25000

SOCO Southern Company Services 25001 27000

SPP Southwest Power Pool 27001 29000

TVA Tennessee Valley Authority 29001 31000

DUKE Duke Power Company 31001 34000

WECC Western Electricity Coordinating Council 34001 36000

SPC Saskatchewan Power Corporation 36001 38000

NBSO New Brunswick System Operator 38001 40000

Phasor Measurement Unite Data Definition File Information – May 2012 10