We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Alliance Model Sample Clauses

Alliance Model. 4.1.1 Project model description Project alliance is a project delivery method based on a multi-party contract between the key players in a project whereby the parties assume joint responsibility for the design and construction of the project to be implemented through a joint organization, which includes the owner or client, and where the players share both positive and negative risks related to the project and observe principles of openness in pursuing close cooperation. The basic idea is that risk is borne jointly and reward is shared on the basis of the success of the entire project. This makes the parties take each other’s views into account and collaborate more efficiently for the benefit of the project. The method also allows combination of a wide range of expertise needed to xxxxxx innovation and to make demanding ventures successful. That, again, necessitates early selection of the players and makes offering services at a fixed price impossible. The solution to that challenge is selection based on a thorough review of team performance and capacity. (Lahdenperä & Petäjäniemi 2012) Alliance process model for district refurbishment is in Figure 11. 0 DG1 DG2 DG3 DG4 Value plan KPI-based value profile VALUE BASED PROCUREMENT Value promise Predicted value Assessed value 1. STRATEGY DEVELOPMENT 2. ALLIANCE FORMATION 3. INNOVATION DEVELOPMENT 4. IMPLEMENTATION PHASE 5.GUARANTEE PERIOD Concept development Design Tendering according to competitive dialogue Vision process Funding Refurbishment Strategic planning Evaluation Risk assessment Target setting Target tracking Evaluating innovation development Use-phase performance monitoring Vision and targets Contractual plan Alliance organization NZE NZE district Preliminary procurement strategy Alliance management team Risk plan Assessment Profit / loss sharing between alliance partners Preliminary budget Contractual plan ACTIVATOR PROJECT COORDINATOR OWNERS FINANCER ALLIANCE MANAGEMENT TEAM ALLIANCE PROJECT TEAM AUTHORITY USERS NZE Primary energy Total energy use OER NZE Gentrification profile Gentrification profile End user advantages Assessed EUA Replicability Awareness raising Global warming potential OUTCOME TASKS NO GO NO GO NO GO ACTORS KPIs ECO PR ENV SOC ENE The description of process phases is as follows:

Related to Alliance Model

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones) B. Estimated total development time

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Commercialization Plan At such times as the JGC will deem appropriate, the JGC will direct the Parties to mutually prepare a Worldwide Commercialization Plan, and the JGC will review and approve such initial Worldwide Commercialization Plan. Thereafter, the JGC will have one or the other Party (or both) update the Worldwide Commercialization Plan each calendar year, and the JGC will review and approve any such update or any other amendment to the Worldwide Commercialization Plan. Notwithstanding anything in this CCPS Agreement to the contrary, the Parties acknowledge and agree that (i) Bluebird may decline to perform any Commercialization activity proposed to be conducted by Bluebird in the Worldwide Commercialization Plan (other than Manufacturing of Vectors and associated Payloads), and (ii) the Worldwide Commercialization Plan will not include, and Bluebird will have no obligation to perform, any such Commercialization activity that Bluebird has declined to perform, provided that once Bluebird has agreed to perform a Commercialization activity, it will be obligated to perform, and cannot decline to perform, such activity. In addition, either Party may request at any time that the JGC consider and approve other updates to the Worldwide Commercialization Plan. Further: (a) The JGC will set the required form and contents of the Worldwide Commercialization Plan. The Worldwide Commercialization Plan will reflect a singular marketing and sales approach worldwide, and will specify, among other things, the number of sales reps in the U.S. for each Party, allocation of regions in the U.S. for each Parties’ sales force, creation of marketing materials, planning for conferences, and other marketing activities. CERTAIN CONFIDENTIAL PORTIONS OF THIS EXHIBIT WERE OMITTED AND REPLACED WITH “[***]”. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECRETARY OF THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO AN APPLICATION REQUESTING CONFIDENTIAL TREATMENT PURSUANT TO RULE 406 PROMULGATED UNDER THE SECURITIES ACT OF 1933, AS AMENDED. (b) Neither Party (itself or by or through any others, including any Affiliates or Sublicensees) will take any material action regarding the Commercialization of Licensed Product unless described in the Worldwide Commercialization Plan or approved by the JGC. (c) All Commercialization of Licensed Product for U.S. Administration will be conducted under the supervision of the JGC and as part of the U.S. Development & Commercialization Program. (d) Celgene will have final decision making authority for all Commercialization activities worldwide, including timing of launch and pricing and the Worldwide Development Plan.

  • Alliance Manager Each Party shall appoint a person(s) who shall oversee contact between the Parties for all matters between meetings of each Joint Committee and shall have such other responsibilities as the Parties may agree in writing after the Effective Date (each, an “Alliance Manager”). Each Party may replace its Alliance Manager at any time by notice in writing to the other Party.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Marketing Plan The MCOP shall submit an annual marketing plan to ODM including all planned activities for promoting membership in or increasing awareness of the MCOP. The marketing plan submission shall include an attestation by the MCOP that the plan is accurate and is not intended to mislead, confuse, or defraud the eligible individuals or ODM.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Alliance Managers Promptly following the Effective Date, each Party will designate an alliance manager to be reasonably available to the other Party to facilitate communication, respond to questions and otherwise oversee that the Parties’ activities hereunder are in line with this Agreement. Such alliance managers will regularly interact with each other on a frequency to be mutually agreed by the Parties and on an ad hoc basis if requested by the Joint Project Team or the Project Leaders. A Party may replace its alliance manager at any time by written notice to the other Party.

  • 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

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.