Collaboration Process Sample Clauses

The Collaboration Process clause defines the procedures and expectations for how parties will work together throughout the duration of their agreement. It typically outlines methods for communication, decision-making, sharing of information, and resolving issues that arise during the collaboration. For example, it may specify regular meetings, designate points of contact, or establish protocols for joint approvals. The core function of this clause is to ensure smooth cooperation and prevent misunderstandings by providing a clear framework for joint activities and interactions.
Collaboration Process. 8.1 Either Party may initiate the development of a new capital project and/or new service it deems to be critical or essential and that may be beneficial to both Parties. Prior to submitting a formal written notice for a new cost-sharing agreement, the initiating Party’s CAO will consult and seek informal support from the other Party’s CAO. 8.2 Once either municipality has received written notice of a new capital project or new service, an Intermunicipal Collaboration Committee meeting must be held within 30 days of the date the written notice was received, unless both ▇▇▇’▇ agree otherwise. 8.3 The Intermunicipal Collaboration Committee will be the forum used to address and develop future Service Agreements and/or cost sharing arrangements. 8.4 Both Parties recognize that the decision to participate in or not participate in a project/arrangement ultimately lies with the respective municipal councils.
View SourceView Similar (4)
Collaboration Process. The collaboration process follows a pre-set number of steps. Despite a fairly standardized process that it is used with all the companies that have enrolled in the IDC program, then work done within these steps is very diverse depending on the unique needs of the enrolled company. This process puts its focus on one step, elaborating short-term measurable actions, but at the same time taking into account what the company has defined in their strategic plans for the long term status and its actual situation. If the company doesn’t have a long term plan or vision, the consortium helps them in the development of such plan. Figure 1: The focus point on the process.
View Source
Collaboration Process. 3.1 The Agreement is a voluntary cooperation between the Parties as individual companies and does not constitute a joint company, joint venture, or other jointly owned legal entity. As such each Party continues to represent and act solely on behalf of their own business. No Party may enter into an agreement with third parties that binds the other Party, unless otherwise specified in a separate written agreement. Decisions relating to the cooperation are made by consensus between the Parties. The Parties are however obligated to accede to decisions as set out in the Agreement. 3.2 Each Party shall designate a contact person who has the necessary authority to act on behalf of the respective Parties with respect to decisions in the cooperation. At present, it is agreed that the contact persons are as follows: Each Party is free to change their contact person with prior written notice of this to the other Party. If a Party has not notified the other Party of any change in the contact person, the Party concerned remains liable for the contact person's actions in the cooperation.
View Source
Collaboration Process. Required in response to the EIR by PAS1192-2 Clause 5.3 a) 5).
View Source
Collaboration Process. The OCP and CoST will have regular check-in and coordination calls (minimum every two months). When possible, members of the two teams will meet in person. In these meetings, the teams will agree on specific next steps, timeframes and, if necessary, resources to implement the collaborations outlined in this agreement. Actions agreed during the meetings will be recorded.
View Source
Collaboration Process. The purpose of this section is to define how, where and when project information will be shared.
View Source
Collaboration Process. The Core Team shall develop a written process governing collaboration between the administrations of the respective parties on the research, investigation and evaluations of site acquisition, design and construction processes of school building projects. The written process shall be provided to the Parties as an information item within 30 days following the approval of this Agreement by both Parties.
View Source
Collaboration Process. Define the process by which the physician assistant and collaborating physician or physicians within the group communicate and make decisions concerning patients’ medical treatment. This process should utilize the knowledge and skills of the physician assistant and the supervising physician based on their respective education, training, and experience. Physician assistants will collaborate with physicians within the group practice based on progressive acquisition and maintenance of medical knowledge, skills, and evidenced based decision making. Collaboration includes access to synchronous and asynchronous communication with a collaborating physician in-person and/or via technology to support acquisition of medical knowledge, skills, and decision making. The on-call physician is also available to the physician assistant in emergency situations. Additionally, physician assistants require physician co-signature per NJH policy (Guidelines for Advanced Practice Providers). Additional requirements are as follows: o New graduate or new to practice physician assistant with less than 5000 hours experience, or less than 3000 hours in new practice area: o Comprehensive evaluation with their collaborating physician at 3, 6, and 12 months, then annually. o Minimum of first 160 hours of practice supervision with collaborating physician in person or via technology. o New graduate physician assistants require physician co-signature of first 75 encounters. o Physician assistants new to a specialty require physician co-signature of first 25 encounters. o Experienced physician assistant with greater than 5000 hours of experience, or greater than 3000 hours in new practice area: o Comprehensive evaluation with their collaborating physician at 6 and 12 months, then annually. o Physician assistants new to NJH require physician co-signature of first 25 encounters.
View Source
Collaboration Process. The collaborative governance process model sometimes describes collaboration as a gradual development (▇▇▇▇▇▇ and ▇▇▇▇, 2007). Or for example, ▇▇▇▇▇▇▇▇ and ▇▇▇▇▇▇▇▇▇▇ (1987:95) describe the consensus building process as having a pre-negotiation phase, a negotiation phase, and an implementation phase; Gray (1989) defines a collaborative process as consisting of three steps, namely: (1) problem setting (2) direction setting, and (3) implementation; and ▇▇▇▇▇▇▇▇▇ (2005:118) identify a three-step process that includes preparation, policy development, and decision making, with each step having several stages. Collaboration at an early stage can positively or negatively affect further collaboration. However, because communication is at the core of collaboration, (▇▇▇▇▇▇ and ▇▇▇▇, 2007) start with:
View Source

Related to Collaboration Process

  • Research Collaboration Upon FibroGen’s request, the Parties will discuss conducting a research program funded by AstraZeneca and directed toward franchise enhancement and lifecycle management for HIF Compounds or other topics that the Parties determine relevant to the Products and the Field. Upon agreement on the terms of such research program, the Parties will enter into a separate agreement or amend this Agreement accordingly.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • Mediation Process A. Mediation is a form of Alternative Dispute Resolution (ADR) that may be requested by the City or the PBA. It is an alternative, not a substitute for the formal arbitration process contained in Section 19.8 above. Mediation is an informal process in which a neutral third party assists the opposing parties in reaching a voluntary, negotiated resolution of a charge of discipline. The decision to mediate is completely voluntary for the PBA and the City. Mediation gives the parties the opportunity to discuss the issues raised in the charging document, clear up misunderstandings, determine the underlying interests or concerns, find areas of agreement and, ultimately, incorporate those areas of agreement into solutions. A mediator does not resolve the charge or impose a decision on the parties. Instead, the mediator helps the parties to agree on a mutually acceptable resolution. The mediation process is strictly confidential. Information disclosed during mediation will not be revealed to anyone. B. If both parties agree, a mediation session conducted by a trained and experienced mediator shall be scheduled at a mutually convenient date and time. Either party may choose to have an attorney represent them during mediation. Persons attending the mediation session shall have the authority to resolve the dispute. If mediation is unsuccessful, the parties may proceed to follow the provisions for Arbitration. Information disclosed during mediation will not be revealed to anyone. C. The parties and, if they desire, their representatives and/or attorneys, are invited to attend a mediation session. No one else may attend without the permission of the parties and the consent of the mediator(s). D. The mediator(s) will not function as the representative of either party. However, the mediator(s) may assist the parties in understanding their rights and the terms of any proposed settlement agreement. Each party acknowledges being advised to seek independent legal review prior to signing any settlement agreement. E. The parties acknowledge that the mediator(s) possesses the discretion to terminate the mediation at any time of any impasse occurs or either party or the mediator deems the case inappropriate for mediation. F. Prior to mediation, both the City and the PBA (or Employee, only in disciplinary matters) shall enter into a confidentiality agreement, as follows: 1. This is an agreement by the parties to participate in a mediation involving the City against the above named employee. The parties understand that mediation is a voluntary process, which may be terminated at any time. 2. The parties agree to participate voluntarily in mediation in an effort to resolve the charge(s) filed by the City. 3. The parties agree that all matters discussed during the mediation are confidential, unless otherwise discoverable, and cannot be used as evidence in any subsequent administrative or judicial proceeding. Confidentiality, however, will not extend to threats of imminent physical harm or incidents of actual violence that occur during the mediation. 4. Any communications between the mediator(s) and/or the parties are considered dispute resolution communications with a neutral and will be kept confidential. 5. The parties agree not to subpoena the mediator(s) or compel the mediator(s) to produce any documents provided by a party in any pending or future administrative or judicial proceeding. The mediator(s) will not voluntarily testify on behalf of a party in any pending or future administrative or judicial proceeding. The parties further agree that the mediator(s) will be held harmless for any claim arising from the mediation process. 6. The parties recognize and agree that the City is subject to Chapter 119, Fla. Stat., relating to public documents. Therefore, all information including all notes, records, or documents generated during the course of the mediation shall be subject to the exemption contained in Section 119.071 (d)(1), Fla. Stats., until the settlement of the matter, or the conclusion of the arbitration, if any, with the exception of the personal notes of the mediator. 7. If a settlement is reached by all the parties, the agreement shall be reduced to writing and when signed shall be binding upon all parties to the agreement, unless the agreement requires City Commission approval, in which case the agreement will not become binding until publicly approved by the City Commission. Said agreement shall be subject to the provisions of Chapter 119, Fla. Stats. If the charge(s) is not resolved through mediation, the parties may proceed to follow the provisions for arbitration.

  • Collaboration activities 4.1 The Collaboration Suppliers will perform the Collaboration Activities and all other obligations of this Agreement in accordance with the Detailed Collaboration Plan. 4.2 The Collaboration Suppliers will provide all additional cooperation and assistance as is reasonably required by the Buyer to ensure the continuous delivery of the services under the Call-Off Contract. 4.3 The Collaboration Suppliers will ensure that their respective subcontractors provide all cooperation and assistance as set out in the Detailed Collaboration Plan.

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