Guidelines for Electronic Data Interchange. Hans Pipke/Nebojša Filipović 09/14/2016

Transcription

1 Guidelines for Electronic Data Interchange Hans Pipke/Nebojša Filipović 09/14/2016

2 Agenda 1. Introduction and Project Approach 2. Project Objectives 3. EDI Framework Roles and domains identification Communication means and file names Data exchanges Metering point database Creation and management of database 4. Definition of standards and implementation Roadmap (activities, timeframes) List of documentation Questionnaire 5. Discussion and next steps 2

3 Introduction and Project Approach

4 Introduction Presentation of document Guidelines for Electronic Data Interchange Key topics of this presentation: EDI framework for retail electricity market Decision on offered options Further development of standards for EDI in BiH 4

5 Project Approach Information model Business processes International best practice EDI Guidelines Current EDI situation Not developed 5

6 Project Objectives

7 Project Objectives Support Market Workgroup in Development of technical standards for data exchange Contribute to the capacity strengthening of the Market Working Group and responsible subordinate subgroups 7

8 EDI Framework

9 Purpose of EDI in Retail Market Serves as basic infrastructure for implementation of business processes It is a must for present-day data exchange Based on Information Technology Based on standardized Internet Protocols Supported by database(s) Multi-party environment 9

10 Elements of EDI standard Identification of roles and domains Communication means File names Acknowledgement and error messages Message types Message time, date and time period Message structure and content 10

11 General recommendations Delivery of proxies should be avoided Deadlines should be defined and respected Communication between suppliers and customers is not a subject of EDI 11

12 Identification of Roles and Domains Roles and domains should be clearly identified Identification should be unique during lifetime Identification should be assigned centrally In this document we consider identification of retail market actors/roles: DSOs Suppliers and domain Metering point Identification of BRP is already implemented 12

13 DSO Identification Should be unique Should be issued by responsible Regulatory Commission Three options: Custom identification scheme GS1-GLN identification scheme EIC identification scheme 13

14 Custom Identification Scheme Define custom scheme for identification Provides flexibility 2 digits country identification 1 digit code type (D for DSO) 5 digits consecutive number 14

15 GS1-GLN Identification Scheme Well known GS1 system, with worldwide uniqueness Parties are identified via 13 digits GLN codes: GS1 company prefix Location reference Last (check) digit 15

16 EIC Identification Scheme Energy Identification Coding scheme, used by ENTSO E 16 alphanumeric characters 2 digits Local Issuing Office number 1 digit code type 12 digits uppercase characters and minus sign 1 digit check digit, based on previous 15 digits 16

17 DSO Identification - Decision Recommendation: usage of EIC identification scheme Market Working Group participants should select the best option Decision should be unanimous, with one solution on a country level 17

18 Supplier Identification Should be unique Should be issued by responsible Regulatory Commission Three options (as for DSOs): Custom identification scheme GS1-GLN identification scheme EIC identification scheme EIC identification scheme is already in use in wholesale market 18

19 Custom Identification Scheme Define custom scheme for identification Provides flexibility 2 digits country identification 1 digit code type (S for supplier) 5 digits consecutive number 19

20 GS1-GLN Identification Scheme Well known GS1 system, with worldwide uniqueness Parties are identified via 13 digits GLN codes: GS1 company prefix Location reference Last (check) digit 20

21 EIC Identification Scheme Energy Identification Coding scheme, used by ENTSO E 16 alphanumeric characters 2 digits Local Issuing Office number 1 digit code type 12 digits uppercase characters and minus sign 1 digit check digit, based on previous 15 digits 21

22 Supplier Identification - Decision Recommendation: usage of EIC identification scheme and its extension to retail market Market Working Group participants should select the most favorable option Decision should be unanimous 22

23 Metering Point Identification Should be unique Should be issued by responsible DSO Three options (as for DSOs and suppliers): Custom identification scheme GS1-GLN identification scheme EIC identification scheme 23

24 Custom Identification Scheme Define custom scheme for identification Provides flexibility 8 digits DSO identification 20 digits consecutive number Example: DSO identification Consecutive number B A D Digits

25 GS1-GSRN Identification Scheme Well known GS1 system, with worldwide uniqueness Metering points are identified via 18 digits GSRN codes: GS1 company prefix Service reference Last (check) digit Example Digits

26 EIC Identification Scheme Energy Identification Coding scheme, used by ENTSO E 16 alphanumeric characters 2 digits Local Issuing Office number 1 digit code type 12 digits uppercase characters and minus sign 1 digit check digit, based on previous 15 digits 26

27 Metering Point Identification - Decision Recommendation: DSOs in this domain have different solutions (even different within a single DSO) This issue should be solved in further development of standards Market Working Group participants should reach a unanimous decision on country level 27

28 Communication means Single message (file) can be exchanged between (retail) market participants using different communication means The most common in use in the retail market are: File Transfer Protocol Web Services Simple Mail Transfer Protocol Recommendation: SMTP ( ) 28

29 File Names Files (messages) which contain data to be exchanged usually have a predefined structure of file name Advantages: It is human readable and understandable It is suitable for automatic data processing File name may contain the following info: Creation data Sender Receiver Message type Version 29

30 Retail Market Data Exchange: Participants and Data Business Parties in retail market process group EDI Customer switch Customers, Suppliers (including Supplier of Last Resort and Public Supplier), DSOs, BRP Connection Network users, DSOs contract Imbalance settlement in retail market DSOs, Suppliers, BRPs, ISO. Exchanged data Applications, requests, notifications, certificates, proposals, contracts, metering data reads Applications, requests, power consent, (initial) power permits, denials, complaints, decisions, contracts, declarations Aggregated metering data 30

31 Acknowledgement and Error Messages Acknowledgement messages confirm successful execution of particular data exchange step Error messages inform about unsuccessful execution of particular data exchange step Both messages are exchanged in an automated manner Recommendation: use acknowledgement and error message in data exchanges. 31

32 Message Types for Data Exchange Type Content EDIFACT equivalent Meter Reading Master Data Invoice Data Shall contain the meter readings, i.e., single meter reading or load profiles. Shall contain master data for customer, contract, metering point, e.g., beginning of supply, end of supply. Shall contain the data for billing grid fees. MSCONS UTILMD INVOIC 32

33 Messages Time, Date and Time Period Local time in BiH: Standard time CET (UTC+1) Daylight savings time CEST (UTC+2) IT systems usually implement UTC Days with 24, 23 and 25 hours Time synchronization between involved IT systems Impact of weekends and holidays 33

34 Message Format and Structure Format selection depends on: Complexity (CSV, XML, EDIFACT) Number of expected data exchanges In-house and in-country experience Message is composed from header and body Header contains data for message flow control and body processing Body contains key (application) data 34

35 Metering Point Database DSO should have a database that consists of: Metering points Customers Suppliers Meter is link to the metering point (where it is installed) Link between customer and metering point has a start and end date Link between supplier and customer (and metering point) has a start and end date 35

36 Balance Reponsible Party PK BPR ID Is balanced by Customer Supplier PK Metering Point ID Has a conttract on supply PK Supplier ID Adress Adress Consumption metered via PK Metering Point Metering Point ID supplies Adress Meter Is installed at Serial No. Register Is part of Register No. Is part of Meter Reading Date from Date to Value 36

37 Business Process: Creation and Management of Database Creation and management of databases Database for load profiles (LPDB) Database for load diagrams (LDDB) Provision of data from databases to authorized users Submission of operation procedures for database 37

38 IT System Software Application and Database Client 4 Client 3 Software Application Database Client 2 Client 1 38

39 General Requirements for Database Database access Data management Automated data entry into database Database backup and restoration process Database security Input, output and data transformation 39

40 Development of Load Profiles Database (LPDB) Data that shall be stored Load profile data (sampled end customer, ambient data, other data) Requested functionality Data entry, validation, substitution, analysis, transformation, export Output data and reports Normalized and replacement load diagrams Interfaces and data exchange Import data from customer sample, export data to LDDB 40

41 Development of Load Diagram Database (LDDB) Data that shall be stored Developed load profiles, metering data, market participant data Requested functionality Data entry, validation, substitution, analysis, transformation, aggregation, exchange, matching, export Output data and reports Load diagrams for customers, data for imbalance settlement (for Suppliers, BRPs, other DSOs, ISO) Interfaces and data exchange Import data from metering system and LPDB, export data to Suppliers and BRP, data exchange with ISO and other DSOs 41

42 Other Business Sub-Processes Provision of Data from Databases to Authorized Users Authorized users: End Customers, Suppliers, BRPs, ISO, Regulatory Commissions On contractual basis Specific case is data request from Other (non-responsible) Regulatory Commission Submission of Operation Procedures for Databases DSO develops and submits to responsible Regulatory Commission operating procedure for database development, management and data provision 42

43 Roadmap for Further Activities

44 Activities Required for Development and Implementation of Standards Presented in a shape of a Roadmap Contains activities and estimated timeframes DSOs have a central role Involvement of stakeholders (Suppliers and BRPs) Involvement of ISO and Regulatory Commissions 44

45 List of Required Activities 1. Determine communication means 2. Unique and unambiguous market participant identification 3. Unique and unambiguous identification of metering point scheme 4. Definition of messages that are exchanged 5. Definition of content (data, list of information) of messages 6. Definition of file formats for messages 7. Definition of necessary software modifications and/or procurement for EDI implementation 8. Technical specification, procurement, development, commissioning 9. Test operation 10. Regular-commercial operation 45

46 Timelines and Interdependence of Steps Activities 1-3 can start at the same time and may happen congruently Before the start of activity 4, business processes should be developed Activity 4 may start at the same time as first three activities Activities 4-6 should be developed sequentially Before the start of activity 7, activity 6 should be finished Activities 7-10 should be developed sequentially 46

47 Development Specialists It is necessary to create an expert group (or groups) Expert group (or groups) shall contain specialists from: DSO Suppliers and BRPs ISO and Regulatory Commissions (where needed) Consultants (if necessary) Depending on activity and process, involved experts shall be: Decision-makers Technical experts (power engineering, IT, metering, business processes, ) Others (if necessary) 47

48 Roadmap in Gantt Charts Minimum estimated duration Maximum estimated duration 48

49 List of Relevant Documentation Document name (German) Common rules and recommendations for exchange of EDIFACT documents Interchange Agreement in the Belgian Liberalized Utility Market Regulation F1: 'EDI communication with the Data Hub in the electricity market' Common Nordic XML rules and recommendations 49

50 Questions and Answers, Discussion

51 Next steps (working groups)