Capacity Allocation & Congestion

Management Network Codes

Stakeholder Meeting

3 July 2012

Introduction & Overview\

Agenda

10.30: Welcome & Introduction 10.40: The CACM network code: A summary of responses to

consultation & the key areas where stakeholder consider we need to focus

10.50 – 13.30: Working Session – Tackling the outstanding challenges: 13.30: Lunch 14.15: Questions & Answers on the treatment of stakeholder comments 14.45: Views from the Associations & stakeholders- What’s your reaction to the proposed way forward?- Where would you encourage us to focus most in the next few months? 15.45: Next steps & concluding remarks

Overview – Process to date & immediate next steps

23 March – Consultation

Begins

Stakeholder workshop

23 May – consultation

closes

Comments considered & code updated

Stakeholder workshop – 3

July

Code updated & circulated

Responses to the consultation

Count of Comments

0 100 200 300 400 500 600 700

Entry into Force

Transitional Arrangements

Cost Recovery

Congestion Rent

Firmness

Clearing and Settlement

Intraday Market

Day Ahead Market

Bidding Zones

Capacity Calculation

Regulatory Aspects

Definitions

Whereas

2098 comments received.

Covering all elements of the code.

But focused on capacity calculation, bidding zones & firmness.

Significant challenge in addressing & including comments.

And in showing how we’ve considered the comments.

Points we received

Capacity calculation methods should be

fully coordinated within regions

More clarity of flow based & NTC based

approaches

Clearer reporting on bidding zone

definitions and reviews

More flexibility in algorithm

development & amendment

Greater clarity on transitional intraday

arrangements

Define force majeure & emergency

situationsAlign the timings

Align with the governance guideline

Harmonise definitions & improve

recitals

Format of this morning

Tab

le 1 Capacity

Calculation & Bidding Zones• Group A

please start here

Tab

le 2 Day

Ahead, Intraday & Firmness• Group B

please start here

Tab

le 3 A common

approach & general questions• Group C

please start here

We’ll then ask groups to rotate so they are involved in a discussion on each topic.

Process to deliver the code to ACER

16 July – code

circulated

1 August – key issues received

7 August – Stakeholder

Group

29 August – Stakeholder

Group

7 September –final internal

Committee approval

11 September – Code

submitted for Assembly approval

25 September – Assembly

meeting

30 September – Deadline for

ACER submission

Thank you