The Norwegian Elhub

Standards, models and conceptual approach

Per Øyvind Berg-KnutsenStatnett SF

Statnett SF

The Norwegian Elhubhttp://www.elhub.no/

Standards, models and conceptual approach

Per Øyvind Berg-Knutsen

Statnett SF

Agenda

• Introduction to the Elhub project– Elhub and the Norwegian power utility market

• Developing Elhub core models– Information assets developed– Transforming Elhub processes into standard messages

• CIM-ebIX harmonisation– Harminization needs

The current Norwegian power utility market

…

4

3

2

1

DSO's

…

D

C

B

A

Suppliers

About 130 DSOs About 110 energy suppliers

About 2.8M meteringpoints

~1M business processesper year

(supplier changes, customer moves, masterdata updates)

The current Norwegian power utility market

…

4

3

2

1

…

D

C

B

A

DSO's Suppliers

About 130 DSOs About 110 energy suppliers

About 2.8M meteringpoints

~1M business processesper year

(supplier changes, customer moves, masterdata updates)

The future Norwegian power utility market

to

"today everyone talks with everyone" "Everyone talks with Datahub"

…

4

3

2

1

…

D

C

B

A

HUB

DSO's Suppliers

…

4

3

2

1

…

D

C

B

AMetered values

Master dataEnd-user inform.

SwitchingMoving

Settlement data

DSO's Suppliers

Elhub will include DATA storage in addition to being a

communications hub

Key aspects of Elhub processes

• Data processing: After-the-fact– Settlement and reconciliation– Reporting

• Preliminary and final processing

• Business processes:– Future (holding)– Current (being executed)– Past (reversals)

Is data available?Processing

time

Preliminary processing

Final processing

Assumed or empirical values

Actual meteredvalues

No Yes

Introduction to the Elhub project

• The Elhub is scheduled to go live on 1 October 2016– The Elhub will be the authoritative source on such data in the market,

although the Metered Data Collector will be collecting these from themeters

• Statnett will be setting up a data hub (Elhub) for storing collectingmetered data from AMS meters to be installed in the market by 2019

• The project has currently a public tender for an overall solution for theElhub– The basis for all of the following information has been shared with and in

the market, although most in Norwegian– The considerations leading up to decisions have been developed in

cooperation with parties in the market

2016: Elhubgo-live

2019: AMR transformation

complete

Data responsibility shiftfrom market actors to

Elhub

Status: Public tender for solution

Models and descriptionsexist in Norwegian

Documents developed in cooperation with market

actors

Regional cooperation and influence

• Regional harmonization– HNR – Harmonised Nordic Retail market– NBS – Nordic Balance Settlement– Wide consensus on common market bases an processes

• SE, DK, FI, NO

• Denmark– Developed a data hub in 2012– Cooperation provide Elhub with vital experiences– Business process similarities

• Sweden, Finland– Starting up– Expect significant business process similarities

Wholesalemarket area

Electric utility Customer area

Existing standards vs. Elhub needsMarket business process area

ebIX functionalcoverage

ENTSO-E functionalcoverage

CIM functional coverage

Wholesalemarket area

Electric utility Customer area

Existing standards vs. Elhub needsMarket business process area

ebIX functionalcoverage

ENTSO-E functionalcoverage

Elhub needs

ebIX functionalcoverage

CIM functional coverage

Elhub in a CIM context

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

Nordic Balance

Settlement

ENTSO-E functionalcoverage

ebIX functionalcoverage

National adaptations to ebIX

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

Elhub base models

• Role model – defining roles and theirassociations

• Information model – defining internalinformation entities and their logical relations

• Security model – defining key considerations for access to information entities by different rolesas defined in the role model

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

Elhub base models

• Role model – defining roles and theirassociations

• Information model – defining internalinformation entities and their logical relations

• Security model – defining key considerations for access to information entities by different rolesas defined in the role model

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

Elhub base models

• Role model – defining roles and theirassociations

• Information model – defining internalinformation entities and their logical relations

• Security model – defining key considerations for access to information entities by different rolesas defined in the role model

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

Elhub base models

• Role model – defining roles and theirassociations

• Information model – defining internalinformation entities and their logical relations

• Security model – defining key considerations for access to information entities by different rolesas defined in the role model

class Role Model-with NECS

Imbalance

Settlement

Responsible(from

Roles)

Balance

Responsible

Party(from

Roles)

Metered Data

Aggregator(from

Roles)

Balance Supplier

(from

Roles)

Balance Supplier

of Last Resort(from

Roles)

Domains::Meter

Domains::Metering

Point

Domains::

Accounting Point

Domains::

Exchange Point

Domains::

MeteringGrid Area

Meter

Administrator(from

Roles)

Domains::Register

Metered Data

Responsible(from

Roles)

Meter Operator

(from

Roles)Metering Point

Administrator

A

(from

Roles)

Metered Data

Collector(from

Roles)

GridAccess

Prov ider(from

Roles)

Consumer

(from

Roles)

Grid Operator

(from

Roles)

Local Settlement

Responsible(from

Roles)

Domains::Market

Balance Area

Name: Role Model-with NECS

Author: annep

Version: 1.0

Created: 03.06.2014 09:15:06

Updated: 03.06.2014 09:15:06

Metered Data

Administrator(from

Roles)

Metering Point

Responsible(from

Roles)

Party connected

to Grid(from

Roles)

Producer

(from

Roles)

Domains::Consumption

Accounting Point

Domains::Production Accounting

Point

Grid Settlement

Responsible(from

Roles)

Energy

Settlement

Responsible(from

Roles)

Billing Agent,

Customer(from

Roles)

Third Party

(from

Roles)

Domains::Certificate

Registry (NECS)

has grid access contract with

reports quota obliged volumes to

aggregates/balances within

operates

1..*

connecting

administrates

is collecting data for

1..*

has

1..*

has

0..*

may be connected

to

provides access to

aggregates balance calculations for

1..*

belongs

to

1

controls financially

uses

uses

may enter

into

contract

with

provides volumes to

has contract with

has balance supply contract with

performs aggregation/balancing for

operates and maintains

is handling data

for

administrates meter information for

is supplier of last resort

within

has contract with

is responsible for creating and closing

is responsible for administration of

administrates meter values for

handles total reconciliation

for

invoices customer

at

1..*

is balance responsible

for

1..*

0..*

may be connected

to

1

contains

1..*

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

- The Elhub Security Model

• Metered values = personal information

• Names and identities must be protected

• Contracts are commercially sensitive information

• Third parties expected to become keyplayers

• Solution: Two levels of access:– Implicit access– explicit access

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

- Metering point State Model• Aggregated from:

– Physical state (metering point)– Contractual binding to Grid Access Provider (DSO)– Contractual binding to Balance Supplier

• Combined and simplified for Elhub purposes…

stm Metering Point State diagram

Decision to

establish

Metering

Point (MP)

MP agg.2

Inactiv e without

contract

(Inaktiv t u/av tale)

MP Activ e

MP Deleted

BRS-NO-121 New

Metering Point

Name: Metering Point State diagram

Author: perber

Version: 1.0

Created: 21.01.2014 10:08:51

Updated: 21.02.2014 14:51:21

ExitPoint

[now] > contract end date +

specified archive period

MP Removed [MP Powered Down]

MP Powered Up, GA contract

registered [MP installed]

Message from grid

owner [T08]MP Powered Down

stm Grid Access contract State diagram

EntryPoint

GA contract

Grid Access (GA)

contract Activ e

GA contract Ended

ExitPoint

Name: Grid Access contract State diagram

Author: perber

Version: 1.0

Created: 21.01.2014 14:31:52

Updated: 26.02.2014 12:08:46

Contract start date = BS

contract start date (for

first BS for this

customper in this MP)

Contract end date = BS

contract end date (for

last BS for this customer

in this MP)

[now] > contract end date +

specified archive period

[now] > contract end date

[now] < contract end date ||

unset(contract end date), [now] >=

contract start date

stm Balance Supply contract State diagram

EntryPoint

BS contract

Name: Balance Supply contract State diagram

Author: perber

Version: 1.0

Created: 21.01.2014 14:43:18

Updated: 26.02.2014 12:09:46

Balance Supply (BS)

contract registered

BS contract Activ e BS contract of last

resort

BS contract Ended

ExitPoint

[now] > contract end date + specified archive period

set(contract cancellation date)

[now] > contract end date [now] > contract end date

Set flag Last Resort, [now]

>= contract start date, [now]

< contract end date ||

unset(contract end date)

[now] >= contract start date,

[now] < contract end date ||

unset(contract end date)

stm Total MP state diagram

No contract

Future contract

Active contract Active MPDeleted MP Inactive MP

Name: Total MP state diagram

Author: perber

Version: 1.0

Created: 21.01.2014 10:53:21

Updated: 28.04.2014 15:00:23Decision to establish Metering Point (MP)

MP agg.2

Inactive without

contract

(Inaktivt u/avtale)

MP agg.3

Inactive, future

contract

(Inaktivt, fremtidig

avtale)

MP agg.4

Inactive w/contract

(Inaktivt m/avtale)

MP agg.5

Active without

contract

(Aktivt uten avtale)

MP agg.6

Active, future

contract

(Aktivt, fremtidig

avtale)

MP agg.7

Active w/contract

(Aktivt med avtale)

MP agg.8

Active, Last Resort

(Aktivt, lev.plikt)

ExitPoint

MP agg.9

Removed

(Deaktivert)

MP agg.10

Active, Supplier

change

(Aktivt,

Leverandørbytte)

Creating active contracts and/or activating contracts will have a configurable

dependence on the presence of metered values for the metering point. This

configuration will differ for registering future contracts and activating contracts.

[now] > contract end date ||

set(contract cancellation date),

Move-out [T18]

Reversed end

date [T21]

Activate MP [T09]

Reversed

move-out

[T20]

[now] >= start date [T23]

Reversed MP activation [T16]

Move-out [T17]

Deactivate MP with

future contract [T15]

[now] > contract end date ||

set(contract cancellation date)

[T19]

Cancel future

contract [C01]

Deactivate MP [T14]

Message from

grid owner [T08]

Restore wrongly

removed [T22]

create

future

contract

[T28]

Create future

contract [T01]

Create future

contract [T02]

[now] >= start date [T24]

[now] > deleted date + specified archive period

Create active contract of Last Resort [T12]

New customer on

Last Resort [T27]

End active

contract [T07]

Set flag Last Resort,

[now] >= start date

[T25]

[now] > contract end date ||

set(contract cancellation date),

Move-out [T06]

Immediate change to new customer

selected supplier agreement [T04]

Remove physical MP [T13]

Create

active

contract

[T03]

[now] >= start date, New

agreement [T26]

Activate MP [T11]

Create future

contract [T29]

Activate MP [T10]

Cancel future

contract [C02]

Create new active

contract [T05]

stm Total MP state diagram

No contract

Future contract

Active contract Active MPDeleted MP Inactive MP

Name: Total MP state diagram

Author: perber

Version: 1.0

Created: 21.01.2014 10:53:21

Updated: 28.04.2014 15:00:23Decision to establish Metering Point (MP)

MP agg.2

Inactive without

contract

(Inaktivt u/avtale)

MP agg.3

Inactive, future

contract

(Inaktivt, fremtidig

avtale)

MP agg.4

Inactive w/contract

(Inaktivt m/avtale)

MP agg.5

Active without

contract

(Aktivt uten avtale)

MP agg.6

Active, future

contract

(Aktivt, fremtidig

avtale)

MP agg.7

Active w/contract

(Aktivt med avtale)

MP agg.8

Active, Last Resort

(Aktivt, lev.plikt)

ExitPoint

MP agg.9

Removed

(Deaktivert)

MP agg.10

Active, Supplier

change

(Aktivt,

Leverandørbytte)

Creating active contracts and/or activating contracts will have a configurable

dependence on the presence of metered values for the metering point. This

configuration will differ for registering future contracts and activating contracts.

[now] > contract end date ||

set(contract cancellation date),

Move-out [T18]

Reversed end

date [T21]

Activate MP [T09]

Reversed

move-out

[T20]

[now] >= start date [T23]

Reversed MP activation [T16]

Move-out [T17]

Deactivate MP with

future contract [T15]

[now] > contract end date ||

set(contract cancellation date)

[T19]

Cancel future

contract [C01]

Deactivate MP [T14]

Message from

grid owner [T08]

Restore wrongly

removed [T22]

create

future

contract

[T28]

Create future

contract [T01]

Create future

contract [T02]

[now] >= start date [T24]

[now] > deleted date + specified archive period

Create active contract of Last Resort [T12]

New customer on

Last Resort [T27]

End active

contract [T07]

Set flag Last Resort,

[now] >= start date

[T25]

[now] > contract end date ||

set(contract cancellation date),

Move-out [T06]

Immediate change to new customer

selected supplier agreement [T04]

Remove physical MP [T13]

Create

active

contract

[T03]

[now] >= start date, New

agreement [T26]

Activate MP [T11]

Create future

contract [T29]

Activate MP [T10]

Cancel future

contract [C02]

Create new active

contract [T05]

• 2 (3) physical states

• 3 contractual states

• 10 aggregated states

• 31 state transformations

State model properties

Logical market process messages

• Process descriptions using "process components"

• "Process components" = logical message structures– per market party, with parameters

• 46 process components => 36 physical Elhub messages

• 133 combinations: Process components and parameters

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

Elhub model coverage and approach

Elhub functional area

Business processes

Metereddata

collection

Calc. & Aggreg.

Settlement & Reconcil.

Data storage

• Top-down approach– Required data for market

processes– Calculations

• What, why, and to which parties?

• Resulting information assets:1. Elhub base models2. Market entity state model3. Data exchange messages

Data exchange messages

• Message names follow ebIX standard with extended descriptive names• Messages are composed from two parts: Header and Payload

• Header define market party and process bindings, including– Document Type Description (UN/CEFACT and ebIX codes)– Business Process Description (ebIX codes only)

• Payload contain key data elements, structured into xml entites– 37 ebIX based entities used or adapted for national use (not final)

Example xml message: RequestStartOfSupply• Contents, e.g., type definitions and formats of

each message are currently being defined in more detail, based on ebIX base classes

• Definitions are being developed using SparxEnterprise Architect

<?xml version="1.0" encoding="UTF-8"?><rsm:RequestStartOfSupply xmlns:rsm="un:unece:260:data:EEM" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="un:unece:260:data:EEM elhub_RequestStartOfSupply.xsd">

<rsm:HeaderEnergyDocument><rsm:Identification>1234567890</rsm:Identification> <rsm:DocumentType listAgencyIdentifier="6">392</rsm:DocumentType><rsm:Creation>2014-02-19T09:30:47Z</rsm:Creation><rsm:SenderEnergyParty>

<rsm:Identification schemeAgencyIdentifier="9">9875673213456</rsm:Identification></rsm:SenderEnergyParty><rsm:RecipientEnergyParty>

<rsm:Identification schemeAgencyIdentifier="9">1223323131312</rsm:Identification></rsm:RecipientEnergyParty>

</rsm:HeaderEnergyDocument><rsm:ProcessEnergyContext>

<rsm:EnergyBusinessProcess listAgencyIdentifier="260">E03</rsm:EnergyBusinessProcess><rsm:EnergyBusinessProcessRole listAgencyIdentifier="6">DDQ</rsm:EnergyBusinessProcessRole><rsm:EnergyIndustryClassification>23</rsm:EnergyIndustryClassification>

</rsm:ProcessEnergyContext><rsm:PayloadMPEvent>

<rsm:StartOfOccurrence>2014-03-01T00:00:00Z</rsm:StartOfOccurrence><rsm:MeteringPointUsedDomainLocation>

<rsm:Identification schemeAgencyIdentifier="9">570987465325465781</rsm:Identification></rsm:MeteringPointUsedDomainLocation><rsm:BalanceResponsibleInvolvedEnergyParty>

<rsm:Identification schemeAgencyIdentifier="9">5983675234543</rsm:Identification></rsm:BalanceResponsibleInvolvedEnergyParty><rsm:BalanceSupplierInvolvedEnergyParty>

<rsm:Identification schemeAgencyIdentifier="9">3456775654441</rsm:Identification></rsm:BalanceSupplierInvolvedEnergyParty>

</rsm:PayloadMPEvent></rsm:RequestStartOfSupply>

CIM-ebIX harmonisation

• Levels of harmonization:

– Market framework (legal and regulatory)

– Market models and -entity states

– Overall processes and sequences

class Information Model Master Data

DSO

Balance Supplier

Bitemporal object

Party connected to

Grid

Grid Access

Prov ider

Balance

Responsible Party

Multi-Domain Base

Market Party

Multi-Domain Base

Address

Bitemporal object

Security Object

Grid AccessContract

Bitemporal object

Security Object

Balance Supply Contract

Security Object

Consumer Personal

Data

Name: Information Model Master Data

Author: perber

Version: 1.0

Created: 15.01.2014 12:43:04

Updated: 16.05.2014 13:57:28

Multi-Domain Base

Taxation Profile

Bitemporal object

Balance Suppliers and

Responsible Parties

activ e in Grid Area

Multi-Domain Base

Domains::Metering

Point

Domains::

Exchange Point

Bitemporal object

Domains::Metering

Grid Area

Domains::

Accounting Point

Postal address

Metering Point

address

Multi-Domain Base

Domains::Market

Balance Area

Security Model::

Third party

Balance Supplier

of Last Resort

Communication

Metered Data

Responsible

connecting

is allowed to act as

balance supplier

through

provides services to

balance supplier through

Belongs to

is located at

0..*references

references references

0..*

points

invoicing to

1 operates and

aggregates data

within

May be

connected to

is related to

governs balance supply to

May be

connected to

contains

is collecting

data for

1..*

acting in

1..*

is used for invoicing of

1

is a contract

with

is a contract

with parties

related to

0..*

use as

contact

0..1

1

is responsible contact for

0..*

is governing access to

must refer to a valid

stm Total MP state diagram

No contract

Future contract

Active contract Active MPDeleted MP Inactive MP

Name: Total MP state diagram

Author: perber

Version: 1.0

Created: 21.01.2014 10:53:21

Updated: 28.04.2014 15:00:23Decision to establish Metering Point (MP)

MP agg.2

Inactive without

contract

(Inaktivt u/avtale)

MP agg.3

Inactive, future

contract

(Inaktivt, fremtidig

avtale)

MP agg.4

Inactive w/contract

(Inaktivt m/avtale)

MP agg.5

Active without

contract

(Aktivt uten avtale)

MP agg.6

Active, future

contract

(Aktivt, fremtidig

avtale)

MP agg.7

Active w/contract

(Aktivt med avtale)

MP agg.8

Active, Last Resort

(Aktivt, lev.plikt)

ExitPoint

MP agg.9

Removed

(Deaktivert)

MP agg.10

Active, Supplier

change

(Aktivt,

Leverandørbytte)

Creating active contracts and/or activating contracts will have a configurable

dependence on the presence of metered values for the metering point. This

configuration will differ for registering future contracts and activating contracts.

[now] > contract end date ||

set(contract cancellation date),

Move-out [T18]

Reversed end

date [T21]

Activate MP [T09]

Reversed

move-out

[T20]

[now] >= start date [T23]

Reversed MP activation [T16]

Move-out [T17]

Deactivate MP with

future contract [T15]

[now] > contract end date ||

set(contract cancellation date)

[T19]

Cancel future

contract [C01]

Deactivate MP [T14]

Message from

grid owner [T08]

Restore wrongly

removed [T22]

create

future

contract

[T28]

Create future

contract [T01]

Create future

contract [T02]

[now] >= start date [T24]

[now] > deleted date + specified archive period

Create active contract of Last Resort [T12]

New customer on

Last Resort [T27]

End active

contract [T07]

Set flag Last Resort,

[now] >= start date

[T25]

[now] > contract end date ||

set(contract cancellation date),

Move-out [T06]

Immediate change to new customer

selected supplier agreement [T04]

Remove physical MP [T13]

Create

active

contract

[T03]

[now] >= start date, New

agreement [T26]

Activate MP [T11]

Create future

contract [T29]

Activate MP [T10]

Cancel future

contract [C02]

Create new active

contract [T05]

Key model development considerations

Market structure

Privacy and security

Processes & calculations

Message content

Standards

Performance

Regulatory

Market

Questions?

Per Øyvind Berg-KnutsenArchitect, Elhub project / Principal at Devoteam Consulting

(per.oyvind.berg.knutsen@devoteam.com)