Supervisory Functions Sample Clauses

Supervisory Functions. It is understood by the parties that employees in this bargaining unit are responsible for performing various supervisory functions, including implementation of established County policies and departmental procedures; as well as specific Department Head directives.
AutoNDA by SimpleDocs
Supervisory Functions. Provide the supervisory consoles the capability of Primary/Secondary Supervisor Hierarchy feature to allow supervisory personnel to priority-override the transmit function of other operators or users regardless of their current state. Other details of the administrative function will be defined in the Detailed Design Document.
Supervisory Functions. No supervisor shall perform bargaining unit work except for the purpose of instruction and demonstration, or if qualified members of the bargaining unit are not readily available, or if an emergency or critical problem exists. An emergency or critical problem shall be defined to mean that immediate performance of work is required (a) to preserve life or property, or (b) to protect against damage to material or process. The University will investigate all complaints of violations of this Section brought to its attention by the Union; if upon investigation the University determines that a supervisor has performed bargaining unit work in violation of this Section it will take appropriate action, including a cease and desist directive, to meet its commitment under this Section without requiring the Union to utilize the grievance and arbitration procedure. In the event that the University determines that a violation exists, but the action taken by the University does not, in the judgment of the Union, cause the violation to cease, or in the event the Union disagrees with the University’s determination that no violation exists, the matter may be grieved at the second step of the grievance procedure. If the matter is referred to arbitration, and the arbitrator decides in favor of the Union, the arbitrator shall have the authority to issue a cease and desist order and to require the University to pay all or a part of the Union’s share of the arbitrator’s costs.
Supervisory Functions. No supervisor shall perform bargaining unit work except and to the extent that such work is a part of his normal duties, or for the purpose of instruction and demonstration, or if qualified members of the bargaining unit are not readily available, or if an emergency or critical problem exists. An emergency or critical problem shall be defined to mean that immediate performance of work is required (a) to preserve life or property, or (b) to protect against damage to material or process. The University will investigate all complaints of violations of this Section brought to its attention by the Union; if upon investigation the University determines that a supervisor has performed bargaining unit work in violation of this Section it will take appropriate action, including a cease and desist directive, to meet its commitment under this Section without requiring the Union to utilize the grievance and arbitration procedure. In the event that the University determines that a violation exists, but the action taken by the University does not, in the judgment of the Union, cause the violation to cease, or in the event the Union disagrees with the University’s determination that no violation exists, the matter may be grieved at the second step of the grievance procedure. If the matter is referred to arbitration, and the arbitrator decides in favor of the Union, the arbitrator shall have the authority to issue a cease and desist order and to require the University to pay all or a part of the Union’s share of the arbitrator’s costs.
Supervisory Functions. All members of the bargaining unit are responsible for performing supervisory and technical functions under the direction of the Library Director and/or his/her designee. Such work involves leading and overseeing bargaining unit and non-bargaining unit employees and volunteers, performing highly specialized and technical senior staff work, exercising considerable independent judgment and initiative within the supervisor’s scope of authority, acting in accordance with and reinforcing the mission and organizational structure of the Library, assisting with the supervision of any functional area of the Library, and performing certain functions of the Library Director in his/her absence when assigned. Supervisors must enforce provisions of collective bargaining agreements, laws, regulations, and policies and must regularly and completely evaluate and manage the performance of employees that they directly or indirectly supervise. This Article is not intended to, nor shall it, constitute a job description but is a general statement on the supervisory responsibilities and functions of the members of this bargaining unit.

Related to Supervisory 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.

  • 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

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

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

  • Labour Management Committee (a) Where the parties mutually agree that there are matters of mutual concern and interest that would be beneficial if discussed at a Labour-Management Committee Meeting during the term of this Agreement, the following shall apply.

  • Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Project Manager, County The County shall appoint a Project Manager to act as liaison between the County and the Subrecipient during the term of this Contract. The County’s Project Manager shall coordinate the activities of the County staff assigned to work with the Subrecipient. The County’s Project Manager, in consultation and agreement with the County, shall have the right to require the removal and replacement of the Subrecipient’s Project Manager and key personnel. The County’s Project Manager shall notify the Subrecipient in writing of such action. The Subrecipient shall accomplish the removal within three (3) business days after written notice from the County’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Subrecipient’s Project Manager from providing further services under the Contract.

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