Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future...

31
Grid Usage Billing based on Aggregated Consumption: A simplified Procedure for Distribution Companies in Liberalized Markets Roll Out IBU Utilities 9.10.2010

Transcript of Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future...

Page 1: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

Grid Usage Billing based on

Aggregated Consumption:

A simplified Procedure for

Distribution Companies in

Liberalized Markets

Roll Out

IBU Utilities9.10.2010

Page 2: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 2

Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document or any related presentation about SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Page 3: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 3

1. Introduction & Motivation

2. Process Steps

3. Data Model

4. Summary and Outlook

5. Appendix

Agenda

Page 4: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 4

Grid Usage Billing – Distribution Company View

Grid Usage bills can be sent to various recipients.

Grid Usage bills can be based on different data.

Bill ReceptionBill Creation

End

CustomerGrid Access Provider

Metering Point Administrator

Billing Agent

DSO

Retailer

Billing Agent

Page 5: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 5

Country Observations on Grid Usage Bills

Legal Invoice per PoD Legal Invoice per Retailer

Consumption based The DSO sends for each point of delivery a bill to the retailer

Tax statement on Retail level

Calculation details on PoD level

Calculation on aggregated consumption per PoD group

Capacity based (Fixed charges only) Billing details on PoD level

Calculation on aggregated number of PoDs per capacity class

(S)

A D

B

F

IRL

P

SK

NL

GB

NL

2009

NL2012(?)

Page 6: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 6

Motivation for an alternative Procedure

Exchanging information on PoD level means a high volume of data

Managing consumer bills on individual contract accounts is over-fulfilling the task

when bills on retail level are required

Complaints processing on PoD-level-bills is a cumbersome process

Page 7: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 7

Motivation for a simplified Procedure

Two ways – one result

GRID USAGE INVOICE

x y zMany Consumptions

Many Grid Usage Bills

Aggregate per Supplier

Many Consumptions

Aggregate per Supplier

One Grid Usage Bill

Page 8: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 8

1. Introduction & Motivation

2. Process Steps

3. Data Model

4. Summary and Outlook

5. Appendix

Agenda

Page 9: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 9

Grid Usage Billing

based on Aggregated Consumption

Distributor

SAP for Utilities

Aggregated

Consumption Profiles

Number of

Points of Delivery

Electronic Invoices

Supplier

SAP for Utilities

1

2

3

4

Meter ReadingUpdate Usage Factors

Aggregate the Usage Factors to Consumption Profiles per Supplier

Perform RTP-Billing & Invoicing

Send Electronic Invoices

Page 10: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 10

1st

step:

Update Usage Factors

Whenever meter readings are estimated, uploaded, deleted or corrected thecorresponding usage factor needs to be adjusted. This can be done byimplementing the function EXIT_SAPLELSV_001.

Update Usage FactorActual

readingresult

CalculatedHistoric UsageFactor

Extra-polatedUsageFactor

Page 11: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 11

2nd

step:

Aggregate the Usage Factors per Supplier

Selection of PoDs of the Grid Usage Settlement Unit Synthetical load profiles are multiplied by individual usage factors of

customers and are aggregated

Points of Delivery are counted

Results:1. Aggregated load profile of non-interval customers within settlement unit2. Load profile with number of PoDs of the settlement unit per interval These profiles are sent to the supplier for information and validation

purposes

+

Page 12: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 12

3rd

step:

Perform RTP-Billing & Invoicing

Off-peakcons.

kWh = 275

Resultparameter

Result function

Result function

Off-peak On-peak Off-peak On-peak Off-peak

Resultprofile off-peak

Resultprofile on-peak

Profile withaggregatedconsumption

On-peak On-peak

Off-peak Off-peak Off-peak

Resultparameter

On-peakkWh = 500

Virtual profile

Virtual profile

The pre-aggregated consumption values (time series) and the numbers of PoDs (time series) are evaluated with regard to on-peak consumption, off-peak consumption and the average

number of PoDs. These values are billed and the billing document is invoiced.

Page 13: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 13

SupplierElectronic

Data Exchange

Communicates consumption values, measurement values, …

Communicates changes to customer data, …

Distributor Supplier

4th

step:

Send Electronic Invoices

GRID USAGE INVOICE

x y z

The Grid Usage Invoice is sent to the Supplier

by Electronic Data Exchange

Page 14: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 14

1. Introduction & Motivation

2. Process Steps

3. Data Model & System Preparation

4. Summary and Outlook

5. Appendix

Agenda

Page 15: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 15

Residential Customers – Data Model

For each consumer and his related installation an assignment to a customer group is performed using synthetic load profiles.

The usage factors for load profiles are updated whenever consumption data are calculated.

There exist usage factors for past periods and forecasted usage factors for future periods.

Settlement

unit

Installation

[Grid]

Device Register

Synth.

ProfileConsumption

Synth.

ProfileForecast

Contract

[Grid]

Contract

account

Business

partner

Service

[Settlement]

Service

[Delivery]

Point of

Delivery

(POD)

Page 16: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 16

Supplier – Settlement View

A settlement unit is needed for each supplier the distributor wants to create a grid usage bill for.

This settlement unit groups all points of delivery of the customers of this supplier.

non-interval

customers

Settlement

coordinator

Supplier Distributor

(Optional)

PoD

Supplier_PoD

Settlement

unit

Device Info

Record

Register

Page 17: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 17

Supplier – Billing View

For each supplier that the distributor wants to bill a complete IS-U data construct needs to exist.

The installation refers to a RTP interface allowing the billing of profile data which are assigned to the corresponding register.

Contract

[grid usage]

Contract

account

Business

Partner

Supplier

PoD

Supplier_PoDInstallation

Device Info

RecordRegister

non-interval

customers

Page 18: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 18

System Preparation

Data Collection

A new settlement process has to be defined. This includes new settlement parameters and settlement steps for aggregating consumptions (usage factors) counting points of delivery sending the results to the BS

Grid Usage Billing

In order to process pre-aggregated consumption data and number of PoDs a new RTP Interface has to be defined. This includes the definition of a new formula and a new result function.

Rate

In order to use the RTP interface within billing, new rates have to be defined that are based on the output parameters of the RTP interface.

Usage factor

In order to update the usage factors as soon as meter reading data (consumption data) are changed, an exit function has to be enhanced.

Page 19: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 19

1. Introduction & Motivation

2. Process Steps

3. Data Model

4. Summary and Outlook

5. Appendix

Agenda

Page 20: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 20

Summary and Outlook

The procedure presented here is easy to implement

It reduces data traffic significantly

It does not need individual bills nor individual invoices

It does not need individual (costumer) contract accounting and…

It leads to the same financial result!

It reduces the TCO

Page 21: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 21

1. Introduction & Motivation

2. Process Steps

3. Data Model

4. Summary and Outlook

5. Appendix

Process Steps on Supplier Side

Suggestion for a Customer Invoice Layout

Correction Process on Distributor Side

Results of Country Observations

Agenda

Page 22: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 22

Grid Usage Billing on Supplier Side

Process Steps

Supplier

SAP for Utilities

Aggregated

Consumption Profiles

Number of

Points of Delivery

Electronic Invoices

Distributor

SAP for Utilities

3

4

1Measurement ValuesUpdate Usage Factors

2Aggregate the Usage Factors toConsumption Profiles per DSO

Check received Profiles against self-aggregated Profiles

Perform simulation of RTP-Billing & Invoicing

Measurement Values

5Check received Invoices against simulated Invoices

Page 23: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 23

Layout for Customer Invoice

An example for a good costumer invoice layout can be found here.This invoice does not use calculated network amounts – it shows the prices per kWh.

Page 24: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 24

Correction Process on Distributor Side

01.01.09 ............................................01.02.09...........15.02.09.................................01.03.09............10.03.09…..............................01.04.09……….

UF1 1.8 (Extrapolated)UF2 2.5 (Extrapolated)UF3 5.8 (Extrapolated)

1

Billing2

Aggr. Consumption Result

Read Meter 13UF1 1.9 (Calculated)

UF1 2.0 (Extrapolated)

UF2 2.5 (Extrapolated)UF3 5.8 (Extrapolated)

Billing4

Aggr. Consumption Result

Aggr. Consumption Result

Correct Meter Reading 1

5

UF1 2.0 (Calculated)

UF1 2.1 (Extrapolated)

UF2 2.7 (Extrapolated)UF3 5.8 (Extrapolated)

Billing6

Aggr. Consumption Result

Aggr. Consumption Result

Aggr. Consumption Result

Page 25: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 25

1. Introduction & Motivation

2. Process Steps

3. Data Model

4. Summary and Outlook

5. Appendix

Process Steps on Supplier Side

Suggestion for a Customer Invoice Layout

Correction Process on Distributor Side

Results of Country Observations

Agenda

Page 26: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 26

Outlined Activities:

Grid Usage Billing Process

Continuously develop German Grid Usage Billing Process

2000 2005 2010 2015

Continuously develop Grid Usage Billing Processes of other European Countries

Observe Grid Usage Process of European Countries

Expect Simplifications of Grid Usage Billing Process

Page 27: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 27

Analyzed countries

Invoice on

PoD level

Invoice on

Retail level

Invoice

attachments

Data

Volume

Calculation

basis

Prepayments/

Budget Bills

Process

Complexity

Austria X High Consumption Medium

Belgium X X High Consumption Yes High

Croatia Not yetdefined

Not yet defined

Not yet defined

Not yet defined

Not yet defined

Not yet defined Not yet defined

Czech Republic

X ? ? ? ? ? ?

France X X High Consumption High

Germany X X Very High Consumption Yes Very High

Great Britain X Medium Aggregated consumption

No Low

Ireland X X High Consumption High

Italy X X High Consumption No High

Netherlands X (X) Low Connection capacity

No Low

Portugal X X High Consumption High

Slovakia X ? ? Consumption Yes ?

Spain X ? ? ? ? ? ?

Sweden X High Consumption Medium

Switzerland Not yetdefined

Not yetdefined

Not yet defined

Not yetdefined

Not yet defined

Not yet defined Not yet defined

Page 28: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 28

Country Sheet: Germany

Grid Usage Billing Process: Single Grid usage bills are created and communicated on PoD level and consumer account Aggregated grid usage bills are created on retailer account Incoming payments are firstly assigned to retailer account and then distributed to consumer

accounts Budget billing procedures are used Complaint processing on PoD level

Evaluation: High data volume at the edge of technical possibilities Complex reconciliation processes between consumer and retailer accounts Complaint processing on PoD level and therefore complaints on “low amount” bills

High operational costs due to complex processes and high data volume

Page 29: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 29

Country Sheet: Great Britain

Grid Usage Billing Process: Aggregated consumption time series are sent from an independent market party to the

distributor and the retailer on a daily basis Grid usage bill is created monthly on retailer level Grid usage bill refers to aggregated consumption Grid usage bill is sent in paper format

Evaluation: Medium data volume due to handling of aggregated measurement values Bilateral complaint processes on the same data basis (aggregated consumption data) Corrections are always included as overall amounts within the follow-up bill

Medium operational costs due to robust processes and medium data volume

Page 30: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

© SAP AG 2009. All rights reserved. / Page 30

Country Sheet: Netherlands

Grid Usage Billing Process: Grid usage bill is created monthly on retailer level Grid usage bill refers to number of metering points and respective connection capacity (fixed

prices per connection capacity class) Grid usage bill is sent in paper format

Evaluation: Low data volume Bilateral complaint processes on the same data basis (number of PoDs within a connection

capacity class)

Low operational costs due to robust processes and low data volume

Page 31: Grid Usage Billing based on Aggregated Consumption · SAP’s strategy and possible future developments, directions, and functionality of products and/or platforms, are all subject

Thank you