Providing Data for Reliability Analysis Sample Clauses

Providing Data for Reliability Analysis. Every fifteen minutes, the Market-Based Operating Entity will be responsible for providing to Reliability Coordinators the following information: • Firm Gen-to-Load Flows for all Coordinated Flowgates in each direction • Economic Dispatch Flows for all Coordinated Flowgates in each direction The Firm Gen-to-Load Flow (Priority 7-FN) will be equivalent to the calculated Market Flow, up to the Firm Gen-to-Load Limit. Any Market Flow in excess of the Firm Gen- to-Load Limit will be reported as Economic Dispatch (Priority 6-NN) (note that under reciprocal operations, some of this Economic Dispatch may be quantified as Priority 2- NH). This information will be provided for both current hour and next hour, and is used in order to communicate to Reliability Coordinators the amount of flows to be considered firm service on the various Coordinated Flowgates in each direction. When Firm Gen-to- Load Limit forecast is calculated to be greater than Market Flow for current hour or next hour, actual Firm Gen-to-Load Limit (used in TLR5) will be set equal to Market Flow. Additionally, every hour the Market-Based Operating Entity will submit to the Reliability Coordinators a set of data describing the marginal units and associated participation factors for generation within the market footprint. The level of detail of the data may vary, as different Operating Entities will have different unique situations to address.‌ However, this data will at a minimum be supplied for imports to and exports from the market area, and will contain as much information as is determined to be necessary to ensure system reliability. This data will be used by the Reliability Coordinators to determine the impacts of schedule curtailment requests when they result in a shift in the dispatch within the market area.
Sample 1
AutoNDA by SimpleDocs

Related to Providing Data for Reliability Analysis

  • Data Analysis In the meeting, the analysis that has led the College President to conclude that a reduction- in-force in the FSA at that College may be necessary will be shared. The analysis will include but is not limited to the following: ● Relationship of the FSA to the mission, vision, values, and strategic plan of the College and district ● External requirement for the services provided by the FSA such as accreditation or intergovernmental agreements ● Annual instructional load (as applicable) ● Percentage of annual instructional load taught by Residential Faculty (as applicable) ● Fall Full-Time Student Equivalent (FFTE) inclusive of dual enrollment ● Number of Residential Faculty teaching/working in the FSA ● Number of Residential Faculty whose primary FSA is the FSA being analyzed ● Revenue trends over five years for the FSA including but not limited to tuition and fees ● Expenditure trends over five years for the FSA including but not limited to personnel and capital ● Account balances for any fees accounts within the FSA ● Cost/benefit analysis of reducing all non-Residential Faculty plus one Residential Faculty within the FSA ● An explanation of the problem that reducing the number of faculty in the FSA would solve ● The list of potential Residential Faculty that are at risk of layoff as determined by the Vice Chancellor of Human Resources ● Other relevant information, as requested

  • Statistical Analysis 31 F-tests and t-tests will be used to analyze OV and Quality Acceptance data. The F-test is a 32 comparison of variances to determine if the OV and Quality Acceptance population variances 33 are equal. The t-test is a comparison of means to determine if the OV and Quality Acceptance 34 population means are equal. In addition to these two types of analyses, independent verification 35 and observation verification will also be used to validate the Quality Acceptance test results.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • DATA COLLECTION AND ANALYSIS The goal of this task is to collect operational data from the project, to analyze that data for economic and environmental impacts, and to include the data and analysis in the Final Report. Formulas will be provided for calculations. A Final Report data collection template will be provided by the Energy Commission. The Recipient shall: • Develop data collection test plan. • Troubleshoot any issues identified. • Collect data, information, and analysis and develop a Final Report which includes: o Total gross project costs. o Length of time from award of bus(es) to project completion. o Fuel usage before and after the project.

  • COMPENSATION ANALYSIS After the expiration of the second (2nd) Renewal Term of this Agreement, if any, a Compensation Analysis may be performed. At such time, based on the reported Total Gross Revenue, performance of the Concession, and/or Department’s existing rates for similarly- performing operations, Department may choose to increase the Concession Payment for the following Renewal Term(s), if any.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

Time is Money Join Law Insider Premium to draft better contracts faster.