SYSTEM LOSS SEGREGATION

PROCESS
OBJECTIVE
„ TO BE ABLE TO MAKE US AWARE OF
THE DETAILED PROCEDURE OF
SYSTEM LOSS SEGREGATION FROM
GATHERING OF SYSTEM DATA TO THE
ACTUAL SEGREGATION OF LOSSES.
OUTLINE
I. DATA GATHERING
II. DATA ORGANIZATION / ENCODING
III. SANITY CHECK PROCESS
IV. SYSTEM MODELLING
V. LOAD FLOW SIMULATIONS
VI. SEGREGATION OF LOSSES
I. DATA GATHERING
„ We try to capture as accurate as
possible all the information and physical
characteristics of the system from the
Sub-Transmission Line, Power
Transformers down to the individual
consumers.
 Typical Distribution System
Primary Distribution Lines
(Main Feeder)
Sub-Transmission Lines

Substation
Transformer Primary Distribution Lines
(Laterals)

Misc Loads

a) Sub-transmission Lines
b) Substation Power Secondary Distribution Lines
Transformers Service Drop
c) Primary Distribution Lines Distribution
d) Distribution Transformers Transformer
e) Secondary Distribution
Lines Residential Commercial Industrial
f) Service Drops
g) Voltage Regulators
h) Capacitors
i) Reactors
j) Other electrical equipment
BUS ID Assignment
„ Equipment installed
„ Lateral Lines
„ Changes of Configuration
„ Conductor size
„ Underbuilt (pole to pole)
„ Open Secondary (pole to pole)
„ Service drop
 Where can you find the system
data ?

„ In the field
„ In the office (billing and engineering)
What are the requirements of data
gathering activities?
„ Qualified and dedicated technical
personnel.
„ Tools /instrument such as measuring
wheel or tape, compass, GPS unit,
digital camera, binocular, calculator,
communication units such as mobile
phone or two-way radio, visible
markers, and so on.
What are the requirements of data
gathering activities?
„ Gathered data must be placed in a
worksheet, staking sheet, map or
diagram (it should be understandable
for all the members of the team).
„ Logistics support such as vehicle,
computers, and dedicated area in the
engineering office.
Lessons learned from data gathering
in the FIELD
„ Pilferage reduction (by-pass of metering facilities and
fraud to authority)
„ Technical loss reduction (broken neutral, unloaded
DTs, no neutral wire, stop meter, and so on)
„ System corrections due to poor workmanship (
octopus tap, non-observance of basic clearances,
material substitution, and so on)
„ Plan maintenance activities (clearing program, pole
maintenance program, replacement of damage
insulators, and so on)
„ Familiarity on the physical location of vital
protection/equipment of the system
„ Location awareness
Lessons learned from data gathering
in the OFFICE
„ Check and balance of billing records
with engineering records
„ Correction of office data versus field
data
„ Un-billed customer/no customer record
„ Retrieval and safe-keeping of technical
data of equipment/materials.
Impact of Data Gathering in
Improvement of System Operation
„ Reduction of System Loss (though
not readily quantifiable)
„ Improved service reliability
II. DATA ORGANIZATION and
ENCODING
„ In-charge must be familiar with the ff.:
„ Microsoft Excel program (expert)
„ ERC Guidelines and prescribed instructions in
filling-up the ERC-DSL Form.
„ NEA Standard Coding
„ Specifications of 13.2 kV distribution system
„ Recommend to acquire AM/FM software
ERC Data Requirements Templates
ERC-DSL-01 Administrative Load Data
ERC-DSL-02 Customer Data
ERC-DSL-03 Billing Cycle Data
ERC-DSL-04 Customer Energy Consumption Data
ERC-DSL-05 Load Curve Data
ERC-DSL-06 Bus Data
ERC-DSL-07 Subtransmission Line Data - Overhead
ERC-DSL-08 Subtransmission Line Data - Underground/Submarine
ERC-DSL-09 Substation Power Transformer Data - Two Winding
ERC-DSL-10 Substation Power Transformer Data - Three Winding
ERC-DSL-11 Primary Distribution Line Data - Overhead
ERC-DSL-12 Primary Distribution Line Data - Underground Cable
ERC-DSL-13 Primary Customer Service Drop Data - Overhead
ERC-DSL-14 Primary Customer Service Drop Data - Underground
ERC-DSL-15 Distribution Transformer Data
ERC-DSL-16 Secondary Distribution Line Data
ERC-DSL-17 Secondary Customer Service Drop Data
ERC-DSL-18 Voltage Regulator Data
ERC-DSL-19 Shunt Capacitor Data
ERC-DSL-20 Shunt Inductor Data
ERC-DSL-21 Series Inductor Data
ERC-DSL-22 Energy Sales Data
ERC-DSL-23 Other Technical Data
Lessons Learned in Data
Organization / Encoding
„ Accessibility of information needed;
„ Analysis of system derived easily;
„ Technology is the tool to fast-track the
plan
BENEFITS OF DATA ORGANIZATION
SYSTEM OPERATION
„ Development of Distribution System
Asset Database
III. SANITY CHECK PROCESS
„ Checks for the ff: (Sanity Check Program )
„ Connectivity
„ Phasing
„ Radiality
„ Others
„ Multiplicity Program – uniqueness checker
„ Comparator Program – 1 to 1 Checker
„ FROM-TO Changer Program – Root Checker
Sanity Check 1.2.6
 Typical Distribution System
Primary Distribution Lines
(Main Feeder)
Sub-Transmission Lines

Substation
Transformer Primary Distribution Lines
(Laterals)

Misc Loads

Check for:
Secondary Distribution Lines
1. Connectivity Service Drop
Distribution
2. Phasing Transformer

3. Radiality Residential Commercial Industrial

 Interpretation of Results
Phasing Layer Phasing of Phasing Branch Type
From Bus ID
From_Bus Check Check
To Bus ID
Terminal Tree Phasing of Radiality
Branch Type
Branch Number To_Bus Check 2
of To_Bus

Branch Type Radiality

of From_Bus Check 1

A B C D E F G H I J K L M N
PL_Bus0001 PL_Bus0002 BN 1 1 1 0 24 1 0 1 0 1 0
PL_Bus0001 PL_Bus0007 BACN 0 1 1 0 2134 1 0 1 0 1 0
PL_Bus0007 PL_Bus0009 BACN 0 2 1 2134 2134 1 1 1 0 1 0
PL_Bus0009 PL_Bus0010 BACN 0 3 1 2134 2134 1 1 1 0 1 0
PL_Bus0009 PL_Bus0019 CABN 0 3 1 2134 3124 1 1 1 0 1 0
PL_Bus0009 PL_Bus0030 BACN 0 3 1 2134 2134 1 1 1 0 1 0
PL_Bus0010 PL_Bus0011 BACN 1 4 1 2134 2134 1 1 1 0 1 0
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
Interpretation of Results
IV. MODELING PROCESS
„ Checking of data assignment based on
prescribed instructions (Engineering
Attributes Programs)
„ Typical values assignment
„ Field data checker
Engineering Attributes Program
V. LOAD FLOW SIMULATIONS /
SEGREGATION OF LOSSES
„ Load flow simulation of system using
three-phase unbalanced load flow
algorithm.
NOTE :
Segregation of System Loss accuracy
is totally dependent on the integrity of
the network data gathered.
Uses of Load Flow Study
„ Sensitivity Analysis with Load Flow
Study
„ Analysis of Existing Conditions
„ Analysis for Correcting PQ Problems
„ Expansion Planning
„ Contingency Analysis
„ System Loss Analysis
Sensitivity Analysis with Load
Flow Study
1) Take any line, transformer or
generator out of service.
2) Add, reduce or remove load to any or
all buses.
3) Add new transmission or distribution
lines.
4) Increase conductor size on T&D lines.
5) Change bus voltages
6) Change transformer taps.
7) Increase or decrease transformer
size.
ANALYSIS OF EXISTING
CONDITIONS
„ Check for voltage violations
„ PGC: 0.95 – 1.05 p.u. (For Transmission)
„ PDC: 0.90 – 1.10 p.u (For Distribution)*
„ *Recommended 0.95 – 1.05 p.u.

„ Check for branch power flow violations

„ Transformer Overloads
„ Line Overloads
„ Check for system losses
„ Caps on Segregated DSL
ANALYSIS FOR CORRECTING
PQ PROBLEMS
• Voltage adjustment by utility at delivery point
„ Transformer tap changing
„ Available Taps
„ At Primary Side
„ At Secondary Side
„ Both Sides
„ Typical Taps
„ Tap 1: +5%
„ Tap 2: +2.5%
„ Tap 3: 0% (Rated Voltage)
„ Tap 4: -2.5%
„ Tap 5: -5%
„ Capacitor compensation
„ Compensate for Peak Loading
„ Check overvoltages during Off-Peak
„ Optimize Capacitor Plan
• System configuration improvement
EXPANSION PLANNING
„ New substation construction
„ Substation capacity expansion
„ New feeder segment construction /
extension
„ Addition of parallel feeder segment
„ Reconducting of existing feeder
segment/ circuit
„ Circuit conversion to higher voltage
„ Addition of Generating units
CONTINGENCY ANALYSIS
„ Reliability analysis of the Sub-
transmission System and Distribution
System
SYSTEM LOSS ANALYSIS
„ Segregation of System Losses
DSL SEGREGATOR 2.0