Quantify and Provide Data for Market Flow Sample Clauses

Quantify and Provide Data for Market Flow. Every fifteen minutes, the Market-Based Operating Entity will be responsible for providing to Reliability Coordinators the following information: • Firm Market Flows for all Coordinated Flowgates in each direction • Non-Firm Market Flows for all Coordinated Flowgates in each direction The Firm Market Flow (Priority 7-FN) will be equivalent to the calculated Market Flow, up to the Firm Flow Limit. In real time, any Market Flow in excess of the Firm Flow Limit will be reported as Non-Firm Market Flow (Priority 6-NN) (note that under reciprocal operations, some of this Non-Firm Market Flow 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 on the various Coordinated Flowgates in each direction. When the Firm Flow Limit forecast is calculated to be greater than Market Flow for current hour or next hour, actual Firm Flow Limit (used in TLR5) will be set equal to Market Flow. Additionally, as frequently as once an hour, but no less frequently than once every three months, the Market-Based Operating Entity will submit to the Reliability Coordinator sets 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 Quantify and Provide Data for Market Flow

  • We provide Message Boards for the use of Our Website users The Message Boards may not be used to promote Websites or any commercial or business activity. We are not responsible for any of the opinions expressed in the Message Boards. By posting a message to the message board You agree to take full legal responsibility and liability for your comments, including for offensive or defamatory statements. Feedback: Feedback is provided for the purpose of facilitating trading by You on Our Website. Feedback provided on other parties must not contain offensive, defamatory, retaliatory or inappropriate language or content. We may remove any feedback that is considered to be offensive, defamatory, retaliatory or inappropriate. You may only give feedback that relates to a specific transaction. You must not post feedback on a transaction that does not relate to that specific transaction. You must not post feedback about Yourself or include any contact details or Personal Information in Your feedback.

  • 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.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.

  • Information and Services Required of the Owner § 3.1.1 The Owner shall provide information with reasonable promptness, regarding requirements for and limitations on the Project, including a written program which shall set forth the Owner’s objectives, constraints, and criteria, including schedule, space requirements and relationships, flexibility and expandability, special equipment, systems, sustainability and site requirements.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Customer Cooperation 3.2.1. Customer shall provide and make available all Customer personnel as may be further addressed in an applicable Order Form or that SAP reasonably requires in connection with performance of the Services.

  • Access Controls a. Authorized Access - DST shall have controls that are designed to maintain the logical separation such that access to systems hosting Fund Data and/or being used to provide services to Fund will uniquely identify each individual requiring access, grant access only to authorized personnel based on the principle of least privileges, and prevent unauthorized access to Fund Data.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

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