Post on 13-Mar-2018
25 May 2016
I-SEM – Technical Liaison Group Ref: TLG.003
1
ISEM Technical Specification (TS) v1 Preview Market Participant Interfaces for Balancing Market Systems
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – I-SEM TS Preview
AOB
2
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – I-SEM TS Preview
AOB
3
I-SEM Central Systems and Services Team
4
Morris Lyness
I-SEM Central Systems and Services Workstream Manager
Michael Harrington
I-SEM Central Systems and Services Technical Team Lead
Tony Brennan
I-SEM Central Systems and Services
Technical Architect
Severin Garanzuay
I-SEM Central Systems and Services
Advisor
Proposed Process
5
In Session
•Presentation of meeting content (including participant requested agenda items)
•Q&A on individual items
•Requests for agenda items in subsequent sessions
•Flag areas of concerns, interest
•Review of items/responses on previous session items
Offline •Submission of comments
•Review of material on website
•Off-line response to queries distributed
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – I-SEM TS Preview
AOB
6
Previous TLG Actions – Balancing Market
7
Ref Topic Actions Status Detailed Update / Resolution
24 Balancing Market -
Interfaces Overview
Cutover format and Process from existing SEM to ISEM: ISEM Project agreed to circulate test cases where available
Open
Cutover from a technical standpoint will be covered in a future TLG – however the Market Participant Readiness run by PEMR will be managing this from an overarching standpoint.
49 CSS Technical
Delivery Timeline
I-SEM Project Team to produce a high level detail of proposed interfaces and associated technologies
Closed For presentation in this forum (TLG 25/05/2016)
50
NEMO – Day Ahead/Intraday
Market Introduction
I-SEM Project Team to discuss the transition to the XBID solution (what is known) at the next TLG meeting
Open XBID will not be available for I-SEM go live as stated above. XBID updates will be presented via the BLG.
51
NEMO – Day Ahead/Intraday
Market Introduction
I-SEM Project Team to provide an answer re. how the Balancing Market mechanism will be implemented, functional view side at the next TLG.
Open
The functional overview of the balancing market will be presented in an upcoming BLG forum. (Date to be communicated to BLG participants )
Previous TLG Actions – Balancing Market
8
Ref Topic Actions Status Detailed Update / Resolution
52 NEMO – Day
Ahead/Intraday Market Introduction
I-SEM Project Team to provide additional details relating to the EPEX Spot communication interface with the client
Closed
Information presented in this forum (TLG 25/05/2016). NEMO specifications will be available via the next I-SEM TS, scheduled for 08 July 2016.
53 NEMO – Day
Ahead/Intraday Market Introduction
I-SEM Project Team to review the BLG: NEMO minutes from 4 April and distribute any information around charges for EPEX API.
Open This is under review currently.
55 Other Business
Wider I-SEM Project Team to review and provide a response at the earliest available day: - (1) Will there be a clearing system? (2) With regard to same day payments, will participants interact with NEMO/a third party system etc.? This could be an issue for participants in Northern Ireland if same day payments are required in euro.
Open
(1) There will be a clearing system element as part of the Balancing market solution. (2) Participants will interact with NEMO through a bank for processing same day payments. The mechanisms for other fees (e.g. Trading Volumes, Central Clearing ) are under review and will be communicated through BLG once agreed.
58 Other Business
At present, SEMO performs REMIT Reporting on behalf of participants. Will this be the case post Go-Live?
Open
13/04/16 - It is the intention for REMIT reporting to be done on behalf of participants by SEMO. It is the Participant’s responsibility (legal obligation) to avail of this service if they do so wish. At a later date, the I-SEM Project Team will take the action to explain how this will be implemented.
Participant Interface Overview (TLG 2 Query – No. 49)
• Registration • Public Static
Reports • Public
Dynamic Rpts • Public XML
Rpts • Summary
Market Status
• Balancing APP • Settlement,
Credit & Clearing
• Member Private / Member Public (reporting)
• Auction App • Settlement,
Credit & Clearing
• Member Reporting
• DA App • Settlement,
Credit & Clearing
• Member Reporting
TBC.
TBC.
Market Participant
Responsibility
1
User Name & Password
I-SEM Cert Security
I-SEM Cert Security,
User Name /Pwd
User Name & Password
TBC.
Interface Type
Interface security Access
Key Functional Components
System [Provider]
Legend: Web Service/Web Portal
Balancing Market [ABB] Public Website [EirGrid] CRM [Unicorn] Day Ahead [EPEX & ECC] Intraday [EPEX & ECC] Bank
7
Central Registration [ABB]
2 4 3 5
• Registration • Settlement,
Credit & Clearing
• Reporting
6
FTR [JAO]
Market Participant Interactions:
1. Public Website EirGrid 2. Balancing Market EirGrid 3. CRM EirGrid 4. Day Ahead EirGrid 5. Intraday Market EirGrid 6. FTR MP Responsibility 7. Bank MP Responsibility
Web Portal
Web Service
Web Portal
Web Portal
Web Service
ETS Client
Web Service: ETS API
Web Portal
Web Service
XML via SOAP XML via SOAP
XML SOAP
XML via SOAP
XML SOAP
Web Service
I-SEM Cert Security,
User Name /Pwd
10
“Day in the Life” Submission Timescales (illustrative)
Data Feed Typical Submission
Forecast Availability
Anytime up to Gate Closure for Imbalance Settlement Period Benefits to keeping availability up to date
Simple COD By 13:30 TD-1 (mandatory) Plus … as often as required, which will depend on intended participation in balancing e.g. perhaps less often if long notice plant, more often if already running Up to Gate Closure for the relevant Imbalance Settlement Period
Complex COD By 13:30 TD-1 (mandatory) Plus … as often as required,perhaps infrequent due to BCOP restrictions? Up to Gate Closure for the relevant Imbalance Settlement Period
Physical Notifications
By 13:30 TD-1 (mandatory) Plus … as often as required (e.g. When significant IDM trade occurs) Up to Gate Closure for the relevant Imbalance Settlement Period
VTOD Existing business process will apply – significant number of days to get a new VTOD set approved
VTOD set selection By 13:30 TD-1 only
11
Three market sub-types within NEMO (Day Ahead, Intra Day Auction, Intra Day Continuous)
DA Auction and Intra Day Auction:
Intra Day Continuous (Proposed) • M7 platform - AMQP based interface • RabbitMQ based implementation recommended by EPEX for
interoperability
NEMO Client Overview – Additional Info (TLG 2 query – No. 52)
Option 1: ETS Client Option
• Client Technical Requirements provided in previous TLG
• ETS is proprietary interface with ETS server in NEMO
Option 2: ETS API
• SOAP over XML based interface
• API documentation and WSDL provided by NEMO (EPEX Spot)
• Modification of their standard API to meet needs of I-SEM
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – I-SEM TS Preview
AOB
12
Proposed TLG Schedule
Session Proposed Agenda
TLG 1 Introduction to TLG Balancing Market Introduction
TLG 2 Day Ahead/Intra Day Market Introduction
TLG 3 FTR overview Preview of Balancing Market Interface Specification
TLG 4 Bal Mkt Specification Updates Preview/Q&A of NEMO specification FTR Overview
Topics proposed for subsequent sessions:
Connectivity for Market Trials
Pre-requisites for client devices
User Management
Data dictionary overview
Guide for interface toolkit
Test Data protocols
Cutover approach
13
Additional: The Proposed Agenda is subject to change and will be confirmed closer to date. Market Participants are encouraged to submit requests on any desired subject matter.
Central Systems and Services
14
Overview of Major Market Systems and Services
Key Technical Delivery Dates
15
MMS External Interface Specification
June 2016
MMS Toolkit
September 2016
I-SEM TS
V1 – Jun .2016 V2 – Jul 2016 V3 – Sep. 2016 V4 – Dec. 2016 V5 – Mar. 2017 V6 – Jun. 2017
I-SEM Technical Specification Document
16
Release Planned Rel.
Date Focus
I-SEM TS 1 3rd June 2016 Balancing Market: interfaces, connectivity requirements (type 2/3), reports (excl. Registration)
I-SEM TS 2 8th July 2016 Balancing Market: updates (incl. Registration) DA/ID: reports DA/ID: Market: interfaces, connectivity requirements (type 2/3)
I-SEM TS 3 5th Sep 2016 DA/ID: updates FTR: reports, interfaces, connectivity requirements (type 2/3, where applicable)*
I-SEM TS 4 16th Dec 2016 Balancing Market: participant interface toolkit Information in preparation for Connectivity (CCQT) testing CRM: interfaces, reports, connectivity requirements (type 2/3)
I-SEM TS 5 31st Mar 2017 Information in preparation for Market Trial
I-SEM TS 6 30th June 2017 Information in preparation for Go-Live
The I-SEM TS is a set of documents that evolve over time with the design, implementation, and updates to the market. It contains functional and technical information related to interfaces, reports, and connectivity requirements.
Note: Decision pending on treatment of FTR I-SEM TS equivalent.
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – Preview of data to be in I-SEM TS v1.0
AOB
17
Balancing Market Interface Specifications – I-SEM TS Preview
18
• I-SEM is introducing a set of new, complex markets
• Trading periods have changed with some moving to 5 minute intervals
• Existing interfaces were designed 10 years ago for SEM (ID and DA markets)
• Standardisation of Interfaces – positive in terms of development & support.
• Security developments and requirements.
New Markets – New Challenges
• We are updating schemas and adding additional elements to provide new functionality
• We are moving from numerated intervals to start/end time interval descriptors
• Meter Data submissions are being incorporated into the interface
• This new design requires revised schemas and a new WSDL
Interface Updates
• We are keeping the existing interface mechanism – XML over SOAP
• The existing submission schema is being maintained “as –is” for Meter Data
Maintaining Continuity
• Overview of changes and walkthrough samples schemas
• I-SEM TS Release and detailed review at TLG 4
Communicating Change
I-SEM TS is composed of several volumes:
19
I-SEM TS Content Overview
• Baseline; Naming Conventions; Constituents etc. A: Overarching
Volume
• Interfaces Architecture; Communication Channels; Security; Messaging Overview; System Prerequisites etc.
B: Technical Volume
• Meter Data; Registration; Trading; Settlement; Reporting C: Balancing
Market
• Day Ahead Market; Intra-Day Market; Reports D: NEMO Ex-Ante
Markets
• Registration; Trading; Settlement; Reporting E: FTR
• Registration; Trading; Settlement; Reporting F: Capacity
Market
• Definitions and terms G: Glossary
20
I-SEM TS Content Overview – Sample Table of Contents
1
• Disclaimer and Content Information
2 • Introduction
3
• Treatment of time in the I-SEM Market Systems
4
• Balancing Market Registration
5 • Balancing Market Trading
6 • Reporting
I-SEM TS Volume C – Balancing Market
21
I-SEM TS Content Overview – Sample Table of Contents
1
• Disclaimer and Content Information
2 • Introduction
3
• Treatment of time in the I-SEM Market Systems
4
• Balancing Market Registration
5 • Balancing Market Trading
6 • Reporting
4 - Balancing Market Registration 4.1 - Introduction 4.1.1 - Scope of I-SEM Registration system 4.1.2 - Gaining access to the ISEM Market Systems 4.2 - Type 2 and Type 3 Query & Submission 4.2.1 - Type 2 Query & Submission via External Registration Portal 4.2.2 - Type 2 Query & Submission via the I- SEM Registration System 4.2.3 - Type 3 Query & Submission via the I-SEM Registration System 4.2.4 - Type 3 Submissions: common attributes and validations 4.3 - Balancing Market Registration - Queries 4.3.1 - Registration Query - Methods 4.3.2 - Registration Query - Elements & Validations 4.4 - Balancing Market Registration - Submission 4.4.1 - Registration Submit – User 4.4.2 - Registration Submit – Party Data 4.4.3 - Registration Submit – Participant 4.4.4 - Registration Submit – Unit Data 4.4.5 - Registration Submit – Trading Site
I-SEM TS Volume C – Balancing Market
22
I-SEM TS Content Overview – Sample Table of Contents
1
• Disclaimer and Content Information
2 • Introduction
3
• Treatment of time in the I-SEM Market Systems
4
• Balancing Market Registration
5 • Balancing Market Trading
6 • Reporting
5 - Balancing Market Trading 5.1 - Introduction 5.2 - Market Interface Data Submission Process 5.2.1 - Default and Trading Day “complex” Commercial Offer Data 5.2.2 - Default and Trading Day Technical Offer Data 5.3 - Message Validation and Sample XML 5.4 - Commercial Offer Data 5.4.1 - Simple Offers 5.4.2 - Complex Offers 5.5 - Technical Offer Data 5.5.1 - Generator TOD Set 5.5.2 - Demand Technical Offer Data 5.5.3 - Technical Offer Data Choice 5.6 - Physical Notifications (PNs) 5.6.1 - Methods and Data Groupings 5.6.2 - Data Elements and Validations 5.6.3 - Sample PN XML Template(s) & Responses
I-SEM TS Volume C – Balancing Market
23
I-SEM TS Content Overview – Sample Table of Contents
1
• Disclaimer and Content Information
2 • Introduction
3
• Treatment of time in the I-SEM Market Systems
4
• Balancing Market Registration
5 • Balancing Market Trading
6 • Reporting
6 - Reporting 6.1 - Introduction 6.2 - MPI Reports 6.3 - Type 3 Report List/Reporting Query Process 6.4 - Report Query Validation 6.5 - MPI Reports and Content Details 6.6 - Market Infrastructure Reports 6.7 - MSUR-EMFIP Reports 6.8 - Settlement Reports
I-SEM TS Volume C – Balancing Market
24
MPI Data Schemas Indicative (from TLG 2 – 13/04/2016)
None/Minimal Change
•Trading Site parameters
Extended Schemas
•Query
•Participant details
•Unit details
•Settlement Reallocation
•Generator Offer details
•Unit Under Test
•Contact details
•Validation Technical Offer Data
•Technical Offer Data
New/Changed Schema
•Commercial Offer Data
•Application details
•Participant Unit Market (CRM, NEMO, BAL, AoLR) Details
Note: Specific data changes may change during completion of design
Balancing Market Data Sets (in Schemas)
25
Data Sets / Transactions New Changing
Forecast Availability N Y
Pumped Storage Parameters N Y
Energy Limit N Y
Simple Commercial Offer Data Y n/a
Complex Commercial Offer Data Y n/a
Physical Notifications Y n/a
VTOD N Y
VTOD Choice N N
Registration Query N Y
Registration Submit - User N Y
Registration Submit – Party Y n/a
Registration Submit – Participant Y n/a
Registration Submit - Unit N Y
Registration Submit – Trading Site Y Y
MDP N Y
Summary No.
New interfaces: 6
Changed Interfaces: 8
Unchanged Interfaces: 1
Total No.: 15
Overall Interface Overview
26
Participants
NEMO
JAO
CRM
Clearing
Market Management
Registration
Balancing Market EirGrid TSO & Internal
Over 40 Balancing Market Interfaces with
EirGrid Systems
REMIT & Transparency
MDP Bank
Balancing Market Interfaces
27
New Changing Rationale
Offer Data
Forecast Availability N Y Different Time convention (start-time, end-time not trading hour/interval)
Pumped Storage Parameters N Y Removed parameters no longer relevant for I-SEM
Energy Limit N Y Different Time convention (start-time, end-time not trading hour/interval)
Simple COD Y n/a New structure to enable submission of simple COD (Incs&Decs)
Complex COD Y n/a
New structure to enable submission of complex COD (Start up costs(or shutdown for DSUs), No Load
and Incs&Decs)
(Note: Similar to existing price_maker_detail element)
Physical Notifications Y n/a New structure to enable submissions of PNs (A01 or A04 formats, depending on the unit type)
VTOD
VTOD N Y Minor changes to fields included in VTOD
VTOD Choice N N No change expected
Market Interface (MI Schema)
Note 1: SRAs; replaced by ARA concept (per rules liaison group discussion)
Note 2: Detailed schema design is under review and is subject to change
Two methods supported: Query and Submit
Balancing Market Interfaces
28
New Changing Rationale
Query N Y To include different element groups (as specified below)
Submit - User N Y To include system access information, contact information, authorisations and
notifications
Submit – Party Y n/a To enable party registration as part of registration workflow management.
Submit – Participant Y n/a To enable participant registration, by market as part of registration workflow
management; now includes banking information
Submit - Unit N Y To enable registration data capture for different markets and unit types
Submit – Trading Site Y Y To enable ISEM structure for Trading Sites
Registration Interface (MPR Schema) - Draft
Note 1: Unit Under Test removed from Registration – is facilitated via submissions of PNs (Per rules liaison group discussions)
Note 2: Detailed schema design is under review and is subject to change
Balancing Market Interface Specifications – Technical
29
• UTC time is standard to be used in Type 3 interfaces
• Type 2 interfaces (portal) will accept entries in local time
Time Representation
• Resource_type has been removed from all interfaces
Resource Types
• The field name representation for Registration interfaces is changing to CamelCasing
• E.g. PARTICIPANT_NAME becomes ParticipantName
• Remaining datasets (including Meter Data) will not adopt this convention
• Vendor has migrated the Registration component to new technology aligned with industry standard
Camel Casing
Example Interface – Physical Notifications
30
• Physical Notifications are MW profiles that are submitted by the Participants at any point up to the Balancing Market Gate Closure for the associated Imbalance Settlement Period.
• They represent a Participants best estimate of its intended generation and/or consumption.
• Can be either A01 or A04 curve type ENTSOE formats depending on the type of unit as set out below.
Overview of Physical Notifications
• When submitted, PNs will be validated in the MPI to ensure that the entire set of PNs is feasible according to the relevant Unit’s technical characteristics, and that the dataset covers the correct timeframe.
• The latest validated and approved set of PNs is retrieved by every execution of Operational Schedule Runs.
Process
• Mandatory Data Elements: market_submit, sem_pn_submit
• Optional Data Elements: identifier [external_id]
Method: Submit
• Mandatory Data Elements: market_query, sem_pn_submit
• Optional Data Elements: identifier [external_id]
• Note: For query the participant can specify time range and a resource name to query against.
Method: Query
Example Interface – Physical Notifications
31
Name Validation Submission Query market_submit/market_query Element
participant_name The “participant_name” attribute is mandatory and the Participant should be registered in the SEM. It should not be more than 12 characters.
Mandatory Mandatory
application_type Specific application request type. Mandatory Mandatory
Must be “BM”.
trading_date YYYY-MM-DD Mandatory Mandatory
There are different validation rules based on the message type, which are detailed in each individual message section below.
participant_name Must be STRING. Mandatory Mandatory
Must be valid in combination with USER_NAME. Must have system privileges to allow Market Trading.
user_name Must be STRING Mandatory Mandatory
Must be valid in combination with PARTICIPANT_NAME. Must have system privileges to allow Market Trading.
version_no The current version of the template. Mandatory Mandatory
Must be “1.0”. mode Must be NORMAL. Mandatory Mandatory
Note: The above fields are common to the market submit/ market-query elements of all data elements. They are used to identify the records against which the submission and queries are to be made.
Example Interface – Physical Notifications
32
Name Validation Submission Query Identifier Element (optional)
external_id Must be STRING. Optional Not Applicable
sem_pn_submit Element
curve_type
Must be ‘A01’ or ‘A04’ (as utilised in the ENTSO-E EDI standards)
Mandatory Not Applicable
Submit either A01 or A04 for : - AOLR Unit, - the registered capacity of the Unit is <10MW, - or the Unit is not Dispatchable. Otherwise, value must be A04.
resource_name Must be VARCHAR2(32).
Mandatory Optional Must be valid Resource and belong to the Participant and User.
from_date_time
Must be of form ‘YYYY-MM-DD’
Mandatory Optional
must cover from next open ISP to the end of the Trading Day for which the BM has most recently closed Contiguous curve for submitted period Feasible in terms of time-based technical parameters (e.g. Min On Time, Min Off Time, Dwell Times, etc) Consistent with daylight savings “from_time” must be less than “to_time” “from_time” must be at the start of a minute
from_mw
Must be >=0 for all Generators part from Pumped Storage Units Mandatory Not applicable
Feasible in terms of all volume-based technical parameters (e.g. Ramp rates, dwell times, min and max capacities etc.) Mandatory Not applicable For A01 type, from_mw=to_mw
Example Interface – Physical Notifications
33
Name Validation Submission Query sem_pn_submit Element (continued)
to_date_time
Must be of form ‘YYYY-MM-DD’
Mandatory Optional
must cover from next open ISP to the end of the Trading Day for which the BM has most recently closed
Contiguous curve for submitted period
Feasible in terms of time-based technical parameters (e.g. Min On Time, Min Off Time, Dwell Times, etc)
Consistent with daylight savings
to_time > from_time
to_time must be at the start of a minute
to_mw For A01 type, from_mw=to_mw Mandatory n/a under_test_flg String (1) “Y” or “N” Optional n/a reason String (120) Optional n/a
to_date_time
Must be of form ‘YYYY-MM-DD’
Mandatory Optional must cover from next open ISP to the end of the Trading Day for which the BM has most recently closed
Contiguous curve for submitted period
Starting point has been the current reports/publication
• Where relevant, existing reports will be retained (or amended as necessary)
In addition, feedback from Participants has been extremely helpful
• Feedback from previous discussions in relation to data that Participants wish to be published has been captured by the project team
• e.g. data listed by submission by Viridian in March 2016
As for the current SEM, reports and publications are categorised as one or more of:
• Member Private (via MPI for individual Participant, e.g. invoices etc)
• Member Public (via MPI for all Participants, via Type 2 or 3)
• General Public (via EirGrid website)
34
Balancing Market Reports/Publications
Report Name Report Description MPI Website Annual Combined Loss
Adjustment Factors
(023)
Annual Combined Loss Adjustment Factors, per Unit for the
following Year Once every
year (Mpub) Once every
year
Annual Load Forecast
(018)
Annual Load Forecast by Jurisdiction and aggregated, by
Trading Period for the Calendar Year Once every
year (Mpub) Once every
year
35
Annual Reports
Note: reports above are those automatically created by Balancing Market systems. Many other reports (e.g. market parameters) are published but are created and loaded manually.
36
Monthly Reports
Note: reports above are those automatically created by Balancing Market systems. Many other reports (e.g. market parameters) are published but are created and loaded manually.
Report Name Report Description MPI Website Monthly Load Forecast &
Assumptions
(025)
Monthly Load Forecast and assumptions by Jurisdiction and
aggregated, for each Trading Period in the following Month Once every
month (MPub)
Once every month
Registered Capacity Report
(037)
Registered Capacity and fuel type information for Units, as at
the date of publication Once every
month (MPub)
Once every month
37
Daily Reports (Ex-Ante/Within Day) – Forecasts (1/2)
Report Name Report Description MPI Website Daily Load Forecast Summary
(020)
Daily Load Forecast Summary, by Jurisdiction for each Trading Period in
the following 4 Trading Days Following
receipt of each Accepted Four
Day Load Forecast feed
(MPub)
Daily
Four Day Rolling Wind Unit
Forecast
(027)
Rolling four day wind forecast by Wind Unit Four times per day, at schedule
times (MPub)
Four Day Aggregated Rolling Wind
Forecast
(028)
Rolling four day wind forecast by jurisdiction Four times per day, at schedule
times (MPub)
Daily
Outage-adjusted Wind Unit
Forecast
(039)
Outage-adjusted Wind forecast MW at a unit level covering 15 minute
periods over the next 36 hours (as used by AOLR). Four times per
day, immediately
following receipt (MPub)
Outage-adjusted Solar Unit
Forecast
(040)
Outage-adjusted Solar forecast MW at a unit level covering 15 minute
periods over the next 36 hours. Four times per
day, immediately
following receipt (MPub)
Aggregated Wind Forecast
(075)
Single aggregated forecast of all wind units included in the earlier
reports, published along with the standard wind forecast Four times per
day at scheduled times
(MPub)
Dynamic Report
Forecast system load
(076)
Daily load forecast for each ISP in the trading day, updated with TSO
forecast updates Daily (MPub) Dynamic Report
38
Daily Reports (Ex-Ante/Within Day) – Forecasts (2/2)
Report Name Report Description MPI Website Forecast Imbalance
(042)
Sum of PNs, Net Interconnector schedule, TSO demand
forecast, TSO renewables forecast (for non dispatchable
renewables) and the resulting calculated imbalance for the
next Imbalance Settlement Period until the end of the latest
Trading Day for which the Day Ahead Market has closed
Every Hour (MPub)
Every Hour
Daily Interconnector NTC (TD-
2, TD-1)
(021, 086)
NTC for each Interconnector, TD-2 NTC for each Trading Day Following results from
the Co-ordinated Capacity
Calculator (MPub)
Following receipt of
results from the Co-
ordinated Capacity
Calculator
Net Imbalance Volume
Forecast
(088)
Net Imbalance Volume for the Trading Day Updated every 30 minutes (MPub)
Updated every 30 minutes
39
Daily Reports (Ex-Ante/Within Day) – COD and TOD
Report Name Report Description MPI Website Daily Technical Offer Data
(011)
Daily Technical Offer Data for all Units, for the Trading Day TD+1 (MPub) TD+1
Bid Offer Data Report
(053)
Report containing Inc/Dec data submitted by Unit and
Imbalance Settlement Period Immediately
following each
Balancing Market Gate Closure time
(MPub)
TD+1
Forecast Availability
(012)
Forecast Availability for all Units, by Trading Period TD+1 (MPub) TD+1
Commercial Offer Data
(013)
Commercial Offer Data for all Units, by Trading Period for the
Trading Day TD+1 (MPub) TD+1
40
Daily Reports (Ex-Ante/Within Day) – Ex-Ante Market Results / PNs
Report Name Report Description MPI Website Aggregated Contracted
Quantities for Generation
(078)
Total contracted quantities submitted to the TSO for imbalance
settlement for each ISP in the Trading Day for all generator
units. These should be published for ISPs for which the gate is
still open.
Hourly (MPub)
Dynamic Report
Aggregated Contracted
Quantities for Demand
(079)
Total contracted quantities submitted to the TSO for imbalance
settlement for each ISP in the Trading Day for all supplier units. Hourly (MPub)
Dynamic Report
Aggregated Contracted
Quantities for Wind
(080)
Total contracted quantities submitted to the TSO for imbalance
settlement for each ISP in the Trading Day for wind generator
units only.
Hourly (MPub)
Dynamic Report
Physical Notifications
(052)
Physical Notifications as submitted by Participants in respect of
Units. Will contain unit identifier, time stamp and PN value. Published each time
PNs submitted
and accepted (MPriv)
Aggregated Physical
Notifications
(077)
Aggregation of all latest PNs submitted to the TSO for each ISP
in the Trading Day Hourly (MPub)
Dynamic Report
Final Physical Notifications
(089)
Final Physical Notifications for the entire Trading Day TD+1 (MPub) TD+1
41
Daily Reports (Ex-Ante/Within Day) – Operational Schedules
Report Name Report Description MPI Website LTS Operational Schedule (001) LTS Operational Schedule, as produced by the TSO as part of its
scheduling and dispatch processes, containing schedules per
Generator Unit and Demand Side Unit for the Optimisation
Time Horizon
After approved LTS
(MPriv)
TD+1 (MPub)
TD+1
RTC Operational Schedule
(002)
RTC Operational Schedule, as produced by the TSO as part of
its scheduling and dispatch processes, containing schedules
per Generator Unit and Demand Side Unit for the Optimisation
Time Horizon
After approved RTC
(MPriv)
TD+1 (MPub)
TD+1
RTD Operational Schedule
(003)
RTD Operational Schedule, as produced by the TSO as part of
its scheduling and dispatch processes, containing schedules
per Generator Unit and Demand Side Unit for the Optimisation
Time Horizon
After approved RTD
(MPriv)
TD+1 (MPub)
TD+1
42
Daily Reports (Ex-Ante/Within Day) – Imbalances
Report Name Report Description MPI Website System Shortfall Imbalance
Index
(084)
System Shortfall Imbalance Index for the Trading
Day Updated hourly
(MPub) Updated hourly
System Imbalance Flattening
Factor
(085)
System Imbalance Flattening Factor for the Trading
Day Updated hourly
(MPub) Updated hourly
Imbalance Price Report
(008)
Imbalance Price by Imbalance Pricing Period, for
all Imbalance Settlement Periods in the Trading
Day (updated following each Imbalance Price
calculation and highlighting where a default price
has been applied)
Following calculation of the Imbalance
Price for an Imbalance Pricing
Period (MPub)
Following calculation of the Imbalance Price for an Imbalance
Pricing Period
Imbalance Price Report
(009)
Imbalance Price by Imbalance Settlement Period Following the final calculation of the
Imbalance Price for an Imbalance
Settlement Period (MPub)
Following the final calculation of the Imbalance Price for an Imbalance
Settlement Period
Imbalance Price Supporting
Information
(050)
The marginal BM price, Net imbalance volume,
QBOAS, associated PBOAS, and related flags and
tags associated with the QBOAS as determined by
the Imbalance Pricing calculation
Immediately following calculation
of the Imbalance Price for an
Imbalance Pricing Period (MPub)
43
Daily Reports (Ex-Ante/Within Day) – Other
Report Name Report Description MPI Website Unit Under Test
(083)
List of units under test scheduled for the following Trading Day TD-1 (MPub) TD-1 (MPub)
Daily Transmission Outage
Schedule
(026)
Daily scheduled outages for all Units for the Trading Day TD-1 (MPub) TD-1 (MPub)
Daily Trading Day Exchange
Rate
(010)
Exchange Rate for the Trading Day TD-2 (MPub) TD-2 (MPub)
Daily Generator & DSU Outage
Schedules
(005)
Daily Generator & DSU Outage Schedules, by Unit for the
Trading Day TD-1 (MPub) TD-1 (MPub)
44
Daily Reports (Ex-Post) 1/2
Report Name Report Description MPI Website Daily Dispatch Instructions
(D+1) (006)
Accepted Dispatch Instructions, as provided by the
TSO on D+1, per Unit for the Settlement Day TD+1 (MPub) TD+1
Daily Dispatch Instructions
(D+4) (007)
Accepted Dispatch Instructions, as provided by the
TSO on D+4, per Unit for the Settlement Day TD+4 (MPub) TD+4
Daily Demand Control Data
Transaction
(014)
Daily load shedding volume, by Imbalance
Settlement Period in the Settlement Day Daily where
demand control occurs TD+1 (MPub)
Daily where demand control
occurs TD+1
Daily Generator Unit Technical
Characteristics Data Transaction
(015)
Daily Outturn Availability and fuel use indicators by
Unit, spot values for the Trading Day TD+1 (MPub) TD+1
Daily Energy Limited Generator
Unit Technical Characteristics
Data Transaction
(016)
Redeclared Energy Limit by Energy Limited Unit, for
the relevant Trading Day TD+1 (MPub) TD+1
Daily Metered Data
(017)
Meter Data by Unit and Imbalance Settlement Period
for the Settlement Day. Includes IC Flows. WD+1 WD+5
(MPub)
WD+1 WD+5
Average System Frequency
(029)
Average Frequency by Imbalance Settlement Period
for the calendar Day TD+1 (MPub) TD+1
SO Interconnector Trades
(030)
SO Interconnector Trades, for each Interconnector,
by Imbalance Settlement Period for the Calendar Day TD+1 (MPub) TD+1
Unit Data
(031)
Unit resource and fuel type for the relevant Trading
Day TD+1 (MPub) TD+1
Report Name Report Description MPI Website Initial Interconnector Flows and
Residual Capacity
(022)
Initial metered Interconnector flow and difference between metered
and the final ICRP for the day, per Imbalance Settlement Period for the
Settlement Day
WD+5 (MPub) WD+5
Daily KPI – Schedules Publication
(032)
Performance of the Market Operator against defined timescales for
publication of all required Operational Schedules, for a Trading Day TD+1 (MPub) TD+1
Daily KPI – Gate Publication
(033)
Performance of the Market Operator against defined timescales for
Balancing Market Gate Closure, for a Trading Day TD+1 (MPub) TD+1
Daily Residual Error Volume
(REVLF) D+5
(034)
Daily Residual Error Volume (REVLF) D+5 report, by Imbalance
Settlement Period and Jurisdiction for the Settlement Day WD+5 (MPub) WD+5
Balancing & Imbalance Market
Costs View
(041)
Settlement Period Imbalance Volume (MWhr) times the Imbalance
Period Price Half Hourly
(MPub) Half Hourly
Metered Volumes by Jurisdiction
(066)
Metered Generation, Metered Demand, Net Jurisdictional flow,
Residual Error Volume aggregated by Jurisdiction, by Imbalance
Settlement Period in the Settlement Day
Energy Settlement\One
Working Day D+1
Energy Settlement\Six Working Day
D+5
Average Outturn Availability
(082)
30 minute availability as the average version of spot Outturn Availability
for the Imbalance Settlement Period. TD+1 (MPub) TD+1
Settlement System Performance
(047)
KPI report detailing the performance of the Settlement System
including time to complete tasks/processes, compared to target
processing timescales
On Demand
Anonymised Inc/Dec Curves
(081)
Sum of all valid submitted Inc/Dec values, by volume and price, both up
and down Hourly (MPub) Dynamic Report 45
Daily Reports (Ex-Post) 2/2
46
Settlement Reports (1/2)
Report Name Report Description MPI Website Settlement Statement
(043)
Statement of settlement amounts As per the Settlement Calendar (MPriv)
Settlement Report
(044)
Report containing information supporting shadow settlement,
such as ISP weighting factors, QBOATOTSO, QBOAUNDEL,
QANF, QBOABIAS.
As per the Settlement Calendar (MPriv)
Settlement Document
(045)
Settlement document for wholesale energy trading amounts
for the Balancing Market and/or CRM As per the Settlement
Calendar (MPriv)
Participant Information
Report (PIR)
(090)
A report providing the backing information for settlement
statements and documents (including proportions of
metering etc.)
As per the Settlement Calendar (MPriv)
Auto Reallocation Requests
(046)
A report showing Auto Reallocation Requests As per the Settlement Calendar (MPriv)
Collateral Report
(048)
Report containing collateral information for a Participant Daily but up to hourly (MPriv)
Collateral Refund Notice
(049)
Notice of a Collateral Refund, including relevant details Daily but up to hourly (MPriv)
Energy Market Financial
Publication – Indicative
(055)
Energy Market Financial Publication - Indicative Daily, Settlement Day + One working day
(MPub)
Daily, Settlement Day + One
working day
Energy Market Financial
Publication – Initial
(056)
Energy Market Financial Publication - Initial Daily, Settlement Day + Five Working days
(MPub)
Daily, Settlement Day + Five
Working days
Energy Market Information
Publication – Indicative
(057)
Energy Market Information Publication - Indicative Daily, Settlement Day + One Working Day (MPub)
Daily, Settlement Day + One Working Day
47
Settlement Reports (2/2)
Report Name Report Description MPI Website Energy Market Information
Publication – Initial
(058)
Energy Market Information Publication - Initial Daily, Settlement Day +
Five Working Days (MPub)
Daily, Settlement Day + Five Working
Days
Capacity Market Financial
Publication – Indicative
(059)
Capacity Market Financial Publication - Indicative Capacity Period + Three Working
(MPub)
Capacity Period + Three Working
Capacity Market Financial
Publication – Initial
(060)
Capacity Market Financial Publication - Initial Capacity Period + Seven Working
(MPub)
Capacity Period + Seven Working
Capacity Market Information
Publication – Indicative
(061)
Capacity Market Financial Publication - Indicative Capacity Period + Three Working days
(MPub)
Capacity Period + Three
Working days
Capacity Market Information
Publication – Initial
(062)
Capacity Market Financial Publication - Initial Capacity Period + Seven Working days
(MPub)
Capacity Period + Seven
Working days
Metered Generation Information
Publication – Indicative
(063)
Metered Generation Information Publication - Indicative Daily, Settlement Day + One Working Day
(MPub)
Daily, Settlement Day + One Working
Day
Metered Generation Information
Publication – Initial
(064)
Metered Generation Information Publication - Initial Daily, Settlement Day +
Five Working Days (MPub)
Daily, Settlement Day + Five Working
Days
DOG/PUG/TOLOG/TOLUG for
Over/Under Generation
(065)
Discount for Over Generation, Premium for Under Generation and
Dispatch Offer price for each Unit, per Imbalance Settlement Period
for the Settlement Day
TD+1
Report Name Report Description MPI Website List of Registered Units
(035)
List of all units registered in I-SEM. It will incorporate all
changes made up to the time the report is run. Once a day
where a change to the
list occurs (MPub)
Once a day where a
change to the list occurs
List of Registered Parties
(036)
List of all registered parties in I-SEM. It will incorporate all
changes made up to the time the report is run. Once a day
where a change to the
list occurs (MPub)
Once a day where a
change to the list occurs
AOLR Unit Report
(038)
Summary of trading inputs and outputs in respect of AOLR
trading activity for AOLR Units Available
once all data that makes up the AOLR unit
display has been finalised
Settlement Calendar
(067)
Settlement Calendar - including Payment Calendar On demand On demand
Annual Combined Loss
Adjustment Factors (023)
Annual Combined Loss Adjustment Factors, per Unit for the
following Year Every time a
new unit joins the market
(MPub)
Every time a new unit joins
the market
Daily Interconnector NTC
(Event Driven)
(087)
NTC for each Interconnector, TD recalculation following a
major system event Event driven Event driven
48
Event Driven Reports
49
Dynamic Reports
Report Name Report Description MPI Website Capacity Payments by Market (069)
Capacity Payments by Market, for each Capacity Period Dynamic Report
Capacity Payments by Unit (070)
Capacity Payments by Unit, for each Capacity Period Dynamic Report
Cross Border Capacity Data (071)
Cross Border Capacity Data for each Capacity Period – North South Tie Line.
Dynamic Report
Dispatch Quantity
(068)
Dispatch Quantity, by Unit for each Imbalance Settlement
Period in the Settlement Day Dynamic Report
Cross Border Weekly Energy
Data
(072)
Cross Border Weekly Energy Data by Jurisdiction (ROI/NI) Dynamic Report
Margin and Loss of Load
Probability Table
(073)
Margin and Loss of Load Probability, for each Imbalance
Settlement Period in the Settlement Day - TABLE Dynamic Report
Make Whole Payment
(074)
Make Whole Payment for each Imbalance Settlement Period in
the relevant Billing Period, by Unit Dynamic Report
Agenda
Welcome and house-keeping
Actions from previous TLG – Balancing Market
CSS Technical Delivery Timeline – Updates and Review
Balancing Market Interface Specifications – I-SEM TS Review
AOB
50
A number of improvements have been made to the I-SEM subsite, making it easier to navigate and find information:
1. Colour Coding and Filter Options in the calendar
51
Website Update
2. Each Liaison Group has its own page tailored to display only relevant information
52
Website Update
3. I-SEM only search functionality
4. Items of interest will be published under Latest I-SEM News:
53
Website Update
Remember to register for I-SEM alerts to receive notifications
54
Website Update
Content Review and Improvements
• Overview and updates to existing sites
• Market Readiness: new content added
New Pages
• Training Page
• Q&A Page
• NEMO Page and Information
A number of developments will be coming soon
1. All queries and feedback should be sent to: I-SEMproject@sem-o.com
2. Queries will be issued with a log number and progress tracked
3. Feedback will be Compiled and circulated to the project team accordingly
55
Query Information and Management
56
TLG Representative (TLR)
In order to streamline communications, each Participant is being asked to nominate a TLG Representative • One TLR and one alternate per participant
• Communications in relation to TLGs going forward will be issued to this distribution list only
• Email will be issued following this TLG – Please respond
Questions?
57
I-SEM Project – Contact Details
58
Web: http://www.sem-o.com/ISEM/ Email: I-SEMproject@sem-o.com Subject: TLG – your topic Thank you