1. Mark Ortiz Enterprise Architecture & Standards

2. CIM Data Requirements Overview Based on SEP 2.0 TRD Included previous SEP data requirements, NASBE, and others such as SAE Covers the following messages: n Common n Demand Response & Load Control n Directed & Public Messages n Pricing n Pre-payment n Metering and Sub-metering (OpenSG) n PEV n DER n Billing

3. Modeling Based on IEC CIM model & 61850, 61968, 61970 (such as Part-9 metering and control) New models (classes/attributes/relationships) based on SEP2.0 TRD for DER & PEV

4. Distribution Energy Resources

5. Mainly three new classes involved: n DistributedEnergySource is a node for a DistributedGeneratingUnit from network perspective. It just likes a ServiceDeliveryPoint links to a MeterAsset. DistributedEnergySource has a relationship to EndDeviceAsset just like SDP has a relationship to EndDeviceAsset so that metering can be established for a DistributedEnergySource/DistributedGeneratingUnit. n DistributedEnergySource (DES) could be associated with HANAsset (Now PANDeviceAsset) if it is in a HAN environment. n DES could be associated with a Battery (or name changed to EnergyStorage). n PowerGenerationCurve is associated with DistributedGeneratingUnit for energy output (measurement)

6. Example on how SEP 2.0 UML aligns with CIM UML SEP 2.0 Pricing Data Model New attribute (href) To identify a RESTful resource New class to meet SEP 2.0 TRD requirements

7. Example on how SEP 2.0 UML aligns with CIM UML CIM Pricing Structure Model

8. RESTFul Service Definition Input n Using HTTP GET or POST following URL naming convention Output n Using XSD for return

9. RESTFul URL Naming Convention n / / such as u http://www.zigbee.org/datastore/MeterReading/Readings (for all readings) or u http://www.zigbee.org/datastore/MeterReading/Readings/?timeStamp= 2010-02-02T00:00:00Z (for readings with the timestamp)

10. RESTFul DER for a PEV Convention GET /dgu{#} returns the DGU for a PEV The client would send: GET /dgu/0 HTTP/1.1 Host: {IPv6 Address} The server would respond: HTTP/1.1 200 OK Content-Type: application/xml Content-Encoding: exi 001 002