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 is used in the TRANSMISSION_ID in “ALL” 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 Identifier Business Frequency, Data Records Transaction Process including containing best Supported latest time of available data delivery Indicative Price PEG Ex-Post Each Calendar Price Maker Effecting Indicative Price Day, by 14:00 Generator Units Generation Setting & on the next Price Taker Metering Indicative Calendar Day Generator Units Settlement (D+1) Indicative Non NPEG Ex-Post Each Week Autonomous Price Effecting Indicative Day, by 14:00 Generator Unit Generation Settlement on the next Metering Week Day (D+1) Indicative CJF Ex-Post Each Week Net Inter Aggregated Indicative Day, by 14:00 Jurisdictional Jurisdiction Settlement on the next Flow Metering Week Day (D+1) 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 Identifier Business Frequency, Data Records Transaction Process including containing best Supported latest time of available data delivery All data required ALL Ex-Post Each Calendar Price Maker from Meter Data Indicative Day, by 14:00 Generator Units Provider Setting & on the next Price Taker Indicative Calendar Day Generator Units Settlement (D+1) Autonomous Generator Unit Net Inter Jurisdictional Flow
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
AP16.docx