Addition of optional cost attribute to allow for cost annotated interval data (power:energyPrice) This modification allows for an optional inclusion of cost annotated usage data in SEP 2.0 supporting devices. As optional, it adds no overhead to SEP 2.0 messaging for the limited set of use cases SEP 2.0 addresses, yet, it supports directly the ability of devices and services to expose the results of complex cost allocation models without having to have the capability to compute those costs. Support for extension of service delivery point specification APnode etc... This extension of description to include the optional elements identified as important by EMIX would facilitate cross-protocol propagation of information for relevant use cases. NAESB Addition of EMIX ids and optional extrinsic property structure Enumerations in the EMIX standard should be reviewed and used to extend those in the NAESB standard to ensure a union of values for covered types. Extension of ServiceDeliveryPoint to include EMIX attributes As described in 3.2.1.6, this would be a useful enhancement to the NAESB standard and would harmonize better with EMIX. Validation of changes to schemas In order to test the modified schemas, two test cases were implemented: Verify that EMIX Use Cases can be implemented with the proposed schema modifications Verify that the reference Use Case can be implemented in SEP 2.0 and EMIX with a one to one correspondence of content Verifying EMIX Schemas the EMIX schemas, an xml example file implementing figure 4-1 EMIX Model from the standard was produced. Here is the figure from the EMIX draft standard: Figure 17: Copy of figure 4-1 from EMIX working draft Here is an XMLSpy rendition of an XML example implementing that use case: Figure 18: XML file implementing figure 4-1 from EMIX Verifying correspondence between XML files implementable based on SEP 2.0 and EMIX enhanced schemas Using same schemas produce an xml example file that implements the same data as the SEP2.0 example presented at the Tiger Team meeting. First, here is an XMLSpy view of the sample SEP 2.0 price schedule: Figure 19: SEP2.0 TT Example Use Case
Addition of optional cost attribute to allow for cost annotated interval data (power:energyPrice) This modification allows for an optional inclusion of cost annotated usage data in SEP 2.0 supporting devices. As optional, it adds no overhead to SEP 2.0 messaging for the limited set of use cases SEP 2.0 addresses, yet, it supports directly the ability of devices and services to expose the results of complex cost allocation models without having to have the capability to compute those costs. Support for extension of service delivery point specification APnode etc... This extension of description to include the optional elements identified as important by EMIX would facilitate cross-protocol propagation of information for relevant use cases. NAESB Addition of EMIX ids and optional extrinsic property structure Enumerations in the EMIX standard should be reviewed and used to extend those in the NAESB standard to ensure a union of values for covered types. Extension of ServiceDeliveryPoint to include EMIX attributes As described in 3.2.1.6, this would be a useful enhancement to the NAESB standard and would harmonize better with EMIX. Validation of changes to schemas In order to test the modified schemas, two test cases were implemented: Verify that EMIX Use Cases can be implemented with the proposed schema modifications Verify that the reference Use Case can be implemented in SEP 2.0 and EMIX with a one to one correspondence of content Verifying EMIX Schemas the EMIX schemas, an xml example file implementing figure 4-1 EMIX Model from the standard was produced. Here is the figure from the EMIX draft standard: Figure 17: Copy of figure 4-1 from EMIX working draft Here is an XMLSpy rendition of an XML example implementing that use case: Figure 18: XML file implementing figure 4-1 from EMIX Verifying correspondence between XML files implementable based on SEP 2.0 and EMIX enhanced schemas Using same schemas produce an xml example file that implements the same data as the SEP2.0 example presented at the Tiger Team meeting. First, here is an XMLSpy view of the sample SEP 2.0 price schedule: Figure 19: SEP2.0 TT Example Use Case
TTMeetingOnPriceCommunications_r2_RD4PUB.docx