Redefining MDM for a Smart Grid Enabled

Transcription

1 Redefining MDM for a Smart Grid Enabled Enterprise Florida Power and Light Radha Swaminathan Director, AMI Information Technology,

2 MDM and its future in a smart grid enabled enterprise A key component within Automated Metering Infrastructure A key enabler to gather and serve billing determinants Fits well within AMR framework Current product trends.. Meter data store to derive billing determinants? Infrastructure to enable pricing programs? Tool to enable energy management programs? Application to enable outage integration?. What is the role of MDM in an AMI enabled enterprise? 2

3 Evolution of Metering Technology and MDM 3

4 AMR Meter Data Management Functions Focused on meter to cash optimization Designed to accommodate the needs of back end billing systems Minimal Process impact to billing operations Overlapping validation and estimation functions Route management to emulate daily meter reads Lack of business functions to effectively utilize interval reads Is not treated as a source of record for meter reads (e.g. cancel/replace) MDM fits well within AMR framework 4

5 AMI Enabled Smart Grid Programs Exploit new business opportunities Renewable Energy Initiatives ( Net Metering) Demand Management (Critical Peak Pricing, TOU) Regulatory Initiatives (Renewable Portfolio Information) Revenue Enhancement Opportunities (New Products and Services) Optimize asset performance and operations Business analytics using interval data and derived market segmentation for cross sell opportunities Revenue Assurance and Revenue Protection Opportunities Asset optimization Opportunities Advanced monitoring and control systems to improve operations Empower consumers to better manage energy use Home Devices (Zigbee, 6LoPan), Energy Portal, Energy Management Devices Smart Grid will generate a lot more granular information about customers, assets and operations 5

6 MDM Products focused on Smart Grid Functions Products competing to accommodate needs of ALL smart grid control and data functions. Mostly Integrated business functions, easy to manage and easy to trouble shoot (Outage Events, Flags, Power quality etc) Distribution and Customer data replication, introduces data integrity issues Additional complex interfaces required to integrate back office systems Incremental changes require long lead times and high cost upgrades Multifold grid based events compared to meter events (outage, device on/off etc) will introduce scalability issues The enterprise will have to evolve with product features. Will limit adaptability to business changes. 6

7 MDM Focused on Core metering Functions Ensures revenue management and the rest Go Figure Focuses on core metering functions (reads, validation and estimation) Focuses on schedules and not routes Highly componentized promotes incremental upgrades Can scale well with data growth Additional interfaces outside MDM to AMI networks, needed for T&D integration Not expected to meet core requirements for Smart Grid outside outage integration Will require a lot of external and internal products to meet smart grid objectives 7

8 Overview of Smart Grid requirements (Data and Events) 8

9 Additional requirements and constraints Confirm to cyber security standards Include functionality to protect bulk electric and transmission grid Provide data capture, storage and management features to facilitate advanced business analytics Provide seamless integration to T&D systems Implement quality of service for business events like CPP, PTR, C/D etc Identify and manage customer in-home devices and grid devices Requirements must include security, control & command, event and data management capabilities 9

10 Proposed Product features to meet SG requirements Component Administration Feature / Function Manage Schedules ( Interval and Billing Reads), Manage Meters Initiation by serial number), Automated device discovery and device Configuration Management Event Management Define Network and Device Events, On/Off Confirmation (Meters, Distribution devices, Outage) Recognize and Forward event flags to back office systems (Theft, PQ etc) Command and Control Initiate Command (C&D, Distribution Devices and Home Devices) Communicate Energy management and price signals within SLA Tight integration with AMI head end systems (gateway to AMI networks) Data Management Prepare interval and billing data for functional use Validate and Estimate based on configurable rules Integrate with external applications for data access, display and analytics Security Protect bulk electric system and Transmission Grid Policy Management for command and control Certificate based authentication 10

11 Product Architecture 11

12 Advantages of proposed architecture Evolves incrementally with Smart Grid Technology and future business requirements Speeds up implementation of metering business functions Execute and Manage business events as decided by operational elements Ensures secure operations of bulk electric grid and transmission grid Delivers rich data management features to facilitate real time pricing programs and advanced analytics Embeds quality of service for prioritized event delivery (outage and energy management functions) Based on industry standards accommodating multiple communication protocols, interfaces and data 12

13 Final Thoughts Current MDM architectures res and functions need to evolve e from meter centric to grid centric in order to meet smart grid requirements. Utility Industry needs to drive grid centric product standards to protect investments and meet compliance (NERC, FERC, SOX..) Cyber security will be a key part of Smart Grid requirements and grid centric product must plug and play within the enterprise security frameworks Grid centric product must provide standards based integration to SCADA / DMS systems. Essential to protect the bulk grid Componentized architecture will help relocate/integrate key functions to meet cyber security / regulatory needs Grid centric products must provide rich data management features to facilitate t real time pricing i programs and scale to data growth Do we really need an MDM or should the components be distributed between AMI network elements and back office systems? 13