MAINTENANCE FUNCTIONS Sample Clauses

MAINTENANCE FUNCTIONS. 36.1: A Public Safety Officer shall not be required to wash or clean departmental vehicles used in patrol, investigative or administrative functions. Public Safety Officers, however, will be required to wash fire trucks and life support vehicles. In addition, Public Safety Officers shall not be required to perform routine janitorial or custodial service, except in the police garage, security garage and Fire Hall. In addition, officers shall be responsible for the stove, cupboards and table tops in the kitchen. The City's custodial service shall clean the carpeting as required for health and safety purposes. 36.2: In cases of inclement weather or conditions which render the building unsafe, the Public Safety Officers may be required to clean or mop those areas where the public is permitted access and where hazards to the public may result without such cleaning. The City may make such arrangements as it deems satisfactory for the washing of patrol, investigative or administrative vehicles.
Sample 1Sample 2
AutoNDA by SimpleDocs
MAINTENANCE FUNCTIONS. (g) Day-to-day routine and emergency supervision, administrative liaison and related functions required in connection with the maintenance and repair of the Public Company Group Assets. The Seconded Employees performing these maintenance supervision, liaison and related functions shall possess the qualifications, experience and/or training consistent with the qualifications and experience which are typical for personnel maintaining such facilities and in accordance with the rules and regulations of Hess and any applicable Governmental Authority and Applicable Law. (h) Maintenance and repair of the Public Company Group Assets, and other obligations required by right-of-way agreements. The Seconded Employees performing this maintenance shall possess the qualifications, experience and/or training consistent with the qualifications and experience which are typical for personnel maintaining such facilities and in accordance with the rules and regulations of Hess and any applicable Governmental Authority and Applicable Law. (i) Provision of equipment inspection, surveillance, corrosion control and monitoring, and the resulting records and history. (j) Implementation of a preventative maintenance program, including static vessel, tank, rotating and electrical equipment maintenance and integrity, for the Public Company Group Assets, including, without limitation, periodic testing, adjustment, maintenance, repair and/or replacement of the Public Company Group Assets. (k) Preparation and retention of appropriate maintenance records and logs regarding the Public Company Group Assets. (l) Technical functions for purposes of trouble-shooting problems, improving, upgrading, repairing and meeting all regulatory or safety requirements for the Public Company Group Assets. (m) Planning, design and engineering functions related to the maintenance and repair of the Public Company Group Assets; selecting contractors and material suppliers for such activities. (n) Advise the General Partner of major plans or significant changes in the maintenance or repair of the Public Company Group Assets. (o) Such other maintenance, repair and related functions as the General Partner may request from time to time.
Sample 1
MAINTENANCE FUNCTIONS. The maintenance functions that are delegated to DISTRICT, at DISTRICT's sole expense, are as follows:
Sample 1
MAINTENANCE FUNCTIONS. The various operations and maintenance functions that are delegated to COUNTY, at COUNTY's expense, are as follows:
Sample 1

Related to MAINTENANCE FUNCTIONS

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.

  • Maintenance Programme (i) The Contractor shall prepare a monthly maintenance programme (the “Maintenance Programme”) in consultation with the Authority’s Engineer and submit the same to the Authority’s Engineer not later than 10 (ten) days prior to the commencement of the month in which the Maintenance is to be carried out. For this purpose a joint monthly inspection by the Contractor and the Authority’s Engineer shall be undertaken. The Maintenance Programme shall contain the following: (a) The condition of the road in the format prescribed by the Authority’s Engineer; (b) the proposed maintenance Works; and (c) deployment of resources for maintenance Works.

  • Maintenance Services Subject to Client’s timely payment of the applicable maintenance fees, Accenture will make available the following maintenance services (“Maintenance Services”):

  • Nondiscretionary Functions The Custodian shall attend to all nondiscretionary details in connection with the sale, exchange, substitution, purchase, transfer or other dealings with securities or other assets of each Portfolio held by the Custodian, except as otherwise directed from time to time pursuant to Proper Instructions.

  • MAINTENANCE SERVICE Free maintenance services including spares shall be provided by the vendor during the period of warranty. User, at its discretion may ask the vendor to provide maintenance services after warranty period, i.e. Annual maintenance and repairs of the system at the rates indicated by bidder in its proposal and on being asked so, the vendor shall provide the same. The cost of annual maintenance and repairs cost (after warranty period), which will include cost of spares replaced, shall be paid in equal quarterly installments at the end of each quarter.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!