INHERENTLY GOVERNMENT FUNCTIONS Sample Clauses

INHERENTLY GOVERNMENT FUNCTIONS. In its performance of a contract or task order, the Contractor must not perform any inherently governmental functions, as identified in the Office of Federal Procurement Policy Letter 11-01. These functions are so intimately related to the public interest as to require performance by Government employees. The term includes functions that require either the exercise of discretion in applying Government authority or the making of value judgments in making decisions for the Government. This would include, among other things, binding the Government to take or not to take some action by contract, policy, regulation, authorization, order, or otherwise, and exerting ultimate control over the acquisition, use, or disposition of the property of the United States, including the collection, control, or disbursement of appropriations and other federal funds.
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
INHERENTLY GOVERNMENT FUNCTIONS. As a matter of policy, an "inherently governmental function" is a function that is so intimately related to the public interest as to mandate performance by Government employees. These functions include those activities that require either the exercise of discretion in applying Government authority or the making of value judgments in making decisions for the Government. Governmental functions normally fall into two categories: (1) the act of governing, i.e., the discretionary exercise of Government authority, and (2) monetary transactions and entitlements. Contractor personnel shall not perform inherently governmental functions.
Sample 1Sample 2
INHERENTLY GOVERNMENT FUNCTIONS. Office of Procurement Policy Letter 92-1 (as published in the Federal Register, Volume 57, No. 190, page 45096, dated September 30, 1992), entitled Inherently Government Functions.
Sample 1Sample 2

Related to INHERENTLY GOVERNMENT FUNCTIONS

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

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

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

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

  • Controlled Government Data The Disclosing Party's Controlled Government Data, if any, will be identified in a separate technical document.

  • Government Standards The Contractor shall ensure that all items and services proposed conform to all local, State and Federal law concerning safety (OSHA and NOSHA) and environmental control (EPA and Bureau County Pollution Regulations) and any other enacted ordinance, code, law or regulation. The Contractor shall be responsible for all costs incurred for compliance with any such possible ordinance, code, law or regulation. No time extensions shall be granted or financial consideration given to the Contractor for time or monies lost due to violations of any such ordinance, code, law or regulations that may occur.

  • Government Procurement 1. Articles II, XVI and XVII shall not apply to laws, regulations or requirements governing the procurement by governmental agencies of services purchased for governmental purposes and not with a view to commercial resale or with a view to use in the supply of services for commercial sale. 2. There shall be multilateral negotiations on government procurement in services under this Agreement within two years from the date of entry into force of the WTO Agreement.

  • 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

  • GOVERNMENT DATA PRACTICES Supplier and Sourcewell must comply with the Minnesota Government Data Practices Act, Minnesota Statutes Chapter 13, as it applies to all data provided by or provided to Sourcewell under this Contract and as it applies to all data created, collected, received, maintained, or disseminated by the Supplier under this Contract.

  • Government Regulations Notwithstanding anything contained herein to the contrary, the Company’s obligation hereunder to issue or deliver certificates evidencing shares of Common Stock shall be subject to the terms of all applicable laws, rules and regulations and to such approvals by any governmental agencies or national securities exchanges as may be required.

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