idaho power mdm implementation and operations les · pdf filehistory of mdm at ipc »...

Introduction

» Idaho Power Co.

• Boise, Idaho

• 500K SP’s

» Les Jensen

• 32 years of service– 6 construction electrician

– 11 years metrology lab

– Current position

– 8 years on MV90

– 2004 to current on IEE

• Retirement – soon I hope!

Agenda

» History of MDM at IPC

» Cultural Transition

» Development of MDM Operational Philosophy

» The Simplistic Approach

» Daily Operations

» Looking Down the Road

History of MDM at IPC

» 1999: AMR pilot with 1500 meters

» 2004: AMI pilot with 25K meters• Started implementation of IEE 4.0 & 5.0

– Went into production with 5.0 in 2007

• Voluntary TV and CPP rate with 130 participants– Billed off of interval data

– Only TV & CPP SP’s were VE’d

» 2006: Implementation of 5.3• Began full deployment of AMI meters – 500K

» 2010: Implementation of 7.0• Elected to use PBC, ARI, & ABE

• Turned on validations for all SP’s

History of MDM at IPC

» 2011: Implementation of IEE SP3 HF16… ?• Drivers for upgrade

– DRS/LDA problems

– ARI Cleanup

» 2012: Implementation of IEE SP4 HF?• Drivers for upgrade

– SAP (CIS) to IEE integration

Cultural Transition

» Dream land!

• Preconceived ideas

• Misinformation

• Hopes

» Reality

• Keep focused

• Satisfy business needs, not wants

• Glossary – all department input

» Metering – the other side

• It isn’t just a Metering system any longer

• It all starts with MDM working

Development of MDM Operational Philosophy

» What is MDM to be used for?

• Just what the acronym is: Meter Data Management

• Service point down in the hierarchy

» Up through IEE 5.3

• Did meter exchanges in IEE– Meter Id = SP_MtrNum

• Used formula channels for TV calculation

» IEE is not used as a Meter Tracking system

• CIS the system of record for Account, SP, billing data

• IEE system of record for interval data

The Simplistic Approach

» IPC Meter History

• No meter has the multiplier programmed in– Meter techs are limited to what they can change in the meter

• For C&I, Special contract, Intertie, generation– Multiplier is in MV90

• All other rates in IEE– Multiplier is in CIS


» IEE 7.0

• No meter exchanges – the Meter Number field is updated– Advantages

• All data exchanges are done based on SP.

• Wrong meter numbers are easily fixed

• Simplified the CIS to IEE sync file

– Disadvantages

• There hasn’t been any

– Limitation

• Old CIS date tracking

• No formula channels for billing information– ABE Request/Response does the aggregation

• No multipliers– IEE is designed to assume that the meter has the multiplier


» IEE 7.0

• One PBC SP and Meter program

• All SP’s have the same hierarchy structure– SPC:1… kWh register

– SPC:2… kWh interval

– SPC:3… kW register

– SPC:50… formula channel

• Used to hold multiplier history

• Exports with Enhanced LodeStar and web API

– All meters are 60 minute interval


» IEE 7.0

• Validation rules– No validation rules on registers

– Failed

• Any one interval marked MEASURE (MEA)

– Used to enable ESTIMATEDUNSCALED (EUS) option

– Any interval from TNS that does not have a good QC and is not associated to a PO is marked as measure

• Any one interval marked ESTIMATEDUNSCALED (EUS)

– Used to mark intervals that were estimated with at least one register read missing


» IEE 7.0

• Validation rules– Warn

• UsageToleranceAbsDiff_ABS

– Threshold: 2

– 2 kWh allows for resolution difference

• DemandHighLimit_DMD

– Threshold: 150

– No meter on these rates should exceed this threshold

– Looking for anomalies created by bad imported data and resulting estimation

• DemandLowLimit

– Threshold: -20

– Looking for anomalies from TNS

Daily Operations -- Imports

» All functions based on a 24-hour clock

• CIS Sync file– 7am

– Information as of previous midnight

• Data Imports/VE– 5:30pm – 9:50pm data imports

– 9:50pm – 11:50pm VE

– Register and interval data in separate import files

Daily Operations – the challenges

» Missing reads

» Bad data – good quality codes

» Net meters – IEE limitations

» Meter Exchanges

» Meter mix-ups

Daily Operations – Goals

» All CIS requested reads sent

» Validation Queue (VQ) (by priority)

1. All time variant SP’s issues resolved

2. All net-meter SP’s issues resolved

3. All load research SP’s issues resolved

4. All disconnected SP’s logged in filter group

5. All warnings issues resolved

6. As many as possible failures resolved

7. As many as possible meter exchanges corrected

Daily Operations – TV Data Validation

» Custom SQL script

» Access tool

» Validates

• Number of register values

• Daily delta to sum of the intervals

» Drives

• Invalid reads

• Operational missteps

Daily Operations – Goals

» Task Monitor

• All tasks reviewed/investigated/cleared or sent to history

» Sync file import

• Resolve any errors

Daily Operations – Tools

» Have all files transferred to IEE?

• ARI Monitor

• By environment

• Restart errors



• Register read count report– Custom SQL export

– On reoccurring schedule

– Report results:

Local_Date,RegRd_Cnt

"07/14/2011",419520

"07/15/2011",419853

"07/16/2011",420506

"07/17/2011",421334

"07/18/2011",421395



• Check the resubmit files– Identify missing SP’s

• These occur due to the filtering applied during the initial import of hierarchy

– They were off system but in CIS during initial import

• Create new SP and import (tool demonstration)

Daily Operations – Tool

Data Management Tool

Daily Operations – Tool: Data Management

» Data Management Tool

• Estimated missing register reads

• Data management categorization– Set Status to Measure

– Manually Accept

– Negative Rotation Estimation

– Delta <> Intervals

– Delta > Intervals

Daily Operations – Missing Read Estimation

» Register Estimation Tool Requirements

• IEE Custom sql exports– List of SP’s from VQ

– Data export from IEE for SP’s in VQ

• End date – 6 days

• CIS Meter exchange report– Last 30 days

– Meter exchanges are excluded from estimation


» Estimation tool required parameters

• Only estimated the start read for the day

• Must have the stop read for the day

• Must have a valid read within four days prior to the read date to be estimated


» Estimation algorithm

• Delta of stop read and most current previous good read– Stop read – most current good read = delta

• Delta kWh and sum of good interval kWh difference– Delta – sum of good intervals = difference

• Difference averaged over missing intervals for time period– Difference / Total missing intervals = missing interval average

• Daily usage: average kWh * # of missing intervals for the day– Total missing intervals of estimation day * missing interval average = delta for day

• Stop read for estimation day – delta for day– Rounded to get start read


» File Export

• File has a txt extension

• File formatted xml

• Exports to SRI import directory

» Visual inspection of file

• Looking for negative reads

» Change extension to xml

• Service picks up file after extension change

» Re-Run failed validations in VQ

Daily Operations – Data Categorization

» Filter the VQ Warns by Data Scenario

• Set Status to Measure– Wrong nomenclature… should be Manual Estimate

– Baseline is zero, estimation is zero

– Delta/sum of interval exceeds threshold of 2 kWh

– Common on seasonal pumps

• Parameters– Both register reads good

– Delta > sum of intervals

– Estimated intervals > 0

• Method– Open all in DEE

– Estimate missing interval/s

– Save all



• Manually Accept– Generally these are net meters with negative rotation


– Delta = sum of intervals

– No estimated intervals


– Check Manually Accept box

– Save all



• Negative Rotation Estimation– net meters with missing intervals

– Positive rotation

• Takes negative estimation to balance to delta

– Negative rotation

• Manual interval estimation



– Use manual estimation tool

– Save all



• Delta <> Intervals– Generally these is a bad register read or bad block of interval data from the head

end system

• Parameters– Delta <> sum of intervals

– No missing intervals


– Identify either bad read or block of interval data

– Calculate the register read or mark the block of interval data as Measure

– Save all



• Delta > Intervals– Wrong nomenclature… should be Delta < Intervals

– Generally these is a bad register read or bad block of interval data from the head end system

• Parameters– Delta < sum of intervals

– Missing intervals


– Identify either bad read or block of interval data

– Calculate the register read or mark the block of interval data as Measure

– Save all

Daily Operations -- Templates

» New SP’s

» Updates

• UDA

• ARI Import status’

• Meter status

» ABE Requests

• Single and multiple SP’s

» Interval estimation

• Single and multiple SP’s

» Meter exchanges

» Static group SP Id imports

Daily Operations – Checklist

» ABE Responses

• Validate file– By cycle

– Total SP and Value count

– Majority of SP’s have the correct dates

• Send to CIS– Check nominal read report

– Resolve missing reads

• Wrong meter number?

– Update meter number

– Recreate request (tool demonstration)

• No reads within last two days?

– SIO

– System estimation

Future of MDM at IPC

» Smart Grid Initiative Grant (SGIG)

• New CIS system– SAP

• New Energy Usage Advisory Tool (EUAT)– New (UAT)

• New Energy Data Warehouse (EDW)

Future of MDM at IPC

» EDW

• Transactional Replication to staging database (4 tables)– FLATCONFIGPHYSICAL

– READING

– READING_STATUS

– READINGREADINGSTATUS

• Staging Database to Enterprise Data warehouse– Informatica – Change Data Capture (CDC)

idaho power mdm implementation and operations les · pdf filehistory of mdm at ipc »...

Documents