Local Professional Development Committee A. There shall be a Local Professional Development Committee (LPDC) to oversee, review, and approve individual professional development plans (IPDP) for course work, continuing education units and/or other equivalent activities.
1. The LPDC shall be responsible to recommend for the Superintendent’s approval, all in-service activities and workshops offered in the district during the school year for staff professional development.
2. Recommendations for District Workshops and In-Service activities should be submitted to the LPDC for approval and recommendation no later than the last school day of the year prior to the year it will be implemented.
3. The LPDC chair shall review and approve all “Professional Growth Reimbursement Application” forms.
B. The LPDC shall consist of three (3) teachers appointed by the Association President and two (2) members appointed by the Superintendent. One of the Superintendent's appointees will be a Principal employed by the district.
C. Appointments shall be for two (2) years with half of the committee members being appointed every other year.
1. Appointments shall be made on or before May 1.
2. The Appointments shall be made by each party outlined above, notifying the other of those appointed.
3. In the event of a vacancy, the committee members shall be replaced in accordance with "B." above.
4. The Association shall name a fourth teacher member and the Superintendent shall name a third administrative member to serve as alternates and attend trainings. These two (2) people shall act as substitutes when a committee member is absent.
D. This committee shall meet monthly.
1. The committee may also be convened by the request of two sitting members.
2. A quorum shall consist of five (5) members. When administrative licenses/certificates are reviewed, two (2) sitting teacher members will abstain and the decision will be decided by three (3) members.
3. If the committee determines it is needed, they will be provided two (2) professional release days to meet during regular school hours. Substitutes will be provided for the committee members on these release days.
4. Committee members shall be provided an additional annual stipend of $1,000 for meetings beyond the normal work day or year. This stipend shall be paid in two (2) semi-annual payments. Any member who fails to serve the full year shall have the above compensation prorated on a monthly basis for each month served.
5. Decisions of the LPDC will be made by consensus of the committee members present.
6. The committee minutes shall be prepared and maintained in compliance with the laws governing the operation of committees of public bodies.
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.
LABOR MANAGEMENT COMMITTEE Section 1. In order to facilitate communication between labor and management, a Labor Management Committee consisting of the Department Head and/or his designated alternate, the Assistant Chief of Police and two (2) Team Managers, and three (3) representatives of the Lincoln Police Union, along with at least one (1) Team Representative, will make up the Labor Management Committee. The Department Head will designate management personnel and the Union shall select Union representatives. Members will serve at the pleasure of the Department Head or Union President, depending upon who the member represents. Members will serve and be replaced on a staggered system (approximately three (3) year limit) depending upon the schedule agreed upon by the Department Head and the Union President.
Section 2. Each Team area will be represented by a member of any rank to serve as spokesperson for that area. They will meet at least one week prior to the monthly Labor Management Committee meeting to formulate the common areas of interest and to elect a spokesperson to present the items in writing to the Labor Management Committee. Payment for attending this meeting will be at the discretion of the Department Head. Spokesperson will be chosen on a rotating basis. Team representatives will be picked by a vote of the Team members that they are representing.
Section 3. The Labor Management Committee may discuss any area of the Department, with limitation only on those areas already under agreement between the City and the Union. The agenda will be based on the problem areas brought to the attention of the Committee by the Team Representatives and on any area representative members of Labor Management feel need to be discussed. Topics for discussion will be posted on the Union bulletin board and disseminated to Labor Management Committee members at least one (1) week prior to the monthly meeting.
Section 4. Membership is subject to change through attrition and elected office, however, a one (1) week notice must be given to the Committee to afford the new member(s) voting privileges.
Section 5. Realizing that communication is the key element to the smooth operation of any organization, the Labor Management Committee will xxxxxx an element of cooperation and unity of organizational members, be they labor or management.
Section 6. Meetings shall be held at least once per calendar month. Additional meetings may be scheduled by mutual agreement of the Committee and the Department Head.
Section 7. A quorum shall consist of two (2) members from labor and two (2) members from management.
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.
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.
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.
Training Committee The parties to this Agreement may form a Training Committee. The Training Committee will be constituted by equal numbers of Employer nominees and ETU employee representatives and have a charter which clearly states its role and responsibilities. It shall monitor the clauses of this Agreement which relate to training and ensure all employees have equal access to training.
LABOR/MANAGEMENT COMMITTEES A. Statewide
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: 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
