PCR_NOR_02: Network Data Sending and

Receiving

Version 2.9
Date 17/02/2016 (implementation date)
Status Draft Final

Previous versions
Version Date Author Summary of changes
0.1 13/07/201 EPEX Writing PX
2
0.2 First PX Reviewer
0.3 11/10/201 BY ALL PXs during the call 11/10/2012
2
0.4 11/06/201 PMO Quality check for typos
3
0.5 20/10/201 EPEX review
3
1.0 21/10/201 PWG Agreed version
3
1.1 25/10/201 PMO Grammatical revision
3
2.0 17/01/201 PWG Approved at PWG
4
2.1 27/02/201 PWG Updated in PWG call
4
2.2 11/03/201 E-mail from Approved by CCB
4 CCB
2.3 09/04/201 PWG Amended by PWG
4
2.4 26/05/201 CCB Approved by CCB.
4
2.5 27/07/201 EPEX SPOT PMB release 7 (cross-check
4 functionality) and renumbering
2.6 26/08/201 OMIE Review
4
2.7 06/10/201 CCB Approved in PCR OPSCOM 6/10
4
2.8 04/05/201 APX and EPEX Updated for compatibility with Flow-
5 CCB Based
18/05/201 Approved in PCR OPSCOM 18/05/2015
5
2.9 15/12/201 EPEX and GME Added a clarification for step 7.
5 PWG Reviewed in PWG
12/01/201 OPSCOM Approved by CCB
6
15/02/201
 PCR_NOR_02: Network Data Sending and Receiving

Version 2.9 Date 17/02/2016 (implementation date) Page 2 of 7

 PCR_NOR_02: Network Data Sending and Receiving

Table of Contents
1. Introduction.............................................................................................. 3
1.1. Summary........................................................................................... 3
1.2. Governed / Regulated by...................................................................4
1.3. Associated Procedures.......................................................................4
2. Procedure................................................................................................. 4
2.1. Preconditions to start.........................................................................4
2.2. General overview............................................................................... 4
2.3. Process Clarification...........................................................................5
2.4. Conditions reached before starting next process...............................6
2.5. Operational manual reference...........................................................6

Noti This document is part of the operational manual of PCR and is governed by Change
ce Control. Any change to this document shall follow the PCR change control
procedure. The content of this document might have evolved by the time you read
or use this document. Please contact the PCR Change Control Administrator to
check that this is the latest version before using this document.

Version 2.9 Date 17/02/2016 (implementation date) Page 3 of 7

 PCR_NOR_02: Network Data Sending and Receiving

1. Introduction
This procedure describes the sending and the receiving of the Network Data
files from each PXs Local PMB to the other PMBs via the Cloud. At the
reception, the PMB validates and stores the Network Data in the database.
Each Virtual Broker (VB) has a specific configuration in terms of
interconnectors (lines) for which Network Data values need to be provided.
This configuration is determined in the Shared Configuration File (SCF), in
the ATC Lines tab.

Sending of
the Confirmation Preliminary Confirmation
Network Results /Publication of Final Results /
Data Preliminary Results publication of
the Final
Results

Reception
of the
Network Preliminar Final Daily
Configuratio Data
Results Sharin
Calculatio g y Results Results Report
n
n PCR Confirmati Confirmatio
Synchronizat Reception Result on n
Target Time of the Start FinishsTarget Target time 12:36 Target time 12:54
09:15 Order Data Target Time 12:22
Time
Local PX
validation

Sending
of the
Order
Data
PCR in blue /Own PX in green

A Network Data file contains Cross Zonal Capacities (CZC) values for one or
more lines that have one of the following configurations, according to
definitions in the PCR Glossary.
a) Single line
b) Decoupling line
c) Alternate line
d) Cross-checked line

1.1. Summary
The Network Data files are received by each PX from its own TSO(s). Each
PXs IT System sends the received Network Data to its Local PMB for checks
and validations.
Once the Network Data have been validated by the Local PMB, each PMB
sends its own Network Data file(s) to the Cloud. At the same time, the Local
PMB will receive the Network Data file from all the other PMBs. This step is
mandatory for the Market Coupling Session to continue.
Each PMB Operator verifies the sending of its own Network Data and the
reception and validation of the Network Data from the other PMBs through
the PMB interface.
All the above steps have to be performed before the Target Time is reached.
Remark: To be noted that there is a clear distinction between the PMB
Target Time for receiving the Network Data (12:10) and the procedural
Target Time for receiving the Network Data in a normal day scenario (10:30).

Version 2.9 Date 17/02/2016 (implementation date) Page 4 of 7

 PCR_NOR_02: Network Data Sending and Receiving

1.2. Governed / Regulated by

- PCR Cooperation Agreement (HLFA included in the Annex
2)

1.3. Associated Procedures

In normal situation:
o PCR_NOR_01: Configuration Synchronization. This previous process
must have been successfully completed.
o PCR_NOR_03: Order Data Sending and Receiving. This process is
done in parallel with the current process PCR_NOR_02.
o PCR_NOR_04: Calculation Process. When PCR_NOR_02 and
PCR_NOR_03 are passed successfully, the PMB automatically
executes the next step: Calculation Process.
In backup situation: As soon as an event occurs that prevents the
normal performance of the PCR_NOR_02 process steps, the Operators
refer to procedure PCR_BUP_02.

2. Procedure
2.1. Preconditions to start
The procedure PCR_NOR_01: Configuration Synchronization must have been
successfully completed.
2.2. General overview

Targe
Description : Network data in PMB Start Messag
Steps t From To C BC NC
dashboard Time e ID
Time
PMB initiates the process when the
ASAP 09:15
1 Configuration Synchronization process is -
completed.
Local
PMB receives and saves the Network Data PX IT Local
2 - - MN10
from its own PX IT System/s. Syste PMB
m
PMB successfully validates the received
3 - -
Network Data.
Local PMB sends its own Network Data to Local
4 - - MN20
PMB
Cloud
the Cloud.
PMB receives and saves the Network Data Local
5 - - MN20 Cloud
PMB
from the other PMBs.
PMB successfully validates the received
6 - -
Network Data.
7 The process repeats step 5 and 6 until all - 10:30
Network Data from all the PMBs in the
Cloud have been received and validated.

The Coordinator checks in the Local PMB,

in the Cross Check page, that all the lines

Version 2.9 Date 17/02/2016 (implementation date) Page 5 of 7

 PCR_NOR_02: Network Data Sending and Receiving

are displayed with the status Validated.

When all the Network Data of all PMBs PMB
have been received and validated and the Target
8 PMB Target Time has been reached, then - Time
the status field indicates that the process 12:10
is completed.

Operator interaction
Without Operator interaction
This role cannot execute it
Opt Optional for each Non Coordinator
C PCR Coordinator
BC Backup Coordinator
NC Non Coordinator (Operator)

2.3. Process Clarification

All of the following steps are mandatory for all PMBs.
1. The process starts as soon as the process PCR_NOR_01: Configuration
Synchronization is completed. This can be verified on the PMB dashboard:
the status of Network Data process became Active. From this moment,
the PMB is ready to receive the Network Data from its Local PX IT
System(s) and from the other PMBs in the Cloud.
2. As soon as possible and before Target Time (10:30), the Network Data are
sent from the Local PX IT System to the Local PMB. In normal
circumstances, all the Network Data from all PMBs should be received
before the Target Time is reached. If any Network Data cannot be
received or sent by Target Time, then the Operators refer to PCR_BUP_02
procedure.
The Network Data are sent through the message MN10 and are saved in the
PMB. The reception in the PMB is indicated in the Receive Network Data detail
screen. The status is set to Arrived. The Notification bar displays the
message: New network data has been received.
3. As soon as the Network Data are received by the PMB as described in step 2,
they are validated by the PMB. The outcome of the validation process for each
PMB is shown in the Receive Network Data detail screen (the right part of the
PMB screen). The status is set to Validated. If the status is Failed, refer to
the PCR_BUP_02 procedure.
4. After the validation, the Network Data are distributed to the Cloud
through the message MN20. A message is sent to every PMB in the Cloud.
The outcome of the sending of the Network Data is shown in the Sent
Network Data detail screen. The status is set to Delivered. If the status
is Not delivered, refer to the PCR_BUP_02 procedure.
5. The Local PMB will receive from the other PMBs the Network Data file
(MN20) and file is saved in the system. The file reception is shown in the
Received Network Data detail screen. The status is set to Received. The
notification bar displays the message New Network Data has been
received from X (X being the name of the sender VB).

Version 2.9 Date 17/02/2016 (implementation date) Page 6 of 7

 PCR_NOR_02: Network Data Sending and Receiving

6. As soon as the Network Data are received, they are validated by the Local
PMB. The outcome of the validation process is shown in the Receive
Network Data detail screen. The status is set to Validated.
The validation of the received Network Data by the Local PMB includes
the Cross-checking validation for the double submission interconnectors
(lines), as specified in the SCF. The validation process can be monitored in
the Cross Check detail screen.
Once the Network Data containing the CZC values for a cross-checked
line is received, the PMB displays an Alert status and activates the
Ignore button. If the Market Coupling Session needs to continue without
the Network Data from the other VB involved in the same line, the
PCR_BUP_02 procedure has to be applied.
The PMB performs the validation of a cross-checked line as soon as the
Network Data files are received from both VBs responsible for that line.
The validation process consists in comparing the hourly CZC values
contained in the two Network Data files, for the same cross-checked line.
If the values are identical, the status field is set to Validated. If the
values are different, the status is set to Failed and the PCR_BUP_02
procedure has to be applied.
7. Step 5 and 6 are repeated for all the PMBs in the Cloud.
The Coordinator checks in the Local PMB, in the Crosscheck page, that all
the lines are displayed with the status Validated.
If at least one line is not Validated, the PCR_BUP_02 procedure will be
followed.
8. When the Network Data have been received from every PMB in the Cloud
and the PMB Target Time (12:10) is reached, the PMB ends the Network
Data process and its status will change to Completed. If the procedure
PCR_NOR_03: Order Data Sending Receiving is finished too, the next
process PCR_NOR_04: Calculation Process will start.

2.4. Conditions reached before starting next

process
The final state to start the next process (Calculation) is the fact that all
Network Data and Order Data have been received by the PMB and the PMB
Target Time has been reached.

2.5. Operational manual reference

See chapter 8.3. Network Data in the Operational Manual (User Guide
provided by Unicorn)

Version 2.9 Date 17/02/2016 (implementation date) Page 7 of 7