CONSULTATION PROTOCOL Sample Clauses

CONSULTATION PROTOCOL. Meetings between the University President and the Chapter President shall be held once each month or as the parties agree for the purpose of discussing matters pertinent to the administration of this Agreement or any other mutually agreeable matters. Each party may invite such other persons as they feel necessary to such meetings and shall inform the other party of such persons so invited. The meetings shall be held on a mutually agreeable date in a mutually agreeable location. Such meetings shall not constitute negotiations to alter any or all terms of this Agreement or be used for the purposes of negotiations or discussions of grievances being processed under the grievance procedures of this Agreement. A scheduled meeting may be re-scheduled at any time by agreement of both parties.
AutoNDA by SimpleDocs
CONSULTATION PROTOCOL. 1. If this CAO-OI that the organization or employer makes or can make rules or more specific rules, the obligation to consult applies as determined in the consultation protocol (appendix 4 to this CAO-OI). 2. If this CAO-OI determines that the organization prescribes or can prescribe rules, this will occur in the local consultation, unless expressly provided otherwise. In the local consultation it can be agreed that adoption of these rules is to occur in consultation with the COR. 3. If this CAO determines that the employer prescribes or can prescribe rules, this will occur in consultation with the COR, unless explicitly provided otherwise. 4. If one of the employers establishes a legal entity whose objects are other than the accommodation of core activities and employees enter into employment with the legal entity that is to be established, this is reported to the employee organisations, who can then express their wish to enter into consultation on the terms of employment that are to apply.
CONSULTATION PROTOCOL. 1. If this Collective Labour Agreement determines that the organization /employer prescribes or can prescribe (further) rules, the obligation to consult applies as determined in the consultation protocol (appendix 4 to this Collective Labour Agreement). 2. If this Collective Labour Agreement determines that the organization prescribes or can prescribe rules, this will occur in the local consultation, unless explicitly provided otherwise. With the local consultation it can be agreed that establishment of these rules is to occur in the consultation with the COR. 3. If this Collective Labour Agreement determines that the employer prescribes or can prescribe rules, this will occur in consultation with the COR, unless explicitly provided otherwise. 4. The provision in paragraphs 2 and 3 applies in consideration of what has been determined in the consultation protocol.
CONSULTATION PROTOCOL. Meetings between the University President and the Chapter President shall be held once each month or as the parties agree for the purpose of discussing matters pertinent to the administration of this Agreement or any other mutually agreeable matters. Each party may invite such other persons as they feel necessary to such meetings and shall inform the other party of such persons so invited. The meetings shall be held on a mutually agreeable date in a mutually agreeable location. Such meetings shall not constitute or be used for the purposes of negotiation or discussion of grievances. A scheduled meeting may be re-scheduled at any time by agreement of both parties.
CONSULTATION PROTOCOL. A. Streamlined Review Process for Undertakings Not Affecting Historic Properties. VDOT may employ the process described below for FHWA undertakings that do not affect historic properties involving Categorical Exclusion, Programmatic Categorical Exclusion, or Blanket Categorical Exclusion documentation prepared pursuant to the National Environmental Policy Act (NEPA) and for all undertakings for which USACE or TVA is the lead Federal Agency, subject to the restrictions in Stipulation II.A.5. 1. VDOT shall determine the scope of the undertaking and its area of potential effects (APE), as defined in 36 CFR 800.16(d), with explicit attention to the APE for direct, as well as indirect, alterations to the character or use of historic properties. 2. VDOT shall be responsible for determining the scope of identification efforts and for completing the identification of historic properties within the APE in accordance with 36 CFR 800.4(a) 800.4(b), 800.4(c), the SHPO’s Guidelines for Conducting Historic Resources Survey in Virginia (revised 2011, or subsequent revisions thereto), the Secretary of the Interior’s Standards and Guidelines (Federal Register 48:44716-44742), and 36 CFR 63. 3. VDOT shall be responsible for determining if no historic properties are present or affected by the undertaking. a. If formal field surveys are necessary to make a determination of effect, VDOT shall report the results of its identification efforts to the SHPO in a report or Management Summary, as appropriate, as defined in Stipulation IV (Attachment A) of this Agreement. b. If no formal field surveys are necessary to make a determination of effect, or if VDOT does not identify buildings, structures, districts, objects, or sites 50 years of age or greater, or properties less than 50 years of age but of potential exceptional significance (36 CFR 60.4, Criteria Consideration G) within the undertaking’s APE, VDOT may make a determination of No Historic Properties Affected without waiting for the SHPO to respond to a Management Summary. c. If VDOT conducts a formal field survey and identifies buildings, structures, districts, objects, or sites 50 years of age or greater, or properties less than 50 years of age but of potential exceptional significance (36 CFR 60.4, Criteria Consideration G) within the undertaking’s APE, and a resource’s eligibility for listing on the NRHP must be known in order for VDOT to make a determination of effect, VDOT shall consult with the SHPO to determine the h...
CONSULTATION PROTOCOL. The parties attach great importance to purposeful consultation. Wherever this collective labour agreement (cao) specifies that the employer shall or may draw up (further) rules, the employer is obliged to consult with the employees’ organisations, as laid down in the consultation protocol (Appendix C).
CONSULTATION PROTOCOL. 1. If this CLA determines that the organization /employer prescribes or can prescribe (further) rules, the obligation to consult applies as determined in the consultation protocol (appendix 4 to this CLA). 2. If this CLA determines that the organization prescribes or can prescribe rules, this will occur in the local consultation, unless explicitly provided otherwise. With the local consultation it can be agreed that establishment of these rules is to occur in the consultation with the COR. 3. If this CLA determines that the employer prescribes or can prescribe rules, this will occur in consultation with the COR, unless explicitly provided otherwise. 4. The provision in paragraphs 2 and 3 applies in consideration of what has been determined in the consultation protocol.
AutoNDA by SimpleDocs
CONSULTATION PROTOCOL. Collective decisions are taken upon request from one or several of the Managers. Such decisions can also be taken upon request from one or several of the Partners representing more than half of the capital stock; failing that, by the Managers who shall consult with the Partners eight days after they have delivered a Notice of Intent by registered mail. Decisions are made by written vote. The text of the proposed resolutions is to be sent by Management or by the Partners participating in the consultation, to the last known address of each Partner by registered mail, with an acknowledgement of receipt. It will contain necessary information and explanations, and if it involves approving the financial statement, will include the Managers' Report on Company business and the certified true and accurate statement of profits and losses. Management is obliged to include in the list of resolutions those proposed before the sending of the letters, by one or several Partners representing at least a quarter of the capital stock. Partners must, within twenty full days after the registered letters have been sent, indicate their acceptance or refusal to Management, also by registered mail, with an acknowledgement of receipt. Vote will be taken on each resolution by a "yes" or a "no". Any Partner who has not indicated his response within the time stipulated above will be considered to have abstained. EXHIBIT 10.0 During the above time periods the Partners may demand of the Management any additional explanations they deem useful. Partners' decisions may also be made in a general meeting. A General Meeting may be called by one or several Partners representing more than half of the capital stock, or, failing this, by a Notice of Meeting from the Managers, to be held eight days after sending out a Notice of Intent by registered mail, with an acknowledgement of receipt. The Notice of Meeting shall be sent by registered mail, with an acknowledgement of receipt, addressed to the last known residence of each Partner. The Notice of Meeting shall clearly indicate the reason for the meeting. Management is obliged to put on the Agenda resolutions proposed before the sending of the letters, by one or several Partners representing at least a quarter of the capital stock. The Notice of Meeting must be sent a full fifteen days before the meeting. The General Meeting will be held at Head Office or in any other place in the city where the Head Office is located. The eldest Manager will pres...
CONSULTATION PROTOCOL 

Related to CONSULTATION PROTOCOL

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

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

  • Consultation Services The company hereby employs the consultant to perform the following services in accordance with the terms and conditions set forth in this agreement: The consultant will consult with the officers and employees of the company concerning matters relating to the management and organization of the company, their financial policies, the terms and conditions of employment, and generally any matter arising out of the business affairs of the company.

  • Consultation 10.1 The Employer agrees to consult the Employee timeously where the exercising of its powers will have amongst others- 10.1.1 A direct effect on the performance of any of the Employee’s functions; 10.1.2 Commit the Employee to implement or to give effect to a decision made by the Employer; and 10.1.3 A substantial financial effect on the Employer. 10.2 The Employer agrees to inform the Employee of the outcome of any decisions taken pursuant to the exercise of powers contemplated in clause 12.1 as soon as is practicable to enable the Employee to take any necessary action with delay.

  • Technical Consultations If a Party has a significant concern with respect to food safety, plant health, or animal health, or an SPS measure that the other Party has proposed or implemented, that Party may request technical consultations with the other Party. The Party that is the subject of the request should respond to the request without undue delay. Each Party shall endeavour to provide the information necessary to avoid a disruption to trade and, as the case may be, to reach a mutually acceptable solution.

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

  • Consultations A Party may request in writing consultations with the other Party with respect to any matter referred to in Article 174 (Scope of Application).

  • JOINT CONSULTATION 25.01 The parties acknowledge the mutual benefits to be derived from joint consultation and will consult on matters of common interest. 25.02 The subjects that may be determined as appropriate for joint consultation will be by mutual agreement of the parties. 25.03 Wherever possible, the Council shall consult with representatives of the Professional Institute at the appropriate level about contemplated changes in conditions of employment or working conditions not governed by this Agreement.

  • Purpose of Consultation Procedure The purpose of the consultation procedure is to endeavor to resolve any failure to meet the provisions of the Service Level Agreement. If a consultation occurs under this Section V, all parties must negotiate in good faith to endeavor to: 1. implement changes which will enable the Service Level Agreement provisions to be met – such changes may include, but are not limited to, modification of either or both parties’ respective operational resources; 2. agree to alternative Service Level Agreement provisions which meet the parties’ respective business requirements; or 3. otherwise find a solution such that within a reasonable time after the consultation, the inability to meet the Service Level Agreement provision(s) is reasonably expected to be less likely to occur in the future.

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

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