Authority and Compliance Borrower has full power and authority to execute and deliver the Loan Documents and to incur and perform the obligations provided for therein, all of which have been duly authorized by all proper and necessary action of the appropriate governing body of Borrower. No consent or approval of any public authority or other third party is required as a condition to the validity of any Loan Document, and Borrower is in compliance with all laws and regulatory requirements to which it is subject.
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.
Financial Viability and Regulatory Compliance 2.6.1 Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. Contractor further warrants and represents that it owes no outstanding delinquent federal, state or local taxes or business assessments. 2.6.2 Contractor agrees to promptly disclose to the MPHA any IRS liens or licensure suspension or revocation that may adversely affect its capacity to perform the services outlined within this contract. The failure by Contractor to disclose such issue to the MPHA in writing within 5 days of such notification received will constitute a material breach of this contract. 2.6.3 Contractor further agrees to promptly disclose to the MPHA any change of more than 50% of its ownership and/or any declaration of bankruptcy that Contractor may undergo during the term(s) of this contract. The failure of Contractor to disclose any change of more than 50% of its ownership and/or its declaration of bankruptcy within 5 days of said actions shall constitute a material breach of this contract. 2.6.4 All disclosures made pursuant to this section of the contract shall be made in writing and submitted to MPHA within the time periods required herein.
Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. 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(s), 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.
Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.
AUTHORITY AND PARTIES In accordance with the National Aeronautics and Space Act (51 U.S.C. § 20113), this Agreement is entered into by the National Aeronautics and Space Administration, located at 000 X Xxxxxx XX, Xxxxxxxxxx, XX 00000 (hereinafter referred to as "NASA") and Xxxxxx Space Systems, Inc., located at 0000 Xxxxxxxx Xx., Xxxxxx, XX 00000 (hereinafter referred to as "Partner" or "Xxxxxx"). NASA and Partner may be individually referred to as a "Party" and collectively referred to as the "Parties."
Information for Regulatory Compliance Each of the Company and the Depositary shall provide to the other, as promptly as practicable, information from its records or otherwise available to it that is reasonably requested by the other to permit the other to comply with applicable law or requirements of governmental or regulatory authorities.
Compliance Audits D. 4.1 Compliance Audit(s). Without limiting the generality of section A.7.4 (Records Review), if requested by the Province from time to time, which request shall be at the Province’s sole discretion, the Recipient, at its own expense, will forthwith retain an independent third party auditor to conduct one or more compliance audits of the Recipient or any Project. The audit will be conducted in accordance with Canadian Generally Accepted Auditing Standards, as adopted by the Canadian Institute of Chartered Accountants, applicable as of the date on which a record is kept or required to be kept under such standards. In addition, the audit will assess the Recipient’s compliance with the terms of the Agreement and will address, with respect to each Project, without limitation, the following: (a) whether the Funds were spent in accordance with the Agreement and with due regard to economy, efficiency, and effectiveness; (b) the Project’s progress or state of completion; (c) whether the financial information the Recipient provided is complete, accurate, and timely, and in accordance with the Agreement; (d) whether the Recipient’s information and monitoring processes and systems are adequate to identify, capture, validate, and monitor the achievement of intended benefits of the Project; (e) the overall management and administration of the Project; (f) recommendations for improvement or redress; and (g) whether prompt and timely corrective action is taken on prior audit findings.
FUND COMPLIANCE 3.1 The Fund and the Adviser acknowledge that any failure (whether intentional or in good faith or otherwise) to comply with the requirements of Subchapter M of the Code or the diversification requirements of Section 817(h) of the Code may result in the Contracts not being treated as variable contracts for federal income tax purposes, which would have adverse tax consequences for Contract owners and could also adversely affect the Company's corporate tax liability. The Fund and the Adviser further acknowledge that any such failure may result in costs and expenses being incurred by the Company in obtaining whatever regulatory authorizations are required to substitute shares of another investment company for those of the failed Fund or as well as fees and expenses of legal counsel and other advisors to the Company and any federal income taxes, interest or tax penalties incurred by the Company in connection with any such failure. 3.2 The Fund represents and warrants that it is currently qualified as a Regulated Investment Company under Subchapter M of the Code, and that it will maintain such qualification (under Subchapter M or any successor or similar provision) and that it will notify the Company immediately upon having a reasonable basis for believing that it has ceased to so qualify or that it might not so qualify in the future. 3.3 The Fund represents that it will at all times invest money from the Contracts in such a manner as to ensure that the Contracts will be treated as variable contracts under the Code and the regulations issued thereunder; including, but not limited to, that the Fund will at all times comply with Section 817(h) of the Code and Treasury Regulation 1.817-5, as amended from time to time, relating to the diversification requirements for variable annuity, endowment, or life insurance contracts, and with Section 817(d) of the Code, relating to the definition of a variable contract, and any amendments or other modifications to such Section or Regulation. The Fund will notify the Company immediately upon having a reasonable basis for believing that the Fund or a Portfolio thereunder has ceased to comply with the diversification requirements or that the Fund or Portfolio might not comply with the diversification requirements in the future. In the event of a breach of this representation by the Fund, it will take all reasonable steps to adequately diversify the Fund so as to achieve compliance within the grace period afforded by Treasury Regulation 1.817-5. 3.4 The Adviser agrees to provide the Company with a certificate or statement indicating compliance by each Portfolio of the Fund with Section 817(h) of the Code, such certificate or statement to be sent to the Company no later than thirty (30) days following the end of each calendar quarter.
Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
