ebix model measure introduction 1.0.d

ebIX Business information model for the exchange of metered data in the energy domain 1 Business information models for Measure Introduction Collect Validate Aggregate Status: Version: Revision: Date: ebIX For implementation 1.0 D April, 2009 April 2009 ebIX Business information model for the exchange of metered data in the energy domain 2 CONTENT 1. Introduction ..................................................................................................................................... 5 1.1. About this document ............................................................................................................... 5 1.2. The energy market ................................................................................................................... 5 1.3. About the ebIX Model ............................................................................................................. 5 1.4. Procedures ............................................................................................................................... 6 1.5. Participants in the project ........................................................................................................ 6 1.6. Comments to the ebIX model .................................................................................................. 6 1.7. References ............................................................................................................................... 7 1.8. Main changes since last version .............................................................................................. 7 2. Business Domain Model ................................................................................................................. 8 2.1. Objectives ................................................................................................................................ 8 2.2. Limitations / prerequisites ....................................................................................................... 8 2.3. Scope ....................................................................................................................................... 9 2.4. Actors, parties and roles .......................................................................................................... 9 2.5. Boundaries of the business domain Measure ........................................................................ 10 2.6. Remark for all Class Diagrams: ............................................................................................ 10 2.7. Comments to the attributes in Class Diagrams: .................................................................... 10 3. RSM annexes for mapping to technology of choice...................................................................... 10 3.1. Core Components .................................................................................................................. 10 3.2. Mapping to Edifact UNSM ................................................................................................... 11 3.3. Mapping to XML................................................................................................................... 11 3.4. Web services.......................................................................................................................... 11 4. Role model for Exchange of Metered Data ................................................................................... 12 5. Measure ......................................................................................................................................... 13 5.1. Use Case Diagram: Measure ................................................................................................. 13 5.1.1. UseCase Description: Measure: Collect + Validate + Aggregate local............................. 13 6. Collect ........................................................................................................................................... 15 6.1. UseCase Diagram: Collect .................................................................................................... 15 6.1.1. Limitations / prerequisites ................................................................................................. 15 6.1.2. UseCase Description: Collect ............................................................................................ 15 6.1.3. Detailed process description: Read register and quality control ....................................... 16 6.1.3.1. Activity diagram: Read register and quality control ..................................................... 16 6.2. BP: UseCase Exchange Collected Data ................................................................................ 17 6.2.1. Limitations / prerequisites ................................................................................................. 17 6.2.2. UseCase Description: Exchange Collected Data ............................................................... 17 6.2.3. Detailed process description: Exchange collected data ..................................................... 18 6.2.3.1. Activity diagram: Exchange collected data ................................................................... 18 6.2.3.2. Class diagram: E30, 23, reason, MDR, function (collected data from the Metered Data Collector to the Metered Data Responsible) ..................................................................................... 19 6.2.3.3. Class diagram: ERR for E30, 23, reason, MDR, 9 (processability error report on E30 for collected data) .............................................................................................................................. 21 6.3. BP: UseCase Request Collected Data ................................................................................... 23 6.3.1. Limitations / prerequisites ................................................................................................. 23 6.3.2. UseCase Description: BP Request Collected Data ............................................................ 23 6.3.3. Detailed process description: BP Request Collected Data ................................................ 24 6.3.3.1. Activity diagram: BP Request Collected Data .............................................................. 24 6.3.3.2. Class diagram: E72, 23, E23, MDR, function (Request for Collected Data from the Metered Data Responsible) ............................................................................................................... 25 6.3.3.3. Class diagram: ERR for E72, 23, E23, MDR, function (Processability Error Report Request for Collected Data) .............................................................................................................. 26 7. Validate ......................................................................................................................................... 27 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 3 7.1. UseCase: Validate ................................................................................................................. 27 7.1.1. Limitations / prerequisites ................................................................................................. 28 7.1.2. UseCase Description: Validate .......................................................................................... 28 7.1.3. Detailed process description: Validate .............................................................................. 29 7.1.3.1. Activity diagram: Validate ............................................................................................ 29 7.1.4. UseCase Description: Determine Stand ............................................................................ 30 7.1.5. Detailed process description: Determine Stand ................................................................. 30 7.1.5.1. Activity diagram: Determine Stand ............................................................................... 30 7.1.6. UseCase Description: Determine Period Volume ............................................................. 31 7.1.7. Detailed process description: Determine Period Volume .................................................. 31 7.1.7.1. Activity diagram: Determine Period Volume ................................................................ 31 7.1.8. UseCase Description: Apply Confidentiality Rules .......................................................... 32 7.1.9. Detailed process description: Apply Confidentiality Rules .............................................. 32 7.2. UseCase: Exchange Validated Data ...................................................................................... 33 7.2.1. Limitations / prerequisites ................................................................................................. 33 7.2.2. UseCase Description: Exchange Validated Data............................................................... 33 8. Aggregate ...................................................................................................................................... 35 8.1. Use Case Aggregate local...................................................................................................... 35 8.2. Limitations / prerequisites ..................................................................................................... 36 8.3. UseCase Description: Aggregate local .................................................................................. 36 9. Confidential Exchange of metered data ........................................................................................ 37 9.1. Introduction ........................................................................................................................... 37 9.2. UseCase: Confidential Exchange of metered data ................................................................ 37 9.3. Limitations / prerequisites ..................................................................................................... 37 9.4. UseCase Description: Confidential Exchange....................................................................... 37 9.4.1. Sequence diagram: BP Confidential Exchange for <<BusinessProcess Name>> ........... 38 10. Generic elements in the ebIX models ........................................................................................ 39 10.1. ebIX Methodology ............................................................................................................ 39 10.2. ebIX Common rules and recommendations ...................................................................... 39 10.3. Detailed process description: ebIX Acknowledgement and error handling ...................... 39 10.4. Detailed process description: ebIX Cancellation of business documents and processes .. 39 10.5. ebIX Core Components ..................................................................................................... 39 10.6. ebIX Code list .................................................................................................................... 39 10.7. ebIX Recommended identification schemes for the European energy industry ................ 39 10.8. ebIX Rules for Mapping to Edifact ................................................................................... 39 10.9. ebIX Rules for combining documents in sets .................................................................... 39 10.10. Overview of available models according to the ebIX domain model ............................... 39 10.11. XML version of code lists used in ebIX EMD models ..................................................... 40 10.12. XML version of UDT’s used in ebIX EMD models ......................................................... 40 10.13. XML version of QDT’s used in ebIX EMD models ......................................................... 40 10.14. XML version of ABIE’s used in ebIX EMD models ........................................................ 40 Appendix A Remarks regarding Class Diagrams for Measure ............................................................. 41 A. Direction .................................................................................................................................... 41 B. Update procedures ..................................................................................................................... 41 Appendix B Mapping to Edifact ........................................................................................................... 42 A. RSM Class diagram: CollectedData .................................................................................. 43 B. RSM Class diagram: ProcessabilityErrorReportCollectedData ........................................ 44 C. RSM Class diagram: RequestCollectedData ..................................................................... 45 D. RSM Class diagram: ProcessabilityErrorReportRequestCollectedData ........................... 46 Appendix C Mapping to XML, document schema’s............................................................................. 47 A. XML schema: CollectedData ............................................................................................ 47 B. XML schema: ProcessabilityErrorReportCollectedData................................................... 49 C. XML schema: RequestCollectedData ............................................................................... 52 D. XML schema: ProcessabilityErrorReportRequestCollectedData ...................................... 54 Appendix D Mapping to XML, Exchangeable Business Information schema’s................................... 57 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 4 E. XML schema: Exchangeable Business Information included in CollectedData ............... 57 F. XML schema: Exchangeable Business Information included in ProcessabilityErrorReportCollectedData .................................................................................. 60 G. XML schema: Exchangeable Business Information included in RequestCollectedData .. 63 H. XML schema: Exchangeable Business Information included in ProcessabilityErrorReportRequestCollectedData...................................................................... 65 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 5 1. INTRODUCTION 1.1. About this document This document is a generic introduction to all ebIX models for the exchange of metered data. The document contains a general introduction to all models for metered data plus the generic model elements that are not specific for a business process for the UseCases Collect, Validate and Aggregate. The UseCase Collect will be completely described in this model, since the collection of metered data is not specific for a business process. The processes are described using the ebIX Methodology which in turn is based on UML (Unified Modelling Language) and UMM (UN/CEFACT Modelling Methodology). Notice: ebIX (and UN/Cefact) are in the middle of the development process for Core Components. So the results of this development will undoubtedly affect the Class Diagrams as presented in this document. 1.2. The energy market Presently the energy market is going through a change process in most of the European countries. These changes include new legislation and a deregulation of the market. Earlier the participants in the market were in a monopoly situation. Today the participant companies are being split into different companies with different roles (in the rest of this document named as actors), such as Metering point administrator, Balance supplier, Balance responsible party, etc. Furthermore national markets turn more and more into a common European market. The change in the structure of the market and the new legislation described above has increased the need for electronic business tremendously (e.g. today the exchange of EDI documents in the energy market in Sweden is about 40 million EDI documents a year, is this sill correct?). This includes both transaction data, such as time series with production and consumption figures between the different parties, and master data. The exchange of information will concern a large amount of participants in many to many relationships. The number of actors which needs information exchange in the energy market may be in the range of a few hundred companies per country (Germany has for instance about 900 Grid operators). 1.3. About the ebIX Model The documents for the domain Measure describe a model for the exchange of metered data in the European energy market. The model will, after the modelling project has finished, be a part of a common ebIX model for the power industry in Europe. The model is important for having a common and agreed understanding on how the exchange of metered data in the energy market works as a basis for development of common methods for exchange of information. EbIX has set out to model the energy market using the UML based methodology proposed by UN/CEFACT. This paper presents a description of the exchange of metered data in the energy market domain expressed as Business UseCases and Business Objects. The document follows the process described in UN/CEFACT/TMWG/N090, UN/CEFACT Unified Modelling Methodology. This methodology involves the following 4 workflows: 1. Business Domain Modelling 2. e-Business Requirements 3. Analysis 4. Design ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 6 The deliverables for each workflow are expressed as UML artefacts together with a glossary of definitions and table of e-business requirements. In this methodology the Business Domain Model will be technology independent but the deliverables from Analysis and Design will increasingly interact with functionality provided by available technology. It must also be remembered that, in practice, these workflows are iterative and the model must be refined from "bottom up" as well as be driven "top down". 1.4. Procedures The modelling work is based on mainly national procedural requirements. The metered data needed for settlement from ETSO is also taken into account as requirements for this model. 1.5. Participants in the project This part of the ebIX Model for the Energy market is made in a project with the following participants: Members Name Rudolf Baumann1 Vlatka Cordes Hugo Dekeyser2 Filip Drijkoningen3 Adrian Fuchs4 Preben Høj Larsen Helmut Lebeau5 Oscar Ludwigs Lars Munter Walter Müller6 Christian Odgaard Lucy Sarkisian Kees Sparreboom Company Swiss Grid RWE UMIX UMIX Swissgrid Energinet.dk VDN SvK SvK TenneT Energinet.dk EBO ebIX Telephone +41585802120 +49 234 515-1638 Peter Bauhofer Frode Gjerde7 Juraj Horvat A&B Elis VSE +435125708830 Jörg Flügge John Buckley Ardo Ott Mare Tammisto Anne-Gaelle LeSaout SAP BGE Eesti Energia Eesti Energia EDF +3211266495 +41585802328 +45 76224247 +4930726148110 +4687397784 +4687397850 +31263731277 +45 76 224463 +31263731631 Mobile +41763844444 +49 162 2519714 +32477558003 +4915115741580 +46705397784 +46705397850 +45 23 338555 +31 6 22667911 E-mail rudolf.baumann@swissgrid.ch vlatka.cordes@rwe.com hugo.dekeyser@umix.info filip.drijkoningen@infrax.be adrian.fuchs@swissgrid.ch phq@energinet.dk helmut.lebeau@vdn-berlin.de oscar.ludwigs@svk.se lars.munter@svk.se w.muller@tennet.org cco@energinet.dk l.sarkisian@tennet.org kees.sparreboom@capgemini.com Observers +421(0) 55 610 29 51 +4962277-64558 +4369912572511 +4795783599 +421 (0) 915 932 285 +4916090823048 +372 511 7637 +372 511 8252 peter.bauhofer@aundb.at frode@elis.no horvat_juraj@vse.sk j.fluegge@sap.com jbuckley@bge.ie ardo.ott@energia.ee mare.tammisto@energia.ee anne-gaelle.lesaout@distribution.edf.fr 1.6. Comments to the ebIX model If you have comments or suggestions to the model please contact any member of the project group or directly to Kees Sparreboom, kees.sparreboom@capgemini.com . 1 Till November 2005 Till January 2007 3 From October 2006 4 From November 2005 5 Till January 2006 6 Till January 2008 7 In 2005 2 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 7 1.7. References  UN/CEFACT Unified Modelling Methodology -TMWG/N090, see http://webster.disa.org/cefact-groups/tmg/doc_bpwg.html  ebIX model for Structuring of the European Energy Market (incl. Customer Switching), version 1.0.- see www.ebix.org  The Electricity Market Role Model – ETSO, ebIX and EFET, see www.edi.etso-net.org 1.8. Main changes since last version Old New Clarification Date Version 1.0.D UML File name:/D:/ksparreb/Documents/ebIX/metered data/model/Migration EMD to UML2/transformatie Jan 200809/ebix06 incl MD & Settle.mdxml 1. 2. 3. 4. 5. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 8 2. BUSINESS DOMAIN MODEL The exchange of metered data is a part of the overall processes in the energy market. To give a brief introduction to where in the overall model the exchange processes belong, the introduction and the business domain UseCase for the energy market is shown below. Please notice that these processes are being discussed in several projects in the European power industry and might be changed in the future. In the various model documents the domain Measure from this Business Domain Model is broken down into individual processes. Structure Plan Structure Trade Plan Operate Trade <<include>> Operate <<include>> <<include>> <<include>> European Energy Market <<include>> <<include>> Measure Measure Settle Settle <<include>> Bill Bill 2.1. Objectives The vision of the project is to produce a model of the energy market. The work will be used to:  Provide a basis for facilitation and harmonisation in planning, trade, settlement and other processes important for the energy market.  Provide a basis for a common way of exchanging information in the energy market.  To make the models based on international accepted standards, so that the result can be understood and used by as many as possible.  To make the deregulated energy market understandable for the participating parties. 2.2. Limitations / prerequisites 1. In the model documents for Measure the exchange of metered data for various purposes is described. 2. A precondition for implementation of the “simple” solutions described in these models is that unique metering point ids are implemented8. If a unique metering point id not is implemented, other attributes must be added to the different documents exchanged on national bases (to assure the correctness of the local metering point).  Usage of the classes with a cardinality of “0..1” or “0..*” are dependent on national rules. 8 see ebIX document: Recommended Identification Schemes for the European Energy Industry (www.ebix.org ) ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 9 3. For the purposes of the EMD project meters have to be identified at least uniquely within one metering point. Identification of physical meters can for this purpose be based on EAN/GSAI (Global Serial Asset Identification). 2.3. Scope The Measure part of the overall model focuses on the exchange of metered data. Within ebIX the work group Customer Switching (CuS) is modelling the processes regarding the exchange of master data within the energy sector. The European Transmission System Operators have modelled within their organisation ETSO various processes where the TSO’s are directly involved. One of these processes being the imbalance settlement for which ebIX has modelled the exchange of metered data in cooperation with ETSO. The process of reconciliation is modelled by ebIX. Next to ETSO also UCTE is describing some processes in which information exchange between TSO’s is required. EFET has modelled some elements in the exchange between traders. 2.4. Actors, parties and roles In this document the term role originates from the ebIX-EFET-ETSO role model. In this model roles are mainly defined in terms of responsibility. The term party refers to the (legal) entity performing the role. A party may combine more than one role. The term actor will be reserved for UML and will be avoided in the ebIX methodology. Some examples: The traditional grid company (as a party) may perform the following roles:  Grid Access Provider  Metering Point Administrator  Metered Data Collector  Metered Data Responsible  Metered Data Aggregator local  Metering Administrator The energy supplier as (a party) may perform the following roles:  Balance Supplier  Balance Responsible o Trade o Consumption o Production For definitions of the different actors and roles, please see the ebIX-EFET-ETSO Role model, www.edi.etso-net.org or www.ebix.org The modelling of the exchange of metered data required the introduction of some new roles:  Metered Data Collector  Metered Data Responsible  Metered Data Aggregator (local/central)  Metering Administrator The definition of the reconciliation process required the introduction of the following new roles:  Reconciliation responsible  Reconciled accountable The model also required a change in the definition of some other roles:  Billing Agent  Market Operator ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 2.5. 10 Boundaries of the business domain Measure The domain Measure of the ebIX model intends to cover all exchange of metered data in the energy sector. In this document all modelling results with respect to the exchange of metered data are to be found. Other modelling results as published by ebIX are:  The maintenance and exchange of master data required in all processes (this part is modelled by ebIX CuS).  The reconciliation process and the exchange of the results of that process (as modelled by ebIX EMD).  The billing of the reconciled volumes (yet to be modelled by ebIX as a generic billing process). The descriptions given in this paragraph will be limited to the requirements for the exchange of metered data only. 2.6. Remark for all Class Diagrams: The Class Diagram follows the UN/Cefact Naming and Design Rules with respect to the relations and the use of cardinality. The naming of elements has still to be checked. Mapping to Edifact follows the ebIX Rules for Mapping. Where possible the product-ID is specified explicitly because:  The ebIX rule is to specify products explicitly even if there is in an instance only one product used;  ebIX intends to use generic re-usable elements (Core Components). In metered data the ebIX recommendation is to limit the cardinality between the Class BusinessDocumentData and the Class MeteringData to 1. 2.7. Comments to the attributes in Class Diagrams:  QuantityQuality: “estimated” is regarded as a higher quality (more precise) than “temporary” 3. RSM ANNEXES FOR MAPPING TO TECHNOLOGY OF CHOICE To all ebIX EMD documents an annex is attached containing the information required to map the Business Requirements for the information to be exchanged (as specified in the Class Diagrams) to the desired technology. Originally ebIX model documents provided only information for mapping to an Edifact UNSM (like UTILTS). Present documents also provide the mapping to XML. 3.1. Core Components The mapping of the Business Requirements Specification (BRS) for the information to be exchanged to the required technology as provided in the Requirements Specification Mapping (RSM) starts with the translation of the data into re-usable Core Components. The Core components used in the present version of the EMD model documents are of provisional nature, since the European energy sector is in the process of defining harmonised Core Components. At the moment the ABIE’s and QDT’s used in the RSM are merely the result of the clustering of the data as defined in the BRS-version. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 3.2. 11 Mapping to Edifact UNSM For the mapping to Edifact the UNSM’s for UTILTS and UTILMD from the UN/Cefact directory version 08.A are used. Rules for mapping to Edifact are to be found in the ebIX document “ebIX Rules for mapping to Edifact, version 0.1.-, d.d. July 2005”. 3.3. Mapping to XML The mapping to XML is done by generating XML schema’s directly from the UML-model. The creation of the XML schema’s follows the recommendations as published by UN/Cefact in the Naming and Design Rules version 2.0. ebIX EMD model documents contain the specification of the XML schema’s that are specific for the information as described in that particular model document. Generic schema’s (code lists used, Unqualified Data Types (UDT), Qualified Data Types (QDT) and Reusable Aggregate Business Information (ABIE) are published in separate documents. As consequence one will find in this document only the XML specification for the information exchanged in the processes regarding Collected Data plus for each document schema a schema that specifies the Exchangeable Business Information used in that document schema and therefore included in that document schema. Exchangeable Business Information specifies ABIE’s that are customised for the use in one particular document. 3.4. Web services ebIX wants the models to be prepared for implementation as web services. Therefore the clustering of the information in the RSM is slightly modified compared to the BRS version.   The header information to be used in the batch exchange as individual documents or as messages containing several documents is specifically split of the definition of the Core Business Data defined in the RSM Class Diagrams. For metered data ebIX assumes that web services will be clustered per responsible role. This implies that the attributes ReasonForTransaction, BusinessSector and Function are part of the Core Business Data. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 12 4. ROLE MODEL FOR EXCHANGE OF METERED DATA Several roles are involved in the exchange of metered data process area. Below is shown a class diagram where the main relations for the roles involved are shown. Balance Responsible Grid Access Provider Consumer Producer 1 1 1 May be financially responsible for Market operator Operates 1..* 1..* Balance Group 1 1..* 1 Provides access to Imbalance Settlement Responsible Controls financially 1..* Market Balance Area 1..* 1 Uses Is composed of Reconciliation Accountable 1 Party Connected to Grid 1 Is financially accountable for 1..* Aggregates within 1..* 1..* Local metering point Exchange Metering Point 1 Connects 2 1..* Metering Grid Area 1..* Controls financially 1..* 1 Metering Point Administrator Administrates 1..* Metering point 1..* 1 1 Processes metered data for Collects data from 1..* 0..* Register 1..* Administrates meter information for Role model section Metered Data Author ksparreb Creation date 6/26/08 4:52 PM Modification date 6/26/08 5:50 PM CD Description Section of the Harmonized Role Model relevant for Metered Data based on HRM Version 2008-01 Structure Codelist version QDT version Metered Data Aggregator central Metered Data Aggregator local 1 Metered Data Responsible 1..* Diagram name 1 1..* Balance Supplier 1 Reconciliation Responsible Aggregates within Supplies to Metered Data Collector 1 Administrates 1 Metered Data Aggregator 1 1 Meter Meter Administrator 1..* Operates and maintains 1 Meter Operator Class diagram – Metered data, Role model for Exchange Metered Data (Based on ebIX-EFET-ETSO version5.0, April 2008) For definitions of the different actors and roles, please see the ebIX-EFET-ETSO Role model, www.edi.etso-net.org or www.ebix.org ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 13 5. MEASURE The UseCase “Measure” is in this chapter elaborated into the following UseCase:  Collect  Validate  Aggregate 5.1. Use Case Diagram: Measure Measure Party connected to grid Metered data collector Collect Grid access provider Balance supplier Metered data responsible Validate Balance responsible party Transport capacity Responsible party Metered Data Aggregator, local Aggregate local Metered data aggregator, central Reconciliation Accountable Reconciliation Responsible UseCase diagram – Measure Comments to the diagram:  The UseCase “Measure ” will be further elaborated in the next chapters of this document.  The role Transport capacity responsible party used at the moment in the gas sector only. 5.1.1. UseCase Description: Measure: Collect + Validate + Aggregate local UseCase Name Traceability Identifier UseCase Description ebIX Measure (ebIX Business Domain) ebIX Energy Market, Measure This UseCase reflects the overall ebIX Business Domain Measure to be further detailed In the measure phase the actors exchange information (metered data) necessary for various purposes. This includes: April 2009 ebIX Business information model for the exchange of metered data in the energy domain Roles Performance Goals       Imbalance settlement Reconciliation Billing (yet to be modelled) Labelling (yet to be modelled) Determine switch stand Metered History (yet to be modelled) ????              Balance Responsible party Balance Supplier Grid Access Provider Metered Data Aggregator local Metered Data Aggregator central Imbalance settlement responsible Metered Data Collector Metered Data Responsible Party Connected to Grid Reconciliation Accountable Reconciliation Responsible Transport Capacity Responsible party The exchange process should be as efficient as possible and should allow finishing the business processes (such as settlement, reconciliation…) within the time limits of the (national) market rules Metered data should be exchanged between the actors, so that all needed information for the business processes (e.g. settlement) can be fulfilled. The exchanged metered data shall allow for quality control within the processes defined in the model. Correct data should be available for business processes in time    Preconditions       The participating actors know each other The actors have entered agreements (e.g. business agreements and interchange agreements) Unique local metering point ids have to be implemented before the current model can be implemented as proposed. If not implemented other attributes for identification of the local metering point have to be added on a national basis. The model is made for usage in the electricity and gas markets. There must be an open market with separated roles, such as balance suppliers, balance responsible parties, metered data collectors. Correct master data should be available for business processes in time Post conditions  Scenario none Alternative Scenario none Special Requirements none Extension Points none ebIX 14 The actors have successfully exchanged metered data and may start the processes based on these metered data. April 2009 ebIX Business information model for the exchange of metered data in the energy domain 15 6. COLLECT 6.1. UseCase Diagram: Collect Use Master Data Register (ebIX Domain.Measure.Use Master Data) 1 Collect Collect <<include>> extension points Collecting Exchange Collected Data Metered data collector <<extend>> (Collecting) Read register <<extend>> (Collecting) Control quality <<extend>> (Exchange Collected Data) BP Exchange Collected Data UseCase diagram – Collect Comments to the diagram:  none 6.1.1. Limitations / prerequisites This UseCase is part of the overall UseCase Measure as described in the document “Measure, Introduction”. Remark: no detailed description available for the UseCases:  Read Register  Control Quality 6.1.2. UseCase Description: Collect UseCase Name Traceability Identifier UseCase Description 1 Collect ebIX Energy Market, Measure, 1 Collect Meter reading and quality control on the data is executed by the metered data collector. Roles  Performance Goals No specific goals Preconditions Collector should know which register to read and have access to relevant master data Post conditions Collected data are available for exchange ebIX Metered data collector April 2009 ebIX Business information model for the exchange of metered data in the energy domain Scenario none Alternative Scenario none Special Requirements  none Extension Points   collection exchange collected data 16 6.1.3. Detailed process description: Read register and quality control 6.1.3.1. Activity diagram: Read register and quality control metered data collector collect metered data improve quality quality control not OK within limits prepare sending data ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 6.2. 17 BP: UseCase Exchange Collected Data package BP Exchange Collected Data [ BP Exchange Collected Data ] BP Exchange Collected Data <<BusinessTransaction>> BP Exchange Collected Data {AncillaryRole = MDR, DocumentType = E30} Metered Data Collector Metered Data Responsible Comments to the diagram:  none 6.2.1. Limitations / prerequisites This UseCase is part of the overall UseCase Collect within Measure. 6.2.2. UseCase Description: Exchange Collected Data UseCase Name Traceability Identifier UseCase Description Roles Performance Goals Exchange Collected Data ebIX Energy Market, Measure, 1 Collect, BP: Exchange Collected Data The meter readings are sent to the Metered Data Responsible  Metered data collector  Metered data responsible No specific goals Preconditions The collected data are available at the Metered Data Collector Post conditions The collected data are available at the Metered Data Responsible as well. Scenario none Alternative Scenario none Special Requirements  none Extension Points  none ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 18 6.2.3. Detailed process description: Exchange collected data 6.2.3.1. Activity diagram: Exchange collected data activity BP Exchange Collected Data [ BP Exchange Collected Data ] Metered Data Collector Metered Data Responsible prepare sending data {ACK required, ACK Timeout = "to be defined", Pattern = Notification} send collected data <<Transaction>> data : CollectedData receive collected data data : CollectedData Success process collected data correct sent data [yes] [no] {ACK required, ACK Timeout = "50", Pattern = Notification} OK send processability error report <<Transaction>> receive processability error report data store collected data data Failure ebIX Success April 2009 ebIX Business information model for the exchange of metered data in the energy domain 19 6.2.3.2. Class diagram: E30, 23, reason, MDR, function (collected data from the Metered Data Collector to the Metered Data Responsible) package BRS CollectedData [ BRS CollectedData ] E30, 23, reason, MDR, 9 1 BusinessDocument +marketDomain : ebIX 02B::QDT::MarketDomainCodeType = E02 +messageDateTime : ebIX 02B::QDT::DateTimeType +receiverID : ebIX 02B::QDT::PartyIdentifierType +requestForAcknowledgementOf Acceptance : ebIX 02B::QDT::Respon seTypeCodeType = AB +senderID : ebIX 02B::QDT::PartyIdentifierType +timeZone : ebIX 02B::QDT::TimeZoneType BusinessDocumentType 1 +type : ebIX 02B::QDT::BusinessDocumentTypeCodeType = E30 +businessSector : ebIX 02B::QDT::BusinessSectorCodeType = 23 +reasonForTransaction : ebIX 02B::QDT::ReasonForTransactionCodeType +ancillaryRole : ebIX 02B::QDT::RoleCodeType = MDR +function : ebIX 02B::QDT::BusinessDocumentFunctionCodeType 1 +identifier : ebIX 02B::QDT::BusinessDocumentIdentificationType BusinessDocumentData ... MeteringData 1 +meteringPointIdentifier : ebIX 02B::QDT::DomainIdentifierType +meterIdentifier : ebIX 02B::QDT::MeterIdentifierType +registerIdentifier : ebIX 02B::QDT::RegisterIdentifierType +observationPeriod : ebIX 02B::QDT::DateTimePeriodType [0..1] +resolution : ebIX 02B::QDT::ResolutionType [0..1] +registrationDateTime : ebIX 02B::QDT::DateTimeType {Used if cardinality Observation > 1} 1..* Observation +position : ebIX 02B::QDT::SequencePositionType +quantity : Data types::float [0..1] +quantityQuality : ebIX 02B::QDT::QuantityQualityType [0..1] If no quantity available, quantityquality = 46 ... Diagram name BRS CollectedData Author ksparreb Creation date 8/3/06 4:51 PM Modification date 10/15/08 11:56 AM <<enumeration>> BusinessDocumentFunctionCode (Codelist.CEFACT) 9{Dsc = "Initial"} 5{Dsc = "Update"} <<enumeration>> QuantityQualityCode (Codelist.CEFACT) 46{Dsc = "Does not exist"} ... ... CD Description Collected Data from Metered Data Collector to Metered Data Responsible Structure Codelist version draft version 0.2.D QDT version <<enumeration>> ReasonForTransactionCode (Codelist.ebIX) E03{Dsc = "Change of Balance Supplier"} E20{Dsc = "End of supply"} E21{Dsc = "Change of party Connected to Grid"} E65{Dsc = "Consumer move in"} E66{Dsc = "Consumer move out"} E77{Dsc = "End of Metering"} E60{Dsc = "Removal of Meter"} E67{Dsc = "Placement of Meter"} E01{Dsc = "Change of Party Connected to Grid"} E23{Dsc = "Periodic metering"} E75{Dsc = "Change of Metering Method"} ... Class diagram – E30 collected data from the Metered Data Collector ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 20 Comments to the attributes:  For time series the QuantityQuality may be used additionally to indicate a special quality of the data. For collected data this can only be the indication that data is missing. If data is missing, the quantity quality code 46 has to be used instead.  For some specific purposes the quantity in Class Observation may be defined as data type integer (based on national requirements).  Collected data have no sign (raw data; no direction) ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 21 6.2.3.3. Class diagram: ERR for E30, 23, reason, MDR, 9 (processability error report on E30 for collected data) package BRS Processability Error Report Collected Data [ BRS Processability Error Report Collected Data ] ERR for E30, 23, reason, MDR, function 1 BusinessDocument +marketDomain : ebIX 02B::QDT::MarketDomainCodeType = E02 +messageDateTime : ebIX 02B::QDT::DateTimeType +receiverID : ebIX 02B::QDT::PartyIdentifierType +requestForAcknowledgementOf Acceptance : ebIX 02B::QDT::Res ponseTypeCodeType = AB +senderID : ebIX 02B::QDT::PartyIdentifierType +timeZone : ebIX 02B::QDT::TimeZoneType BusinessDocumentType +type : ebIX 02B::QDT::BusinessDocumentTypeCodeType = ERR +businessSector : ebIX 02B::QDT::BusinessSectorCodeType = 23 +reasonForTransaction : ebIX 02B::QDT::ReasonForTransactionCo deType +ancillaryRole : ebIX 02B::QDT::RoleCodeType = MDR +function : ebIX 02B::QDT::BusinessDocumentFunctionCodeType = 9 +classDiagramVersion [0] 1 BusinessDocumentData +identifier : ebIX 02B::QDT::BusinessDocumentIdentificationType +status : ebIX 02B::QDT::TransactionResponseStatusCodeType = 4 1 1 Reference ToOriginalDocumentSet (Message) 0..1 +reference : ebIX 02B::QDT::ReferenceType +type : Codelist::ebIXCombined::BusinessDocumentTypeCode = E30 ReferenceToOriginalDocument (Transaction) 1 +reference : ebIX 02B::QDT::ReferenceToBusinessDocumentType +meteringPointIdentifier : ebIX 02B::QDT::DomainIdentifierType [0..1 ] +observationPeriod : ebIX 02B::QDT::DateTimePeriodType [0..1] 1..* OriginalDocumentError +reason : ebIX 02B::QDT::BusinessDocumentAcceptanceStatusCo deType Diagram name BRS Processability Error Report Collected Data Author ksparreb Creation date 2/21/05 10:54 AM Modification date 10/15/08 12:09 PM CD Description processability error report collected data for E Structure Codelist version draft version 0.2.D QDT version <<enumeration>> BusinessDocumentAcceptanceStatusCode (Codelist.ebIX) E10{Dsc = "Metering Point not identifiable"} E55{Dsc = "Unauthorised Metered Data Responsible"} E09{Dsc = "Installation not identifiable"} E19{Dsc = "Meter stand not within limits"} E50{Dsc = "Invalid period"} E51{Dsc = "Invalid number of decimals"} E61{Dsc = "Meter not identifiable"} E62{Dsc = "Register not identifiable"} E85{Dsc = "Unauthorized Metering Administrator"} ... <<enumeration>> ReasonForTransactionCode (Codelist.ebIX) E03{Dsc = "Change of Balance Supplier"} E20{Dsc = "End of supply"} E21{Dsc = "Change of party Connected to Grid"} E65{Dsc = "Consumer move in"} E66{Dsc = "Consumer move out"} E77{Dsc = "End of Metering"} E60{Dsc = "Removal of Meter"} E67{Dsc = "Placement of Meter"} E01{Dsc = "Change of Party Connected to Grid"} E23{Dsc = "Periodic metering"} E75{Dsc = "Change of Metering Method"} ... Class diagram – ERR processability error report on E30 for collected data ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 22 Comments to the attributes:  The reference to the original business document maybe limited to a reference to a unique ID if available; if not references to metering point and/or observation period may replace or add to the not unique ID. If a unique transaction ID is used to identify business documents, the reference to the business document set is not required.  Likely additional error codes, but yet to be issued by ebIX: o Invalid observation period o Number of observations does not fit observation period/resolution o Invalid resolution ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 6.3. 23 BP: UseCase Request Collected Data package BP Request Collected Data [ BP Request Collected Data ] BP Request Collected Data Request Collected Data Metered Data Responsible {AncillaryRole = MDR, DocumentType = E72} Metered Data Collector <<include>> BP Exchange Collected Data {AncillaryRole = MDR, DocumentType = E30} Comments to the diagram:  none 6.3.1. Limitations / prerequisites This UseCase is part of the overall UseCase Collect within Measure. 6.3.2. UseCase Description: BP Request Collected Data UseCase Name Traceability Identifier UseCase Description Performance Goals BP Request Collected Data ebIX Energy Market, Measure, 1 Collect, BP: Request Collected Data The Metered Data Responsible requests the Metered Data Collector for Collected Data  Metered data collector  Metered data responsible No specific goals Preconditions The Metered Data Responsible needs Collected Data Post conditions The Metered Data Collector has either rejected the request or made the requested Collected Data available to the Metered Data Responsible. Scenario none Alternative Scenario none Special Requirements  none Extension Points  none Roles ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 24 6.3.3. Detailed process description: BP Request Collected Data 6.3.3.1. Activity diagram: BP Request Collected Data activity BP Request Collected Data [ BP Request Collected Data ] Metered Data Responsible Metered Data Collector Prepare Request {ACK required, ACK Timeout = "to be defined", Pattern = Request-Response} Send Request <<Transaction>> data : RequestCollectedData data : RequestCollectedData Receive Request correct request Process request [no] {ACK required, ACK Timeout = "to be defined", Pattern = Notification} send processability error report <<Transaction>> [yes] data [retry] receive processability error report data Failure [no retry] Failure receive requested data : BP Exchange Collected Data Success Success ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 25 6.3.3.2. Class diagram: E72, 23, E23, MDR, function (Request for Collected Data from the Metered Data Responsible) package BRS Request Collected Data [ BRS Request Collected Data ] E72, 23, reason, Z05, 9 1 BusinessDocument +marketDomain : ebIX 02B::QDT::MarketDomainCodeType = E02 +messageDateTime : ebIX 02B::QDT::DateTimeType +receiverID : ebIX 02B::QDT::PartyIdentifierType +requestForAcknowledgementOf Acceptance : ebIX 02B::QDT::Res ponseTypeCodeType = AB +senderID : ebIX 02B::QDT::PartyIdentifierType +timeZone : ebIX 02B::QDT::TimeZoneType BusinessDocumentType 1 +type : ebIX 02B::QDT::BusinessDocumentTypeCodeType = E72 +businessSector : ebIX 02B::QDT::BusinessSectorCodeType = 23 +reasonForTransaction : ebIX 02B::QDT::ReasonForTransactionC odeType +ancillaryRole : ebIX 02B::QDT::RoleCodeType = Z05 +function : ebIX 02B::QDT::BusinessDocumentFunctionCodeType = 9 +classDiagramVersion [0] BusinessDocumentData 1 +identifier : ebIX 02B::QDT::BusinessDocumentIdentificationType ... 0..* Diagram name BRS Request Collected Data Author ksparreb Creation date 2/18/08 5:28 PM Modification date 9/17/08 11:00 AM CD Description Request for Collected Data from the Metered Data Responsible Structure Edifact, UTILTS 02.B MeteringData +meteringPointIdentifier : ebIX 02B::QDT::DomainIdentifierType +meterIdentifier : ebIX 02B::QDT::MeterIdentifierType [0..*] +registerIdentifier : ebIX 02B::QDT::RegisterIdentifierType [0..*] +observationPeriod : ebIX 02B::QDT::DateTimePeriodType [0..1] ... <<enumeration>> ReasonForTransactionCode (CodeList ebIX) Codelist version draft version 0.2.D QDT version QDT 02, version 0.1.F E03{Dsc = "Change of Balance Supplier"} E20{Dsc = "End of supply"} E21{Dsc = "Change of party Connected to Grid"} E65{Dsc = "Consumer move in"} E66{Dsc = "Consumer move out"} E77{Dsc = "End of Metering"} E60{Dsc = "Removal of Meter"} E67{Dsc = "Placement of Meter"} E01{Dsc = "Change of Party Connected to Grid"} E23{Dsc = "Periodic metering"} E75{Dsc = "Change of Metering Method"} ... ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 26 6.3.3.3. Class diagram: ERR for E72, 23, E23, MDR, function (Processability Error Report Request for Collected Data) package BRS ProcessabilityErrorReportRequestCollectedData [ BRS ProcessabilityErrorReportRequestCollectedData ] ERR for E72, 23, reason, MDR, function 1 BusinessDocument +marketDomain : ebIX 02B::QDT::MarketDomainCodeType = E02 +messageDateTime : ebIX 02B::QDT::DateTimeType +receiverID : ebIX 02B::QDT::PartyIdentifierType +requestForAcknowledgementOf Acceptance : ebIX 02B::QDT::Respon seTypeCodeType = AB +senderID : ebIX 02B::QDT::PartyIdentifierType +timeZone : ebIX 02B::QDT::TimeZoneType BusinessDocumentType +type : ebIX 02B::QDT::BusinessDocumentTypeCodeType = ERR +businessSector : ebIX 02B::QDT::BusinessSectorCodeType = 23 +reasonForTransaction : ebIX 02B::QDT::ReasonForTransactionCodeType +ancillaryRole : ebIX 02B::QDT::RoleCodeType = MDR +function : ebIX 02B::QDT::BusinessDocumentFunctionCodeType = 9 +classDiagramVersion [0] 1 BusinessDocumentData +identifier : ebIX 02B::QDT::BusinessDocumentIdentificationType +status : ebIX 02B::QDT::TransactionResponseStatusCodeType = 41 1 Reference ToOriginalDocumentSet (Message) 0..1 +reference : ebIX 02B::QDT::ReferenceType +type : Codelist::ebIXCombined::BusinessDocumentTypeCode = E72 ReferenceToOriginalDocument (Transaction) 1 +reference : ebIX 02B::QDT::ReferenceToBusinessDocumentType +meteringPointIdentifier : ebIX 02B::QDT::DomainIdentifierType [0..1] +observationPeriod : ebIX 02B::QDT::DateTimePeriodType [0..1] 1..* OriginalDocumentError +reason : ebIX 02B::QDT::BusinessDocumentAcceptanceStatusCodeType Diagram name BRS ProcessabilityErrorReportRequestCollectedData Author ksparreb Creation date 10/16/08 10:58 AM Modification date 10/16/08 11:17 AM CD Description processability error report request collected data for E Structure Codelist version draft version 0.2.D QDT version <<enumeration>> BusinessDocumentAcceptanceStatusCode (Codelist.ebIX) E10{Dsc = "Metering Point not identifiable"} E55{Dsc = "Unauthorised Metered Data Responsible"} E09{Dsc = "Installation not identifiable"} E19{Dsc = "Meter stand not within limits"} E50{Dsc = "Invalid period"} E51{Dsc = "Invalid number of decimals"} E61{Dsc = "Meter not identifiable"} E62{Dsc = "Register not identifiable"} ... <<enumeration>> ReasonForTransactionCode (Codelist.ebIX) E03{Dsc = "Change of Balance Supplier"} E20{Dsc = "End of supply"} E21{Dsc = "Change of party Connected to Grid"} E65{Dsc = "Consumer move in"} E66{Dsc = "Consumer move out"} E77{Dsc = "End of Metering"} E60{Dsc = "Removal of Meter"} E67{Dsc = "Placement of Meter"} E01{Dsc = "Change of Party Connected to Grid"} E23{Dsc = "Periodic metering"} E75{Dsc = "Change of Metering Method"} ... ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 27 7. VALIDATE 7.1. UseCase: Validate package 2 Validate [ Validate ] 2 Validate Complete for missing collected data Use history or control readings <<include>> Use Master Data Metering Point (ebIX Domain.Measure.Use Master Data) <<include>> Metered Data Responsible Determine Stand <<extend>> <<include>> Validate (stand) extension points stand volume (volume) extension points billing imbalance settlement reconciliation labelling Apply Confidentiality Rules Use Master Data Register (ebIX Domain.Measure.Use Master Data) Determine Period Volume <<extend>> <<include>> <<extend>> (labelling) BP Exchange for Labelling (ebIX Domain.Measure.2 Validate.Exchange Validated Data.BP Exchange for Labelling) <<extend>> (imbalance settlement, reconciliation, billing) extension points confidentiality rules no confidentiality rules <<extend>> (confidentiality rules) Exchange Validated Data, confidential (ebIX Domain.Measure.2 Validate.Exchange Validated Data, confidential) <<extend>> (no confidentiality rules) Exchange Validated Data (ebIX Domain.Measure.2 Validate.Exchange Validated Data) UseCase diagram – Validate ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 28 7.1.1. Limitations / prerequisites This UseCase is part of the overall UseCase Measure. Remark: no detailed description available yet for the UseCases:  Complete for missing collected data  Use history or control readings 7.1.2. UseCase Description: Validate UseCase Name Validate Traceability Identifier ebIX Energy Market, Measure, 2 Validate UseCase Description The Metered Data Responsible transforms the collected data as received into validated data. In this process he makes use of the available history of metered data and in case of determination of volumes also of master data (for Physical Connection Point, Metering Point and register/meter). In case of missing collected data the Metered Data Responsible can use the history of metered data or control readings in order to complete the data. Roles  Metered Data Responsible Performance Goals  Preconditions      The Metered Data Responsible shall start the determination of the stand or the determination of the period volume. Quality of the metered data shall meet the standards set by national market rules The Metered Data Responsible has received the collected data in time; Relevant master data (Physical Connection Point, Metering Point and register/meter) are available; History of metered data is available; National validation rules are available. Post conditions    the application of confidentiality rules to the validated data can start in time, the determination of the switch stand can start in time the exchange of labelling data in time Scenario none Alternative Scenario none Special Requirements none Extension Points   ebIX stand: determine validated stand volume: determine validated period volume April 2009 ebIX Business information model for the exchange of metered data in the energy domain 29 7.1.3. Detailed process description: Validate 7.1.3.1. Activity diagram: Validate Metered Data Responsible Retrieve Collected Data Evaluate data quality OK not OK Use history or control readings Determine Stand volume needed Determine Period Volume no volume needed Comments to the diagram (process): None ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 30 7.1.4. UseCase Description: Determine Stand UseCase Name Validate Traceability Identifier ebIX Energy Market, Measure, Validate UseCase Description The Metered Data Responsible transforms the collected stand as received into a validated stand. In this process he may use the available history of metered data. In case of missing collected data the Metered Data Responsible can use the history of metered data or control readings in order to complete the data. Roles  Metered Data Responsible Performance Goals       The Metered Data Responsible shall start the routing of the validated stands within the time limits provided by national market rules Updates and adjustments in the validated stands can be exchanged within the time provided by national market rules Quality of the metered data shall meet the standards set by national market rules The Metered Data Responsible has received the collected data in time; Relevant master data (metering point and register/meter) are available; History of metered data is available National validation rules are available Post conditions    the application of confidentiality rules to the validated data can start in time, the determination of the switch stand can start in time the exchange of labelling data in time Scenario none Alternative Scenario none Special Requirements none  Preconditions Extension Points 7.1.5. Detailed process description: Determine Stand 7.1.5.1. Activity diagram: Determine Stand ebIX assumes that the process of determine stand is modelled elsewhere (nationally or within the company systems). Comments to the diagram (process): None ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 31 7.1.6. UseCase Description: Determine Period Volume UseCase Name Validate Traceability Identifier ebIX Energy Market, Measure, Validate UseCase Description The Metered Data Responsible transforms the collected data as received into validated data. In this process he makes use of the available history of metered data and also of master data (for Physical Connection Point, Metering Point and register/meter). In case of missing collected data the Metered Data Responsible may use the history of metered data or control readings in order to complete the data. Roles  Metered Data Responsible Performance Goals    The Metered Data Responsible shall start the application of confidentiality rules or the exchange of labelling data within the time limits provided by national market rules Updates and adjustments in the validated data can be exchanged within the time provided by national market rules Quality of the metered data shall meet the standards set by national market rules The Metered Data Responsible has received the collected data in time; Relevant master data (Physical Connection Point, Metering Point and register/meter) are available; History of metered data is available National validation rules are available Post conditions   the application of confidentiality rules to the validated data can start in time, the exchange of labelling data in time Scenario none Alternative Scenario none Special Requirements none Extension Points      Preconditions    imbalance settlement: validation for imbalance settlement reconciliation: validation for reconciliation billing: validation for billing labelling: validation for labelling (not modelled yet) 7.1.7. Detailed process description: Determine Period Volume 7.1.7.1. Activity diagram: Determine Period Volume ebIX assumes that the process of determine stand is modelled elsewhere (nationally or within the company systems). Comments to the diagram (process): None ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 32 7.1.8. UseCase Description: Apply Confidentiality Rules UseCase Name Traceability Identifier UseCase Description Route Validated Metered Data ebIX Energy Market, Measure, Validate The Metered Data Responsible routes the validated metered data given the national confidentiality rules Roles  Metered Data Responsible Performance Goals Preconditions    The Metered Data Responsible shall conform to national confidentiality rules. Confidentiality rules are available Validated metered data are available Post conditions  The exchange of validated metered data can start Scenario none Alternative Scenario none Special Requirements none Extension Points   Confidentiality rules: validated metered data shall be exchanged according to these rules No confidentiality rules: no limitations for the exchange of metered data to the balance responsible and balance supplier 7.1.9. Detailed process description: Apply Confidentiality Rules No detailed description available. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 7.2. 33 UseCase: Exchange Validated Data Exchange Validated Data Exchange Validated Data extension points Billing Imbalance Settlement Metered History (not yet available) Reconciliation Labelling (not yet available) Metered Data Responsible <<extend>> (Imbalance Settlement) BP Exchange Validated Data for Imbalance Settlement <<extend>> (Reconciliation) <<extend>> (Billing) BP Exchange Validated Data for Reconciliation BP Exchange Validated Data for Billing UseCase diagram – Exchange Validated Data 7.2.1. Limitations / prerequisites This UseCase is part of the UseCase Validate within the overall UseCase Measure. For the detailed description of the UseCases “Exchange for <<BusinessProcess Name>>” see the separate models per business process (www.ebix.org ) Remark:  Detailed description for the UseCase Exchange Validated Data for Imbalance Settlement: see separate model document;  Detailed description for the UseCase Exchange Validated Data for Reconciliation: see separate model document;  Detailed description for the UseCase Exchange Validated Data for billing: see separate model document;  No detailed description available (yet) for the UseCases: o Exchange Validated Data for metered history o Exchange Validated Data for labelling 7.2.2. UseCase Description: Exchange Validated Data UseCase Name Traceability Identifier UseCase Description Exchange Validated Data ebIX Energy Market, Measure, 2 Validate The Metered Data Responsible exchanges validated metered data for the various specified purposes Roles  Metered Data Responsible Performance Goals  The Metered Data Responsible shall complete the exchange of the validated metered data in time Preconditions  No confidentiality rules to be applied Post conditions  The exchange processes can start. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain Scenario none Alternative Scenario Exchange validated metered data with confidentiality rules. This alternative is to be used in Belgium and France. Special Requirements none Extension Points      ebIX 34 Imbalance settlement: exchange validated metered data to be used in imbalance settlement including the establishment of imbalance Reconciliation: exchange validated metered data to be used in reconciliation Billing: exchange validated metered data to be used for billing Metered History: exchange of historic validated metered data on request (not yet modelled) Labelling: exchange of validated metered data for labelling (not yet modelled) April 2009 ebIX Business information model for the exchange of metered data in the energy domain 35 8. AGGREGATE 8.1. Use Case Aggregate local Aggregate local Aggregate local (ebIX Domain.Measure) Metered Data Aggregator, local extension points Imbalance Settlement Reconciliation Use Master Data Metering Point (ebIX Domain.Measure.Use Master Data) <<include>> <<include>> Use Master Data Metering Grid area (ebIX Domain.Measure.Use Master Data) <<extend>> (Imbalance Settlement) Aggregate for Imbalance Settlement <<extend>> (Reconciliation) Aggregate for Reconciliation UseCase diagram – Aggregate local ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 36 8.2. Limitations / prerequisites This UseCase is part of the overall UseCase Measure. For the detailed description of the UseCases “Exchange for <<BusinessProcess Name>>” see the separate models per business process (www.ebix.org ) The overall UseCase Aggregate is split into Aggregate central and Aggregate local. The central aggregation is defined by ETSO. Remark:  Detailed description for the UseCase Aggregate for Imbalance Settlement: see separate model document;  Detailed description for the UseCase Aggregate for Reconciliation: see separate model document;  Detailed description for the UseCase Aggregate for Billing: see separate model document; 8.3. UseCase Description: Aggregate local UseCase Name Traceability Identifier UseCase Description Aggregate local ebIX Energy Market, Measure, 3 Aggregate, Aggregate local The Metered Data Aggregator local aggregates the validated data for the required purpose: settlement or reconciliation. The aggregation requirements may be influenced by national rules. In this process the Metered Data Aggregator makes use of master data (for metering point and metering grid area). Roles  Metered Data Aggregator local Performance Goals  The Metered Data Aggregator local aggregates data for respective purposes according to the aggregation criteria as required by national rules. Rules for precision and rounding are nationally defined. The quality indication for the aggregated data shall correspond to lowest quality for data used in the aggregation. Aggregation shall meet the standards set by national market rules    Preconditions   The Metered Data Aggregator local has received the validated data in time; Relevant master data (metering point and metering grid area) are available; Post conditions  The activities specified in the included external UseCases may start Scenario none Alternative Scenario none Special Requirements none Extension Points   ebIX Imbalance settlement: aggregate validated metered data to be used in imbalance settlement including the establishment of imbalance Reconciliation: aggregate validated metered data to be used in reconciliation April 2009 ebIX Business information model for the exchange of metered data in the energy domain 37 9. CONFIDENTIAL EXCHANGE OF METERED DATA 9.1. Introduction During the development of the ebIX Business information models for the exchange of metered data in the energy domain the work group responsible for this development, was informed that there might be a difference in confidentiality requirements in European countries. The present models reflect the requirements as identified for the countries represented in the ebIX work group. Nevertheless the work group has decided to open the model for alternative confidentiality requirements. This paragraph reflects this opening. Concrete modelling however is only possible with specific requirements. In order to come to a more generic solution for confidentiality issues, an update for the ebIX-EFETETSO role model has been proposed by the EMVR work group in May 2008. This proposal is being discussed within the ebIX-EFET-ETSO Harmonization Group at the moment. Further elaboration of this paragraph depends on the outcome of this discussion or on specific requests to be made by other countries joining the ebIX organization. 9.2. UseCase: Confidential Exchange of metered data Confidential Exchange Confidential Exchange Metered data responsible extension points Billing Imbalance Settlement Metered History (?) Reconciliation Labelling (?) <<extend>> (Imbalance Settlement) <<extend>> (Billing) BP Confidential Exchange for Billing <<extend>> (Reconciliation) BP Confidential Exchange for Imbalance Settlement BP Confidential Exchange for Reconciliation UseCase diagram – Confidential Exchange 9.3. Limitations / prerequisites This UseCase is part of the overall UseCase Measure. 9.4. UseCase Description: Confidential Exchange UseCase Name Traceability Identifier UseCase Description Exchange Validated Metered Data ebIX Energy Market, Measure, 2 Validate The Metered Data Responsible exchanges validated metered data for the various specified purposes Roles  Performance Goals Appendix A The Metered Data Responsible shall complete the exchange of the validated metered data in time Appendix B  Confidentiality rules to be applied Preconditions ebIX Metered Data Responsible April 2009 ebIX Business information model for the exchange of metered data in the energy domain Post conditions  Scenario none Alternative Scenario Exchange validated metered data without confidentiality rules. This alternative is to be used in other countries than Belgium and France. Special Requirements none Extension Points      38 The exchange processes can start. Imbalance settlement: exchange validated metered data to be used in imbalance settlement including the establishment of imbalance Reconciliation: exchange validated metered data to be used in reconciliation Billing: exchange validated metered data to be used for billing (not yet modelled) Metered History: exchange of historic validated metered data on request (not yet modelled) Labelling: exchange of validated metered data for labelling (not yet modelled) 9.4.1. Sequence diagram: BP Confidential Exchange for <<BusinessProcess Name>> From here model elements have yet to be developed depending on the outcome of the update of the role model because of new confidentiality requirements or because of requirements from new ebIX member countries. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 39 10. GENERIC ELEMENTS IN THE EBIX MODELS The modelling is based on the ebIX Methodology and makes use of the ebIX common rules and recommendations (see www.ebix.org ). 10.1. ebIX Methodology version 1.0.- April 2004 (see ebIX website). Some elements from the ebIX Methodology are additionally mentioned in Annex A to this model document. 10.2. ebIX Common rules and recommendations ebIX has published an approved version of the common rules and recommendations version 1.0.B, 2005-03-21 (see ebIX website) 10.3. Detailed process description: ebIX Acknowledgement and error handling This process is described by ebIX ETC in Recommendations for acknowledgement and error handling version 1.0.- (status approved document, to be found on the ebIX website). 10.4. Detailed process description: ebIX Cancellation of business documents and processes This process is described by ebIX ETC in Recommendations for Cancellation of business documents and processes version 0.9 (status Request for Comment, to be found on the ebIX website). 10.5. ebIX Core Components ebIX has published a draft version for Core Components version 0.1.A, 2005-03-05 (see ebIX website). This version is not used in this model. In this model a draft version for Qualified Data Types is used. This document is published as annex to this model, but has no ebIX status yet. These QDT’s include the mapping to Edifact version 02.B. 10.6. ebIX Code list ebIX has published a list of the codes used in ebIX models (and MIG’s) (see ebIX website). 10.7. ebIX Recommended identification schemes for the European energy industry ebIX has published version 1.1.B of this document 2005-06-03. 10.8. ebIX Rules for Mapping to Edifact ebIX has published a draft version of these rules. This version a working document. 10.9. ebIX Rules for combining documents in sets ebIX has not published a version of this document yet. The version used in this document is a working document and is published as annex to this document. 10.10. Overview of available models according to the ebIX domain model ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 40 ebIX has not published a version of this document yet. The version used in this document is a working document and is published as annex to this document. 10.11. XML version of code lists used in ebIX EMD models ebIX has not published an XML version of code lists yet. The version used in this document is based on an older version of the ebIX code lists. The XML version of code lists used in ebIX EMD models is a working document and is published as annex to this document. 10.12. XML version of UDT’s used in ebIX EMD models ebIX has not published a version of this document yet. The version used in this document is a working document and is published as annex to this document. 10.13. XML version of QDT’s used in ebIX EMD models ebIX has not published a version of this document yet. The version used in this document is a working document and is published as annex to this document. 10.14. XML version of ABIE’s used in ebIX EMD models ebIX has not published a version of this document yet. The version used in this document is a working document and is published as annex to this document. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 41 Appendix A REMARKS REGARDING CLASS DIAGRAMS FOR MEASURE A.   Direction ebIX models provide the opportunity to specify the directions explicitly: o for exchange metering points by specifying the in- and/or out-area; o for local metering points by specifying the type of metering point (production or consumption) o at least one attribute has to be specified (either out area or in area) In case the direction is only specified implicitly, the convention for signs used to specify the direction (also for combined metering point type): o For metering grid area’s: the direction is always defined relative to the specified (own) metering grid area  a flow out of the own metering grid area is indicated as – (minus) according to ETSOebIX convention and as 1 according the OBIS-convention (Austria, Germany and Switzerland according to IEC-standard)  a flow into the own metering grid area is indicated as + (plus) according to ETSOebIX convention and as 2 according the OBIS-convention (Austria, Germany and Switzerland according to IEC-standard) B. Update procedures Update procedures may differ nationally. Below you find the overview over the update procedures that are used per country. Country AT Update procedure update per business document (time series) BE update per business document (time series) CH update per business document (time series) DE update per business document (time series) DK update per business document (time series) NL update per business document (time series) NO update per business document (time series) SE update per business document (time series) ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 42 Appendix B MAPPING TO EDIFACT Mapping to Edifact is based on the UTILTS version 2008.A. The mapping as shown in this appendix will be reviewed in light of the specification of the definition of Core Components with a split between payload and header information. April 2009. ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 43 A. RSM Class diagram: CollectedData package RSM CollectedData [ RSM CollectedData ] <<QDT>> Type : BusinessDocumentTypeCodeType E30, 23, reason, MDR, 9 codeSchemeResponsibleAgency = 260 content = E30 <<QDT>> MarketDomain : MarketDomainCodeType <<based on>> <<InfEnv>> CollectedData +DataSet codeSchemeResponsibleAgency = 260 content = E02 <<ExchangeableBusinessInformation>> Identification {based on = Identification} 1 <<QDT>> RequestForAcknowledgementOfAcceptance : ResponseTypeCodeType +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} +MarketDomain : ebIX 02::QDT::MarketDomainCodeType [1]{SG = "0"} +MessageDateTime : ebIX 02::QDT::DateTimeType [1]{Qualifier = "DTM-C507.2005=137", SG = "0"} +ReceiverID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MR", SG = "2"} +RequestForAcknowledgementOf Acceptance : ebIX 02::QDT::ResponseTypeCodeType [1]{SG = "0"} +SenderID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MS", SG = "2"} +TimeZone : ebIX 02::QDT::TimeZoneType [0..1]{SG = "0"} content = AB <<QDT>> AncillaryRole : RoleCodeType content = MDR <<QDT>> ReasonForTransaction : ReasonForTransactionCodeType codeSchemeResponsibleAgency = 260 content = E03, E20, E21, E65, E66, E77, E60, E67, E01, E23, E75 <<QDT>> BusinessSector : BusinessSectorCodeType content = 23 <<QDT>> Function : BusinessDocumentFunctionCodeType content = 9, 5 +CollectedData 1..* <<ExchangeableBusinessInformation>> TimeSeries <<ExchangeableBusinessInformation>> Domain +MeteringPoint {based on = TimeSeries} +Identification : ebIX 02::QDT::BusinessDocumentIdentificationType [1]{SG = "5"} +AncillaryRole : ebIX 02::QDT::RoleCodeType [1]{SG = "2"} +ReasonForTransaction : ebIX 02::QDT::ReasonForTransactionCodeType [1]{SG = "5"} +BusinessSector : ebIX 02::QDT::BusinessSectorCodeType [1]{SG = "0"} +Function : ebIX 02::QDT::BusinessDocumentFunctionCodeType [1]{SG = "0"} +ObservationPeriod : ebIX 02::QDT::DateTimePeriodType [0..1]{Qualifier = "DTM-C507.2005=324", SG = "5"} +Resolution : ebIX 02::QDT::ResolutionType [1]{SG = "5"} +RegistrationDateTime : ebIX 02::QDT::DateTimeType [1]{Qualifier = "DTM-2005=597", SG = "5"} 1 {based on = Domain} +Identification : ebIX 02::QDT::DomainIdentifierType{SG = "5"} +Register <<ExchangeableBusinessInformation>> Installation 1 {based on = Installation} {Used if cardinality Observation > 1} +MeterIdentification : ebIX 02::QDT::MeterIdentifierType [1]{SG = "8"} +RegisterIdentification : ebIX 02::QDT::RegisterIdentifierType [1]{SG = "8"} +Reading 1..* <<ExchangeableBusinessInformation>> VolumeObservation {based on = VolumeObservation} <<QDT>> QuantityQuality : QuantityQualityType content = 46 +Position : ebIX 02::QDT::SequencePositionType [1]{SG = "8"} +Quantity : Data types::float [0..1]{Data = "QTY-C186.6060", Qualifier = "QTY-C186.6063=136", SG = "11"} +QuantityQuality : ebIX 02::QDT::QuantityQualityType [0..1] = QuantityQuality{readOnly,SG = "11"} {Used if cardinality Quantity=0} ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 44 B. RSM Class diagram: ProcessabilityErrorReportCollectedData package RSM Processability Error Report Collected Data [ RSM ProcessabilityErrorReportCollectedData ] <<QDT>> Type : BusinessDocumentTypeCodeType ERR for E30, 23, reason, MDR, function codeSchemeResponsibleAgency = 260 content = ERR <<based on>> <<InfEnv>> ProcessabilityErrorReportCollectedData 1 <<QDT>> MarketDomain : MarketDomainCodeType <<ExchangeableBusinessInformation>> Identification +DataSet codeSchemeResponsibleAgency = 260 content = E02 +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} +MarketDomain : ebIX 02::QDT::MarketDomainCodeType [1]{SG = "0"} +MessageDateTime : ebIX 02::QDT::DateTimeType [1]{Qualifier = "DTM-C507.2005=137", SG = "0"} +ReceiverID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MR", SG = "2"} +RequestForAcknowledgementOf Acceptance : ebIX 02::QDT::ResponseTypeCodeType [1]{SG = "0"} +SenderID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MS", SG = "2"} +TimeZone : ebIX 02::QDT::TimeZoneType [0..1]{SG = "0"} <<QDT>> RequestForAcknowledgementOfAcceptance : ResponseTypeCodeType content = AB <<comment>> <<QDT>> ErrorCode : BusinessDocumentAcceptanceStatusCodeType Problem: we should not use one ABIE several times in one Class Diagram! Naming does not help here. Only customising outside UML. Is that what we want? codeSchemeResponsibleAgency = 260 content = E10, E09, E19, E50, E51, E55, E61, E62, E85 +Response 1 <<ExchangeableBusinessInformation>> Status +Status : ebIX 02::QDT::TransactionResponseStatusCodeType [1]{SG = "5"} <<ExchangeableBusinessInformation>> ErrorDescription +OriginalDocument 1..* +ErrorCode : ebIX 02::QDT::BusinessDocumentAcceptanceStatusCodeType [1]{SG = "5"} +ReferenceTo OriginalDataSet 0..1 <<ExchangeableBusinessInformation>> Identification1 +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} <<QDT>> Status : TransactionResponseStatusCodeType <<comment>> Mapping to Edifact is a problem here that still has to be solved content = 41 <<QDT>> : BusinessDocumentTypeCodeType +ReferenceToOriginal CollectedData 1 codeSchemeResponsibleAgency = 260 content = E30 <<ExchangeableBusinessInformation>> MeteringData +Identification : ebIX 02::QDT::BusinessDocumentIdentificationType [1]{SG = "5"} +AncillaryRole : ebIX 02::QDT::RoleCodeType [1]{SG = "2"} +ReasonForTransaction : ebIX 02::QDT::ReasonForTransactionCodeType [1]{SG = "5"} +BusinessSector : ebIX 02::QDT::BusinessSectorCodeType [1]{SG = "0"} +Function : ebIX 02::QDT::BusinessDocumentFunctionCodeType [1]{SG = "0"} +ObservationPeriod : ebIX 02::QDT::DateTimePeriodType [0..1]{Qualifier = "DTM-C507.2005=324", SG = "5"} <<QDT>> AncillaryRole : RoleCodeType content = MDR <<QDT>> ReasonForTransaction : ReasonForTransactionCodeType codeSchemeResponsibleAgency = 260 content = E03, E20, E21, E65, E66, E77, E60, E67, E01, E23, E75 +MeteringPoint 0..1 <<ExchangeableBusinessInformation>> Domain <<QDT>> BusinessSector : BusinessSectorCodeType +Identification : ebIX 02::QDT::DomainIdentifierType [1]{SG = "5"} content = 23 <<QDT>> Function : BusinessDocumentFunctionCodeType content = 9 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 45 C. RSM Class diagram: RequestCollectedData package RSM Request Collected Data [ RSM RequestCollected Data ] E72, 23, reason, Z05, 9 <<QDT>> Type : BusinessDocumentTypeCodeType codeSchemeResponsibleAgency = 260 content = E72 <<based on>> <<InfEnv>> RequestCollectedData 1 <<QDT>> MarketDomain : MarketDomainCodeType <<ExchangeableBusinessInformation>> Identification +DataSet +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} +MarketDomain : ebIX 02::QDT::MarketDomainCodeType [1]{SG = "0"} +MessageDateTime : ebIX 02::QDT::DateTimeType [1]{Qualifier = "DTM-C507.2005=137", SG = "0"} +ReceiverID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MR", SG = "2"} +RequestForAcknowledgementOf Acceptance : ebIX 02::QDT::ResponseTypeCodeType [1]{SG = "0"} +SenderID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MS", SG = "2"} +TimeZone : ebIX 02::QDT::TimeZoneType [0..1]{SG = "0"} codeSchemeResponsibleAgency = 260 content = E02 <<QDT>> RequestForAcknowledgementOfAcceptance : ResponseTypeCodeType content = AB <<QDT>> AncillaryRole : RoleCodeType +Requested CollectedData 1..* content = MDR <<ExchangeableBusinessInformation>> TimeSeries <<QDT>> ReasonForTransaction : ReasonForTransactionCodeType +Identification : ebIX 02::QDT::BusinessDocumentIdentificationType [1]{SG = "5"} +AncillaryRole : ebIX 02::QDT::RoleCodeType [1]{SG = "2"} +ReasonForTransaction : ebIX 02::QDT::ReasonForTransactionCodeType [1]{SG = "5"} +BusinessSector : ebIX 02::QDT::BusinessSectorCodeType [1]{SG = "0"} +Function : ebIX 02::QDT::BusinessDocumentFunctionCodeType [1]{SG = "0"} +ObservationPeriod : ebIX 02::QDT::DateTimePeriodType [0..1]{Qualifier = "DTM-C507.2005=324", SG = "5"} codeSchemeResponsibleAgency = 260 content = E03, E20, E21, E65, E66, E77, E60, E67, E01, E23, E75 <<QDT>> BusinessSector : BusinessSectorCodeType content = 23 +Register 0..* ebIX +MeteringPoint 0..* <<ExchangeableBusinessInformation>> Installation <<ExchangeableBusinessInformation>> Domain +MeterIdentification : ebIX 02::QDT::MeterIdentifierType [0..1]{SG = "8"} +RegisterIdentification : ebIX 02::QDT::RegisterIdentifierType [1]{SG = "8"} +Identification : ebIX 02::QDT::DomainIdentifierType [1]{SG = "5"} April 2009 <<QDT>> Function : BusinessDocumentFunctionCodeType content = 9, 5 ebIX Business information model for the exchange of metered data in the energy domain 46 D. RSM Class diagram: ProcessabilityErrorReportRequestCollectedData package RSM ProcessabilityErrorReportRequestCollectedData [ RSM ProcessabilityErrorReportRequestCollectedData ] <<QDT>> Type : BusinessDocumentTypeCodeType ERR for E72, 23, reason, MDR, function codeSchemeResponsibleAgency = 260 content = ERR <<ExchangeableBusinessInformation>> Identification <<based on>> <<InfEnv>> ProcessabilityErrorReportRequestCollectedData +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} +MarketDomain : ebIX 02::QDT::MarketDomainCodeType [1]{SG = "0"} +MessageDateTime : ebIX 02::QDT::DateTimeType [1]{Qualifier = "DTM-C507.2005=137", SG = "0"} +DataSet +ReceiverID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MR", SG = "2"} +RequestForAcknowledgementOf Acceptance : ebIX 02::QDT::ResponseTypeCodeType [1]{SG = "0"} 1 +SenderID : ebIX 02::QDT::PartyIdentifierType [1]{Qualifier = "NAD-3035=MS", SG = "2"} +TimeZone : ebIX 02::QDT::TimeZoneType [0..1]{SG = "0"} <<QDT>> MarketDomain : MarketDomainCodeType codeSchemeResponsibleAgency = 260 content = E02 <<QDT>> RequestForAcknowledgementOfAcceptance : ResponseTypeCodeType content = AB +Response 1 <<ExchangeableBusinessInformation>> Status +Status : ebIX 02::QDT::TransactionResponseStatusCodeType [1]{SG = "5"} +OriginalDocument 1..* <<ExchangeableBusinessInformation>> ErrorDescription +ErrorCode : ebIX 02::QDT::BusinessDocumentAcceptanceStatusCodeType [1]{SG = "5"} <<QDT>> ErrorCode : BusinessDocumentAcceptanceStatusCodeType codeSchemeResponsibleAgency = 260 content = E10, E09, E19, E50, E51, E55, E61, E62 +ReferenceTo OriginalDataSet 0..1 <<ExchangeableBusinessInformation>> Identification1 <<QDT>> Status : TransactionResponseStatusCodeType +Identification : ebIX 02::QDT::MessageIdentifier [1]{SG = "0"} +Type : ebIX 02::QDT::BusinessDocumentTypeCodeType [1]{SG = "0"} content = 41 +ReferenceTo OriginalRequest 1 <<QDT>> : BusinessDocumentTypeCodeType <<ExchangeableBusinessInformation>> <<ExchangeableBusinessInformation>> TimeSeries +Identification : ebIX 02::QDT::BusinessDocumentIdentificationType [1]{SG = "5"} +AncillaryRole : ebIX 02::QDT::RoleCodeType [1]{SG = "2"} +ReasonForTransaction : ebIX 02::QDT::ReasonForTransactionCodeType [1]{SG = "5"} +BusinessSector : ebIX 02::QDT::BusinessSectorCodeType [1]{SG = "0"} +Function : ebIX 02::QDT::BusinessDocumentFunctionCodeType [1]{SG = "0"} +ObservationPeriod : ebIX 02::QDT::DateTimePeriodType [0..1]{Qualifier = "DTM-C507.2005=324", SG = "5"} Domain codeSchemeResponsibleAgency = 260 content = E72 +MeteringPoint +Identification : ebIX 02::QDT::DomainIdentifierType [1]{SG = "5"} 0..1 <<QDT>> AncillaryRole : RoleCodeType content = MDR <<QDT>> ReasonForTransaction : ReasonForTransactionCodeType codeSchemeResponsibleAgency = 260 content = E03, E20, E21, E65, E66, E77, E60, E67, E01, E23, E75 <<QDT>> BusinessSector : BusinessSectorCodeType content = 23 <<QDT>> Function : BusinessDocumentFunctionCodeType content = 9 ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 47 Appendix C MAPPING TO XML, DOCUMENT SCHEMA’S A. XML schema: CollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:rsm="http://www.ebix.org" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/> <xsd:include schemaLocation="CollectedData_ebi_1.xsd"/> <xsd:element name="CollectedData" type="rsm:CollectedDataType"/> <xsd:complexType name="CollectedDataType"> <xsd:sequence> <xsd:element name="DataSet"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:IdentificationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="CollectedData" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:TimeSeriesType"> <xsd:sequence> <xsd:element name="MeteringPoint"> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 48 <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:DomainType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="Register"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:InstallationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="Reading" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:VolumeObservationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 49 B. XML schema: ProcessabilityErrorReportCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:rsm="http://www.ebix.org" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/> <xsd:include schemaLocation="ProcessabilityErrorReportCollectedData_ebi_1.xsd"/> <xsd:element name="ProcessabilityErrorReportCollectedData" type="rsm:ProcessabilityErrorReportCollectedDataType"/> <xsd:complexType name="ProcessabilityErrorReportCollectedDataType"> <xsd:sequence> <xsd:element name="DataSet"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:IdentificationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="Response"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:StatusType"> <xsd:sequence> <xsd:element name="OriginalDocument" maxOccurs="unbounded"> <xsd:complexType> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 50 <xsd:complexContent> <xsd:extension base="rsm:ErrorDescriptionType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="ReferenceToOriginalDataSet" minOccurs="0"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:Identification1Type"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="ReferenceToOriginalCollectedData"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:MeteringDataType"> <xsd:sequence> <xsd:element name="MeteringPoint" minOccurs="0"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:DomainType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 51 </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 52 C. XML schema: RequestCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:rsm="http://www.ebix.org" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/> <xsd:include schemaLocation="RequestCollectedData_ebi_1.xsd"/> <xsd:element name="RequestCollectedData" type="rsm:RequestCollectedDataType"/> <xsd:complexType name="RequestCollectedDataType"> <xsd:sequence> <xsd:element name="DataSet"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:IdentificationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="RequestedCollectedData" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:TimeSeriesType"> <xsd:sequence> <xsd:element name="MeteringPoint" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 53 <xsd:complexContent> <xsd:extension base="rsm:DomainType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="Register" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:InstallationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 54 D. XML schema: ProcessabilityErrorReportRequestCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:rsm="http://www.ebix.org" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/> <xsd:include schemaLocation="ProcessabilityErrorReportRequestCollectedData_ebi_1.xsd"/> <xsd:element name="ProcessabilityErrorReportRequestCollectedData" type="rsm:ProcessabilityErrorReportRequestCollectedDataType"/> <xsd:complexType name="ProcessabilityErrorReportRequestCollectedDataType"> <xsd:sequence> <xsd:element name="DataSet"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:IdentificationType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="Response"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:StatusType"> <xsd:sequence> <xsd:element name="OriginalDocument" maxOccurs="unbounded"> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 55 <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:ErrorDescriptionType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="ReferenceToOriginalDataSet" minOccurs="0"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:Identification1Type"/> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="ReferenceToOriginalRequest"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:TimeSeriesType"> <xsd:sequence> <xsd:element name="MeteringPoint" minOccurs="0"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="rsm:DomainType"/> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 56 </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 57 Appendix D MAPPING TO XML, EXCHANGEABLE BUSINESS INFORMATION SCHEMA’S E. XML schema: Exchangeable Business Information included in CollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:rsm="http://www.ebix.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/>     <xsd:element name="CollectedData_ebi_1"/>    <xsd:element name="Identification" type="rsm:IdentificationType"/> <xsd:element name="TimeSeries" type="rsm:TimeSeriesType"/> <xsd:element name="Domain" type="rsm:DomainType"/> <xsd:element name="Installation" type="rsm:InstallationType"/> <xsd:element name="VolumeObservation" type="rsm:VolumeObservationType"/>    <xsd:complexType name="IdentificationType"> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 58 <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> <xsd:element name="MarketDomain" type="qdt:MarketDomainCodeType"/> <xsd:element name="MessageDateTime" type="qdt:DateTimeType"/> <xsd:element name="ReceiverID" type="qdt:PartyIdentifierType"/> <xsd:element name="RequestForAcknowledgementOfAcceptance" type="qdt:ResponseTypeCodeType"/> <xsd:element name="SenderID" type="qdt:PartyIdentifierType"/> <xsd:element name="TimeZone" type="qdt:TimeZoneType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="TimeSeriesType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:BusinessDocumentIdentificationType"/> <xsd:element name="AncillaryRole" type="qdt:RoleCodeType"/> <xsd:element name="ReasonForTransaction" type="qdt:ReasonForTransactionCodeType"/> <xsd:element name="BusinessSector" type="qdt:BusinessSectorCodeType"/> <xsd:element name="Function" type="qdt:BusinessDocumentFunctionCodeType"/> <xsd:element name="ObservationPeriod" type="qdt:DateTimePeriodType" minOccurs="0"/> <xsd:element name="Resolution" type="qdt:ResolutionType"/> <xsd:element name="RegistrationDateTime" type="qdt:DateTimeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="DomainType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:DomainIdentifierType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="InstallationType"> <xsd:sequence> <xsd:element name="MeterIdentification" type="qdt:MeterIdentifierType"/> <xsd:element name="RegisterIdentification" type="qdt:RegisterIdentifierType"/> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 59 </xsd:sequence> </xsd:complexType> <xsd:complexType name="VolumeObservationType"> <xsd:sequence> <xsd:element name="Position" type="qdt:SequencePositionType"/> <xsd:element name="Quantity" type="xsd:float" minOccurs="0"/> <xsd:element name="QuantityQuality" type="qdt:QuantityQualityType" minOccurs="0"/> </xsd:sequence> </xsd:complexType>  </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 60 F. XML schema: Exchangeable Business Information included in ProcessabilityErrorReportCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:rsm="http://www.ebix.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/>     <xsd:element name="ProcessabilityErrorReportCollectedData_ebi_1"/>    <xsd:element name="Identification" type="rsm:IdentificationType"/> <xsd:element name="Status" type="rsm:StatusType"/> <xsd:element name="ErrorDescription" type="rsm:ErrorDescriptionType"/> <xsd:element name="Identification1" type="rsm:Identification1Type"/> <xsd:element name="MeteringData" type="rsm:MeteringDataType"/> <xsd:element name="Domain" type="rsm:DomainType"/>    <xsd:complexType name="IdentificationType"> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 61 <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> <xsd:element name="MarketDomain" type="qdt:MarketDomainCodeType"/> <xsd:element name="MessageDateTime" type="qdt:DateTimeType"/> <xsd:element name="ReceiverID" type="qdt:PartyIdentifierType"/> <xsd:element name="RequestForAcknowledgementOfAcceptance" type="qdt:ResponseTypeCodeType"/> <xsd:element name="SenderID" type="qdt:PartyIdentifierType"/> <xsd:element name="TimeZone" type="qdt:TimeZoneType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="StatusType"> <xsd:sequence> <xsd:element name="Status" type="qdt:TransactionResponseStatusCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ErrorDescriptionType"> <xsd:sequence> <xsd:element name="ErrorCode" type="qdt:BusinessDocumentAcceptanceStatusCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="Identification1Type"> <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="MeteringDataType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:BusinessDocumentIdentificationType"/> <xsd:element name="AncillaryRole" type="qdt:RoleCodeType"/> <xsd:element name="ReasonForTransaction" type="qdt:ReasonForTransactionCodeType"/> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 62 <xsd:element name="BusinessSector" type="qdt:BusinessSectorCodeType"/> <xsd:element name="Function" type="qdt:BusinessDocumentFunctionCodeType"/> <xsd:element name="ObservationPeriod" type="qdt:DateTimePeriodType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="DomainType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:DomainIdentifierType"/> </xsd:sequence> </xsd:complexType>  </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 63 G. XML schema: Exchangeable Business Information included in RequestCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:rsm="http://www.ebix.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/>     <xsd:element name="RequestCollectedData_ebi_1"/>    <xsd:element name="Identification" type="rsm:IdentificationType"/> <xsd:element name="TimeSeries" type="rsm:TimeSeriesType"/> <xsd:element name="Domain" type="rsm:DomainType"/> <xsd:element name="Installation" type="rsm:InstallationType"/>    <xsd:complexType name="IdentificationType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 64 <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> <xsd:element name="MarketDomain" type="qdt:MarketDomainCodeType"/> <xsd:element name="MessageDateTime" type="qdt:DateTimeType"/> <xsd:element name="ReceiverID" type="qdt:PartyIdentifierType"/> <xsd:element name="RequestForAcknowledgementOfAcceptance" type="qdt:ResponseTypeCodeType"/> <xsd:element name="SenderID" type="qdt:PartyIdentifierType"/> <xsd:element name="TimeZone" type="qdt:TimeZoneType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="TimeSeriesType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:BusinessDocumentIdentificationType"/> <xsd:element name="AncillaryRole" type="qdt:RoleCodeType"/> <xsd:element name="ReasonForTransaction" type="qdt:ReasonForTransactionCodeType"/> <xsd:element name="BusinessSector" type="qdt:BusinessSectorCodeType"/> <xsd:element name="Function" type="qdt:BusinessDocumentFunctionCodeType"/> <xsd:element name="ObservationPeriod" type="qdt:DateTimePeriodType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="DomainType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:DomainIdentifierType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="InstallationType"> <xsd:sequence> <xsd:element name="MeterIdentification" type="qdt:MeterIdentifierType" minOccurs="0"/> <xsd:element name="RegisterIdentification" type="qdt:RegisterIdentifierType"/> </xsd:sequence> </xsd:complexType>  </xsd:schema> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 65 H. XML schema: Exchangeable Business Information included in ProcessabilityErrorReportRequestCollectedData <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:rsm="http://www.ebix.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ccts="urn:un:unece:uncefact:documentation:standard:CoreComponentsTechnicalSpecification:2" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" xmlns:qdt="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" xmlns:ram="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" targetNamespace="http://www.ebix.org" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1"> <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:3" schemaLocation="UnqualifiedDataType_3p0.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:QualifiedDataType:02H" schemaLocation="QualifiedDataType_02H.xsd"/> <xsd:import namespace="urn:un:unece:uncefact:data:draft:ReusableAggregateBusinessInformationEntity:04" schemaLocation="ReusableAggregateBusinessInformationEntity_04.xsd"/>     <xsd:element name="ProcessabilityErrorReportRequestCollectedData_ebi_1"/>    <xsd:element name="Identification" type="rsm:IdentificationType"/> <xsd:element name="Status" type="rsm:StatusType"/> <xsd:element name="ErrorDescription" type="rsm:ErrorDescriptionType"/> <xsd:element name="Identification1" type="rsm:Identification1Type"/> <xsd:element name="TimeSeries" type="rsm:TimeSeriesType"/> <xsd:element name="Domain" type="rsm:DomainType"/>    <xsd:complexType name="IdentificationType"> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 66 <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> <xsd:element name="MarketDomain" type="qdt:MarketDomainCodeType"/> <xsd:element name="MessageDateTime" type="qdt:DateTimeType"/> <xsd:element name="ReceiverID" type="qdt:PartyIdentifierType"/> <xsd:element name="RequestForAcknowledgementOfAcceptance" type="qdt:ResponseTypeCodeType"/> <xsd:element name="SenderID" type="qdt:PartyIdentifierType"/> <xsd:element name="TimeZone" type="qdt:TimeZoneType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="StatusType"> <xsd:sequence> <xsd:element name="Status" type="qdt:TransactionResponseStatusCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="ErrorDescriptionType"> <xsd:sequence> <xsd:element name="ErrorCode" type="qdt:BusinessDocumentAcceptanceStatusCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="Identification1Type"> <xsd:sequence> <xsd:element name="Identification" type="qdt:MessageIdentifier"/> <xsd:element name="Type" type="qdt:BusinessDocumentTypeCodeType"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="TimeSeriesType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:BusinessDocumentIdentificationType"/> <xsd:element name="AncillaryRole" type="qdt:RoleCodeType"/> <xsd:element name="ReasonForTransaction" type="qdt:ReasonForTransactionCodeType"/> ebIX April 2009 ebIX Business information model for the exchange of metered data in the energy domain 67 <xsd:element name="BusinessSector" type="qdt:BusinessSectorCodeType"/> <xsd:element name="Function" type="qdt:BusinessDocumentFunctionCodeType"/> <xsd:element name="ObservationPeriod" type="qdt:DateTimePeriodType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="DomainType"> <xsd:sequence> <xsd:element name="Identification" type="qdt:DomainIdentifierType"/> </xsd:sequence> </xsd:complexType>  </xsd:schema> ebIX April 2009

ebix model measure introduction 1.0.d

Related documents

Products

Support

ebix model measure introduction 1.0.d

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib