iee mdm overview - itron · pdf fileagenda • business drivers • mdm roles • mdm...

IEE MDM Overview

October 22, 2007Orlando, FL

Agenda

• Business Drivers• MDM Roles• MDM Boundaries• IEE MDM Architecture• IEE MDM Features• Demo

The typical utility IT infrastructure . . .In

dust

rial:

Hou

rlyC

&I:

Dai

lyM

ass

Mar

ket:

Dai

lyM

ass

Mar

ket:

Mon

thly

MV- 90

-Xi COMMTCP/IP

C&I FN

FN

MeterReading

2 way Interval

Hourly

Daily

Handheld

RTUsRTUs PI Historian

SCADA

LDW 3

LDW

LDW 2

CIS

SettlementCentral Market

RetailRetailOffice

Forecasting

RatesLoad Research

Customer Care

Assets

WMS

Circuit Analysis

LDW 4

ComplexBilling

Routes

GIS

MDM – The Solution Briefly Defined

Meter DataManagement

Business Drivers for MDM• AMI is the latest – but certainly not the only – MDM driver• Demand Response is driving AMI and AMI is driving

demand for new generation of MDM.• Energy Policy Act of 2005

– Encourages electric utility investment in advanced metering systems– Requires the PUCs to investigate implementation of standards

relating to time-of-use rates and advanced metering initiatives– Each electric utility is required to offer each customer class a time-

based rate schedule that reflects the variance, if any, in wholesalecost of generating and purchasing electricity and enables electricconsumers to manage energy use and cost through advancedmetering and communications technology.

– The law provides that customers of third party marketers are entitledto the same time based metering and communications devices asan electric utility's retail customers.

Business Drivers for MDM – cont.

• Economic and Regulatory Forces– Rising and more volatile energy prices– Peak demand is increasing faster than total energy use– Greater US focus and momentum at state and city level on green

house gas emissions

• State PUC’s recognizing that the status quo is notworking– Recent pilots suggest that customers are open to time-based rates

and direct load control programs– And can achieve demand response with such programs

Technology Drivers for new MDM

• Cost of solid state meters had decreased in last10 years and capabilities have increased

• Solid state meter is the foundation for AMImeters

• Significant advancements in communications –wireless and power line communications

• Merging communications methods: Zigbee,Bluetooth, GPRS

Agenda


MDM’s Role in Utility• Isolate the CIS system from the

complexities of meter data collection andmanagement

– Multi-vendor data collection and management– Collection of data using multiple methods

including remote interrogation (phone, IP) orhandheld, probe, mobile, RF fixed network, PLC,BPL, etc.

• Two way interaction with the AMI system tosupport key AMI business benefits

– Remote connect/disconnect, on-demand reads,demand response events

• Provide persistent data storage with customerinformation in enterprise-class and scalabledatabase

• Integrate and analyze frequently collecteddata

– Existing applications do not need or supportcollection of detailed data

• Enable data availability across theenterprise Distribution, forecasting, loadresearch, customer service, revenueassurance, etc.

MDM’s Role in Utility - cont

• Comprehensive interval data management– Validation, Editing and Estimation– Flexible billing determinant calculations– Workflow tools for utility operators to effectively manage key

operations (data import, validation failures, calculations, and exports)

• Data processing reports, exception reports, customerusage

• Integrate non-billing features of meter reading systems– Outage, restore, tamper, connect/disconnect, demand response,

distribution monitoring

• Enable change– Integration of multiple systems, vendors, technologies

MDM Reduces Risk for AMI

• AMI roll-outs take a long time, must co-exist with traditionalmeter reading methods– Use MDM to consolidate interfaces rather than build point-to-point– Use MDM to phase in AMI on a route-by-route basis

• Legacy systems have limited integration options– Use EAI to enable integration with new technologies– Leverage MDM to manage new asset information and interpret new actions

• Standard billing systems cannot manage daily or hourly reads– Use MDM to manage detailed data and provide commercial-ready billing

determinants to CIS

• AMI costs are justified on new applications of detailed data– Use MDM and applications to support new users with new applications

Some Key MDM Functionality• Security

– Verify sender has rights to send data for meter– Verify requestor has rights to receive data for meter or perform commands

• Exception handling– Event or meter data arrives for unknown meter– No meter data arrives for known meter– Usage for inactive meters, zero usage for active meters

• Linking meter data to operations– Outages by premise or transformer rather than endpoint– Energy usage combined with AC cycling or thermostat settings– Meter diagnostic events over time

• Filtering– Storm mode for outages– Outage/tamper combinations– Tamper and usage changes

• Validation– Actual vs. historical averages

• Billing Determinant Calculations– Peak Time Rebate for non-TOU customers

• absolute or % difference of actual usage during critical peak hours vs. average usage for same hours on 5 non-event like days

– Net meters, check meters, usage allocation

Agenda


MDM Boundaries

RadioMeter

Utility LAN

RF LAN000

012345

UID

1

2

hpProLiant

DL380 G4

Sim

plex

Dup

lex

c hch

21

00

113

32

2

44

55

Tape

Meter Data Management

Cell Relay

RadioMeter

Zigbee

RadioMeter

RF LAN000

012345

Cell Relay

RadioMeter

Zigbee

PublicBackhaul

UID

1

2

hpProLiant

DL380 G4

Sim

plex

Dup

lex

chch

21

00

113

32

2

44

55

Tape

AMI Collection System

UID

1

2

hpProLiant

DL380 G4

Sim

plex

Dup

lex

chch

21

00

113

32

2

44

55

Tape

CIS & Other Applications

Role of AMI Collection System vs. MDMSystem

Collection Engine• Transitory data store• Manages network components• Monitors data collection process

for a single technology• Collects data from backhaul• Distributes raw data

Meter Data Management• Persistent data store• Manages customer relationships• Monitors data collection process

for all connected technologies• Collects data from all connected

systems• Validates, repairs data

anomalies• Distributes validated data to

utility applications and market

Systems of Record and Data Synch.• Main link between MDM and CIS is Service Point

– CIS is system of record for• Customer/account/premise/address/contact information• Financial relationships – accounts and cycles• Rates• Billed values at the account level• Financial events (collections, payments, cancel/rebill, budget bills)

– MDM is system of record for• Meter/register/channel/endpoint information• Meter reading relationships• Raw data from devices• Billing determinants• Device-level events (outage, tamper, diagnostics)

• Main link between MDM and AMI is Endpoint/Meter– AMI is originating system or system of record for

• Endpoint/collector/cell relay/substation equipment• Data collection relationships (endpoint to collector/cell relay…)• Raw data (as it comes from devices)• Device-level events (collector/cell relay diagnostics)

Customer

Account

Meter

Premise

Cycle orRoute

Endpoint

ServicePoint

Agenda


History of IEE Meter Data Management

MV-90

MV-90 EE

EEM Suite3.1

EEM Suite4.0

Itron Enterprise Edition5.0

1990

2003

2001

UTS/Itron Products Silicon Energy Products

2002

2007

Timeline

MV-STAR1999

Data Collection

Validation/Edit/Est

Meter Data Mgmt

UCE

Versioning

MDM/Collection

Knowledge Layer

.NET Architecture

Database Design

Mass Market

C&IService Mode

AMI Integration

AMR Integration



SQL and Oracle

2006

IEE Meter Data Management

ES

B

Integration Across Systems

MDM and SOA

to collectiontechnologies

to rest of enterprise

Current MDM Interfaces

Itron Enterprise EditionMeter Data Management

Col

lect

ion

Syst

ems

Ope

ratio

nal S

yste

ms

Customer/1

Custom BillingSolutions

XML

Inte

grat

or

Prem

ierp

lus

4

MV

-RS

xi S

ervi

ce

Mod

e

MD

EF

HH

F

MV

-90

Spr

eads

heet

Flat

File

Cus

tom

XML

Inte

grat

or

Prem

ierp

lus

4

MV

-RS

MV-

90

Mai

nfra

me

Flat

File

Cus

tom

Lode

Sta

r

Lode

Sta

r E

nhan

ced

MV-

90

Spr

eads

heet

IS-U CCS Energy Billing Expert Load Research

MV-90 xiAMR/Network

DAA RPS Load Research Customer Care Curtailment

Outage Mgmt

CC&B

Agenda


Versioning• All versions of data maintained, regardless of how many times data

is changed or corrected• Audit trail of changes

– Reproducibility of results “as of” a specific date/time

Versions of Configuration data•Contract relationship changes•Meter changes

Versions of Reading data•Raw readings•Edited or estimated

Validation, Estimation and Editing• Consistent validation, estimation, and editing capabilities• Built-in parameter-based validation and estimation rules• User-defined validation and estimation rules using Universal

Calculation Engine, requires no code changes• Manual editing, export and estimation user interface

Estimation: Linear Interpolation

• For small issues, draws a “straight line” between the lastgood interval and the next good interval.

Estimation: Historical Estimation

• For larger issues, uses the given SPC’s own historicaldata to generate estimates . . .

Estimation: Load Profile

If insufficient history is available for Historical to run, use areference load shape and the register channel usage togenerate estimates . . .

Universal Calculation Engine• Consistent aggregation, losses, netting, and other calculations, regardless of

data source– Total consumption over bill cycle– Derived or captured demand– TOU and CPP billing determinants

• Easy-to-use scripting language• Rich function set delivered with product• Changes to formulas tracked over time

• + - * /• Square root, sine, cosine, etc.• Unit conversion functions

� KWH, KVARH � KVAH or PF, V2H �V,etc.

• Conditional and Logical Operators� IF/AND/OR/NOT,<.>, etc� 50 levels of nesting

� Conditional functions based on status• Read statuses

• Write statuses• Date and Time functions• TOU functions

Reporting and Exporting• Interactive Graphing• Analytical - Usage, Consumption, Summary, KVA, etc.• Operational - Cycle Due Date, Missing Data, Comm Logs, etc.• Exports – XML, MV9 Mainframe, LSE, Spreadsheet, etc.

MV-90 Integration – xi Service Mode

• Centralized configuration, scheduling and interrogationmanagement

• Remotely controls MV-90 xi in “Service Mode”• Can control multiple MV-90 xi systems simultaneously in

the same or different time zones• Provides a single interface for all user access and

upstream business systems• MV-90 operates as a “black box”, requires no operational

user intervention and stores no data

IEE MDM AMI Integration

• AMI Two Way Controls– Remote Interrogation– Remote Disconnect/Connect– Demand Reset– On Demand Read

Agenda


iee mdm overview - itron · pdf fileagenda • business drivers • mdm roles • mdm...

Documents