Attendance at Agent Functions Sample Clauses

Attendance at Agent Functions. From time-to-time there are corporate functions hosted by Agent, which will benefit the on-site staff members, and Association hereby consents to its on-site staff members’ attendance of such functions. In addition, depending upon the time and character of the Agent function, the Association understands that the on-site staff office, if applicable, will either be closed or alternate staff coverage may be provided at the Association’s expense.
AutoNDA by SimpleDocs

Related to Attendance at Agent 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.

  • JOINT LABOUR MANAGEMENT COMMITTEE A Joint Labour Management Committee shall be established to attend to those matters which are of mutual interest. To ensure its effectiveness the Committee shall be separate and apart from the grievance procedure.

  • 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. (b) An equal number of representatives of each party as mutually agreed shall meet at a time and place mutually satisfactory. A request for a meeting hereunder will be made in writing prior to the date proposed and accompanied by an agenda of matters proposed to be discussed, which shall not include matters that are properly the subject of grievance or negotiations for the amendment or renewal of this agreement. Any representative(s) attending such meetings during their regularly scheduled hours of work shall not lose regular earnings as a result of such attendance. (c) It is agreed that the topic of a rehabilitation program for drug and alcohol abuse is an appropriate topic for the Labour-Management Committee. It is also agreed that the topic of the utilization of full-time and part-time staff is an appropriate topic for the Labour-Management Committee. The committee shall have access to work schedules and job postings upon request. (d) It is understood that joint meetings with other Labour-Management Committees in the Hospital may be scheduled concerning issues of mutual interest if satisfactory to all concerned. (e) Where two or more agreements exist between a Hospital and CUPE the Committee may be a joint one representing employees under both agreements, unless otherwise agreed.

  • Association Responsibilities The Association shall have, in addition to other responsibilities expressly set forth herein or provided by law, the following responsibilities:

  • Professional Responsibilities Other activities to support the delivery of the Xxxxxx Xxxxxx Business Plan and Xxxxxx Mission Strategic Plan, as requested by your manager • As an employee, be responsible under the Work Health & Safety Act for the health and safety of all persons they come into contact with, during employment • All hazards and injuries must be reported through the normal process as set out in Xxxxxx Mission’s Work Health, Safety and Rehabilitation Quality Management System and site procedures • Participate in the review and maintenance of industry specific and internal audit processes, as per Xxxxxx Mission’s standard policy and procedures • In relation to Xxxxxx Mission and the Uniting Church in Australia, attend such functions, meetings, seminars, training courses as directed by your supervisor • In relation to Xxxxxx Mission attend worship services as encouraged by your supervisor • Participate on a quarterly basis in Xxxxxx Mission’s Employee contribution and development process • Take responsibility for personal career development and training • Participate in Xxxxxx Mission’s Orientation program, so as to gain an understanding of, and • promote, the application of the EEO, Affirmative Action, Privacy Act, Work Health & Safety Act and other relevant legislation • Administer Xxxxxx Mission’s philosophy of care and other relevant policy documents as appropriate • Demonstrate responsible stewardship of all resources, and willingness to report impropriety in keeping with the values of Xxxxxx Mission • Ensure the reputation and integrity of Xxxxxx Mission is maintained at all times • Maintain confidentiality

  • 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

  • Contractor’s Project Manager and Key Personnel Contractor shall appoint a Project Manager to direct the Contractor’s efforts in fulfilling Contractor’s obligations under this Contract. This Project Manager shall be subject to approval by the County and shall not be changed without the written consent of the County’s Project Manager, which consent shall not be unreasonably withheld. The Contractor’s Project Manager shall be assigned to this project for the duration of the Contract and shall diligently pursue all work and services to meet the project time lines. The County’s Project Manager shall have the right to require the removal and replacement of the Contractor’s Project Manager from providing services to the County under this Contract. The County’s Project manager shall notify the Contractor in writing of such action. The Contractor shall accomplish the removal within five (5) business days after written notice by the County’s Project Manager. The County’s Project Manager shall review and approve the appointment of the replacement for the Contractor’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Contractor’s Project Manager from providing further services under the Contract.

  • Other Agents; Arrangers and Managers None of the Lenders or other Persons identified on the facing page or signature pages of this Agreement as a “syndication agent,” “documentation agent,” “co-agent,” “book manager,” “lead manager,” “arranger,” “lead arranger” or “co-arranger” shall have any right, power, obligation, liability, responsibility or duty under this Agreement other than, in the case of such Lenders, those applicable to all Lenders as such. Without limiting the foregoing, none of the Lenders or other Persons so identified shall have or be deemed to have any fiduciary relationship with any Lender. Each Lender acknowledges that it has not relied, and will not rely, on any of the Lenders or other Persons so identified in deciding to enter into this Agreement or in taking or not taking action hereunder.

  • JOINT LABOR MANAGEMENT COMMITTEE The parties agree that they will continue the Joint Labor-Management Committee to discuss matters of mutual interest relating to the employees covered by this Agreement. Topics for the Joint Labor-Management Committee may include, but are not limited to, Professional Development, Incentive Pay, etc. The Committee shall meet quarterly or as mutually agreed by the co-chairs. The President of CWA or designee and the Director of Human Resources or designee shall serve as co-chairs.

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