Cooperation plan and operating specification Sample Clauses

Cooperation plan and operating specification. The Contractor shall prepare or make available a cooperation plan and operating specification prior to the commencement of the approval period. The cooperation plan shall be finalised in consultation with the Customer. The cooperation plan shall contain the routines and procedures necessary for the cooperation between the Customer and the Contractor, including procedures for change handling and procedures for handling undesirable incidents, and shall be based on the cooperation requirements set out by the Customer in Appendices 5 and 6.
AutoNDA by SimpleDocs

Related to Cooperation plan and operating specification

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • Quality Assurance Program An employee shall be entitled to leave of absence without loss of earnings from her or his regularly scheduled working hours for the purpose of writing examinations required by the College of Nurses of Ontario arising out of the Quality Assurance Program.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • Quality Assurance Plan The contractor shall develop and submit to NMFS a contractor Quality Assurance Plan, as referenced in Section F.5.3, which details how the contractor will ensure effectiveness and efficiency of collection efforts as well as the quality of data collected by its At-Sea Monitors. The contractor shall further establish, implement, and maintain a Quality Assurance Management program to ensure consistent quality of all work products and services performed under this contract.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Developer Operating Requirements (a) Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Standard Operating Procedures Over approximately the past eight years, the Parties have been supplying select Products to one another for use in the operation of their respective businesses within the United States of America, Canada and Mexico. The Parties developed and been following certain standard operating procedures in connecting with, among other topics, forecasting, production planning, ordering, delivering and resolving claims on the Products supplied to one another (the “Current SOPs”). The Parties will be updating their respective business systems over the next six months, and the updates to these business systems will require the Parties to modify the Current SOPs. Once the Parties have completed the updates to the business systems and agreed on the necessary modifications to the Current SOPs, the Parties will sign a written amendment to this Agreement appending the updated standard operating procedures (the “Updated SOPs”). Until the Parties have signed a written amendment appending the Updated SOPs, the parties will continue to follow the Current SOPs. The Parties will comply with the applicable SOPs in connection with the purchase and sale of products identified in a Purchase Schedule. The Parties may add terms and conditions to, and amend the terms and conditions of, the SOP in a Purchase Schedule, but any additional and amended terms and conditions in a Purchase Schedule supplementing and modifying the SOP will only apply the specific products identified in that Purchase Schedule for its duration.

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