Identification of Flowgates Sample Clauses

The Identification of Flowgates clause defines the process and criteria for designating specific points or paths within an electrical transmission system where power flow is monitored or controlled. In practice, this clause outlines how flowgates are selected based on system studies, operational needs, or congestion management requirements, and may specify the roles of system operators or market participants in this identification process. Its core function is to ensure that all parties have a clear understanding of which transmission elements are critical for system reliability and market operations, thereby facilitating effective congestion management and risk allocation.
Identification of Flowgates. Each Party shall consider in its TFC and AFC determination process all Flowgates as required under the NERC Reliability Standards.that may initiate a TLR event. As determined in accordance with Section 3 of the Congestion Management Process, Flowgates that have a response factor equal to or greater than the distribution factor cut-off must be included in the evaluating Party’s model to the extent inclusion is practical.
View SourceView Similar (5)
Identification of Flowgates. Each Party shall consider in its TTC and ATC/AFC determination process all Flowgates that may initiate a TLR event. As determined in accordance with Section 3 of the CMP, Flowgates that have a response factor equal to or greater than the distribution factor cut-off must be included in the evaluating Party’s model to the extent inclusion is practical.
View SourceView Similar (2)
Identification of Flowgates. As determined in accordance with the Protocols (Attachments A and B), Flowgates that have a response factor equal to or greater than the distribution factor cut-off must be included in the evaluating Party’s model to the extent inclusion is practical. The Parties shall use the response factor cut-off that the owning/operating Party uses for its Flowgate in its AFC determination efforts.
View Source

Related to Identification of Flowgates

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Identification of Goods Identification of the goods shall not be deemed to have been made until both Buyer and Seller have agreed that the goods in question are to be appropriate to the performance of this Agreement.

  • Identification When performing work on District property, Contractor shall be in appropriate work attire (or uniform, if applicable) at all times. If Contractor does not have a specific uniform, then Contractor shall provide identification tags and/or any other mechanism the District in its sole discretion determines is required to easily identify Contractor. Contractor and its employees shall (i) display on their clothes the above-mentioned identifying information and (ii) carry photo identification and present it to any District personnel upon request. If Contractor cannot produce such identification or if the identification is unacceptable to District, District may provide at its sole discretion, District-produced identification tags to Contractor, costs to be borne by Contractor.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Type and Jurisdiction of Organization, Organizational and Identification Numbers The type of entity of such Grantor, its state of organization, the organizational number issued to it by its state of organization and its federal employer identification number are set forth on Exhibit A.