Scheduling Checkout Protocols Sample Clauses
Scheduling Checkout Protocols. 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.
35.13.1.2 When there is a transaction scheduling conflict, the Parties will work to modify the schedule as soon as practical.
35.13.1.3 The Parties will perform the following types of checkouts. Checkouts will be consistent with 35.13.1.1 and 35.13.1.2.
(a) Day-ahead checkout shall be performed daily on the day before the transaction is to flow. Day-ahead checkout includes the verification of import and export totals and individual transaction schedules.
(b) Real-time checkout shall be performed hourly during the hour before the transaction is to flow. Real-time checkout includes the verification of import and export totals and individual transaction schedules.
(c) After-the-fact checkout of transactions shall be performed the next business day following the day of the transactions.
(d) After-the-fact reporting of hourly scheduled energy interchanged and hourly actual energy interchanged shall be updated by each Party each day and exchanged with the other Party. Each day, month to date data shall be exchanged. Parties shall resolve discrepancies within ten (10) business days of the end of each month.
Scheduling Checkout Protocols. Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.
Scheduling Checkout Protocols. Both Parties shall require all real-time energy market transaction schedules over Interconnections to be tagged in accord with the NERC tagging standard. For Simultaneous Activation of Reserves (“SAR”) and other emergency schedules that are not tagged, the Parties will enter manual schedules into their respective operating systems. When there is a real-time energy market transaction scheduling conflict, the Parties will work to modify the schedule as soon as practical. Consistent with the foregoing requirements, the Parties will perform the following types of checkouts:
Scheduling Checkout Protocols. Both Parties shall require all real-time energy market transaction schedules over Interconnections to be tagged in accord with the NERC tagging standard. For Simultaneous Activation of Reserves (“SAR”) and other emergency schedules that are not tagged, the Parties will enter manual schedules into their respective operating systems. When there is a real-time energy market transaction scheduling conflict, the Parties will work to modify the schedule as soon as practical. Consistent with the foregoing requirements, the Parties will perform the following types of checkouts:
(a) Day-ahead checkout shall be performed daily on the day before the transaction is to flow.
(b) Real-time checkout shall be performed during the period before the transaction is to flow.
(c) After-the-fact checkout of real-time transactions shall be performed the next business day following the day of the transactions;
(d) After-the-fact reporting of scheduled energy interchange and actual energy interchange shall be updated by each Party each day and exchanged with the other Party. Within ten (10) business days of the end of each month, the previous month’s data shall be reconciled.
Scheduling Checkout Protocols. 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.
35.13.1.2 When there is a transaction scheduling conflict, the Parties will work to modify the schedule as soon as practical.
35.13.1.3 The Parties will perform the following types of checkouts. Checkouts will be consistent with 35.13.1.1 and 35.13.1.2.
(a) Day-ahead checkout shall be performed daily on the day before the transaction is to flow. Day-ahead checkout includes the verification of import and export totals and individual transaction schedules.
Scheduling Checkout Protocols. 35.13.1.1 Both Parties shall require all transaction schedules to be tagged in accord with the NERC tagging standard. For reserve sharing and other emergency schedules that are not tagged, the Parties will enter manual schedules after the fact into their respective scheduling systems.
35.13.1.2 When there is a transaction scheduling conflict, the Parties will work to modify the schedule as soon as practical.
35.13.1.3 The Parties will perform the following types of checkouts. Checkouts will be consistent with 35.13.1.1 and 35.13.1.2.
(a) Day-ahead checkout shall be performed daily on the day before the transaction is to flow. Day-ahead checkout includes the verification of import and export totals and individual transaction schedules.
(b) Real-time checkout shall be performed hourly during the hour before the transaction is to flow. Real-time checkout includes the verification of import and export totals and individual transaction schedules.
(c) After-the-fact checkout of transactions shall be performed the next business day following the day of the transactions.
Scheduling Checkout Protocols. 12.1.1 35.12.1.1 12.1.2 35.12.1.2 ARTICLE THIRTEEN - TTC/ATC/AFC CALCULATIONS 35.13 TTC/ATC/AFC CALCULATIONS
Scheduling Checkout Protocols