Distribution

Management Systems

Presented By:
Bob Uluski
Electric Power Research Institute

CRN Summit
Cleveland Ohio
July 20, 2011
•What is a DMS?
•Key Applications
•Planning, Procuring,
and Implementing a
new DMS
•Open discussion

2
 What is a DMS?

• A Decision Support
System to assist the
control room and field
operating personnel with
the monitoring and
control of the electric
distribution system in an
optimal manner while
improving safety and
asset protection

3
What are the Major DMS Components?

4
Distribution Management System Components
SCADA provides the foundation
Field Devices

Switched Cap
Banks
Line regulators
Line switches
Real
Time Faulted circuit
Indicators
(FCIs)
Distribution DG, Energy
SCADA storage

Substation Switched
Cap Banks
Real
•Real time data
acquisition Time CBs, MODs
•Basic operational
alerts (alarms) Vreg/LTC
•Remote control
Subs secondary
•Tagging
equip
•Display real time
data
•Data archiving
Substation
Devices

5
Distribution Management System Components
DMS Applications Use SCADA Capabilities
Field Devices

Switched Cap
Banks
Line regulators
Line switches
Real
Time Faulted circuit
Indicators
(FCIs)
Advanced Distribution DG, Energy
Applications SCADA storage

Substation Switched
Cap Banks
Real
•Intelligent alarm •Real time data
processing acquisition Time CBs, MODs
•On-line power flow •Basic operational
alerts (alarms) Vreg/LTC
•State estimation
•Remote control
•Distribution model Subs secondary
•Tagging
•Switch order mgmt equip
•Display real time
•VVO data
•FLISR/ONR •Data archiving
Substation
•Contingency Analysis Devices
•DER Management

6
Distribution Management System Components
Interactions with Operational Support Systems
Field Devices

Near
Mobile Data Switched Cap
Advanced Real System Banks
Time,
Metering “day (MDS) Line regulators
after”
System
Line switches
(AMI) Switch orders,
R-T data
Real
Temp Time Faulted circuit
Model Indicators
updates
Outage (FCIs)

Management Predicted Advanced Distribution DG, Energy

System (OMS)
outages
Applications SCADA storage

Substation Switched
Cap Banks
Real
•Intelligent alarm •Real time data
Time
Geographic processing acquisition CBs, MODs
“As •On-line power flow •Basic operational
Information engineered” •State estimation
alerts (alarms) Vreg/LTC
•Remote control
System (GIS) state of the
system
•Distribution model
•Tagging
Subs secondary
•Switch order mgmt equip
•Display real time
•VVO data
•FLISR/ONR •Data archiving
Substation
•Contingency Analysis Devices
•DER Management

7
The Distribution Management System
Field Devices

Near
Mobile Data Distribution Switched Cap
Advanced Real System Management Banks
Time,
Metering “day (MDS)
after” System Line regulators
System
Line switches
(AMI) Switch orders,
R-T data
Real
Temp Time Faulted circuit
Model Indicators
updates
Outage (FCIs)

Management Predicted Advanced Distribution DG, Energy

System (OMS)
outages
Applications SCADA storage

Substation Switched
Cap Banks
Real
•Intelligent alarm •Real time data
Time
Geographic processing acquisition CBs, MODs
“As •On-line power flow •Basic operational
Information engineered” •State estimation
alerts (alarms) Vreg/LTC
•Remote control
System (GIS) state of the
system
•Distribution model
•Tagging
Subs secondary
•Switch order mgmt equip
•Display real time
•VVO data
•FLISR/ONR •Data archiving
Substation
•Contingency Analysis Devices
•DER Management

8
Combined DMS/OMS System
Field Devices

Near
Mobile Data Distribution Switched Cap
Advanced Real System Management Banks
Time,
Metering “day (MDS)
after” System Line regulators
System
Line switches
(AMI) Switch orders,
R-T data
Real
Temp Time Faulted circuit
Model Indicators
updates
Outage (FCIs)

Management Predicted Advanced Distribution DG, Energy

System (OMS)
outages
Applications SCADA storage

Substation Switched
Cap Banks
Real
•Intelligent alarm •Real time data
Time
Geographic processing acquisition CBs, MODs
“As •On-line power flow •Basic operational
Information engineered” •State estimation
alerts (alarms) Vreg/LTC
•Remote control
System (GIS) state of the
system
•Distribution model
•Tagging
Subs secondary
•Switch order mgmt equip
•Display real time
•VVO data
•FLISR/ONR •Data archiving
Substation
•Contingency Analysis Devices
•DER Management

9
 Typical Distribution Control Center a
Few Years Ago

• Distribution System was operated

manually with wall- mounted
switching diagrams
• Mostly paper driven processes

10
 Electronic Map Visualization

• Static mapboards replaced by large

screen, video displays

• Operator workstations include large

number of computer monitors
(side-by side)

11
 Current Trend in Control Center Design

• Increasing emphasis on “outside the fence”

visualization
• Large mapboards disappearing from
distribution control centers
• Use of stackable monitors for operator
workstations – allows view of specific “area of
responsibility”

12
• DMS Applications
– Basic Applications
– Advanced Applications

13
 Advanced Display Capabilities

• Standard display
capabilities
Substation One-
Line Schematic

Trend line

Tabular

14
 Advanced Display Capabilities

• Advanced display
capabilities

15
 Advanced Display Capabilities

• Topology Processing Feeder

Color

16
Highlighting abnormal sections of the
distribution feeders

17
 Intelligent Alarm Processing

• Intelligent Alarm Processing

– (Standard) Compare
measurements against
operating limits and alert
operator to abnormal conditions
– Conditional alarms
– Prioritization
– Filtering
– Routing

18
 Data Archiving

• Data Archiving
– Store and retrieve data,
alarms, event logs, feeder
configuration changes, etc
– Allow access to data inside
and outside the control center
for studies etc.
– Most DMS vendors support
interface to commercial data
management systems (e.g.,
OSI Soft PI)

19
 Tagging Permits Clearance Management

• Tagging Permits Clearance Management

– Enables users to request, manage and
plan outage requests.
– Support the creation and monitoring of
safety protection guarantees
– Information exchanged with mobile
workforce management system
– All DMS vendors support tagging – most
are weak in overall permit/tag request
and management

20
Advanced DMS Applications

21
Distribution System Model
• Accurate distribution system model is essential element of DMS
(the “heart and soul”)
• Provides basis for graphical displays and advanced applications
– Network model
– member (Load) Model…..

22
 Distribution System Model:
One Model – Two Parts

Physical Model
– Energized equipment Load Model
• wires, transformers, switches,
capacitor banks, voltage – member Load Profiles
regulators, distributed energy – Load-Voltage Sensitivities
resources
– Connections between equipment

23
Distribution System Physical Model

• Extent of physical model

– Most cases – substation transformer hi voltage side down
to distribution transformer
– Some applications (e.g. VVO) may need modeling down to
member meter

24
Distribution System Physical Model

• Three main variations for the physical model:

– As operated – reflects the current energized state of the
distribution system
– As planned – includes work-in-progress, but not yet
energized
– As it was – for “post mortem” analysis

25
 Distribution System Physical Model
• Building and updating the physical model
– “Permanent” changes from GIS
– “Temporary” changes from SCADA and by operator entry
– Need to determine source of substation model (often this
information is not maintained via GIS)
– Planned alterations and additions
• Allows utility to enter information for work that is planned or
work in progress, but not yet energized – reduced latency
when work is energized
• Allows utility to consider work in progress when planning future
outage

26
 member Load Model – Load Profile
Applications like on-line power flow (OLPF) require a means of
estimating the load at distribution service transformer Load Profile - Customer 1

Two main alternatives for member load estimation:

– Measure it directly with AMI meters 1

• Not practical to send all AMI meter data for all meter 0.8

locations to DMS in real-time each 0.6

– Estimate load using load profile information 0.4

• Load profile based on historical load surveys 0.2

• Provides percent of peak load estimate at each time of day 0

1 6 11 16 21

• Different load profile for each member class Ho ur o f D ay

• Different load profile for season and different type of day

– Weekday Comparison of Load Profiles

– Weekend 1

– Special day (holiday) 0.8

Customer 1
Estimate reactive power consumption at each transformer via
0.6
Customer 2
0.4

reactive power profile or fixed power factor 0.2

11

13

15

17

19

21

23
1

9
Hour of Day

27
 member Load Model – Load Voltage Sensitivity

• Load profile information provides load estimate at nominal voltage (120 V)

• Need model of member load (real and reactive) variation with voltage – varies with time
of day, day of week, weather conditions, mix of appliances, and other factors
• EPRI working with IEEE PES Volt-VAR task Force to create standard library of member
load-voltage sensitivity models

Effect of voltage reduction

28
 Distribution System Model – DMS Perspective

Issues TYPICAL BAD DATA

– Data quality: bad data, incorrect Conductor electrical data
phasing Switchgear electrical data
– Lack of data in GIS for Transformer data missing (voltage,
substations and secondary windings, etc.)
circuits Equipment voltage/phase not matching
– Standard models (e.g., Common topology
Information Model)”?
Connectivity errors
– Lack of accurate member load Duplicate lines
models (Load and load-voltage
sensitivity) Loops without switches
Segments not connected
– Modeling of distributed energy
resources (“negative load” versus Multiple sources
“fully dynamic” model) Devices not connected
Wrong coordinates

29
 On Line Power Flow (OLPF)
• Similar to engineering analysis tool
– Engineering tool – peak load analysis
– OLPF – what’s happening in “near real time
• Calculates electrical conditions right now
(near real-time) at all points on the
distribution feeder
• Provides “visibility” in places where no
measurements exist …. alerts dispatcher to
trouble spots
• OLPF used by many DMS applications that
require up-to date electrical information
• Characteristics:
– 3 phase unbalanced
– Handles radial and “weakly-meshed” distribution
feeders
• “Study mode” - uses past or planned feeder
model in off line mode

30
 On Line Power Flow (OLPF)
• Similar to engineering analysis tool
– Engineering tool – peak load analysis
– OLPF – what’s happening in “near real time
• Calculates electrical conditions right now
(near real-time) at all points on the
distribution feeder
• Provides “visibility” in places where no
measurements exist …. alerts dispatcher to
trouble spots
• OLPF used by many DMS applications that
require up-to date electrical information
• Characteristics:
– 3 phase unbalanced
– Handles radial and “weakly-meshed” distribution
feeders
• “Study mode” - uses past or planned feeder
model in off line mode

31
 OLPF Study Mode
• “Off line” version of DMS power flow useful for
analyzing:
– Past events
– Upcoming (future) events
• Runs in background – does not impact real-time
(live) applications
• Specify time and date for which study is required
• Study mode estimates the load for past or future
events
• Potential use for all engineering analysis

32
 Load Estimation for OLPF

• OLPF uses real-time or near-real-time feeder measurements

• At many utilities, measurements available only at “head-end” of feeder
• Need more information to determine feeder powerflow

Bus
Voltage

CB R

kW
kVAR

33
 On Line Power Flow

• If you knew all the electrical impedances, could do a conventional power flow fairly easily
– Usually have a reasonably good idea of what the line impedance is
– Generally don’t know the impedance of every house –depends on which appliances are
on – changes all the time

Bus
Voltage

CB R X R X R X R X R X

XL XL XL XL
kW
kVAR RL RL RL RL

34
 On Line Power Flow
Can use kW rating of distribution service transformers to estimate
the load:
– Split measurement from head-end of feeder in proportion to kW rating of the
transformer

Bus
Voltage

CB R

kW
25kW 1 kW 25kW 1 kW 25kW 1 kW 25kW 1 kW
4 kW

Estimated load at each house = kW rating of distribution

service transformer / total connected kW = 25 / (4 * 25) = 1/4

35
 On Line Power Flow

This approach works well as long as all members have the same “load
profile” (Fraction of peak load at given time and given day)

Bus
Voltage
CB Recloser

kW 25kW 1 kW 25kW 1 kW 25kW 1 kW 25kW

4 kW 1 kW

Estimated load at each house = kW rating of distribution

service transformer / total connected kW = 25 / (4 * 25) = 1/4

36
 Using load profiles to estimate the load

Splitting load in proportion to rating of distribution service transformer works ok

if all members have the same load profile

Load Profile - Custom er 1 Load Profile - Custom er 2

1 1

0.8 0.8

0.6 0.6

0.4 0.4

0.2 0.2

0 0
1 6 11 16 21 1 6 11 16 21
Ho ur o f D ay Ho ur o f D ay

member #1 member #N

37
 Load Estimation with Different Load
Profiles
• But if load profile is different for each member, method doesn’t work
• Load estimate = kW of distribution transformer x (fraction of peak load from
load profile) / total of all members
– member 2 gets a little more of the load estimate at hours 11 and 22
– member 1 gets a higher percentage of the load during hour 18

Comparison of Load Profiles

0.8

0.6 Customer 1
Customer 2
0.4

0.2

0
11

13

15

17

19

21

23
1

Hour of Day

38
 Summary of Load Estimation Approach

• Obtain load profile for each member for given day (weekday,
weekend, special day) and season
• Determine percent of peak load for each member at given time of day
• Load Estimate For member “i” = (SCADA measurement from head
end of feeder) x (transformer rating for member “i”) x (Percent of peak
load from load profile for member “i”) / sum of ∑ (ratings of all
transformers)

39
 Use of Meter Readings from AMI
• Can use meter readings from Advanced Metering Infrastructure (AMI) to:
– Create a load profile for each member/transformer based on yesterday’s AMI data
– Determine transformer load for selected members using nearly-real-time data for
selected members

Bus
Voltage
CB Recloser

kW 25kW 1.2 kW 25kW .9 kW 25kW 1 kW 25kW

4 kW .7 kW

Meter Data
Management
System

40
 Switching Order Management

• One of the most important

operating tools – addresses
fundamental “person in charge”
duties
• Provides software tools to
assist in creating switching
orders

Paper Switch Order

41
 Switching Order Management

• Simplest form – click on

schematic display to populate
Switch order

Paper Switch Order

42
 Switching Order Management

• Simplest form – click on

schematic display to populate
switch order

• Helps to eliminate handwriting

errors

Electronic (DMS) Switch Order

43
 Switching Orders
Geographic versus Schematic Views

• When creating Switch Order off DMS

geographical display, its often difficult
to get entire, properly scaled diagram
on the screen at once
• Operators have to navigate around the
geographic display to access the
switching components (inconvenient,
time consuming)
• Some DMS Vendors offer automatic
schematic diagram generator

44
 Switching Orders
Geographic versus Schematic Views

• Schematic view removes details not Schematic View

needed for switching
– Not to scale
– Allows operator to view relevant
portion of the feeder on one
screen
• “State-of-the-art” DMS includes
automatic generation of schematic
diagrams from geographic display built
using GIS data
• Beware of “build in advance”
schematics

45
 Off-Line Validation of Switch Orders
• Allows operator to single step
through switching order in Study
Mode

• Verifies (in advance) that switching

steps do not create unacceptable
electrical conditions on the feeder

• Verify loading on adjacent feeders

for entire duration of the planned
outage work (uses short-term load
forecast)

46
 Automatic Generation of Switching Orders
• Some DMS include facility for
automatic generation of switching
orders based on established work
rules and practices

• Operator selects equipment that

needs to be worked on

• DMS supplies draft version of

switch order

47
 Volt-VAR Control and Optimization

• Develops and executes a coordinated “optimal”

switching plan for all voltage and VAR control
devices
• DMS uses OLPF program to determine what
actions to take
• Two Variations of the Model Driven Approach
– Voltage Reduction – DMS version of
Conservation Voltage Reduction
– Volt VAR Optimization (VVO) –
accomplishes one or more utility specified
“objective functions

48
 DMS Conservation Voltage Reduction (CVR)

• Voltage Reduction perform the following

activities:
– “Flatten” the voltage profile
• This allows levelized voltage drop across
the feeder
– Determine the critical voltage points
• Allows monitoring of lowest voltage point
to ensure voltage is above minimum
acceptable voltage
– Determine the necessary control
actions to accomplish CVR

49
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3846 kW
Q = 1318 kVAR

PF = .946
Losses = 96 kW

50
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Sample Rules:
1. Identify “candidate” cap banks for switching
• Cap bank “i” is currently “off”
• Rating of cap bank “i” is less than
measured reactive power flow at head end
VVO/CVR of the feeder
Processor
2. Choose the “candidate” cap bank that has the
lowest measured local voltage
RTU
3. Switch the chosen cap bank to the “ON” position

P = 3846 kW
Q = 1318 kVAR 1 2 N

PF = .946
Losses = 96 kW

51
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3846 kW
Q = 1318 kVAR Chosen
cap bank
PF = .946
Losses = 96 kW

52
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3880 kW
Q = 920 kVAR Chosen
cap bank
PF = .973
Losses = 91 kW

53
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3920 kW
Q = 687 kVAR

PF = .985
Losses = 89 kW

54
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3940 kW
Q = 532 kVAR

PF = .991
Losses = 88 kW

55
 SCADA (Rule Based) Volt-VAR Control
Part 1: VAR Control (Power Factor
Correction)
Voltage Profile Before and After

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3940 kW
Q = 532 kVAR

PF = .991
Losses = 88 kW

56
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)

Sample rule for voltage

reduction:
1. If voltage at head end of
the feeder exceeds LTC
setpoint, then lower the
VVO/CVR voltage
Processor

RTU

57
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

58
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3898 kW
Q = 508 kVAR

PF = .992
Losses = 88 kW

59
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3805 kW
Q = 508 kVAR

PF = .991 End of Line

Voltage
Losses = 88 kW Feedback

60
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)
Voltage Profile

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = 3778 kW
Q = 492 kVAR

PF = .992 End of Line

Voltage
Losses = 88 kW Feedback

61
 SCADA (Rule Based) Volt-VAR Control
Part 2: Voltage Control (CVR)
Voltage Profile Before and After

124

122

120
VVO/CVR
Processor
118

116
RTU 0 0.25 0.5 0.75 1

P = -41 kW (1.05%)
Q = -809 kVAR (61%)

PF = +.045 End of Line

Changes: Voltage
Losses = -8% Feedback

62
Volt-VAR Optimization

• Develops and executes a coordinated

“optimal” switching plan for all voltage
control devices to achieve utility-
specified objective functions:
– Minimize energy consumption
– Minimize losses
– Minimize power demand
– Combination of the above
• Can bias the results to minimize tap
changer movement and other
equipment control actions that put
additional “wear and tear” on the
physical equipment

63
 Volt VAR Optimization (VVO) System Operation
Voltage Feedback,
Accurate load data Switch
Status

Bank voltage & status,

switch control

IVVC requires real-

time monitoring &
control of sub &
feeder devices

Monitor & control tap

position, measure load
Monitor & control tap
voltage and load
position, measure load
voltage and load
Bank voltage & status,
switch control

64
 Volt VAR Optimization (VVO) System Operation

Real-Time
Cuts, jumpers, Updates
manual switching

Permanent asset changes

(line extension,
reconductor)

IVVC requires an
accurate, up-to date
electrical model

65
 Volt VAR Optimization (VVO) System Operation

OLPF calculates
losses, voltage
profile, etc

Powerflow
Results

66
 Volt VAR Optimization (VVO) System Operation

Determines optimal
set of control
actions to achieve a
desired objective

Powerflow
Results

Alternative
Switching
Plan

67
 Volt VAR Optimization (VVO) System Operation

Determines optimal
set of control
actions to achieve a
desired objective

Optimal
Switching
Plan

68
 Predictive Fault Location
• Objective: Assist field crews in pinpointing
fault location
• Fault distance provided by protective relay
IEDs not accurate:
– Assumes homogeneous wire
size/arrangement
– Fault impedance unknown
• DMS Approach:
– “Reverse short circuit” analysis
• Obtain fault magnitude and type (A,
B, C, A-B, etc) from relay IED
• Determine possible fault locations
using DMS short circuit analysis tool
and associated feeder model

69
 Fault Location Isolation & Service Restoration (FLISR)

• Fault Location, Isolation, and Service

Restoration
• Use of automated feeder switching to:
– Detect feeder faults
– Determine the fault location (between 2
switches)
– Isolate the faulted section of the feeder
(between 2 feeder switches)
– Restore service to “healthy” portions of the
feeder

70
 Nature of the Problem
• When a permanent fault occurs, members on “healthy” sections of the
feeder may experience a lengthy outage

POWER RESTORED
Feeder
member Field TO memberS ON
FAULT Reports Crews
Fault Back to
Located HEALTHY SECTIONS
OCCURS Outage On-Scene Normal
OF FEEDER
Fault Investigation Time to Perform
Travel Time & Patrol Time Manual Switching Repair Time

• FLISR provides the means to restore service to some members before

fieldminutes
5crews
– 10 arrive
15 – 30 on the scene
minutes
15 – 20
minutes
10- 15
minutes

45 – 75
minutes

71
FLISR Operation – Normal State

Substation #2 System in its normal state (no fault

exists)
5 FLISR keeping track of net load on
each section of feeder (15 minute
average measured at each DA switch)
4

Net Load
= 1 MW

3
Substation #1 Net Load Net Load Substation #3
= 2.5 MW = 2 MW

1 2 6 7 8

72
FLISR Operation – A Fault Occurs

Substation #2 Permanent fault occurs in section

surrounded by switches 2, 3 and 6
5 FDs at switches 1 and 2 detect the fault
FLISR stores net load on each feeder
section
4
FLISR logic does not yet open/close
any switches

3 No
Substation #1 Fault
Fault
Substation #3
Fault
Current
1 2 6 7 8

Fault Fault No
Fault

73
CB Trips – Feeder De-energized

Substation #2 Circuit breaker trips

Entire circuit de-energized
5
(dotted line)
FDs at switches 1 and 2
4
remain picked up
Still no FLISR control
actions
3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault Fault No
Fault

74
CB Recloses – Fault Still There

Substation #2
FDs at switches 1 and 2
5 remain picked up
Still no FLISR control
actions
4

3 No
Substation #1 Fault
Fault
Substation #3
Fault
Current
1 2 6 7 8

Fault Fault No
Fault

75
CB Trips Again – Feeder Deenergized
Circuit breaker trips and
locks out
Substation #2
Entire circuit de-energized
5
(dotted line)
FDs at switches 1 and 2
remain picked up
4
FLISR open/close logic
triggered
3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault Fault No
Fault

76
FLISR Step 1 – Identify Faulted Section

Substation #2 FDs 1 & 2 saw a fault

FDs 3 and 6 did not see the
5
fault
Fault must be in section
4
between switches 2,3, & 6

Faulted
3 No
Feeder
Substation #1 Fault
Substation #3
Section Fault
1 2 6 7 8

Fault Fault No
Fault

77
FLISR Step 2 – Isolate Faulted Section

Substation #2 Automatically open

switches 2,3, & 6
5

Faulted
3 No
Feeder
Substation #1 Fault
Substation #3
Section Fault
1 2 6 7 8

Fault Fault No
Fault

78
FLISR Step 3 – Restore “Upstream” Section

Substation #2 No need to check load for

“Upstream”
Upstream” =
“Upstream” restoration –
between
5 we know CB can carry the
substation and
first section!
faulted section
FLISR closes CB
4
FD at switch # 1 resets

Faulted
No
Feeder 3
Substation #1 Section
Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

79
FLISR Step 4 – Restore “Downstream” Section
(if possible)

Substation #2 Prior to fault, FLISR was

“Downstream”
tracking load in each
= between
5 section (15 min average)
faulted section
and end of FLISR now determines
feeder currently available capacity
4 on Substation #2

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

80
FLISR Step 4 – Restore “Downstream” Section
(if possible)

Substation #2 Compare available capacity

with pre-fault load
Available
Capacity 5
= 2 MW
Available capacity on
substation #2 > pre-fault
load in section 3-4
4
Net Okay to transfer this portion
Load =
1 MW of the downstream load
3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

81
FLISR Step 4 – Restore “Downstream” Load
(If Possible)

Substation #2 Substation #2 currently has

capacity – it can carry
Available
Capacity 5 additional load
= 1 MW
Close switch 4 to pick up
part of faulted feeder
4
Net
Load =
1 MW

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

82
FLISR Step 5 – Restore “Downstream” Load
(continued)
Now check available capacity on
Substation #2 Substation #3
Compare with pre-fault net load on
5 section 6-7
Net load exceeds available capacity!
Section 6 - 7 remains de-energized
4
End of FLISR operation

3 No
Net
Substation #1 Fault
Load = Substation #3
Fault 2 MW
1 2 6 7 8
Available
Capacity
Fault No
Fault
= 1 MW

83
 Time Line Without and With FLISR
member Feeder
Fault Fault Back to
Reports
Located Normal
Occurs Outage

Fault Investigation Time to Perform

Travel Time & Patrol Time Manual Switching Repair Time
Without
FLISR 1-4
5 – 10 15 – 30 15 – 20 10 - 15
minutes minutes minutes minutes Hours

POWER RESTORED
45 – 75 TO memberS ON
minutes HEALTHY SECTIONS
POWER RESTORED
OF FEEDER
TO memberS ON
HEALTHY SECTIONS
OF FEEDER Feeder
Field
member Crews Back to
FAULT
Reports On-Scene Normal
OCCURS Outage
Patrol
Travel Time Time Repair Time
With
FLISR
5 – 10 15 – 30 5 - 10 1-4
minutes minutes Hours
minutes

1 to 5
minutes

84
 FLISR with and without Large DG on
Distribution Networks

Substation #2
Earlier slide (no DG)
5

3 No
Substation #1 Fault
Fault
Substation #3
Fault
Current
1 2 6 7 8

Fault Fault No
Fault

85
FLISR with Large DG on Distribution Networks

Include large DG that is

Substation #2
capable of producing
significant fault current
5
FD at Switch 6 picks up
FLISR fault detectors might
4 predict fault beyond switch
number 6, and….

3 No
Substation #1 Fault
Fault
Fault Substation #3
Fault
Current Current
1 2 6 7 8

Fault Fault Fault

86
FLISR with Large DG or Distribution Networks

Substation #2 Trip switch 6, ultimately

resulting in…
5

3 No
Substation #1 Fault
Fault
Substation #3
Fault
Current
1 2 6 7 8

Fault Fault Fault

87
FLISR with Large DG or Distribution Networks

Substation #2 Entire feeder outage

5

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault Fault Fault

88
FLISR with Large DG or Distribution Networks

Substation #2 With directional fault

indicators or more
5
advanced DMS version
of FLISR, would locate
4
the fault properly,
resulting in

3 No
Substation #1 Fault
Fault
Fault Substation #3
Fault
Current Current
1 2 6 7 8

Fault Fault Fault

89
FLISR with Large DG or Distribution Networks

Substation #2 Power restored to as

many members as
5
possible!

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault Fault Fault

90
Opportunity – Islanding

Substation #2 Assumes a 5 MW DG unit is

available
5 Also assume measured
prefault load is 3 MW

5 MW DG Unit

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

3 MW prefault
load
91
Opportunity – Islanding

Substation #2
Since DG rating exceeds pre-
fault load, can establish an
5
island fed by the DG unit

5 MW DG Unit

3 No
Substation #1 Fault
Substation #3
Fault
1 2 6 7 8

Fault No
Fault

3 MW prefault
load
92
 Optimal Network Reconfiguration
• Goal: Identify changes in feeder
configuration that would improve overall
distribution feeder performance and
reliability
– optimize topology for steady state
operations…

• Selectable Operating Objective

– Minimal power and energy losses
– Maximum reliability
– Best load balance
– Best voltage profiles
– Other?
– Weighted combination of the above

93
 Optimal Network Reconfiguration
• Goal: Identify changes in feeder
configuration that would improve overall
distribution feeder performance and
reliability
– optimize topology for steady state
operations…

• Selectable Operating Objective

– Minimal power and energy losses
– Maximum reliability
– Best load balance
– Best voltage profiles
– Other?
– Weighted combination of the above

Load
Transfer
Occurs
94
 Optimal Network Reconfiguration

• Analyze best state of the network for the selected

objective function
– Minimal power and energy losses
– Maximum reliability
– Best load balance
– Best voltage profiles
• Output = optimal network configuration
– Ordered switching list
– Improvement results for each switching operation
– Cumulative affect of switching steps
• Execute those steps that bring the most benefit

Courtesy of Telvent
95
Optimal Network Reconfiguration
(Load Balancing) – Sample Case

≈40% loss
reduction

96
 Distribution Contingency Analysis (DCA)

• Tool to assess whether the network could “survive” a

contingency and operate inside technical limits
• “Survive” means the parts of distribution networks
that are affected by faults could be re-supplied in
reasonable time (without waiting to repair the faulted
elements).
• DCA Functions:
– analyze faults in specified network's elements
– Test the possibilities of re-supplying the de-
energized consumers
– Output list of critical outages, after which power
cannot be restored to all consumers

97
 Management of Distributed Energy Resources

• DER output and status monitoring

• Transfer tripping
• Dynamic model of all DERs
– Impact of DER on distribution power flow
– Fault current contribution of DG units
• Management of intentional islands
– Monitoring and Control of energy storage facilities
• Future economic dispatch (virtual power plants)

98
 Dispatch Training Simulator

• Difference between “simulator” and “playback”

• Full blown power system model, not just a
playback tool for scripted scenarios
– Open switch, load through switch goes to zero
– Place fault – model calculates fault current
and relays operate with proper
coordination
• Simulator uses same displays as on line system
• Maintain model through GIS or live DMS

99
Planning for a New DMS
 Contents of the Plan

• Business case
• Needs analysis (functional requirements)
• Conceptual architecture
• Implementation strategy (Procurement, design/build,
Install, commission)

101
Overview of the Implementation Plan

102
 What is a “Business Case”?

• A set of reasons or arguments to convince persons who hold

“purse strings” (company executives, regulators) to spend a lot of
money on a proposed project

• Business case usually addresses:

– Technical issues – “What business problem is solved by
the investment?”
– Financial issues – “Do the benefits outweigh the costs?”

103
 Keys to Business Case Success
• Proposed DMS project must:
– Address significant business problem(s)
– Support important business driver(s)
– Provide monetary payback within an acceptable period to offset
the expenditure

• “Technology for technology’s sake” not an acceptable reason to

proceed with a significant automation project
– At best, will result in demonstration (“pilot”) project with little
support that goes nowhere

104
Business Case Methodology
Needs Analysis

Understand Relate Develop

Begin Opportunity
Business Drivers & Automation
Process Matrix
Operational Needs to Needs

Results of Perform
Benefit/Cost Analyze Gather Operating
Sensitivity
Analysis Scenarios & Financial Data
Analysis

Benefit-Cost Analysis

Requirement Update
Final Report Management Specs & Business Case
Approval Technology & Cost/Benefit
Selection Expectations

Conclusions and Recommendations

105
 Identifying Business Drivers

• No “one size fits all”

– company organization - degree of vertical integration
– Regional concerns
– member expectations
• Relevant drivers should be defined by persons who “own”
the problems: Senior Level Managers

106
 Identifying Business Drivers
• Typical Business Driver categories
– Workforce safety DMS projects can
contribute to each of
– Reduce O&M costs
these business driver
– member satisfaction categories
– Quality of service (reliability & power quality)
– Worker safety and productivity
– Proactive/direct response to regulatory compliance
– Energy efficiency
– Increased capacity utilization
– Support Demand Response activities
– Accommodate Distributed Energy Resources (e.g. PHEV, DER)
– Manage Electric vehicle charging

107
 DMS Value Drivers

• Safety
• Reliability
• Efficiency
• Asset Utilization
• Maximize Use of Distributed Energy Resources
• Manage Electric Vehicle Charging Scenarios

108
 Safety

– Create and validate

complex switching
orders accurately and
efficiently
– Maximize awareness of
current tags,
clearances, etc
– Convey information
electronically to field
crews

109
 Reliability

–Pinpoint fault
location
–Automatically
isolate fault
and restore
service to as
many members Substation #2
Close switch 4 to pick up
as possible 5
part of faulted feeder
FLISR logic stops here

3 No

Substation #1 Fault

Fault
1 2 6

Fault No
Fault

110
 Efficiency

• Reduce losses through Volt-

VAR optimization and Load
balancing
• Conservation voltage reduction
to reduce energy consumption
and/or electrical demand

111
Asset Utilization

• Dynamic rating of
cables, transformers Base rating on
current
– Squeeze more “Real-time”
capacity out of conditions
and recent
existing assets history

– Defer capital
expenditures for
capacity addition

112
 Maximize Use of DER

• Balance DER output with load

and storage capabilities
• Leverage electronic inverters
for VAR support as part of
Volt-VAR Control strategy
• Manage power fluctuations
using energy storage

113
 Manage Electric Vehicle Charging
Scenarios

• Enable/disable fast
charging based on
feeder conditions
• Manage Vehicle to
Grid (V2G) strategy

114
Needs Analysis –
Identifying Major Functional
Requirements for the DMS
 DMS “Opportunity Matrix”
• Relates business needs to DMS application functions

Accommodate
Corporate Quality of Support Distributed Manage
profitability, service Increased Demand Energy Electric
e.g. O&M Customer (reliability & Energy capacity Response Resources (e.g. vehicle Workforce
costs satisfaction power quality) efficiency utilization activities PHEV, DER) charging safety

Intelligent alarm processing √ √ √ √ √ √ √ √ √

Distribution model √ √ √ √ √ √ √ √ √
State estimation √ √ √ √ √ √ √ √ √
Load Forecasting √ √ √ √ √ √ √ √ √
On-line power flow √ √ √ √ √ √ √ √ √
Switch order management √ √ √ √ √ √ √
Volt VAR Optimization √ √ √ √ √ √
FLISR √ √ √ √ √ √
Optimzal Network Reconfiguration √ √ √ √ √
Contingency Analysis √ √ √ √ √ √ √
DER Management √ √ √ √ √ √ √ √ √
PHEV Charging Management √ √ √ √ √ √ √ √
Emergency Load Shedding √ √ √ √

116
 Discovery Meetings with
DMS Stakeholders

• Defined DMS needs for meeting the business drivers via series of interviews and workshops with key project stakeholders:
– Field and control center operations
– Engineering planning and design
– Protective relaying
– Restoration center (outage management)
– Communication engineering
– Information technology
• IT Standards, GIS, OMS, work management, mobile data
– SCADA engineering
– Engineering standards
– Smart metering
– member care
– DG connections
– Substation engineering
– Many others

117
 Stakeholder Interviews – Items to Discuss

• Required DMS functions (must relate to the business case) – need to get to
the next level of detail
• Operational Needs – what level of DMS functionality is needed to address
operational needs and issues?
• Existing systems
– Will existing systems remain as separate standalone system, be
interfaced to the DMS, or be wholly incorporated in the DMS
– What are the available sources of information? Real time data (SCADA.
DA, AMI, external systems) and static data (GIS)
– Do existing independent systems require DMS data? (e.g. OMS requires
feeder outage data)

118
 Request for Information (RFI)

• Objectives
– Obtain information (obviously)
• General info (financial and people resources, past
similar projects, etc)
• Standard offerings in areas of interest to the utility
• Handling of specific “tough spots” (GIS data quality,
cyber security, interfaces in general, etc.)
– Create “short list” for DMS procurement (10 vendors -> 3 bidders)
– Did not request budgetary pricing – in general this is meaningless at
RFI stage

119
 Request for Information (RFI)

• RFI contents
– Overview of functional technical requirements
– Questions, Questions, more questions
• RFI process
– Send RFI to vendors
– Read vendor responses (“Tell Me” phase)
– Vendor demonstrations (“Show Me” phase)
– “Show Me” phase changed opinions developed during “Tell
Me’ phase

120
• Develop “Conceptual” Architecture
– Goal is to identify high level “technical” features of the DMS
(e.g. requirement for primary and independent backup control
center)
– Should not unnecessarily restrict the vendor in this area – let
them be creative within reason
• e.g. allow use or “virtualization” for the training/development
environment where performance and reliability are not mission
critical

121
Centralized vs. Decentralized

• Refers to the location where the main logic resides under normal
circumstances
– Does not refer to the input/output location
– Does not refer to the human machine interface location

122
 Alternatives

Centralized Substation Centered Distributed (Peer-peer)

123
 Centralized Architecture

Centralized Substation Centered Distributed (Peer-peer)

Main Logic
Resides here

124
 Substation Centered Architecture

Centralized Substation Centered Distributed (Peer-peer)

Main Logic
Resides here

125
 Fully Distributed Architecture

Centralized Substation Centered Distributed (Peer-peer)

Main Logic
Resides here

126
 Hybrid DMS Architecture

Centralized Substation Centered Distributed (Peer-peer)

Most DMS systems are a combination of at least

2 of the 3 main alternatives
127
Main Architectural Tradeoffs
• Complexity versus Speed (Response Time)
Dynamic
System Model
(Frequent based
changes) solution

COMPLEXITY
COMPLEXITY

Centralized

Substation
Centered

Distributed
Static Fixed set
System of rules
Milliseconds Minutes
SPEED

128
Other Considerations
Substation-
Criteria Centralized Distributed
Centered
Small # of geographically
High % of feeders All feeders at selected
# of DA Feeders automated substations automated
dispersed feeders
automated
Can tolerate some Can tolerate some
Nothing happens without
Operator Visibility operator being informed
control actions without control actions without
operator notification operator notification

Availability of suitable Requires local area Requires local area

Requires high-speed
communication wide area comunications
commmunications (sub- commmunications (pole-
pole, sub-sub) pole, sub-pole)
facililties

Availability of
VVO, FLISR, ONR VVC, FLISR, DFA FLISR
commercial products

Process large quantity Limited by data transfer Well-suited for waveform

Little or no capabilities
of data capability analysis, ECM

VVO – Volt VAR Optimization

FLISR – Fault Location, Isolation, and Service Restoration
ONR – Optimal Network Reconfiguration
DFA – Distribution Fault Anticipator
ECM – Equipment Condition Monitoring

129
 Architecture by Application

Substation-
Application Centralized Distributed
Centered
FLISR



Volt VAR Control (rule based)


Volt VAR Opt (model based)

Adaptable VVO


Dynamic Volt-VAR Control


Optimal Network Reconfiguration

Fault Anticipator

Equipment Condition Monitoring

130
 Centralized DMS Architecture
AMI Network
and Interface Distribution
Field Devices

OMS
GIS
Peer-Peer
Field
Devices

Data
EMS/SCADA
Warehouse Distribution
Network
Control Center
consoles

Substation
RTUs DMS

131
“Bolt-On” Configuration
• Substation inputs and outputs handled via EMS/SCADA
• Field (feeder) inputs handled directly by DMS (DNP/IP)

Vendor 1 Vendor 2
EMS/SCADA DMS
Secure ICCP

FIELD
AUTOMATION
NETWORK

132
 Redundant, Location Agnostic Design
• Dual redundant architecture – Fully redundant DMS installed at primary and backup control centers
• “Location Agnostic” Design: Operator consoles and DMS servers installed at different locations
(remote data center concept)

DMS Data Center (Primary)

Distribution Control Center (Site 1)

Distribution Control Center (Site 2)

DMS Data Center (Backup)

133
DMS Interfaces – Essential for effective deployment

Illustrates the
importance of
external interfaces to
the DMS
implementation
project

134
 Interface functional requirements

• Sample Interface spec: DMS - AMI

Interface Requests From DMS On demand meter read requests, on demand energized state requests, queries of historical
data from AMI/MDMS

Interface Data Elements Returned to DMS On demand results, interval transformer demand, energized status

Interface Function Description The DMS interface to AMI/MDMS must be capable of requesting and receiving on
demand reads, obtaining outage event information, provide an ability to query
historical data from AMI/MDMS,

Frequency of Requests On demand, 15 minute intervals, occasional, depending on type of request

Preferred Integration Implementation ESB

Preferred Integration Method Publish-subscribe: web services or XML using Java Message Service (JMS)

Latency Requirements 30 seconds or less for on demand pinging of up to 100 meters, 15 minute and hourly for
transformer readings and interval load profile reads, 30 seconds for on demand
energized state requests.

135
Interface Standards
e.g. MultiSpeak

136
Implementation Plan
• The implementation strategy should be divided into the
following key activities:
– Procurement
– Design and Test
– Installation
– Implementation and Commissioning
– Sustainment

138
 Main objectives for the DMS implementation strategy

• Ensure that the DMS is designed, implemented, tested, installed and commissioned in
accordance with utility’s requirements

• Ensure that the Vendor completes all contractual obligations to utility’s satisfaction.

• Ensure that electric utility personnel are fully trained in design, maintenance, and
operation of all aspects of the system so that utility company can be as self-sufficient
as possible in the future.
• Should not have to depend on the vendor and outside consultants for day-to-
day DMS “sustenance”.

139
 Contents of the Implementation Strategy
• Identifies strategies for implementing the DMS facilities that satisfy the functional and architectural
requirements
• “Multi-Stage” approach versus “Single-Stage” approach
• Provides a roadmap for implementing and maintaining the system.
• Relationships with other projects
• Identifies a strategy for implementing the new system without disrupting ongoing operations
• Summarize the role of Electric Utility personnel and its Subject Matter Experts (consultants) during
each activity
• Provide a rough estimate of the level of effort required during each activity.
• Change management and training strategy
• Scheduling and budgeting

140
Procuring a new DMS
 Approaches to System Procurement

• Sole source (e.g., incumbent vendor (EMS, OMS, GIS)

• Competitive Bid Process
– Pick vendor based on evaluation of fixed price bid
– Pick vendor based of evaluation of general capabilities,
then work together of specifications and negotiate
scope of work and price
– Other Variation?

142
 Approaches to System Procurement

• Sole source (e.g., incumbent vendor (EMS, OMS, GIS)

• Competitive Bid Process
– Pick vendor based on evaluation of fixed price bid
– Pick vendor based of evaluation of general capabilities,
then work together of specifications and negotiate
scope of work and price
– Other Variation?

143
Prepare RFP & Bid Evaluation Method
An Overview of the Process

144
Request for Proposal (RFP)

• Overall objectives
– Obtain firm fixed pricing
– Obtain information to compare proposals from the
proponents and pick a winner
– Lay foundation for DMS Contract

145
Request for Proposal (RFP)

• Terms of Reference
– Commercial terms and conditions
– Instructions to bidders
– Functional/technical requirements
– Questionnaire (lots of questions)

146
Request for Proposal (RFP)
Commercial terms and conditions

– Utilities often start with the same Ts and Cs that

are used for other procurements

– There are numerous Ts and Cs pertaining to DMS

procurement to be added:

147
Additions to standard
Commercial terms and conditions
– Right to use system and make changes without
voiding warranty
– Disclosure of interfaces
– Availability of source code
– Right to move software to replacement hardware
– Right to make copies of documentation
– Complicated definition of “Acceptance”
– Milestone payments
– Many others

148
Request for Proposal (RFP)

• Terms of Reference
– Instructions to bidders
• Format of proposal Requirement to have consistent
• Pricing forms format and content simplifies
review process
• Table of compliance
– Allows Vendor to concisely indicate where
they comply or take exception

149
Sample Table of Compliance
(Blank form)

150
Sample Table of Compliance
(With vendor entries)

151
 Request for Proposal (RFP)
• Terms of Reference
– Questionnaire
• Prepare questions seeking clarification on specific issues
pertaining to the proposal
• Guideline: At least one question per specification section
• Questionnaire responses become part of statement of
work/contract for winning vendor

152
 Request for Proposal (RFP)

• Terms of Reference
– Functional/technical requirements
• Technical description of requirements for
equipment, software, services
• Focus on “what” is needed, not solution
• Provide enough detail to avoid confusion. But
don’t over-specify

153
Contents of Technical Specification

• Section 1: Project Overview

– Brief project summary, including identifying major project
objectives
– Responsibility of each party to complete the required work
• Vendor responsibilities
• Utility responsibilities
• Responsibilities of 3rd parties (consultants, installers, system
integrators, etc)

154
Contents of Technical Specification

• Section 2: Functional Requirements

– Functional description of each major application function
• Basic functions:
– data acquisition
– Displays
– historian
• Advanced functions:
– Intelligent alarming
– distribution system model
– On line power flow
– Volt VAR Optimization
– Automatic line sectionalizing
– Switch order management
– Others…..

155
Contents of Technical Specification

• Section 3: Technical (Architectural) Requirements

– Description of architectural requirements for the system
• General architecture (centralized, decentralized)
• Primary and back up control centers
• “Location agnostic” requirements
• Relevant IT standards
• Interfacing requirements to external systems

156
 Contents of Technical Specification

• Section 4: Sizing and Performance

– Define initial and ultimate sizing requirements for the system
• Number of concurrent users
• Quantities of operator workstations
• Initial and ultimate quantities of inputs and outputs
• Requirement for spare capacity and expansion capability
– Performance requirements
• Maximum allowable response time (latency) under normal and peak load
(emergency) conditions
• Maximum time to complete powerflow run for “N” feeders
– Reliability requirements
• Overall system reliability requirements (e.g. 99,999% availability)
– Need to explain what being available means – is the overall system
considered unavailable if one console fails
• Availability of individual system components

157
 Contents of Technical Specification

• Section 5: Hardware and software

– Relevant standards that apply to hardware and software

– Acceptable use of virtualization

– Software to build and edit database, models, displays

– Required diagnostic capabilities and maintenance tools

158
Contents of Technical Specification

• Section 6: Documentation and Training

Documentation
– Summary of required documentation needed to enable utility to achieve desired level of system
support capability
– Required drawings and drawing format
– Quantities of paper copies
– Procedure for review and approval of documentation

Training
– Summary of required training needed to enable utility to achieve desired level of system
support capability
– General approach to training (train the trainer, versus vendor handles all training)
– Training location

159
Training

• Categories:
Programmers, database & display builders,
dispatchers, maintenance technicians, installation
teams
– Train the trainer?
– Informal hands-on dispatcher training
– Delay formal dispatcher training
– On-the-job training of programmers
(6 mo - 12 mo)

160
Contents of Technical Specification

• Section 7: Testing and Quality Assurance

– Factory acceptance testing

– Site testing
• Installation tests
• Site acceptance test
• System availability test

161
Contents of Technical Specification

• Section 8: Implementation Services

– Project management
– Project meetings
– Maintenance prior to and following acceptance
– System installation
– Expert assistance during installation and checkout of advanced
applications

162
Bid Evaluation Process
 Bid Evaluation
• Cross functional evaluation team
• Develop scoring methodology in advance of bids arriving (avoid
bias in weighting factors used for scoring)
• Scoring categories
– Functional & Technical
– Commercial
– Bid demonstration
– Risk
– Pricing

164
 Bid demonstrations

• All bidders should make bid presentations at your offices

• Presentation included functional demonstration of key application functions (GIS data conversion,
model building, OLPF, VVO, FLISR)

• Conversion of company-specific “raw” GIS data

• Bidders convert the data as needed, built company specific models and displays, demonstrated
DMS application functions using these models

• Demonstration quality can be a key differentiator among bidders

165
Sample score-sheet

166
 Bid Evaluation Stages

• Read proposals (“Tell Me”)

• Produce one set of results

• Bid demonstrations (“Show Me”)

• Alters the ranking significantly

• Site visits (“Prove It”)

• Seals the deal

167
Evaluation Methodology – Weighting Factors

General Proponent
Responsibilities
QA and Testing
Documentation and
Training
Sustainment

Volt Var Optimization

Fault Location
Data Acquisition & Control
User Interface
Alarming
Decision Support Tools
Data Models, etc

System Architecture
End-End Integration
Hardware Characteristics
Software Characteristics
Performance, expansion,
reliability
IT Standards

168
Scoring Summaries

169
Contract Negotiation

• Create statement of work based on winning proposal and clarifications received during bid
evaluation

• Developed a “conformed specification” that became part of the contract

– Started with your terms of reference (TOR)

– Updated TOR wording only where the bidder proposed alternatives or took
exception during bid evaluation process
– Allows you to essentially maintain control of the contract wording

170
Designing Building and
Implementing the System
 Design, Configuration and Testing
• General organization and Project Management
– Single point of contact
– Core team with representatives of affected parties
• Design input and review
• Testing
– Type testing
– Functional and performance testing
– Integrated system testing
• Training and Documentation
– Prepare you for self sufficient O&M

Vendor Preliminary Review

Work
Design Design Core Team Review Test
Statement Preliminary
System
Documents Training Procedures
Design
Approved Conduct
Test Ship
Factory
Provide Procedures System
Approved Order Develop Testing
Input Data Design
Components/ Factory Test
Documents
Build System Procedures

172
Barriers to Successful
Implementation
 Barriers to Successful deployment
• Lack of accurate data for modeling
– No record of construction details for overhead conductors
• Conductor arrangement needed to compute line reactance, for
example
• Can assume default conductor arrangement
– Incorrect records of phasing
• EPRI researching techniques to identify phase
– Lack of standard models for members and loads
• EPRI Load/Voltage Modeling Initiative
– Lack of information on substations in GIS
– Lack of information about secondary circuits in GIS
• Vendors can do some consistency checks

174
 Barriers to Successful deployment

• Changes to time-proven control room

procedures - Lack of trained resources
– No such thing as “plug and play” when it
comes to DMS
– “System optimization” a new concept for
system operators – may require power
system engineering support group
– process design to deal with the degree
of DMS business processes both before
and after the DMS is implemented

175
 Barriers to Successful deployment
• Lack of reliable, near real-time, two way communication
facilities
– Is AMI communications network the answer?
– Need failsafe design for local controllers (revert to standalone local
control if communications fail)

176
 More Barriers to Successful
Deployment
• Lack of support for advanced distribution applications
– Lack of field proven advanced applications
– Vendor offerings not fully developed
• Lack of industry standard interfaces (CIM, MultiSpeak)
• Management of distributed energy resources
• Others???

177
 Questions and Discussion

Bob Uluski
EPRI
Technical Executive
[email protected]
215-317-9105

178