MDM Integration with CIS Itron User s Conference September 29, 2009
Southern Company Southern Company is one of the nations largest generators of electricity. 4.5 million retail customers across 120,000 square mile service territory. Alabama Power Georgia Power Gulf Power Mississippi Power
AMI Benefits Customer Service Accurate meter readings Off cycle meter readings Remote connect and disconnect Data to respond to customer inquiries More current data for bill estimation Reduced meter re-reads, reduced billing adjustments Dynamic pricing plans Distribution Outage and power restoration notification Power quality information Revenue Protection Meter tamper alerts Usage at premise with inactive account Environmental
AMI Systems Operations & Support AMI Dashboard AMI System CSS IEE MV90 Load Control External Interfaces METS RNI Other Security Key Mgmt FlexServer End-User Portal Utility Portal OMS Other
AMI System Overview ARMS AMI Dashboard WFMS a Dat CSS Collectors n atio m o Aut Itron EE (Meter Data Management System) Head end Systems Event Management System Automate Workflow Management of Tickets for Events OMS DOES Revenue Protection Meter Logistics Tracking System (Pending) TCMS IDMS (Future)
Wireless Technologies Sensus/AMDS Licensed,901.1125 RF DSO/Transport COAM or Leased Residential or Commercial Structure OPCo Tower and Base Radio ARMS, Dashboard, Future APPS Network Itron EE GPCo and APCo Corp Headquarters CSS (Change Orders, Data Automation, Billing) MV90
Meter Data Management System AMI IT Initiatives Itron EE (Meter Data Management System) Itron Enterprise Edition (IEE) Meter data management system (MDMS) Stores meter configuration data Stores meter readings Stores meter events
Data Automation AMI IT Initiatives Data Automation AMI Data Automation: Phase 1: Automated integration of AMI meter configuration data from CSS to Itron EE (meter number, reading types, premise ID, meter status, etc.) Phase 2: In early planning stages GPS location of meters
Meter Data Automation How do you keep the data synchronized? What data do you synchronized? What system is the system of record? Phase I Meter Sets/Swaps/Removes Meter number Meter status Phase II Customer information Bill Group Changes GIS Data Rate Codes
Enterprise Service Bus
AMI Dashboard AMI Dashboard AMI IT Initiatives and Implementation Support AMI meter read performance and AMI billing success statistics Meter read success rate Meter download/upload to/from MDMS success rate Billing success rate Drill down capability for further investigation
AMI Dashboard Bill Group Process Date Meters Requested Meters Read Meters Billed Meters Previous Billed Meter Exceptions Meters Inactive Meters Estimated Success Rate 21 8/6/2009 26501 26501 1447 23662 221 1171 110 98.69% 1 8/6/2009 30981 30333 9307 19165 371 1490 0 96.38% 2 8/6/2009 27883 26098 24753 0 273 1186 0 92.72% 3 8/6/2009 26987 0 0 0 0 1212 0 N/A Success Rate: ((Meters Billed + Meters Previous Billed) Meters Estimated) / (Meters Requested Meters Inactive)
Customer Service Impacts Monthly meter readings Automated CMO process Off cycle readings Meter health Reconnect/Disconnect (in design) Enhanced Estimation Routine (under review) Web portal (future) Pre-pay Metering (future)
CSS Changes (things I wish someone had told me!) CSS Modify CSS to recognize AMI meters Download to IEE Upload from IEE Field order print Automate reroute from non-ami to AMI
Meter Reading Flow HHF Request File Creator attributes Configuration request data tampers, changes Request Process MRAS Request/ Response table change flags Process Change Flags change flags HHF Adapter CSS MRMS Response Process Readings Batch Gateway Middleware readings
Request Process Detail Program to format Itron Integrator files. Uses data from MRAS Request Response table and Configuration tables. Some custom logic to fill in custom fields added to Integrator (in filler). HHF Request File Creator attributes Configuration request data Request Process MRAS Request/ Response table Routes, premises, meters, registers and several attributes needed to broker requests across multiple reading systems. Kept in sync with billing system or meter shop via EAI transactions to published API. CSS MRMS Flat file input in specified format Processed through Adapter to verify fields and save to MRAS Request Response table. List of routes, premises, meters, registers to be read by scheduled read date. Includes hazards and access instructions. Assumed to be the most up-to-date list of premises on routes. De-normalized table containing all request values. Holds space for change flags and changed values coming from MRMS. Delivered to FTP site. Contains extra trailer record and confirms delivery via "OK" files.
Response Process Detail Configuration Program to parse data from MRMS file. Processes readings through Batch Gateway and Middleware. Processes change flags and tamper codes to be applied to Configuration and MRAS Request Response table rows. tampers, changes MRAS Request/ Response table change flags Process Change Flags change flags HHF Adapter CSS MRMS Response Process Readings Batch Gateway Middleware readings Program to gather readings for each register on MRAS Request Response table. Special logic to translate No Read Codes for billing system. Contains logic to send "0" readings on scheduled read date if no reading returned. Creates one row per register with information provided in request file and updated change flags from MRMS. Creates flat file output in custom format for integration with specific billing system. GW Adapter manages time stamps, converts No Read Codes to status codes. Extra information from MRMS is stored as "blob" with each reading - meter reader/operator ID, read method, no read message.
CSS Changes CSS Automate CMO process BIG task 5000 meters/day (4.4M in 5 years) 98% auto completion rate (billing window, pending orders, etc.) User friendly error report for manual completions Setting meters in empty sockets (set meter only) Premise address file for meter change outs Adding contacts/notes to accounts
Automated CMO AMR CMO File Interface Programs MEMS CSS Issue CMO CSS Complete CMO Rate Validation Reports 1 Received Report 2 Processed Report 3 Error Report
CSS Changes CSS Modify CSS to retrieve off-cycle meter readings from IEE Orders which require meter reading only New batch processes Demand Reset Error handling Consider impacts to existing service order processing (void, maintain, combine orders, etc.)
Off Cycle Readings Service orders on premise with AMI meter will not be sent to the field order management system Connect when status is on Disconnect Re-Read Meter High Bill Re-Read Service orders on premise with AMI meter are processed in batch daily List built at 9 pm File is sent to IEE at 1 pm the following day If a reading is found in IEE, the order is completed in CSS Orders are completed at 8:30 pm If a reading is not found, the meter will be included in the following day s list After 3 days CSS issues an Unable to Complete work item, if no reading received
CSS Changes AMI IT Initiatives Planned CSS Events management * Outage management Power Quality Revenue Protection Demand Reset Meter Health/Quality * Managing lots of events data
Meter Health Events No readings Missing readings Inverted Meter Temperature Tamper Consumption on Inactive Meter (in review) Meter Malfunction (future)
No Read/Missing Read Event Meter is in CSS and IEE and no reading has ever been received from the AMI head-end Meter is in CSS and IEE, the AMI head-end has been sending readings, but no reading is the last X number of days CSS receives an event file from IEE daily CSS creates a no read or missing read work item to be worked by field service personnel Meter cut at pole do not create work item Open outage event do not create work item Open no read event do not create work item
Inverted Meter Event Event created when the AMI system detects a meter that has been turned upside down CSS receives an event file from IEE daily CSS issues a Revenue Protection order Active account issue an account level order No active account issue a premise level order Event rules Reviews Check and Seal and Revenue Protection orders
Demand Reset AMI head-in sends an event when not able to reset the demand register Event is sent directly to our middleware Middleware sends event file to CSS and IEE CSS creates a Demand Reset Failure work item No work item is generated when kw is less than 5.0 No work item is generated when tariff does not bill kw Event is stored in an event folder in IEE
Temperature Event AMI Meter Events - Temperature Interface calls CSS Interface Business Rules BizTalk START BizTalk calls Temperature Mainframe Web Service Pending (i.e., not Complete or Void) Other Meter Temperature order exists at the premise. Yes Ignore Event No No Issue premise level Other Meter Temperature FO comments - Meter Temperature Alert / Possible High Temperature - Temperature of meter - Timestamp of event - Last Reading - Timestamp of last reading Evaluate Bill Account Status Active Bill Account Yes Issue account level Other Meter Temperature FO comments - Meter Temperature Alert / Possible High Temperature - Temperature of meter - Timestamp of event - Last Reading - Timestamp of last reading No Successful Yes Write Event to file (to be written to the error report later) END
Tamper Event AMI Meter Events Tamper 1 of 3 Printed: 6/29/2009 START Tamper Event END Y Already had tamper event today N Evaluate Meter Status Removed Meter Status at the Premise N Evaluate OMS OMS Order Exist N Evaluate CSS Y Y CSS Order Exist Y Evaluate OMS/ Event Timestamp Y N Ignore Event Y Timestamp Tamper between open & closing of Outage Ticket Evaluate SO N N Both Pending and Completed/RTC FO Evaluate if pending & complete/rtc FO exist SO Banked or Held Y Evaluate Order Status 1A 1B Completed or RTC FO N Evaluate FO Types: - Check-n-Seal - Revenue Protection Y Evaluate Event and FO Timestamp N Timestamp Tamper Event < = Timestamp of FO Completion Evaluate FO Types: - CME - Install Wires - CMO - Leave Door Hanger - CM/SD - Maintain Lights - Collection Inspection - Other (All) - Connect - Property Damage - Connect Lights - Rate Check - Cut In - Re-read Meter - CNP - Read Meter Only - Delete Meter - Remove Meter Only - DM/SD - Repair Lights - Disconnect - RS/SM Active - Disconnect Inactive (All) - RS/SM Inactive - Disconnect Lights - Set Active - Disconnect and Remove - Set Inactive - High Bill - Stuck Meter - High Bill Re-read - Tree Trim - High Bill Test Meter N Y N END N Issue Check and Seal FO (comments = Meter Tamper Event Please Investigate ) Issue Revenue Protection FO (comments = Meter Tamper Event Please Investigate ) Fail Y Write to current Events Error Report
Tamper - CSS Evaluation 1A
Tamper Event CSS Evaluation 1B
Future Event Management Consumption on Inactive Meter Event created when kwh exceeds X threshold CSS calculates CIM First time cumulative Subsequent work item to work item If there is an open CIM work item, do not create a new CIM work item If there is a pending service order, do not create CIM work item Only one CIM work item in a 30 day period Meter Malfunction There are many events which fall in this category Some relate to Customer Service others to Metering Different meters recognize an event differently
CSS Changes AMI IT Initiatives Planned CSS Remote Connect/Disconnect (RC/DC) Install approximately 3-5% of meter population Scope out changes to CSS Active collections Motivate customers to pay Reduce number of vehicles Safety
RC/DC Key Findings AMI meters with RC/DC functionality need to be certified Start lab and field testing early to insure timely deployment Current no-load policy requires a physical inspection of the meter load prior to connection; any load on the meter may result in the connection being rescheduled for a later time Selective or targeted installation of RC/DC meters based upon highest customer benefit / cost ratio is the prevailing industry standard for deployment Deploy to residential customers first Target other customer segments or extend to small commercial customers, on a case by case basis Utilities deploying RC/DC limit the issuance of RC/DC operations to a single group or function, generally collections or dispatch Pilot the process before you attempt to automate
RC/DC Customer Service Processes Volume of RC/DC meters and operations will ramp up over time; process impacts will ramp accordingly RC/DC deployment will impact call center or local office processes, customer service processes (dispatch, field service orders), active collections, billing services, and system support services over time Process impacts stemming from no-load policy decision could be Company-wide, depending upon decision Back-office processes necessary to issue RC/DC operations are new and will require training and additional staffing coverage until automation can be achieved Field service processes relating to RC/DC meter installation and trouble-shooting can be developed as experience is gained with RC/DC meters
RC/DC Key Challenges Transitioning through no-load connection policy is challenging Obtain key stakeholder approval Modify customer touch points emphasizing safe connection practices Meter Certification Process Implementing timely system changes to identify meters equipped with RC/DC switches in CSS Meter identifier Critical Contact Full automation is a long process
Enhance Estimation Routine Current Process IEE sends reading record with a no read code on the critical date CSS uses an estimate, if available, based on historical data Proposed Process IEE sends last available reading with date CSS calculates per day consumption since last billed reading date CSS calculates estimate for missing days based on per day consumption times number of missing days Estimate is based on sum of actual consumption plus estimated consumption If CSS can t perform the estimate use current estimate process
Future Enhancements Web portal Internal External Unbilled Revenue Calculation Pre-pay Meter Reading Customer specific reading dates Customer specific due dates Review current billing architecture
AMI Support Model