Transformer Losses Calculation

Using IEEE® PQDIF Data Sources with
PQView® 3
May 18, 2013
Using IEEE® PQDIF Data Sources with PQView® 3
Table of Contents
Overview ....................................................................................................................................................... 3
PQView’s PQDIF Characterizer...................................................................................................................... 3
Data Processed by the PQDIF Characterizer ............................................................................................. 3
Triggered Data or Events....................................................................................................................... 3
Steady-State Data ......................................................................................................................................... 4
PQDIF Tags Required by PQView that are Optional in IEEE 1159.3 .......................................................... 4
Data Types Ignored ................................................................................................................................... 5
RMS Triggered Events Records ..................................................................................................................... 5
Data Source Definition .............................................................................................................................. 6
Monitor Settings Record ........................................................................................................................... 7
Observation Record .................................................................................................................................. 7
Waveform Channels with RMS Triggered Data ........................................................................................ 8
Waveform Samples with No RMS ............................................................................................................. 9
Transient Records ......................................................................................................................................... 9
Data Source Definition .............................................................................................................................. 9
Monitor Settings Record ......................................................................................................................... 10
Observation Record ................................................................................................................................ 10
Trend Data .................................................................................................................................................. 11
Data Source Definition ............................................................................................................................ 11
Monitor Settings Record ......................................................................................................................... 12
Mapping between PQView Steady State Channels and IEEE PQDIF Value Log ...................................... 13
Waveform Snapshots .................................................................................................................................. 16
Data Source Definition ............................................................................................................................ 16
Legal Information ........................................................................................................................................ 17
Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 2

Overview
This white paper is intended to give specific guidance in reading files formatted to the IEEE® PQDIF
standard for use with PQView®.
PQView is a power quality database management and analysis database system. PQView was designed
so that measurement data from various proprietary instrument formats could be stored in a common
database format allowing system analyses based on data from various instrument sources. For more
information, see www.pqview.com.
PQDIF is a binary file format specified in IEEE Std 1159.3-2003 that is used to exchange voltage, current,
power, and energy measurements between software applications. PQDIF is an acronym for “Power
Quality Data Interchange Format.” IEEE PQDIF is maintained by the IEEE P1159.3 Task Force of the IEEE
Working Group on Monitoring Electric Power Quality. For more information, see
http://grouper.ieee.org/groups/1159/3/.
This work is sponsored by the IEEE Power Quality Subcommittee. For more information, see
http://grouper.ieee.org/groups/td/pq/.
PQView’s PQDIF Characterizer

The PQView PQDIF characterizer was designed to allow PQView users to import measurement data from
any source or format that is exported as a PQDIF file.
PQView is designed to hold and analyze a broad range of power quality data. The data model for
PQView is event-centric for disturbance information. Steady-state information is stored as compressed
trend data.
Data Processed by the PQDIF Characterizer

Triggered Data or Events
Triggered or event data are waveform samples, rms samples, or event characteristics gathered as the
result of a trigger condition and is meant to be a disturbance or event. The event is usually triggered by
channel data from the instrument and can be marked using the trigger method
ID_TRIGGER_METH_CHANNEL. An external trigger may also be indicated. Full analysis by the PQView
characterizer requires a trigger channel to be specified. As a result, not all characteristics would be
available for externally triggered data. The two types of data processed by the PQDIF characterizer are
rms samples and waveform samples. The triggered data analysis portion of the characterizer analyzes
only voltage-triggered information and processes up to three phases of voltage and current plus neutral,
residual, and “net” channels.
Samples of waveform or rms for an event must be represented in a single observation. For example, all
of the individual channels recorded for a single event – VA, IA, VB, IB, etc. – should be included in a
single observation. Additionally, all of the data for each individual channel must be stored in a single
channel instance of the overall observation. If the data for one of the channels is stored as multiple
channel instances within the one event observation, each instance will be processed as though they
were separate events. This is only a recommendation in the IEEE 1159.3 standard, but a requirement
for PQView.

Voltage sag, voltage swell, and voltage interruption measurements can be represented using the
ID_QT_MAGDURTIME quantity type. This measurement consists of the time stamp, voltage magnitude,
current magnitude, and duration typical of data represented on a CBEMA Curve or an ITIC Curve.
Steady-State Data
Non-triggered information like steady-state voltage, current and power information is handled in a
different manner in the characterizer. This information is tagged with the ID_TRIGGER_METH_PERIODIC
for the trigger method. Again there are two types of data that fall into the steady-state category, trend
data, and periodically sampled waveform information.
Trend data is a time trend of any value supported by PQView. Any values that are not represented in
the PQView Channel table are disregarded. Additional channels are periodically added to this table so
you should consult Electrotek Concepts or EPRI for updated listings if you do not find a channel
definition meeting a particular need.
Periodic waveforms are analyzed to provide as much information as possible. Fourier transforms are
performed on all data that has at least one full cycle of information that has been sampled at a power of
2 points per cycle. There must be at least 32 points per cycle for full analysis. If Fourier analysis is
performed the following characteristics are extracted:
Voltage/Current Waveforms
 rms, harmonic rms, arithmetic sum, and peak
 crest factor, form factor
 telephone interference factor (TIF)
 total harmonic distortion (THD), THD for even harmonics, THD for odd harmonics
 harmonic spectrum
 positive-sequence component, negative-sequence component, and zero-sequence component
 negative-sequence imbalance, positive-sequence imbalance, line-neutral magnitude imbalance,
and line-line magnitude imbalance
If three phases of voltage and current are present power calculations are performed and the following
additional characteristics are added to the database:
 active power, reactive power, apparent power by phase and for three phases
 true power factor, displacement power factor by phase
 real and apparent power harmonic spectrum by phase phase
PQDIF Tags Required by PQView that are Optional in IEEE 1159.3

A number of tags are listed as optional in IEEE Std 1159.3-2003. They are either required or
recommended for processing of data by the PQView PQDIF characterizer.
Tag Record Comment Required

by PQView 3?
tagNameDS Data Source This tag must be at the top level of the Required
Data Source Definition. This entry
becomes the name of the site in

PQView. Specifically, it is stored in the

name field of the Site table (Site.name).
tagSeriesNominalQuantity Data Source This tag should be defined in order to Required

characterize event records, the voltage
channels defined for the event records
must inform the characterizer of the
base voltage
tagChannelTriggerIdx Observation This tag indicates the channel or Required
channels that caused the event to be
triggered. The value of this tag is the
channel definition index referencing the
data source
tagNominalFrequency Monitor Settings This specifies nominal system frequency. Highly
If not specified, 60 Hz is assumed. Recommended
Data Types Ignored

The PQView PQDIF characterizer continues to evolve as Electrotek and EPRI evaluate the benefits of
importing various data types that can be specified by PQDIF but that are not yet compatible with the
PQView PQDIF characterizer. This section identifies several types of data that can be stored in a valid
PQDIF file that are not imported into PQView. Some of these types have no PQView equivalent and
others have yet to be implemented.
All statistical data except quantity characteristics that reflect a statistical basis such as flicker (Pst)
 Statistical information such as probability distribution function or histogram data types are not
included
 All channels with the following quantity types are currently not supported:
o ID_QT_RESPONSE
o ID_QT_FLASH
o ID_QT_HISTOGRAM
o ID_QT_HISTOGRAM3D
o ID_QT_CPF
o ID_QT_XY
o ID_QT_MAGDUR
o ID_QT_XYZ
o ID_QT_MAGDURCOUNT
RMS Triggered Events Records

This section describes how to define a channel to hold standard rms information that is part of a
triggered rms type event. Information for rms variation events is stored as a set of magnitude and
duration characteristics that are derived by the characterizer from voltage rms samples. The original
triggered trend data can optionally be imported to the database as well.

Some instruments can capture corresponding waveform information along with the rms trace of a
triggered rms variation event. The characterizer will maintain the relationship between the rms and
waveform data provided all of the data is included in a single observation record. The waveform data
will be characterized for transient characteristics as well and stored as shown below in the Transient
Events section.
Data Source Definition

For each channel of data, there must be a Data Source definition record to define the data type,
including its characteristics and the format in which it is stored. The following PQDIF Data Source record
definition shows all of the fields either required or recommended for a triggered rms voltage channel,
VAB. The remaining voltage channels (VBC, VCA) would be identical with the exception of the
tagPhaseID value. These channel definitions may optionally be followed by definitions for the current
channels.
This definition includes minimum, maximum, and average series definitions for each channel. This
allows for envelope-based measurements. If only instantaneous values of the rms value are available
(and it is not an average over an interval longer than one cycle) only the ID_SERIES_VAL_TYPE_VALUE
should be used. If you have just a series of average values over an interval, omit the
ID_SERIES_VALUE_TYPE_MIN and ID_SERIES_VALUE_TYPE_MAX series definitions.
All rms variation event data must be reported using the ID_QT_PHASOR quantity type whether phase
angle information is available or not. This can be considered an implementation restriction.
All other tags in Figure 1 are required in order create valid triggered RMS variation event PQDIF channel
so that the PQView characterizer adequately processes the event. The following example data source
segment illustrates the hierarchical structure of the required data source elements and is created with
the PQDIFR tool available from the IEEE 1159.3 web site.
-tag: tagRecDataSource (level 0)
+-tag: tagEffective value: 9/3/1999 15:2:42.000000000
+-tag: tagDataSourceTypeID value: ID_DS_TYPE_MEASURE
+-tag: tagNameDS value: 'Standby'
+- tag: tagChannelDefns (level 1)
| +- tag: tagOneChannelDefn (level 2)
| | +-tag: tagChannelName value: 'Voltage A'
| | +-tag: tagPhaseID value: 5 (ID_PHASE_AB)
| | +-tag: tagQuantityTypeID value: ID_QT_PHASOR
| | +-tag: tagQuantityMeasuredID value: ID_QM_VOLTAGE
| | +- -- tag: tagSeriesDefns (level 3)
| | | +- tag: tagOneSeriesDefn (level 4)
| | | | +- tag: tagQuantityUnitsID value: ID_QU_SECONDS
| | | | +- tag: tagQuantityCharacteristicID value: ID_QC_RMS
| | | | +- tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_TIME
| | | | +- tag: tagStorageMethodID value: 6
| | | | +-(End of collection)
| | | | +- tag: tagQuantityUnitsID value: ID_QU_VOLTS
| | | | +- tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_MIN
| | | | +- tag: tagSeriesNominalQuantity value: 480.000000
| | | +-tag: tagOneSeriesDefn (level 4)
| | | | +-tag: tagQuantityUnitsID value: ID_QU_VOLTS
| | | | +-tag: tagQuantityCharacteristicID value: ID_QC_RMS
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_MAX

| | | | +-tag: tagStorageMethodID value: 3

| | | | +-tag: tagSeriesNominalQuantity value: 480.000000
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_AVG
| | | +-(End of collection)
| | +-(End of collection)
The channel definitions repeat to include all recorded phases.
Figure 1: Required Tags for Triggered RMS Variation Event.
Monitor Settings Record

The Monitor Settings records are normally optional in PQDIF. They are not required for the PQDIF
characterizer but several of the tags in the Monitor Settings record are highly recommended. Figure 2
shows the minimum tags that are highly recommended as part of the Monitor Settings record
The base system frequency is required for a number of calculations with the characterizer. This is
specified as a tag in the monitor settings record. The characterizer will assume 60 Hz if this tag is not
present.
-tag: tagRecMonitorSettings (level 0)
+-tag: tagEffective value: 9/3/1999 15:2:42.000000000
+-tag: tagNominalFrequency (value: 60.000000
+-tag: tagChannelSettingsArray (level 1)
| +- tag: tagOneChannelSetting (level 2)
| | +-tag: tagChannelDefnIdx value: 0
| | +-tag: tagTriggerTypeID value: 3 (ID_TRIG_LOW | ID_TRIG_HI)
| | +-tag: tagTriggerHigh value: 528.000000
| | +-tag: tagTriggerLow value: 432.000000
… Repeated for all channels
Figure 2: Minimum Recommended Tags for Monitor Settings Record
Observation Record
Observation records carry the actual data for an event or trend of steady-state data. For rms variation
event data, the observation needs certain time stamp information for the record including the start time
for the record and the trigger time that usually is some time after the beginning of the record. For event
records, the trigger information is very important and is required for full characterization of the data.
Figure 3 is a sample observation record for an rms variation event. This event was triggered on voltage
phase a-n as the rms voltage violated the ID_TRIGGER_METH_LOW trigger value specified in the
Monitor Settings record. The software creating this record had elected to name the record “RMS
Variation (Sag).” This name is arbitrary and you can choose a title that suits your naming conventions.
As discussed in the Data Source section above, the quantity type for rms records must be
ID_QT_PHASOR. The time series must be the first series instance in the channel. If the event is
triggered on a base voltage other than the tagSeriesNominalQuantity specified in the channel definition,

the tagSeriesBaseQuantity of the observation record is used to override the channel definition base
value.
- tag: tagRecObservation (level 0)
+- tag: tagObservationName value: 'RMS Variation (Sag)'
+-tag: tagTimeCreate value: 9/15/1999 20:32:50.000000000
+-tag: tagTriggerMethodID value: ID_TRIGGER_METH_LOW
+-tag: tagTimeTriggered value: 9/15/1999 10:11:16.630000000
+-tag: tagTimeStart value: 9/15/1999 10:11:16.630000000
+-tag: tagChannelTriggerIdx values: ID_PHASE_AN
+-tag: tagChannelInstances (level 1)
| +-tag: tagOneChannelInst (level 2)
| | +-tag: tagChannelDefnIdx value: 0 References the channel defn. in data source
| | +-tag: tagSeriesInstances (level 3)
| | | +-tag: tagOneSeriesInstance (level 4) Series 0, Time
| | | | +-tag: tagSeriesScale value: 1.000000
| | | | +-tag: tagSeriesOffset value: 0.000000
| | | | +-tag: tagSeriesValues (Vector of time data)
| | | +-tag: tagOneSeriesInstance (level 4) Series 1, Average
| | | | +-tag: tagSeriesBaseQuantity value: 480.000000
| | | | +-tag: tagSeriesValues (Vector of average data)
| | | +-tag: tagOneSeriesInstance (level 4) Series 2, Minimum
| | | | +-tag: tagSeriesValues (Vector of minimum data)
| | | +-tag: tagOneSeriesInstance (level 4) Series 3, Maximum
| | | | +-tag: tagSeriesValues (Vector of maximum data)
|…for all channels
Figure 3: Sample Observation Record for RMS Variation Event
Waveform Channels with RMS Triggered Data

Some instruments are capable of capturing waveform information at the trigger time of an rms variation
event. This data can be included with rms variation event insuring that the relationship is maintained or
it can be saved as separate transient event records. To include waveform information with rms
variation events, follow the recommendations given in the following Transient Records section. You
may include temporally noncontiguous sections of waveform data by adding multiple instances of each
channel of waveform data.
There is no hard limit to the number of “segments” or instances of each channel. By default, PQView 3
will import up to twelve “subevents” associated with each event, but this number can be increased. The
additional waveform segments’ time series must be relative to the observation time stamp to ensure
that a viewer or analysis program can show the waveforms in proper time sequence.

Waveform Samples with No RMS

It is the responsibility of the instrument or instrument support software to process the waveform
information, to identify trigger information from the raw data, and to process the waveform information
to create rms data that can be processed as rms variation events.
A good approach is to create a virtual instrument to process the waveforms for both transient and rms
variation events. Many trigger algorithms can be applied to the raw waveform information to identify
trigger points -- waveshape fault, rate change, deviation from base, etc. Processing of rms also can be
done in a straightforward manner by applying a sliding one-cycle rms calculation to the waveform data
and checking against specified sag and swell thresholds. Once the trigger point has been determined,
the data can be completely processed by the PQDIF characterizer to find a full range of characteristics.
Transient Records
Transient event records in the context of the PQDIF characterizer are those triggered events that are
composed of waveform data as opposed to rms trend data. This section describes how to define a
channel to hold transient event information that is part of a triggered waveform event type.
Briefly, transient records are processed for a number of characteristics including magnitude, duration,
and principle frequency among others. The original triggered raw waveform data can optionally be
imported to the database as well. The PQView PQDIF characterizer will process up to four voltage and
four current waveforms in each observation. For complete characterization, the waveforms must be
sampled at a power of 2 points per cycle between 32 points per cycle and 4096 points per cycle. Trigger
information from the instrument is important for accurate and complete characterization.

The following PQDIF Data Source record definitions show all of the fields either required or
recommended for a triggered transient voltage channel, VA. The remaining voltage channels (VB, VC)
would be identical with the exception of the tagPhaseID value. These channel definition may optionally
be followed by definitions for the current channels.
This channel definition in Figure 4 includes a value series for the waveform itself and min and max series
with tagValueType of ID_SERIES_VALUE_TYPE_PEAK for passing along the instantaneous maximum and
minimum values of the event. The value series is used to hold the waveform data. The time series
should contain (or expand to) exactly the same number of points as the waveform series.
Important Note: Note that the tagSeriesBaseQuantity value for the VAL, MIN, and MAX series is set to
the “peak” base voltage for a 480 volt system, 678 Volts. For waveform information, 100% or 1 per unit
should correspond the peak value of the normal waveform, which should be 1.414 multiplied by the rms
base voltage.
The peak channels are optional and are used to hold peak values of the signal between the individual
samples of the waveform. By our convention, these values include low frequency information. The max
series hold the positive going peak value and the min series hold the negative going peak.
All transient event data must be reported using the ID_QT_WAVEFORM quantity type. All other tags in
the fragment are required in order create valid PQDIF and to adequately process the event.

| +-tag: tagOneChannelDefn (level 2)

| | +-tag: tagChannelName value: 'Voltage A'
| | +-tag: tagPhaseID value: ID_PHASE_AN
| | +-tag: tagQuantityTypeID value: ID_QT_WAVEFORM
| | +-tag: tagQuantityMeasuredID ID_QM_VOLTAGE
| | +-tag: tagSeriesDefns (level 3)
| | | | +-tag: tagQuantityUnitsID value: ID_QU_SECONDS
| | | | +-tag: tagQuantityCharacteristicID value: ID_QC_INSTANTANEOUS
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_TIME
| | | | +-tag: tagQuantityCharacteristicID value: ID_QC_INSTANTANEOUS
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_VAL
| | | | +-tag: tagQuantityCharacteristicID value: ID_QC_PEAK
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_MAX
| | | +-Collection -- tag: tagOneSeriesDefn (level 4)
| | | | +-tag: tagQuantityCharacteristicID value: ID_QC_PEAK
| | | | +-tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_MIN
Figure 4: Required Fields for a Triggered Transient Voltage Channel (VA)

There are no special requirements for characterization of transient events in the monitor settings
beyond tagNominalFrequency giving the base frequency for the system monitored.
Observation Record
Observation records carry the actual data for an event or trend of steady state data. For transient event
data, the observation needs certain time stamp information for the record including the start time for
the record and the trigger time that usually is some time after the beginning of the record. For event
records, the trigger information is very important and is required for full characterization of the data.
The peak channels are optional and are used to hold peak values of the signal between the individual
samples of the waveform. By our convention, these values include low frequency information. The max
series hold the positive going peak value and the min series hold the negative going peak. The values in
the peak series are interpreted as follows. If full series of values (one peak value for each entry in the
waveform value series) are present then the peak data is analyzed as each point being the peak in the
previous time interval. If only one point is present in each of the peak series, those values are assumed
to be at the trigger time indicated by the tagTimeTriggered tag. The peak characteristics for the
transient are determined by these peak channels, if they are present.

Figure 5 is a sample transient data observation record. Trigger information is extremely important for
complete characterization of the data. Note that the tagSeriesBaseQuantity tags are not really needed
as the tagSeriesNominalQuantity from the data source record provides the correct value.
-tag: tagRecObservation (level 0)
+- tag: tagTimeCreate value: 9/15/1999 20:31:33.000000000
+- tag: tagTimeStart value: 9/15/1999 20:28:15.537302083
+- tag: tagTimeTriggered value: 9/15/1999 20:28:15.561000000
+- tag: tagTriggerMethodID value: ID_TRIGGER_METH_CHANNEL
+- tag: tagChannelTriggerIdx values: 4 Trigger was on channel defn. 4 in data source
+- tag: tagChannelInstances (level 1)
| +- tag: tagOneChannelInst (level 2)
| | +- tag: tagChannelDefnIdx value: 4 References the channel defn. in data source
| | +- tag: tagChannelFrequency value: 60.000000
| | +- tag: tagSeriesInstances (level 3)
| | | +- tag: tagOneSeriesInstance (level 4) Series 0, Time
| | | | +- tag: tagSeriesOffset value: 0.000000
| | | | +- tag: tagSeriesScale: 0.000130
| | | | +- tag: tagSeriesValues (type: INTEGER2) [ 3 ]
| | | +- tag: tagOneSeriesInstance (level 4) Series 1, Voltage waveform
| | | | +- tag: tagSeriesBaseQuantity value: 678.822510
| | | | +- tag: tagSeriesScale value: 0.100000
| | | +- tag: tagOneSeriesInstance (level 4) Series 2, Positive Peaks
| | | | +- tag: tagSeriesOffset: 0.000000
| | | +- tag: tagOneSeriesInstance (level 4) Series 3, Negative Peaks
Figure 5: Sample Transient Data Observation Record
Trend Data
Trend data records give long-term steady-state trends of any quantity that PQView recognizes. The
table of channels accepted by PQView is given in Table 1. In general, trend data is indicated by
specifying a trigger method of ID_TRIGGER_METH_PERIODIC in the observation record and specifying a
quantity type of ID_QT_VALUELOG in the data source definition for the channel.
Trend data can be stored in several ways. The simplest of these would have just a series of
instantaneous values collected over time. These values could be the average value of the variable over
the time interval. In addition, the minimum and maximum values over the interval can be captured.

The data source definitions for trend data are similar to the previous types discussed thus far. Typically,
there is a time series definition followed by one or more series to hold the data for the channel.

Figure 6 shows a record fragment that displays the definition for phase A rms voltage trend with
minimum, maximum, and average value series. As with all data source voltage-based channels
definitions, it is recommended to include the base voltage for the record. While the characterizer does
not currently use that information, it is passed on to PQView for steady state analysis such as voltage
regulation.
| | +- tag: tagChannelName value: 'SS RMS VAN'
| | +- tag: tagPhaseID value: ID_PHASE_AN
| | +- tag: tagQuantityMeasuredID value: ID_QM_VOLTAGE
| | +- tag: tagQuantityTypeID value: ID_QT_VALUELOG
| | +- tag: tagSeriesDefns (level 3)
| | | | +- tag: tagValueTypeID valueID_SERIES_VALUE_TYPE_MIN
| | | | +- tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_MAX
| | | +-Collection -- tag: tagOneSeriesDefn (level 4)
| | | | +- tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_AVG
Figure 6: PQDIF Data Source Record Fragment – Definition for Phase A RMS Voltage Trend

There are no special requirements for characterization of trend data in the monitor settings beyond
tagNominalFrequency giving the base frequency for the system monitored.
Observation Record
Observation records carry the actual data for an event or trend of steady state data. For waveform
snapshot data, the observation needs certain time stamp information for the record and the
ID_TRIGGER_METHOD_PERIODIC tag.
Figure 7 is a fragment of a sample periodic triggered waveform data observation record. Note that the
tagSeriesBaseQuantity tags, if specified, supersede the value specified by tagSeriesNominalQuantity in
the data source record. The tagSeriesNominalQuantity represents the declared nominal for the
measurement location, whereas the tagSeriesBaseQuantity represents the actual base value existing at

the time of the observation measurement. These can be different for instruments that support features
such as floating base voltages for triggering purposes.
+- tag: tagObservationName value: 'Steady-state trend'
+- tag: tagTriggerMethodID value: ID_TRIGGER_METH_PERIODIC
| | +- tag: tagChannelDefnIdx value: 26
| | | +- tag: tagOneSeriesInstance (level 4)
| | | | +- tag: tagSeriesValues (type: REAL4) [ 96 ]
| | | +-Collection -- tag: tagOneSeriesInstance (level 4)
Figure 7: Sample Fragment of Periodic Triggered Waveform Data Observation Record
Mapping between PQView Steady State Channels and IEEE PQDIF Value Log
Table 1 presents the PQDIF GUID and ID values that should be specified in a PQDIF data source channel
definition record in order to map value logs to PQView steady-state samples. Additionally, the PQDIF
channel definition record should to specify a PQDIF phase ID (e.g., ID_PHASE_AN, ID_PHASE_AB,
ID_PHASE_NET, etc.) and a PQDIF value type ID (i.e., ID_SERIES_VALUE_TYPE_MIN,
ID_SERIES_VALUE_TYPE_MAX, ID_SERIES_VALUE_TYPE_AVG, or ID_SERIES_VALUE_TYPE_VAL).
Table 1: Map between PQView Steady-State records and PQDIF Value Log GUID
and ID Channel Definition Values
PQView PQView PQDIF Quantity PQDIF Quantity Recommend PQDIF

Channel Channel Measured ID Characteristic ID Quantity Units
ID Name
4144 V Peak ID_QM_VOLTAGE ID_QC_PEAK ID_QU_VOLTS
4160 V RMS ID_QM_VOLTAGE ID_QC_RMS ID_QU_VOLTS
4176 V HRMS ID_QM_VOLTAGE ID_QC_HRMS ID_QU_VOLTS
4192 V THD ID_QM_VOLTAGE ID_QC_TOTAL_THD ID_QU_NONE
4208 V ETHD ID_QM_VOLTAGE ID_QC_EVEN_THD ID_QU_NONE
4224 V OTHD ID_QM_VOLTAGE ID_QC_ODD_THD ID_QU_NONE
4256 V CF ID_QM_VOLTAGE ID_QC_CREST_FACTOR ID_QU_NONE
4272 V FF ID_QM_VOLTAGE ID_QC_FORM_FACTOR ID_QU_NONE
4288 V AS ID_QM_VOLTAGE ID_QC_ARITH_SUM ID_QU_VOLTS
4304 V S0/S1 ID_QM_VOLTAGE ID_QC_S0S1 ID_QU_NONE
4320 V S2/S1 ID_QM_VOLTAGE ID_QC_S2S1 ID_QU_NONE

4336 V SPOS ID_QM_VOLTAGE ID_QC_SPOS ID_QU_VOLTS

4352 V TIF ID_QM_VOLTAGE ID_QC_TIF ID_QU_NONE
4368 V Flicker RMS ID_QM_VOLTAGE ID_QC_FLKR_MAG_AVG ID_QU_VOLTS
4384 V Flicker dV/V ID_QM_VOLTAGE ID_QC_FLKR_MAX_DVV ID_QU_NONE
4400 V Flicker Frequency ID_QM_VOLTAGE ID_QC_FLKR_FREQ_MAX ID_QU_HERTZ
4416 V Flicker Magnitude ID_QM_VOLTAGE ID_QC_FLKR_MAG_MAX ID_QU_VOLTS
4432 V Flicker SWA ID_QM_VOLTAGE ID_QC_FLKR_WGT_AVG ID_QU_NONE
4448 V Flicker(f) ID_QM_VOLTAGE ID_QC_FLKR_SPECTRUM ID_QU_NONE
4464 V SNEG ID_QM_VOLTAGE ID_QC_SNEG ID_QU_VOLTS
4480 V SZERO ID_QM_VOLTAGE ID_QC_SZERO ID_QU_VOLTS
4496 V Flicker Pst ID_QM_VOLTAGE ID_QC_FLKR_PST ID_QU_NONE
4512 V Flicker Plt ID_QM_VOLTAGE ID_QC_FLKR_PLT ID_QU_NONE
4528 V TIF RMS ID_QM_VOLTAGE ID_QC_TIF_RMS ID_QU_NONE
4544 V Flicker Plt Slide ID_QM_VOLTAGE ID_QC_FLKR_PLTSLIDE ID_QU_NONE
4768 V THD RMS ID_QM_VOLTAGE ID_QC_TOTAL_THD_RMS ID_QU_NONE
4784 V THD RMS Odd ID_QM_VOLTAGE ID_QC_ODD_THD_RMS ID_QU_NONE
4800 V THD RMS Even ID_QM_VOLTAGE ID_QC_EVEN_THD_RMS ID_QU_NONE
4816 V TID ID_QM_VOLTAGE ID_QC_TID ID_QU_NONE
4832 V TID RMS ID_QM_VOLTAGE ID_QC_TID_RMS ID_QU_NONE
4848 V Interharmonic RMS ID_QM_VOLTAGE ID_QC_IHRMS ID_QU_VOLTS
5120 V Imbalance ID_QM_VOLTAGE ID_QC_AVG_IMBAL ID_QU_NONE
5536 V Phase Angle ID_QM_VOLTAGE ID_QC_ANGLE_FUND ID_QU_DEGREES
8240 I Peak ID_QM_CURRENT ID_QC_PEAK ID_QU_AMPS
8256 I RMS ID_QM_CURRENT ID_QC_RMS ID_QU_AMPS
8272 I HRMS ID_QM_CURRENT ID_QC_HRMS ID_QU_AMPS
8288 I THD ID_QM_CURRENT ID_QC_TOTAL_THD ID_QU_NONE
8304 I ETHD ID_QM_CURRENT ID_QC_EVEN_THD ID_QU_NONE
8320 I OTHD ID_QM_VOLTAGE ID_QC_ODD_THD ID_QU_NONE
8352 I CF ID_QM_CURRENT ID_QC_CREST_FACTOR ID_QU_NONE
8368 I FF ID_QM_CURRENT ID_QC_FORM_FACTOR ID_QU_NONE
8384 I AS ID_QM_CURRENT ID_QC_ARITH_SUM ID_QU_AMPS
8400 I S0/S1 ID_QM_CURRENT ID_QC_S0S1 ID_QU_NONE
8416 I S2/S1 ID_QM_CURRENT ID_QC_S2S1 ID_QU_NONE
8432 I SPOS ID_QM_CURRENT ID_QC_SPOS ID_QU_AMPS
8448 I TIF ID_QM_CURRENT ID_QC_TIF ID_QU_AMPS
8560 I SNEG ID_QM_CURRENT ID_QC_SNEG ID_QU_AMPS
8576 I ZERO ID_QM_CURRENT ID_QC_SZERO ID_QU_AMPS
8624 I TIF RMS ID_QM_CURRENT ID_QC_TIF_RMS ID_QU_AMPS
8704 IT ID_QM_CURRENT ID_QC_IT ID_QU_NONE
8720 I Demand ID_QM_CURRENT ID_QC_RMS_DEMAND ID_QU_AMPS
8736 ANSI TDF ID_QM_CURRENT ID_QC_ANSI_TDF ID_QU_NONE
8752 K Factor ID_QM_CURRENT ID_QC_K_FACTOR ID_QU_NONE
8768 TDD ID_QM_CURRENT ID_QC_TDD ID_QU_NONE
8784 I RMS Peak Demand ID_QM_CURRENT ID_QC_RMS_PEAK_DEMAND ID_QU_AMPS
8864 I THD RMS ID_QM_CURRENT ID_QC_TOTAL_THD_RMS ID_QU_NONE
8880 I THD RMS Odd ID_QM_CURRENT ID_QC_ODD_THD_RMS ID_QU_NONE
8896 I THD RMS Even ID_QM_CURRENT ID_QC_EVEN_THD_RMS ID_QU_NONE
8912 I TID ID_QM_CURRENT ID_QC_TID ID_QU_NONE
8928 I TID RMS ID_QM_CURRENT ID_QC_TID ID_QU_NONE
8944 I Interharmonic RMS ID_QM_CURRENT ID_QC_HRMS ID_QU_AMPS
9216 I Imbalance ID_QM_CURRENT ID_QC_AVG_IMBAL ID_QU_NONE
9632 I Phase Angle ID_QM_CURRENT ID_QC_ANGLE_FUND ID_QU_DEGREES
13056 P ID_QM_POWER ID_QC_P ID_QU_WATTS
13072 Q ID_QM_POWER ID_QC_Q ID_QU_VARS
13088 S ID_QM_POWER ID_QC_S ID_QU_VA
13104 PF ID_QM_POWER ID_QC_PF ID_QU_NONE
13120 DF ID_QM_POWER ID_QC_DF ID_QU_NONE
13136 P Demand ID_QM_POWER ID_QC_P_DEMAND ID_QU_WATTS
13152 Q Demand ID_QM_POWER ID_QC_Q_DEMAND ID_QU_VARS
13168 S Demand ID_QM_POWER ID_QC_S_DEMAND ID_QU_VA
13184 DF Demand ID_QM_POWER ID_QC_DF_DEMAND ID_QU_NONE
13200 PF Demand ID_QM_POWER ID_QC_PF_DEMAND ID_QU_NONE
13216 P Pred Demand ID_QM_POWER ID_QC_P_PRED_DEMAND ID_QU_WATTS

13232 Q Pred Demand ID_QM_POWER ID_QC_Q_PRED_DEMAND ID_QU_VARS

13248 S Pred Demand ID_QM_POWER ID_QC_S_PRED_DEMAND ID_QU_VA
13568 P Coincident with Q ID_QM_POWER ID_QC_P_CO_Q_DEMAND ID_QU_WATTS
13584 P Coincident with S ID_QM_POWER ID_QC_P_CO_S_DEMAND ID_QU_WATTS
13600 Q Coincident with P ID_QM_POWER ID_QC_Q_CO_P_DEMAND ID_QU_VARS
13616 Q Coincident with S ID_QM_POWER ID_QC_Q_CO_S_DEMAND ID_QU_VARS
13632 PF Coincident with P ID_QM_POWER ID_QC_PF_CO_P_DEMAND ID_QU_NONE
13648 PF Coincident with Q ID_QM_POWER ID_QC_PF_CO_Q_DEMAND ID_QU_NONE
13664 S Coincident with P ID_QM_POWER ID_QC_S_CO_P_DEMAND ID_QU_VA
13680 S Coincident with Q ID_QM_POWER ID_QC_S_CO_Q_DEMAND ID_QU_VA
13696 DF Coincident with S ID_QM_POWER ID_QC_DF_CO_S_DEMAND ID_QU_NONE
13712 PF Coincident with S ID_QM_POWER ID_QC_PF_CO_S_DEMAND ID_QU_NONE
13728 Power Angle Fund ID_QM_POWER ID_QC_ANGLE_FUND ID_QU_DEGREES
13744 Q Fund ID_QM_POWER ID_QC_Q_FUND ID_QU_VARS
13760 S Fund ID_QM_POWER ID_QC_S_FUND ID_QU_VA
13776 PF Vector ID_QM_POWER ID_QC_PF_VECTOR ID_QU_NONE
13792 DF Vector ID_QM_POWER ID_QC_DF_VECTOR ID_QU_NONE
13808 S Vector ID_QM_POWER ID_QC_S_VECTOR ID_QU_VA
13824 S VectorFund ID_QM_POWER ID_QC_S_VECTOR_FUND ID_QU_VA
13840 PF Arith ID_QM_POWER ID_QC_PF_ARITH ID_QU_NONE
13856 DF Arith ID_QM_POWER ID_QC_DF_ARITH ID_QU_NONE
13872 S Arith ID_QM_POWER ID_QC_S_ARITH ID_QU_VA
13888 S ArithFund ID_QM_POWER ID_QC_S_ARITH_FUND ID_QU_VA
13904 P Harmonic ID_QM_POWER ID_QC_P_HARMONIC ID_QU_WATTS
13920 P Harmonic Unsigned ID_QM_POWER ID_QC_P_HARMONIC ID_QU_WATTS
_UNSIGNED
14320 P Fund ID_QM_POWER ID_QC_P_FUND ID_QU_WATTS
21520 P Integrated ID_QM_ENERGY ID_QC_P_INTG ID_QU_WATTHOURS
21536 P Integrated Pos ID_QM_ENERGY ID_QC_P_INTG_POS ID_QU_WATTHOURS
21552 P Integrated Neg ID_QM_ENERGY ID_QC_P_INTG_NEG ID_QU_WATTHOURS
21568 Q Integrated ID_QM_ENERGY ID_QC_Q_INTG ID_QU_VARHOURS
21584 Q Integrated Pos ID_QM_ENERGY ID_QC_Q_INTG_POS ID_QU_VARHOURS
21600 Q Integrated Neg ID_QM_ENERGY ID_QC_Q_INTG_NEG ID_QU_VARHOURS
21616 S Integrated ID_QM_ENERGY ID_QC_S_INTG ID_QU_VAHOURS
21632 P Integrated Pos Fund ID_QM_ENERGY ID_QC_P_INTG_POS_FUND ID_QU_WATTHOURS
21648 P Integrated Neg Fund ID_QM_ENERGY ID_QC_P_INTG_NEG_FUND ID_QU_WATTHOURS
21664 Q Integrated Pos Fund ID_QM_ENERGY ID_QC_Q_INTG_POS_FUND ID_QU_VARHOURS
21680 Q Integrated Neg Fund ID_QM_ENERGY ID_QC_Q_INTG_NEG_FUND ID_QU_VARHOURS
21696 S Integrated Fund ID_QM_ENERGY ID_QC_S_INTG_FUND ID_QU_VAHOURS
21712 P Interval Integrated ID_QM_ENERGY ID_QC_P_IVL_INTG ID_QU_WATTHOURS
21728 P Interval Integrated ID_QM_ENERGY ID_QC_P_IVL_INTG_POS ID_QU_WATTHOURS
Pos
21744 P Interval Integrated ID_QM_ENERGY ID_QC_P_IVL_INTG_NEG ID_QU_WATTHOURS
Neg
22128 Q Interval Integrated ID_QM_ENERGY ID_QC_Q_IVL_INTG ID_QU_VARHOURS
22144 Q Interval Integrated ID_QM_ENERGY ID_QC_Q_IVL_INTG_POS ID_QU_VARHOURS
Pos
22160 Q Interval Integrated ID_QM_ENERGY ID_QC_Q_IVL_INTG_NEG ID_QU_VARHOURS
Neg
22176 S Interval Integrated ID_QM_ENERGY ID_QC_S_IVL_INTG ID_QU_VAHOURS
22192 P Interval Integrated ID_QM_ENERGY ID_QC_P_IVL_INTG_POS_FUND ID_QU_WATTHOURS
Pos Fund
22208 P Interval Integrated ID_QM_ENERGY ID_QC_P_IVL_INTG_NEG_FUND ID_QU_WATTHOURS
Neg Fund
22224 Q Interval Integrated ID_QM_ENERGY ID_QC_Q_IVL_INTG_POS_FUND ID_QU_VARHOURS
Pos Fund
22240 Q Interval Integrated ID_QM_ENERGY ID_QC_Q_IVL_INTG_NEG_FUND ID_QU_VARHOURS
Neg Fund
22256 S Interval Integrated ID_QM_ENERGY ID_QC_S_IVL_INTG_FUND ID_QU_VAHOURS
Fund

Waveform Snapshots
Steady-state data can also be derived from periodic snapshots of voltage and current waveforms. The
PQView PQDIF characterizer can process these waveforms to give a full set of steady-state quantities
and pass them through to the database. Note that as of version 3.42 of the characterizer, only one cycle
of data is analyzed, and that for full processing the number of points per cycle must be a power of 2
between 32 and 4096 points.
Waveform snapshot records are indicated to the PQDIF characterizer by the use of the
ID_TRIGGER_METH_PERIODIC tag in the observation record and the ID_QT_WAVEFORM tag in the
definition.

The Data Source definition for waveform snapshots includes a time series and a value series for each
channel. The data source record fragment below shows the definition for Phase A voltage waveform
snapshot with time and value series.
| | +- tag: tagChannelName (value: 'Waveform VA'
| | +- tag: tagPhaseID value: ID_PHASE_AN
| | +- tag: tagQuantityMeasuredID value: ID_QM_VOLTAGE
| | +- tag: tagQuantityTypeID value: ID_QT_WAVEFORM
| | +- tag: tagSeriesDefns (level 3)
| | | | +- tag: tagQuantityCharacteristicID value: ID_QC_ INSTANTANEOUS
| | | | +- tag: tagQuantityCharacteristicID value: ID_QC_INSTANTANEOUS
| | | | +- tag: tagValueTypeID value: ID_SERIES_VALUE_TYPE_VAL
Figure 8: Record Fragment of Definition for Phase A Voltage Waveform Snapshot with Time
There are no special requirements for characterization of snapshot waveform data in the monitor
settings beyond tagNominalFrequency giving the base frequency for the system monitored.
Observation Record
A sample observation record for a waveform snapshot is shown in Figure 9.
+- tag: tagObservationName value: 'Snapshot'
+- tag: tagTriggerMethodID value: 2
| | +- tag: tagChannelDefnIdx value: 2
| | +- tag: tagSeriesBaseQuantity value: 678.822510
| | +- tag: tagChannelFrequency value: 60.000000


Figure 9: Sample Record of a Waveform Snapshot
Legal Information
“PQView”, “Electrotek Concepts” are registered trademarks of Electrotek Concepts, Inc. “EPRI” is
registered trademark of the Electric Power Research Institute, Inc. “IEEE” is a registered trademark of
the Institute of Electrical and Electronics Engineers.

Transformer Losses Calculation

Uploaded by

Copyright:

Available Formats

Transformer Losses Calculation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transformer Losses Calculation

Uploaded by

Copyright:

Available Formats

Using IEEE® PQDIF Data Sources with

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 2

PQView’s PQDIF Characterizer

Data Processed by the PQDIF Characterizer

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 3

PQDIF Tags Required by PQView that are Optional in IEEE 1159.3

Tag Record Comment Required

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 4

PQView. Specifically, it is stored in the

tagSeriesNominalQuantity Data Source This tag should be defined in order to Required

Data Types Ignored

RMS Triggered Events Records

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 5

Data Source Definition

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 6

| | | | +-tag: tagStorageMethodID value: 3

The channel definitions repeat to include all recorded phases.

Figure 1: Required Tags for Triggered RMS Variation Event.

Monitor Settings Record

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 7

Waveform Channels with RMS Triggered Data

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 8

Waveform Samples with No RMS

Data Source Definition

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 9

| +-tag: tagOneChannelDefn (level 2)

Monitor Settings Record

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 10

Data Source Definition

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 11

Monitor Settings Record

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 12

PQView PQView PQDIF Quantity PQDIF Quantity Recommend PQDIF

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 13

4336 V SPOS ID_QM_VOLTAGE ID_QC_SPOS ID_QU_VOLTS

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 14

13232 Q Pred Demand ID_QM_POWER ID_QC_Q_PRED_DEMAND ID_QU_VARS

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 15

Data Source Definition

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 16

| | | | +- tag: tagSeriesOffset value: 0.000000

Copyright© 2013 Electrotek Concepts, Inc. All rights reserved. Page 17

You might also like