MANAGERIAL FUNCTIONS Sample Clauses

MANAGERIAL FUNCTIONS. 4.01 The Union recognizes and acknowledges that the management of the Company and direction of the working forces are fixed exclusively in the Company and without restricting the generality of the foregoing, the Union acknowledges that it is the exclusive function of the Company to:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
MANAGERIAL FUNCTIONS. 4.01 The Union recognizes and acknowledges that the management of the Company and direction of the working forces are fixed exclusively in the Company and without restricting the generality of the foregoing, the Union acknowledges that it is the exclusive function of the Company to: a) Maintain order, discipline and efficiency; b) Hire, retire, assign direct, promote, demote, classify, transfer, layoff, recall and, for just cause, to suspend, discharge or otherwise discipline employees subject to the right of the employees to grieve, to the extent and manner provided herein if the provisions of this Agreement are violated in the exercises of these rights; c) Determine the nature and kind of business conducted by the Company, the methods and techniques of work, the schedules of work, number of personnel to be employed, to make studies of and to institute changes in the jobs and job assignments, the extension, limitation, curtailment or cessation of operations and to determine all other functions and prerogatives here before invested in and exercised by the Company which shall remain solely with the Company; • The Company will allow all bases to propose schedules. The Union and Management will engage in meaningful discussions in response to any proposed schedule. d) Make and enforce and alter from time to time reasonable rules and regulations to be observed by the employees; e) Have the sole and exclusive jurisdiction over all operations, buildings, facilities and equipment.
Sample 1

Related to MANAGERIAL FUNCTIONS

  • MANAGEMENT FUNCTIONS 6.01 The Union acknowledges that it is the exclusive function of the Employer to:

  • Primary Function The primary function of the Program Manager is to provide strategic guidance and direction to the Project Team and to manage the Project on behalf of the Owner. Program Manager agrees that the services provided by the Program Manager are intended to coordinate and complement the activities of the Project Team, but not to diminish, alter or substitute for any of the services, authority, obligations or responsibilities being provided by the Design Professional and CM/GC under their respective contracts. Nothing herein shall be deemed to impose upon the Program Manager any responsibilities to provide any services constituting the practice of architecture, engineering, or any related design profession, or to provide any services constituting construction or means and methods of construction. The Program Manager should seek to exercise its authority through sound principles of leadership and persuasion to achieve effective coordination of the design and construction of the Project. The Program Manager should use its authority to direct the activities of the Design Professional and CM/GC within the requirements of their respective contracts; or in unusual or ambiguous situations, after consultation with the Owner and under the specific direction of the Owner.

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

  • 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: Field # Field Name Description 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

  • Commercially Useful Function a Small Local Business Enterprise or Emerging Local Business Enterprise (SLBE/ELBE) performs a commercially useful function when it is responsible for execution of the work and is carrying out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the SLBE/ELBE shall also be responsible, with respect to materials and supplies used on the contract, for negotiating price, determining quantity and quality, ordering the material, and installing (where applicable) and paying for the material itself. To determine whether an SLBE/XXXX is performing a commercially useful function, an evaluation will be performed of the amount of work subcontracted, normal industry practices, whether the amount the SLBE/ELBE firm is to be paid under the contract is commensurate with the work it is actually performing and the SLBE/ELBE credit claimed for its performance of the work, and other relevant factors. Specifically, a SLBE/ELBE does not perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of meaningful and useful SLBE/ELBE participation, when in similar transactions in which SLBE-ELBE firms do not participate, there is no such role performed. Disadvantaged Business Enterprise (DBE): a certified business that is (1) at least fifty-one (51%) owned by socially and economically Disadvantaged Individuals, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more socially and economically Disadvantaged Individuals; and (2) whose daily business operations are managed and directed by one or more socially and economically disadvantaged owners. Disadvantaged Individuals include Black Americans, Hispanic Americans, Asian Americans, and other minorities, or individual found to be disadvantaged by the Small Business Administration pursuant to Section 8 of the Small Business Reauthorization Act. Disabled Veteran Business Enterprise (DVBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more disabled veterans; and (2) business operations must be managed and controlled by one or more disabled veterans. Disabled Veteran is a veteran of the U.S. military, naval, or air service; the veteran must have a service-connected disability or at least 10% or more; and the veteran must reside in California. The firm shall be certified by the State of California’s Department of General Services, Office of Small and Minority Business. Emerging Business Enterprise (EBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and which meets all other criteria set forth in the regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for EBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. Emerging Local Business Enterprise (ELBE): a Local Business Enterprise that is also an Emerging Business Enterprise. Local Business Enterprise (LBE): a firm having a Principal Place of Business and a Significant Employment Presence in San Diego County, California, that has been in operation for 12 consecutive months and a valid business tax certificate. This definition is subsumed within the definition of Small Local Business Enterprise. Minority Business Enterprise (MBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more minority individuals, or, in the case of a publicly owned business at least fifty- one percent (51%) of the stock is owned by one or more minority individuals; and (2) whose daily business operations are managed and directed by one or more minorities owners. Minorities include the groups with the following ethnic origins: African, Asian Pacific, Asian Subcontinent, Hispanic, Native Alaskan, Native American, and Native Hawaiian. Other Business Enterprise (OBE): any business which does not otherwise qualify as Minority, Woman, Disadvantaged or Disabled Veteran Business Enterprise. Principal Place of Business: a location wherein a firm maintains a physical office and through which it obtains no less than fifty percent (50%) of its overall customers or sales dollars. Significant Employee Presence: no less than twenty-five percent (25%) of a business’s total number of employees are domiciled in San Diego County. Small Business Enterprise (SBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and that meets all other criteria set forth in regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for SBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. A business certified as a DVBE by the State of California, and that has provided proof of such certification to the City Manager, shall be deemed to be an SBE. Small Local Business Enterprise (SLBE): a Local Business Enterprise that is also a Small Business Enterprise. Women Business Enterprise (WBE): a certified business that is (1) at least fifty-one percent (51 %) owned by a woman or women, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more women; and (2) whose daily business operations are managed and directed by one or more women owners.

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

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

  • Personnel Provide, without remuneration from or other cost to the Trust, the services of individuals competent to perform the administrative functions which are not performed by employees or other agents engaged by the Trust or by the Adviser acting in some other capacity pursuant to a separate agreement or arrangement with the Trust.

  • INDEPENDENT CONTRACTOR; NO AGENCY Nothing in this Agreement will in any way be construed to render Influencer to be or to be construed as an agent, employee or representative of Brand. Influencer is and will perform the Services hereunder as an independent contractor. Influencer acknowledges and agrees that Influencer will not be eligible for any employee benefits (nor do they desire any of them) and expressly waives any entitlement to such benefits. Influencer further agrees to indemnify Brand and hold it harmless to the extent of any obligation imposed on Brand resulting from Influencer’s being determined not to be an independent contractor.

  • Regulatory Activities Beginning on the Effective Date and to the extent UGNX remains the Lead Development Party with respect to a particular territory, subject to and in accordance with the terms and conditions of this Agreement and the requirements of Applicable Laws, UGNX, shall: (a) use Commercially Reasonable Efforts to file (or have filed) all Regulatory Filings with respect to the Licensed Products in the Field in order to obtain Marketing Approvals in each country in the Territory and the European Territory (or to obtain the European Centralized Approval in the European Core Territory) and in order to obtain Pricing and/or Reimbursement Approvals in the Profit Share Territory; (b) respond in a timely fashion to requests for data and information from Regulatory Authorities with respect to the Licensed Products in the Field in the Territory and the European Territory; and (c) meet with officials of the Regulatory Authorities at such times as may be requested by such Regulatory Authorities with respect to the Core Development Activities (“Regulatory Activities”), provided that KHK will have primary responsibility for obtaining, and UGNX shall provide all assistance reasonably requested by KHK, in relation to Pricing and/or Reimbursement Approvals for the Licensed Products in the Field in the European Territory. For the avoidance of doubt, UGNX will be responsible for obtaining, and KHK will provide all assistance reasonably requested by UGNX, in relation to Pricing and/or Reimbursement Approvals, if any, for the Licensed Products in the Field in the Profit Share Territory as part of the UGNX Core Development Activities, it being understood that the costs incurred by UGNX in connection with such activities will be shared equally (50/50). All such Regulatory Activities will be conducted in a manner consistent with the Core Development Plan and coordinated by the JSC in accordance with Article 3. Without limiting the applicability of the foregoing and the remainder of this Article 5, UGNX shall interface with the applicable Regulatory Authority(ies) and, through the JDC, shall keep KHK reasonably informed of all material events and developments occurring in the course of the Regulatory Activities, including scheduled UGNX regulatory strategy discussions and meetings with Regulatory Authorities in the Territory and the European Territory relating to the Licensed Products in the Field.

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