DTE Energy CIM Experience CIM Role in Smart Grid for Transmission and Distribution EPRI Conference, Washington DC 08-Sep-2010 Focus of discussion… • Fast forward -- DTE Energy background • Strategy -- key factors, gaining acceptance, and moving forward • Implementation -- experiences with project teams 2 DTE Energy Overview: Facts and Figures Company Name: DTE Energy Co. (NYSE:DTE) Corporate Headquarters: One Energy Plaza Detroit, Michigan 48226 Chief Executive Officer: Anthony F. Earley Jr. Employees: 11,000 Financial Information: Revenue Net Income Market Cap Assets Avg. Shares Outstanding: 165 million 3 $8 Billion $530 Million $7.4 Billion $24 Billion DTE Energy Overview: Business Segments 4 DTE Energy Overview: Interesting Facts • 10th largest electric utility and the 11th largest gas utility • License application filed to commission a new Nuclear plant • Investing $1 billion in biomass, solar, wind and other renewable energy sources • Contributions of nearly $7 million to non-profit organizations • Currently operating in 26 states • U.S. Department of Energy grant of $84 million will accelerate our Smart Grid program 5 SmartCurrentssm = The Future of Energy SmartCurrents = Data -Connected Model -Equipment Specifications -Continuously updated mapping data SmartCurrents = Customer Satisfaction -Shorter, less frequent outages -Control of home energy consumption and cost -Wind Power, Solar Power, and Electric Vehicles SmartCurrents = Job Satisfaction -Dispatch direct to trouble locations -Reduced patrol time, particularly at night or in bad weather -Better operating maps and mapping products 6 Smart Grid Investment Grant Project Scope A two year project within the SmartCurrents program AMI • 660,000+ meters • Rollout begins in Oakland County and continues in the surrounding areas, including the city of Detroit • DECo offers OpenWay AMI solutions from Itron Smart Home • Smart appliances to 300 customers • In-home displays (IHD) to 3,600 customers • Programmable Thermostats (PCT) to 3,400 customers • Dynamic pricing to 5,000 customers Smart Circuit • 55 circuit upgrades covering 11 substations at 3 distinct sites (Bloomfield, Milford, Commerce Lake) • Sites will overlap with AMI installations in Oakland County • DECo offers PCTs and IHDs from Comverge and smart appliances Information Technology (IT) • 15 integrated IT systems to provide a complete and connected picture of the distribution network • Security and Interoperability 7 Continuous Improvement is one of the top corporate priorities Capabilities of the operationally outstanding Capability 1: Design work to see problems • All work is designed so best practices are captured and problems are evident immediately. Capability 2: Swarm problems when they occur Capability 1: Process Design • Problems are immediately addressed, both to contain their effects from propagating, and to trigger problem solving. Failure Mode: Pre-specification to Capability Share ideal3:(no gapknowledge to ideal) where it is created • Knowledge generated locally becomes systemic through shared problem solving. Capability 4: Leaders train, coach, assist and teach • Leaders have to own the capability development process. 8 CMI at DTE Energy: The Perfect Storm • • • • • • • • Awareness of point-to-point problem Awareness of service oriented architecture approach Experience with services development for AMI Promotion to SmartCurrents IT Program Manager CIM revelation at Charlotte Securing DOE funding NIST standards as driver for DOE efforts Control over how interfaces built 9 CMI at DTE Energy: The Perfect Storm 2005 Awareness • Point to point problem • soa 2007 -2008 AMI Experience • MDM services 1 • MDM services 2 2009 DOE Proposal • AMI >> smart grid • IT work streams - - - - - - - - - - - - - - - - 2010 - - - - - - - - - - - - - - DOE Deal • IT Program Mgmt • App Integration scope CIM • Charlotte revelation • Smart grid standards SmartCurrents • App Integration Strategy • ESD team 10 Purpose: Describe SmartCurrents IT approach for managing application interfaces 1. The most significant NIST standard for Smart Grid Interoperability relevant to IT applications is IEC 61968/61970 – Common Information Model (CIM) … and SmartCurrents IT work shall comply 2. SmartCurrents shall develop an Enterprise Semantic Model (ESM) as the basis for all application interfaces 3. SmartCurrents shall have a centralized project team with responsibility to ensure development of ESMcompliant application interfaces 11 IT is key for smart grid through end-to-end system integration of utility operations; CIM is focal point of IT application interoperability standard • “Interoperability” implies both inter-utility and intra-utility • Most standards relate to devices, interconnection, security, but most important to applications pertain to semantics Semantics: The study of meaning; in IT, the meaning or definition of data 12 An ESM is a definition of terms, concepts, and data that is a corporate standard independent of any single department or application Also known as a Canonical Data Model; a proven pattern for system integration Assertions: • The lack of an ESM results in a proliferation of application specific data implementations… this is the root cause of point-to-point interfaces and “accidental architecture” • The CIM is sufficient to provide a basis for a comprehensive ESM that meets the needs of SmartCurrents and DTE Energy • Incremental integration using the ESM to define data messages is a successful approach for ESM refinement and application interface development 13 An industry problem is point-to-point interfaces: each interface is a mapping between two application data implementations GIS OMS CIS AMR WMS DMS 14 The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For Identifying Information Exchange Requirements Among Utility Business Functions All IEC 61968 Activity Diagrams and Sequence Diagrams are organized by the IRM Business Functions Distribution Management External To Distribution Business Functions Management (NO) Network Operation Interface Standard: Part 3 (AM) Records & Asset Management (OP) Operational Planning & Optimization (MC) Maintenance & Construction Interface Standard: Part 4 Interface Standard: Part 5 Interface Standard: Part 6 (EMS) Energy Management & Energy Trading Interface Standard: Part 10 (RET) Retail Interface Standard: Part 10 (SC) Supply Chain and Logistics Interface Standard: Part 10 IEC 61968 Compliant Middleware Services Interface Standard: Part 7 Interface Standard: Part 8 (NE) Network Extension Planning (CS) Customer Support Interface Standard: Part 9 (MR) Meter Reading & Control Electric Distribution Network Planning, Constructing, Maintaining, and Operating Interface Standard: Part 10 (ACT) Customer Account Management Interface Standard: Part 10 Interface Standard: Part 10 Interface Standard: Part 10 (FIN) Financial (PRM) Premises (HR) Human Resources Generation and Transmission Management, Enterprise Resource Planning, Supply Chain, and General Corporate Services 15 CIM Users Group: CIM for Enterprise Integration The CIM provides the basis for the DTE Energy ESM, then we extend it as necessary to meet situational needs 16 Key Concept: Incremental Integration - in Step With Business Needs GIS OMS CIS Semantically Consistent ESB AMR WMS DMS 17 CIM Users Group: CIM for Enterprise Integration The required skills and maturity for ESM/CIMbased implementation requires a centralized approach with our best technical people • Provides: Needs for application integration or interface • Application data semantics • Receives: Service and payload design Application Team (Consumer) • Technical Architect acts as liaison supporting both ESM Services and Application Teams in realizing objectives Enterprise Semantic Model ESD Services Team Industry Standards Groups • Requires: CIM training • Consulting services to assist in mapping application to ESM • Provides: Application data semantics • Receives: Needs for application integration or interface • Service and payload design Application Team (Provider) • Provides: Mapping of application to ESM data • ESM changes • Standards feedback • Implementation specifics (ESB) • Receives: Standards details 18 Several services now exist in our “Service Catalog” Service Name Description Producer Consumer Team Team createMeterReadings Send a request to get meter reading data AMI-MDM CIS getMeterReadings Send a request to get readings from a meter AMI-MDM CIS disconnectMeter Send a request to open the disconnect switch of a meter AMI CIS resetDemand Send a request to reset demand registers of a meter AMI CIS pingMeters Send a request to get energization status for a list of meters AMI AMI Operations powerOutageNotification Send a notification of a power outage event from a meter AMI OMS powerRestorationNotification Send a notification of a power restore event from a meter AMI OMS 19 Services use various CIM objects Service Operation CIM Object implementation MeteringService createMeterReading MeterReading MeteringService pingMeter MeterReading MeteringService resetDemand EndDeviceControl/EndDeviceEvent MeteringService disconnectMeter EndDeviceControl/EndDeviceEvent MeterDataService getMeterReading MeterReading OutageService createdMeterOutage EndDeviceEvent OutageService createdMeterRestoration EndDeviceEvent 20 Steps that the Enterprise Services Development team followed • Jump start session with SISCO guided our first CIM implementations. • Business partners, IT leadership, and development teams participated in CIM orientation. • Working sessions addressed services/object exchanges. • Mapping documents created for services outlining attributes of CIM objects. Corresponding XSDs and WSDLs created. • Producer and Consumer application teams built interfaces based on the contract. 21 As a result of the process, the Enterprise Services Development team proposed CIM changes • Use case: Trouble ticket for reporting power problems. – Developed new objects. – Other attribute format changes. • Left with our consultants to recommend changes with the working groups. 22 Retrospective – What went well? • Availability of industry experts. • Support from CIM community. • CIMUg engagement. • Centralized development team for our Enterprise Semantic Model and services. • Well defined and documented objects. 23 Retrospective – What did we learn? • Leadership support: getting right people involved at the right time. • CIM orientation provides necessary context. • Ambassadorial approach to ensure understanding and engagement. 24 Retrospective – What should we do differently? • Repository of results (document management versus searchable web). • Assume responsibility for entire services design earlier (error handling, SLAs, and other details). 25 Retrospective – What still confuses us? • No visibility into CIM working group. • Confusion around implied duplication. – Example: ‘ping’ a meter for its energization status. MeterReading or EndDeviceControl/Event? • How do we get the right people in the room at the right time? 26 27