Operations Data Clause Samples

The Operations Data clause defines how operational information generated or used during the performance of a contract is managed, accessed, and shared between the parties. Typically, this clause specifies what constitutes operations data, who owns or has rights to use it, and any restrictions or obligations regarding its handling, such as confidentiality or permitted uses. Its core practical function is to ensure clarity and prevent disputes over the control, use, and disclosure of valuable operational data, thereby protecting the interests of both parties and supporting efficient contract administration.
Operations Data. Business will provide data to CareerWise from time to time upon CareerWise’s reasonable request to allow CareerWise to evaluate the success of the Program and to place apprentices for employment if such apprentices are not hired by Business following their apprenticeship.
Operations Data. The Recipient will provide public access to the Project’s Operations Data. Data should be downloadable in csv format (or as otherwise agreed) and include 5-minute interval data including but not limited to: (a) State of charge (b) Active power consumption and provision distinguished for energy market and FCAS modes of operation (c) Reactive power consumption and provision (d) Electricity losses on site (e) Electricity exported to the grid (f) Power outages – unforeseen and planned (g) Applicable loss factors (generator and load) (h) Turbine efficiency (i) Storage power capacity and duration Advancing Renewables Program Funding Agreement | Vast Solar, Port Augusta Concentrated Solar Power Project 2022/ARP026 70 (j) Site conditions such as - incident solar irradiation, temperature, humidity, and wind speed (k) Impact of site conditions such as - high temperature or high humidity on the plant’s output and degradation. (l) Maintenance issues (downtime - scheduled and unscheduled etc.) (m) Curtailment events (voluntary and involuntary) Advancing Renewables Program Funding Agreement | Vast Solar, Port Augusta Concentrated Solar Power Project 2022/ARP026 71
Operations Data. ITA will host the operation of the Licensed Software and will provide and manage data required for the operation of the Licensed Software. The provision of such services will be governed by the SLA. Notwithstanding the foregoing, Galileo may at any time assume responsibility for hosting the operation of the Licensed Software, pursuant to the provisions of Section 7.3(b) of the SLA.
Operations Data. HTA shall establish, maintain and submit to COUNTY a record for each bus transit system route covered by this Agreement, which contains all of the information specified below. HTA shall submit to COUNTY the following information in a six (6) month report by March 31st and annual report by September 30th for each year of this Agreement that also includes a statement of revenue and expenses (actual vs. budgeted), balance sheet, analysis of change in retained earnings, statement of sources and application of funds: 1. Fare revenue report for each route (to be tabulated on a daily basis). 2. Total ridership by route, day, trip, number and fare category, including transfers. 3. Vehicle revenue service hours by route, day and vehicle. 4. Vehicle revenue service miles by route, day and vehicle. 5. Service breaks summary of breakdowns, road calls, missed trips and delays over thirty (30) minutes by trip number. 6. Complaints, compliments and service requests refused. 7. Vehicle and passenger accidents. 8. Vault count summary by route, day and vault number. 9. Other data which is reasonably necessary for COUNTY to evaluate service efficiency and effectiveness of COUNTY’s bus transit system.
Operations Data. CONTRACTOR shall establish, maintain and submit to COUNTY a record which contains all of the information specified below for each route covered by this Agreement. CONTRACTOR shall submit the following information to COUNTY in biannual operation reports, which include a statement of revenue and expenses, balance sheets, analysis of changes in retained earnings, a statement of sources and applications for additional funds, no later than March 31st and September 15th of each year in which this Agreement is in effect: 1. Fare revenue tabulated on a daily basis for each route covered by this Agreement. 2. Total ridership by route, day, trip number and fare category, including transfers. 3. Vehicle revenue service hours by route, day and vehicle. 4. Vehicle revenue service miles by route, day and vehicle. 5. Service break summary of breakdowns, road calls, missed trips and delays over fifteen (15) minutes by trip number. 6. Complaints, compliments and service requests refused. 7. Vehicle and passenger accidents. 8. Vehicle condition summary which includes all of the following: a. Mileage sorted by month, year-to-date and total. b. Fuel and oil consumption by miles per unit. c. Oil analysis for all vehicles upon which such an analysis is due. d. Accidents and road calls including a description of each malfunction. e. Preventive maintenance services and inspections performed. f. Major component rebuilding and other vehicle repairs made. 9. Driver list, employee training and turnover summary. 10. General summary of any and all operational problems, evaluations and solutions. 11. Other data which is reasonably necessary for COUNTY to evaluate the effectiveness of the transportation services provided pursuant to the terms and conditions of this Agreement.
Operations Data. SkiKrumb may collect technical logs, analytics or other data and learnings related to Company’s use of the SkiKrumb Products and Services (“Operations Data”) and use it to operate, improve and support the SkiKrumb Products and Services and for other lawful business purposes, including benchmarking and reports. SkiKrumb will not disclose Operations Data externally without Company’s prior written consent unless it is: (i) de-identified so that it does not identify Company or any individual; and (ii) aggregated with data across other customers.

Related to Operations Data

  • Project Information describing each Eligible Project that started, ended, or was ongoing in the reporting year.

  • Operations Fire An “Operations Fire” is a fire caused by Purchaser’s Operations other than a Neg- ligent Fire.

  • Billing Information 6.1 NLT and the RL shall provide each other with information within their possession that is necessary to allow them to provide accurate and timely billing to each other and to any other relevant third parties.