1. The HETS Operator shall execute the ISP based on the following data, for each Dispatch Period concerned:

   a) The price - quantity pairs of the stepwise ISP Balancing Energy Offers.

   b) The price-quantity pairs of the Balancing Capacity Offers for upward and downward FCR, upward and downward aFRR and upward and downward mFRR.

   c) The Registered Characteristics of the Balancing Service Entities.

   d) The Techno-Economic Declarations submitted by the Balancing Service Providers for the Balancing Service Entities they represent.

   e) The Total and Partial non-Availability Declarations and the Major Outage Declarations submitted by the Balancing Service Providers for the Balancing Service Entities they represent.

   f) The operational status of the Balancing Service Entities at the start of the scheduling period, namely the number of half-hours already in operation or out of operation and the scheduled injection or consumption at the start of the ISP scheduling period.

   g) The Market Schedules of all the Balancing Service Entities.

   h) Any updated schedules for the scheduled operation of the generating units in Commissioning Operation.

   i) Any updated schedules for the scheduled operation of the Dispatchable Generating Units in Testing Operation.

   j) The mandatory schedules for hydroelectric power generation, as submitted by the respective Producers to the HETS Operator through the daily mandatory hydro injection declarations.

   k) The zonal Load Imbalances.

   l) The zonal RES Units Imbalances.

   m) The available flows in the Inter-Zonal Corridors.

   n) The import/export schedule Imbalances at the interconnections imposed by the HETS Operator.

   o) The zonal and systemic needs of the HETS in Balancing Capacity.

   p) Events that are notified to the HETS Operator, in accordance with the HETS Grid Code.

   q) The declarations of maximum daily energy injection constraint.

   r)Other information collected and/or notified to the HETS Operator in accordance with the HETS Grid Code, as well as other technical data and simulation data regarding the operation of the HETS.

2. On the basis of the data sent by the Energy Exchange, the HETS Operator shall determine:

   a) the Final Internal Schedules per Dispatch Period of the Dispatch Day, which correspond to Balancing Service Entities and Balance Responsible Entities in Greece and are equal to the Market Schedules sent by the Energy Exchange, and

   b) the Final External Schedules per Dispatch Period of the Dispatch Day, which correspond to import/export schedules at the interconnections, and take into account the Market Schedules, the schedules among Transmission System Operators, any imbalances due to technical constraints on interconnection lines and the import/export imbalances included in the latest Physical Transmission Rights Declarations of the Participants, caused:

         i. either by the difference between the imported quantity included in the Market Schedule of a Participant and his nomination of long-term Physical Transmission Rights for electricity imports through an interconnection where there is an obligation for physical delivery,

        ii. or by the difference between the quantities of energy sold/bought on the Day-Ahead Market that correspond to the short-term Physical Transmission Rights and the quantities of energy sold/bought on the Day-Ahead Market(s) of neighboring countries that correspond to the same short term Physical Transmission Rights.

1. The ISP is executed as a Mixed Integer Linear Programming model.

2. The quantity of the upward ISP Balancing Energy Offer taken into account in the ISP corresponds to the difference between the Available Capacity of the Balancing Service Provider and the capacity resulting from the Balancing Service Provider's Market Schedule, as in force at the time of submission of the Offer. The quantity of the downward ISP Balancing Energy Offer corresponds to the difference between zero quantity and the capacity resulting from the Balancing Service Provider's Market Schedule as in force at the time of submission of the Offer. If the Balancing Energy prices of the ISP Balancing Energy Offers for the same Dispatch Period arithmetically coincide, and the respective Balancing Energy quantities of such ISP Balancing Energy Offers are not fully included in the ISP results, then the following order of priority shall be applied for the bidding segments: (a) Dispatchable RES Units Portfolio, (b) Dispatchable hydro Generating Units, (c) Dispatchable Load Portfolio, and (d) Dispatchable thermal Generating Units. Among bidding segments that belong to the same category, priority shall be given to the segments of the offers corresponding to the Balancing Service Entity with the highest Ramp Up Rate. For bidding segments that come into the same category and have the same Ramp Up Rate there will be random selection.

3. If the Balancing Capacity prices of the Balancing Capacity Offers for the same Dispatch Period arithmetically coincide, and the respective Balancing Capacity quantities of those Balancing Capacity Offers are not fully included in the ISP results, the bidding segments shall be selected in the following order of priority: (a) Dispatchable RES Units Portfolio, (b) Dispatchable hydro Generating Units, (c) Dispatchable Load Portfolio, and (d) Dispatchable thermal Generating Units. Among bidding segments that belong to the same category, priority shall be given to the segments of the offers corresponding to the Balancing Service Entity with the highest Ramp Up Rate. For bidding segments that come into the same category and have the same Ramp Up Rate there will be random selection.

4. The Integrated Scheduling Process Optimization Algorithm is briefly described as follows:

   a) The ISP execution produces:

   i. the commitment status of each Balancing Service Entity, for each Dispatch Period of the Dispatch Day,

   ii. the upward and downward Balancing Capacity for FCR in MW per Balancing Service Entity for each Dispatch Period of the Dispatch Day,

   iii. the upward and downward Balancing Capacity for aFRR in MW per Balancing Service Entity for each Dispatch Period of the Dispatch Day,

   iv. the upward and downward Balancing Capacity for mFRR in MW per Balancing Service Entity for each Dispatch Period of the Dispatch Day,

   v. the inter-zonal flows,

   vi. the potential energy surplus in MW for every Dispatch Period of the Dispatch Day, and

   vii. the Balancing Capacity requirements limitation in MW, when required, for every Dispatch Period of the Dispatch Day.

   b) The algorithm works in such a way that the total Balancing Energy and Balancing Capacity procurement cost is minimized. The total cost of providing Balancing Energy may include the estimated cost of real-time activation of Balancing Capacity. Total cost of Balancing Energy and Balancing Capacity procurement means the sum of the Balancing Energy and Balancing Capacity procurement for all Dispatch Periods of Dispatch Day D in the case of ISP1 and ISP2, or for the remaining Dispatch Periods of Dispatch Day D in the case of ISP3 and any other execution of any ad hoc ISP during the Dispatch Day.

   c) The algorithm must comply with the following constraints:

   i. the HETS Imbalances constraint, according to which the sum of the allocated upward and downward ISP Balancing Energy is equal to the forecasted HETS Imbalances, per Bidding Zone and as a total,

   ii. the inter-zonal constraints,

   iii. the sum of the Balancing Capacity for FCR of all Balancing Service Entities that have been chosen to provide Balancing Capacity for FCR must be greater than or equal to the total requirements per Bidding Zone or/and of HETS as a whole with respect to upward and downward Balancing Capacity for FCR,

   iv. the sum of the Balancing Capacity for aFRR of all Balancing Service Entities that have been chosen to provide Balancing Capacity for aFRR must be greater than or equal to the total requirements per Bidding Zone or/and of HETS as a whole or of the bidding zone with respect to upward and downward Balancing Capacity for aFRR,

   v. the sum of Ramp Up or Ramp Down Rates of Balancing Service Entities that have been selected to provide Balancing Capacity for aFRR must be greater than or equal to the total requirements of the HETS with respect to Ramp Up and Ramp Down Rates for aFRR,

   vi. the sum of the Balancing Capacity for mFRR of all Balancing Service Entities that have been chosen to provide Balancing Capacity for mFRR must be greater than or equal to the total requirements per Bidding Zone or/and of HETS as a whole with respect to upward and downward Balancing Capacity for mFRR,

   vii. the updated operation schedules of generating units in Commissioning Operation,

   viii. the updated operation schedules of Dispatchable Generating Units in Testing Operation,

   ix. the daily mandatory hydro management declarations,

   x. the technical constraints of the Balancing Service Entities that are included in their Declared Characteristics such as Balancing capacity supply constraints, Balancing Energy constraints, Technically Minimum Generation and Maximum Net Capacity and Available Capacity constraints under normal operation or under AGC, synchronization time, soak time and desynchronization time, time and generation of the Dispatchable Generating Unit between synchronization and the Technically Minimum Generation, the logical status of commitment constraints, the minimum up/down time constraints, the ramp rate of power output and Balancing Capacity of the Units constraints, the Maximum Operating Time per activation and the Maximum Number of Activations per Dispatch Day,

   xi. the constraints on the maximum daily energy injection from Dispatchable Natural Gas Generating Units,

   xii. the constraints on the maximum daily energy injection from Dispatchable Hydro Generating Units based on the constraints declarations for maximum daily energy injection from Dispatchable Hydro Generating Units,

   xiii. in each Dispatch Period, pumped storage Dispatchable Hydro Generating Units shall operate either as Dispatchable Generating Units or as pumping loads,

   xiv. in each Dispatch Period the Dispatchable Multi-Shaft Combined Cycle Generating Units shall operate only in one configuration,

   xv. in each Dispatch Period, the Dispatchable Load Portfolios may be allocated either as (a) Balancing Energy for mFRR and/or FCR or (b) Balancing Energy for aFRR and/or FCR. Additionally, if the Dispatchable Load Portfolio has a non-zero Market Schedule or a non-zero ISP Schedule during a Dispatch Period, it cannot be assigned aFRR Balancing Energy.

   xvi. In each Dispatch Period, Dispatchable Intermittent RES Units Portfolio may be allocated either as (a) Balancing Energy for mFRR and/or FCR or (b) Balancing Energy for aFRR and/or FCR. In addition, if the Dispatchable Intermittent RES Unit Portfolio has a non-zero ISP Schedule during a Dispatch Period, it cannot be assigned aFRR Balancing Energy,

   xvii. the constraints for the transition between two virtual entities, as those are defined and specified in the Technical Decision “Integrated Scheduling Process”.

   d) In cases where observance of the energy balance is not feasible, in order to achieve the desired convergence of the algorithm, and especially in cases of excess energy, the algorithm may resolve it by displaying the energy surplus in the ISP results. Relevant details are described in the Technical Decision “Integrated Scheduling Process”.

   e) In cases where maintaining Balancing Capacity zonal/systemic requirements is not feasible, in order to achieve the desired algorithm convergence, the algorithm may solve by limiting the Balancing Capacity requirements up to a maximum specified volume. Relevant details are described in the Technical Decision “Integrated Scheduling Process”.

5. In the event that, after resolution of the ISP, coverage of anticipated imbalances and/or zonal/systemic Balancing Capacity requirements remains impossible, any available ISP Balancing Energy Offers for Contracted Generating Units shall be included, the following constraints shall be gradually lifted, and the ISP shall be executed again. The procedure for lifting constraints is as follows:

   a) First of all, the constraint on Balancing Capacity requirements for upward and downward mFRR is not implemented across its full range,

   b) Then, the Balancing Capacity requirements constraint for upward and downward FCR is not implemented in its entire range,

   c) Furthermore, the constraint on Balancing Capacity requirements for upward and downward aFRR is not implemented across its full range,

   d) Finally, the HETS Imbalances constraint is not implemented in its entire range.

6. The HETS Operator shall include in the ISP data the declarations of maximum daily energy injection constraint from Dispatchable Natural Gas Generating Units. The quantity of injected electricity that is included in the ISP for the Dispatchable Natural Gas Generating Units, to which the submitted declarations of maximum daily energy injection constraint from Dispatchable Natural Gas Generating Units refer, may not exceed the quantity specified in the above declarations.

7. The HETS Operator shall include in the ISP data the declarations of maximum daily energy injection constraint from Dispatchable hydro Generating Units. The quantity of injected electricity that is included in the ISP for the Dispatchable hydro Generating Units, to which the submitted declarations of maximum daily energy injection constraint from Dispatchable hydro Generating Units refer, may not exceed the quantity specified in the above declarations.

1. The results of the ISP, shall include:

   a) the commitment (synchronization/desynchronization) schedule of the Balancing Service Entities,

   b) the Balancing Capacity for FCR, mFRR and aFRR in either direction (upward and downward) for each Balancing Service Entity and for each Dispatch Period of the Dispatch Day.

   c) the potential energy surplus in MW for every Dispatch Period of the Dispatch Day

   d) the constraint of Balancing Capacity requirements in MW, when required, for every Dispatch Period of the Dispatch Day, and

   e) the inter-zonal flows.

2. For each Dispatch Period, the sum of the upward and downward Balancing Power awarded by the ISP to each Balancing Service Entity calculated separately for each of the Balancing Power Products (FCR, mFRR and aFRR) cannot be less than a specified limit. This limit is calculated for Dispatchable Generating Units as 2% of the Maximum Net Capacity and for Dispatchable Load Portfolios or Dispatchable RES Units Portfolios as 2% of the dispatched capacity. The above limit is rounded to a whole number and is assigned values from 1MW to 10MW. In cases where this limit is calculated to be less than 1MW, it is assigned the value 1 MW and in cases where it is calculated to be greater than 10MW it is assigned the value 10 MW.

3. An indicative generation/consumption schedule also results from the ISP, for each Balancing Service Entity and for each Dispatch Period of the Dispatch Day ("ISP schedule"). The differences between the ISP schedule and the automatic Dispatch Instruction mechanism (Balancing Energy Market) shall not be considered deviations from the ISP. In addition, an indicative schedule may also result from the ISP, which corresponds to the energy surplus, in MW, for every Dispatch Period of the Dispatch Day. The energy surplus observed in real time can differ significantly from the indicative schedule mentioned above and can be addressed with appropriate measures taken by the HETS Operator close to real-time.

4. Without prejudice to paragraph 5 of this Article, with regard to the results of the ISP for Balancing Capacity, the following shall apply:

   a) The results of ISP1 shall not be binding.

   b) The results of ISP2 shall be binding for the first twenty-four (24) Dispatch Periods of Dispatch Day D.

   c) The results of ISP3 shall be binding for the last twenty-four (24) Dispatch Periods of Dispatch Day D.

   d) The results of the ad hoc ISPs shall be binding for the Dispatch Periods to which they refer.

5. The results of all ISP executions shall be binding with regard to the commitment schedule of the Balancing Service Entities.

6. The Balancing Service Providers are obliged to comply with the binding results of the ISP executions. In case of non-compliance, the Balancing Service Providers shall not be entitled to a fee and shall be subject to non-Compliance Charges, in accordance with CHAPTER 22 of this Rulebook.

7. The HETS Operator shall publish the results forty-five (45) minutes after the execution of each ad-hoc ISP. Within the same deadline, it shall inform the Balancing Service Providers whose Balancing Energy and Balancing Capacity Offers were submitted to the ISP and accepted of the results of the ISP that concern them.

8. The HETS Operator may deviate from the results of the ISP in all cases where it has substantiated evidence to consider that such a deviation is necessary so as to ensure the safe operation of the HETS and the smooth operation of the Balancing Market.

Until 11:00 EET on each D+1 calendar day, the HETS Operator shall notify the RAEWW of all data, parameters and results of the ISP executed on Dispatch Day D in editable form, in order for the Authority to review the regular operation of the ISP and identify potential distortions in the ISP results and the scheduling of Balancing Service Entities.