Eng TSVD 01 06 2011

Annex No.
Technical Specifications
of Data Exchange
with Distribution Network
Operator
1/88
1. CONTENTS
2. Abbreviations ....................................................................................................... 6
3. Introduction .......................................................................................................... 7
3.1. Overall data exchange context between natural gas supplier and DNO........ 7
3.2. Communication channels .............................................................................. 8
3.3. Message formats ........................................................................................... 8
3.4. Security ......................................................................................................... 9
3.4.1. Example of encryption and decryption on the command line ..................... 9
3.4.1.1. Decryption............................................................................................. 10
3.4.1.2. Encryption ............................................................................................. 10
3.4.2. Automatic encryption and decryption ....................................................... 11
3.4.3. Technical information ............................................................................... 11
4. Principles of communication .............................................................................. 11
4.1. Specifications for electronic communication................................................ 11
4.2. Technical conditions necessary for the proper functioning of electronic
communication ...................................................................................................... 12
4.3. Principles of electronic communication........................................................ 12
4.4. Types of e-mails .......................................................................................... 13
4.4.1. Error reports ............................................................................................. 13
4.4.1.1. Error report e-mail from DNO to natural gas supplier............................ 14
4.4.1.2. Error report e-mail from natural gas supplier to DNO............................ 14
4.4.2. Import ....................................................................................................... 14
4.4.2.1. Import e-mail from natural gas supplier to DNO.................................... 14
4.4.2.2. Import confirmation e-mail from DNO to natural gas supplier ............... 15
4.4.3. Export....................................................................................................... 15
4.4.3.1. Export e-mail from DNO to natural gas supplier.................................... 15
4.4.3.2. Export confirmation e-mail from supplier to DNO.................................. 15
4.4.4. Mass readings.......................................................................................... 16
4.4.4.1. Mass readings e-mail from DNO to natural gas supplier....................... 16
4.4.4.2. Mass reading confirmation e-mail from natural gas supplier to DNO .... 16
4.4.5. Exchange of public keys or certificates .................................................... 16
4.4.5.1. E-mail for public key exchange from DNO to natural gas supplier ........ 16
4.4.5.2. E-mail for public key exchange from natural gas supplier to DNO ........ 17
2/88
4.5. Specification for communication via Web application .................................. 17
4.5.1. Security and accessing of the application ............................................. 17
4.5.2. Execution method - reading/displaying messages ................................ 17
4.5.3. Execution method – writing and sending messages ............................. 17
5. general principles for using MESSAGES ........................................................... 18
5.1. Identifiers..................................................................................................... 18
5.1.1. PoD identifier............................................................................................ 18
5.1.2. Identifier of communicating partner .......................................................... 18
5.2. Use and format of date and time ................................................................. 18
5.3. Date format.................................................................................................. 18
5.4. Numerical data format ................................................................................. 18
6. MESSAGE FORMATS....................................................................................... 19
6.1. Definition of message formats ..................................................................... 19
6.1.1. MSCONS message format....................................................................... 19
6.1.2. UTILMD message format ......................................................................... 22
7. DATA EXCHANGE SCENARIOS ...................................................................... 24
7.1 Scenarios for exchange of master data ....................................................... 24
7.1.1. Concluding contract for PoD ................................................................ 24
7.1.1.2 Description of the scenario Concluding contract on access to
distribution network and the distribution of gas to
POD…………………………………………………………………..………………………………24
7.1.1.3 Scenario for Concluding contract for PoD .................................... 25
7.1. 2. Terminating contract for Point of Delivery ............................................ 26
7.1.2.1. Scenario for Terminating contract for PoD ..................................... 26
7.1.2.2. Scenario for Concluding contract for Point of Delivery ................... 26
7.1.3. Change of customer at PoD................................................................ 27
7.1.3.1. Scenario of Change of customer at PoD ........................................ 27
7.1.3.2. Scenario of Change of customer at PoD ........................................ 28
7.1.4. Change of customer name................................................................... 29
7.1.4.1. Scenario of Change of customer name .......................................... 29
7.1.4.2. Scenario of Change of customer name .......................................... 29
7.1.5. Replacement of device ....................................................................... 30
7.1.5.1. Scenario for Replacement of device............................................... 30
7.1.5.2. Scenario for Replacement of device............................................... 30
3/88
7.2. Scenarios for exchange of measured data .................................................. 31
7.2.1. Regular reading ................................................................................... 31
7.2.1.1. Scenario for Regular reading.......................................................... 31
7.2.1.2. Scenario of Regular reading........................................................... 31
7.2.2. Extraordinary reading........................................................................... 32
7.2.2.1. Scenario of Extraordinary reading .................................................. 32
7.2.2.2. Scenario of Extraordinary reading .................................................. 32
7.2.3 Corretive reading ............................................................................... 33
7.2.3.1. Scenario of Corrective reading ....................................................... 33
7.2.3.2. Scenario of Corrective reading ....................................................... 33
7.2.4. Mass input reading............................................................................... 34
7.2.4.1. Scenario of Mass input reading ...................................................... 34
7.2.4.2. Scenario of Mass input reading ...................................................... 34
7.3. Scenarios for exchange of information on distribution services................... 35
7.3.1. Request for disconnection due to non-payment................................... 35
7.3.1.1. Scenario request for disconnection due to non-payment................ 35
7.3.1.2. Scenario of Request for disconnection due to non-payment .......... 35
7.3.2 Request for reconnection of non-payer .......................................... 36
7.3.2.1. Scenario Request for reconnection of non-payer ........................... 36
7.3.2.2. Scenario of Request for reconnection of non-payer ....................... 37
7.3.3. Request for disconnection.................................................................... 38
7.3.3.1. Scenario for Request for disconnection.......................................... 38
7.3.3.2. Scenario of Request for disconnection ........................................... 39
7.3.4. Request for reconnection ..................................................................... 40
7.3.4.1. Scenario of Request for reconnection ............................................ 40
7.3.4.2. Scenario of Request for reconnection ............................................ 40
7.3.5. Request for Info-order. ......................................................................... 41
7.3.5.1. Scenario of Request for Info-order ................................................ 41
7.3.5.2. Scenario of Request for Info-order ................................................. 41
7.3.6. Request for a claim concerning reading............................................... 42
7.3.6.1. Scenario of Request for claim concerning reading ......................... 42
7.3.6.2. Scenario of Request for claim concerning reading ......................... 43
7.3.6.3. Scenario of Request for claim concerning device........................... 44
4/88
7.3.7. Request for self-reading, Change of contractual tariffs ........................ 45
7.3.7.1. Description: Request for self-reading, Change of contractual tariffs45
7.3.7.2. Scenario of Request for self-reading .............................................. 45
7.3.7.3. Scenario for Change of contractual tariff ........................................ 45
7.4. Scenarios for change of supplier.............................................................. 46
7.4.1. Change of supplier to PoD from perspective of DNO........................... 48
7.4.1.1. Scenario of Change of supplier to PoD from perspective of DNO .. 48
7.4.1.2 Scenario of Change of supplier to PoD from perspective of DNO ...... 49
7.5. Scenarios of periodically exchanged data ................................................ 50
7.5.1. Transfer of combustion heat values ..................................................... 50
7.5.1.1. Scenario description: Transfer of combustion heat values ............. 50
7.5.1.2. Diagram of Transfer of combustion heat values scenario............... 50
8. Formats of xml messages - XSD schemes ........................................................ 52
9. Interfaces between DNO SPP- distribúcia, a.s. and natural gas suppliers......... 52
10. List of annexes................................................................................................ 53
Annex No.1 MSCONS message format……………….………….……………………53

Annex No.2 UTILMD message format……………….…………………………………62
5/88
2. ABBREVIATIONS
Abbreviation
Meaning
ETSO Identification Code
EIC Code
ETSO = European Transmission System Operators
Intercompany Data Exchange (data exchange concept between
IDE
organizations on the network markets)
PoD Point of Delivery
DNO Distribution Network Operator
S/MIME Security services for applications using e-mail.
TSDE Technical specifications of data exchange
UN/EDIFACT International standards for electronic data interchange
MSCONS UN/EDIFACT message used for transferring measurement data
UN/EDIFACT message used for transferring point of delivery master
UTILMD
data
XML Extensive Markup Language, developed and standardized by the
XSD W3C.
Definition of data transferred via XML.
6/88
3. INTRODUCTION
The Technical Specifications of Data Exchange document is a manual for

communication with SPP – distribúcia, a.s., acting as distribution network operator
(DNO), with other gas market participants (suppliers of natural gas). The
specifications contain a detailed description of the processes, procedures and data
definition of electronic communication with the DNO.
This document describes in detail the following:

 The conditions and general principles of communication in the natural gas
market
 Identifiers, data type formats, formats of messages used
 Flow charts, sequence of data exchange processes and step-by-step data
exchange descriptions linked to company processes. The duties and
responsibilities of market participants in the data exchange process and the
timetable for data exchange are defined in the Operation Rules of SPP –
distribúcia, a.s.
 Transferred data at each data exchange step, description of defined fields,
their meaning and code book
 Rules of electronic communication via e-mail
 Protection of transferred data via encryption
3.1. Overall data exchange context between natural gas supplier and DNO
Under Art. 25 of Act No. 656/2004 Coll. on the Energy Sector, which enacts
separation of the distribution network operation from the business division, data
exchange between the natural gas supplier and the distribution network operator is
needed.
The data exchange between the entities in the liberalized gas market is conducted
electronically. The DNO converts the data to be exchanged into XML format,
encrypts them and sends them via mail server to the natural gas supplier, whose task
is to decrypt the message and duly interpret the information contained in the XML.
The natural gas supplier will have the option of displaying as well as sending XML
documents over a Web application. The same principles apply to data transfer in the
opposite direction.
7/88
Map of Supplier Map of Distributor
System for Customer

Mail server Data Information
Exchange Portal
Picture 1 – Overall context of data exchange with DNO
3.2. Communication channels
Communication between the natural gas supplier and the DNO may take place in two
ways:
1. Electronically, by means of message exchange via documents in XML format
in accordance with these technical specifications.
2. Information exchange between the natural gas supplier and the DNO may also
take place via a Web application which makes XML documents available for
natural gas suppliers which have no information system implemented for
processing the given information.
Availability of documents: The technical specifications as well as the templates of the

respective forms are available at the website of the DNO: (http://www.spp-
distribucia.sk/Portal3en/DesktopDefault.aspx?tabid=1121).
3.3. Message formats
For electronic communication messages according to UN/EDIFACT specification are

used. The messages are in UTILMD and MSCONS formats.
UN/EDIFACT
EDIFACT is an acronym for Electronic Data Interchange for Administration,

Commerce and Transport. It provides:
 International standards for electronic data exchange
 A set of syntax rules
 Data elements, segments and codes
 Messages – various business documents composed of segments arranged
in a hierarchical structure
8/88
EDIFACT was created by combining American and European standards and thus it
formed an international standard which is still being developed and coordinated by
the UN (United Nations) and ECE (Economic Commission for Europe).
The description of each message format includes:

 Basic structure of segments
 Description of the various segments and their constituent fields.
 XML messaging schemes
3.4. Security
The goal is to create an encrypted communication channel between the DNO and the
natural gas supplier. Each e-mail contains an encrypted attachment in SMIME format
and an optional e-mail body. Therefore, sensitive data can be located only in the
attachment of the e-mail and not in the e-mail body. Here the following applies:
1. Asymmetric encryption is used: encryption using public key, decryption using
private key. It follows that each natural gas supplier shall obtain a public key
from the DNO. Furthermore, SPP - distribúcia, a.s. acting as DNO shall obtain
a public key from each natural gas supplier.
2. The DNO’s as well as all natural gas suppliers’ public keys shall meet the
following: they must be a part of the certificate in X509 v3 format, they must be
designated for RSA algorithm with a minimal length of 1024 bits, they must be
designated for encryption, i.e. the Key Usage attribute (Usage of Key) must
include a data Encipherment option (encryption of messages) and the period
of certificate validity must be no longer than 2 years. The fulfilment of these
requirements for the supplied public keys will be checked manually upon
receiving the public key from each natural gas supplier. In every e-mail
message only the attachment is encrypted. It follows that the e-mails may
optionally include an accompanying text. The subject of the message is also
not encrypted.
3. To encrypt and decrypt the attachment of the e-mail any software supporting
SMIME format can be used, e.g. OpenSSL (http://www.openssl.org), cryptigo
(http://www.vptechnologies.net), IP*Works! S/MIME
(http://www.nsoftware.com/ipworks/smime/)... Below is an example using
OpenSSL utility.
The encryption / decryption will be performed automatically during the transmission.

Of course it is possible to perform this operation manually.
3.4.1. Example of encryption and decryption on the command line
Below is the procedure for natural gas supplier which describes manual encryption
and decryption of e-mail attachments using the open SSL utility. A detailed
9/88
description of the open ssl command parameters can be found in the product
documentation1.
3.4.1.1. Decryption
Procedure:
1. Open the e-mail
2. Save e-mail attachment to disk
3. Run the command to decrypt
openssl smime -decrypt -inform DER -in encrypted.p7m -inkey

mycertificate1key.pem -out decrypted
Command description: the command decrypts the encrypted.p7m file using

private key mycertificate1key.pem. The output is a file called decrypted.
4. Use the decrypted file, in our case it is the file called "decrypted".
3.4.1.2. Encryption
Procedure:
1. Run the command to encrypt
openssl smime -encrypt -in subor.txt -outform DER -out encrypted.p7m -

aes256
-binary mycertificate1cert.pem
Command description: the command encrypts the subor.txt file using

encryption algorithm aes256 and certificate mycertificate1cert.pem. The output
is a file called encrypted.p7m in binary DER format.
2. Add the newly created file as an e-mail attachment (in our case it’s the file
called encrypted.p7m)
3. Fill in the other details of the e-mail according to Chapter 4.4 Chyba! Nenašiel
sa žiaden zdroj odkazov.
1
http://www.openssl.org/docs/apps/smime.html
10/88
3.4.2. Automatic encryption and decryption
Automatic encryption and decryption requires implementation of software that

supports SMIME format within the system of the natural gas supplier:
1. By means of own implementation of encryption/decryption in SMIME format or
by using third party library.
3.4.3. Technical information
Parameter Description
Encryption algorithm AES256 or AES256_CBC
Mail format Multipart
Encrypted attachment – p7m (then the file name will be e.g.
extension sprava.p7m)
Encrypted attachment – application/octet-stream
content type
Encrypted attachment – Format used: SMIME
format The encrypted data must be compatible
with the output generated by the commands
described in Chapters Chyba! Nenašiel sa
žiaden zdroj odkazov. and Chyba!
Nenašiel sa žiaden zdroj odkazov..
4. PRINCIPLES OF COMMUNICATION
4.1. Specifications for electronic communication
The whole electronic communication process is automated. However, it is required

that the e-mails are in S/MIME format and that each e-mail includes an XML
document as attachment containing complete information about the required action.
The creator of the file is responsible for:
 Timeliness of data transmission
 Formal correctness of data sent
 Correctness of content of data sent
 Automation of data transmission
 Security of data sent
In order to meet the requirements imposed on data exchange it is necessary that
e-mail communication also meets the following criteria:
 Maintaining trade secrets (It is undesirable if any third party has access to the
content of e-mails. Therefore, the communication between both parties must
be electronically encrypted.)
 Verification of message origin (Serves as an unambiguous identification of
information originator. Prevents forgery of electronic documents.)
 Each message will be automatically confirmed upon receipt.
11/88
 Electronic mail will be compatible with S/MIME standard.
 Each message used contains data for one point of delivery, with the exception
of meter readings transferred in bulk.
 Each party shall have a specially designed and published e-mail inbox for this
type of communication to which they will receive these messages and from
which they will send these message.
4.2. Technical conditions necessary for the proper functioning of

electronic communication
 Information support for file creation in XML format according to the approved
technical specifications (a prerequisite for information system used for
converting)
 Mail server and e-mail addresses published also suppliers’ side. One e-mail
address for distribution and one for each contractor.
 Authorization and identification of communicating partners
 Setup of automatic reply to received message according to accepted
conventions
4.3. Principles of electronic communication
The data exchange between DNO and the natural gas supplier is conducted via e-
mail communication channel. Data exchange takes place in two directions:
1. Communication in direction from DNO to natural gas supplier (Export)

works as follows: The message from DNO’s system of MSCONS or UTILMD
type, the mass meter reading or the import confirmation is encrypted by the
target natural gas supplier’s public key and is sent in the attachment of the e-
mail to the given natural gas supplier. The natural gas supplier decrypts the
message from the attachment of the e-mail using his private key. In direction
from DNO to supplier also e-mails with an error might arrive which do not
contain any attachment, only an error description in the message body.
2. Communication in direction from natural gas supplier to SPP to DNO

(Import) works as follows: The message which is created at the natural gas
supplier’s side of MSCONS or UTILMD type or the export confirmation is
encrypted by the DNO’s public key and is sent in the attachment of the e-mail
to the address of SPP - distribúcia, a.s.. The DNO’s system decrypts the
message from the attachment of the received e-mail using its private key. In
direction from natural gas supplier also e-mails with an error might arrive
which do not contain any attachment, only an error description in the message
body.
12/88
Here are the specific types of e-mails used, the format and method of securing of the
transferred data.
The following e-mail addresses are used for communication with SPP – distribúcia:
extide_confirmation@spp-distribucia.sk – natural gas suppliers send confirmation of
receipt of exports here
extide_import@spp-distribucia.sk – natural gas suppliers send imports here
soaadministrators@spp-distribucia.sk – natural gas suppliers send error reports here
<naturalgassupplier@naturalgassupplier.sk> – the natural gas supplier’s e-mail
address will be recorded in the document in this format. It is used for receiving
exports, mass meter readings, import confirmations, error reports (addressee or
recipient) and public key exchange.
4.4. Types of e-mails
Natural gas suppliers communicate with the DNO via e-mails described in this
chapter.
In the subject of the e-mails the following information is indicated:
 <supplier id> - supplier’s unique identifier, assigned by DNO
 <message type> - type of transferred message (e.g. S01, see
documentation Technical Specifications of Data Exchange with DNO)
 <message id> - unique message identifier
- supplier must generate this identifier when importing
 <x> - used in mass meter reading export, represents the file
number
The e-mail subject, i.e. its fields are important, as the messages are reconciled
based on them. This means that when confirming the same e-mail subject must be
used as when exporting. Similarly, in case of error the same field values will be used
(<supplier id>, <message type>, <message id>).
4.4.1. Error reports
During communication between the DNO and the natural gas supplier errors may
occur. The parties communicate the errors to each other by means of e-mails
described below. From the DNO’s system an error report may arrive to the natural
gas supplier in response to his
e-mail with import or export confirmation, or mass meter reading confirmation due to
the following reasons:
 The message does not contain the required details (recipient, sender, subject,
e-mail body, attachment, see below described types of e-mails)
 The XML in the e-mail attachment to be imported is not in accordance with
MSCONS or UTILMD scheme (see chapter “Formats of XML messages - XSD
schemes”)
 The e-mail attachment with confirmation does not have the correct content
(see chapter “Import confirmation, export confirmation, mass meter reading
confirmation”)
13/88
 Cannot decrypt the attachment
 Incorrect certificate was used
4.4.1.1. Error report e-mail from DNO to natural gas supplier
The e-mail in which the natural gas supplier receives an error report from the DNO’s
system has the following structure:
Addressee: <naturalgassupplier@naturalgassupplier.sk>
Sender: soaadministrators@spp-distribucia.sk
Subject: error: <supplier id>_<message type >_<message id>
E-mail body: <error description>
Attachment: without attachment
By means of this error report the DNO– notifies the natural gas supplier of a problem
in his
e-mail sent earlier, of type:
 import
 export confirmation
 mass meter reading confirmation
4.4.1.2. Error report e-mail from natural gas supplier to DNO
The e-mail in which the natural gas supplier sends an error report into the DNO’s
system has the following structure:
Addressee: soaadministrators@spp-distribucia.sk
Sender: <naturalgassupplier@naturalgassupplier.sk>
Subject: chyba: <supplier id>_<message type>_<message id>
E-mail body: <error description>
Attachment: without attachment
By means of this error report the natural gas supplier can notify the DNO’s system
administrator of a problem relating to a received:
 export
 mass meter readin
 import confirmation
4.4.2. Import
4.4.2.1. Import e-mail from natural gas supplier to DNO
The e-mail in which the natural gas supplier sends data for importing into the DNO’s
system must have the following structure:
Addressee: extide_import@spp-distribucia.sk
14/88
Subject: <supplier id>_<message type>_<message id>
E-mail body: blank
Attachment: encrypted XML containing import, must be in accordance with the
scheme for the given message type (see chapter “Formats of XML
messages - XSD schemes”)
4.4.2.2. Import confirmation e-mail from DNO to natural gas supplier
The e-mail in which the DNO confirms to the natural gas supplier the receipt of the
import has the following structure:
Subject: confirmation: <supplier id>_<message type>_<message id>
E-mail body: blank
Attachment: encrypted text file containing <message id> identifier
4.4.3. Export
4.4.3.1. Export e-mail from DNO to natural gas supplier
The e-mail in which the DNO sends exported data to the narural gas supplier has the
following structure:
Sender: extide_confirmation@spp-distribucia.sk
Subject: <supplier id>_<message type>_<message id>
E-mail body: blank
Attachment: encrypted XML containing export which is in accordance with the
scheme for the given message type (see chapter “Formats of XML
messages - XSD schemes”)
4.4.3.2. Export confirmation e-mail from supplier to DNO
The e-mail in which the natural gas supplier confirms the receipt of the export must
have the following structure:
Addressee: extide_confirmation@spp-distribucia.sk
Subject: confirmation: <supplier id>_<message type>_<message id>
E-mail body: blank
15/88
4.4.4. Mass readings
In case that the mass reading is divided into several files, each file is sent via e-mail
separately and the natural gas supplier confirms the receipt of each file, also
separately.
4.4.4.1. Mass readings e-mail from DNO to natural gas supplier
The e-mail in which the DNO sends a mass reading to the natural gas supplier has
the following structure:
Sender: extide_confirmation@spp-distribucia.sk
Subject: <supplier id>_<message type>_<message id>_<x>
E-mail body: “File <x> from <y>” – Information on which file in the sequence (x) is
being sent from the total number of files (y).
Attachment: encypted compresses ZIP file containing an XML export which
corresponds to the mass reading scheme (see chapter “Formats of
XML messages - XSD schemes”).
4.4.4.2. Mass reading confirmation e-mail from natural gas supplier to DNO
The e-mail in which the natural gas supplier confirms the receipt of the mass reading
must have the following structure:
Addressee: extide_confirmation@spp-distribucia.sk
Subject: confirmation: <supplier id>_<message type>_<message id>_<x>
E-mail body:“File <x> from <y>” – Information on which file in the sequence (x) is
being confirmed from the total number of sent files (y).
4.4.5. Exchange of public keys or certificates

Certificates expire at regular time intervals. The public key or certificate exchange
process is supported by the following e-mail communication.
4.4.5.1. E-mail for public key exchange from DNO to natural gas supplier
The e-mail in which the DNO sends his public key to the natural gas supplier has the
following structure. The requirements to be met by the given public key are described
in chapter 3.4.
Subject: certificate:_<supplier id>_<message type>_<message id>
E-mail body: Optional accompanying text.
Attachment: Public key.
16/88
4.4.5.2. E-mail for public key exchange from natural gas supplier to DNO
The e-mail in which the natural gas supplier sends his public key has the following
structure. The requirements to be met by the given public key are described in
chapter 3.4. The given key is manually checked prior to the import to the system.
Addressee: soaadministrators@spp-distribucia.sk
Subject: certificate: <supplier id>_<message type>_<message id>
E-mail body: Optional accompanying text.
Attachment: Public key.
4.5. Specification for communication via Web application
Communication via web application in the form of form application represents an

alternative way of transferring information between the natural gas supplier and the
DNO. Only those XML documents (messages) will be loaded and displayed which
are intended for the particular supplier. The same feature will be implemented also in
the opposite direction when entering data for the DNO.
4.5.1. Security and accessing of the application
The access to the application will be secured via an encrypted channel. Each natural
gas supplier must authenticate himself prior to using the Web application and based
on the granted authorization data he will gain access only to those XML documents
which are intended for him. The authorization data will be obtained from the solution
operator on written request and after approval by the DNO’s authorized staff
4.5.2. Execution method - reading/displaying messages
Each XML document will be interpreted by a specific XML form and a strictly defined
XSD scheme. For every message there will be separate XSD schemes and forms via
which the given message (XML document) will be displayed for the authorized Web
application user in an acceptable form. It will be possible to save the displayed
document in other formats (e.g. html, doc, pdf, ...) according to the available natively
supported formats.
4.5.3. Execution method – writing and sending messages
The same application will be used for sending XML messages. To send an XML
document to the DNO’s system it will be necessary to choose the correct form for the
given message type. Only a user having sufficient range of authorizations for working
with XML documents will be able to send the document. After completing all the
relevant data the XML document will be processed by the DNO’s system. The
application user will have the option to save a copy of the XML document on his
workstation having the same content as the one saved in the Web application.
17/88
5. GENERAL PRINCIPLES FOR USING MESSAGES
5.1. Identifiers
5.1.1. PoD identifier
The point of delivery is the basic communication object for the import and export of
data. The point of delivery is identified by a distinct label.
Identification: SKSPPDISDDDDDCCCCCCC
DDDDD – the type of PoD according to the internal codebook of SPP- distribucia,
a.s.
CCCCCCC – the number of the PoD of the customer, 7-figure serial number of
discount, justified with zeros from the left.
5.1.2. Identifier of communicating partner
Identification: SKSPPDAAAAAA*
AAAAAA* – acronym for partner
5.2. Use and format of date and time
 The date and time are always given at the currently valid time.
 The periods are indicated by the time of commencement and the end of the
period
5.3. Date format
A Gas Day is the time period of 24 hours commencing at 8.00 am Central European
Time or summer time.
For dates and times that the EDI transcribes in the format RRRRMMDDHHmm we
will use the standard XSD type xs:dateTime, and for dates in the format
RRRRMMDD the standard XSD type xs:date, with indication as follows:
RRRR – calendar year ; MM – calendar month; DD – calendar day
HH – hour of day ; mm – minute of hour
5.4. Numerical data format
Numerical data re given in standard formats of XSD -
xs: decimal places (with maximum two decimal places)

xs: integer for whole numbers (or xs: non-negative integer for natural
numbers).
18/88
6. MESSAGE FORMATS
Applied messages sent between parties to electronic data exchange, i.e. between
the NG supplier and the DNO:
List of messages
Message
Message code Description
format
S02 Total heating value UTILMD
S41 Notice of change of customer at PoD UTILMD
S42 Request to disconnect non-payer UTILMD
S43 Request to connect non-payer UTILMD
S46 Request to disconnect UTILMD
S48 Request to reconnect UTILMD
S49 Request for a claim UTILMD
S50 Info-order UTILMD
S60 Notice of conclusion of order UTILMD
S70 Information about change to equipment UTILMD
S80 Reading MSCONS
S82 Corrective reading, cancel reading MSCONS
S89 Reading reported by customer UTILMD
S92 Mass reading MSCONS
E03(STS=Z16) Change of business partner UTILMD
E03(STS=Z25) Change of PoD UTILMD
E01(STS=E02) Request for commencement of supply UTILMD
E02(STS=E01) Request for termination of supply UTILMD
E01(STS=E03) Request for change of supplier UTILMD
E01(STS=E01) Notice on change of customer UTILMD
Cancellation of request for change of UTILMD
E01(STS=E05) supplier
E01(STS=E14) Negative reply to change of supplier UTILMD
E01(STS=E15) Positive reply to change of supplier UTILMD
E02(STS=E01) Notice on termination of supply UTILMD
6.1. Definition of message formats
6.1.1. MSCONS message format

The message is in accordance with UN/EDIFACT specifications, version D.04B. This
message is used for transferring measured data (reading data) from the distribution
network operator to gas supplier.
A detailed definition of the attributes and the data are described in the Annex No. 3.1
- MSCONS message format.
Scheme of MSCONS message segments
19/88
MSCONS
UNH Message header
BGM Beginning of message
DTM Document date
NAD Address of off-take point and addressee for correspodence
CTA Contact details
COM Communication information (target / source e-mail)
UNS Beginning of data section
NAD NAD – Content of MSCONS message
UNT End of message
20/88
LOC Identifier of of-take point
RFF Reference (e.g. in case of correction)
LIN Item (counter)
QTY Quantity readout
DTM Period
CCI Additional information ( classification)
MEA Values
21/88
6.1.2. UTILMD message format

message is used for transferring master data and information necessary for providing
services at the point of delivery.
A detailed definition of the attributes and the data are described in the Annex No. 3.2
- UTILMD message format.
Scheme of UTILMD message segments
UTILMD
UNH Message header
DTM Document date
CTA Contact details
IDE Master Data
UNT End of message
22/88
IDE Master Data
DTM Document date
STS Status
FTX Free text
AGR Contract (identification or data of contract)
RFF Reference
CAV Classification value
SEQ Item (register)
CTA Contact details
23/88
7. DATA EXCHANGE SCENARIOS
The scenarios define the specific situations under which exchange of data takes place
between the NG supplier and the DNO. The exchange of data is automatic between the
information systems of the DNO and the NG supplier.
The following chapter outlines the processes involved in data exchange between entities on
the liberalised market with gas. Processes are integrated and dependent on other processes.
We can refer to this dependent relationship of various data exchange processes as the data
exchange scenarios.
Depending on the type of exchanged data, scenarios are divided into five classes:
 Scenarios for exchange of master data
 Scenarios for exchange of measurement data
 Scenarios for exchange of data on distribution services
 Scenarios for exchange of data about the process of changing supplier
 Scenarios of periodically exchanged data
7.1 Scenarios for exchange of master data
Within the group of scenarios for the exchange of master data there are scenarios by which
contractual or master data are exchanged between individual key entities on the gas market.
The scenarios outline the exchange of basic data required for concluding and administering
contractual and technical data of the partner (customer) at the PoD.
7.1.1. Concluding contract for PoD
7.1.1.2 Description of the scenario Concluding contract on access to distribution

network and the distribution of gas to PoD
The process is initiated by the supplier by sending message E01 Request for
connection of new offtake. This message transfers technical master data.
On the side of the DNO, master data are recorded and a service order is
created for installation of a device at the PoD. The service order is released
Steps of after confirmation of the request for distribution for the respective PoD. In the
scenario case of new PoD, release of the order is subject to acceptance and
confirmation of the request for establishment of connection and payment of
the connection fee. Once the service work has been done the DNO sends the
supplier the message S70 Information on installation of gas meter and
message S60 Request for reaction to service work.
24/88
7.1.1.3 Scenario for Concluding contract on access to distribution network and the
distribution of gas to a PoD
Supplier Distributor
New Supplier SPP-D
Request
for new
contract
New contract Recording of

contractual
data
Dispatch of Recording
E01 (STS=E02)
message TKD
Request to connect new offtake
Distribution
contract
Installation
of device
Recording
Dispatch of
info-record S70
message
device
Information on installation /
uninstallation of gas meter
Active offtake
Displaying of Dispatch of
S60
message message
Reaction to request
for service activity
Completion of
contact with
customer
25/88
7.1. 2. Terminating Contract for Point of Delivery
7.1.2.1. Description of the scenario Terminating contract on access to distribution

network and the distribution of gas to a PoD
The gas supplier sends a Request for disassembly of the device to the DNO
Steps of by message E02. The DNO performs service work, uninstalls the device and
scenario sends information about it back to the supplier by messages S70 Information
on disassembly of device and S60 Reaction to request for service work.
7.1.2.2. Diagram of scenario Terminating contract on access to distribution network

and the distribution of gas to a PoD
New Supplier SPP-D
Request
to terminate
supply
contract
Termination
of supply
contract
Dispatch of Uninstallation
E02 (STS=E01)
message of device
Žiadosť na demontáž prístroja
Uninstallation
Dispatch of
of info-record S70
message
of device
Offtake
terminated
S60
message message
Reaction to request
Termination of
contract
with customer
26/88
7.1.3. Change of customer at PoD
7.1.3.1. Description of scenario Change of customer at PoD
After creating the new supply contract for the existing PoD the gas supplier
sends information to the DNO by message S41 as Notice of change of
customer at PoD. This message transfers the main reading that the customer
states when deregistering.
If the reading is trustworthy, the status given by the customer using message
S80 is confirmed. The scenario closes with message S60 as Reaction to
Steps of
request for service activity.
scenario
If the reading given by the successor customer is evaluated as trustworthy, a
service order is created in the system of the DNO for a check reading, which
once performed is transferred by message S80. The scenario is concluded by
message S60 as a Reaction to request for service activity.
New technical master data of the customer at the PoD are transferred by
message E01 as Request for a change.
27/88
7.1.3.2. Scenario of Change of customer at PoD
New Supplier SPP-D
Request for
registration of
change at PoD
Change of
customer
at PoD
Dispatch of Reading
S41
message check
Reporting change of
customer to CM
S60
message message
Reaction to request
Unreliable Reliable
reading reading
Inputting
results of
reading
Recording Dispatch of
S80
reading message
Readings
Dispatch of Change of
E01(STS=E03)
message TKD
Request for making

change of supplier
TKD
updated
28/88
7.1.4. Change of customer name
7.1.4.1. Description of scenario Change of customer name
Based on the request for a change, the gas supplier sends the DNO
Steps of information about the change of customer name at the PoD using the
scenario message E03. Based on the received message, the DNO updates the master
data of the customer
7.1.4.2. Scenario of Change of Customer name
New Supplier SPP-D
Request for
change of
customer
name
Change of
customer
name
Dispatch of Change of
E03 (STS=Z16)
message customer name
Change of customer at PoD
Updated
customer
name
field
29/88
7.1.5. Replacement of device
7.1.5.1. Description of scenario Replacement of device
After creating the service order, the DNO uninstalls the device at the PoD,
Steps of
installs a new device and informs the supplier about the intervention by
scenario
generating Information about installation of gas meter by message S70.
7.1.5.2. Scenario Replacement of device
New Supplier SPP-D
Installation
of device
Recording
Dispatch of
info-record S70
message
device
Active offtake
30/88
7.2. Scenario for exchange of measurement data
The group of scenarios describes the situation where there is an exchange of measurement
data or data relating to a claim between individual key entities on the gas market.
7.2.1. Regular reading
7.2.1.1. Description of scenario Regular reading
The DNO sends the results of the readings to the supplier by message S92
Steps of (see process “Mass input reading“), or in cases of individual entry by message
scenario S80.
7.2.1.2. Scenario of Regular reading

New Supplier SPP-D
Periodic
reading of
balance
Inputting
results of
reading
S80
reading message
Readings
Record of
reading was
generated
31/88
7.2.2. Extraordinary reading
7.2.2.1. Description of scenario Extraordinary reading
An extraordinary reading requested by the gas supplier initiates at the DNO a

Steps of service intervention and a reading of the said PoD at a time other than that
scenario defined in the Contract on distribution.
The reading is transferred by message S80 to the gas supplier.
7.2.2.2. Scenario of Extraordinary reading
New Supplier SPP-D
Immediate
reading
Inputting
results of
reading
S80
reading message
Readings
Record of
reading was
generated
32/88
7.2.3. Corrective reading
7.2.3.1. Description of scenario Corrective reading
Based on the request the DNO makes a corrective reading, enters it into the
Steps of
information system and processes it. It then generates message S82 –
scenario
Information on correction of reading, which it sends to the gas supplier.
7.2.3.2. Scenario of Corrective reading
New Supplier SPP-D
Correction of
reading
Reading –
recording
corrected
reading
Change of
Dispatch of
reading or S82
message
cancellation
Correction of reading
Record on
reading
changed or
cancelled
33/88
7.2.4. Mass input reading
7.2.4.1. Description of scenario Mass input reading
Mass input readings are transferred daily at 04:00. The transfer includes a
large volume of readings that were entered to the system during the previous
day from support systems for collecting reading data. In the case of individual
input of a reading, the reading will be sent by message S80 (see process
Steps of “Regular reading””)
scenario The transfer comprises message S92 – Mass readings and aggregated
messages with readings. Message S92 contains a reference to all generated
messages with readings in the given batch.
Individual files with readings and the message with the reference will be
transferred to and recorded at the gas supplier.
7.2.4.2. Scenario of Mass input reading
New Supplier SPP-D
Immediate
reading
Inputting
results of
Files reading
with
readings
S92
reading message
Hromadné odpočty
Files
Record of with
reading was readings
generated
34/88
7.3. Scenarios for exchange of information on distribution services
The scenarios describe the exchange of data between the DNO and the gas supplier
required for securing services linked to the distribution of gas.
7.3.1. Request for disconnection due to non-payment
7.3.1.1. Description of scenario Request for disconnection due to non-payment
Upon repeated non-payment for supplied services and gas at a business

partner (customer) the supplier sends to the DNO a Request for disconnection
of non-payer by message S42. Based on the service order generated by the
Steps of
transfer the DNO disconnects the device and makes a reading. Following
scenario
completion of the service intervention the DNO is obliged to send the supplier
information about readings by message S80 and Reaction to request for
performed service activity by message S60.
7.3.1.2. Scenario of Request for disconnection due to non-payment
35/88
7.3.2. Request for reconnection of non-payer
7.3.2.1. Description of scenario Request for reconnection of non-payer

New Supplier SPP-D
Request for
disconnection
due to non
-payment
Entering
request for
disconnection
Inputting
Dispatch of
S42 results of
message
reading
Request for disconnection
of non-payer
S80
reading message
Readings
Record of
reading was
generated
S60
message message
Reaction to request
Completion of
contact with
customer
The gas supplier sends the DNO the message S43 Request for reconnection
of non-payer. Based on the service order generated by the transfer, the DNO
Steps of
connects the device and makes a reading, which it sends by message S80. At
scenario
the same time the DNO sends also a Reaction to request for service activity
by way of message S60.
36/88
7.3.2.2. Scenario of Request for reconnection of non-payer
New Supplier SPP-D
Request for
reconnection of
non-payer
Restoration
of supply
Dispatch of Installation
S48
message of device
Application for
reconnection of non-payer
Recording
Dispatch of
info-record S70
message
device
Active offtake
S60
message message
Reaction to request
Completion of
contact with
customer
37/88
7.3.3. Request for disconnection
7.3.3.1. Description of scenario Request for disconnection from customer
Through the gas supplier the customer request the DNO to shut-off of the gas
supply for a determinate period. The supplier by recording the request for
disconnection/interruption of offtake by way of message S46 requests the
Steps of
disconnection of the PoD.
scenario
Based on the service order generated by the transfer the DNO uninstalls the
device and sends message S70. The scenario is concluded by message S60
as Reaction to request for service activity.
38/88
7.3.3.2. Scenario Request for disconnection from customer
New Supplier SPP-D
Request for
interruption
of supply
Interruption
of supply
Dispatch of Uninstallation
S46
message of device
Application for disconnection

/interruption of supply
Uninstallation
Dispatch of
of info-record S70
message
of device
Offtake
terminated
S60
message message
Reaction to request
Completion of
contact with
customer
39/88
7.3.4. Request for reconnection
7.3.4.1. Description of scenario Request for reconnection
If it is possible to restore the supply of gas, the supplier sends the DNO a
request for reconnection using message S48. Based on the service order
Steps of
generated by the transfer the DNO installs the device and sends message
scenario
S70. At the same time the DNO sends message S60 Reaction to request for
service activity.
7.3.4.2. Scenario of Request for reconnection
New Supplier SPP-D
Request for
reconnection
Restoration
of supply
Dispatch of Installation
S48
message of device
Application for
reconnection of non-payer
Recording
Dispatch of
info-record S70
message
device
Active offtake
S60
message message
Reaction to request
Completion of
contact with
customer
40/88
7.3.5. Request for Info-order
7.3.5.1. Description of scenario Request for Info-order
The initiative comes from the supplier, which generates an Info-order in the
Steps of
system and sends it by message S50 to the DNO. The obligation of the DNO
scenario
is to carry out activity based on which it can send back message S60 to the
supplier as a reaction to request for service activity.
7.3.5.2. Scenario of Request for Info-order
New Supplier SPP-D
Request
Inputting
request
Dispatch of Performance
S50
message of activity
Info-order
S60
message message
Reaction to request
Completion of
contact with
customer
41/88
7.3.6. Request for a claim concerning reading
7.3.6.1. Description of scenario Request for claim concerning reading
Following receipt of a claim from a customer the supplier records and sends
the claim to the DNO.
Claim concerning reading
If the supplier discovers an error in the received reading, it also sends the
claim to the DNO by message S49. Following receipt of the message, the
DNO sets up a service order for the reading claim. If the claim is
substantiated, it makes a service intervention. After the service intervention
the DNO checks the reading data and sends back to the supplier information
Steps of on the corrected reading by message S82.
scenario Claim concerning device - legal exam (S51 - REUS)
After receipt of the message the DNO sets up a service order for the device
claim REUS. If the claim is substantiated, it makes a service intervention.
Following the service intervention the DNO orders examination of the device
and proceeds with correction of the gauge according to the discovered faults.
Reading result is not given.
The claim is completed by message S60 as a reaction to request for service

activity.
42/88
7.3.6.2. Scenario of Request for claim concerning reading
New Supplier SPP-D
Claim
Claim
Inputting
Dispatch of
S49 corrected
message
reading
Claim concerning
reading
Correction of Dispatch of
S82
reading message
Record of
reading was
generated
S60
message message
Reaction to request
Completion of
contact with
customer
43/88
New Supplier SPP-D
Claim
Claim
Inputting
Dispatch of
S49(STS=REME) corrected
message
reading
Claim concerning
reading
Correction of Dispatch of
S82
reading message
Record of
reading was
generated
S60
message message
Reaction to request
Completion of
contact with
customer
44/88
7.3.6.3. Scenario of Request for claim concerning device
Supplier SPP-D
Claim
Claim
Dispatch of Gas meter

S 49 (STS=REUS)
message instalation
Claim concerning device
Establishment
Dispatch of
of gas meter S70
message
inforecord
Offtake
is active
S60
message message
Reaction to request
Completion of
contact with
customer
45/88
7.3.7. Request for self-reading, Change of contractual tariff
7.3.7.1. Description: Request for self-reading, Change of contractual tariff
With a Request for self-reading the supplier sends message S89 to the DNO
with the input reading reported by the business partner (customer). In the
system of distribution the reading is verified and if trustworthy, it is confirmed
by transfer of S80. If the reading is untrustworthy, a service order is set up in
the system of distribution, a reading is made and this is sent to the supplier by
message S80. The process is completed by the transfer of message S60
Reaction to request for service activity.
Steps of
scenario
Upon a change of contractual tariff the supplier inputs into the system the
reading reported by the business partner (customer) and sends message S89
to the DNO. In the system of distribution the reading is checked and if
trustworthy, is confirmed by transfer of S80. If the reading is untrustworthy, a
service order is set up in the system of distribution, a reading is made and this
is sent to the supplier by message S80. The process is completed by the
transfer of message S60 Reaction to request for service activity.
7.3.7.2. Scenario of Request for self-reading
7.3.7.3. Scenario of Change of contractual tariff
46/88
7.4. Scenarios for change of gas supplier
New Supplier SPP-D
Customer
reports
reading
Inputting
reading
from
customer
Dispatch of Reading
S89
message check
Input of self-reading
S60
message message
Reaction to request
Completion of
contact with
customer
Unreliable Reliable
reading reading
Inputting
results of
reading
S80
reading message
Readings
Record of
reading was
generated
47/88
New Supplier SPP-D
Customer
reports
reading
Inputting
reading
from
customer
Dispatch of Reading
S89
message check
Input of self-reading
S60
message message
Reaction to request
Completion of
contact with
customer
Unreliable Reliable
reading reading
Inputting
results of
reading
S80
reading message
Readings
Record of
reading was
generated
The scenarios for a change of supplier describe all the processes that have to be executed
manually or automatically so that the customer can receive natural gas from another supplier
(trader). The following parties are involved in the process:
 customer
 previous supplier (previous trader)
 new supplier (new trader)
 Distribution Network Operator (DNO)
48/88
7.4.1. Change of gas supplier to PoD from perspective of DNO
7.4.1.1. Description of scenario Change of gas supplier to PoD from perspective of

DNO
The process for changing supplier starts at the new supplier. Following
identification or the recording of commercial and technical master data, it
sends the DNO a request to conclude a gas distribution contract. The DNO
receives the request, registers it in the system and informs the former supplier
about the request for a change of supplier. The DNO concludes in the system
the gas distribution contract with the new gas supplier. The new supplier
sends the DNO a request for actual performance of the change of supplier.
The DNO receives the request for a change of supplier by message E01. After
receipt of the request for a change the DNO checks the data of the message
and if not accepting the requirements it sends the new supplier message E01
Rejection of request for change of supplier. If all the criteria are satisfied, the
Steps of request is accepted and the DNO assigns the PoD of the customer to the new
scenario supplier. The DNO sends a confirmation of the change to the new supplier by
message E01 and to the previous supplier a notice of change of supplier by
message E02. The new supplier is entitled to request the cancellation of a
change of supplier by message E01 Cancellation of request for change of
supplier, provided this has not yet been confirmed.
If the cancellation is confirmed, message E01 Rejection of request to change
supplier is sent to the new supplier. If the request has already been confirmed,
then the cancellation is rejected by the generation and dispatch of message
E01 Confirmation of request for a change of supplier. After processing the
change of supplier at the DNO, an info-record about the device is generated,
and also a service order for making a reading is generated and executed,
which by law is then sent to the former supplier by message S80 as historical
data for billing and to the new supplier as the initial meter reading.
49/88
7.4.1.2 Scenario of Change of supplier to PoD from perspective of DNO
New supplier Previous supplier PDS
Previous
New Supplier Supplier SPP-D
Request
of supplier
change
Sending
request
of distribution
contract
Recieving
request of
distribution
contract
Recieving
Notify
information about
Previous
delivery request of
Supplier
supplier change
Information about
delivery request of
supplier change
Make a gas Make

delivery a distribution
contract contract
Sending request
of change
supplier
executing
Processing
Dispatch of of change
E01(STS=E03)
message supplier
request
Request for making
change of supplier
Vytvorenie
Request
požiadavky
is NOT
na storno zmeny
acceptable
dodávateľa
Recieving
Dispatch of of suplier
E01(STS=E05)
message change
canceling
Cancel Supplier change
Cancelling
is allowable
Cancelling Request
Dispatch of
is NOT IS
message
allowable acceptable
Refusal
E01(STS=E14)
processing
Refusal supplier change
Refusal
of supplier
change is
executed
Executing of
Dispatch of
confirmation and Confirmation
message
contract making
Confirmation of (for new supplier)
supplier change
Contract
is made Spracovanie
Dispatch of
oznámenia o zmene E02(STS=E01)
message
dodávateľa
Oznámenie (starému dodávateľovi)
zmeny dodávateľa
Zmluva
so zákazníkom
je ukončená
Recording
Dispatch of
info-record S70
message
device
Active offtake Inputting

results of
reading
S80
reading message
Readings
Record of
meter reading
is done Recording Dispatch of
S80
reading message
Readings
Record of
meter reading
is done
50/88
7.5. Scenarios for periodically exchanged data
7.5.1. Transmission of Gross Calorific Value
7.5.1.1. Description of scenario: Transmission of Gross Calorific Value
The system allows the automatic and periodic transmission of heat values to
the gas supplier, which are needed to convert the gas consumption in cubic
meters to kWh.
The transmission process is triggered by a periodic timer or possibly triggered
by the user. After the transfer the heat values will be saved at the supplier and
Steps of
subsequently used in conversions when billing.
scenario
The report contains heat values defined for a given date. The characteristics
of the point of delivery are used for the transmission. The number of the point
of delivery (PoD) mentioned in the message is fictive – the heat values are
generally applicable.
7.5.1.2. Scenario of Transmission of Gross Calorific Value
O...
Supplier SPP-D
.
Periodically
activated
Recording of
Dispatching
combustion S02
message
heat values
Combustion heat values
Data
were
recorded
51/88
8. FORMATS OF XML MESSAGES - XSD SCHEMES
The XML in e-mail attachments containing exports and imports must fully comply with
the defined XSD schemes:
- Universal scheme for MSCONS
- Schemes for each message type that are derived from MSCONS
- Universal scheme for UTILMD
- Schemes for each message type that are derived from UTILMD
- Mass reading scheme
The schemes will be published at - http://www.spp-

distribucia.sk/Portal3en/DesktopDefault.aspx?tabid=1121.
9. INTERFACES BETWEEN DNO SPP- DISTRIBÚCIA, A.S. AND NATURAL GAS

SUPPLIERS
List of processes covered by the Distribution Information System (DIS)
For the completeness of the range of technical specifications of data exchange

between DNO and natural gas suppliers it is necessary to have indispensable
communication via the Distribution Information System of the DNO.
The interfaces are implemented in the form of graphical user interface (Web GUI), via
which the supplier using his login and password assigned can interactively submit via
the Internet his enquiries and also obtain information on the results of his activities.
These are primarily:
Creating a new supplier in the DIS information system

After all requirements defined by the legislation are met, a new supplier is created in
the DIS IS. The new supplier receives his login and password and the role for
performing the relevant activities listed below is assigned to him. In case of the
supplier’s termination of operation the access to the DIS is cancelled
Contract on access to distribution network and gas distribution

Type of contracts:
annual contract,
short-term contract,
long-term contract
Distribution requests can be entered via the Web GUI or in a mass form using a text
file of a defined structure, sending it to the DNO and its subsequent import to the
system. The information on the confirmation / refusal of the access request to
52/88
distribution network and gas distribution for the respective supplier is accessible via
the Web GUI.
Nominations, renominations
Entering provisional monthly, provisional weekly and daily nominations as well as
renominations is possible in accordance with the regulations in force via the Web GUI
interface. The information on confirmation / refusal of nomination is accessible to the
respective supplier via the Web GUI.
Daily and cumulative deviation as part of network balancing

The calculation of deviations is conducted in accordance with the regulations in force
and the respective supplier has access to the information indicated on his account via
the Web GUI.
Billing
The billing of distribution capacity, exceeding allowable cumulative deviation and
contracted daily limit is conducted in accordance with the regulations in force and the
contract in force on the access to distribution network and gas distribution with the
natural gas supplier. The outgoing invoices are available for reading via the Web GUI
and similarly, also detailed information on the supplier’s individual points of delivery
(PoD) that were used for calculations of the invoice. The official invoice for payment
is officially sent to supplier in a paper form by post.
Change of supplier at point of delivery

Submitting distribution requests (conducted under clause 2) in case of changing
supplier, monitoring given conditions whose fulfilment is a condition for change of
supplier, (household, others) and confirming distribution contract in case of changing
supplier are available via the Web GUI.
10.LIST OF ANNEXES
Annexe Name
Annexe No. 3.1 MSCONS message formats
Annexe No. 3.2 UTILMD message formats
53/88
Annex No. 3.1
MSCONS message format
11.INTRODUCTION
This document is an implementation guide for MSCONS type message (Metered

Services Consumption Report). It describes the UN/EDIFACT message MSCONS in
details.
12.MESSAGE FORMATS
12.1. Data types

Acronym
Description
types
R-NN String, of length NN
N-NN.n Number, of total length NN, with a maximum of n decimal places
according to the rules set out in chapter 5 - General Principles of
Technical Specifications of Data Exchange.
If the total length of number is not indicated, the minimum
supported length is 15.
If the number of decimal places is not indicated, at least 4 decimal
places are supported.
C-NN Integer, of length NN (must not contain digits in the decimal part)
DT Date and time according to the rules set out in chapter 5 - General
Principles of Technical Specifications of Data Exchange.
D Date according to the rules set out in chapter 5 - General
12.2. Format definition

message is used for transferring measured data (reading data) from the distribution
network provider (DNO) to natural gas supplier.
Scheme of segments
54/88
MSCONS
UNH Message header
DTM Document date
CTA Contact details
UNS Beginning of data section
UNT End of message
55/88
LOC Identifier of of-take point
RFF Reference (e.g. in case of correction)
LIN Item (counter)
DTM Period
MEA Values
56/88
12.3. Chart of segments
12.3.1. Document header

Num.
Segment name / Content
/ Description EDIEL Content - remark
Field name - value
Type
Message header
> UNH 1-1 Message header
data
REFERENCENU R-14 Message 0062 Unique message
MBER identifier identifier
IDENTIFIER R-6 Message type 0065 MSCON
version identifier S
VERSIONNUMBE R-3 Message type 0052 D
R version
RELEASENUMBE R-3 Release of 0054 04B
R message type
version
CONTROLAGEN R-2 Agency 0051 UN
CY
> BGM 1-1 Beginning of message
NAME R-3 Message type 1001 S80 Reading
code
S82 Corrected reading,
reading cancellation
S92 Mass reading
(reference
message)
CODELISTAGEN R-3 Organization 3055 60 Assigned by
CY national
organization
FULLNAME R-35 Document name 1000 Document type
name
DOCUMENTNUM R-35 Message 1004 Unique identifier
BER identifier
VERSION R-9 Version of 1056 3.00
electronic
document
DOCUMENTFUN R-3 Message 1225 9 Original copy
C function
Date and time of
> DTM 1-1 Date and time
message creation
DATUMQUALIFIE R-3 Purpose 2005 137 Date of message
R creation
DATUM DT Date and time 2380
(35)
Name and address
Typ segmentu
> 2-2 Name and address of communicating
NAD s označením:
partner
NAD_1 1 Sender (ACTION field = “MS”)
NAD_2 1 Addressee (ACTION field = “MR”)
57/88
ACTION R-3 Partner role 3035 MR Recipient
MS Sender
PARTNER R-35 Partner number 3039 Format:
SKSPPDAAAAA*
A – partner name
acronym
CODELISTAGEN R-3 Organization 3055 60 Assigned by
CY national
organization
NAMEADDRESS1 R-35 Designation of 3124
partner
PARTNERNAME1 R-35 Partner name 3036
PARTNERNAME2 R-35 Partner name 3036
STREET1 R-35 Street 3042
STREET2 R-35 Number 3042
CITY R-35 City 3164
REGION R-9 Region 3229
ZIPCODE R-9 ZIP code 3251
COUNTRY R-3 Country 3207 SK
>> CTA 1-1 Contact details
CONTACTNAME R-35 Name of contact 3412
person or branch
Communication
>>> COM 1-n
contact
COMMNUMBER R- Address 3148
512
COMMQUALF R-3 Contact type 3155 EM Electronic mail
code
12.3.2. Document data
Num Conte
Segment name / EDIE
./ Description nt - Content - remark
Field name L
Type value
> UNS 1-1 Beginning of data section identifier
SECTION_ID R-1 Section identifier 0081 D Data
Name of
> NAD 1-n Name and address information
provider
ACTION R-3 Partner role 3035 GN Information
provider
PARTNER R-35 Partner number 3039 Format:
SKSPPDAAAAA
A
A – partner
name acronym
CODELISTAGENC R-3 Organization 3055 60 Assigned by
Y national
organization
>> LOC 1-n Location identification
PLACE_QUALIFIE R-3 Place type code 3227 172 Reporting
58/88
R location
PLACE_ID R-35 Place of delivery 3225
number (PoD)
CODE_LIST_ R-3 Organization 3055 89 Code assigned
RESPONSIBLE_ by distributor
AGENCY_1
>>> RFF 1-n Reference
REFERENCEQUAL R-3 Reference type code 1153 MG Device number
IFIER (Serial number)
MSC Aggregate
readings (file)
REFERENCENUM R-35 Reference 1154 Reference -
BER Device number
or ID of
referenced
document with
readings
>>> LIN 1-n Reading record
LINE_ITEM_NUMB R-6 Number 1082 Line number
ER
ACTION_REQUES R-3 Action code 1229 1 Add
T_ NOT_CODE
>>>> QTY 1-1 Quantity
QUANTITY_QUALI R-3 Processing type 6063 220 Regular reading
FIER code (purpose)
427 Reading
correction
182 reading
cancellation
QUANTITY N- Quantity 6060 Number (2
15.2 decimal places)
MEASURE_UNIT_ R-8 Unit of measure 6411 MTQ Cubic meters
QUALIFIER
>>>> Date and time of
DTM 1-1 Date and time
> reading
DATUMQUALIFIER R-3 Purpose 2005 368 Date of reading
DATUM DT Date and time 2380
(35)
Characteristics
>>>> CCI 0-n Characteristics segment for
quantity
PROPERTY_CLAS R-3 Type of 7059 9 Reading
S characteristics
CHARACTERISTIC R-17 Code of 7037 Z_2 Reason
_ID characteristics
Z_5 Planned reading
type
Z_7 Status
Z_8 Reading type
Z_9 Active / Inactive
59/88
Num Conte
Segment name / EDIE
./ Description nt - Content - remark
Field name L
Type value
Segment of
>>>>
MEA 1-1 Measured values measurement
>
attributes
MEASUREMENT_ R-3 Value code 6155 Code from code book for
ATTRIBUTE_COD classification Z_2, Z_5,
E Z_7, Z_8, Z_9
MEASUREMENT_ R-70 Text description of 6154 Code from code book for
ATTRIBUTE value classification Z_2, Z_5,
Z_7, Z_8, Z_9
> UNT 1-1 End of message
NUMSEG C-6 Number of 0074 Integer
transferred
segments
REFNUM R-14 Reference number 0062
12.3.3. Code book
Characteristi Content
Content - description
cs - value
Z_2 - Reason
01 Periodical reading
02 Progressing reading with settlement
Final reading at
03 registration/deregistration
04 Verification reading
06 Reading upon registration
08 Reading due to technical installation
09 Progressive reading without settlement
10 Check reading
11 Reading after programming/adjustment
12 Reading due to technical removal
Reading prior to
16 programming/adjustment
17 Reading upon structure change of point
of delivery
21 Reading for technical installation in
connection with settlement
22 Reading due to technical removal in
24 Change of installation
25 Change of removal
Reading after change of log. number of
29 counter
60/88
Z_5 - Planned reading type
01 Reading for public utilities
02 Reading for customers
03 Automatic estimate
04 Derived reading
Z_7 - Status
0 Reading command created
1 Billable
2 Blocked automatically
3 Blocked by agent
4 Released by agent
5 Checked independently
7 Settled
Characteristi Content
Content - Description
cs - value
Z_8 - Reading type
01 Reading for public utilities - SAP
02 Reading for customer - SAP
03 Automatic estimate - SAP
04 Derived reading - SAP
05 New estimate after overestimate - SAP
06 Internet reading - SAP
Result of reading, upload, receipt of
07 invoice
Estimate of readings from DIS -
13 individual transfer
84 Reading without bar code, correction
Correction of estimate from DIS - mass
85 transfer
86 Reading correction via GMS
Correction of meter reading sheet -
87 mass input
Correction of estimate of readings -
88 mass transfer
89 Correction of readings - PSION
94 Reading without bar code
Estimate of readings from DIS - mass
95 transfer
96 Reading via GMS
97 Meter reading sheet - mass input
98 Estimate of readings - mass transfer
99 Mass transfers - PSION
B1 KOSK_SAM Auto reading
61/88
B2 KOSK_SAK Check of auto reading
ODZP_ENE Restoration of supply after
D1 payment
D2 ODZP_ENZ Restoration of supply new
E1 PDZP_ENE Cut-off
PDZP_ENP Unauthorized consumption
E2 ext.
PDZP_INP Unauthorized consumption
E3 int.
H1 REME_EIP Other complaint
H2 REME_EKM Check of measurement
H3 REME_ENS Complaint implausible
H4 REME_EOD Complaint of reading ext.
H5 REME_IOD Complaint of reading int.
H6 REME_NOS Complaint of natural gas
consumption estimate
H7 REME Completion of consumption
calculation - stuck counter
HD Consumption supplement
Automatic estimate - extraordinary
HM measurement
ZMPR_EKO Change of customer at
K1 point of delivery
KL Postal card
PZOD_EUO Customer request
L1 consumption cut-off
L2 PZPD_EOO Customer request
restoration of consumption
Z_9 - Active / Inactive
01 Active
62/88
Annex No. 3.2
UTILMD message format
13.INTRODUCTION
This document is an implementation guide for UTILMD type message (Utility Master
Data). It describes the UN/EDIFACT message UTILMD in details.
The UTILMD message is sent between the natural gas supplier and the distribution
network operator (DNO). It is used to transfer data about premises and services and
can be used to request information.
Examples of use:
Information on final customer connection
Information on change of supplier
Information on contract termination with final customer
Information on change of characteristics of final customer’s device
Information on change of supplier
Information on change of premises or service characteristics
63/88
14.FORMAT OF MESSAGES
14.1. Data types

Acronym
Description
types
R-NN String, of length NN
N-NN.n Number, of total length NN, with a maximum of n decimal places
If the number of decimal places is not indicated, at least 4 decimal
places are supported.
C-NN Integer, of length NN (must not contain digits in the decimal part)
DT Date and time according to the rules set out in chapter 5 - General
D Date according to the rules set out in chapter 5 - General
14.2. Message structure definition

message is used for transferring master data and information necessary for providing
services at the point of delivery.
Scheme of segments
64/88
UTILMD
UNH Message header
DTM Document date
CTA Contact details
IDE Master Data
UNT End of message
65/88
IDE Master Data
DTM Document date
STS Status
FTX Free text
AGR Contract (identification or data of contract)
RFF Reference
SEQ Item (register)
CTA Contact details
66/88
14.3. Chart of segments
14.3.1. Document header
Num. Conte
Segment name /
/ Description EDIEL nt - Content - remark
Field name
Type value
Message header
> UNH 1-1 Message header
data
REFERENCENUM R- Message 0062 Unique message
BER 14 identifier identifier
IDENTIFIER R-6 Message 0065 UTIL
type version MD
identifier
VERSIONNUMBER R-3 Message 0052 D
type version
RELEASENUMBE R-3 Release of 0054 04B
R message
type version
CONTROLAGENC R-2 Agency 0051 UN
Y
> BGM 1-1 Beginning of message
NAME R-3 Message 1001 E01 New consumption
type code connection request
E02 Termination request
E03 Change of master
data
S02 Combustion heat
values
S41 Notification of
customer change to
PoD
S42 Disconnection
request of non-
paying customer
S43 Connection request
of non-paying
customer
S46 Disconnection
request
S48 Reconnection
request
S49 Complaint request
(reading, device)
S50 Info order
S60 Order completion
notification
S70 Information on
change on device
67/88
S89 Reading reported by
customer
CODELISTAGENC R-3 Organization 3055 60 Assigned by national
Y organization
FULLNAME R- Document 1000 Document type name
35 name (defined in the list of
messages, TSDE
chapter 6)
DOCUMENTNUMB R- Message 1004 Unique message
ER 35 identifier identifier
VERSION R-9 Version of 1056 3.00
electronic
document
DOCUMENTFUNC R-3 Message 1225 9 Original copy
function
Date and time of
> DTM 1-1 Date and time
message creation
DATUMQUALIFIER R-3 Purpose 2005 137 Date of message
creation
DATUM DT Date and 2380
(35) time
Num. Conte
Segment name /
Field name
Type value
Name and address of
NAD segment type
> 2-2 Name and address communicating
with tag
partner
NAD_1 1 Sender (ACTION field = “MS”)
NAD_2 1 Addressee (ACTION = “MR”)
ACTION R-3 Partner role 3035 MR Addressee
MS Sender
PARTNER R- Partner 3039 Format:
35 number SKSPPDAAAAA*
A – partner name
acronym
CODELISTAGENC R-3 Organization 3055 60 Assigned by national
Y organization
NAMEADDRESS1 R- Designation 3124
35 of partner
PARTNERNAME1 R- Partner 3036
35 name
PARTNERNAME2 R- Partner 3036
35 name
STREET1 R- Street 3042
35
STREET2 R- Number 3042
35
68/88
CITY R- City 3164
35
COUNTRY R-3 Country 3207 SK
>> CTA 1-1 Contact details
CONTACTNAME R- Name of 3413
35 contact
person or
branch
>>> COM 1-n Communication contact
COMMNUMBER R- Address 3148
512
COMMQUALF R-3 Contact type 3155 EM Electronic mail
code
14.3.2. Document data

Num. Conte
Segment name /
Field name
Type value
> IDE 1-n IDE identification
OBJECT_TYPE R-3 Object type 7495 24 Transaction
code
Date and time of
>> DTM 1-n Date and time
message creation
DATUMQUALIFIER R-3 Purpose 2005 92 Required start date
93 Required end date
157 Date of validity
158 Confirmation of start
date
159 Confirmation of end
date
171 Date of referenced
document
368 Date of reading
409 End date of activity
(required)
471 Next possible date
549 Order date (real)
DATUM DT, Date (and 2380 CCYYMMDDHHmm
D time) or CCYYMMDD;
(35) Note: - the general
XSD scheme will
have
xs:anySimpleType
data type, XSD
schemes for specific
69/88
messages will have
specific type xs:date
or xs:dateTime
(according to
DATUMQUALIFIER
type)
>> STS 0-n Status
CATEGORY R-3 Status 9015 7 Transaction
category
code
E01 Respond to request
2 Order administration
CATEGORY_AGE R-3 Organization 3055 PDS
NCY
Num. Conte
Segment name /
Field name
Type value
REASON_1_ R-3 Action code 9013 Category code 7 -
DESCRIPTION_C Transaction
ODE
Message type E01 -
New consumption
connection request
E01 Master data at
change
E02 New consumption
connection request
E03 Change of supplier at
PoD
E05 Cancellation of
change of supplier at
PoD
Message type E02 -
Termination request
E01 Supply termination
request / Device
removal request
Message type E03 –
Change of master
data
Z16 Change of customer
name at PoD
Z19 Change of
consumption point
address
Z25 Change of point of
delivery data
Message type S70 –
70/88
Information on
installation of gas
meter
E01 Master data at
change
E02 New consumption
connection request
E05 Cancellation
E20 Removal
Category code E01 –
Response to request
E14 Refusal of change of
supplier
E15 Approval of change
of supplier - of new
supplier (without
corrections)
REASON_1_ R- Service call / 9012 Category code 2 –
DESCRIPTION 35 order type Order administration
ZMPR Change of customer
at point of delivery
PDZP Natural gas supply
request
ODZP Restoration of natural
gas supply
DEM Removal
E
PZPD Customer request for
supply cut-off
PZOD Customer request for
restoration of supply
REM Complaint about
E reading
REUS Complaint about
device
INFO Information transfer
order
SAM Reading verification
O order on customer
request
71/88
Num. Conte
Segment name /
Field name
Type value
7 - Transaction
REASON_2_ R-3 Additional 9013 Message type S70 –
DESCRIPTION_C status Information on
ODE installation of gas
meter
I01 Installation
I02 Removal
REASON_2_ R- Additional 9012 Message type S70 -
DESCRIPTION 35 information Information on
installation of gas
meter
Class of counters
(not sent at
cancellation
>> FTX 0-n Free text
TEXT_SUBJECT_ R-3 Text type 4451 BLG Comment on
QUALIFIER code requested service
AAI General information
ACB Additional
information
ADM Information on
readings
CODE_LIST_QUAL R- Code of item 1131 Text line number
IFIER 17
CODE_LIST_ R-3 Organization 3055 PDS
RESPONSIBLE_A
GENCY
FREE_TEXT_1 R- Free text 4440
190 field
190 field
190 field
190 field
190 field
LANGUAGE R-3 Language 3453 SK Slovak
according to
ISO 639-1
72/88
Num. Conte
Segment name / Descriptio EDIE
/ nt - Content - remark
Field name n L
Type value
>> AGR 0-n Distribution contract data Contract data
AGREE_TYPE_ID R-3 Type of 743 11 Connection to network
contract 1
AGREE_TYPE_ R-3 Type of 743 5 Local contract
DESCRIPTION contract 3
AGREE_TYPE_ R- Code 113 ZTR - Billing class
CODE_LIST 17 1
1100 Class for households –
protected customer (for
tariff type D)
2200 Class for small
consumption (for tariff type
M)
2400 Class for medium and
high consumption (for tariff
type S and V)
TTY - Tariff type
D Households – Private
individual, contracted
offtake up to 60,000 m3
yearly, inclusive
M Small consumption – Sole
trader or legal entity,
contracted offtake up to
60,000 m3 yearly,
inclusive
S Medium consumption –
Sole trader or legal entity,
contracted offtake from
60,001 up to 400.000 m3
yearly, inclusive
V High consumption – Sole
trader or legal entity,
contracted offtake above
400.001 m3 yearly,
inclusive
OJD – Reading unit
T00 Weekly
D00 Decadal
M00 Monthly
R01 Annual, January
R02 Annual, February
R03 Annual - March
73/88
R04 Annual - April
R05 Annual - May
R06 Annual - June
R07 Annual - July
R08 Annual - August
R09 Annual - September
R10 Annual - October
R11 Annual - November
R12 Annual - December
DUM Reading unit for ZBZ /
MY Request
DOM - Point of delivery
type
01 Point of delivery
02 Self-consumption
03 CNG
04 Supply substation
AGREE_TYPE_AG R-3 Organizat 305 PDS
ENCY ion 5
SERVICE_LAYER R-3 Value 941
type 9 DOM Point of delivery type
ZTR Settlement class
TTY Tariff type
OJD Reading unit
Num. Conte
Segment name / EDIE
/ Description nt - Content - remark
Field name L
Type value
>> LOC 1-1 Location identification
PLACE_QUALIFIE R-3 Place type 322 172 Reporting location
R code 7
PLACE_ID R- Point of 322
35 delivery 5
number (PoD)
CODE_LIST_ R-3 Organization 305 89 Code assigned by
RESPONSIBLE_ 5 distributor
AGENCY_1
>> RFF 0-n Reference
REFERENCEQUA R-3 Reference 115 MG Device number
LIFIER type code 3 (Serial number)
TN Request number
(Request number)
REFERENCENUM R- Reference 115 Reference
BER 35 4
Segment of
>> CCI 0-n Characteristics characteristics of
point of delivery
PROPERTY_CLAS R-3 Type of 705 16 Parameter - Facts
S classification 9
74/88
3 Measured values
CHARACTERISTIC R- Code of 703 16 - Parameter -
_ID 17 classification 7 Facts
Described in
separate chapter
Facts
3 – Measured values
(calorific value)
CALO Caloric area
R_AR
EA
CALO Calorific value
R_VA
L
CHARACTERISTIC D Amendment 1 703
_1 - date from 6
CHARACTERISTIC D Amendment 2 703
_2 - date to 6
>>> CAV 1-1 Characteristics values
CODE_LIST_ID R- Value code 711 Value – identifier
17 1 from code book
CHARACTERISTIC R- Text 711 Value – description
_ VALUE_1 35 description of 0 from code book or
value directly entered value
CHARACTERISTIC R- Text 711
_ VALUE_2 35 description of 0
value
>> SEQ 0-n Reading record
ACTION_REQUES R-3 Action code 122 1 Add
T 9
SEQU_INFOS_ C- Number 105 Line number
SEQUENCENR 10 0
>>> QTY 1-1 Quantity
QUANTITY_QUALI R-3 Processing 606 220 Regular reading
FIER code type 3
31 Consumption
QUANTITY N- Quantity 606 Number (2 decimal
15.2 0 places)
MEASURE_UNIT_ R-3 Unit of 641 MTQ Cubic metres
QUALIFIER measure 1
75/88
Num. Conte
Segment name / EDIE
Field name L
Type value
Segment of
>>> CCI 0-n Characteristics characteristics for
quantity
PROPERTY_CLAS R-3 Type of 705 9 Measurement
S classification 9
8 Measurement device
(air pressure)
CHARACTERISTIC R- Classification 703 9 - Measurement
_ID 17 code 7
Z_2 Reason
Z_8 Reading type
8 - Parameter of air
pressure area
PR_ Air pressure area
AREA
_AI
CALO Caloric area
R
_ARE
A
TEMP Temperature area
_ARE
A
>>>
CAV 1-1 Classification values
>
CODE_LIST_ID R- Value code 711
17 1
value
value
>> NAD segment type 0-2 Name and address Name of customer,
with tag: address
Address of connected premises and name of
NAD_1 1 customer (ACTION field = “IT”), must not contain
contact details segments
Mailing address and contact (ACTION field = “UD”) –
NAD_2 1
optional information
ACTION R-3 Partner role 303 IT On-site
5 installation(Connecte
d premises)
UD Recipient of product
or service
76/88
(customer’s mailing
address)
CODELISTAGENC R-3 Organization 305 PDS
Y 5
NAMEADDRESS1 R- Additional 312
35 information on 4
partner
NAMEADDRESS2 R- Additional 312
35 information on 4
partner
PARTNERNAME1 R- Person’s last 303
35 name or 6
business
name of
company
PARTNERNAME2 R- Person’s first 303
35 name 6
STREET1 R- Street 304
35 2
STREET2 R- Number 304
35 2
STREET3 R- Extension 304
35 number 2
4
CITY R- City 322
35 9
1
COUNTRY R- Country 320
35 7
>>> CTA 1-1 Contact details
77/88
Num. Conte
Segment name / EDIE
Field name L
Type value
>>>
COM 0-n Communication contact
>
COMMNUMBER R- Value 3148 Phone number or e-
512 mail
COMMQUALF R-3 Contact type 3155
code AL Mobile phone
TE Phone
EM Electronic mail
> UNT 1-1 End of message
NUMSEG C-6 Number of 0074 Integer
transferred
segments
REFNUM 14 Reference 0062
number
14.3.3. Code book

Characterist Content
ics - value
Z_2 - Reason
01 Periodical reading
02 Progressive reading with settlement
Final reading at
03 registration/deregistration
04 Verification reading
06 Reading at registration
08 Reading due to technical installation
09 Progressive reading without settlement
10 Check reading
11 Reading after programming/adjustment
12 Reading due to technical removal
Reading prior to
16 programming/adjustment
17 Reading upon structure change of point
of delivery
21 Reading for technical installation in
22 Reading due to technical removal in
24 Change of installation
25 Change of removal
29 Reading after change of log. number of
78/88
counter
Z_8 - Reading type
01 Reading for public utilities - SAP
02 Reading for customer - SAP
03 Automatic estimate - SAP
04 Derived reading - SAP
05 New estimate after overestimate - SAP
06 Internet reading - SAP
Result of reading, upload, receipt of
07 invoice
Estimate of readings from DIS -
13 individual transfer
84 Reading without bar code, correction
Correction of estimate from DIS - mass
85 transfer
86 Reading correction via GMS
Correction of meter reading sheet -
87 mass input
Correction of estimate of readings -
88 mass transfer
89 Correction of readings - PSION
94 Reading without bar code
Estimate of readings from DIS - mass
95 transfer
96 Reading via GMS
97 Meter reading sheet - mass input
98 Estimate of readings - mass transfer
99 Mass transfers - PSION
B1 KOSK_SAM Auto reading
B2 KOSK_SAK Check of auto reading
ODZP_ENE Restoration of supply after
D1 payment
D2 ODZP_ENZ Restoration of supply new
E1 PDZP_ENE Cut-off
PDZP_ENP Unauthorized consumption
E2 ext.
PDZP_INP Unauthorized consumption
E3 int.
H1 REME_EIP Other complaint
H2 REME_EKM Check of measurement
H3 REME_ENS Complaint implausible
79/88
ics - value
Z_8 - Reading type
H4 REME_EOD Complaint of reading ext.
H5 REME_IOD Complaint of reading int.
H6 REME_NOS Complaint of natural gas
consumption estimate
H7 REME Completion of consumption
calculation - stuck counter
HD Consumption supplement
Automatic estimate - extraordinary
HM measurement
ZMPR_EKO Change of customer at
K1 point of delivery
KL Postal card
PZOD_EUO Customer request
L1 consumption cut-off
PZPD_EOO Customer request
L2 restoration of supply
ics - value
CALOR_AREA - Caloric area
0001 Caloric area 1
TEMP_AREA - Temperature area
12 -12
15 -15
18 -18
ics - value
PR_AREA_AI - Air pressure area
0.882 1143 - mnm
0.887 1109 - mnm
0.898 1020 - mnm
0.901 993 - mnm
0.904 967 - 972 mnm
0.906 953 - mnm
0.908 938 - mnm
0.910 916 - mnm
0.912 900 - 901 mnm
0.913 895 - mnm
0.914 885 - 889 mnm
0.915 880 - 881 mnm
0.917 863 - 865 mnm
80/88
0.918 853 - 858 mnm
0.919 844 - 850 mnm
0.920 835 - 841 mnm
0.921 829 - 831 mnm
0.922 819 - 820 mnm
0.924 805 - 807 mnm
0.925 795 - 802 mnm
0.926 787 - 792 mnm
0.927 779 - 784 mnm
0.928 771 - 776 mnm
0.929 762 - 768 mnm
0.930 754 - 761 mnm
0.931 746 - 752 mnm
0.932 738 - 744 mnm
ics - value
PR_AREA_AI - Air pressure area
0.933 730 - 736 mnm
0.934 721 - 724 mnm
0.935 714 - 720 mnm
0.936 709 - 711 mnm
0.937 697 - 704 mnm
0.938 690 - 693 mnm
0.939 681 - 688 mnm
0.940 673 - 680 mnm
0.941 665 - 671 mnm
0.942 657 - 662 mnm
0.943 648 - 656 mnm
0.944 640 - 647 mnm
0.945 633 - 635 mnm
0.946 624 - 630 mnm
0.947 616 - 623 mnm
0.948 610 - 615 mnm
0.949 600 - 607 mnm
0.950 592 - 599 mnm
0.951 584 - 591 mnm
0.952 578 - 583 mnm
0.953 567 - 574 mnm
0.954 559 - 566 mnm
0.955 551 - 557 mnm
0.956 543 - 550 mnm
0.957 535 - 542 mnm
0.958 527 - 534 mnm
81/88
0.959 519 - 526 mnm
0.960 511 - 518 mnm
0.961 503 - 510 mnm
0.962 494 - 502 mnm
0.963 486 - 493 mnm
0.964 478 - 485 mnm
0.965 470 - 477 mnm
0.966 462 - 469 mnm
0.967 454 - 461 mnm
0.968 446 - 453 mnm
0.969 438 - 445 mnm
0.970 430 - 437 mnm
0.971 422 - 429 mnm
0.972 413 - 421 mnm
0.973 405 - 412 mnm
0.974 397 - 404 mnm
0.975 389 - 396 mnm
0.976 381 - 388 mnm
0.977 373 - 380 mnm
0.978 365 - 372 mnm
0.978 365 - 372 mnm
0.979 357 - 364 mnm
0.980 349 - 356 mnm
0.981 340 - 348 mnm
0.982 332 - 339 mnm
ics - value
PR_AREA_AI - Oblasť tlaku vzduchu
0.983 324 - 331 mnm
0.984 317 - 323 mnm
0.985 308 - 315 mnm
0.986 300 - 307 mnm
0.987 292 - 299 mnm
0.988 284 - 291 mnm
0.989 276 - 283 mnm
0.990 268 - 275 mnm
0.991 259 - 267 mnm
0.992 251 - 258 mnm
0.993 243 - 250 mnm
0.994 235 - 242 mnm
0.995 227 - 234 mnm
0.996 219 - 226 mnm
0.997 211 - 218 mnm
82/88
0.998 203 - 210 mnm
0.999 195 - 202 mnm
1.000 186 - 194 mnm
1.001 178 - 185 mnm
1.002 170 - 177 mnm
1.003 162 - 169 mnm
1.004 154 - 161 mnm
1.005 146 - 153 mnm
1.006 138 - 145 mnm
1.007 130 - 137 mnm
1.008 122 - 129 mnm
1.009 113 - 121 mnm
1.010 105 - 112 mnm
1.011 97 - 104 mnm
14.3.4. Facts
Data
Name Description Remark
type
Point of delivery facts – Household (HH)
Estimated yearly
QU_DRS_D consumption-HH Number Mandatory field
US_ZN_NAP Indicator of connection Number Information field
(optional), value from
code book – “Indicator
of connection”,
Information field
(optional)
Nature of consumption-HH- Information field
FL_CHAD_K heating Flag (optional)
FL_CHAD_T DHW Flag (optional)
FL_CHAD_V cooking Flag (optional)
Information field
QU_KWH_D Estimated yearly Number (optional)
consumption-HH in kWh
83/88
Data
type
Point of delivery facts – Small consumption
Estimated yearly consumption
QU_DRS_M SC Number Mandatory field
QU_DRS_L_ Estimated consumption- Information field
M summer per.SC Number (optional)
US_ZN_NAP Indicator of connection Number Information field
(optional), value from
codebook – “Indicator
of connection”,
Information field
(optional)
QU_DRS_Z_ Estimated consumption-winter Information field
M per.SC Number (optional)
Nature of consumption-SC- Information field
FL_CHAM_P food manuf. Flag (optional)
FL_CHAM_T techology Flag (optional)
FL_CHAM_T Nature of consumption-SC- Information field
V DHW Flag (optional)
FL_CHAM_V heating Flag (optional)
Estimated yearly consumption Information field
QU_KWH_M SC Number (optional)
QU_MAXH_ Information field
LM Max.hour.consumption in Number (optional)
summer per.SC
QU_MAXH_ Max.hour.consumption in Information field
ZM winter per.SC Number (optional)
QU_MAXR_ Max.annual consumption for Information field
TM technol.SC Number (optional)
QU_MAXR_ Max.annual consumption for Information field
VM heating SC Number (optional)
Data
type
Point of delivery facts – Medium and high
consumption
Nature of consumption-
FA_CHA_T technology HC Number Mandatory field
84/88
FA_POC_ZM Number of changes (working) Number Mandatory field
ANQ annual contracted
QU_DRS_V quantity Number Mandatory field
QU_DRS_V_
Z Increase of ANQ -amendment Number Mandatory field
to contract
QU_MAXHO
_L Max. hour.consumption in Number Mandatory field
summer per.HC
QU_MAXHO Max.hour. consumption in
_Z winter per.HC Number Mandatory field
QU_ZDENM NDM contracted daily
AX maximum Number Mandatory field
FA_NAHR_P Mandatory for
A Substitute fuel Number selected cust.
FA_VK_TE1 Mandatory for
0 Temperature 10 Number selected cust.
FA_VK_TE1 Mandatory for
FA_VK_TE1 Temperature - end of heating Mandatory for
2 period Number selected cust.
FA_VK_TEP Mandatory for
QU_MAX_M Mandatory for
TE Q-yearly - technology Number selected cust.
QU_MAX_M Q-yearly consumption - Mandatory for
VY heating Number selected cust.
QU_MAXHH Max.daily consumption in Number Mandatory for

85/88
_L summer per.HC selected cust.
QU_MAXHH Max.daily consumption in Mandatory for

_Z winter per.HC Number selected cust.
QU_MINHO_ Mandatory for
L Min.hour.consumption in Number selected cust.
summer per.HC
QU_MINHO_ Min.hour.consumption in Mandatory for
Z winter per.HC Number selected cust.
QU_OS_SKL Mandatory for
Z Time lag (consumption levels) Number selected cust.
Mandatory for
QU_OS8 Consumption level 8 - m3 Number selected cust.
Data
type
Point of delivery facts – Medium and high
consumption
Mandatory for
QU_RP4_1 RP 4 - months I-III, XI-XII Number selected cust.
Mandatory for
QU_RP4_4 RP 4 - months IV,X Number selected cust.
Mandatory for
QU_RP4_5 RP 4 - months V-IX Number selected cust.
Mandatory for
Mandatory for
Mandatory for
Mandatory for
Mandatory for
Mandatory for
Mandatory for
86/88
Mandatory for
Mandatory for
Mandatory for
Mandatory for
Mandatory for
QU_VK_MN1 Mandatory for
0 Quantity for temperature 10 Number selected cust.
QU_VK_MN1 Mandatory for
1 Quantity for temperature 11 Number selected cust.
QU_VK_MN1 Quantity - end of heating Mandatory for
2 period Number selected cust.
QU_VK_MN Mandatory for
O1 Quantity for temperature 1 Number selected cust.
VT_PR_L_G Mandatory for
R Q-summer consumption Number selected cust.
Nature of consumption-HC- Information field
FL_CHAV_T technology Flag (optional)
FL_CHAV_V heating Flag (optional)
FL_CHAV_Z mixed Flag (optional)
ANQ annual contracted Information field
QU_KWH_V quantity Number (optional)
87/88
QU_KWH_V Information field
_Z Increase of ANQ -amendment Number (optional)
to contract
QU_NAD_VY Information field
S Altitude Number (optional)
QU_ROCNS Information field
P Annual consumption Number (optional)
RA_CHARO Information field
DB Nature of consumption Number (optional)
QU_PRE_HU Information field
P Required operating pressure Number (optional)
14.3.5. Code book for facts
Content
Fact Content - description
- value
US_ZN_NAP - Indicator of connection
1
2
3
5
88/88

Eng TSVD 01 06 2011

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Eng TSVD 01 06 2011

Încărcat de

Drepturi de autor:

Formate disponibile

Annex No.

Annex No.1 MSCONS message format……………….………….……………………53

The Technical Specifications of Data Exchange document is a manual for

This document describes in detail the following:

System for Customer

Picture 1 – Overall context of data exchange with DNO

3.2. Communication channels

Availability of documents: The technical specifications as well as the templates of the

3.3. Message formats

For electronic communication messages according to UN/EDIFACT specification are

EDIFACT is an acronym for Electronic Data Interchange for Administration,

The description of each message format includes:

The encryption / decryption will be performed automatically during the transmission.

3.4.1. Example of encryption and decryption on the command line

openssl smime -decrypt -inform DER -in encrypted.p7m -inkey

Command description: the command decrypts the encrypted.p7m file using

1. Run the command to encrypt

openssl smime -encrypt -in subor.txt -outform DER -out encrypted.p7m -

Command description: the command encrypts the subor.txt file using

Automatic encryption and decryption requires implementation of software that

3.4.3. Technical information

4.1. Specifications for electronic communication

The whole electronic communication process is automated. However, it is required

4.2. Technical conditions necessary for the proper functioning of

4.3. Principles of electronic communication

1. Communication in direction from DNO to natural gas supplier (Export)

2. Communication in direction from natural gas supplier to SPP to DNO

4.4. Types of e-mails

4.4.1. Error reports

4.4.1.1. Error report e-mail from DNO to natural gas supplier

4.4.1.2. Error report e-mail from natural gas supplier to DNO

4.4.2.1. Import e-mail from natural gas supplier to DNO

4.4.2.2. Import confirmation e-mail from DNO to natural gas supplier

4.4.3.1. Export e-mail from DNO to natural gas supplier

4.4.3.2. Export confirmation e-mail from supplier to DNO

4.4.4.1. Mass readings e-mail from DNO to natural gas supplier

4.4.5. Exchange of public keys or certificates

Communication via web application in the form of form application represents an

4.5.1. Security and accessing of the application

4.5.2. Execution method - reading/displaying messages

4.5.3. Execution method – writing and sending messages

5.1.1. PoD identifier

5.1.2. Identifier of communicating partner

5.3. Date format

5.4. Numerical data format

Numerical data re given in standard formats of XSD -

xs: decimal places (with maximum two decimal places)

6.1. Definition of message formats

6.1.1. MSCONS message format

Scheme of MSCONS message segments

UNH Message header

BGM Beginning of message

DTM Document date

NAD Address of off-take point and addressee for correspodence

CTA Contact details

COM Communication information (target / source e-mail)

UNS Beginning of data section

NAD NAD – Content of MSCONS message

UNT End of message

LOC Identifier of of-take point

RFF Reference (e.g. in case of correction)

LIN Item (counter)

QTY Quantity readout