Strategy As an organization without operational services (fuel, maintenance, etc.), and in consideration that the majority of potential issues come from boat maintenance whereby the boats are personal property, the predominant strategy will be the minimization of on-site waste. With this approach, the organization will have minimal potential impact on the environment and reduce regulatory risk. To accomplish this, requirements will be established by policy, periodic communications shall occur, and audits will be utilized to provide feedback for improvement.
Negotiation Teams The Board and the Association shall each designate in writing, at the first negotiation session, the names of not more than five (5) persons who shall serve as their respective representatives for negotiation pursuant to the provisions of this Agreement. Each party shall also designate the person on its team who will serve as spokesperson.
Strategies The ESC will seek to achieve employment stability strategies as follows: - current and multi-year strategies should be developed within the resources available. Such strategies could include, but not necessarily be limited to, planning, retraining, identifying ways of determining employees= skills, training and experience previously achieved, early retirement, voluntary exit programs, alternative assignment, secondment, employee career counselling, job sharing, job trading, job shadowing, and professional development; - discussions between the parties which explore these possible strategies would assist in the development of appropriate enhancements to Employment Stability; - data which is relevant to employment stability shall be made available to both parties.
Product Development (a) Supplier may develop enhancements it intends to incorporate into the BioGlue Surgical Adhesive during the term of this Agreement that have potential application to the Company Product (“Enhancements”). Unless otherwise agreed by the parties, at least once every six months during the Term, representatives of each of BioForm and Supplier shall hold a meeting in accordance with Sections 4.4 and 8.4 (the “Product Development Meeting”) at which Supplier will present Enhancements for BioForm to consider for application to the Company Product. At such Product Development Meeting, BioForm will also present its marketing plans (pursuant to Section 4.4) for the period and any information or feedback that BioForm reasonably believes may lead to Improvements. Within 30 calendar days following each Product Development Meeting, Supplier shall deliver a notice to BioForm (the “Enhancements Notice”) that shall describe the Enhancements that were presented by Supplier at such Product Development Meeting. Within 30 calendar days following receipt of the Enhancements Notice, BioForm may notify Supplier in writing if BioForm elects that any Enhancement described in the Enhancements Notice shall become an Improvement. If BioForm does provide such notice to Supplier during such 30-calendar day period, then BioForm and Supplier shall agree on a timeline for implementation of the Improvement in new Product Specifications for Company Product. If BioForm does not provide such a notice, said Enhancement shall not be implemented into the Company Product. The Enhancements Notice may also describe any potential Enhancements presented by Supplier at the Product Development Meeting, but BioForm shall not be required to take any action under this Section 8.4 with respect to such potential Enhancements until such time as they are presented by Supplier as Enhancements at a future Product Development Meeting. All Enhancements and potential Enhancement information provided by Supplier shall be considered Supplier Confidential Information. (b) From time to time, each party may request the other party to participate in joint projects to develop Improvements. Neither party is obligated to participate in such projects, and in each **** Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. instance, each party’s decision whether to participate will be made in such party’s sole discretion. If both parties mutually agree to participate in such a project (a “Program”), the parties will promptly prepare a mutually agreeable written development agreement specifying the development activities to be performed by and the research and development tasks assigned to each party (the “Development Agreement”). All allocation of Intellectual Property rights with respect to any Program will be set forth in writing in the Development Agreement. (c) In the absence of a Development Agreement, (i) BioForm and Supplier shall retain joint ownership of Intellectual Property rights in which there is joint inventorship by BioForm (or its Affiliates) and Supplier, as determined in accordance with United States patent law, with Supplier’s rights in such joint ownership being subject to the license rights of BioForm under this Agreement, (ii) any Intellectual Property rights related to the Company Products, Enhancements, and Improvements that are created solely by employees or consultants of Supplier during the Term shall be considered to be Intellectual Property rights of Supplier, subject to the license rights of BioForm under this Agreement, and (iii) any Intellectual Property rights related to the Company Products and Improvements that are created solely by employees or consultants of BioForm or any of its Affiliates during the Term shall be considered to be Intellectual Property rights of BioForm. BioForm hereby grants to Supplier a perpetual, royalty free, world-wide, nonexclusive license to Supplier under such Blocking Intellectual Property to make, use, and sell such Intellectual Property outside the Field. “Blocking Intellectual Property” for the purposes of Section 8.4(c)(iii) shall mean Intellectual Property necessary for Supplier to make, use, or sell SA Product.
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.
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).
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.
Marketing Vendor agrees to allow TIPS to use their name and logo within the TIPS website, database, marketing materials, and advertisements unless Vendor negotiates this term to include a specific acceptable-use directive. Any use of TIPS’ name and logo or any form of publicity, inclusive of press release, regarding this Agreement by Vendor must have prior approval from TIPS which will not be unreasonably withheld. Request may be made by email to xxxx@xxxx-xxx.xxx. For marketing efforts directed to TIPS Members, Vendor must request and execute a separate Joint Marketing Disclaimer, at xxxxxxxxx@xxxx-xxx.xxx, before TIPS can release contact information for TIPS Member entities for the purpose of marketing your TIPS contract(s). Vendor must adhere to strict Marketing Requirements once a disclaimer is executed. The Joint Marketing Disclaimer is a supplemental agreement specific to joint marketing efforts and has no effect on the terms of the TIPS Vendor Agreement. Vendor agrees that any images, photos, writing, audio, clip art, music, or any other intellectual property (“Property”) or Vendor Data utilized, provided, or approved by Vendor during the course of the joint marketing efforts are either the exclusive property of Vendor, or Vendor has all necessary rights, license, and permissions to utilize said Property in the joint marketing efforts. Vendor agrees that they shall indemnify and hold harmless TIPS and its employees, officers, agents, representatives, contractors, assignees, designees, and TIPS Members from any and all claims, damages, and judgments involving infringement of patent, copyright, trade secrets, trade or services marks, and any other intellectual or intangible property rights and/or claims arising from the Vendor’s (including Vendor’s officers’, employees’, agents’, Authorized Resellers’, subcontractors’, licensees’, or invitees’) unauthorized use or distribution of Vendor Data and Property.
Commercialization Intrexon shall have the right to develop and Commercialize the Reverted Products itself or with one or more Third Parties, and shall have the right, without obligation to Fibrocell, to take any such actions in connection with such activities as Intrexon (or its designee), at its discretion, deems appropriate.
NEGOTIATIONS PROCEDURES 3.1 The Board and SEE shall each exchange, in writing, at the first negotiations session, the names of persons who shall serve as their respective representatives for negotiations, up to ten (10). Each party shall also designate the person on its team who will serve as spokesperson. Other persons may be permitted to attend negotiation sessions for resource purposes upon prior mutual agreement of the parties. (revised 2012-13) 3.2 No later than April 15 of each ensuing year, either SEE or the Board shall submit a written request for negotiations to commence to the other party, if it desires there to be negotiations for that year. If no such request is made during the time period above, negotiations will not take place for the ensuing year. (revised 2012-13) 3.3 The first negotiation session shall occur on a mutually agreeable date. (revised 2012-13) 3.4 The Board and SEE shall share their initial written concerns at least one week prior to scheduled negotiations. Subsequent initial concerns may only be submitted upon mutual agreement of the parties. (revised 2012-13) 3.5 Only those members who comprise the negotiation teams will be present in the room during negotiations except for the OEA advocate and clerical assistance. Other parties may be permitted to be present only by mutual agreement of the parties. (revised 2012-13) 3.6 Negotiations shall be conducted in closed sessions. No recordings or official transcripts shall be made without mutual agreement of the parties. 3.7 Negotiations will only be conducted between the designated representatives of the parties and only in regular negotiations sessions at the times, dates, and places mutually agreed upon by the parties. The time, date, place and agenda of subsequent sessions will be set by mutual agreement of the parties prior to the close of each negotiations session. 3.8 Negotiations sessions shall be scheduled outside the regular work day of the representatives of the bargaining unit, except by mutual agreement. 3.9 Releases to the news media will be by mutual agreement only. However, neither the Board nor SEE shall be prohibited from communicating with its own members. 3.10 When tentative agreement is reached on any item, it shall be reduced to writing, and signed and dated by the spokesperson of each team. When tentative agreement is reached on all items, they shall be submitted first as a package by SEE to the bargaining unit for ratification and then by the Superintendent to the Board for ratification.