6. CONCLUSION AND FUTURE WORK
6.2 Future Work
The infrastructure developed as part of this thesis, is in the early stage. The infrastructure must be improved to be flexible and interoperable in future work. Some of those improve-ments are discussed in this section.
Firstly, the infrastructure is not robust while mapping with the MES system. Therefore, more MES functions must be coupled with the demand response functions. The ISA – 95 standard must consider including the demand response program function. The program must be an integral part of all the manufacturing industry who is accepting industrial rev-olution 4.0.
The portlet communication is good for limited number of resources. But with the increased number of resource in the facility, transmitting and receiving of information becomes com-plex. Therefore, IoT communication protocol like CoAP must be considered instead of HTTP. The user interface for demand response program could be much simpler so that anyone can easily learn. Therefore, testing of the user interface is required deploying to the facility.
As a final note, demand response might seems like a simple task to integrate to an existing infrastructure. But in reality implementing the demand response infrastructure require more investment. Some facilities understand the real value in DR program and starts to invest in it. But some does not want to step out from their favorable conditions. The gov-ernment need to provide incentives to those willing to participate in DR program and more pilot programs are needed to evaluate the programs.
REFERENCES
[1] “Electricity use by machine drives varies significantly by manufacturing industry - Today in Energy - U.S. Energy Information Administration (EIA).” [Online]. Availa-ble: https://www.eia.gov/todayinenergy/detail.php?id=13431. [Accessed: 22-Mar-2018].
[2] C.-W. Park et al., “Energy consumption reduction technology in manufacturing — A selective review of policies, standards, and research,” Int. J. Precis. Eng. Manuf., vol.
10, no. 5, pp. 151–173, Dec. 2009.
[3] “FERC: Industries - Reports on Demand Response & Advanced Metering.” [Online].
Available: https://www.ferc.gov/industries/electric/indus-act/demand-response/dem-res-adv-metering.asp. [Accessed: 23-Mar-2018].
[4] S. Bougain, D. Gerhard, C. Nigischer, and S. Uĝurlu, “Towards Energy Management in Production Planning Software Based on Energy Consumption as a Planning Re-source,” Procedia CIRP, vol. 26, pp. 139–144, 2015.
[5] J. Torriti, M. G. Hassan, and M. Leach, “Demand response experience in Europe: Pol-icies, programmes and implementation,” Energy, vol. 35, no. 4, pp. 1575–1583, Apr.
2010.
[6] N. O׳Connell, P. Pinson, H. Madsen, and M. O׳Malley, “Benefits and challenges of electrical demand response: A critical review,” Renew. Sustain. Energy Rev., vol. 39, pp. 686–699, Nov. 2014.
[7] N. G. Paterakis, O. Erdinç, and J. P. S. Catalão, “An overview of Demand Response:
Key-elements and international experience,” Renew. Sustain. Energy Rev., vol. 69, pp.
871–891, Mar. 2017.
[8] “Market data.” [Online]. Available: http://www.nordpoolspot.com/Market-data1/Dayahead/Area-Prices/FI/Hourly/. [Accessed: 04-Apr-2018].
[9] “Demand-Side Management,” Fingrid. [Online]. Available: https://www.fin-grid.fi/en/electricity-market/demand-side-management/. [Accessed: 04-Apr-2018].
[10] V. S. K. Murthy Balijepalli, V. Pradhan, S. A. Khaparde, and R. M. Shereef, “Re-view of demand response under smart grid paradigm,” 2011, pp. 236–243.
[11] “Demand Response | Department of Energy.” [Online]. Available: https://www.en- ergy.gov/oe/activities/technology-development/grid-modernization-and-smart-grid/demand-response. [Accessed: 14-Apr-2018].
[12] F. Shariatzadeh, P. Mandal, and A. K. Srivastava, “Demand response for sustainable energy systems: A review, application and implementation strategy,” Renew. Sustain.
Energy Rev., vol. 45, pp. 343–350, May 2015.
[13] “Benefits of Demand Response in Electricity Markets and Recommendations for Achieving Them,” p. 122.
[14] O. Abrishambaf, M. A. F. Ghazvini, L. Gomes, P. Faria, Z. Vale, and J. M.
Corchado, “Application of a Home Energy Management System for Incentive-Based Demand Response Program Implementation,” in 2016 27th International Workshop on Database and Expert Systems Applications (DEXA), 2016, pp. 153–157.
[15] H. A. Aalami, M. P. Moghaddam, and G. R. Yousefi, “Demand response modeling considering Interruptible/Curtailable loads and capacity market programs,” Appl. En-ergy, vol. 87, no. 1, pp. 243–250, 2010.
[16] P. Cappers, J. MacDonald, and C. Goldman, “Market and Policy Barriers for De-mand Response Providing Ancillary Services in U.S. Markets,” p. 61.
[17] Dong-Min Kim and Jin-O Kim, “Design of Emergency Demand Response Program Using Analytic Hierarchy Process,” IEEE Trans. Smart Grid, vol. 3, no. 2, pp. 635–
644, Jun. 2012.
[18] J. Saebi, H. Taheri, J. Mohammadi, and S. S. Nayer, “Demand bidding/buyback modeling and its impact on market clearing price,” 2010, pp. 791–796.
[19] Shen Zhao and Zhou Ming, “Modeling demand response under time-of-use pric-ing,” 2014, pp. 1948–1955.
[20] P. Cappers, A. Todd, and C. A. Goldamn, “Summary of Utility Studies: Smart Grid Investment Grant Consumer Behavior Study Analysis,” LBNL--6248E, 1171525, May 2013.
[21] M. A. R. Muzmar, M. P. Abdullah, M. Y. Hassan, and F. Hussin, “Time of Use pricing for residential customers case of Malaysia,” 2015, pp. 589–593.
[22] M. Ambrosio, “Assessment of Customer Response to Real Time Pricing,” p. 23.
[23] P. Ponnaganti, J. R. Pillai, and B. Bak-Jensen, “Opportunities and challenges of demand response in active distribution networks: Opportunities and challenges of de-mand response,” Wiley Interdiscip. Rev. Energy Environ., vol. 7, no. 1, p. e271, Jan.
2018.
[24] M. Miner, “Wholesale Electricity Markets.” .
[25] “Introduction to electricity markets, its balancing mechanism and the role of renew-able sources.” .
[26] “The main arena for trading power.” [Online]. Available: http://www.nordpool-spot.com/the-power-market/Day-ahead-market/. [Accessed: 03-May-2018].
[27] “European Demand Response (DR) Market, 2018–2025.” [Online]. Available:
https://cds.frost.com/p/56579/#!/ppt/c?id=MDDC-01-00-00-00.
[28] S. P. Burger and M. Luke, “Business models for distributed energy resources: A review and empirical analysis,” Energy Policy, vol. 109, pp. 230–248, Oct. 2017.
[29] C. Roe, S. Meliopoulos, R. Entriken, and S. Chhaya, “Simulated demand response of a residential energy management system,” in IEEE 2011 EnergyTech, 2011, pp. 1–
6.
[30] Yuemin Ding and S. H. Hong, “A model of demand response energy management system in industrial facilities,” 2013, pp. 241–246.
[31] S. Mitra, I. E. Grossmann, J. M. Pinto, and N. Arora, “Optimal production planning under time-sensitive electricity prices for continuous power-intensive processes,”
Comput. Chem. Eng., vol. 38, pp. 171–184, Mar. 2012.
[32] T. Samad and S. Kiliccote, “Smart grid technologies and applications for the indus-trial sector,” Comput. Chem. Eng., vol. 47, pp. 76–84, Dec. 2012.
[33] H. Fraser, “The Importance of an Active Demand Side in the Electricity Industry,”
Electr. J., vol. 14, no. 9, pp. 52–73, Nov. 2001.
[34] G. Strbac, “Demand side management: Benefits and challenges,” Energy Policy, vol. 36, no. 12, pp. 4419–4426, Dec. 2008.
[35] S. Valero, M. Ortiz, C. Senabre, C. Alvarez, F. J. G. Franco, and A. Gabaldon,
“Methods for customer and demand response policies selection in new electricity mar-kets,” IET Gener. Transm. Distrib., vol. 1, no. 1, p. 104, 2007.
[36] A. Mutanen, M. Ruska, S. Repo, and P. Jarventausta, “Customer Classification and Load Profiling Method for Distribution Systems,” IEEE Trans. Power Deliv., vol. 26, no. 3, pp. 1755–1763, Jul. 2011.
[37] N. Mahmoudi-Kohan, M. K. Sheikh-El-Eslami, and S. M. Bidaki, “Improving WFA K-means Technique for Demand Response Programs Applications,” p. 5.
[38] A. J. Roscoe and G. Ault, “Supporting high penetrations of renewable generation via implementation of real-time electricity pricing and demand response,” IET Renew.
Power Gener., vol. 4, no. 4, p. 369, 2010.
[39] “Energy Interoperation Version 1.0.” [Online]. Available: http://docs.oasis-open.org/energyinterop/ei/v1.0/energyinterop-v1.0.html. [Accessed: 07-May-2018].
[40] “Extensible Markup Language (XML) 1.0 (Fifth Edition).” [Online]. Available:
https://www.w3.org/TR/2008/REC-xml-20081126/. [Accessed: 07-May-2018].
[41] “OASIS Web Services Calendar (WS-Calendar) TC | OASIS.” [Online]. Available:
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-calendar. [Ac-cessed: 07-May-2018].
[42] “Energy Market Information Exchange (EMIX) Version 1.0.” [Online]. Available:
http://docs.oasis-open.org/emix/emix/v1.0/emix-v1.0.html. [Accessed: 07-May-2018].
[43] M. Piette et al., “Open Automated Demand Response Communications Specifica-tion (Version 1.0),” 2009. .
[44] “Home.” [Online]. Available: http://www.openadr.org/. [Accessed: 15-May-2018].
[45] “OpenADR - Nestfield.” [Online]. Available: https://sites.google.com/a/nest-field.co.kr/nestfield/home_e/openadr. [Accessed: 15-May-2018].
[46] “OpenADR 2.0 Profile Specification B Profile.” .
[47] Girish Ghatikar and R. Bienert, “Smart Grid Standards and Systems Interoperabil-ity: A Precedent with OpenADR,” Unpublished, 2011.
[48] “Smart Energy Profile 2.0 Application Protocol Standard,” p. 339, 2013.
[49] B. Ash and R. Simpson, “IEEE 2030.5: Relationship to other Smart Grid Standards, Testing and Certification,” p. 73.
[50] “96/05639 BACnet. A data communication protocol for building automation and control networks,” Fuel Energy Abstr., vol. 37, no. 5, p. 390, Sep. 1996.
[51] “The Language of BACnet.” [Online]. Available: http://www.bacnet.org/Bibliog-raphy/ES-7-96/ES-7-96.htm. [Accessed: 15-May-2018].
[52] V. Boed, Networking and Integration of Facilities Automation Systems. CRC Press, 1999.
[53] F. Luo, K. Q. Xiong, B. Li, M. Zhong, and H. G. Yan, “Extending IEC 61968 to Support Wide Area Demand Response Program,” Appl. Mech. Mater., vol. 701–702, pp. 1337–1342, Dec. 2014.
[54] C. Scott, “Comparison of Demand Response Communication Protocols,” Tech.
Rep., p. 21, 2011.
[55] P. Simoneau, “The OSI Model: Understanding the Seven Layers of Computer Net-works,” p. 11.
[56] P. J. Leach, T. Berners-Lee, J. C. Mogul, L. Masinter, R. T. Fielding, and J. Gettys,
“Hypertext Transfer Protocol -- HTTP/1.1.” [Online]. Available:
https://tools.ietf.org/html/rfc2616. [Accessed: 22-May-2018].
[57] L. Masinter, “Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).” [Online].
Available: https://tools.ietf.org/html/rfc2324. [Accessed: 22-May-2018].
[58] M. Hauswirth and M. Jazayeri, “A Component and Communication Model for Push Systems?,” p. 19.
[59] M. Shariff, A. Bhandari, P. Majmudar, and V. Choudhary, “Alfresco 3 Web Content Management,” p. 32.
[60] M. M. HOSSAIN, “PORTLET-BASED PRESENTATION OF ENERGY KPIS IN SOA- ENABLED MANUFACTURING FACILITIES TARGETING HOLISTIC EN-ERGY MANAGEMENT,” p. 95.
[61] D. Schachinger, S. Gaida, and W. Kastner, “Smart grid communication at the inter-face of customer buildings with focus on demand response,” 2015, pp. 368–373.
[62] A. T. McKane et al., “Opportunities, Barriers and Actions for Industrial Demand Response in California,” LBNL-1335E, 945364, Jan. 2008.
[63] U. Herberg, D. Mashima, J. G. Jetcheva, and S. Mirzazad-Barijough, “OpenADR 2.0 deployment architectures: Options and implications,” 2014, pp. 782–787.
[64] S. H. Hong, “Development of a BACnet-ZigBee gateway for demand response in buildings,” 2013, pp. 19–23.
[65] S. Son, H. Lee, and B.-T. Lee, “CoAP-based lightweight information exchange technique for demand response,” 2017, pp. 973–975.
[66] A. Keranen, M. Ersue, and C. Bormann, “Terminology for Constrained-Node Net-works.” [Online]. Available: https://tools.ietf.org/html/rfc7228. [Accessed: 22-May-2018].
[67] T. Sato et al., Smart Grid Standards : Specifications, Requirements, and Technolo-gies. Singapore, SINGAPORE: John Wiley & Sons, Incorporated, 2015.
[68] W. T. ZHANG Jing, “Research on Technical Standardization for Electric Demand Response,” Proceeding CSEE, vol. 34, no. 22, pp. 3623–3629, 2014.
[69] M. A. Piette, G. Ghatikar, S. Kiliccote, D. Watson, E. Koch, and D. Hennage, “De-sign and Operation of an Open, Interoperable Automated Demand Response Infra-structure for Commercial Buildings,” J. Comput. Inf. Sci. Eng., vol. 9, no. 2, p. 021004, 2009.
[70] “Introduction to Liferay Development - Liferay 7.0 - Liferay Developer Network.”
[Online]. Available: https://dev.liferay.com/fi/develop/tutorials/-/knowledge_base/7-0/introduction-to-liferay-development. [Accessed: 11-Jul-2018].
[71] “Maven Repository: com.liferay.faces » liferay-faces-bridge-impl » 4.2.5-ga6.”
[Online]. Available: https://mvnrepository.com/artifact/com.liferay.faces/liferay-faces-bridge-impl/4.2.5-ga6. [Accessed: 11-Jul-2018].
[72] D. A. Lobov and J. L. M. Lastra, “WAEL MOHAMMED ENCAPSULATION OF MES FUNCTIONALITIES AS RESTFUL WEB SERVICES FOR KNOWLEDGE-DRIVEN MANUFACTURING SYS- TEMS,” p. 65.
APPENDIX A – EMIX CLASSES AND MESSAGE SCHEMA
This XML file does not appear to have any style information associated with it.
The document tree is shown below [42]
<!--
Energy Market Information Exchange (EMIX) Version 1.0 Committee Specification 02
11 January 2012
Copyright (c) OASIS Open 2012. All Rights Reserved.
Source: http://docs.oasis-open.org/emix/emix/v1.0/cs02/xsd/
-->
EMIX, EMIX-Termss, EMIX-Warrants (emix)
Power, Power-Contracts, Power-Quality (power) Resource (resource)
-->
<!-- 1.0 EMIX: Energy Market Information Exchange -->
<xs:schema
<xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0"
Emix Product, .i.e., a Product Description applied to a schedule.
</xs:documentation>
EMIX Product Type, i.e. a Product Description applied to a Schedule
</xs:documentation>
<xs:element ref="emix:expirationDate" minOccurs="0" maxOccurs="1"/>
<xs:element ref="emix:integralOnly" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>
As part of a Tender, indicates element must be accepted in full or rejected
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="emix:currency" minOccurs="0" maxOccurs="1"/>
<xs:element ref="emix:marketContext"/>
<xs:element ref="emix:side"/>
<xs:element ref="emix:terms" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
<xs:documentation>Option to buy an Emix Product</xs:documentation>
</xs:annotation>
<xs:element ref="emix:expirationDate" minOccurs="0" maxOccurs="1"/>
<xs:element ref="emix:integralOnly" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>
If true, each Option Call must be for the full amount specified
</xs:documentation>
</xs:annotation>
<xs:element ref="emix:currency" minOccurs="0" maxOccurs="1"/>
<xs:element ref="emix:terms" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
Receipt / Report of Product Delivery. Injection flag is true for adding product to market supply, false for taking from market.
</xs:documentation>
<xs:element ref="emix:warrants" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
<!-- 8.0 Supporting Information Structures -->
<!-- 8.2 Market defintions -->
</xs:restriction>
<xs:documentation>Currency codes coming from UN CEFACT schemas</xs:docu-mentation>
<xs:element name="priceBase" type="emix:PriceBaseType" abstract="true">
<xs:annotation>
<xs:documentation>Abstract base for EMIX Prices</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="PriceBaseType" abstract="true">
<xs:annotation>
<xs:documentation>Type of Abstract base for EMIX Prices</xs:documenta-tion>
<xs:element ref="emix:value" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- 8.3.2 Multiplier Price - multiplier on base amount -->
<xs:element name="priceMultiplier" type="emix:PriceMultiplierType" sub-stitutionGroup="emix:priceBase"/>
<xs:complexType name="PriceMultiplierType" mixed="false">
<xs:annotation>
<xs:documentation>
Multiplier times market price, 1 for same as market
<xs:element name="multiplier" type="xs:float" minOccurs="1" max-Occurs="1"/>
<xs:element ref="emix:marketContext" minOccurs="0" maxOccurs="1">
<xs:annotation>
8.3.4 Price Offset (additive or subtractive) over base amount -->
Price Relative is a fixed charge (positive or negative) apllied to base price
<xs:element ref="emix:value" minOccurs="1" maxOccurs="1"/>
<xs:element ref="emix:marketContext" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:simpleType name="IntegralOnlyType">
<xs:annotation>
<xs:documentation>
Integral Only is an indication that the element described is [tendered]
as an all or nothing product. It may apply to an (amount, response, ramp) that is all (true) or nothing (false)
</xs:documentation>
An autonomous resource or service (true) is able to respond or maintain service independently. A non autonomous service (false) must await dis-patch.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:boolean"/>
</xs:simpleType>
<!-- 8.7 Enumeration for Option Types -->
<xs:element name="optionType" type="emix:OptionTypeType"/>
<!--9.1 Abstract EMIX Base(product applied to a schedule)-->
<xs:element name="emixBase" type="emix:EmixBaseType"/>
<xs:complexType name="EmixBaseType" abstract="true">
<xs:annotation>
<xs:documentation> iCalendar-derived object to host EMIX ele-ments</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xcal:VcalendarType">
<xs:sequence>
<xs:element ref="emix:uid" minOccurs="1" maxOccurs="1"/>
<xs:element ref="emix:envelopeContents" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- 9.2 Abstract Product Description -->
<xs:element name="productDescription" type="emix:ProductDescription-Type" abstract="true" substitutionGroup="xcal:artifactBase"/>
<xs:complexType name="ProductDescriptionType" abstract="true">
<xs:annotation>
<xs:documentation>
In EMIX, the Product Description is placed in the Interval or Gluon attachment. The respective product schemas extend this abstract class.
</xs:documentation>
The Service Area is the geographic region that is affected by the EMIX market condition
<xs:complexType name="EmixInterfaceType" abstract="true" mixed="false">
<xs:annotation>
<xs:documentation>
Abstract base class for the interfaces for EMIX Product delivery, meas-urement, and/or pricing
Abstract base class used for granularity of market indications of interest and tenders
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="itemBase" type="emix:ItemBaseType" abstract="true"/>
<xs:complexType name="ItemBaseType" abstract="true" mixed="false">
<xs:annotation>
<xs:documentation>
Abstract base type for units for EMIX Product delivery, measurement, and warrants. Item as in PO Item, Requisition Item, Invoice Item, Lading Item. Item does not include Quantity or Price, because a single product description or transaction may have multiple quantities or prices asso-ciated with a single item.
</xs:documentation>
A unique identifier for an EMIX Type. Different markets and specifications that use EMIX may have their own rules for specifying an UID.
</xs:documentation>
<xs:documentation>Base type for all quanties in EMIX.</xs:documentation>
</xs:annotation>
Expiration date for tenders and similar related information.
</xs:documentation>
Pattern used for extending string enumeration, where allowed
</xs:documentation>
APPENDIX B – EIREGISTERATION AND EIPARTY SCHEMA’S
The corresponding XSD (XML Schema Definition) for EiRegisterationType and EiParty is given below:
The Figure below depicts eiRegisteration operation payload. EiRequestPartyRegistration-Type, EiReplyPartyRegistrationEiRequestPartyRegistration-Type, EiCreatePartyRegistrationEiRequestPartyRegistration-Type, EiCreatedPar-tyRegistrationType, EiCancelPartyRegistrationType are the information model communi-cated sequentially between the DR participants during registration.
The corresponding XSD (XML Schema Definition) for eiRegisteration operation payload is given below:
eiCreatePartyRegisteration:
<xs:element name="eiCreatePartyRegistration" type="pyld:EiCreatePartyRegistra-tionType"/>
<xs:complexType name="EiCreatePartyRegistrationType">
<xs:annotation>
<xs:documentation>Used to create and send a Party Registration re-quest.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element ref="pyld:requestID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registreePartyID" minOccurs="0"
<xs:element ref="ei:eiResponse" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrarPartyID" minOccurs="0" max-Occurs="1"/>
<xs:element ref="ei:registrationID" minOccurs="0" maxOccurs="1"/>
<xs:element ref="ei:registreePartyID" minOccurs="0" max-Occurs="1"/>
</xs:sequence>
</xs:complexType>
eiRequestPartyRegisteration:
<xs:element name="eiRequestPartyRegistration" type="pyld:EiRequestPartyRegis-trationType"/>
<xs:annotation>
<xs:documentation>Request for information about extant registra-tions.</xs:documentation>
</xs:annotation>
<xs:complexType name="EiRequestPartyRegistrationType">
<xs:sequence>
<xs:element ref="pyld:requestID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registreePartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrarPartyID" minOccurs="0" maxOccurs="1"/>
<xs:element ref="ei:requestorPartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrationID" minOccurs="0" maxOccurs="un-bounded"/>
<xs:element ref="xcal:interval" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:documentation>If present, limits range of request to reg-istrations within Interval.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
eiReplyPartyRegisteration:
<xs:element name="eiReplyPartyRegistration" type="pyld:EiReplyPartyRegistra-tionType"/>
<xs:complexType name="EiReplyPartyRegistrationType">
<xs:sequence>
<xs:element ref="ei:eiRegistration" minOccurs="0" maxOccurs="un-bounded"/>
<xs:element ref="ei:eiResponse" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:responses" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
eiCancelPartyRegisteration:
<xs:element name="eiCancelPartyRegistration" type="pyld:EiCancelPartyRegistra-tionType"/>
<xs:complexType name="EiCancelPartyRegistrationType">
<xs:annotation>
<xs:documentation>Used to cancel one or more Party Registrations.</xs:doc-umentation>
</xs:annotation>
<xs:sequence>
<xs:element ref="pyld:requestID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registreePartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrarPartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrationID" minOccurs="1" maxOccurs="un-bounded"/>
</xs:sequence>
</xs:complexType>
eiCanceledPartyRegisteration:
<xs:element name="eiCanceledPartyRegistration" type="pyld:EiCanceledPartyReg-istrationType"/>
<xs:complexType name="EiCanceledPartyRegistrationType">
<xs:sequence>
<xs:element ref="ei:respondingPartyID" minOccurs="1" max-Occurs="1"/>
<xs:element ref="ei:registreePartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:registrarPartyID" minOccurs="1" maxOccurs="1"/>
<xs:element ref="ei:eiResponse" minOccurs="0" maxOccurs="un-bounded"/>
<xs:element ref="ei:responses" minOccurs="0" maxOccurs="un-bounded"/>
</xs:sequence>
</xs:complexType>
APPENDIX C – EIQUOTE AND EMIXBASE TYPE SCHEMA’S
The corresponding XSD (XML Schema Definition) for EiQuoteType and EmixBaseType is given below in Figures:
eiQuote message schema
EMIXBaseType message schema
The Figure below depicts eiQuote operation payload. They are the day-ahead electricity price information model communicated between the utility and facility.
eiQuote operation payload
The corresponding XSD (XML Schema Definition) for eiQuote operation payload is given
The corresponding XSD (XML Schema Definition) for eiQuote operation payload is given