Idd part 1 Interfaces with bsc parties and their Agents




старонка82/82
Дата канвертавання24.04.2016
Памер4.34 Mb.
1   ...   74   75   76   77   78   79   80   81   82

8.5 SAA-I016: (output) Settlement Calendar


Interface ID:

From: SAA-I016

To: CDCA-I034


User:

BSC Party,

BSC Party Agent, SVAA, BSCCo Ltd, CDCA


Title:

Settlement Calendar



BSC reference:

RETA SCH: 4, B, 2.1.1, 2.2.1

SAA SD: 5.2.1, A2

SAA BPM: 3.2, 4.40, CP1222



Mechanism:

Manual, in normal NETA file format, but without header and trailer records, probably as an email attachment



Frequency:

Annual


Volumes:


Interface Requirement:

The SAA Service shall publish the Settlement Calendar once a year to all BSC Parties and Agents, SVAA, BSCCo Ltd and CDCA.




The Settlement Calendar shall include the publication date/time of the calendar, and then the following details for each Settlement Date / Settlement Run Type :


Settlement Date

Settlement Run Type (II/SF/R1/R2/R3/RF/D/DF)

CVA run date (CDCA)++

SVA run date (SVAA, n/a for II for Settlement Days prior to the P253 effective date)++

Settlement Run date (SAA)++

Notification Date (date credit/debit report must reach FAA)**

Payment Date (date money changes hands)**

Notification Period (days between Settlement Date and Notification Date)**

Payment Period (days between Settlement Date and Payment Date)**

Elapsed Days SAA after Settlement

Working Days SAA after Settlement

Working Days SAA before Notification


** indicates fields copied from payment calendar

++ nominal date for runs. Run is any time after 9:00 a.m. on the scheduled date; results to be delivered to next service provider by 9:00 a.m. the next working day.

Physical Interface Details:

The physical structure is included in the SAA tab of the IDD spreadsheet, although the file is not sent over the network as a NETA format file.


8.6 SAA-I017: (output) SAA Data Exception Report


Interface ID:

From: SAA-I017

To: CRA-I030

To: CDCA-I050

To: ECVAA-I020


User:

IAs


ECVAA

CDCA


CRA

SO

SVAA



MIDP

Title:

SAA Data Exception Report



BSC reference:

SAA IRR: SAA1, SAA4, CP595, P78



Mechanism:

Electronic data file transfer, unless stated below as Manual (phone call and / or fax) or via Shared Database




Frequency:

As required



Volumes:


Interface Requirement:

If an exception occurs while processing a received file, the SAA Service shall issue Exception Report to the sender of the file, one of the following:


ECVAA

CDCA (via Shared Database)

CRA (via Shared Database)

SO

IA



SVAA (Manual)

MIDP



The Exception Reports shall include:


File Header of file being processed

Exception Type

Exception Description




8.7 SAA-I018: (output) Dispute Reports


Interface ID:

SAA-I018


User:

BSC Party, BSCCo Ltd, System Operator



Title:

Dispute Reports



BSC reference:

SAA SD: 5.1.4

SAA IRR: SAA10


Mechanism:

Manual


Frequency:

Ad-hoc


Volumes:


Interface Requirement:

The SAA Service shall issue Dispute Reports to BSC Parties, BSCCo Ltd and the SO on an ad-hoc basis.


The contents of these reports to BSC Parties are likely to be defined on an ad hoc basis.
Summary reports to BSCCo Ltd are likely to include the following data:
Number of Disputes in Month, by status

Total Materiality, by status

For each dispute:

Dispute Reference

BSC Parties Involved

Dispute Status

Settlement Period Involved

Materiality

Nature of Dispute

Actions Taken

Outstanding Actions

Expected Resolution Date







8.8 SAA-I021: Receive Acknowledgement of SAA Messages


See Section 2.2.7.

8.9 SAA-I022: Issue SAA Acknowledgement of Messages


See Section 2.2.7.

8.10 SAA-I030: (input) Receive Market Index Data


Interface ID:

SAA-I030


Source:

MIDPs


Title:

Receive Market Index Data



BSC reference:

P78


Mechanism:

Automatic



Frequency:

Daily


Volumes:


Interface Requirement:
The SAA shall receive Market Index Data, from Market Index Data Providers, for each Settlement Day.
The flow shall include:
Market Index Data Provider Identifier

Settlement Date



Period Data (46/48/50)

Settlement Period

Market Index Price

Market Index Volume

Traded Price (to be ignored)

Traded Volume (to be ignored)







1 TLFA functionality was added for the Introduction of Zonal Transmission Losses on an Average Basis (P82), but will not be used.

2 The Omitted Data functionality has been developed, but is disabled.

3 Note that the DF flow ceases publication in Q1/2009

4 Note that the DF flow ceases publication in Q1/2009

5 Where OCNMFD is referred to throughout this document, it should be interpreted as being equivalent to SPLD.

6 Where OCNMFW is referred to throughout this document, it should be interpreted as being equivalent to SPLW.

7 Note that the Contact Name is not included in the CRA-I014 (sub flow 1) sent in response to new and amended data.

8 Note that the Contact Name is not reported in the CRA-I014

9 The Omitted Data functionality has been developed, but is disabled.

10 The Omitted Data functionality has been developed, but is disabled.

11 P98: Note that because the format of the ECVAA-I007 and ECVAA-I008 flows is changing, this flow will also change. The detail of the change will be contained in the IDD where a new version of the flow will be added. The default version of this report will remain the pre-P98 version (i.e. with no report requirements) until further notice.

12 Variation 43

13 Note that flexible reporting preferences for version numbers overrule specific report requirements. For example, in order to receive Matching Data in the ECVAA-I028 a Party must elect to receive V002 of the flow (V001 will be the default) and specify that it wishes to receive Matching Data via a Report Requirement Change Request (ECVAA-I002); a subsequent reversion to V001 of the ECVAA-I028, effected through flexible reporting would negate the Report Requirement Change Request.

14 Note that flexible reporting preferences for version numbers overrule specific report requirements. For example, in order to receive Matching Data in the ECVAA-I029 a Party must elect to receive V002 of the flow (V001 will be the default) and specify that it wishes to receive Matching Data via a Report Requirement Change Request (ECVAA-I003); a subsequent reversion to V001 of the ECVAA-I029, effected through flexible reporting would negate the Report Requirement Change Request.

Balancing and Settlement Code Page of 3 November 2011

© ELEXON Limited 2011
1   ...   74   75   76   77   78   79   80   81   82


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка