Development protocol Sample Clauses

Development protocol. The Trade Unions shall, at their request, be invited for an information meeting with regard to the policy of individual companies that fall under the Collective Agreement. Plantum shall make available for this a list of members. The chairperson and secretary of the Works Council may also be present at this meeting. The information meeting may be related to the following topics: • Sustainable employability vision development; • Employee satisfaction survey; • Preventive medical examinations and health examinations • Training/accreditation of prior learning/career policy; • Job taxation (including travel); • The application of the pay policy for job category H in relation to overtime; • Students becoming familiar with the sector; • Deployment of people with an occupational impairment; • Deployment of temporary workers. The primacy when making agreements on a company level about these topics is with the Works Council except for the last issue.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Development protocol. ‌ The Trade Unions shall, at their request, be invited for an information meeting with regard to the policy of individual companies that fall under the Collective Agreement. Plantum shall make available for this a list of members. The chairperson and secretary of the Works Council may also be present at this meeting. The information meeting may be related to the following topics: • Sustainable employability vision development; • Employee satisfaction survey; • Preventive medical examinations and health examinations • Training/accreditation of prior learning/career policy; • Job taxation (including travel); • The application of the pay policy for job category H in relation to overtime; • Students becoming familiar with the sector; • Deployment of people with an occupational impairment; • Deployment of temporary workers. The primacy when making agreements on a company level about these topics is with the Works Council except for the last issue.
Sample 1

Related to Development protocol

  • 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 Contract Area, including its abandonment.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

Time is Money Join Law Insider Premium to draft better contracts faster.