Embed Size (px)
Citation preview
1
Vectren Experience with
MOD-033
Larry Rogers
Manager, Transmission System Operations(TSO)
Vectren Energy Delivery
Evansville, Indiana
Vectren at a glance
• Fortune 1000 company, Headquarter in Evansville, Indiana
• Gas & Electric Investor Owned Utility (IOU)(NSE: VVC)
• Indiana is not a degregulated state• Vectren Transmission System Operations –
Local BA, TO/TOP, TP, GO/GOP, LSE, DP, MP
• Vectren Power Supply, ALCOA, AMP - GOPs
• Midcontinent ISO - RC and BA
• ReliabilityFirst - NERC Regional Entity
• 65 miles 345kV, 350 miles 138kV lines, and
550 miles 69kV lines
• 50 Transmission Stations
• 140,000 Electric Customers - SW Indiana
• 1 Million Gas Customers - Indiana and Ohio
Generation and Load
Peak Load - 1,850 MW (Summer)
Total Resources – 1,866 MW
Interconnections
Big Rivers Electric Corporation
Duke Energy Midwest
LG&E/KU
Hoosier Energy REC
Indianapolis Power and Light
Topics to cover today
• How Vectren builds Planning Models
• How Vectren builds Operational Models
• How Vectren checks model validity
– Steady State
– Short Circuit
– Dynamics
3
Vectren’s Elec. Transmission Planning Modeling Process
Transmission
Planning
Steady State
Short Circuit
DynamicsTransmission
Owners (TO)
Lines (PLS-CAD),
transformers (test
sheets), shunts,
Ratings, GIS data.
Generator Owners
(GO’s - multiple)
Generation
add/retire/dispatch
interchange
Transmission
Operator (TOP)
SCADA and EMS,
Pi Historian
Planning Authority (PA-
MISO)
Model On Demand
(MOD), MTEP, GI,
TSR
Reliability Coordinator (RC-
MISO)
Webtool, Network model,
Commercial Model, Op-
Guides, Flowgates
Reliability Entity (RE-
Reliability First)
MMWG, Seasonal
Assesments, Near term &
Long Term plans
IURC (Resource
Planning)
Integrated
Resource Plan
NERC MOD-
010 & 012
Validation
Base Cases
Neighbor TO’s
(multiple)
Tie lines,
interchange
Inputs
Relay Protection (TO)
Disturbance data, DFR’s,
DDR’s, PMU’s
Load Serving Entities
(LSE’s-multiple)
Actual load (Meter
values), UFLS, and
future load forecast
Outputs
NERC MOD-
026, 027 & 033
NERC TPL-001
thru 004
NERC TOP-002
thru 008
Vectren’s Elec. Transmission Operations Modeling Process
Transmission
Real-Time
Operations
SCADA – Real
time, alarms,
gross meas. errSubstation RTU’s
Equipment status,
flows, voltages,
alarms, frequency,
GPS clocks
Generator Owners
(GO’s - multiple)
Generation status
and forecasts
Transmission
Planning (TP)
Ratings and
connectivity
MISO Settelments
nMarket Reports,
Energy reports and
billing
Distribution System
Operations (DSO)
SCADA, OMS
MISO (RC)
ICCP data for outside
areas and generation set-
points
Validation
Neighbor TO’s
(multiple)
Tie line checkout,
(metered ties)
Inputs
PI Historian
All real-time archives
Load forecasts and
(LSE’s)
1) Pattern Recognition
Technologies
2) Internal ABB STLF
Nostradamus (future)
Outputs
State Estimation
(SE & CA) model
Dispatcher Load
Flow (DLF) –
Operational
Horizon
Simulation (EPRI)
Black start
validation
NERC EOP-005
NERC MOD-033
Vectren’s Steady State Model Validation Process
• Validate EMS Model to real-time SCADA flows & voltages.
• EMS model that does not solve “is” an indicator of a model
error
• But EMS model that does solve “is not” an indicator of a valid
model. Solution values must be checked against real-time
values or some event.
• Vectren considers values valid if within these tolerances:
• MW & MVAR each within 3% of facility rating (lines &
transformers) with no contingencies.
(Vectren started with largest errors with the gross
measurement error tool and started between 5-10% error.)
Most values are within 1%.
• MW & MVAR each within 5% of facility rating (lines &
transformers) with contingency analysis prior to switching
compared to post switching values.
• Voltages within 1% of nominal voltage
Vectren’s Steady State Model Validation Process
• PSS/e case compare EMS operational model snapshot to
Planning model to check exact match for R, X, B, Rate A, Rate B,
connectivity, & Out of service facilities (status).
• PSS/e case compare same cases to confirm total load, load
profile, generation dispatch, and net interchange “reasonably
represents” accurate time period for the models.
Example: a single commercial load normally varies daily
between 12-18MVA. When the EMS model snapshot was
exported the load was at 12MVA. The planning model contains
16MVA at that load. The load does not have to be exact as long
as it represents expectation. A peak model may be closer to
18MVA value and an off peak model may be closer to the
12MVA value. The load is commercial and may be non-
conforming and remain at 16MVA for all time periods.
8
Real-Time Raw
Values
EMS Solved Case
Values
4MW/3MVAR
error on Line with
~300MVA rating
7MW/7MVAR error
on Line with
~300MVA rating
2MW/5MVAR error on
XFMr with ~150MVA
Rating (tap difference)1kV Voltage error
at 138kV bus
Vectren’s Short Circuit Model Validation Process
• Planning engineers manually compare peak Planning model to
Aspen Short Circuit base model to check exact match for bus
names and numbers, R, X, B, Rate A, Rate B, connectivity, & Out
of service facilities (status).
This is somewhat difficult because comparing negative, zero,
and positive sequence data that is not a consistent data format
in each software application (PSS/e vs. Aspen).
• Planning Engineers manually compare all facilities match the
Aspen line property database and that the line database matches
the PLS-CAD detailed design and ESRI GIS system data.
• Relay engineers enter relays to link to Aspen relay database to
reflect most accurate base cases during peak conditions.
• Relay engineers copy the base model for specific conditions
during events to compare event fault data to a simulated fault in
the short circuit model and notify planning engineers of any
suspected issues. Accuracy at the descretion of the relay
engineers.
• Engineers keep periodic historical models to allow relay engineers
to go back and see model conditions that relay settings were likely
developed. Useful for mis-operation reviews.
Vectren’s Dynamic Model Validation Process
Generator Owners
(GO’s - multiple)
Go’s submit initial
equipment data to
TP
Transmission Operator
(TOP)
Notifies that fault or
dynamic event occured
MMWG
Consolidates multiple TPs
data
Transmission Planner
(TP)
Develops Dynamic Base
cases for reference using
steady state topology.
Generation Operator
If no event occurs or
data is not captured,
coordinates test per
MOD-026&027
Base Cases
Relay Protection (TO)
Disturbance data
collected from Relays,
DFR’s, DDR’s, PMU’s
Load Serving
Entities (LSE’s-
multiple)
LSE’s submit
loads to TP
Transmission Planner
(TP)
Conducts simulation of
event to validate model
(valid or not valid)
Other validation checks• Does the model adequately reflect actual events
within reason. Specifically, stable or not stable
within similar number of cycles/seconds.
11
