Parties to the Process Sample Clauses

Parties to the Process a) There shall be established a Central Dispute Resolution Committee (“The Committee”), which shall be composed of equal representation of up to four (4) representatives each of the employer bargaining agency and employee bargaining agency (“the central parties”), and up to three representatives of the Crown. The Committee will be co-chaired by a representative from each bargaining agency. All correspondence to the committee will be sent to both co-chairs. b) The Central Parties and the Crown will provide a written list of representatives appointed to the Committee with contact information every September. Any changes in representation will be confirmed in writing. c) A local party shall not be party to the CDRP, or to the Committee, except to the extent its interests are represented by its respective central party on the Committee. d) For the purposes of this section, “central party” means an employer bargaining agency or employee bargaining agency, and “local party” means an employer or trade union party to a local collective agreement.
Sample 1Sample 2Sample 3See All (114)
Parties to the Process a) There shall be established a Central Dispute Resolution Committee (“The Committee”), which shall be composed of equal representation of up to four
Sample 1Sample 2Sample 3See All (47)
Parties to the Process a) There shall be established a Central Dispute Resolution Committee (“The Committee”), which shall be composed of equal representation of up to four (4) representatives each of the employer bargaining agency and employee bargaining agency (“the central parties”), and up to three representatives of the Crown. The Committee will be co-chaired by a representative from each bargaining agency. All correspondence to the committee will be sent to both co-chairs. b) The Central Parties and the Crown will provide a written list of representatives appointed to the Committee with contact information every September. Any changes in representation will be confirmed in writing. c) A local party shall not be party to the CDRP, or to the Committee, except to the extent its interests are represented by its respective central party on the Committee.
Sample 1Sample 2Sample 3See All (5)
Parties to the Process a) There shall be established a Central Dispute Resolution Committee (“The Committee”), which shall be composed of equal representation of up to four (4) representatives each of the employer bargaining agency and employee bargaining agency (“the central parties”), and up to three representatives of the Crown. The Committee will be co-chaired by a representative from each bargaining agency. All correspondence to the committee will be sent to both co-chairs. b) The Central Parties and the Crown will provide a written list of representatives appointed to the Committee with contact information every September. Any changes in representation will be confirmed in writing.
Sample 1

Related to Parties to the Process

  • Details of the Processing The subject-matter of Processing of Personal Data by Data Processor is the performance of the Services pursuant to the Agreement. The duration of the Processing, the nature and purpose of the Processing, as well as the types of Personal Data Processed and categories of Data Subjects under this DPA are further specified in Schedule 1 (Details of the Processing) to this DPA.

  • Consultative Process This Agreement recognises a commitment of the parties to develop working arrangements which will bring success to the operations of the Company through the ability to implement flexible work arrangements to meet the requirements of customers and the personal, study or family commitments of employees.

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

  • Nature of the processing MailChimp provides an email service, automation and marketing platform and other related services, as described in the Agreement.

  • Scope of the Procurement II.1.1) Title

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

  • Steps of the Procedure A grievance regarding a dispute over contract interpretation shall be filed at the lowest step in the grievance procedure in which the City’s representative would have the authority to make a final and binding resolution of the grievance, provided, however, that a grievance may not be filed at a Step higher than Step 2, except by mutual agreement of the parties. In the event a grievance is filed at a Step in the grievance procedure which the City deems inappropriate, the City’s representative with whom the grievance was filed shall remand the grievance to the appropriate Step.

  • Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.

  • Duration of the Processing Personal Data will be Processed for the duration of the Agreement, subject to Section 4 of this DPA.

  • Execution of the Project (a) The Borrower declares its commitment to the objectives of the Project as set forth in Schedule 2 to this Agreement, and, to this end, shall carry out the Project through the Directorate General of Community Empowerment of its Ministry of Home Affairs with due diligence and efficiency and in conformity with appropriate administrative, agricultural, engineering, and financial practices and sound environmental and social standards acceptable to the Association, and shall provide, promptly as needed, the funds, facilities, services and other resources required for the Project. (b) Without limitation upon the provisions of paragraph (a) of this Section and except as the Borrower and the Association shall otherwise agree, the Borrower shall carry out the Project in accordance with the Implementation Program set forth in Schedule 4 to this Agreement. (a) Except as the Association shall otherwise agree, procurement of the goods, works and services required for the Project and to be financed out of the proceeds of the Credit shall be governed by the provisions of Schedule 3 to this Agreement, as said provisions may be further elaborated in the Procurement Plan. (b) The Borrower shall update the Procurement Plan in accordance with guidelines acceptable to the Association, and furnish such update to the Association not later than twelve (12) months after the date of the preceding Procurement Plan, for the Association’s approval. Section 3.03. For the purposes of Section 9.06 of the General Conditions and without limitation thereto, the Borrower shall: (a) prepare, on the basis of guidelines acceptable to the Association, and furnish to the Association not later than six (6) months after the Closing Date or such later date as may be agreed for this purpose between the Borrower and the Association, a plan designed to ensure the continued achievement of the objectives of the Project; and (b) afford the Association a reasonable opportunity to exchange views with the Borrower on said plan.