Initiation (i) Seller shall deliver a Transaction Request or Purchase Price Increase Request, as applicable, to Buyer on or prior to the date and time set forth in Section 4(b)(vii) prior to entering into any Transaction. Such Transaction Request or Purchase Price Increase Request shall include an Asset Schedule with respect to the Underlying Assets to be sold in such requested Transaction. Buyer shall confirm the terms of each Transaction by issuing a written confirmation to the Seller promptly after the parties enter into such Transaction in the form of Exhibit A attached hereto (a “Confirmation”). Such Confirmation shall set forth (A) the Purchase Date, (B) the Purchase Price, (C) the Repurchase/Release Date, (D) the Pricing Rate applicable to the Transaction, (E) the applicable Purchase Price Percentages, and (F) additional terms or conditions not inconsistent with this Agreement. Seller shall execute and return the Confirmation to Buyer via facsimile or electronic mail on or prior to 5:00 p.m. (New York time) on the date one (1) Business Day prior to the related Purchase Date.
(ii) The Repurchase/Release Date for each Transaction shall not be later than the Termination Date.
(iii) Each Confirmation, together with this Agreement, shall be conclusive evidence of the terms of the Transaction(s) covered thereby.
(iv) Subject to the terms and conditions of this Agreement, during such period Seller may sell, repurchase and resell Purchased Assets, Pledged Assets, Underlying Assets and Eligible Assets hereunder.
(v) No later than the date and time set forth in the Custodial Agreement, Seller shall deliver to the Custodian the Asset File pertaining to each Eligible Asset to be purchased by Buyer.
(vi) Upon Buyer’s receipt of the Trust Receipt in accordance with the Custodial Agreement and subject to the provisions of this Section 4, the Purchase Price may then be made available to Seller by Buyer transferring, via wire transfer to the account designated by the Seller, in the aggregate amount of such Purchase Price in funds immediately available.
Negotiation Teams Neither party in any negotiations shall have any control over the selection of the bargaining representatives of the other party. The parties mutually pledge that their representatives will be clothed with all necessary authority and power to make proposals, counterproposals and to reach tentative agreement on items being negotiated. The parties realize the Agreement shall only be effective subject to the ratification of the BTU-ESP and the School Board. The Negotiation/Labor Management team shall consist of no more than six
Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget.
ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule.
iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables.
iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff.
v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project.
vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project.
vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project.
viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan.
ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution.
x - Base Drawings and Site Survey Information
Service Coordinators Each Party has designated an employee or title as the key contact for the day-to-day implementation or monitoring of each Service as specified in the applicable Transition Service Schedule (each, a “Service Coordinator”). The Parties shall direct communications relating to specific Services to the applicable Service Coordinators. The Service Coordinators shall report to the Transition Committee from time to time, as directed by the members of the Transition Committee designated by the applicable Party.
Project Coordinator Within 14 days of the effective date of this Consent Agreement, DTSC and Respondent shall each designate a Project Coordinator and shall notify each other in writing of the Project Coordinator selected. Each Project Coordinator shall be responsible for overseeing the implementation of this Consent Agreement and for designating a person to act in his/her absence. All communications between Respondent and DTSC, and all documents, report approvals, and other correspondence concerning the activities performed pursuant to this Consent Agreement shall be directed through the Project Coordinators. Each party may change its Project Coordinator with at least seven days prior written notice.
Office of Inspector General Investigative Findings Expert Review In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 531.102(m-1)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.
Scope of Professional Services 3.1 On the terms and conditions set forth in this Agreement, COUNTY hereby engages CONTRACTOR to provide all labor, materials and equipment to complete the Project/Service in accordance with the Scope of Services, attached hereto and incorporated herein as Attachment A, as modified or clarified by Addendum(s) # , dated , attached hereto and incorporated herein by reference as Attachment B. It is understood that the Scope of Services may be modified by change order as the Project/Service progresses, but to be effective and binding, any such change order must be in writing, executed by the parties, and in accordance with the COUNTY’s Purchasing Policies and Procedures. A copy of these policies and procedures shall be made available to the CONTRACTOR upon request.
3.2 The term of this Agreement shall be as follows (please check box): The parties acknowledge that this is a project specific agreement and that the single Project/Service shall be completed by the CONTRACTOR within ( ) calendar days after the Notice to Proceed is issued. The CONTRACTOR and COUNTY acknowledge that this Agreement is for a twelve (12) month term and that the CONTRACTOR shall complete the work as specified in the Scope of Services. The COUNTY has the option to renewal this Agreement for four (4) additional one (1) year period(s). The prices set forth in this Agreement shall prevail for the full duration of the initial contract term unless otherwise indicated elsewhere in this document. Prior to completion of each exercised contract term, the COUNTY may consider an adjustment to price based on changes in the following pricing index: CPI. It is the CONTRACTOR’s responsibility to request any pricing adjustment in writing under this provision. The CONTRACTOR’s written request for adjustment should be submitted thirty (30) calendar days prior to expiration of the then current contract term and clearly substantiate the requested increase. The written request for adjustment should not be in excess of the relevant pricing index change. If no adjustment request is received from the CONTRACTOR, the COUNTY will assume that the CONTRACTOR has agreed that the optional term may be exercised without pricing adjustment. Any adjustment request received after the commencement of a new option period shall not be considered. The COUNTY reserves the right to reject any written price adjustments submitted by the CONTRACTOR and/or to not exercise any otherwise available option period based on such price adjustments. Continuation of the contract beyond the initial period, and any option subsequently exercised, is a COUNTY’s prerogative, and not a right of the CONTRACTOR. This prerogative will be exercised only when such continuation is clearly in the best interest of the COUNTY. All work shall be performed in accordance with good commercial practice. The work schedule and completion dates shall be adhered to by the CONTRACTOR except in such cases where the completion date will be delayed due to acts of God, strikes, or other causes beyond the control of the CONTRACTOR. In these cases, the CONTRACTOR shall notify the COUNTY of the delays in advance of the original completion so that a revised delivery schedule can be appropriately considered by the COUNTY. No additional days shall be granted for rain delays.
3.3 The CONTRACTOR shall be solely responsible for obtaining all necessary approvals and permits to complete the Project/Service.
3.4 The CONTRACTOR shall remain appropriately licensed and/or employ the services of a subcontractor who is appropriately licensed throughout the course of the Project/Service. Failure to maintain all required licenses shall entitle the COUNTY, at its option, to terminate this Agreement.
3.5 Although this Agreement identifies specific facilities to be serviced, it is hereby agreed and understood that any County department or agency facility may be added to this Agreement at the option of the County. When required by the pricing structure of the Agreement, the CONTRACTOR shall be invited to submit price quotes for these additional facilities. The additional site(s) shall be added to this Agreement by formal modification. The COUNTY may obtain price quotes for the additional facilities from other vendors in the event that fair and reasonable pricing is not obtained from the CONTRACTOR or for other reasons at the County’s discretion. Although this Agreement identifies specific facilities to be serviced, it is hereby agreed and understood that any County department or agency may delete service for any facility when such service is no longer required, upon fourteen (14) calendar days written notice.
3.6 The CONTRACTOR acknowledges that it has sufficient understanding of the nature and location of the work; the general and local conditions, including but not limited to, those bearing upon transportation, disposal, handling and storage of materials; availability of labor, water, electric power, and roads; and uncertainties of weather or similar physical conditions at the site; the character of equipment and facilities needed preliminary to and during the completion of the Project/Service. The CONTRACTOR further acknowledges that the CONTRACTOR has satisfied itself as to the character, quality and quantity of surface and subsurface materials, obstacles or conditions of the site. Any failure by the CONTRACTOR to acquaint itself with any aspect of the work or with any of the applicable conditions shall not relieve the CONTRACTOR from responsibility for adequately evaluating the difficulty or cost of successfully performing the work required, nor shall it be considered a basis for any claim for additional time or compensation. The COUNTY assumes no responsibility for any conclusions or interpretations made by the CONTRACTOR on the basis of the information made available by the COUNTY. The COUNTY also assumes no responsibility for any understanding or representations made by its officers or agents during or prior to the execution of this contract, unless such understanding or interpretations are made in writing and incorporated herein by reference.
3.7 If required, the Contractors shall attend a mandatory pre-bid meeting. Whether or not there is a mandatory or non-mandatory pre-bid, the contractor shall be required to carefully examine any supplied drawings and/or specifications and be thoroughly aware regarding any and all conditions that may in any manner affect the work to be performed under the contract. If a pre-bid meeting is not required the Contractor shall visit the site to familiarize themselves with the Project/Service, see existing conditions, and take measurements. No additional allowances will be made for lack of knowledge of these conditions.
3.8 In the event of any conflict between the drawings and specifications contained within this Agreement, the following shall govern:
A. Addenda shall supersede all other contract documents to the extent specified in the addenda. Subsequent addenda shall supersede prior to addenda only to the extent specified therein.
B. Drawings and specifications are intended to agree and be mutually complete. Any item not contained within the drawings, but contained in the specifications, or vice-versa, shall be provided and/or executed as shown in either the drawing or specification at no extra costs to the COUNTY. Should anything not included in either the drawing and/or the specifications be necessary for the proper construction and/or operation of the Project/Service as herein specified, or should any error or disagreement between the specifications and drawings exist or appear to exist, the CONTRACTOR shall not derive unjust benefit thereby, or use such disagreement counter to the best interests of the COUNTY. The CONTRACTOR shall immediately notify the COUNTY’s Project Manager of any discrepancy and await the Project Manager’s direction before proceeding with the work in question.
3.9 CONTRACTOR acknowledges and agrees that CONTRACTOR shall utilize the U.S. Department of Homeland Security’s E-Verify system in accordance with the terms governing use of the system to confirm the employment eligibility of:
A. All persons employed by the CONTRACTOR during the term of this Agreement to perform employment duties within Lake County; and
B. All persons, including subcontractors, assigned by the CONTRACTOR to perform work pursuant to the contract.
3.10 CONTRACTOR acknowledges and agrees that, in accordance with Section 255.099, Florida Statutes, if the Project/Service assigned to CONTRACTOR is being supported in whole or in part by State funding the CONTRACTOR shall give preference to the employment of state residents in the performance of the work on the Project/Service if state residents have substantially equal qualifications to those of non- residents. If the CONTRACTOR is required to employ state residents, the CONTRACTOR shall contact the Department of Economic Opportunity to post the employment needs in the State’s job bank system. However, in work involving the expenditure of federal aid funds, this section may not be enforced in such a manner as to conflict with or be contrary to federal law prescribing a labor preference to honorably discharged soldiers, sailors, or marines, or prohibiting as unlawful any other preference or discrimination among the citizens of the United States.
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).
Project Steering Committee 1. For a sound implementation and management of the project, a steering committee shall be set up in line with provisions of the programme manual.
2. The steering committee is the decision-making body of the project and it shall be composed by representatives of the LP and all PPs duly authorised to represent the respective LP and PP institutions. It shall be chaired by the LP and it shall meet on a regular basis. Associated partners shall be invited to take part in the steering committee in an advisory capacity. External key stakeholders may also be invited to take part to one or more meetings in an observer/advisory capacity.
3. The steering committee shall at least:
a. be responsible for monitoring and validating the implementation of the project and the achievement of the planned results as in the approved application form;
b. perform the financial monitoring of the project implementation and to decide on any budget modifications as in § 11 of this agreement;
c. monitor and manage deviations of the project implementation;
d. decide on project modifications (e.g. partnership, budget, activities, and duration) if needed;
e. be responsible for the settlement of any disputes within the partnership (as stipulated in § 22 of this agreement).
4. Further aspects, including the creation of sub-groups or task forces, may be set out in the rules of procedure of the steering committee.
Project Coordination The Engineer shall coordinate all subconsultant activity to include quality and consistency of deliverables and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.
