Preparation Procedure Sample Clauses

Preparation Procedure. The Operator shall submit the operation expense budget identifying Joint Operation needs and broken down by expense item according to classification provided in this Agreement Clause 14 (section 14.1.
AutoNDA by SimpleDocs
Preparation Procedure. A Local Agency Agreement signed by the approving authority must be submitted by the local agency to the Region Local Programs Engineer when the Project Prospectus2 is submitted. To allow sufficient time for WSDOT review and execution, these documents should be submitted a minimum of 4 weeks prior to the time when federal authorization is desired. Agreements containing errors will be returned to the local agency for correction. Any changes must be initialed by the approving authority3. To avoid this delay, the agency should check all figures prior to submittal, and if in doubt, request assistance from the Region Local Programs Engineer. An agreement form and instructions are in DOT Form 140-039. Local agency cost estimates for each phase of a project are entered on the form, as well as the project name, length, termini, description, Project Agreement End Date, Proposed Advertisement Date (required for construction phase) and method of construction financing. These methods are described in the instructions of DOT Form 140-039. Local agency resolutions or ordinances that may be needed are discussed in the instructions of DOT Form 140-039.
Preparation Procedure. The Operator shall submit the Operating Expenses Budget, identifying the requirements of the Joint Operation, and shall detail the expense items set forth in the classification indicated in Clause 14 (number 14.1.2) of this Agreement. The cost factors for the assessment of the various activities that it plans to carry out during the year to which the Budget refers to, shall correspond to the true figures known at the time of preparation or, to the best information available. In all cases, the operating expense Budget shall be calculated bearing in mind the costs that are required by the entities that,
Preparation Procedure. Before proceeding with the cleaning procedure, ensure that you are wearing a lab coat and protective gloves.
Preparation Procedure. To provide MDT with the information necessary to write the PSA, a Local Agency Agreement Form must be prepared and submitted by the local agency to the LAG Certification Liaison when the Project Proposal (see Chapter 6) is submitted. This agreement form will be retained by MDT. It is the responsibility of the local agency to retain a copy for their files. An agreement form is contained in Appendix 7.4.1, with instructions for completing it in Appendix
Preparation Procedure. An original Local Agency Agreement signed by the approving authority must be submitted by the local agency to the Region Local Programs Engineer when the Project Prospectus (Chapter 21) is submitted. This agreement form will be retained by WSDOT. It is the responsibility of the local agency to submit an additional agreement form or a copy if they need an executed agreement for their files. To allow sufficient time for WSDOT review and execution, these documents should be submitted a minimum of 4 weeks prior to the time when federal authorization is desired. Agreements containing errors will be returned to the local agency for correction. Any changes must be initialed by the approving authority (Chapter 13). To avoid this delay, the agency should check all figures prior to submittal, and if in doubt, request assistance from the Region Local Programs Engineer. An agreement form and instructions are in DOT Form 140-039. Local agency cost estimates for each phase of a project are entered on the form, as well as the project name, length, termini, description, Project Agreement End Date, Proposed Advertisement Date (required for construction phase) and method of construction financing. These methods are described in the instructions of DOT Form 140-039. Local agency resolutions or ordinances that may be needed are discussed in the instructions of DOT Form 140-039.

Related to Preparation Procedure

  • NEGOTIATION PROCEDURE 3.1 On or before September 1 of the prior year in which this agreement is to expire either party may initiate negotiations in accordance with RSA 273:A. The parties shall meet not later than September 15th, at which time the Association shall submit its proposals, unless another date is mutually agreed to by the parties. 3.2 The Negotiating Committee of the Board and the Negotiating Committee of the Association shall have authority to reach a complete agreement, subject to ratification by the Board and the qualified voting members of the Association covered by this Agreement. 3.3 Any agreement reached shall be reduced to writing and signed by the Board and the Association. Any agreement reached which requires the expenditure of additional public funds for its implementation shall not be binding on the Board, unless and until the necessary appropriations have been made by the Annual School District Meeting. The Board shall make a good faith effort to secure the funds necessary to implement said agreements. 3.4 If, after discussion of all negotiable matters, the parties fail to reach agreement, either party may declare impasse. In the event of impasse, the rules and procedures for “Resolution of Disputes” as outlined under RSA 273: A-12 shall be followed. 3.5 The cost for the services of the mediator and/or fact finder including per diem expenses, if any, will be shared equally by the Board and the Association. 3.6 Determinations and/or recommendations under the provision of Section 3.4 of this Article III will not be binding on the parties in accordance with RSA 273: A 3.7 If the monies to fund the economic provisions are not appropriated as provided in this Article III, Section 3.3 and/or if either party rejects the recommendations set forth in this Article III, Section 3.6, then the parties shall do the following: A. The appropriate party shall notify the other party of its intent to renegotiate the provisions of this Agreement, and: B. If either negotiating team rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the full membership of the employee organization and to the Board of the public employer, which shall vote to accept or reject so much of his/her recommendations as is otherwise permitted by law. C. If either the full membership of the employee organization or the public employer rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the legislative body of the public employer, which shall vote to accept or reject so much of his/her recommendations as otherwise is permitted by law. D. If the impasse is not resolved following the action of the legislative body, negotiations shall be reopened. Mediation may be requested by either party and may involve the Board of the public employer if the mediator so chooses. 3.8 The parties may, by mutual agreement, pass over mediation and go directly to fact finding. 3.9 Neither party in any negotiations shall interfere with the selection of the negotiating or bargaining representatives of the other party.

  • NEGOTIATION PROCEDURES A. At least sixty (60) days prior to the expiration of this Agreement, the parties will begin negotiations for a new Agreement covering wages, hours, terms and conditions of employment of employees covered by this Agreement. B. In any negotiations described in this article, neither party shall have control over the selection of the negotiating representatives of the other party and each party may select its representatives from within or outside the school district. It is recognized that no final Agreement between the parties may be executed without ratification by the Board and the Association. The parties mutually pledge that representatives selected by each shall be clothed with necessary power and authority to make proposals and concessions in the course of negotiations, subject only to such ultimate ratification. C. If the parties fail to reach an agreement in any such negotiations, either party may invoke the procedures established under Public Act 379 as amended. D. Members of the Association’s negotiating team and/or consultants thereto, who are employees of the Employer, shall be released from their normal duties without loss of salary when meetings of the two negotiating teams are scheduled during their normal working hours. E. The parties hereby agree that their Teams shall meet at least quarterly during the school year to attempt to resolve problems. The topics for these meetings shall be established by the group at the previous quarter’s meeting whenever possible. Topics will remain on the agendas until resolved or until deleted by mutual agreement. F. Prior to the establishment of any new position in the bargaining unit, the Employer shall notify the Association of such a contemplated action, and meet with the Association to negotiate workload for the position. This provision does not preclude the Employer’s ability to create and post positions. If the timing of the decision to establish the position precludes such a meeting, the Employer shall meet with the Association as soon as possible. The parties may agree that the position should be allowed to operate without a defined workload for some defined period of time to determine what a reasonable workload might be. G. By mutual consent of both parties any section of this agreement may be reopened.

  • Evaluation Procedure The procedural requirements set forth in this agreement which conform with and provide specificity to the statutory obligations established by Ohio Rev. Code § 3319.111 and § 3319.112.

  • Mediation Procedure The Chairman shall promptly advise the parties of a scheduled Mediation Hearing date. Unless a party requests an expedited procedure, or unless all parties to the proceeding agree to one or more extensions of time, the Mediation Hearing set forth below shall be completed within forty (40) days of BCBSA's receipt of the Complaint. The selected mediators, unless the parties otherwise agree, shall adhere to the following procedure: i. Each party must be represented by its CEO or other representative who has been delegated full authority to resolve the dispute. However, parties may send additional representatives as they see fit. ii. By no later than five (5) days prior to the date designated for the Mediation Hearing, each party shall supply and serve a list of all persons who will be attending the Mediation Hearing, and indicate who will have the authority to resolve the dispute. iii. Each party will be given one-half hour to present its case, beginning with the complaining party (or parties), followed by the other party or parties. The parties are free to structure their presentations as they see fit, using oral statements or direct examination of witnesses. However, neither cross- examination nor questioning of opposing representatives will be permitted. At the close of each presentation, the selected mediators will be given an opportunity to ask questions of the presenters and witnesses. All parties must be present throughout the Mediation Hearing. The selected mediators may extend the time allowed for each party's presentation at the Mediation Hearing. The selected mediators may meet in executive session, outside the presence of the parties, or may meet with the parties separately, to discuss the controversy. iv. After the close of the presentations, the parties will attempt to negotiate a settlement of the dispute. If the parties desire, the selected mediators, or any one or more of the selected mediators, will sit in on the negotiations. v. After the close of the presentations, the selected mediators may meet privately to agree upon a recommendation for resolution of the dispute which would be submitted to the parties for their consideration and approval. If the parties have previously agreed to be bound by the results of this procedure, this recommendation shall be binding upon the parties. vi. The purpose of the Mediation Hearing is to assist the parties to settle their grievances short of mandatory dispute resolution. As a result, the Mediation Hearing has been designed to be as informal as possible. Rules of evidence shall not apply. There will be no transcript of the proceedings, and no party may make a tape recording of the Mediation Hearing. vii. In order to facilitate a free and open discussion, the Mediation proceeding shall remain confidential. A "Stipulation to Confidentiality" which prohibits future use of settlement offers, all position papers or other statements furnished to the selected mediators, and decisions or recommendations in any Mediation proceeding shall be executed by each party. viii. Upon request of the selected mediators, or one of the parties, BCBSA staff may also submit documentation at any time during the proceedings.

  • Selection Procedure 10.2.4.1 Internal applicants shall be defined as all applicants with seniority in accordance with Article 12.5. 10.2.4.2 In filling a posted vacancy, first consideration shall be given to internal applicants who meet the stated qualifications. All Faculty members who meet the stated qualifications for the posted vacancy shall be interviewed by the Selection Committee. Past service and evaluations shall be considered by the Committee. The best qualified candidate shall be recommended for appointment to the position. 10.2.4.3 Where the qualifications of two or more of the applicants are relatively equal, the applicant with the greatest seniority shall be recommended for appointment to the position. 10.2.4.4 In establishing the qualifications, and in evaluating the qualifications and past performance of the applicants, the committee shall act in good faith, in a fair and reasonable manner, and shall not act in an arbitrary or discriminatory fashion. 10.2.4.5 Following the interviews, the committee will submit its recommendations containing a list of qualified candidates in order of preference, through the appropriate Xxxx to the President or delegate. 10.2.4.6 New faculty members shall be appointed only when there are no qualified internal applicants. 10.2.4.7 If there are no qualified internal applicants, the selection committee may consider external applications, in accordance with the procedure outlined above. 10.2.4.8 Internal applicants will be advised as soon as possible of the selection committee's decision that the committee will be considering external applications in accordance with Article 10.2.4.7.

  • Consultation Procedure If a party hereto is unable to meet the provisions of the Service Level Agreement, or in the event that a dispute arises relating to performance goals set forth in the Service Level Agreement, either party to this Agreement shall address any concerns it may have by requiring a consultation with the other party.

  • Verification Procedure (1) The signature file of each processed file is validated. (2) If processed files are pieces of a bigger file, the latter is put together. (3) Each file obtained in the previous step is then decrypted and uncompressed. (4) Each data file contained in the previous step is then validated against the format defined in Part A, Section 9, reference 1 of this Specification. (5) If Part A, Section 9, reference 1 of this Specification includes a verification process, that will be applied at this step. If any discrepancy is found in any of the steps, the Deposit will be considered incomplete.

  • Application Procedure 7.4.1. Application Priority........................................ 7.4.2. [Reserved].................................................. 7.4.3. Advance Payments............................................

  • Notification Procedure Each such notice shall be deemed to have been delivered: (i) when presented personally to the GOB, (ii) when transmitted by facsimile, or (iii) five (5) Days after being deposited in a regularly maintained receptacle for the postal service in Bangladesh, postage prepaid, registered or certified, return receipt requested, addressed to the GOB, at the address indicated in Section 17 of the Implementation Agreement (or such other address as the GOB may have specified by written notice delivered in accordance therewith). Any notice given by facsimile under this Section 7.5 shall be confirmed in writing delivered personally or sent by prepaid post, but failure to so confirm shall not void or invalidate the original notice if it is in fact received by the GOB.

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

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