The Standard

Transcription

1 The Standard

2 Content What is What is EASEE-Gas Why EDI How it works EDI standard Message Implementation Guidelines (MIG) EDI Standard Version 3 Uncovered items Edig@s Workgroup Members

3 What is is a comprehensive EDI Standard for the exchange of data via electronic means between parties involved in the Gas Industry.

4 EASEE-GAS Structure Members Producers Transporters Distribution Network Ops Traders & Shippers Suppliers Retail Suppliers End Users Service Providers Board Executive Committee Advisory Panel CBP Implementation Task-Force WG1 WG2 WG3 WG4 WG5 WG6 WG7 WG8 WG9 IT Communication Network Real-time Data Exchange Message Codification & Maintenance ebxml Business Rules Harmonisation of units Message Specification Gas Quality Harmonisation Codification and Definitions

5 Common Business Practice Common Business Practices (CBPs( CBPs) ) are standards, procedures and/or protocols commonly used in the gas industry in Europe and recommended by EASEE- gas for adoption by all relevant industry players to simplify and streamline business processes across the whole of Europe. Once CBPs are developed in the groups they are presented to the Executive Committee (ExCom( ExCom) ) to consider. If they are agreed, the CBPs are issued to the membership for final comments. The final CBPs are then presented to the ExCom for approval and to a General Meeting of Members for ratification.

6 Common Business Practice EASEE-gas has now approved and issued a number of CBPs and, in consultation with the Madrid Forum participants, has taken responsibility for monitoring the implementation of these CBPs.. To enable the Executive Committee to report on an annual basis to the Madrid Forum it has undertaken a survey of all Full Members of EASEE-gas to respond on their experiences and where appropriate indicate by country the progress of implementation or existence of barriers of any kind.

7 Common Business Practice Common Business Practice /01 003/01 This Common Business Practice has been approved by EASEE-gas for use in gas business transactions. It states: Protocol to be used: EASEE-Gas recommends for current practice the use of the protocol for exchange of business information, regarding transactions, between parties in the European gas market, as described in the Message Implementation Guidelines (MIG).

8 Why To cope with: the increasing number of players in the gas business the increasing number of messages the increasing demand for just-in in-time deliveries the increasing need for immediate response allows for: speed and reliability automation through standardisation cost efficiency

9 EDI: how it works COMMUNICATION SW COMMUNICATION SW TRANSLATOR TRANSLATOR APPLICATION APPLICATION

10 EDI Standard The EDI Standard is a subset of the UN/EDIFACT worldwide EDI standard. Edig@s is based on the standard messages published in the UN/EDIFACT D 96A and D 97A directories. UN/EDIFACT syntax version 3 is recommended for the Edig@s messages. Version 3.2 is the most recent published version of the Edig@s EDI standard.

11 MIG The Message Implementation Guidelines (MIG) are available on the website. The document consists of 7 parts: I Contractual messages Messages exchanged between Sellers and Buyers or their representatives and between Traders. Messages are: - Availability - Request - Response to Request - Trader s s Net Trade Notice - Trader s s Net Confirmation Notice

12 MIG II Transport messages Messages exchanged between Shippers, Transit System Operators, HUB Operators, Storage Managers, Messages are: - Nomination and Nomination Response - Delivery Order and Delivery Order Response - Allocation - Flow Rate information - Changed Capacity - Quality Deficient Gas Notice and Quality Deficient Gas Take Notice - Imbalance Notification

13 MIG III IV General messages Messages exchanged between all parties. Messages are: - Gasdata Request and Gasdata - Daily Report - General Message - Acknowledgement message - Control message Financial messages Messages exchanged between all parties. Messages are: - Invoice - Attachment to Invoice

14 MIG V Attachments Information relevant for all messages and rules for the maintenance of the standard. Attachments are: - EDIFACT Syntax - Maintenance Guidelines - Message and Segment Directories VI Code List Provides all Edig@s specific codes to be used in. the messages.

15 MIG VII PVE Messages messages specifically developed for the Netherlands and to be used as of Messages are: - NOMINT - NOMRES - DAYREP - IMBNOT - CONTRL - APERAK

16 EDI Standard Version 3 What is different between Edig@s version 2 and 3: Templates: : to limit the free interpretation of the Edig@s Message Implementation Guidelines (MIG) templates have been defined. The templates provide a very clear and strict definition of how a message needs to be implemented. The purpose of the templates is to facilitate the implementation of the Edig@s messages.

17 EDI Standard Version 3 Connection Point: : the previously used concept of delivery and redelivery point has been replaced by the concept connection point, i.e. where two systems are connected. TSO Connection Point (TCP): the European TSO Connection Points have been coded in line with the EIC Coding methodology. Messages will now refer to those locations by using a 16-digit code that can be found in code list 3225 (Part VI of the MIG).

18 EDI Standard Version 3 Internal/External Shipper: : those terms have been newly introduced to replace the previously used Upstream/Downstream shipper.

19 How to use the Templates SG2 M Remarks SG2.1 M NAD M NAD-LOC The mandatory segment group 2 consists of: NAD to identify the party - (mandatory) LOC to identify a location relevant for that party - (conditional) The EDIFACT guidelines indicate that the identification of the buyer or similar party and the seller or similar party is mandatory. The segment group can be repeated more than twice if other parties than the mandatory ones need to be identified in relation to the content of this message. This Edig@s template describes only the two mandatory occurrences. Message issuer NAME AND ADDRESS Identifies the issuer of the message 3035 M an..3 Party qualifier See restricted qualifier code list below C082:3039 M an..35 Party identification details Use Edig@s code list 3039 C082:1131 N Not used C082:3055 M an..3 Code list responsible agency ZEW (=Edig@s) Example NAD+ZPO+ABC::ZEW Restricted qualifier code list for NAD-3035 ZHO ZPO Hub Operator Pipeline Operator

20 How to use the Templates Segment or segment group explanation: Segment (group) identification tag and status Segment tag or components of the segment group SG2 M Remarks NAD-LOC The mandatory segment group 2 consists of: NAD to identify the party - (mandatory) LOC to identify a location relevant for that party - (conditional) The EDIFACT guidelines indicate that the identification of the buyer or similar party and the seller or similar party is mandatory. The segment group can be repeated more than twice if other parties than the mandatory ones need to be identified in relation to the content of this message. This Edig@s template describes only the two mandatory occurrences. How to use the segment or segment group

21 How to use the Templates Segment description Data element (DE) tag Segment tag and status Segment location, name and function NAD M NAME AND ADDRESS Identifies the issuer of the message 3035 M an..3 Party qualifier See restricted qualifier code list below C082:3039 M an..35 Party identification details Use Edig@s code list 3039 C082:1131 N Not used C082:3055 M an..3 Code list responsible agency ZEW (=Edig@s) Example NAD+ZPO+ABC::ZEW Composite DE tag Example DE status DE format DE name Unused DE Comments and references

22 How to use the Templates Restricted code list DE for which code list is added Restricted qualifier code list for NAD-3035 ZHO ZPO Hub Operator Pipeline Operator Code tag Code name

23 Uncovered Requirement What to do if a requirement is uncovered? question to be submitted to EDIG@S Workgroup (direct contact or Website) question studied in Workgroup solution must be in line with EDIFACT rules solution approved by Workgroup solution included in next MIG version

24 How can be used? Information can be obtained from each member company. The messages are EDIFACT subsets. This allows the use of EDIFACT-compliant software with minimal customisation.

25 Workgroup Members Consultant to the workgroup

26 an open solution is not a proprietary solution... but it is open to all gas companies who want to implement this new way of communicating! Edig@s is the only European standard for message exchange in the Gas Industry.

27 Want to know more? For more information on this standard visit the website at :