Suspension or Debarment Instructions Instructions for Certification 1. By answering yes to the next Attribute question below, the vendor and prospective lower tier participant is providing the certification set out herein in accordance with these instructions.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
SOURCE OF INSTRUCTIONS The Contractor shall neither seek nor accept instructions from any authority external to UNDP in connection with the performance of its services under this Contract. The Contractor shall refrain from any action that may adversely affect UNDP or the United Nations and shall fulfill its commitments with the fullest regard to the interests of UNDP.
Use of Attachment Facilities by Third Parties Purpose of Attachment Facilities. Except as may be required by Applicable Laws and Regulations, or as otherwise agreed to among the Parties, the Attachment Facilities shall be constructed for the sole purpose of interconnecting the Large Generating Facility to the New York State Transmission System and shall be used for no other purpose.
Certification of Public Information Holdings and each Lender acknowledge that certain of the Lenders may be “public-side” Lenders (Lenders that do not wish to receive material non-public information with respect to Holdings, its Subsidiaries or their securities) and, if documents or notices required to be delivered pursuant to this Section 5.01 or otherwise are being distributed through IntraLinks/IntraAgency, SyndTrak or another relevant website or other information platform (the “Platform”), any document or notice that Holdings has indicated contains Non-Public Information shall not be posted on that portion of the Platform designated for such public-side Lenders. Holdings agrees to clearly designate all Information provided to the Administrative Agent by or on behalf of Holdings which is suitable to make available to Public Lenders. If Holdings has not indicated whether a document or notice delivered pursuant to this Section 5.01 contains Non-Public Information, the Administrative Agent reserves the right to post such document or notice solely on that portion of the Platform designated for Lenders who wish to receive material non-public information with respect to Holdings, its Subsidiaries and their securities;
Form of Instructions Instructions to restrict or prohibit trading must include the TIN, ITIN, or GII, if known, and the specific restriction(s) to be executed. If the TIN, ITIN, or GII is not known, the instructions must include an equivalent identifying number of the Shareholder(s) or account(s) or other agreed upon information to which the instruction relates.
Acting on Instructions; Unclear Instructions (a) Bank is authorized to act under this Agreement (or to refrain from taking action) in accordance with the instructions received by Bank, via telephone, telex, facsimile transmission, or other teleprocess or electronic instruction or trade information system acceptable to Bank ("Instructions"). Bank shall have no responsibility for the authenticity or propriety of any Instructions that Bank believes in good faith to have been given by Authorized Persons or which are transmitted with proper testing or authentication pursuant to terms and conditions that Bank may specify. Customer authorizes Bank to accept and act upon any Instructions received by it without inquiry. Customer shall indemnify the Bank Indemnitees against, and hold each of them harmless from, any Liabilities that may be imposed on, incurred by, or asserted against the Bank Indemnitees as a result of any action or omission taken in accordance with any Instructions or other directions upon which Bank is authorized to rely under the terms of this Agreement, provided that Bank shall not be indemnified against or held harmless from any Liabilities arising out of Bank's negligence, bad faith, fraud, or willful misconduct.
(b) Unless otherwise expressly provided, all Instructions shall continue in full force and effect until canceled or superseded.
(c) Bank may (in its sole discretion and without affecting any part of this Section 3.1) seek clarification or confirmation of an Instruction from an Authorized Person and may decline to act upon an Instruction if it does not receive clarification or confirmation satisfactory to it. Bank shall not, except as provided in Section 7.1 hereof, be liable for any loss arising from any delay while it seeks such clarification or confirmation.
(d) In executing or paying a payment order Bank may rely upon the identifying number (e.g. Fedwire routing number or account) of any party as instructed in the payment order. Customer assumes full responsibility for any inconsistency within an Instruction between the name and identifying number of any party in payment orders issued to Bank in Customer's name.
Form of Instruction Each Instruction shall be transmitted by such secured or authenticated electro-mechanical means as the Custodian shall make available to the Fund from time to time unless the Fund shall elect to transmit such Instruction in accordance with Subsections 4.2.1 through 4.2.3 of this Section.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
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.
