Distribution Company enters vacating consumer's Gas Supplier's Terminal Date as the valid one
Distribution Company enters incoming consumer's Gas Supplier's Terminal Date as the valid one
Incoming Consumer Vacating Consumer
Incoming consumer's Gas Supplier announces valid Terminal Date to incoming consumer
Vacating Consumer's Gas Supplier announces valid Terminal Date to va-cating consumer Scenario 2: Incoming consumer's Gas Supplier's Terminal Date is prior to the date entered by the vacating consumer's Gas Supplier.
Scenario 1: Vacating consumer's Gas Supplier's entered Terminal Date is prior to the date entered by the incoming consumer's Gas Supplier
1.1
Information about end of supply
BT-002: End of supply - from the Distribution Company Z08 (Terminal date changed)
Confirmation BT-004: Base data for a Metering Site
Z08 (Terminal date changed) Information about base data, Metering Site
Confirmation
Figure 15: BS-219: Change of Terminal Date
Generelly about Change of Terminal Date
The process is only to be applied in case of diasgreements between the Terminal Date in connection with Relocation of a vacating consumer.
This business process consists of two transactions:
End of supply
Base data
Start condition of Change of Terminal Date
The Distribution Company ascertains discrepancies between the entered Terminal Dates from vacating and incoming consumer’s Gas Supplier respectively.
Two scenarios may occur:
1. Vacating consumer’s Gas Supplier’s entered Terminal Date is prior to the date entered by the incoming consumer’s Gas Supplier
2. Incoming consumer’s Gas Supplier’s Terminal Date is prior to the date entered by the vacating consumer’s Gas Supplier.
Steps in the scenario Changes of Terminal Date
Scenario 1:1.1. Distribution Company enters vacating consumer’s Gas Supplier’s Termi-nal Date as the valid one.
1.2. Distributionsselskabet sends Base data with reason code Z08 (Terminal Date changed) to incoming consumer’s Gas Supplier with valid Terminal Date.
1.3. Incoming consumer’s Gas Supplier announces valid Terminal Date to in-coming consumer.
Scenario 2:
2.1. Distribution Company enters incoming consumer’s Gas Supplier’s Termi-nal Date as the valid one.
2.2. Distribution Company sends End of supply with reason code Z08 (Termi-nal Date changed) to vacating consumer’s Gas Supplier with the valid Terminal Date.
2.3. Vacating Consumer’s Gas Supplier announces valid Terminal Date to va-cating consumer.
Deadlines for Change of Terminal Date
Process Deadline Explanation
End of supply No later that 16th Business Days after Terminal Date
Sent to vacating consumer’s supplier if he is affected
Base data No later that 16th Business Days after Terminal Date
Sent to incoming consumer’s supplier if he is affected
Data content for Change of Terminal Date
Below the significant data fields, which are part of the individual data streams, are mentioned. Significant means the data that are significant to the business.
Announcement of End of Terminal Date
Metering Point id
Reason code:
o Z08 (Terminal Date changed)
Scheduled end date
Supplier id
Announcement about Base data
Reason code:
o Z08 (Terminal date changed)
Metering Point id
Metering Point address
Metering Point’s reading form
Connection date
Scheduled start date of supply
Supplier id
Reading day
Expected annual consumption
Identification of process and transactions
In this table the precise names of the business process and the applied EDI trans-actions are stated.
BS ID BS-219
BS navn Change of Terminal Date BS version 3
BS release 1 BS dato
EDI transaktioner:
BT ID DK-BT-002
BT navn End of supply – from MPA BT version 4
BT ID DK-BT-004
BT navn Base data for Metering Point BT version 4
3 Error handling
The section on EDI communication (in Regulation F) describes in detail how the par-ties should act in the event of errors in the EDI data exchange. Only the three most important principles are mentioned below:
1. The party (A) that has initiated the data exchange by sending the first EDI message to a recipient (B) is responsible for checking that a reply is received within the dead-line. If this is not so, and A is certain that B has the correct communication setup, A must contact B in order to clarify the error.
2. If A receives a negative reply, the error must be corrected on the basis of the error report and a new message be submitted. If this is not possible, A must contact B in order to clarify the problem.
3. If B sends a positive reply but A's IT system detects an error in the reply so that an error message is sent to B, B must contact A in order to clarify the error. In this type of situation, B's systems must not automatically cancel the transaction.
4 Fallback procedures
All Distribution Companies in the Danish natural gas market must be able to electron-ically submit notifications of change of supplier. For situations where this is not pos-sible due to IT system breakdown, a fallback procedure has been developed in the form of a paper form that can be faxed or exchanged by ordinary post between the players. In this way, situations are avoided where a Gas Supplier loses consumers be-cause he is unable to submit the notification of change of supplier to the Distribution Company in time.
If an IT system used for changing supplier breaks down, the Distribution Company evaluates whether it is necessary to use fallback procedures.
If a Gas Supplier does not get a reply to an electronic message, he must check the sta-tus of the Distribution Company's system. If the stasta-tus is offline, and the deadline for notification is about to expire, the Gas Supplier must submit the notification of change of supplier using the fallback procedure.
The Distribution Company may arrange with Gas Suppliers that have used the fallback procedures to resubmit the notifications when the Distribution Company's systems are online again.
The table below shows whether there is an fallback procedure for a given business scenario:
Business scenario Fallback
procedure
BS-201: Change of supplier Yes
BS-202: End of supply Yes
BS-203: Submission of base data No
BS-205: Consumption statement for a Non-Daily Read Meter-ing Point
No
BS-206: Consumption statement for a Daily Read Metering Point
Yes
BS-207: Termination of Metering Point Yes
Yes BS-209: Relocation (incoming consumer) Yes BS-210: Disconnection and reconnection of a Metering Point Yes
BS-212: Change of meter reading method Yes
BS-213: Submission of market share values Yes
BS-214: Submission of calorific values Yes
BS-216: Aggregated gas consumption Yes
BS-217: Reconciliation statement Yes
BS-218: Relocation (vacating consumer) Yes
BS-219: Change of Terminal Date Yes
Note that some of the fallback procedures are based on a form intended for change of supplier. A copy of the form for Change of Gas Supplier/End of Supply is shown in section 4.1.
All the fallback procedures are based on submission of information by email, post or telefax. The appropriate addresses appear from the common register of players.
BS-201 and BS-202
The Gas Supplier's notification is delivered by email, post or telefax. The Distribution Company returns a copy of the form indicating approval or rejection.
BS-207, , BS-210,BS-212 and BS-219
The Distribution Company sends notifications by email, post or telefax. The recipient must acknowledge receipt by replying to the return address.
BS-209 and BS-218
The Gas Supplier sends notifications by email, post or telefax. The Distribution Company replies indicating approval or rejection.
BS-206 and BS-213-BS-217
Reference is made to the fallback report giving detailed information about the fallback procedures applying to these business scenarios.
The deadlines for the individual fallback procedures are the same as the standard deadlines indicated under the above-mentioned business scenarios (section 2).