Mark ortiz enterprise architecture standards
Download
1 / 10

Mark Ortiz Enterprise Architecture & Standards - PowerPoint PPT Presentation


  • 48 Views
  • Uploaded on

Mark Ortiz Enterprise Architecture & Standards . 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: Common Demand Response & Load Control Directed & Public Messages Pricing

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Mark Ortiz Enterprise Architecture & Standards ' - patrick-leach


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Mark ortiz enterprise architecture standards

Mark Ortiz Enterprise Architecture & Standards


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:

    • Common

    • Demand Response & Load Control

    • Directed & Public Messages

    • Pricing

    • Pre-payment

    • Metering and Sub-metering (OpenSG)

    • PEV

    • DER

    • Billing


Modeling
Modeling

  • Based on IEC CIM model & 61850, 61968, 61970 (such as Part-9metering and control)

  • New models (classes/attributes/relationships) based on SEP2.0 TRD for DER & PEV



Distribution energy resources1
Distribution Energy Resources

  • Mainly three new classes involved:

    • 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.

    • DistributedEnergySource (DES) could be associated with HANAsset (Now PANDeviceAsset) if it is in a HAN environment.

    • DES could be associated with a Battery (or name changed to EnergyStorage).

    • PowerGenerationCurve is associated with DistributedGeneratingUnit for energy output (measurement)


Example on how sep 2 0 uml aligns with cim uml
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



Restful service definition
RESTFul Service Definition

  • Input

    • Using HTTP GET or POST following URL naming convention

  • Output

    • Using XSD for return


Restful url naming convention
RESTFul URL Naming Convention

  • <Service Namespace>/<root element>/<child element> such as

    • http://www.zigbee.org/datastore/MeterReading/Readings  (for all readings)

      or

    • http://www.zigbee.org/datastore/MeterReading/Readings/?timeStamp=2010-02-02T00:00:00Z  (for readings with the timestamp)


Restful der for a pev convention
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

    <?xml version=’1.0’ encoding=’UTF-8’?>

    <DistributedGeneratingUnithref=”http{s}://{IPv6 Address}/dgu/0”>

    <ID>001</ID>

    </DistributedGeneratingUnit>

    <DistributedGeneratingUnithref=”http{s}://{IPv6 Address}/dgu/1”>

    <ID>002</ID>

    </DistributedGeneratingUnit>


ad