Submission BIE’s & BDT’s + some proposed new CC’s UN/CEFACT Forum, PDA Supply Chain April 2012

ebIX ® ebIX ® : European Forum for energy business Information eXchange European Energy Market: Electricity and Gas Focus on downstream part of the market: Customer Distribution System Operator (lower voltage grids) Supplier, Metering companies Master data and measured data Start: mid nineties in Nordic countries as Ediel organization, since 2002 as ebIX ® for Europe

ebIX ® work 1990’s: Start with Edifact Message Implementtaion Guides (MSCONS, DELFOR, PRODAT, …) : Development of UTILMD and UTILTS UNSM’s 2001: start modeling using UML Around 2005: first draft CC’s 2008-now: next step in modeling

ebIX ® modeling since 2008 UML-2 UMM-2 CCTS UPCC 3.0 NDR 3.0 OCL 2.0 Model Driven Architecture paradigm: model in UML + use of OCL and derive technology dependent elements from UML model Supported technologies: XML (schema’s based on NDR 3.0) Edifact (UTILMD and UTILTS, yet to be completed) Web services (yet to be developed)

ebIX ® model organization Organized along lines of responsibility: separate modules for different responsibilities moduleorganizationcontent UMM-2/UPCCUN/CEFACTMeta model information CefactUN/CEFACTCC’s and code & qualifier lists ebIX ® CC’s, code lists and additional meta model information Role modelebIX ®, EFET and ENTSO-E Responsibilities, domains and installations Business domainsVarious work groups and organizations High level >

Business Requirements Previous model version used as start for new Business Requirements Specification (BRS) Business work groups for re-defining BRS “Modeled” in UML Using UMM-2 recommendations for Business Requirements View Payload for information exchange specified for synchronous web services Optional additional information for a- synchronous and “optional” additions

ebIX ® BIE’s and BDT’s Previously: Information clusters acting as draft CC’s in previous model version as developed from 2005 onwards, have been used as initial guide for clustering new BIE’s Now: Real clustering based on defining objects and on normalization; where possible starting from available CC’s

Messages: header and context In previous model version use of SBDH version 1 In present UMM-2 model version still intention to use the finalised SBDH version 3.0, but ….. For the time being using own header specification We have defined an > for Context to be added to the > next to the SBDH in case of a-synchronous message exchange

Collected Data built from CC

Present ebIX ® header info Temporary ebIX ® header Context specification as expected to be required next to ebIX ® web service specification

ebIX ® business processes modeled yet Introduction to ebIX ® models Measure Collect Measure for Imbalance Settlement Measure for Labeling Measure for Reconciliation (only BRS, no BIM yet) Structure Change of Supplier

ebIX ® business processes still to do this year Measure for Reconciliation (complete BIM) Measure for Billing Measure Determine Switch Read Settle for Reconciliation Structure End of Supply Structure Notify MP master data Structure Change of Metered Data Responsible Structure Change of Balance Responsible Structure End of Metered Data Responsible Structure End of Balance Responsible Structure Change of Customer Structure Change of Meter Structure Notify Meter master data

contact