ebix standard presentation 20080102

Name

[email protected]

January, 2008

Overview of ebIX workGoals and results to date

European forum for energy Business Information eXchange

Customer choice crucial since it helps achieve the other goals.

Enabling customers in the different Member States to choose and change their electricity suppliers freely:

One of the most important goals for the IEM.

Why is data exchange important? EU Internal Market perspective:

Main benefits for the European economies and citizens of competitive energy markets within the European internal market: Cost effective use of generation resources, including optimal

Europe-wide power plant dispatch Optimal and sufficient investment in new generation

resources Customer choice

What enables customer choice?EU Internal Market perspective:

The ability for suppliers to offer their products to customers in other countries cost-effectively

This necessitates an easy understanding of the rules for customer switching, i.e. rules that are harmonised and well-known

Clear and harmonised definitions of the data needed for switching a customer from one supplier to another, and of the way the meter data get transferred to the suppliers

In short: Harmonised data exchange processes, ebIX’ raison d`etre:

Advance, develop and standardise the use of electronic information exchange in the energy industry

Speak the language of software developers

Objective and goals

Make standards independent of syntax and communication

Cover exchange of administrative data Cover both the whole-sale and retail market for both

gas and electricity Promote and advance the standardisation process in

the European energy market Contact and coordination with other EDI/XML

standardization organizations Follow the rules of the European Union

Why is the ebIX work importantto the market partners?

The danger of stranded investments is high: If things do not work, customers complain. If things do not work, national regulators and the EU

Commission get tempted to impose rules and deadlines. These may or may not be compatible with prior IT

investments. Learning from the experiences of other ebIX

countries may speed development of national systems and reduce the overall amount of work and discussions needed nationally.

Harmonising process descriptions with other countries reduces the risk of regulators imposing diverging rules.

The software needed to implement a liberalised household customer market is very costly.

The ebIX organisation

CuS

EMVR

NationalebIX groups

Nationalprojects ETCMembers:

BelgiumDenmarkGermanyNorway

NetherlandsSwitzerland

Sweden

ETC ebIX Technical CommitteeEMD ebIX Exchange of Metered Data projectCuS ebIX structuring of the energy market (Customer Switching) projectEMVR ebIX and ETSO Metered Value Report project

Observers:Austria BulgariaEstoniaFinlandFranceGreece

Nord Pool

EMD

Eurelectric/ebIXLiaison group

ebIX, EFET and ETSOHarmonisation group

The history of ebIX (Ediel)

Nord Pool ASA starts EDI-project 1993

Co-operation Norway and Sweden 1994

Ediel Nordic Forum established 1995

The Netherlands and Germany become observers 1998

France joins the CoS project 2000

Belgium becomes observer 2001

ebIX (European forum for energy Business Information eXchange) is formed as a European standardisation body 2003

Switzerland becomes member 2004

ebIX messages/day - Sweden

0

10000

20000

30000

40000

50000

60000

70000

80000

1996 1997 1998 1999 2000 2001 2002 2003 2004 2005

Energy standardisation bodies

European forum for energy Business Information eXchange

Observer

ebIX structuringof the energy

market project

EMDebIX metereddata prosjekt

ebIX TechnicalCommittee

MoU

MoU

CuSETC

TCG

TF-EDI

TC57/WG16

Category “D” liaison organization?

EMVR

ebIX MeteredValue report

EASEE-gas

ebIX/EFET/ETSO Harmonisation group

“CC project”

Eurelectric and ebIX

liaison group

Edig@sEdig@sEdig@s

Why is data exchange difficult?It used to be easy in the integrated utility!

Production

Network

Supply

Metering

Settlement

Reconciliation

Billing

Competition

Why is data exchange difficult? Splitting between DGO, TSO and supplier

DGO:• Metering• Metering Point

administration

TSO:• Settlement• reconciliation

Maintain Balance: Split TSO from regulated net Need for scheduling and metering

• Trader• Supplier• Producer• Balance

Responsible

Unique Metering Point Identification

Why is data exchange difficult? Organize Metering

Grid area

Grid area

DGO:• Settlement• Reconciliation

Organize Settlement

Supply

TSO Production

MesswandlerzählerZählerangaben StromwandlerSpannungswandler

1234567.8181 +W HT M1

Drehstromzähler Cl. 27EC6352 -0CA5 -1 AA0 / D06Nr. 00 000 000 943 x 230 / 400 V 10 (60) A 50 HzRL= 1 000 Imp./ kWh

Schltg.S4520

RL

DÜPARRÜCK

Eigentum desElektrizitätswerkes


1234567.8181 +W HT M1


Schltg.S4520

RL

DÜPARRÜCK



1234567.8181 +W HT M1


Schltg.S4520

RL

DÜPARRÜCK



1234567.8181 +W HT M1


Schltg.S4520

RL

DÜPARRÜCK



1234567.8181 +W HT M1


Schltg.S4520

RL

DÜPARRÜCK



1234567.8181 +W HT M1


Schltg.S4520

RL

DÜPARRÜCK


AMR/Profiled

ebIX, EFET and ETSOHarmonised role model

A role is of a logical nature (such as a Metered data responsible) which act within a given domain (such as a Metering grid area).

A role represents the external intended behaviour of a party. A single party may assume multiple roles.

The role model shall be the formal means of identifying roles and domains used in information interchange.

The role model permits a processes to be analysed within the context of identified roles and not within the context of parties.

A domain represents a delimited area that is uniquely identified for a specific purpose.

ebIX, EFET and ETSOHarmonised role model

1. Harmonisation of vocabulary2. Definition of terms3. Identification of roles and domains4. Shows responsibilities

Identification ofRoles of actors

Identification of geographical and functional domains

ebIX Technical Committee (ETC)

A permanent ebIX working group Responsible for the technical part of the ebIX

standards, such as: how to create and manage ebIX projects how to model according to ebIX rules

ebIX Modelling methodology ebIX European energy domain model ebIX Business information models (technical) ebIX Core Components ebIX Registry and repository ebIX Common rules and recommendations ebIX XML and EDIFACT Implementation Guides

ebIX Technical Committee (ETC) Modelling Methodology

A guide for ebIX projects and wg’s

Describes: how to create and manage ebIX projects

how to model according to ebIX rules how to make syntax specific business documents how to maintain and change models and business document

Based on: UN/CEFACT Modelling Methodology (UMM) UN/CEFACT XML Naming and Design Rules (NDR) UN/CEFACT Core Components Technical Specification

(CCTS) ebIX, EFET and ETSO Harmonised role model

ebIX Technical Committee (ETC) Data exchange architecture

Basic building blocks for data exchange Process design based upon

Uniform methodology based on UMM (CEFACT) (e.g. Standard Transaction patterns)

Graphic language : UML ebIX rules and recommendations Naming and design rules

Translation of models to syntax-dependent messages (EDIFACT/XML)

Identification schemes for metering points, parties and roles,…

Code lists for data elements

ebIX Technical Committee (ETC) Architecture Layers

Implementation

Process models

Building blocks

MethodologyUMM

(UN/CEFACT Modelling Methodology)

NDR(UN/CEFCAT XML

Naming and design rules)

ebIX Core Components ebIX Code lists

External CC External Code lists

Specific(Customer switching,

Metering)

NDR(UN/CEFCAT XML Naming

and design rules )

EDIFACT(Implementation guides)

XML(Schemas )

ebIX Technical Committee (ETC) Energy business domain model

ebIX Technical Committee (ETC) UMM Artefacts

Sequence diagram

A UseCase is described by an Activity diagram and a Sequence diagram

Activity diagram

Action state

An Activity diagram may have one or more Subactivity diagrams linked through Subactivity states

Subactivity state

Metering point characteristic

-Additional information (text)[0..1]-Category of net user[0..1]-Energy fee[0..1]-Location description (text)[0..1]-Loss factor[0..1]-Maximum power[0..1]-Meter voltage level[0..1]-Metering grid area[0..1]-Metering method[0..1]-Metering point address[0..1]-Metering point voltage level[0..1]-Net reserve power[0..1]-Next scheduled meter reading date[0..*]-Priority[0..1]-Settlement method[0..1]-Standard load profile[0..1]-Switch category[0..1]-Type of Metering point[0..1]-VAT[0..1]

<<e.Message>>414, Confirmation of start of supply

-Market[0..1]-Message date[1]-Message function[1]-Message id[1]-Message name[1]-Message receipient - Coding scheme[1]-Message sender - Coding scheme[1]-Request for acknowledgement[1]-Time zone[1]

Transaction

-Hierarchical level of Metering point[0..1]-Meter id[0..1]-Metering grid area[0..1]-Metering point id[0..1]-Observation length[0..1]-Processing period[0..1]-Reason for transaction[1]-Transaction id[1]

Consumer

-Grid operators customer number[0..1]-Party address[0..1]-Party id[0..1]-Party name[1]-Suppliers customer number[0..1]

Type of net using contracy

-Type of net using contract, coded[1]

Meter data

-Capacity status[0..1]-Constant[0..1]-EDIS code[0..1]-Estimated annual volume[0..1]-Meter id[0..1]-Meter time frame[0..1]-Number of digits[0..1]-Product[0..1]-Register id[0..*]

Answer status

-Reason for answer[0..1]-Reference to transaction[0..1]-Status for answer[1]

Balance responsible party

-Party id[1]

Reason for transaction:- Change of supplier- Move- Switch on drop

Contract start date

-Date[1]

Only Denmark

1

0..1

1

0..1

1

0..1

1

0..1

10..1

1

0..*

1

1

1

1..*

A message is detailed in a Class diagram

Class diagram

ebIX, EMD ebIX Metered data project

Making a model for the exchange of metered data between parties in the upstream European energy market: Fit into the overall ebIX model of the deregulated European

energy market Give a basis for a common way of exchanging metered data

in the upstream energy market

Models available for Measure for imbalance settlement Measure for reconciliation Measure for billing Measure for determine switch stand

ebIX, EMDEMD UseCases (processes)

ebIX, EMD Example of detailed use case

ebIX, Customer Switching (CuS)

Making a model for the exchange of structuring data in the European energy market

Many characteristics of an object in the energy sector change over time: Customer switching Customer move End of supply Maintenance of master data Switch of roles, such as Balance responsible and Metered

data collector Switch of attributes, such as Standard Load Profile, Annual

consumption, Metering method….

ebIX, Customer Switching (CuS)UseCase: Structure

ebIX, Customer Switching (CuS)Sequence: Customer switching

ebIX, Customer Switching (CuS) Activities: Customer switching

New balance supplier

Make contract with new consumer

<<CommercialTransactionActivity>>Send request for change ofmetering point master data

<<RespondingBusinessActivity>>Handle negative

confirmation of start of supply

<<RespondingBusinessActivity>>Start supply

To be continued....

Old balance supplier

<<RespondingBusinessActivity>>Stop supply

Metering point administrator

<<NotificationActivity>>Notify of end of relation

<<RespondingBusinessActivity>>Process switch

<<RespondingBusinessActivity>>Update

metering point db

414/E03 (negative)

414/E03 (positive)

392/E03

Is there a balance supplierconnected to the MP?

E44/E03

End

Switch OK?

Start

End

End

Yes

Yes

No

No

ebIX, Customer Switching (CuS) Activities: Customer switching, continued

New balance supplier

<<RespondingBusinessActivity>>Update DB

Metering point administrator

Exchange master data

<<NotificationActivity>>Send master data, metering point

Exchange switch stand

E07/E03

EndEnd

End

ebIX, Customer Switching (CuS) Class diagram: 392, Request for change of metering point master data (E03)

Energy Measured Values Report

Foreseen deliverables first phase: Model for Exchange of Metered Data for Billing between TSOs Common Core Components for Metered Data

Joint project by ebIX and ETSO (with cooperation from EFET and UCTE)

Eurelectricand ebIX liaison group

Eurelectric has the main responsibility for the business issues, while ebIX takes care of the technical (modelling) issues.

The model may in a later stage be extended to other processes within the structuring phase of the energy market, i.e.: customer move end of supply change of meter update of master data etc.

The liaison group have made a UseCase model describing the Change of supplier process within the European liberalised electricity market

Eurelectric and ebIX liaison groupUseCase: Change of supplier

ebIX Vendor group

To review ebIX deliverables before publication and generate feedback: standards should be clear and technical sound solutions

To exchange experiences with implementation of ebIX (related) standards in various countries

To advise ebIX about its on-going work and possible new work

Dissemination of the ebIX results to the market participants

Encourage standardisation from a practical perspective

Provide observers for ebIX working groups on request from one of the groups or on own initiative

To be informed by ebIX about its activities

General results of the ebIX work

The ebIX framework is implemented in Austria, Belgium, Denmark, Finland, Germany, Netherlands, Norway, Sweden and Switzerland

Millions of messages are exchanged between hundreds of actors in the above mentioned countries

About 80 million messages a year in Sweden About 1000 actors in Germany and 300 in Norway

The implemented processes include Structuring, including customer switching Metered data for settlement, reconciliation and billing Bidding on the Nordic power exchange (NordPool) Scheduling (in some countries)

Technical documents available on www.ebix.org :

ebIX Methodology ebIX Recommended identification schemes for

the European energy industry ebIX Common rules and recommendations ebIX Recommendations for acknowledgement

and error handling Implementation guides for UTILMD and UTILTS

Results, Technical documents

Results,Benefits

The only European alternative for the downstream energy domain

Reuse of relevant experience

We have a modelled solution: Quick development of national models Cost-efficient implementation using fixed

elements

Harmonisation challenges

Several bodies are involved in making e-business standards in the European energy market

The rules, legislation, organisation and level of deregulation differs between countries and regions

Complex and changing business processes Cooperation across boundaries:

Electricity and gas Whole-sale (upstream) and retail (downstream)

Moving towards ONE European energy market Special planning requirements for electricity Huge data volumes

How to succeed

Understand common problems and markets Formulate practical and efficient solutions Cooperate with the gas market to reach the goals Respect local market rules and solutions,

i.e. make it possible to adapt to new standards Promote the ”lessons learned” Try to obtain unanimous decisions Try to become the de-facto European standardisation-

body for the energy market Base the work on voluntary participation,

keeping the budget to a minimum

Conclusions

Process descriptions and syntax are detailed and hard work

ebIX syntax is open and modern (EDIFACT, XML) ebIX process descriptions are harmonised and open

The processes cover much of the member countries need The process can be modified to fit new countries

Without open and harmonised process descriptions (and syntax), much duplication of effort and of software will occur, and customer choice would suffer

Harmonised process descriptions are especially important for open household customer markets

Within the 3rd EU Internal Energy Market package, several items support the work and the goals of ebIX

Harmonised data exchange is very important for IEM-wide customer choice and overall success of liberalisation

Thank you for yourkind attention

www.ebix.org

ebix standard presentation 20080102

Documents