Central Management Members Sample Clauses

Open Split View

Download

Share

Cite

Central Management Members. Intel will appoint five members. Three members will be senior managers and two HR representatives.

Sample 1

Save

Copy

Related to Central Management Members

• Management Members and Shares 8 2.1 Rights and Duties of the Manager. 8 2.2 Officers 9 2.3 Members. 9

• Labour Management Meetings The committee meeting shall normally be held every second month however, either party may call a meeting of the Joint Labour Management Committee. The meeting shall be held at a time and place fixed by mutual agreement but no later than fourteen (14) calendar days after the initial request, unless mutually agreed.

• Union/Management Meetings ‌ The Union Committee and the Senior Union Official of the Union, or her/his representative, shall, as occasion warrants, meet with the Committee on Labour Relations for the purpose of discussing and negotiating a speedy settlement of any grievance or dispute arising between the Employer and the employee concerned, including possible re-negotiations relative to this Agreement and the Schedules which are a part hereof. However, except for renegotiations of Agreements, these matters shall be introduced to such meetings only after the established grievance procedure has been followed. Grievances of a general nature may be initiated by a member of the Union Committee in step two of the grievance procedure outlined in Article 9.04.

• Management meetings 31.1 Either the Engineer or the Contractor may require the other to attend a management meeting. The business of a management meeting shall be to review the plans for remaining work and to deal with matters raised in accordance with the early warning procedure. 31.2 The Engineer shall record the business of management meetings and is to provide copies of his record to those attending the meeting and to the Employer. The responsibility of the parties for actions to be taken is to be decided by the Engineer either at the management meeting or after the management meeting and stated in writing to all who attended the meeting.

• Shareholder Services Transfer Agent or its agent will investigate all inquiries from Shareholders of a Fund relating to Shareholder accounts and will respond to all communications from Shareholders and others relating to its duties hereunder and such other correspondence as may from time to time be mutually agreed upon between Transfer Agent and a Fund. Transfer Agent shall provide each Fund with reports concerning Shareholder inquires and the responses thereto by Transfer Agent, in such form and at such times as are agreed to by the Fund and Transfer Agent.

• Labour Management Relations Committee In recognition of the mutual benefits of open communications and on-going consultation between the faculty and the employer, the Labour/Management Relations Committee will meet on a regular basis and have equal representation for the Union and the Employer. The LMRC will serve as an open forum for the free and candid discussion of matters of mutual concern to faculty members and management.

• Labor Management Meetings Section 11.1. In the interest of sound labor/management relations, the parties agree to meet at agreeable dates and times for the purpose of discussing those issues outlined herein. Normally, meetings held pursuant to this Article will occur no more frequently than once every three (3) months, unless matters of an urgent nature require immediate attention. No more than three (3) employee representatives in pay status will attend such meetings. The Employer and OAPSE may have representatives as each deems necessary to address the issues. Section 11.2. The party requesting the meeting shall furnish an agenda and the names of the employees who will be attending, with the request for the meeting. Subjects that may be discussed at these meetings shall include but not be limited to the items listed below: A. Discuss the administration of this Agreement. B. Notify OAPSE of changes made by the Employer which may affect bargaining unit members. C. Discuss grievances which have not been processed beyond the final step of the Grievance Procedure when such discussions are mutually agreed to by the parties. D. Disseminate general information of interest to the parties. E. Give OAPSE representatives the opportunity to share the views of its members and/or make suggestions on subjects of interest to their members. F. Discuss ways to improve efficiency and work performance. Section 11.3. Written responses promised by either party shall be submitted to the other party within ten (10) work days after such meeting. Section 11.4. Labor/Management meetings are not intended to be negotiation sessions to alter or amend the basic agreement. Section 11.5. In the event of a change of duties of a position within the bargaining unit, or in the event that a new position is created within the Library, the Employer shall determine whether the new or changed position will be included in or excluded from the bargaining unit and shall so advise the Union in writing within thirty (30) calendar days. If the Union disputes the Employer's determination of bargaining unit status, the parties shall meet in an attempt to resolve their disagreement within seven (7) calendar days from the Union notification to the Employer. If the parties agree on the determination, it shall be implemented as agreed by the Employer and the Union and a joint petition for amendment of the bargaining unit shall be filed with the State Employment Relations Board (SERB). If the parties do not agree, the parties shall jointly petition SERB pursuant to Chapter 4117 of the Ohio Revised Code and the SERB Rules and Regulations for a determination of bargaining unit status.

• Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

• Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

• Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.