Common use of Dynamic Creation of Coordinated Flowgates Clause in Contracts

Dynamic Creation of Coordinated Flowgates. For temporary Flowgates developed “on the fly,” the IDC will utilize the current IDC methodology for determining NNL contribution until the Market-Based Operating Entity has begun reporting data for the new Flowgate. Interchange transactions into, out of, or across the Market-Based Operating Entity will continue to be E-tagged and available for curtailment in TLR 3, 4, or 5. Market-Based Operating Entities will study the Flowgate in a timely manner and begin reporting Flowgate data within no more than two business days (where the Flowgate has already been designated as an AFC Flowgate). This will ensure that the Market-Based Operating Entity has the time necessary to properly study the Flowgate using the four studies detailed earlier in this document and determine the Flowgate’s relationship with the Market-Based Operating Entity’s dispatch. For internal Flowgates, the Market-Based Operating Entity will redispatch during a TLR 3 to manage the constraint as necessary until it begins reporting the Firm and Non-Firm Market Flows; during a TLR 5, the IDC will request NNL relief in the same manner as today. Alternatively, for internal and external Flowgates, an Operating Entity may utilize an appropriate substitute Coordinated Flowgate that has similar Market Flows and tag impacts as the temporary Flowgate. In this case, an Operating Entity would have to realize relief through redispatch and TLR 3. An example of an appropriate substitute would be a Flowgate with a monitored element directly in series with a temporary Flowgate’s monitored element and with the same contingent element. If the Flowgate meets the necessary criteria, the Market- Based Operating Entity will begin to provide the necessary values to the IDC in the same manner as Market Flow values are provided to the IDC for all other Coordinated Flowgates. The necessary criteria for adding a Flowgate are defined in Appendix C. If in the event of a system emergency (TLR 3b or higher) and the situation requires a response faster than the process may provide, the Market-Based Operating Entities will coordinate respective actions to provide immediate relief until final review.

Dynamic Creation of Coordinated Flowgates. For temporary Flowgates developed “on the fly,” the IDC will utilize the current IDC methodology for determining NNL contribution until the Market-Based Operating Entity has begun reporting data for the new Flowgate. Interchange transactions into, out of, or across the Market-Based Operating Entity will continue to be E-tagged and available for curtailment in TLR 3, 4, or 5. Market-Based Operating Entities will study the Flowgate in a timely manner and begin reporting Flowgate data within no more than two business days (where the Flowgate has already been designated as an AFC Flowgate). This will ensure that the Market-Based Operating Entity has the time necessary to properly study the Flowgate using the four five studies detailed earlier in this document and determine the Flowgate’s relationship with the Market-Based Operating Entity’s dispatch. For internal Flowgates, the Market-Based Operating Entity will redispatch during a TLR 3 to manage the constraint as necessary until it begins reporting the Firm and Non-Firm Market Flows; during a TLR 5, the IDC will request NNL relief in the same manner as today. Alternatively, for internal and external Flowgates, an Operating Entity may utilize an appropriate substitute Coordinated Flowgate that has similar Market Flows and tag impacts as the temporary Flowgate. In this case, an Operating Entity would have to realize relief through redispatch and TLR 3. An example of an appropriate substitute would be a Flowgate with a monitored element directly in series with a temporary Flowgate’s monitored element and with the same contingent element. If the Flowgate meets the necessary criteria, the Market- Market-Based Operating Entity will begin to provide the necessary values to the IDC in the same manner as Market Flow values are provided to the IDC for all other Coordinated Flowgates. The necessary criteria for adding a Flowgate are defined in Appendix C. If in the event of a system emergency (TLR 3b or higher) and the situation requires a response faster than the process may provide, the Market-Based Operating Entities will coordinate respective actions to provide immediate relief until final review.

Dynamic Creation of Coordinated Flowgates. For temporary Flowgates developed “on the fly,” the IDC will utilize the current IDC methodology for determining NNL contribution until the Market-Based Operating Entity has begun reporting data for the new Flowgate. Interchange transactions into, out of, or across the Market-Based Operating Entity will continue to be E-tagged and available for curtailment in TLR 3, 4, or 5. Market-Market- Based Operating Entities will endeavor to study the Flowgate in a timely manner and begin reporting Flowgate data within no more than two business days (where the Flowgate has already been designated as an AFC Flowgate)days. This will ensure that the Market-Based Operating Entity has the time necessary to properly study the Flowgate using the four studies detailed earlier in this document above and determine the Flowgate’s relationship with the Market-Based Operating Entity’s dispatchdispatch (based on the studies above). For internal Flowgates, the Market-Market Based Operating Entity will redispatch during a TLR 3 to manage the constraint as necessary until it begins reporting the Firm 7-FN, 6-NN, and Non2-Firm Market FlowsNH components; during a TLR 5, the IDC will request NNL relief in the same pro-rata manner as today. Alternatively, for internal and external Flowgates, an either Operating Entity may utilize an appropriate substitute internal Coordinated Flowgate that has similar Market Flows internal and tag external impacts as the temporary Flowgate. In this case, an either Operating Entity would have to realize relief through redispatch and TLR 3. An example of an appropriate substitute would be a Flowgate with a monitored element directly in series with a temporary Flowgate’s monitored element and with the same contingent element. If the Flowgate meets the necessary criteria, the Market- Market-Based Operating Entity will begin to provide the necessary values to the IDC in the same manner as Market Flow values Flows are provided to the IDC for all other Coordinated Flowgates. The necessary criteria for adding a Flowgate are defined in Appendix C. If in the event of a system emergency (TLR 3b or higher) and the situation requires a response faster than the process may provide, the Market-Based Operating Entities will coordinate respective actions to provide immediate relief until final review. Note that the information requirements for Market-Based Operating Entities only apply to MISO at the point at which it begins to operate a security constrained, bid based economic dispatch bounded by a clearly defined market area. Until that time, MISO will only be performing reciprocal operations on these Flowgates. The present Day 1 functionality of MISO’s real-time Security Analysis programs allows for the creation and activation of new contingencies or Flowgates in real- time within a matter of minutes. Data set builds or uploads are not necessary to add a new contingency or Flowgate to these real-time monitoring and control applications. With the Flowgate now included in the real-time system, MISO can then redispatch effective internal generation to provide the required/requested relief exactly as will be done for all other Coordinated Flowgates.

Dynamic Creation of Coordinated Flowgates. For temporary Flowgates developed “on the fly,” the IDC will utilize calculate GTL relief obligation based on GPS or TSNT method and once market entities submit the current IDC methodology for determining NNL contribution until Firm Flow limits the Market-Based Operating Entity has begun reporting data for GTL relief obligation will be based on submitted firm flow limits on the new Flowgate. Interchange transactions into, out of, or across the Market-Based Operating Entity will continue to be E-E- tagged and available for curtailment in TLR 3, 4, or 5. Market-Based Operating Entities will study the Flowgate in a timely manner and begin reporting Flowgate data within no more than two business days (where the Flowgate has already been designated as an AFC Flowgate). This will ensure that the Market-Based Operating Entity has the time necessary to properly study the Flowgate using the four five studies detailed earlier in this document and determine the Flowgate’s relationship with the Market-Based Operating Entity’s dispatch. For internal Flowgates, the Market-Based Operating Entity will redispatch during a TLR 3 to manage the constraint as necessary until it begins reporting the Firm and Non-Firm Market FlowsLimits; during a TLR 5, the IDC will request NNL GTL relief obligation in the same manner as today. Alternatively, for internal and external Flowgates, an Operating Entity may utilize an appropriate substitute Coordinated Flowgate that has similar Market Flows and tag impacts as the temporary Flowgate. In this case, an Operating Entity would have to realize relief through redispatch and TLR 3. An example of an appropriate substitute would be a Flowgate with a monitored element directly in series with a temporary Flowgate’s monitored element and with the same contingent element. If the Flowgate meets the necessary criteria, the Market- Market-Based Operating Entity will begin to provide the necessary values to the IDC in the same manner as Market Flow values are provided to the IDC for all other Coordinated Flowgates. The necessary criteria for adding a Flowgate are defined in Appendix C. If in the event of a system emergency (TLR 3b or higher) and the situation requires a response faster than the process may provide, the Market-Based Operating Entities will coordinate respective actions to provide immediate relief until final review.