European forum for energy Business Information eXchange Minutes, CuS Meeting, February 6th and 7th, 2006 CuS, Structuring of the energy market, phase V March 10 th , 2006 Corrected minutes – CuS project meeting, February 6 th and 7 th , 2006 Date: Monday February 6 th and Tuesday February 7 th , 2006 Time: 10:00 – 18:00, 9:00 – 16:00 Place: Electrabel, Brussels Participants: Eva Lepperhoff, RWE, DE Hugo Dekeyser (Convenor), UMIX, BE Jesper Grona Larsen, Devoteam, DK Kees Sparreboom, TenneT, NL Leif Morland, AtosOrigin, NO Margit Reiter, Energie Ag, AT Ove Nesvik (Secretary), EdiSys, NO Enclosure: 20060206 UTILMD.xls (German overview of usage of UTILMD) Corrections: Eurelectric will be added to the CuS mailing list for information only, and not as member. 1) Approval of agenda Approved with the following additions: DMRs from Sweden, AOB Contact with EURELECTRIC, AOB Progress of modelling techniques, AOB 2) Minutes from previous meeting Approved with the following addition: Comment from Kees: The bullet points under paragraph 3.1 in the minutes were the result of the discussions and are the start of the modelling of the structuring package within the ebIX domain model. 3) CuS working group & SAP A mail from SAP can be found in Appendix A, CuS working group & SAP. ebIX/CUS Page: 1
Transcript
European forum for energyBusiness Information eXchange
Minutes, CuS Meeting, February 6th and 7th, 2006
CuS, Structuring of the energy market, phase V March 10th, 2006
Corrected minutes – CuS project meeting, February 6th and 7th, 2006
Date: Monday February 6th and Tuesday February 7th, 2006 Time: 10:00 – 18:00, 9:00 – 16:00Place: Electrabel, BrusselsParticipants: Eva Lepperhoff, RWE, DE
Hugo Dekeyser (Convenor), UMIX, BEJesper Grona Larsen, Devoteam, DKKees Sparreboom, TenneT, NLLeif Morland, AtosOrigin, NOMargit Reiter, Energie Ag, ATOve Nesvik (Secretary), EdiSys, NO
Enclosure: 20060206 UTILMD.xls (German overview of usage of UTILMD)
Corrections: Eurelectric will be added to the CuS mailing list for information only, and not as member.
1) Approval of agendaApproved with the following additions: DMRs from Sweden, AOB Contact with EURELECTRIC, AOB Progress of modelling techniques, AOB
2) Minutes from previous meetingApproved with the following addition: Comment from Kees: The bullet points under paragraph 3.1 in the minutes were the result of the discussions
and are the start of the modelling of the structuring package within the ebIX domain model.
3) CuS working group & SAPA mail from SAP can be found in Appendix A, CuS working group & SAP.
Kees informed that SAP participated on the latest EMD meeting as an observer and, for the time being, SAP will continue this participation. There is an ongoing discussion related to creation of a vender group within ebIX, if more vendors want to participate, which in turn may find two (?) representatives (or observers) for the working groups.
The mail and proposal from SAP was discussed, and the proposal of having a vendor group with up to two members/observers in CuS was seen as a good solution.
The SAP model attached with the agenda was briefly discussed and it showed that SAP is in line with the ebIX CuS models. ebIX want to be a reliable partner but does not have the means to give “free consultancy”. It is therefore impossible for CuS to discuss every individual model from vendors and countries. Hugo will ask Konstantin of advice on how to invite/cooperate with SAP and other possible vendors.
ebIX/CUS Page: 1
Information from after the meeting (response from Konstantin):“Dear Hugo,
if SAP is interested in participating in CuS as well, I have no objections against inviting them with preliminary guest status. Given your latest discussion, I am even more convinced that we should try a change of the ebIX Articles to form such a vendor group, but that decision must wait until the April Forum meeting.
Sincerely,
Konstantin Staschus, Ph. D.”
4) Use Cases
4.1) Proposed Use Cases from Germany The homework from Eva, Appendix C and the attachment “20060206 UTILMD.xls”, was reviewed and the following comments made: The third parties used in the German documents are outside of the scope of the models from the CuS group
and the Role model. However the third parties have to be handled by the ebIX standards in some way. Probably the best is making an “exchange recommendation” from ETC.
The use of aggregated MPs should be reviewed by the countries using it. There may be several problems using it, e.g. a customer may have many MPs in many Metering Grid areas, a Customer may want to change Balance supplier for only some of these MPs, you may get different tax rates for different “colour” of the energy etc. A simpler way of doing it may be to add a customer id to the MPs instead of the using the aggregated MP.
The “Physical work for temperature dependent Meter” means “Energy needed (in kWh) to increase (or decrease) the temperature with 1 oC for a MP”.
Request to EMD:CuS asks for definitions/explanations of the following Settlement methods: non profiled profiled temperature depended profiled group of temperature depended profiled Metering points
Request to ETC:CuS will ask ETC to making an agenda item for a discussion related to “Control Area”, “Balance Group Number“, “Sub-Balance Group Number”, “Subgroup Number” within Germany (Carl Major).
Homework: Eva will make a description on how local MPs are aggregated into aggregated MPs. Eva will verify if “Net Reserve Power” can be renamed to “Ordered reserve grid transport (or connection)
capacity” or something similar. Eva will verify if the “Physical work for temperature dependent Meter” really is used. Eva will find a better name for “Type of Installation” (i.e. what kind of “type” it is).
4.2) Presentation of a Norwegian process for creation of MPs, Leif
ebIX/CuS Page: 2
A document describing a message exchange for creation, changes and end of MPs, distributed before the previous meeting, was presented by Leif. The document describes 6 messages:
a) New Installation. This is used when an Installation not is known earlier, and one ore more Metering buses are being established. A work order is produced in the CIS system: Metering setup for passive metering bus. The message is first sent from the installation company to the grid asking for a new MP, included a series of attributes. The message is returned from the Grid including new attributes, such as the Metering point id.
b) New Metering bus. This message is used when one or more metering buses are to be set up on an existing Installation (changes or additions to an existing Installation). A work order is produced in the CIS system: Metering setup for passive metering bus.
c) Temporary Installation. Same as a) except that the installation is temporary.d) Change of ”peak voltage fuse” or ”main fuse”.e) Work done on the Metering point. Work done to change meter, transformer etc. May trigger a Change of
meter message by Ediel.f) Change of usage. Other changes to the Metering bus or Installation.
To the participants knowledge this kind of message exchange is only used in Norway. CuS will for the time being not do anything more with the item.
4.3) National rules and values for Connection statusThe Swedish information was reviewed, see Appendix E. No changes were done to the list of connection statuses from previous meeting.
4.4) Continuation of making descriptions of the CuS UseCases
Pre-switch checking processMargit presented a sequence diagram explaining the Austrian Pre-switch checking; see Appendix B, Homework from Austria. It was noted that Austrians allow for sending the 392 equivalent message without a Metering point id.
Switch of BRPThe process of switching BRP was discussed and a first UML collaboration diagram was made as an effort to clarify (and not as the final model).
Change MDRThe process of switching MDR was discussed and a first UML UseCase and collaboration diagram was made, see…
Switch of Balance group (BG)Also the process of switching BG was discussed and a first UML collaboration diagram was made.
On the next meeting CuS will continue with the following processes: Change Meter Bulk switch Creation of MPs
ebIX/CuS Page: 3
Deletion of MPs Change Connection status Change Metering method Change of Grid services contract Distribute Master Data Billing/Contract Distribute Master Data Installation Address Distribute Master Data Balance area Distribute Master Data Procedure allocation. Distribute Master Data Measuring Distribute Master Data Payment Agreement
Homework:Ove will add the artefacts and descriptions made during this meeting and the previous two meetings into a word document as a basis for the work in the coming meetings.
5) Work itemsDue to lack of time the item was postponed.
6) Meeting scheduleMarch, 30th and 31st 2006, start at 09:00, Linz - Note new dateApril, 26th and 27th 2006, start at 09:00, OsloMay, 31st and June 1st, start at 09:00, Düsseldorf
7) AOB
DMRs from SwedenA set with DMRs has been received from Sweden. ebIX/EMD took care of DMR 3, ebIX CuS will take care of DMR 2 and the rest is for ebIX ETC.
Due to lack of time the item was postponed.
Contact with EURELECTRICEURELECTRIC and ebIX are in the process of establishing a MoU on their respective work and responsibilities.Related to these MoU discussions Edith Hofer from Eurelectric ([email protected]) will be added to the mailing list for CuS for information purposes and be invited for the next CuS meeting.
Progress of modelling techniques:The chairman (Hugo) sent during the meeting a mail to the chairman of ETC (Jon-Egil), asking ETC to make progress with the modelling principles to use.
-----Original Message-----From: Knust, HaraldTo: [email protected] Cc: [email protected] Sent: 30/01/06 17:44Subject: CuS working group & SAP
Dear Hugo,As discussed in St. Ullrich, I would like to summarize the intentions of SAP in regards to the next steps of a generic customer switch solution.
The Position Paper we've recently issued intends to set the basis for discussing the topic of Change of Supplier. It is not implying in any way how an extended future solution of SAP's current offering for the supplier switch could look like.
We have already started a project to continue with the next steps, which includes a detailed process and activity modelling with the goal of identifying the generic 'building blocks' of a common European change of supplier. In contrast with the statement in the position paper we intend to include all 'related processes' like move-in, move-out, end of supply as well.
It was very encouraging to hear from you that the CuS working group at ebIX has already invested much time and work into the same topic with similar goals. Your published document from June 2004 already provided interesting insight into your work. I believe that it will be very beneficial for both ebIX and SAP if we could cooperate on this topic in one way or the other.
My understanding is that the newest version of the CuS document is likely to be published on the ebIX website in April and then everybody has access to it. So what would be the benefit of a cooperation?
ebIX: verification and additional input. By having industry experts from SAP reading your document, you will
receive competent feedback, even before publication. acceptance. In case SAP will base it's new generic customer switch solution entirely or partly on the ebIX
model, ebIX will receive a higher recognition 'in the regulator circles'. I write this without the intention of being arrogant, it's just the side effect of being the market leader in the European utilities industry. I understand that there are political concerns about favoring one software vendor. SAP does not expect to be favored, it just seems that SAP is currently the only software vendor who is taking responsibility of the investment of it's customers and actively participating in workshops about the liberalized European market.
SAP: timing. A publication in April is quite late for our own release planning and we would therefore benefit
having access to a pre-version. cost. Based on my short discussions with you and Kees the working group has already defined the generic
building blocks, which would help SAP avoiding to do the same investigation again.
I would very much appreciate a positive response from you and the CuS working group. In case of a general agreement of a closer relationship with SAP, we shall get in contact again and discuss how such an engagement could look like.
Business Development SAP for UtilitiesSAP AGDietmar-Hopp-Allee 1669190 WalldorfT +49/6227/7-47685F +49/6227/78-00131M +49/160/8896589E [email protected]://www.sap.com/utilities
Notification of no change only if BS new does not overrule the objection. This message terminates change process (8 and 9 are omitted)
If Metering Point not uniquely identified or authorisation invalid
Transactions number
transaction from to
3 0101 Request for change for a list of “customer” BS new MPA/DSO4 0302 Request for improvement data quality if Metering point is not
uniquely identified MPA/DSO BS new
5 0103 Request for change for a list of “customer” (improved data and/or new customer)
BS new MPA/DSO
6 0304 Notification of request for change, only uniquely identified MP for a certain date of change
MPA/DSO BS old
6 0305 Notification of request for change, only uniquely identified MP for a certain date of change
MPA/DSO BS new
6 0312 Notification: no change MPA/DSO BS new11 0307 Forecast date MPA/DSO BS new13 0308 Billing data (Consumption) MPA/DSO BS old
7 0240 Objection BS old MPA/DSO8 0341 Notification Objection MPA/DSO BS new9 0142 Overrule Objection (change confirmed) BS new MPA/DSO10 0350 Notification: no change MPA/DSO BS new10 0351 Notification: no change MPA/DSO BS old9a 0353 Notification of change MPA/DSO BS old
0206 Order for reading the meter data (optional) BS old MPA/DSO0160 Cancellation BS new MPA/DSO0360 Cancellation MPA/DSO BS new
ebIX/CuS Page: 8
APPENDIX C HOMEWORK FROM GERMANY
Some corrections from the last meeting:The concession fee is paid by used kWh / Net voltage per MP. The concession fee might be decreased per Metering point e.g. a big company might get a discount because the commune wants to keep the jobs in town. Only the commune is allowed to do it, no one else! The maximum concession fee is disclosed every year by the government.
Beistellung: Means a supplier places a full service contract with a customer. Than the supplier places a service contract with the Supplier and Grid Access Provider of this Area. In our Example the RWE has a full service contract with me and because I’m living in Düsseldorf the RWE places a service contract with the Düsseldorfer Stadtwerke. If I got a Problem with my meter, I will call the RWE, but the repairing will be done by the grid owner = Düsseldorfer Stadtwerke, also the Meter Reading and so on. But normally the RWE will have a Grid Contract with the Düsseldorfer Stadtwerke and will supply me by themselves.
In Germany we got a law that prohibits the disconnection of special services e.g. hospital, military, police and old people’s home.
ebIX/CuS Page: 9
APPENDIX D HOMEWORK FROM NORWAY (LEIF)
Trigger based data alignmentOne of my homework's was to describe what "trigger based data alignment" is. I think this is more a matter of definition. For me this is the same as normal "master data update" and "request for master data update".
The triggers for a "trigger based data alignment" could be;
On the sender's side:
o Changes in master data outside of expected intervals/eventso Corrections in the master data
On the receiver side:
o Missing master datao Inconsistency between received data elementso Errors in received data.
If this is covered by the "master data update" and "request for master data update", we can concentrate on these processes.
ebIX/CuS Page: 10
APPENDIX E INFORMATION RELATED TO CONNECTION STATUS FROM SWEDEN
The following are received from Sweden:
Connection statusFrom 20061001 the Grid company has to send a message to the Balance supplier when he disconnect a Metering point and also a new message when he connect the Metering point again. The two messages are PRODAT//Z06H and PRODAT/Z04T. These messages will probably also be followed by meter readings. This new way of doing it is done so that the Balance supplier doesn’t have to send a preliminary bill to the customer which can cause problem. If the Balance supplier want to disconnect the MP it still has to be done manually because of the rules of written request and that it has to be served to the customer etc.
At the same time we also will introduce a special message if the supplier wants to "close" the delivery to the Metering point, which is possible only when the customer commit an essential breach of a contract. Today we don’t have any message for this, but it will indirect be showed by the readings when we send a meter reading when we disconnect and one meter reading when we connect the Metering point again, but in this case the Balance supplier don’t know about the disconnection before the MP is connected again.
First priority:Item StatusA) Class diagram for Metering point master data DoneB) Change of other roles than Balance supplier connected to a Metering point December 2005C) Addition of Balance Group id to the switch messages Waiting for
updated role model
D) Change of attributes connected to a Metering point. December 2005E) Summer 'Review process' Ongoing F) Presentation of the model: Training and HTML. December 2005
(Hugo)G) Making a “Market view” of the CuS model, presented in the introduction of the
CuS business information model, seen from the customer point of view. This should include the Consumer and his/hers interface to the Metered data collector, the Grid access provider and the Balance supplier).
Postponed until 2006 (Leif)
H) Efficient data alignment: Done monthly in Germany (UTILMD). Done on request as .csv or Excel in
Austria, Denmark (may be UTILMD), Norway and Sweden. In the Netherlands request/response messages (UTILMD/UTILTS) are exchanged when needed.
Include alignment of master data, such as MP master data, e.g. as periodical master data report from MPA
Does not include pre-switch checking Exchange of metered data can be seen as a sort of data alignment Data alignment is a periodic comparison data.
December 2005 Kees will present EAN principles from retail December 2005 and Leif will describe the alignment problems as he sees it.
I) Efficient pre-switch checking and verification of contractual matters between the new and the old (current) Balance suppler Currently done as UTILMD messages in Germany. Under discussion as WEB based services in Denmark and Norway. Metering point ids, address and postcode is available in centralised systems in
the Netherlands and Belgium (meant for data alignment and not pre-switch checking). In the Netherlands also request/response messages (UTILMD/UTILTS) are exchanged for pre-switch checking.
J) Bulk switch May be change of all customers belonging to one BS (e.g. related to bankruptcy)
or a switch of all MPs related to one customer (petrol stations, banks etc). Currently done in the Netherlands (for all customers belonging to one BS) with a
manual trigger of the process (manual handling of the 392 information), but using normal messages for the confirmations/notifications (both to BS and BRP).
Denmark and Germany are discussing switch of all MPs related to one customer using one virtual/aggregated MP id.
K) Change to/from Supplier of last resort Exist in Norway, Germany and Belgium. Does not exist in Austria, Sweden, Netherlands and Denmark. A Balance supplier appointed by the authorities (e.g. the regulator) to supply
ebIX/CuS Page: 16
energy under certain conditions to consumers rejected by other Balance suppliers.L) Change to/from Default supplier Does not exist in Austria, Norway, Netherlands and Belgium. Exist in Sweden, Germany and Denmark. A Balance supplier that supplies MPs within a Metering Grid Area (chosen by the
MPA) when the customer has not chosen another BS.
In addition there will always be a “Loss supplier” responsible for the grid-loss. M) Creating and deleting metering points An automated process has been “tested” in Denmark. It is difficult to let the BS
create a MP, since he needs a MP-id, which not is available until the MP is created in the MPA database.
The process of creating a MP may include the need for a new role; “Electrical Installation company”.
N) Change request and exchange of master data to other databases, such as parties and contracts.
O) Class diagram for Installation information (inclusive "premise id" and "location id") and Exchange of master data for "Measuring field". This may require a recast of UTILMD.
