Maintenance and Operation Categories Sample Clauses

The "Maintenance and Operation Categories" clause defines how various maintenance and operational responsibilities are organized and assigned within an agreement. It typically outlines specific categories or types of maintenance—such as routine, preventive, or emergency—and clarifies which party is responsible for each. For example, a lease might specify that the tenant handles day-to-day upkeep while the landlord manages structural repairs. This clause ensures clear allocation of duties, reducing disputes and confusion over who is responsible for different aspects of property or equipment maintenance.
Maintenance and Operation Categories. 7.1 The M&O expenses can be divided into the following three categories : 7.1.1 Category A. M&O expenses that are shared by the entire Collaboration (cf. Article 6.3.1 above). Error! Reference source not found. lists the headings under which Category A costs are categorised. 7.1.2 Category B. M&O expenses that are borne by part of the Collaboration, i.e. by single Institutes or groups of Institutes, and their Funding Agencies (cf. Article 6.3.2 above). The headings in this category are defined with reference to the distribution of responsibilities amongst the various Institutes for the construction of the Error! Reference source not found. Detector as given in Error! Reference source not found.. Error! Reference source not found. lists the headings under which Category B costs are categorised and the Institutes concerned. It is agreed that an Institute having responsibility under a Category B heading will contribute to providing the necessary financial, scientific and technical support, as well as replacement or spare parts, for normal operation of that equipment and for the routine maintenance needed to keep it in good working order. If problems arise that require major modifications, responsibility will lie with the Collaboration as a whole. The Collaboration will propose on a case-by-case basis the events to which this provision will apply. The proposal will be submitted for approval to the next RRB meeting, which will also be asked to approve the provision of the necessary resources.
View SourceView Similar (4)

Related to Maintenance and Operation Categories

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

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

  • Maintenance and Support Services If this Agreement is for IT goods or services, this section applies: Unless otherwise specified in this Agreement: The Contractor shall promptly provide the Court with all Upgrades, including without limitation: (i) all Upgrades generally made available by Contractor to its other customers; (ii) Upgrades as necessary so that the Work complies with the Specifications and Applicable Law (including changes in Applicable Law); (iii) Upgrades as necessary so that the Work operates under new versions or releases of the Court’s operating system or database platform; and (iv) all on-site services necessary for installation of Upgrades. Without limiting any other obligation of Contractor under this Agreement, Contractor represents and warrants that it will maintain services, equipment, software or any other part of the Work so that they operate in accordance with their Specifications and Documentation; and The Contractor shall respond to the Court within four (4) hours after the Court reports a Technical Support Incident (such hours all occurring during Standard M&S Hours) to Contractor. DELIVERY, ACCEPTANCE, AND PAYMENT Delivery. Contractor shall deliver to the Court the Deliverables in accordance with this Agreement, including the Statement of Work. Unless otherwise specified by this Agreement, Contractor will deliver all goods purchased by the Court “Free on Board Destination Freight Prepaid” to the Court at the address and location specified by the Court. Title to all goods purchased by the Court vests in the Court upon payment of the applicable purchase price. Contractor will bear the risk of loss for any Work being delivered until received by the Court at the proper location. All shipments by Contractor or its Subcontractors must include packing sheets identifying: this Agreement number, the Court’s purchase order number, item number, quantity and unit of measure, part number and description of the goods shipped, and appropriate evidence of inspection, if required. Goods for different Agreements shall be listed on separate packing sheets.

  • Application and Operation 5 PART 2 - DISPUTE RESOLUTION AND CONSULTATION 12

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.