We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Reduction Process Sample Clauses

Reduction ProcessIn the event Vendor accepts a proposed New Broadband Backhaul Market Price pursuant to clause (1) of Subsection (ii) of this Subsection (a), then effective as of the later of (a) the New Broadband Backhaul Market Price Effective Date corresponding to such New Broadband Backhaul Market Price Notice, and (b) [*Material Omitted and Separately Filed Under an Application for Confidential Treatment], the Monthly Per Subscriber Line Charge will be reduced to the New Broadband Backhaul Market Price set forth in the corresponding New Broadband Backhaul Market Price Notice, and with respect to such CONFIDENTIAL TREATMENT REQUESTED Broadband Backhaul Services, Vendor will, if requested by Customer, [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] per [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] at [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] or the [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] corresponding to such New Broadband Backhaul Market Price; provided, however, that Vendor shall not be obligated to reduce the Monthly Per Subscriber Line Charge [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] for which Vendor reduced prices pursuant to this Subsection (iii). Notwithstanding the foregoing: (1) Vendor shall not be obligated to reduce the Monthly Per Subscriber Line Charge at a rate that is more rapid than the rate at which the [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] provides Customer with [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] relative to the applicable [*Material Omitted and Separately Filed Under an Application for Confidential Treatment], as measured monthly.
Reduction ProcessThe District will determine the Teacher(s) to be reduced within a program area in accordance with the following procedure which recognizes both the quality and length of the Teacher's service to the District. Teacher(s) who are subject to this process will be informed of that fact.
Reduction Process. The Board shall dismiss employees in inverse seniority order in each category of position, when a reduction in force due to economic reasons and/or due to reduction of some particular type of educational support personnel service is deemed to be in the best interest of the District. The sequence of dismissal for bargaining unit members in a reduction in force shall be the following order: 1. All part‐time ESPs shall be dismissed prior to dismissal of full‐time members; 2. The least senior members in each of the remaining categories of positions listed in Section A hereinabove as the Board determines; 3. Any ties in seniority dates shall be broken by a draw of lots; 4. Bumping rights" as a part of reduction in force shall be as follows: a) Part‐time employees shall have no right to "bump" or move into any other category of position because of seniority acquired at JSD #117. b) Bargaining unit members may only "bump" or move into the General Education Paraprofessionals category of position if a member has more seniority in that category than a less senior member assigned to that category and the member is highly qualified under the law. No bargaining unit member may "bump" into any other category of position other than the General Education Paraprofessionals category of position as provided herein above.
Reduction Process. On a calendar quarterly basis, beginning after the Effective Date, Cadence shall review invoices paid against items in the Baxter Capex for that quarter and provide Baxter with a letter indicating Cadence’s intention to reduce the face value of the Letter of Credit, by amendment, for the total amount of the invoices paid in the prior periods (and not yet credited). If Baxter agrees with the amount of Cadence’s proposed reduction, Baxter will send a letter to the designated contact of the issuer of the Letter of Credit authorizing the reduction, with a copy to Cadence. The issuance and maintenance of the Letter of Credit and its amendments will be at the sole cost and expense of Cadence. Any Letter of Credit amendments shall be in form and substance satisfactory to Baxter, and shall be implemented with no lapse in coverage.
Reduction Process. 1. The District reserves the right to determine positions to be eliminated. 2. Layoffs within each affected job classification shall be determined by the District on the basis of the operational needs, special occupational skills, specialized training, and employees' seniority within such job classification. 3. Where job classification seniority dates are the same, the employee’s bargaining unit seniority shall apply. 4. A tie in bargaining unit seniority shall be settled by drawing of lots. The Director of Human Resources and the Association President or their designees will witness the drawing. 5. No regular employee shall be laid off within a job classification until all probationary and temporary employees in such classification have been terminated. 6. An employee laid off in a classification may bump into a previously held classification or a lesser classification within a job family, so long as the District determines the employee is qualified and has proven satisfactory performance, based upon the employee’s evaluation in the classification. The District will determine placement of the affected employee.
Reduction Process. The specific process for reduction with respect to the union bargaining units is set out below. The Unions will seek to facilitate the process within the context of their responsibilities to their members. The parties agree that voluntary solutions are the best ones, and will make every effort to achieve them. The employer together with the unions will canvass the bargaining units by means of a notification process to see the degree to which necessary reductions can be accomplished on a voluntary basis by early retirement, transfer to another employer, and other voluntary options. In the case of voluntary options, where more employees are interested in an available option than are needed for the necessary reductions, the options will be offered to qualified employees on the basis of seniority. The parties at the facility level will cooperate in the spirit of this agreement to facilitate interim job security solutions by means of relief assignments pending more permanent solutions. In the case of voluntary job sharing that assists in the needs of labour adjustment, the labour adjustment program will pay the additional cost of group benefits that result from the job sharing arrangement. Failing voluntary resolution, positions to be reduced will be identified by the employer in accordance with the terms of the respective collective agreements. Employees identified by this process will be laid off only if: ◆ they chose layoff instead of options for continued employment with the same employer in another position, including a temporary position*; or ◆ they refuse placement into a generally comparable position with another employer in the region.
Reduction Process. ‌ In the event it becomes necessary for the Board to reduce the staff, the following procedures shall be followed: 1. The Board shall prepare a seniority list by either department or section showing professional personnel who are currently working or are qualified to be working in that department/section. 2. The seniority list above shall be made available to the Association by January 31st of the fiscal year. 3. Each professional bargaining unit member shall have five (5) work days to request any appropriate correction in the seniority list should the bargaining unit member believe that information contained therein is inaccurate. The final decision as to accuracy of information contained on the seniority list shall be left to the Superintendent. If no request is made within five (5) workdays, this shall constitute a waiver of a bargaining unit member’s right to a change or correction. 4. In the event it becomes necessary to reduce staff, the Board shall issue layoff notices to those individuals who are lowest on the seniority list for that department/section as defined in E.1. above. In the event that more than one Professional Staff Member in a department/section has the same seniority date, every attempt will be made to determine the order of hire on that date. This order will be used to determine the sequential listing of individuals for purposes of layoff. If no sequence can be determined a lottery agreed to by all affected individuals will be used to determine the layoff order. 5. Persons holding positions in other sections/departments who are on layoff status shall have the option to bump the least senior bargaining unit member in another department/section holding a position for which he/she has more seniority, provided they are not recalled by August 1st of current fiscal year to a position which requires their certification/approval.
Reduction Process. If reductions are still required after all voluntary processes have occurred, the District will follow the process outlined in Article 14 of the Teacher Contract.

Related to Reduction Process

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Sick Leave Verification Process a. The new school district shall provide the employee with the necessary verification form at the time the employee receives confirmation of employment in the school district. b. An employee must initiate the sick leave verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of commencing employment with the new school district. c. The previous school district(s) shall make every reasonable effort to retrieve and verify the sick leave credits which the employee seeks to port.

  • Seniority Verification Process i. The new school district shall provide the employee with the necessary verification form at the time the employee achieves continuing contract status. ii. The employee must initiate the seniority verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of receiving a continuing appointment in the new school district. iii. The previous school district(s) shall make every reasonable effort to retrieve and verify the seniority credits which the employee seeks to port.

  • Due Process 1. No certificated employee shall be disciplined without just cause. 2. The specific grounds forming the basis for official disciplinary action shall be made available to the employee in writing. If an employee is requested to give information which the District understands may lead to disciplinary action against that employee, the District shall advise the employee of the right to representation. If a request for representation is made, the interview shall not take place for a reasonable period of time to allow for the representative’s attendance. 3. Any complaint against an employee by a parent, student, or other person, which if proven true would provide the basis for discipline, shall be called to the attention of the employee within ten (10) days of receipt. Any complaint not called to the attention of the employee within ten (10) days of receipt may not be used as a basis for disciplinary action against the employee. 4. The District agrees to follow a policy of progressive discipline which generally includes verbal warning and written reprimand provided, however, that any disciplinary action taken against an employee shall be appropriate to the behavior which precipitates said action. (a) A verbal warning is an official verbal notification of employee misconduct. The warning should include the reason(s) for the warning and notice that future misconduct could result in more severe disciplinary action. Documentation of the verbal warning may be noted in the administrator’s working file. (b) A written reprimand is an official written notification of employee misconduct. A written reprimand should include the reasons for the reprimand and notice that future misconduct could result in more severe disciplinary action. (c) Any suspension of a teacher pending charges shall be with pay until official action by the Board of Directors. 5. Subject to the other provisions of this Agreement, any non-provisional employee receiving notification of non-renewal of contract, discharge, or adverse effect may elect to have the matter heard by either a hearing officer in accordance with RCW 28A.405.310 or an arbitrator in accordance with the grievance procedure.