INTRODUCTION/DURATION Sample Clauses

INTRODUCTION/DURATION. This agreement is made effective as of the first day of March, 2008, through and including February 28, 2010. This Agreement is by and between the County and the Sheriff of Xxxxxxxx County (hereinafter referred to as "Employer") and the Employees' Union of the Xxxxxxxx County Deputy Sheriff's Association, Inc.Sheriffs Department, affiliated with the New York State Union of Police Associations, Inc., or its successor (hereinafter referred to as the "Union" or "PBA"). In the event this Agreement expires and there is no successor agreement, and in accordance with NYS Civil Service Law, all terms and conditions shall remain in full force and effect until such time as an Agreement is effectuated. The Public Employees' Fair Employment Act of the State of New York, the other provisions of the State Civil Service Law, and local laws or resolutions now or hereafter adopted by the County which are not inconsistent with said Act shall govern the terms of this settlement.
Sample 1
AutoNDA by SimpleDocs

Related to INTRODUCTION/DURATION

  • Introduction The Texas Health and Human Services Commission ("HHSC") and the Contractor named in Section I (HHSC and Contractor may be referenced in this document collectively as the “Parties” and individually as the “Party") hereby enter into this Community Services Contract - Provider Agreement (the “Contract”) for the provision of services under the Contract type specified in Section I for the considerations set forth herein. The Contract Begin Date specified in Section I is not valid until this Contract is signed by both parties.

  • Contract Duration Actual Contract Duration: …………………………………………………………………………. Quality of office administration Quality of site management Competence of xxxxxxx Co-operation during contract Quality of workmanship Quality of materials Programme management Rectification of condemned work Tidiness of site Adequacy of equipment Adequacy of labour force Procurement of materials Labour relations Any other remarks considered necessary to assist in evaluation of the contractor? ................................................................................................................................................................................... ...................................................................................................................................................................................

  • Purchase Order Duration Purchase orders issued pursuant to this State Term Contract must be received by the Contractor no later than close of business on the last day of the Contract’s term to be considered timely. The Contractor is obliged to fill those orders in accordance with the Contract’s terms and conditions. Purchase orders received by the Contractor after close of business on the last day of the State Term Contract’s term shall be considered void. Purchase orders for a one-time performance of contractual services shall be valid through the performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the single delivery/performance, and shall survive the termination of the Contract. Contractors are required to accept purchase orders specifying delivery schedules exceeding the contracted schedule even when such extended delivery will occur after expiration of the State Term Contract. For example, if a state term contract calls for delivery 30 days after receipt of order (ARO), and an order specifies delivery will occur both in excess of 30 days ARO and after expiration of the state term contract, the Contractor will accept the order. However, if the Contractor expressly and in writing notifies the ordering office within ten (10) calendar days of receipt of the purchase order that Contractor will not accept the extended delivery terms beyond the expiration of the state term contract, then the purchase order will either be amended in writing by the ordering entity within ten (10) calendar days of receipt of the contractor’s notice to reflect the state term contract delivery schedule, or it shall be considered withdrawn. The duration of purchase orders for recurring deliveries of commodities or performance of services shall not exceed the expiration of the State Term Contract by more than twelve months. However, if an extended pricing plan offered in the State Term Contract is selected by the Customer, the Contract terms on pricing plans shall govern the maximum duration of purchase orders reflecting such pricing plans. Timely purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the recurring delivery/performance as provided herein, and shall survive the termination of the Contract. Ordering offices shall not renew a purchase order issued pursuant to a State Term Contract if the underlying contract expires prior to the effective date of the renewal.

  • Agreement Duration The term of the Agreement shall begin and end on the dates indicated in the Standard Grant Agreement, unless extended or terminated earlier in accordance with the applicable terms and conditions. The Grantee shall be eligible for reimbursement for work performed on or after the date of execution through the expiration date of this Agreement, unless otherwise specified in Attachment 2, Special Terms and Conditions. However, work performed prior to the execution of this Agreement may be reimbursable or used for match purposes if permitted by the Special Terms and Conditions.

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

  • Bidding Process 3.1. Bidding shall generally commence based on the sequence of the lot being shown on the PAH Website. However the Auctioneer has the right to vary the sequence without having to give prior notice to the intended bidders. 3.2. It shall be the responsibilities of the E-bidders to login through PAH website to wait for the turn to bid for the property lot in which they intend to bid. 3.3. The Auctioneer has the discretion to set a new reserve price in the event that there is more than one (1) registered bidder. 3.4. The amount of incremental bid will appear on the website prior to the commencement of the auction. 3.5. Registered online Bidders shall start bidding online by pressing the BID Button using their own gadgets with internet connection. If your bid is the highest, it will be denoted by a Green Coloured Box otherwise it will be a Red Coloured Box The highest bid shall flash 10 seconds (subject to change) interval for four (4) times " Calling Once, Calling Twice, Last Call and Sold". E-bidders may submit their bid at any of these stages of biddings by pressing the BID button. The successful bidder's bid will be denoted by a green coloured screen. The highest bidder shall be declared as the successful purchaser upon the fall of the hammer. 3.6. In the event that there is no bid after forty(40) seconds from the time of commencement of the auction, the auction shall be aborted. 3.7. Any bid once entered by the registered online E-bidders shall be binding and the bid shall not be withdrawn or retracted in any manner whatsoever after the fall of the hammer. 3.8. Both the successful and unsuccessful bidders will be notified by the Auctioneer through the website and also via E-mail where further directions are given in order to conclude the sale of the auction property. 3.9. In the event of any dispute, the decision of the Auctioneer shall be final and binding on all bidders. 3.10. Unsuccessful E-bidders shall have the deposit refunded to the same bank account from which the deposit transfer was made within two (2) working days from the date of auction. 3.11. The information shown and/or prompted on the screen handled by the PAH website in regards to the auction in particular the increment of the bidding price during the bidding process and the declaration of the successful bidder shall be final and conclusive.

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

  • Rejection During Probation ‌ (a) The Employer may reject any probationary employee for just cause. A rejection during probation shall not be considered a dismissal for the purpose of Clause 10.

  • Objectives and Scope 1. The Parties confirm their joint objective of strengthening and deepening their relations in all fields covered by this Agreement by developing their political dialogue and reinforcing their co-operation. 2. The Parties confirm their joint objective of working towards creating conditions under which, building on the outcome of the Doha Work Programme, a feasible and mutually beneficial Association Agreement, including a Free Trade Agreement, could be negotiated between them. 3. Implementation of this Agreement should help to create these conditions by striving for political and social stability, deepening the regional integration process and reducing poverty within a sustainable development framework in the Andean Community. 4. This Agreement governs the political dialogue and co-operation between the Parties and contains the necessary institutional arrangements for its application. 5. The Parties undertake to periodically assess progress, taking account of progress achieved before the entry into force of the Agreement.

  • Study Population ‌ Infants who underwent creation of an enterostomy receiving postoperative care and awaiting enterostomy closure: to be assessed for eligibility: n = 201 to be assigned to the study: n = 106 to be analysed: n = 106 Duration of intervention per patient of the intervention group: 6 weeks between enterostomy creation and enterostomy closure Follow-up per patient: 3 months, 6 months and 12 months post enterostomy closure, following enterostomy closure (12-month follow-up only applicable for patients that are recruited early enough to complete this follow-up within the 48 month of overall study duration).

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