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.
AGREEMENT MANAGEMENT Pinellas Community Foundation designates the following person(s) as the liaison for the Xxxxxx Xxxxxx, CEO Pinellas Community Foundation
Staff Development The County and the Association agree that the County retains full authority to determine training needs, resources that can be made available, and the method of payment for training authorized by the County. Nothing in this subsection shall preclude the right of an employee to request specific training.
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.
Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;
Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.
Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).
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.
Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5