Minutes ETC meeting April 8th, 2003

Date:	Tuesday, April 8th, 2003
Time:		9:30 – 18:00
Place:	Electrabel, Brugge 
Participants:	Carl Major, E-on Netz, Germany
Christian Odgaard, Eltra, Denmark
Erik Hartwell, Eltra, Denmark
Eva Appelqvist, SvK, Sweden
Hugo Dekeyser, Electrabel, Belgium
Jon-Egil Nordvik, Statnett (Convenor), Norway
Kees Sparreboom, TenneT, the Netherlands
Ove Nesvik, ebIX (secretary), Norway
Rolf-Dieter Kasper, VDEW (rwenet), Germany
Terje Nilsen, Nord Pool, Norway
Written by:	Ove Nesvik
To:	Participants
ETC
Attachment:	Power point presentation from Kees

1)	Approval of agenda
Approved with the following additions to AOB:
A)	How to send percentages – is 3 percent sent as 3 or 0,03?
B)	Proposal for handling of errors and updates
C)	From CuS, How to update master data when deleting previous sent information in optional elements
D)	Communication, encryption

2)	Minutes from previous meeting
Approved with a comment to item 4, ebIX are doing more than just downstream exchanges, i.e. are concerned about the whole industry, both upstream and downstream.

3)	Election of convenor for ETC
Jon-Egil Nordvik from Statnett was elected – Congratulation!

4)	Information
TF-14
•	Implementation of ESS is ongoing in 4 countries. There is however some problems with transit through Germany. A new version is being planned.
•	Two new project proposals have been discussed in the ETSO steering group. 
o	Ancillary services project (only modelling in the first phase). Postponed for about ½ year. 
o	Settlement project. Postponed to the next ETSO steering group meeting. 

5)	ETC methodology
The methodology document will guide the working groups in their work and will define partly the work to be done by the ETC.

Kees presented some slides describing the principles for CC, Blueprints etc.

Erik presented a model from the Danish routing document.

One of the input documents to the ETC methodology will be the ETSO methodology. When modelling principles are taken from the ETSO methodology the text should be copied from the ETSO document (not only referenced). Copied text will be marked as copied from the ETSO methodology.

The ebIX models should always reflect the core business need for a majority of the participating countries. If an item only is used by one country it should not be a part of the basic model, but kept in an overall model for possible future implementation. 

The basic principles for using UML will be:
1.	An interested party requests a new process to be modelled. This party bring in the functional requirements, procedures etc + in addition the ETC Methodology, rules etc shall be available.
---
2.	UseCase diagrams – made mainly by national user groups and ebIX project groups.
3.	Sequence diagrams - made mainly by national user groups and ebIX project groups.
---
4.	Activity diagrams - made mainly by technical groups (ebIX project groups).
5.	Class diagrams - made mainly by technical group (ebIX project groups).
---
6.	The artefacts will be checked by ETC.
---
7.	National implementations.

The first draft of the ETC methodology will be ready before the end of June 2003.

Homework:
Ove will make a first proposal for a methodology before the next meeting. The ETC methodology will include items from item 6 (see below) and the Danish routing document. 

6)	ETC work plan and review of the old EEEG activity list (see appendix A).

CC registry
•	The ebIX CC activities should be user driven, reusable, easy to maintain and fit into the overall UN/CEFACT CC specifications.
•	ETC will publish and approve CC from the working group.

Code lists registry
A code list registry is already available on www.ediel.org. The code list will be made syntax independent and maintenance will be continued. Rules for maintenance procedures and corrections CC will be a part of the ETC methodology.

Blueprint registry
A blueprint registry is postponed until the working groups have documented their needs.

Rules for the work of ETC
The rules for ETC will include such items as how to prepare items for the ETC meeting, what should a request include (priority, time limit, reference to CC, problem description, proposal for solution, etc).

A first draft for rules for ETC will be ready before the autumn 2003 ebIX meeting.

Review of the old EEEG activity list
Due to lack of time this item was postponed.

Identification of gases - Homework:
Kees will make a specification of the problem area “identification of gases” for the next meeting. The specification will be made according to the above-proposed rules (priority, time limit, reference to CC, problem description and proposal for solution).

7)	Preparation for next ebIX meeting, April 9th 
The work item list was reviewed. Dates were added for the methodology work item and the rules for ETC work item. The activity regarding EU funding was moved to ebIX Forum, see appendix B.

8)	Addressing / Internal routing
Erik presented the Danish routing document that among others include the following rules:
•	There shall only be one party id for each legal company.
•	There shall only be one communication address per party id and protocol. 
•	Authorised third parties may be addressed in UNB with their own party id and their own communication address (connected to the third party’s party id).
•	A party can use different third parties for different OBPI’s (Overall Business Process Id). 

The Swedish/Norwegian proposal covers the same principles as the Danish. This document will be enclosed to the minutes, for comments before next meeting. The document is made as a proposal for a new chapter in the functional description. 

Homework:
Everybody should read and make comments to the Swedish/Norwegian addressing proposal before the next meeting, see appendix D.

9)	Installation identification
The principle for identification of an installation was discussed. An installation is a sub-entity under a metering point, e.g. one windmill in a windmill park. Kees will look into the possibility to use meters and registers according to the current model to identify an installation.

10)	Description of the codes in UTILTS/SG11/STS/4405 
When to use the following codes in UTILTS/SG11/STS/4405:
Code:	Proposal from Hugo:
Adjusted 	Use this code for values adapted according to validation rules, either automatically or manually, before sending to the receiver (e.g. supplier)
Revised 	For correcting a previous sent meter reading or consumption value, interpreted as 'corrected'.

A short discussion resulted in homework for Kees and Ove.

Homework:
Kees and Ove will verify the origin of the codes – Further discussions on the next meeting

11)	Version numbering of Ediel IGs:
The following rules are implemented in “UNH/S009 0057” in UTILMD and UTILTS:
Use the code “EDIEL4” if the Ediel IG is implemented in its full version, or a code of the format “E4yyzz”if a national IG is the basis, where:
E4	Indicates Ediel version 4
yy 	ISO 2 letter country code or an abbreviation for an international organisation
zz 	user guide or national implementation guide version number

The version numbering will also be added to the MSCON, DELFOR, PRODAT and APERAK IG’s. 

Homework:
Ove will update the IGs for MSCON, DELFOR, PRODAT and APERAK.

12)	Ediel maintained code lists
Due to lack of time the item was postponed until next meeting

13)	New DMRs
The following DMRs will be sent to EEG1:
•	Request from Holland for a new  “Party function code qualifier in NAD/3035, “Transport capacity responsible party”
•	Request from Belgium for a new “Measurement unit code” (UN recommendation 20), “kWh/m3“(kilowatt-hour/cubic meter)”
•	Request from Germany for a new “Location function code qualifier” in LOC/3227, “Climate zone”.
•	Request from Germany for a new “Measurement unit code” (UN recommendation 20), “kWh/K (kilowatt-hour/Kelvin)”.

14)	MSCONS
Request from Norway for a new date format at detailed level (connected to meter stands) without hours and minutes – “102, CCYYMMDD”

Due to lack of time the item was postponed until next meeting

15)	Next meeting(s)
Date	Place	Agenda items	
3-4/6	Hannover	•	ETC Methodology
•	Technical questions	
26/6	Stockholm	•	Finalising first draft methodology
•	Rules for the ETC work
•	Kees will make a first draft for how to help new countries	
23/9	Oslo	•	Finalising first draft of Rules for the ETC work 	
7/10	Berlin (the day before ebIX meeting)		

16)	AOB

A)	How to send percentages – is 3 percent sent as 3 or 0,03?
If qualified as a percentage (P3) use 3, if qualified as a factor use 0.03. 

Homework:
Ove will update the functional description.

B)	Proposal for handling of errors and updates
Due to lack of time the item was postponed until next meeting

C)	From CuS, How to update master data when deleting previous sent information in optional elements
Due to lack of time the item was postponed until next meeting

D)	Communication, encryption
Due to lack of time the item was postponed until next meeting

Appendix A	
Participants in ETC (to be verified).

Name	Company	Telephone	Mobile	E-mail	
Carl Major	E.ON Netz	+49 5132 88 2179	+49 172 5109881	Carl.Major@eon-energie.com	
Christian Odgaard	Eltra	+45 76 22 44 63	+45 23 33 85 55	Christian.odgaard@eltra.dk 	
Eva Appelqvist	SvK			Eva.Appelqvist@svk.se 	
Hugo Dekeyser	Electrabel	+32 2 518 65 87	+32 4 77 5580 03	hugo.dekeyser@electrabel.be 	
Jon-Egil Nordvik (Convenor)	Statnett	+47 22 52 70 00	+47 975 36 303	jon-egil.nordvik@statnett.no 	
Kees Sparreboom	TenneT	+31 26 373 1405 (TenneT)
+31 30 689 6017 (Cap Gemini)	+31 622 66 7911	kees.sparreboom@cgey.nl	
Matti Vasara	Fingrid	+358 405 19 50 17		Matti.Vasara@fingrid.fi 	
Oscar Ludwigs	SvK	+46 8 739 7784	+46 70 539 7784	oscar.Ludwigs@svk.se	
Ove Nesvik (Secretary)	EdiSys	+47 22 42 13 80	+47 928 22 908	ove.nesvik@edisys.no	
Rolf-Dieter Kasper	RWE Net	+49 231 438 2465	+49 172 2311977	rolf.kasper@rwenet.com	

Appendix B	
Work items for ETC

Work item	Comments	Initiated	Status	
ETC methodology	Making a methodology defining how wg’s are supposed to work.

ETC will maintain a document with additions to the ETSO/ebIX methodology to be reviewed and approved by the ETSO/ebIX harmonisation group.	20030305	First draft planned available for the wg end of June 2003.	
CC registry	Maintenance of a list of CC used in the ebIX and TF-14 (?)	20030305		
Code lists registry	Maintenance of a list of codes used within ebIX and TF-14 (?)	20030305		
Blueprint registry	Maintenance of a set of predefined reusable elements to be used in developments of exchangeable documents and business processes. 

One blueprint may typically consist of several UML artefacts (e.g. activity and class diagrams). Examples of blueprints are the message header of a document, the time series part of a document or a generic acknowledgment process.	20030305		
Rules for the work of ETC	Making a document describing how ETC shall work including:
•	Time for handling questions to ETC
•	How to work (mail  meetings)
•	How to deal with technical implementation questions from participating countries
•	What items/questions shall be handles by ETC and what by the wg’s
•	How to help new countries in the start, e.g. finding “godfather(s)” responsible for helping new countries with practical/administrative questions.
•	Etc. 	20030305	First proposal planned before the autumn 2003 ebIX meeting 	

Appendix C	
Activity list from EEEG (to be discussed).

Item	Status	Responsible	Create date	
Make suggestions for project plans for acknowledgement projects:
1)	Harmonisation of acknowledgement principles and codes
2)	Technical implementation of APERAK/CONTRL	To be done before the next ebIX meeting in March 2003	All	20021203	
Make a position paper, explaining why Ediel wants to define the role in the sequence diagrams, and make separate message types for each message flow. 

Include a change proposal to the ETSO Methodology, chapter 5	Moved to the CoS project

A proposal will be sent to the harmonisation group	CoS

Ove	20021008

20021203	
Discussion and comments to the ETSO/Ediel methodology 	Moved to the CoS project

To be done	CoS

All	20021008

20021203	
Ediel news-group	To be discussed in ETC spring 2003	EEEG (ETC)	20011009	
MSCONS, removal of direction	Postponed until spring 2003	EEEG	20011009	
Verification of APERAK error codes		Kees	20020312	
New DMRs:
MKS/7293:	Garbage
TV Distribution
Water
PCD/5245:	Reliability percentage for aggregated data
QTY:	Adjusted planned quantity	

DMRs sent to EBES/EEG1

DMRs sent to EBES/TCG for review February 2003	All

Ove

Ove	20020619

20021125

20021202	
Finalising UTILTS version 4.0 based on the Dutch national IG version 1.0 and EDIFACT D.01C	To be done 

A RFC is planned sent out after December 13th 	Ove

Ove	20020619

20021203	
Open discussion items:
•	Should there be a separate rejection message for UTILTS?
•	Removal of not needed codes in STS/9013
•	Do we need a code to specify if its horizontal or vertical reconciliation?	To be done 	All	20020619	

Appendix D	
Proposal for a new chapter in the Functional description: “Addressing”

1.	Basic principles

1.1	Definitions
Juridical party:	In this document a Juridical party will be used as the party juridical responsible for sending or receiving information. Also called originator or final recipient of documents.

OBPI:	The key element in routing and addressing is the Overall Business Process that will be identified by a code called the Overall Business Process Identification (OBPI). OBPI also serves as the key element to indicate the business process capabilities of a party. The user group, government agency, or national Ediel group that make the User Guides for the business processes assigns this code. A User Guide describes how a general Ediel Implementation Guide (made by the Nordic/European Ediel Group or similar organisations is to be implemented and provides the rules on how to make use of these for specific business processes in the country or the user community. 

Party id:	The identification of a party, i.e. the party’s EAN location number or the party’s EIC (ETSO Identification Code). 

Third party:	A party acting on behalf of the juridical parties (as an intermediate) in a document exchange scenario. In between the Juridical parties there may be several Third parties. These intermediates can have different responsibilities, such as routing of documents, conversions to/from EDIFACT/XML and/or handling of the document content on behalf of the originator or final recipient. Intermediates only doing routing of documents will not be a part of the addressing principles discussed below. The Third parties may be split into the following two subtypes:

Application service provider (ASP):	A third party that takes care of the database (application) for a juridical party. The ASP is responsible for returning application acknowledgements, such as APERAK.
EDI Service Provider (ESP):	A third party that is responsible for the document exchange on behalf of the juridical party, including conversion of documents. The ESP is responsible for returning syntax related acknowledgements, such as CONTRL. 

Relationship between roles in document exchange

A juridical party can choose weather or not to use one or more third parties in his document exchange. It is also possible to combine usage of third parties for one or more business areas and handle the document exchange himself for other business areas.

1.2	Principles for addresses and identifications
1.	The juridical party may choose weather to use one or more third parties as intermediates in a document exchange scenario.
2.	Routing of documents, including acknowledgements, shall use the same principles even if third parties are used.
3.	The main use of the addresses in the interchange header (EDIFACT/UNB) is routing purposes. The routing information includes information regarding the OBPI, as specified in the sub address.
4.	The interchange header (EDIFACT/UNB) can identify the originator and final recipient of the interchange or the third parties involved, according to the rules given in this document. In addition the OBPI involved may be given as the sub address. 
5.	Sub addresses shall only be used for routing of documents to the right application through identification of a OBPI, and NOT to identify different organisations, departments or other entities.
6.	There shall be a one-to-many association between the communication address (e.g. X.400 addresses or SMTP addresses) and the party id used for routing purposes (e.g. in EDIFACT/UNB). A party id in the interchange header (EDIFACT/UNB) can only be linked to one communication address, but a communication address may be linked to several party ids.
7.	As a consequence of the previous rule, if a juridical party uses one or more third parties or have several communication addresses of other reasons, must have different party ids for each communication address. 
8.	Different parties (e.g. FR, DO, MS, MR in the NAD segment in the header part of a document) shall not be mixed in an interchange. 
9.	It shall always be the Juridical party, the party juridical responsible for sending or receiving the information that is identified in the document header level (NAD segment). 
10.	Parties shall be identified through a common, global and unique identification scheme. The identification scheme shall be either EAN or EIC (ETSO Identification Code).
11.	Sub addresses shall be used. This shall identify the OBPI concerned. 
12.	Application acknowledgements, such as EDIFACT/APERAK, shall be treated as any other document regarding the addresses. I.e. the sender address, including sub address in the original document, shall be sent as receiver address in the application acknowledgement. And the receiver address, including sub address in the original document, shall be sent as sender address in the application acknowledgement.
13.	Syntax acknowledgements, such as EDIFACT/CONTRL documents, shall be returned with opposite addresses. I.e. the sender address, including sub address in the original document, shall be sent as receiver address in the syntax acknowledgement. And the receiver address, including sub address in the original document, shall be sent as sender address in the syntax acknowledgement.

Relationship between juridical party, OBPI, party id and communication address

1.3	Usage of the UNB segment 
The UNB segment shall contain both the sender and the receiver addresses in the following data elements:

S002	INTERCHANGE SENDER	M			
0004	Sender identification	M	an..35	EAN Global Location no. (GLN) or EIC 	
0007	Partner identification code qualifier	R	an..4	Code:
14	EAN (European Article Numbering Association)
??	ETSO Identification Code (EIC)	
0008	Address for reverse routing	O	an..14	An OBPI may be used according to national rules.	
S003	INTERCHANGE RECIPIENT	M			
0010	Recipient Identification	M	an..35	EAN Global Location no. (GLN)	
0007	Partner identification	R	an..4	Code:
14	EAN (European Article Numbering Association) 
??	ETSO Identification Code (EIC)	
0014	Routing address	O	an..14	An OBPI may be used according to national rules.