Common use of Scheduling Protocols Clause in Contracts

Scheduling Protocols. The Parties agree that each Party will leverage technology, where feasible, to perform electronic approvals of schedules and to perform electronic checkouts. The Parties agree to follow the following scheduling protocols: Each Party, acting as the scheduling agent for their respective BAs, will conduct all checkouts with their first tier BAs or the scheduling agent acting on behalf of those first-tier BAs. A first tier BA is any BA that is directly connected to any Party’s members’ BA. The Parties will require all schedules between the Parties, other than reserve sharing or other emergency events and loss payback schedules, to be tagged via 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 to facilitate checkout between the Parties. When there is a scheduling conflict, the Parties will work in unison to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will make the correction in real-time and not wait until the quarter hour. If the schedule has already started and one Party identifies an error, then the Parties will make the correction at the earliest quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will stand for both Parties. For BAs or associated scheduling agents that do not use the respective Parties’ electronic scheduling interfaces, the Parties will contact those entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value to ensure accuracy. The Parties will perform the following types of checkouts: (a) Pre-schedule (day-ahead) daily between 1800 and 2200 hours(Eastern Prevailing Time); Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes. (b) Hourly Before the Fact (Real-Time); Checkout for the next hours shall be net scheduled. Import and export totals may also be verified in addition to NSI if it is deemed necessary by either Party. The Parties may checkout individual schedules if deemed necessary by either Party. Checkout for the top of the next hour is performed during the last half of the current hour. (c) Daily after the fact checkout shall occur no later than ten (10) business days after the fact (via email or mutually agreed upon method). (d) Monthly after the fact checkout shall occur no later than one (1) month after the fact (via phone or mutually agreed upon method). The Parties will require that each of these checkouts be performed with first tier BAs. If a checkout discrepancy is discovered, the Parties will use the NERC tag to find where the discrepancy exists. The Parties will require any entity that conducts business within its RC Area to checkout with the Parties using NERC tag numbers; special naming convention used by that entity or other naming conventions given to schedules by other entities will not be permitted.

Scheduling Protocols. The Parties agree that each Party will leverage technology, where feasible, to perform electronic approvals of schedules and to perform electronic checkouts. The Parties agree to follow the following scheduling protocols: : Section 10.1.1.1 Each Party, acting as the scheduling agent for their respective BAs, will conduct all checkouts with their first tier BAs or the scheduling agent acting on behalf of those first-tier BAs. A first tier BA is any BA that is directly connected to any Party’s members’ BA. . Section 10.1.1.2 The Parties will require all schedules between the Parties, other than reserve sharing or other emergency events and loss payback schedules, to be tagged via 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 to facilitate checkout between the Parties. . Section 10.1.1.3 When there is a scheduling conflict, the Parties will work in unison to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will make the correction in real-time and not wait until the quarter hour. If the schedule has already started and one Party identifies an error, then the Parties will make the correction at the earliest quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will stand for both Parties. . Section 10.1.1.4 For BAs or associated scheduling agents that do not use the respective Parties’ electronic scheduling interfaces, the Parties will contact those entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value to ensure accuracy. . Section 10.1.1.5 The Parties will perform the following types of checkouts: (a) Pre-schedule (day-ahead) daily between 1800 and 2200 hours(Eastern Prevailing Time); • Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes. (b) Hourly Before the Fact (Real-Time); • Checkout for the next hours shall be net scheduled. Import and export totals may also be verified in addition to NSI if it is deemed necessary by either Party. The Parties may checkout individual schedules if deemed necessary by either Party. • Checkout for the top of the next hour is performed during the last half of the current hour. (c) Daily after the fact checkout shall occur no later than ten (10) business days after the fact (via email or mutually agreed upon method). (d) Monthly after the fact checkout shall occur no later than one (1) month after the fact (via phone or mutually agreed upon method). . Section 10.1.1.6 The Parties will require that each of these checkouts be performed with first tier BAs. If a checkout discrepancy is discovered, the Parties will use the NERC tag to find where the discrepancy exists. The Parties will require any entity that conducts business within its RC Area to checkout with the Parties using NERC tag numbers; special naming convention used by that entity or other naming conventions given to schedules by other entities will not be permitted.

Scheduling Protocols. The Parties agree that each Each Party will shall leverage technology, where feasible, technology to perform electronic approvals of schedules schedules, and to perform electronic checkouts. The Parties agree to shall follow the following scheduling protocols: : 9.1.1.1 Each Party, acting as the scheduling agent for their its respective BAs, will shall conduct all checkouts with their first tier BAs or the scheduling agent acting on behalf of those first-tier BAs. A first first-tier BA is any BA that is directly connected to any Party’s members’ BA. BA or any BA operated by an independent transmission company. 9.1.1.2 The Parties will shall require all schedules between the Parties, other than reserve sharing or other emergency events and loss payback schedules, to be tagged via the in accordance with applicable NERC tagging standardstandards and NAESB Business Practices. For reserve sharing and other emergency schedules that are not tagged, the Parties will shall enter manual schedules after the fact into their respective scheduling systems to facilitate checkout between the Parties. . 9.1.1.3 When there is a scheduling conflict, the Parties will shall work in unison together to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will shall make the correction in realReal-time and not wait until the quarter hourtime. If the schedule has already started and one Party identifies an error, then the Parties will shall make the correction at the earliest possible quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both shall adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will shall stand for both Parties. . 9.1.1.4 For BAs or associated scheduling agents entities that do not use the respective Parties’ electronic scheduling interfaces, the Parties will shall contact those the non-member first-tier entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value three-part communication shall be used to ensure accuracy. accuracy of NSI values. 9.1.1.5 The Parties will shall perform the following types of checkouts: (a) Pre-schedule (day-ahead) ), daily between 1800 1600 and 2200 hours(Eastern Prevailing Time); Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes2000 (eastern prevailing time) hours. (b) Hourly Before the Before-the-Fact (Real-Time); time): (i) Checkout for the next hours shall be net scheduled. Import and export totals may also be verified in addition to NSI if it is deemed necessary by either a Party. The Parties may checkout individual schedules schedules, if deemed necessary by either Party. Checkout for the top of the next hour Parties; (ii) Hourly checkout is performed during starting at the last half of hour and ending at the current ramp hour; (iii) Intra-hour checkout/schedule confirmation shall occur as required due to intra-hour scheduled changes. (c) Daily after the after-the-fact checkout shall occur no later than ten (10) business days after the fact (via email or a mutually agreed upon method). (d) Monthly after the after-the-fact checkout shall occur no later than one (1) month after the fact (via phone or a mutually agreed upon method). . 9.1.1.6 The Parties will shall require that each of these checkouts checkout be performed with first tier BAs. If a checkout discrepancy is discovered, the Parties will shall use the NERC tag to find determine where the discrepancy exists. The Parties will shall require any entity that conducts business within its RC Area to checkout with the Parties applicable Party using NERC tag numbers; . Any special naming convention used by that entity or other naming conventions given to schedules by other entities will shall not be permitted.

Scheduling Protocols. The Parties agree that each Party will leverage technology, where feasible, to perform electronic approvals of schedules and to perform electronic checkouts. The Parties agree to follow the following scheduling protocols: : Section 10.1.1.1 Each Party, acting as the scheduling agent for their respective BAs, will conduct all checkouts with their first tier BAs or the scheduling agent acting on behalf of those first-tier BAs. A first tier BA is any BA that is directly connected to any Party’s members’ BA. Party‟s Section 10.1.1.2 The Parties will require all schedules between the Parties, other than reserve sharing or other emergency events and loss payback schedules, to be tagged via 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 to facilitate checkout between the Parties. . Section 10.1.1.3 When there is a scheduling conflict, the Parties will work in unison to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will make the correction in real-time and not wait until the quarter hour. If the schedule has already started and one Party identifies an error, then the Parties will make the correction at the earliest quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will stand for both Parties. . Section 10.1.1.4 For BAs or associated scheduling agents that do not use the respective Parties’ Parties‟ electronic scheduling interfaces, the Parties will contact those entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value to ensure accuracy. . Section 10.1.1.5 The Parties will perform the following types of checkouts: (a) Pre-schedule (day-ahead) daily between 1800 and 2200 hours(Eastern Prevailing Time); Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes. (b) Hourly Before the Fact (Real-Time); Checkout for the next hours shall be net scheduled. Import and export totals may also be verified in addition to NSI if it is deemed necessary by either Party. The Parties may checkout individual schedules if deemed necessary by either Party. Checkout for the top of the next hour is performed during the last half of the current hour. (c) Daily after the fact checkout shall occur no later than ten (10) business days after the fact (via email or mutually agreed upon method). (d) Monthly after the fact checkout shall occur no later than one (1) month after the fact (via phone or mutually agreed upon method). . Section 10.1.1.6 The Parties will require that each of these checkouts be performed with first tier BAs. If a checkout discrepancy is discovered, the Parties will use the NERC tag to find where the discrepancy exists. The Parties will require any entity that conducts business within its RC Area to checkout with the Parties using NERC tag numbers; special naming convention used by that entity or other naming conventions given to schedules by other entities will not be permitted.

Scheduling Protocols. The Parties agree that each Party will leverage technology, where feasible, to perform electronic approvals of schedules and to perform electronic checkouts, in lieu of telephone calls. The Parties agree to follow the following scheduling protocols: : Section 10.1.1.1 Each Party, acting as the scheduling agent for their respective BAsControl Areas, will conduct all checkouts with their first tier BAs Control Areas or the scheduling agent acting on behalf of those first-tier BAsControl Areas. A first tier BA Control Area is any BA Control Area that is directly connected to any Party’s members’ BA. Control Area. Section 10.1.1.2 The Parties will require all schedules between the Partiesschedules, other than reserve sharing or other emergency events and loss payback schedules, to be tagged via 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 to facilitate checkout between the Parties. . Section 10.1.1.3 When there is a scheduling conflict, the Parties will work in unison to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will make the correction in real-time and not wait until the quarter hour. If the schedule has already started and one Party identifies an error, then the Parties will make the correction at the earliest quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will stand for both Parties. . Section 10.1.1.4 For BAs Control Areas or associated scheduling agents that do not use the respective Parties’ electronic scheduling interfaces, the Parties will contact those entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value to ensure accuracy. . Section 10.1.1.5 The Parties will perform the following types of checkouts: (a) Pre-schedule (dayDay-aheadAhead) daily between 1800 and 2200 hours(Eastern Prevailing Time)hours; • Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes. (b) Hourly Before the Fact (Real-Time); Checkout for • Hourly before the next hours shall be net scheduled. Import fact checkout includes the verification of import and export totals may also be verified in addition to NSI if it is deemed necessary by either Partynet scheduled interchange (“NSI”) for control areas with that ability. The At a future time, the Parties may checkout individual schedules if deemed necessary by either Partyschedules. Checkout for the top of the next hour • Hourly checkout is performed during starting at the last half of hour and ending at the current ramp hour. (c) Daily after After the fact checkout shall occur no later than ten Fact (10Day End) business days after the fact (via email or mutually agreed upon method).daily starting at 0100 hours; and (d) Monthly after After the fact checkout shall occur no later than one Fact (1Monthly) daily on a month after to date basis (usually via email) starting on the fact first business day of the month and ending by the tenth (via phone or mutually agreed upon method). 10th) business day of that following month. Section 10.1.1.6 The Parties will require that each of these checkouts be performed with first tier BAsControl Areas. If a checkout discrepancy is discovered, the Parties will use the NERC tag to find where the discrepancy exists. The Parties will require any entity that conducts business within its RC Area region to checkout with the Parties using NERC tag numbers; special naming convention used by that entity or other naming conventions given to schedules by other entities will not be permitted.

Scheduling Protocols. The Parties agree that each Each Party will leverage technology, where feasible, technology to perform electronic approvals of schedules and to perform electronic checkouts, in lieu of telephone calls. The Parties agree to will follow the following scheduling protocols: : 10.1.1.1 Each Party, acting as the scheduling agent for their its respective BAsControl Areas, will conduct all checkouts with their first tier BAs or the scheduling agent acting on behalf of those first-tier BAsControl Areas. A first tier BA Control Area is any BA Control Area that is directly connected to any Party’s members’ BA. Control Area or any Control Area operated by an independent transmission company. 10.1.1.2 The Parties will require all schedules between the Partiesschedules, other than reserve sharing or other emergency events and loss payback schedulesevents, to be tagged via 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 to facilitate checkout between the Parties. . 10.1.1.3 When there is a scheduling conflict, the Parties will work in unison to modify the schedule as soon as practical. If there is a scheduling conflict that is identified before the schedule has started, then both Parties will make the correction in real-time and not wait until the quarter hour. If the schedule has already started and one Party identifies an error, then the Parties will make the correction at the earliest quarter hour increment. If a scheduling conflict cannot be resolved between the Parties (but the source and sink have agreed to a MW value), then the Parties will both adjust their numbers to that same MW value. If source and sink are unable to agree to a MW value, then the previously tagged value will stand for both Parties. . 10.1.1.4 For BAs or associated scheduling agents entities that do not use the respective Parties’ electronic scheduling interfaces, the Parties will contact those the non-member first-tier entities by telephone to perform checkouts. When performing checkouts by telephone, each entity will verbally repeat the numerical NSI value to ensure accuracy. . 10.1.1.5 The Parties will perform the following types of checkouts: (a) Pre-schedule (dayDay-aheadAhead) daily between 1800 1600 and 2200 hours(Eastern Prevailing Time); 2000 hours: (i) Intra-hour checkout/schedule confirmation will occur as required due to intra-hour scheduled changes. (b) Hourly Before the Fact (Real-Time); Checkout for ): (i) Hourly before the next hours shall be net scheduled. Import fact checkout includes the verification of import and export totals may also be verified in addition and is not limited to NSI if it is deemed necessary by either Partynet scheduled interchange for Control Areas with the ability to determine such net scheduled interchange. The At a future time, the Parties may checkout individual schedules if deemed necessary by either Party. Checkout for the top of the next hour schedules. (ii) Hourly checkout is performed during starting at the last half of hour and ending at the current ramp hour.. Issued by: Xxxxx X. Xxxxxxxxx, President and CEO, Midwest ISO Effective: March 1, 2004 Xxxxx Xxxxxx, Vice President, Government Policy, PJM Interconnection, L.L.C. Issued on: December 31, 2003 Midwest ISO Substitute Original Sheet No. 58 FERC Electric Tariff, Rate Schedule Xx. 0 Xxxxxxxxxxx Xxxxxxxx Xxxxx Xx. 00 XXX Interconnection, L.L.C. FERC Electric Tariff, Rate Schedule No. 38 (c) Daily after the fact checkout shall occur no later than ten (10) business days after After the fact (via email or mutually agreed upon method).day end) daily starting at 0100 hours; and (d) Monthly after the fact checkout shall occur no later than one (1) month after After the fact (monthly) daily on a month to date basis (usually via phone or mutually agreed upon method). email) starting on the first business day of the following month and ending by the tenth (10th) business day of that month. 10.1.1.6 The Parties will require that each of these checkouts be performed with first tier BAsControl Areas. If a checkout discrepancy is discovered, the Parties will use the NERC tag to find determine where the discrepancy exists. The Parties will require any entity that conducts business within its RC Area Region to checkout with the Parties applicable Party using NERC tag numbers; special naming convention used by that entity or other naming conventions given to schedules by other entities will not be permitted.