PCR_NOR_01: Configuration Synchronization

Version 2.4
Date 25/06/2015 (implementation date)
Status Draft Final

Previous versions
Versio Date Author Summary of changes
n
0.1 22/07/2012 OMIE Writing PX
0.2 03/10/2012 EPEX First PX Reviewer
0.3 11/10/2012 BY ALL PXs during the call 11/10/2012
0.4 11/06/2013 PMO Quality check for typos
0.5 20/10/2013 EPEX reviewing
1.0 21/10/2013 PWG Agreed version
1.1 25/10/2013 PMO Grammatical revision
2.0 17/01/2014 PWG Approved at PWG
2.1 26/05/2014 CCB Approved by CCB
2.2 01/07/2014 PWG Amended Overview Figure in PWG
2.3 23/07/2014 CCB Approved by CCB
2.4 06/05/2015 GME Reviewed for the PMB r8
12/05/2015 PWG Reviewed and approved by PWG
22/06/2015 CCB Approved by CCB
 PCR_NOR_01: Configuration Synchronization
Table of Contents
1. Introduction.................................................................................................. 3
1.1. Summary............................................................................................... 3
1.2. Governed / Regulated by.......................................................................3
1.3. Associated Procedures...........................................................................3
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...................................5
2.5. Operational manual reference...............................................................5

Noti This document is part of the operational manual of PCR and is governed by Change Control. Any
ce 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.4 Date 25/06/2015 (implementation date)

Page 2 of 5
 PCR_NOR_01: Configuration Synchronization

1. Introduction
This procedure describes the process of verifying that all connected PMBs have
activated the same version of the Shared Configuration file.

Sending of Confirmation
the Final Results /
Network Confirmation Preliminary publication of
data Results /Publication of the final
preliminary results results

Reception
of the
Daily
Network
Results Sharing Preliminar Final Report +
Configuratio data
Calculatio Results y Results Results Euphemia
n Confirmati
n PCR Confirmatio Session
Synchroniza Reception on n Dump
Target time 9:15 of the Target time 12:36 Target time 12:54
Start TargetFinish Target
Order data
Time 12:10 Time 12:22
Local PX validation

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

1.1. Summary
The first process of the Market Coupling Session is the verification of the PMB
and Algorithm configurations for each PMB. The common parameters of the
PMB and Algorithm must always be identical for all PMBs.
In a normal situation, this process is automatically launched when the PMB
Start Time is reached.
All the PMBs send their current Shared Configuration file to the Cloud and also
receive the Shared Configurations files from the other PMBs. When a Local PMB
receives the Shared Configuration file, it compares it with its own Shared
Configuration file, which must be equal for all PMBs.

1.2. Governed / Regulated by

- PCR Cooperation Agreement (HLFA included in the Annex 2 of this Co-
operation agreement)

1.3. Associated Procedures

- In normal situation: If the Configuration Synchronization process is
finished successfully, the process continues automatically with the
next steps:
PCR_NOR_02: Network Data Sending and Receiving
PCR_NOR_03: Order Data Sending and Receiving
- In backup situation: As soon as an event occurs that prevents the
normal performance of the PCR_NOR_01 process step, the PXs refer to
procedure PCR_BUP_01.

Version 2.4 Date 25/06/2015 (implementation date)

Page 3 of 5
 PCR_NOR_01: Configuration Synchronization

2. Procedure
2.1. Preconditions to start
All PMBs of all PXs must be online.

2.2. General overview

Description :
Start Target Messag
Steps Configuration Synchronization in From To C BC NC
Time Time e ID
PMB

The PMB initiates the process 09:00

1 when the PMB Start Time is - - - -
reached.

All PMBs creates a notification in

the GUI that the Market Coupling
Session has been started for
delivery day the following day,
2 requests for Synchronization and - - MC30 PMB Cloud
distributes to the Cloud its
Shared Configuration file
containing its PMB and Algorithm
configuration.

The Local PMB receives the

Shared Configuration file from
3 - - MC40 Cloud PMB
another PMB through the Cloud,
and saves it in the database.

The Local PMB compares the

received Shared Configuration
4 file with its own active Shared - - - - -
Configuration file and indicates if
the content is equal.

The Local PMB repeats the steps

5 3 and 4 until all the Shared - - - - -
Configuration files are validated.

The Configuration
Synchronization process is
6 completed when all the - 9:15 - - -
configurations of all Local PMBs
are equal.

Operator interaction
Without Operator interaction
This role cannot execute it
Opt Optional for each Non Coordinator
C PCR Coordinator

Version 2.4 Date 25/06/2015 (implementation date)

Page 4 of 5
 PCR_NOR_01: Configuration Synchronization

Description :
Start Target Messag
Steps Configuration Synchronization in From To C BC NC
Time Time e ID
PMB

BC Backup Coordinator
NC Non Coordinator (Operator)

2.3. Process clarification

All of the following steps are mandatory for all the PMBs.
1. At Start Time, the Local PMB automatically activates the new Market Coupling
Session for delivery date the following day (already created at midnight), by
indicating in the dashboard that the Market Coupling Session is Active. A message
stating that the Market Coupling Session has started is written in the Notifications in
the left part of the PMB GUI.
2. The Configuration Synchronization starts with the sending of the Configuration
check signal message (MC30) from the Local PMB to all the other PMBs. The status
of the Configuration Synchronization is set to Active.
3. The Local PMB will receive from all the other PMBs in the Cloud the Shared
Configuration message (MC40). The message is automatically saved in the PMB.
The message reception is shown in the Received Shared Configurations detail in the
right part of the PMB GUI.
4. The Local PMB compares the received Shared Configuration message with its own
configuration and shows the result of this comparison in the Received Shared
Configurations detail: the status of the comparison result is set to Equal in case
the Configurations are aligned. If not, the status is set to different, and the
procedure PCR_BUP_01is applied.
Moreover, the Local PMB compares the Common Parameters, showing if the
Coordinator, the PCR Application (PMB) version, the Algorithm version and the
Delivery Date are Equal in all PMBs. This is displayed in the right side of the GUI,
section Current common parameters comparison. If these are not Equal, the
PCR_BUP_01 procedure needs to be followed.
5. Steps 3 and 4 are repeated for all the PMBs in the Cloud.
6. When all of the previous steps are successfully finished, the Local PMB ends the
Configuration Synchronization process: its status is changed to Completed and
the Notification screen displays Broker Cloud is synchronized. The next processes
(PCR_NOR_02: Sending/ Reception of Network Data and PCR_NOR_03: Sending/
Reception of Order Data) automatically start.

2.4. Conditions reached before starting next process

The final state to start the next process is the fact that each Local PMB has
received all the Shared Configuration files from the Cloud and that all of them
are equal, the status field in the GUI of each PMB being Completed.

2.5. Operational manual reference

See chapter 8.1 - Dashboard Synchronization and 8.2. Configuration
Synchronization in the User Guide provided by Unicorn

Version 2.4 Date 25/06/2015 (implementation date)

Page 5 of 5