Coordination Process Sample Clauses

The Coordination Process clause establishes the procedures and responsibilities for parties to communicate, collaborate, and synchronize their activities throughout the course of a project or agreement. Typically, this clause outlines how meetings will be scheduled, how information will be shared, and who will serve as the primary points of contact between the parties. By setting clear expectations for coordination, the clause helps prevent misunderstandings, ensures timely decision-making, and facilitates smooth project execution.
Coordination Process. The goal of Flint’s coordination process is to achieve an LOD 350 model at time of submission to the AHJ. This requires three (3) distinct phases of coordination which are listed below. Project specific collaboration procedures are further defined in section H of the Project BIM execution plan.
View SourceView Similar (4)
Coordination Process. The Contractor shall assign one lead individual, with the authority to obligate the contractor, to be responsible for communications with the Government for overall contract administration. This individual must be available 24 hours / day and respond to Government inquiries within two (2) hours. The Contractor shall assign one lead individual for each DO who shall coordinate all aspects of the job with the designated Government representative and vice versa. The Contractor’s designated representative will keep the Government's representative apprised of schedule, technical, material and financial issues pertaining to the order. The designated “lead individual” for the IDIQ-MAC and individual DOs may be the same employee as long as all contract and DO-level requirements are met. All communication with other Government organizations, Commands and Departments shall be via the Contracting Officer unless otherwise authorized. The Contractor’s employees shall not visit vessels or military activity associated with a DO without prior approval from the Contracting Officer or Project Manager. All visits shall be coordinated by the Government Maintenance Team.
View SourceView Similar (2)
Coordination Process. 5.1 Slot-requests based on historical rights from the corresponding previous season, will be allocated during initial coordination. 5.2 Slot series which cannot be confirmed during initial coordination will be put on a waiting list. 5.3 According to the availability, all other slot-series will be allocated on a provisional basis and without entitlement for historical rights after the IATA SC. 5.4 Night slots that are not based on historic rights will be confirmed with - Action code “T” and - Status information tag “NIGHTRESTR” in the Score database, subject to availability. 5.5 The priorities for the allocation from the night flight pool are as follows: a) Extensions of existing slot series holding historical rights (also single flights, the extension itself does not create historical rights) b) Slot series having been confirmed in the corresponding previous season c) New slot series 5.6 Requests for single flights will be accepted and provisionally coordinated only after the Historics Baseline Date for the relevant season. 5.7 Slot requests for GA/BA flights are accepted maximum 28 days ahead of the planned operation. 5.8 For each season a waitlist will be maintained of all outstanding requests. This waitlist will be reviewed regularly to replenish any slot capacity available by cancellations or changes. Criterions for the waitlist-handling are number of frequency, extensions of already coordinated slot series, sequence of requests, etc.
View SourceView Similar (2)
Coordination Process. SCAG shall engage in a consultative process with VCTC and Transit Operators in accordance with applicable federal and state laws and regulations, and successors thereto, pertaining to the roles and responsibilities of the Parties in metropolitan transportation planning. a. SCAG shall provide timely notice of the opportunity to comment on its Draft RTP and Draft FTIP to the parties and the opportunity to participate in Overall Work Program development. b. SCAG shall continue maintaining the Regional Transit Technical Advisory Committee or a successor group, to provide a forum for VCTC, other CTCs, and Transit Operators, to participate in the metropolitan transportation planning process. c. VCTC agrees to participate in SCAG's Technical Working Group or any successor group established to serve the same function which shall also serve as a forum to ensure that local transportation projects, plans and programs are effectively integrated into the RTP and FTIP updates. d. The Executive Officers of SCAG and the CTCs shall continue to meet regularly to ensure executive coordination of regional/county/local transportation issues, including issues regarding transit coordination. e. VCTC shall ensure that Transit Operators’ plans, programs, studies and other issues are integrated into the county and regional transportation planning process. VCTC shall provide Transit Operators the opportunity to propose projects for inclusion in VCTC's TIP and CMP. Projects and programs adopted by the VCTC in the Ventura County TIP and CMP shall be submitted to SCAG and recommended for inclusion in the FTIP and RTP, respectively. f. The Parties shall cooperatively develop an annual listing of projects for which funds under 23 U.S.C. or 49 U.S.C. Chapter 53 were obligated in the preceding program year, in accordance with 23 CFR 450.334. g. The Parties shall cooperatively develop estimates of funds that will be available to support RTP implementation, and reasonable financial principles and information that support revenue and cost estimates, to be used in the RTP and FTIP financial plan, in accordance with 23 CFR 450.324(f)(11). h. The Parties agree to collaborate to implement federal performance reporting and performance-based planning provisions in accordance with 23 CFR 450.306(d)(2)(iii), and subject to applicable final rulemaking. The Parties further agree to coordinate to the maximum extent practicable in the selection of performance targets, and will cooperatively develop and s...
View SourceView Similar (2)
Coordination Process. C.14.1. The Contractor shall assign one separate dedicated Contractor Lead Project Manager as a single point of contact for each delivery order and this person shall coordinate all aspects of the delivery order with the designated Government representative and vice versa. The Contactor Lead Project Manager will keep Government representatives apprised of schedule, technical, material and financial concerns pertaining to the delivery order.
View Source
Coordination Process. 2.1 The Parties agree to establish a process, as set forth in this section, for coordinating the development of proposed standards, in accordance with the principles in Section 1 of this MOU. 2.2 The JIC shall be responsible for the coordination process. The JIC shall be composed of representatives from NERC holding one-third of the votes, representatives from NAESB WEQ holding one-third of the votes and representatives from the ISO/RTO Council holding one-third of the votes. Each Party will determine its representatives to the JIC, with every effort to have each segment or area represented. The quorum necessary for the transaction of business at meetings of the JIC shall require a majority of the representatives of each of any two Parties. Any or all members of the JIC may participate in a meeting, including being counted as part of the quorum, by means of a communication system by which all persons participating in the meeting are able to hear each other. Use of notational balloting or proxies will not be permitted. NERC, NAESB and the ISO/RTO Council will separately determine whether designated alternates will be permitted to participate in place of their absent JIC representatives. The JIC will have co-chairs, one representing NERC, one representing NAESB, and one representing the ISO/RTO Council chosen by each Party from among its JIC representatives. 2.3 Decisions of the JIC will be by a simple majority of all votes cast, with each NERC representative present at a meeting having a vote equal to 33.3% divided by the number of NERC representatives participating in the meeting, each NAESB representative having a vote equal to 33.3% divided by the number of NAESB representatives participating in the meeting, and each ISO/RTO Council representative having a vote equal to 33.3% divided by the number of ISO/RTO Council representatives participating in the meeting. In the event any Party fails to be represented by at least one representative and quorum requirements are met, the remaining two Parties shall each receive 50% of the vote, to be divided equally among the Party’s representatives. In the event of a tie vote, the matter will be referred to the Chairmen of the Parties present for the tie vote [or their Board level designee(s)] for resolution. In the determinations made under Section 2.6, each Party may abstain from voting on any question in which it determines it does not have a material interest. 4 The Parties expressly agree that reliability and bu...
View Source
Coordination Process. The Contractor shall assign one lead individual, with the authority to obligate the Contractor, to be responsible for communications with the Government for overall contract administration. This individual must be available 24 hours / day and respond to Government inquiries within two (2) hours. The Contractor shall assign one lead individual for each DO who shall coordinate all aspects of the job with the designated Government representative and vice versa. The Contractor’s designated representative will keep the Government's representative apprised of schedule, technical, material and financial issues pertaining to the order. The designated “lead individual” for the IDIQ-MAC and individual DOs may be the same employee as long as all contract and DO-level requirements are met. All communication with any Government organizations shall be via the Contracting Officer or the Contracting Officer’s Representative (COR) unless otherwise authorized. All visits shall be coordinated by the Government Maintenance Team.
View Source

Related to Coordination Process

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

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

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

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.