Non-Publication The parties mutually agree not to disclose publicly the terms of this Agreement except to the extent that disclosure is mandated by applicable law or regulation or to their respective advisors (e.g., attorneys, accountants).
RESEARCH AND PUBLICATION 29 CONTRACTOR shall not utilize information and/or data received from COUNTY, or arising out 30 of, or developed, as a result of this Agreement for the purpose of personal or professional research, or 31 for publication. 32
Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
REJECTION OF GOODS Notwithstanding any other rights of, or remedies available to UNDP under the Contract, in case any of the Goods are defective or otherwise do not conform to the specifications or other requirements of the Contract, UNDP, at its sole option, may reject or refuse to accept the Goods, and within thirty (30) days following receipt of notice from UNDP of such rejection or refusal to accept the Goods, the Contractor shall, in sole option of UNDP: 11.7.1 provide a full refund upon return of the Goods, or a partial refund upon a return of a portion of the Goods, by UNDP; or, 11.7.2 repair the Goods in a manner that would enable the Goods to conform to the specifications or other requirements of the Contract; or, 11.7.3 replace the Goods with Goods of equal or better quality; and, 11.7.4 pay all costs relating to the repair or return of the defective Goods as well as the costs relating to the storage of any such defective Goods and for the delivery of any replacement Goods to UNDP.
Inspection of Goods 8.1 The Buyer shall inspect the goods upon delivery. 8.2 Where goods are damaged the Buyer shall notify the Supplier. The Buyer may reject the damaged goods and the following provisions shall apply: 8.2.1 the Supplier shall collect the damaged goods from the Buyer at the Supplier’s expense; 8.2.2 during the period between delivery of the goods to the Buyer and collection by the Supplier, the Buyer shall not be liable for any loss or further damage caused to the damaged goods; 8.2.3 all sums payable by the Buyer in relation to the damaged goods shall cease to become payable; 8.2.4 all sums paid by the Buyer in relation to the damaged goods shall be repaid by the Supplier immediately; 8.2.5 the Buyer shall be entitled to claim damages from the Supplier for any losses caused to the Buyer as a result of the goods being damaged. 8.3 Where there are shortages in the order the Buyer shall notify the Supplier and the following provisions shall apply: 8.3.1 all sums payable by the Buyer in relation to the missing goods shall cease to become payable; 8.3.2 all sums paid by the Buyer in relation to the missing goods shall be repaid by the Supplier immediately; 8.3.3 the Buyer shall be entitled to claim damages from the Supplier for any losses caused to the Buyer as a result of the shortages. 8.4 If the Buyer so requests, the Supplier shall immediately replace damaged goods or supply goods which are missing at the Supplier’s expense or the Buyer shall be entitled to cancel, without notice, the whole or any unexecuted part of the order and the rights referred to in Clause 5.2 shall apply. 8.5 Where there is an excess of goods in relation to the order the Buyer may reject the excess goods by notice in writing to the Supplier and the following provisions shall apply: 8.5.1 the Supplier shall collect the excess goods from the Buyer at the Supplier’s expense; 8.5.2 during the period between delivery of the goods and collection by the Supplier, the Buyer shall not be liable for any loss or damage caused to the excess goods; 8.5.3 no sum shall be due to the Supplier for the excess goods and in the event that sums are paid to the Supplier for the excess goods, the Supplier shall repay such sums to the Buyer immediately. 8.6 The Buyer may accept excess goods by notifying the Supplier of such acceptance and the price of the excess goods shall be payable by the Buyer. 8.7 The Supplier shall repair or replace free of charge, goods damaged or lost in transit upon receiving notice to that effect from the Buyer. 8.8 The Buyer’s signature on any delivery note of the Supplier is evidence of the number of packages received only and not evidence of the correct quantity of goods received or that the goods are in a good condition or of the correct quality.
Technical Standards The Generation System shall be installed and operated by the Interconnection Customer consistent with the requirements of this Agreement; the Technical Requirements; the applicable requirements located in the National Electrical Code (NEC); the applicable standards published by the American National Standards Institute (ANSI) and the Institute of Electrical and Electronic Engineers (IEEE); and local building and other applicable ordinances in effect at the time of the installation of the Generation System.
Governing Law, Regulatory Authority, and Rules The validity, interpretation and enforcement of this Agreement and each of its provisions shall be governed by the laws of the state of New York, without regard to its conflicts of law principles. This Agreement is subject to all Applicable Laws and Regulations. Each Party expressly reserves the right to seek changes in, appeal, or otherwise contest any laws, orders, or regulations of a Governmental Authority.
General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.
Release of Goods 1. Each Party shall adopt or maintain simplified customs procedures for the efficient release of goods in order to facilitate trade between the Parties. 2. Pursuant to paragraph 1, each Party shall adopt or maintain procedures that: (a) provide for the immediate release of goods upon receipt of the customs declaration and fulfillment of all applicable requirements and procedures; (b) provide for the electronic submission and processing of documentation and data, including manifests, in advance of the arrival of the goods in order to expedite the release of goods from customs control upon arrival; (c) allow goods to be released at the point of arrival without requiring temporary transfer to warehouses or other facilities; and (d) require that the importer be informed if a Party does not promptly release goods, including, to the extent permitted by its law, the reasons why the goods are not released and which border agency, if not the customs administration, has withheld release of the goods. 3. Each Party shall adopt or maintain procedures that provide for the release of goods prior to a final determination and payment of any customs duties, taxes, fees, and charges imposed on or in connection with importation of the goods, when these are not determined prior to or promptly upon arrival, provided that the goods are otherwise eligible for release and any security required by the importing Party has been provided. 4. If a Party allows for the release of goods conditioned ona security, it shall adopt or maintain procedures that: (a) ensure that the amount of the security is no greater than that required to ensure that obligations arising from the importation of the goods will be fulfilled; (b) ensure that the security shall be discharged as soon as possible after its customs administration is satisfied that the obligations arising from the importation of the goods have been fulfilled or, for instruments covering multiple entries, until it is no longer required by the customs administration; and (c) allow an importer to provide security using a non-cash financial instrument, including, if applicable, when an importer frequently enters goods, an instrument covering multiple entries. 5. Nothing in this Article requires a Party to release a good if its requirements for release have not been met nor prevents a Party from liquidating a security in accordance with its law. 6. Each Party shall allow, to the extent practicable, goods intended for import to be moved within its territory under customs control from the point of entry into the Party's territory to another customs office in its territory from where the goods are intended to be released, provided the applicable regulatory requirements are met.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.
