Data Record is as defined in the Glossary of the Code Data Transaction Identifier SEM Business Process Supported Frequency, including latest time of delivery Data Records containing best available data Indicative Price Effecting Generation Metering PEG Ex-Post Indicative Setting & Indicative Settlement Each Calendar Day, by 14:00 on the next Calendar Day (D+1) Maker Generator Units and/or Price Taker Generator Units) Initial Price Effecting Generation Metering PEG Initial Price Setting & Initial Settlement Each Calendar Day, by 14:00 on the third next Calendar Day (D+3) Price Maker Generator Units and/or Price Taker Generator Units) Revised Price Effecting Generation Metering PEG Query generation process & Dispute process Ad-hoc, as material data changes are identified. Timelines under Agreed Procedure 13 “Query Generation” and Agreed Procedure 14 “Disputes” Price Maker Generator Units and/or Price Taker Generator Units) Indicative Non Price Effecting Generation Metering NPEG Ex-Post Indicative Settlement Each Week Day, by 14:00 on the next Week Day (D+1) Autonomous Generator Unit Initial Non Effecting Generation Metering NPEG Initial Settlement Each Week Day, by 17:00 on the fourth next Week Day (D+4) Autonomous Generator Unit
Revised Non Price Effecting Generation Metering NPEG generation process & Dispute process Ad-hoc, as material data changes are identified. Timelines under Agreed Procedure 13 “Query Generation” and Agreed Procedure 14 “Disputes” Autonomous Generator Unit Resettlement 1 Non Price Effecting Generation Metering NPEG Resettlement 1 On a Week Day, by 14:00 in time for the M+4 Resettlement as defined in the Settlement Calendar and no earlier than one month before the relevant Resettlement Distribution Connected Autonomous Generator Unit Resettlement 2 Non Price Effecting Generation Metering NPEG Resettlement 2 On a Week Day, by 14:00 in time for the M+13 Resettlement as defined in the Settlement Calendar and no earlier than one month before the relevant Resettlement Distribution Connected Autonomous Generator Unit Indicative Aggregated Inter Jurisdiction Metering CJF Ex-Post Indicative Settlement Each Week Day, by 14:00 on the next Week Day (D+1) Net Inter Jurisdictional Flow Initial Aggregated Inter Jurisdiction Metering CJF Initial Settlement Each Week Day, by 17:00 on the fourth next Week Day (D+4) Net Inter Flow
Revised Aggregated Inter Jurisdiction Metering CJF Query generation process & Dispute process Ad-hoc, as material data changes are identified. Timelines Agreed Procedure 13 “Query Generation” and Agreed Procedure 14 “Disputes” Net Jurisdictional Flow Indicative Aggregated Demand Price Effecting Metering PED Ex-Post Indicative Price Setting & Indicative Settlement Each Calendar Day, by 14:00 on the next Calendar Day (D+1) Trading Site Supplier Unit (that relates to single Trading Site with access for its generation) Initial Aggregated Demand Price Effecting Metering PED Initial Price Setting & Initial Settlement Each Calendar Day, by 14:00 on the third next Calendar Day (D+3) Trading Site Supplier Unit (that relates to single Trading Site with Access for its generation) Revised Aggregated Demand Price Effecting Metering PED Query generation process & Dispute process Ad-hoc, as material data changes are identified. Timelines under Agreed Procedure 13 “Query Generation” and Agreed Procedure 14 “Disputes” Trading Site Supplier Unit (that relates to single Trading Site with Access for its generation) Firm Firm Firm
Indicative Aggregated Demand Metering NPED Ex-Post Indicative Settlement Each Week Day, by 14:00 on the next Week Day (D+1) Supplier Unit Demand Side Unit Associated Supplier Unit Trading Site Supplier Unit (that relates to single Trading Site with full Access for its generation) Initial Aggregated Demand Metering NPED Initial Settlement Each Week Day, by 17:00 on the fourth next Week Day (D+4) Supplier Unit Demand Side Unit Associated Supplier Unit Trading Site Supplier Unit (that relates to single Trading Site with full Access for its generation) Resettlement 1 Aggregated Demand Metering NPED Resettlement 1 On a Week Day, by 14:00 in time for the M+4 Resettlement as defined in the Settlement Calendar and no earlier than one before the relevant Resettlement Supplier Unit Demand Side Unit Associated Supplier Unit Trading Site Supplier Unit (that relates to single Trading Site with full Access for its generation)
The Data Transaction is delivered under the most stringent of the timeframes if a Data Transaction fulfils more than one business requirement. A Data Transaction identifier of “ALL” is used in the TRANSMISSION_ID in the file, and contains all for which the Meter Data Provider is responsible for providing to fulfil the relevant business process. For example, a Data Provider is responsible for the following three Data Transactions, all related to the same business requirement – Ex-Post Indicative Settlement. Data Transaction Identifier Business Process Supported Frequency, including latest time of delivery Data Records containing best available data Indicative Price Effecting Generation Metering PEG Ex-Post Indicative Price Setting & Indicative Settlement Each Calendar Day, by 14:00 on the next Calendar Day (D+1) Price Maker Generator Units Price Taker Generator Units Indicative Non Price Effecting Generation Metering NPEG Ex-Post Indicative Settlement Each Week Day, by 14:00 on the next Week Day (D+1) Autonomous Generator Unit Indicative Aggregated Jurisdiction Metering CJF Ex-Post Indicative Settlement Each Week Day, by 14:00 on the next Week Day (D+1) Net Inter Jurisdictional Flow Through suitable registration with the Market Operator, the Meter Data Provider may compress these three Data Transactions (each a different file send) into one file to support Ex-Post Indicative Settlement (and Ex-Post Indicative Price Setting as a consequence) as follows: Data Transaction Identifier Business Process Supported Frequency, including latest time of delivery Data Records containing best available data All data required from Meter Data Provider ALL Ex-Post Indicative Setting & Indicative Settlement Each Calendar Day, by 14:00 on the next Calendar Day (D+1) Price Maker Generator Units Price Taker Generator Units Autonomous Generator Unit Net Inter Jurisdictional Flow
# Procedural Step Timing Auto/Manual Who Linkage 1 Determine what Data Records (Unit, Net Jurisdictional Flow, etc.) are due to be included in Data Transaction(s) to MO for that Settlement Day. If this is not the Indicative to the MO, ensure that the full set of Data Records in the Indicative file-send are included Every Working Day: 3 Working Days before the relevant Settlement Day Manual Meter Data Provider PRECEDING: Agreed Procedure 1 “Participant & Unit Registration and Deregistration” (Where updates to Unit registration are communicated) FOLLOWING: 2 2 Determine the division of Data Records among the Data Transactions Every Working Day: 3 Working Days before the relevant Settlement Day Manual Meter Data Provider PRECEDING: Agreed Procedure 1 “Participant & Unit Registration and Deregistration” the Meter Data Provider updates their own registration with the MO for the Data Records in the Data Transaction (ALL or PEG / NPEG / CJF / PED / NPED)) FOLLOWING: 3, 4, 5, 6, 7, 8, 9, 10 3 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support Ex-Post Indicative Price Setting for the Trading Day? Every Working Day: 3 Working Days before the relevant Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 1,2 FOLLOWING: 3.1, 3.2 3.1 If yes, create the appropriate Data Records over the Settlement Data containing Price Setting Data determined in steps 1 and 2 By 14:00 the Calendar Day after the Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Data Provider PRECEDING: 3 FOLLOWING: 4 3.2 If no, do nothing PRECEDING: 3 FOLLOWING: 4
4 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support Ex-Post Indicative Settlement for the Settlement Day that have not been covered by Step 3.1? Every Working Day: 3 Working Days before the relevant Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 3.1, 3.2 FOLLOWING: 4.1, 4.2 4.1 If yes, create the appropriate Data Records for the Settlement Data containing Effecting Data determined in steps 1 and 2 If Price Effecting Data included in step 3.1, by 14:00 the Calendar Day after the Settlement Day, otherwise by 14:00 the Week Day after the Settlement Day Automatic or manual (at the discretion of the Data Provider) Meter Data Provider PRECEDING: 4 FOLLOWING: 5 4.2 If no, do nothing PRECEDING: 4 FOLLOWING: 5 5 If Data Records created in step 3.1 or step 4.1 send the Data Records in the Transaction(s) determined in step 1 to the Market Operator If Effecting Data included, by 14:00 the Calendar Day after the Settlement Day, otherwise by 14:00 the Week Day after the Settlement Day Automatic Type 3 Channel Meter Data Provider PRECEDING: 4.1, 4.2 FOLLOWING: 6, 17 6 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support Initial Price Setting for the Settlement Day? Every Working Day: 3 Working Days before the relevant Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 5 FOLLOWING: 6.1, 6.2
6.1 If yes, update the appropriate Data Records for the Settlement Data containing Effecting Data determined in steps 1 and 2 By 14:00 three Calendar Days after the Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 6 FOLLOWING: 7 6.2 If no, do nothing PRECEDING: 6 FOLLOWING: 7 7 Does the Data Provider have a responsibility to deliver a Data Transaction to support Initial Settlement for the Settlement Day? Every Working Day: 3 Working Days before the relevant Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 1,2 FOLLOWING: 6.1, 6.2 7.1 If yes, update the appropriate Data Records for the Settlement Data containing Non-Price Effecting Data determined in steps 1 and 2 If Price Effecting Data included, by 14:00 three Calendar Days after the Settlement Day, otherwise by 17:00 four Week Days after the Settlement Day Automatic or manual (at the discretion of the Data Provider) Meter Data Provider PRECEDING: 7 FOLLOWING: 8 7.2 If no, do nothing PRECEDING: 7 FOLLOWING: 8
8 If Data Records created in step 6.1 or step 7.1 send the collated Data Records in the Transaction(s) determined in step 1 to the Market Operator If Price Effecting Data included, by 14:00 three Calendar Days after the Settlement, otherwise by 17:00 four Week Days after the Settlement Day Automatic Type 3 Channel Meter Data Provider PRECEDING: 7.1, 7.2 FOLLOWING: 9, 17 9 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support Resettlement 1 for the Settlement Day? Before deadline for the first Data Transaction submission to MO for that Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 8 FOLLOWING: 9.1, 9.2 9.1 If yes, update the appropriate Data Records for the Resettlement 1 containing Effecting Data determined in steps 1 and 2 Before deadline for the first Data Transaction submission to MO for that Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 9 FOLLOWING: 10 9.2 If no, do nothing PRECEDING: 9 FOLLOWING: 10 10 If Data Records created in step 9.1 send the Data Records in the Transaction(s) determined in step 1 to the Market Operator By 14:00 on the Day of the Resettlement 1 indicated in the Settlement Calendar Automatic Type 3 Channel Data Provider PRECEDING: 9.1, 9.2 FOLLOWING: 11, 17 11 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support Resettlement 2 for the Settlement Day? Before deadline for the Data Transaction submission to MO for that Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Data Provider PRECEDING: 10 FOLLOWING: 11.1, 11.2
11.1 If yes, update the appropriate Data Records for the Resettlement 2 containing Non-Price Effecting Data determined in steps 1 and 2 Before deadline for the Data Transaction submission to MO for that Settlement Day Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 11 FOLLOWING: 12 11.2 If no, do nothing PRECEDING: 11 FOLLOWING: 12 12 If Data Records created in step 11.1 send the Data Records in the Transaction(s) determined in step 1 to the Market Operator By 14:00 on the Day of the Resettlement 2 indicated in the Settlement Calendar Automatic Type 3 Channel Meter Data Provider PRECEDING: 11.1, 11.2 FOLLOWING: 13, 17 13 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support a Data Query or Settlement Query for the Settlement Day? As soon as possible, within the timelines for a data Manual Data Provider PRECEDING: 12 FOLLOWING: 13.1, 13.2 13.1 If yes, update the appropriate Data Records for the Data Query or Settlement Query containing Non-Price Effecting Data determined in steps 1 and 2 As soon as possible, within the timelines for a data Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 13 FOLLOWING: 14 13.2 If no, do nothing PRECEDING: 13 FOLLOWING: 14 14 If Data Records created in step 13.1 send the Data Records in the Transaction(s) determined in step 1 to the Market Operator As soon as possible, within the timelines for a data query Automatic Type 3 Channel Meter Data Provider PRECEDING: 13.1, 13.2 FOLLOWING: 15, 17 15 Does the Meter Data Provider have a responsibility to deliver a Data Transaction to support a Dispute for a single Settlement Day? As soon as possible, within the timelines for a data query Automatic Meter Data Provider PRECEDING: 14 FOLLOWING: 15.1, 15.2
15.1 If yes, update the appropriate Data Records for the Data Query or Settlement Query containing Non-Price Effecting Data determined in steps 1 and 2 As soon as possible, within the timelines for a data query Automatic or manual (at the discretion of the Meter Data Provider) Meter Data Provider PRECEDING: 15 FOLLOWING: 16 15.2 If no, do nothing PRECEDING: 15 FOLLOWING: 16 16 If Data Records created in step 15.1 send the Data Records in the Transaction(s) determined in step 1 to the Market Operator As soon as possible, within the timelines determined by the Dispute Resolution Board Automatic Type 3 Channel Data Provider PRECEDING: 15.1, 15.2 FOLLOWING: 17 16.1 Are Units with a Discovered Error? 16.2 If yes, then Collate Meter Data Records into Transactions 16.3 Then Create Data Records for Discovered Error 16.4 Collate Data Records into Transactions and send to MO 16.5 If no, then do nothing 17 In all cases, check that the Transaction has been received, otherwise call Market Operator to resolve problem Within appropriate timescales Automatic Type 3 Channel Meter Data Provider PRECEDING: 5, 8, 10, 12, 14, 16 FOLLOWING: 18 18 If acknowledgement received, end. If not, resolve issue, potentially utilising AP7 As required Type 1 Channel Meter Data Provider PRECEDING: 17 FOLLOWING: Potentially AP7