COOPERATIVE FRAMEWORK Sample Clauses

COOPERATIVE FRAMEWORK. Consistent with the terms and conditions of this MOU, the Parties will coordinate, to the maximum extent practicable, their regulatory responsibilities related to the secure transportation of radioactive materials that pose a significant risk to public health and safety and the environment or the common defense and security. The Parties recognize that the topical areas set forth in Attachment 1 of this MOU are important to development and deployment of an enhanced security strategy for the transportation of risk significant radioactive material in the U.S. and across U.S. borders. For the purposes of this MOU, the term “risk significant radioactive material” means radioactive material that requires security measures to be applied to it above prudent management practices. See e.g., the International Atomic Energy Agency’s Nuclear Security Recommendations on Physical Protection of Nuclear Material and Nuclear Facilities (Information Circular/225/Revision 5). In addition, the Parties will agree on the radioactive material, within the statutory and regulatory jurisdiction of a Party, for implementation under this MOU, on a case-by-case basis. Attachment 1 of the MOU describes the infrastructure of the desired interactions between the Parties to this MOU. A series of annexes will be developed after approval of the MOU to establish the working arrangements between the NRC and the relevant component agencies within the signatory Departments. Working arrangements will provide the details of these interactions.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
COOPERATIVE FRAMEWORK. 3.1 All communication between the PSDOs may use email, including electronic circulation of executed PDF documents. However, all legally binding communications must be explicitly acknowledged with an email from each PSDO to become effective. 3.2 The PSDOs will establish a Liaison Work Group (LWG) that any member of any PSDO may attend. The LWG is responsible for drafting the Specification and may accept contributions from any participating member of any PSDO. 3.3 The LWG shall have agreed logistical resources, governance and decision making protocols defined in the Working Group Guidelines in Attachment A. 3.4 All work products and draft specifications of the LWG shall be confidential information and may only be distributed to the PSDOs and their membership. 3.5 Each attending member will state its PSDO affiliation at the beginning of each LWG meeting and that affiliation shall be recorded in the minutes. If a member belongs to more than one PSDO it may choose to state affiliation to one or more PSDOs. 3.6 Each PSDO may enable individual members to opt-out of participation in the LWG and hence any IP licensing commitments under that affiliation. A list of members that have opted-out from participation in affiliation with a PSDO will be made available at the LWG. Members that opt-out may not attend LWG meetings under that affiliation. If they do attend any meeting under an affiliation they are deemed to immediately be participant members and subject to IP licensing commitments under that affiliation until the next ratification by that PSDO. 3.7 The IP being licensed under each PSDO’s IP framework shall not be listed or discussed at the LWG. 3.8 Each PSDO may enable individual members to exclude specific patents from a licensing obligation by issuing an IP Disclosure, as outlined in Attachment B, that are handled by the working group processes in attachment A. Multi-SDO Specification Liaison Memorandum of Understanding Oct12 DRAFT nt3 1 3.9 Once the LWG has created a final Specification draft, each PSDO shall consider ratification of the Specification under its individual IP framework. The LWG shall set a ratification review period of sufficient length to enable all PSDOs to comply with their internal ratification procedures. Once all PSDOs have confirmed individual ratification, the specification can be released publicly by any PSDO. 3.10 If any PSDO is unable to ratify a draft specification the LWG will attempt to redraft the specification until all PSDOs c...
Sample 1
COOPERATIVE FRAMEWORK. Item 2. Set up Project Leading Group To seek for unified leadership and smooth implementation of the project, Party A is responsible to set up "Train TV Project Leading Group of the Ministry of Railway". Item 3. Establish Cooperative Management Institution Under the leadership of the Project Leading Group, the two parties co-establish the cooperative management institution named as "Train TV Department of China Railway Scientific and Technological Development Company" (hereinafter referred to as Train TV Dept.). The two parties will jointly register a company when the project operates into a large scale. The Train TV Department is responsible for the planning, design, installation, management, advertisement sales, etc of the project. Party A shall appoint the General Manager of the Train TV Department and Party B the Deputy General Manager. The involved "Management Agreement " and "Advertisement Agent Agreement" signed between Party A's subsidiaries "China Railway Cable TV Station" and "China Railway HongYuan Advertisement Company" in the progress of the project are attachments of this agreement.
Sample 1

Related to COOPERATIVE FRAMEWORK

  • Legal Framework 1. This programme agreement shall be read in conjunction with the following documents which, together with this programme agreement, constitute the legal framework of the EEA Financial Mechanism 2014-2021: (a) Protocol 38c to the EEA Agreement on the EEA Financial Mechanism 2014-2021; (b) the Regulation on the implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “Regulation”) issued by the Donor States in accordance with Article 10(5) of Protocol 38c; (c) the Memorandum of Understanding on the Implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “MoU”), entered into between the Donor States and the Beneficiary State; and (d) any guidelines adopted by the FMC in accordance with the Regulation. 2. In case of an inconsistency between this programme agreement and the Regulation, the Regulation shall prevail. 3. The legal framework is binding for the Parties. An act or omission by a Party to this programme agreement that is incompatible with the legal framework constitutes a breach of this programme agreement by that Party.

  • Economic Cooperation 1. The Parties will encourage the utilization of cooperation instruments and mechanisms with a view to strengthen the processes of economic integration and commercial exchange. 2. The objectives of economic cooperation will be: (a) to build on existing agreements or arrangements already in place for trade and economic cooperation; and (b) to advance and strengthen trade and economic relations between the Parties. 3. The Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) dialogue about policies and regular exchanges of information and views on ways to promote and expand trade in goods and services between the Parties; (b) joint elaboration of studies and technical projects of economic interest according to the economic development needs identified by the Parties; (c) keeping each other informed of important economic and trade issues, and any impediments to furthering their economic cooperation; (d) providing assistance and facilities to business persons and trade missions that visit the other Party with the knowledge and support of the relevant agencies; (e) supporting dialogue and exchanges of experience among the respective business communities of the Parties; (f) establishing and developing mechanisms for providing information and identifying opportunities for business cooperation, trade in goods and services, investment, and government procurement; and (g) stimulating and facilitating actions of public and/or private sectors in areas of economic interest.

  • Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Procurement All goods, works and services required for the Project and to be financed out of the proceeds of the Financing shall be procured in accordance with the provisions of Section III of Schedule 2 to the Financing Agreement.

  • Emergency Replacement SAP may replace a Subprocessor without advance notice where the reason for the change is outside of SAP’s reasonable control and prompt replacement is required for security or other urgent reasons. In this case, SAP will inform Customer of the replacement Subprocessor as soon as possible following its appointment. Section 6.3 applies accordingly.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles: (a) Such schedules shall be established by mutual agreement of the Home and the Union; (b) These schedules may pertain to full-time and/or part-time employees; (c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations; (d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules; (e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis. (f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!