Fuel Use Monitoring Sample Clauses

Fuel Use Monitoring. The permittee shall implement the requirements of the District-approved Fuel Use Monitoring Plan (FUMP). The operator shall submit a FUMP for District review and approval within 45 days of the final issuance date of this permit. The FUMP shall include a description of the fuel monitoring system at each lease, meter specifications, example logs, and calculation sheets. The plan may be modified only upon written approval by the District and shall be maintained on-site and be made available to District personnel upon request.
AutoNDA by SimpleDocs

Related to Fuel Use Monitoring

  • Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.

  • System Monitoring to ensure safe and continuous operation, the Customer must monitor key services and resource use as recommended by Deswik, and provide Deswik with details of monitoring and any relevant alerts as needed. Services to be monitors include, without limitation, disk space, CPU usage, memory usage, database connectivity, and network utilization.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Supply Chain Monitoring A copy of the supply chain monitoring process, which should include details of the process for monitoring the financial viability of the supply chain (including timing), together with any known risks to supply chain stability and material changes to the supply chain. This should include extracts from Board level meetings, risk registers etc where any of the above items have been discussed. Annex 1 1 Information from Contractors who are not required to submit form AR01 to Companies House

  • Access, Use, Monitoring and Inspection Site shall provide original or copies (as the case may be) of all Study Data to Quintiles and Sponsor for Sponsor’s use. Site shall afford Sponsor and Quintiles and their representatives and designees reasonable access to Site’s facilities and to Medical Records and Study Data so as to permit Sponsor and Quintiles and their representatives and designees to monitor the Study. 1.3.3.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

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

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