Contents of Agreement This Agreement, together with the other Transaction Documents, sets forth the entire understanding of the parties hereto with respect to the Transactions and supersedes all prior agreements or understandings among the parties regarding those matters.
Contents of Notice The notice of each Member meeting shall include a description of the purpose(s) for which the meeting is called. If a purpose of any Member meeting is to consider: (i) a proposed amendment to or restatement of the Articles requiring Member approval; (ii) a plan of merger or share exchange; (iii) the sale, lease, exchange or other disposition of all, or substantially all of the Company’s Property; (iv) the dissolution of the Company; or (v) removal of a Governor, then the notice must so state and must be accompanied, as applicable, by a copy or summary of the (1) amendment(s) to the Articles, (2) plan of merger or share exchange, (3) documents relating to the transaction for the disposition of all the Company’s property, and/or (4) plan and Articles of Dissolution.
Requirements of Rights-of-Way Pur- chaser’s road construction and use of rights-of-way identi- fied in attached list or C5.11 shall be confined to rights-of- way and limited by the related easements and stipula- tions, if any, unless Purchaser makes other arrangements that will not infringe upon or adversely affect the grantee’s rights. Easements or right-of-way documents are avail- able in the offices of the Forest Supervisor and District Ranger.
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. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. 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.
PAYMENT AND INVOICE PROVISIONS An itemized invoice addressed to the ordering entity shall reference purchase order number, contract number, quantity, description, list and net unit price. Installation/Labor and any other ancillary charges will be shown as a separate line item on all quotes and invoices. Payment will be made in accordance with applicable State of Arkansas accounting procedures upon acceptance by the Agency. The State may not be invoiced in advance of delivery and acceptance of any commodity. Payment will be made only after the contractor has successfully satisfied the state agency as to the goods purchased. Contractor should invoice agency by an itemized list of charges. Purchase Order Number and/or Contract Number should be referenced on each invoice.
Exclusion of applications on preliminary points of law Any recourse to any Court for the determination of a preliminary point of law arising in the course of the arbitration proceedings is excluded.
Additional Procedures Applicable to High Value Accounts 1. If a Preexisting Individual Account is a High Value Account as of December 31, 2013, the Reporting [FATCA Partner] Financial Institution must complete the enhanced review procedures described in paragraph D of this section with respect to such account by December 31, 2014. If based on this review, such account is identified as a U.S. Reportable Account, the Reporting [FATCA Partner] Financial Institution must report the required information about such account with respect to 2013 and 2014 in the first report on the Account. For all subsequent years, information about the account should be reported on an annual basis.
Open and Transparent Consistent with ICANN’s expressed mission and core values, ICANN shall operate in an open and transparent manner.
Data Protection Impact Assessment and Prior Consultation Processor shall provide reasonable assistance to the Company with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Company reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Company Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.
USE OF TBS ACCESS CODE (a) An Account Holder may operate the TBS in relation to his Account by using his TBS Access Code.
