Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: No Action
    • Affects Version/s: CSD03/PR03
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Marty Burns PR03 Comments

    • Resolution:
      Hide

      Close, no action--not in scope of Public Review 03.

      Show
      Close, no action--not in scope of Public Review 03.

      Description

      See http://lists.oasis-open.org/archives/emix-comment/201108/msg00000.html ; text copied below.

      Subject: FW: [PAP09] Process needed to maintain alignment between SEP 2 and OASIS EMIX

      From: "Marty Burns" <burnsmarty@aol.com>
      To: <emix-comment@lists.oasis-open.org>
      Date: Thu, 11 Aug 2011 10:38:04 -0400

      All,

      The forwarded email comes from Don Sturek as a result of the presentations
      in the SGIP PAP030409 review session held yesterday. It illustrates some of
      the concerns with the current draft that should be addressed prior to
      completion of the standard.

      Those of us who have worked long and hard to support this effort with our
      in-depth analysis, review, and comments would like to see the ultimate
      result have a strong interoperability path with SEP 2.0.

      Cheers,
      Marty

      ----Original Message----
      From: SGIP PAP09 Working Group SGIP-PAP09WG@SMARTGRIDLISTSERV.ORG
      On Behalf Of Don Sturek
      Sent: Wednesday, August 10, 2011 5:33 PM
      To: SGIP-PAP09WG@SMARTGRIDLISTSERV.ORG
      Subject: [PAP09] Process needed to maintain alignment between SEP 2 and
      OASIS EMIX

      On today's PAP 3, 4 and 9 call, I brought up a concern around alignment
      between the OASIS EMIX work and ZigBee SEP 2.0. This alignment is also
      needed in the OpenADR.org group.

      Here is some background:
      1) PAP 10 aligned the seed standard from ZigBee SEP 2.0 with the EIS
      Alliance (since folded into ASHRAE SPC201) plus aligned the data from the
      OASIS EMIX work (at the time)
      2) There was a PAP 3, 4, 9 alignment meeting between OASIS, OpenADR and
      ZigBee SEP 2 last December where some useful differences were noted and
      folded into OASIS EMIX comments.
      3) The OASIS EMIX work is close to completion and will be the starting
      point for the OpenADR.org work.
      4) Likewise, ZigBee SEP 2 is out for public comment which closes on Sunday.
      5) The gameplan in ZigBee SEP 2 is still to donate the UML model back to
      IEC 61968 for consideration (and as a standards repository)

      Here are the artifacts we have to work with on this alignment:
      1) ZigBee SEP 2 started with the iEC 61968 model and extended it for PEV,
      DER and DR use cases. This model was aligned with the SGIP through the PAP
      10 process.
      2) ZigBee SEP 2 uses XSDs derived from the model above as its normative
      reference. The model is not normative but used to derive these XSDs
      3) OASIS EMIX uses a data model and has reverse engineered a UML model. I
      was not clear on whether this was analyzed with the PAP 10 work for
      alignment or not.

      My main concern with the above process is how to keep the underlying object
      models aligned so that smart grid implementers (whether in the utility back
      office or in a translation box in a premise) can clearly map between the SEP
      2 and OASIS EMIX standards. Right now, I am not 100% sure this is possible
      and going forward I think we all agreed some process is needed to ensure
      this alignment.

      So my request in this note is two fold:
      1) Go through one last alignment review of SEP 2 and OASIS EMIX to be sure
      these standards, when launched, have a clear mapping.
      2) Absent a reference-able UML model that both can use to facilitate a
      mapping, we need a procedure to ensure that future revisions of OASIS EMIX
      and SEP 2 remain in alignment from a data model point of view.

      Don

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              william.cox William Cox (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: