MAINTENANCE AND OPERATION SCHEDULE AND REQUIREMENTS Sample Clauses

MAINTENANCE AND OPERATION SCHEDULE AND REQUIREMENTS. 5.1 General Concessions Maintenance and Operation ▪ Kitchen: Thorough cleaning of the kitchen and cooking area daily that will consist of disinfecting surfaces and equipment. ▪ Litter: Remove throughout the day as necessary, and when requested by County, from all use areas and parking lots.
Sample 1
AutoNDA by SimpleDocs
MAINTENANCE AND OPERATION SCHEDULE AND REQUIREMENTS. 6.1. General Park Maintenance and Operation: Applicable to all park areas:
Sample 1
MAINTENANCE AND OPERATION SCHEDULE AND REQUIREMENTS. 6.1 General Park Maintenance and Operation. Applicable to all park areas:  Comfort Stations. Basic cleaning of the day use comfort stations twice daily at a frequency that is acceptable to City that will consist of disinfecting surfaces and toilet bowls and restocking of all needed paper products. City will provide the necessary supplies for the bathrooms. Contractor will clean comfort stations to a standard acceptable to City.  Picnic Areas by Reservation. Clean and prepare all day-use Picnic Areas according to reservations report or as needed upon request by City. Contractor may request assistance from City to clean and prepare Picnic Areas in order to meet reservation demand, subject to the availability of City resources to assist with preparations and cleanings. Post reservation signs per schedule provided by City.  Mowing and String Trimming. Mow and string trim all areas weekly or as needed to keep the grass less than 4” in height, or upon request by City.  Gate. Open and close gates on schedule requested by City.  Litter. Remove daily as necessary, and when requested by City, from all use areas and parking lots.
Sample 1

Related to MAINTENANCE AND OPERATION SCHEDULE AND REQUIREMENTS

  • Maintenance and Operation Member-Generator agrees to maintain their system and facilities in accordance with applicable manufacturer's recommended maintenance schedule and standard prudent engineering practices. Member-Generator covenants and agrees to operate their system, facilities and equipment so as to minimize the likelihood for a malfunction or other disturbance, damaging or otherwise affecting or impairing Cooperative’s electrical system. Member-Generator shall comply with all applicable laws, regulations, zoning, building codes, safety rules and other environmental regulations or restrictions applicable to the design, installation, operation and maintenance of the Member-Generator's System. Member-Generator must, at least once every year, conduct a test to confirm that Member-Generator’s System automatically ceases to energize the output (interconnection equipment output voltage goes to zero) within two (2) seconds of being disconnected from Cooperative’s electrical system. Disconnecting the Member-Generator’s System from Cooperative’s electrical system at the visible disconnect switch and measuring the time required for the unit to cease to energize the output shall satisfy this test. Member-Generator shall maintain a record of the results of these tests and, upon request by Cooperative, shall provide a copy of the test results to Cooperative. If Member-Generator is unable to provide a copy of the test results upon request, Cooperative shall notify Member- Generator by mail that Member-Generator has thirty (30) days from the date Member-Generator receives the request to provide Cooperative with the results of a test. If Member-Generator does not provide Cooperative with the test results within the thirty (30) day time period or if the test results provided to Cooperative show that Member-Generator’s net metering unit is not functioning correctly, Cooperative may immediately disconnect Member-Generator’s System from Cooperative’s electrical system. If Member-Generator’s equipment ever fails this test, Member-Generator shall immediately disconnect Member-Generator’s System from Cooperative's electrical system. Member-Generator’s System shall not be reconnected to Cooperative's electrical system by the Member-Generator until Member-Generator’s System is repaired and operating in a normal and safe manner. Cooperative shall have the right to have a representative present and informed when any such tests are conducted. Cooperative does not warrant the testing procedures or results by the presence of its representative. Member-Generator is responsible for protecting their equipment from transient high voltage spikes caused by lightning and/or transient low voltage conditions caused by faults or short circuits, and from any other causes or events. Therefore, Cooperative shall not be responsible for damage to Member-Generator’s equipment allegedly caused by transient high voltage spikes caused by lightning and/or transient low voltage conditions caused by faults or short circuits or other causes or events. Member-Generator agrees to notify Cooperative no less than thirty (30) days prior to modification of the components or design of the Member-Generator’s System that in any way may degrade or significantly alter the System’s output characteristics. Member-Generator acknowledges that any such modifications will require submission of a new Application and Agreement to Cooperative.

  • Developer Operating Requirements (a) Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time.

  • Management Requirements Procedures for managing equipment (including replacement equipment), whether acquired in whole or in part under a Federal award, until disposition takes place will, as a minimum, meet the following requirements:

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Use and Operation 3.1 Permitted Use ......................................................................................................

  • Maintenance Standards Unless otherwise authorized by the CRC Board, the General Manager shall prepare and submit to the CRC Board proposals (including the Program Maintenance plan submitted pursuant to Section 5(b)) for the performance of such Routine Maintenance and Program Maintenance as is reasonably necessary to keep and maintain the Shared Assets substantially in their condition as of the date of this Agreement. If the CRC Board fails either to approve or disapprove by majority vote any such proposal within 45 days after it was submitted to the CRC Board, the disagreement over the propriety or need for any of the Routine Maintenance or Program Maintenance included in such proposal may be submitted by either Operator for resolution by binding arbitration pursuant to Section 13.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

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