1. Managers Guide to AMI Enterprise

2. AMI Enterprise What it is Why you need to be involved How you get involved Who from your organization needs to be involved When to get involved Where to get involved

3. AMI Enterprise What –Task force chartered under the UCA International Users Group (UCAIug): ucaiug.org –Utility led and vendor supported –Standards-based, eg. IEC 61968, Multispeak, WS-I –With goals to define: Common business processes Common architecture principles and patterns Common data model Common information services; (functions & interfaces) Tested interoperability between vendor products

4. AMI Enterprise 2009 Roadmap Highlights –March First draft of Services Documentation Services Master list WSDLs/XSDs –June Collaboration Strategy, eg., IEC WG14 and MultiSpeak –September Interoperability testing –December Ratification Goal is to get a baseline documents and artifacts ratified for a subset of use cases (per utility prioritization, for example, meter to cash…) and establish a foundation for future work beyond 2009. Goal is also to be lock step with associated SDOs so that proposed use cases and design artifacts will be adopted as standards.

5. AMI Enterprise Why –Utilities have an opportunity to learn from others, contribute their best practices and lessons learned, and implement a better solution in the end. –Utilities will have an opportunity to leverage work products from AMI-ENT in their AMI/SmartGrid RFI/RFP process. –As more utilities participate, vendors are encouraged to comply with standards –Common services and interfaces drives down acquisition and TCO costs and risks of implementation and maintenance. –Vendors will have to compete on merits (features) of their solution and how well they interoperate with others, rather than attempt to lock in with proprietary technologies.

6. AMI Enterprise How –Participation in a sub-team Services Requirements Documentation Use Case sub-team Services Definition sub-team –Reviewing and Contributing Deliverables are posted on smartgridipedia.org Utilizing deliverables in RFPs

7. AMI Enterprise Who – –Dependent on interest area Services Requirements Documentation –Business Process Analysts, Enterprise Architects, Vendor product/solution architects Use Case development –Industry specialists, Enterprise Architects, Business Analysts, Vendor product managers. Services Definition Team –Integration Architects, Services Architects, Enterprise Architects, Software Architects, Vendor integration architects and developers.

8. AMI Enterprise When –Bi-monthly face-to-face meetings –2009 Jan – Palo Alto Mar – Miami May – Knoxville Jul – Sep – Nov – –Sub-team conference calls per interest group

9. AMI Enterprise Representation American Electric Power Centerpoint Consumers Energy Detroit Edison Duke Energy Florida Power & Light Pacific Gas & Electric San Diego Gas & Electric Southern California Edison Your utility here Vendor? Representing approximately: XX million meters

10. UCA Membership How to join: –www.blahblahblah.comwww.blahblahblah.com Cost to join: –$$$

11. Key Contacts Wayne Longcore Co-Chairwrlongcore@cmsenergy.com Greg RobinsonCo-Chairgrobinson@xtensible.net Terry MohnUse Case definition tmohn@sempra.com Joe ZhouOverall Documentation jzhou@xtensible.net Gerald GrayServices Definition grgray@cmsenergy.com