Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).
Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.
Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.
Electronic Delivery of Certain Information Each Guarantor acknowledges and agrees that information regarding the Guarantor may be delivered electronically pursuant to Section 8.5. of the Credit Agreement.
Filing of Amendments; Response to Commission Requests The Company will promptly advise the Representatives of any proposal to amend or supplement at any time the Initial Registration Statement, any Additional Registration Statement or any Statutory Prospectus and will not effect such amendment or supplementation without the Representatives’ consent; and the Company will also advise the Representatives promptly of (i) the effectiveness of any Additional Registration Statement (if its Effective Time is subsequent to the execution and delivery of this Agreement), (ii) any amendment or supplementation of a Registration Statement or any Statutory Prospectus, (iii) any request by the Commission or its staff for any amendment to any Registration Statement, for any supplement to any Statutory Prospectus or for any additional information, (iv) the institution by the Commission of any stop order proceedings in respect of a Registration Statement or the threatening of any proceeding for that purpose, and (v) the receipt by the Company of any notification with respect to the suspension of the qualification of the Offered Securities in any jurisdiction or the institution or threatening of any proceedings for such purpose. The Company will use its best efforts to prevent the issuance of any such stop order or the suspension of any such qualification and, if issued, to obtain as soon as possible the withdrawal thereof.
REPORT SUBMISSION 1. Copies of reporting packages for audits conducted in accordance with 2 CFR Part 200, Subpart F-Audit Requirements, and required by PART I of this form shall be submitted, when required by 2 CFR 200.512, by or on behalf of the recipient directly to the Federal Audit Clearinghouse (FAC) as provided in 2 CFR 200.36 and 200.512 A. The Federal Audit Clearinghouse designated in 2 CFR §200.501(a) (the number of copies required by 2 CFR §200.501(a) should be submitted to the Federal Audit Clearinghouse), at the following address: Federal Audit Clearinghouse Bureau of the Census 0000 Xxxx 00xx Xxxxxx Xxxxxxxxxxxxxx, XX 00000 Submissions of the Single Audit reporting package for fiscal periods ending on or after January 1, 2008, must be submitted using the Federal Clearinghouse’s Internet Data Entry System which can be found at xxxx://xxxxxxxxx.xxxxxx.xxx/facweb/ 2. Copies of financial reporting packages required by PART II of this Attachment shall be submitted by or on behalf of the recipient directly to each of the following: A. The Department of Environmental Protection at one of the following addresses: By Mail: Florida Department of Environmental Protection Office of Inspector General, MS 40 0000 Xxxxxxxxxxxx Xxxxxxxxx Tallahassee, Florida 32399-3000 Electronically: XXXXXxxxxxXxxxx@xxx.xxxxx.xx.xx B. The Auditor General’s Office at the following address: Auditor General Local Government Audits/342 Xxxxxx Xxxxxx Building, Room 000 000 Xxxx Xxxxxxx Xxxxxx Xxxxxxxxxxx, Xxxxxxx 00000-1450 The Auditor General’s website (xxxx://xxxxxxxxx.xxx/) provides instructions for filing an electronic copy of a financial reporting package. 3. Copies of reports or management letters required by PART III of this Attachment shall be submitted by or on behalf of the recipient directly to the Department of Environmental Protection at one of the following addresses: By Mail: Florida Department of Environmental Protection Office of Inspector General, MS 40 0000 Xxxxxxxxxxxx Xxxxxxxxx Tallahassee, Florida 32399-3000 Electronically: XXXXXxxxxxXxxxx@xxx.xxxxx.xx.xx 4. Any reports, management letters, or other information required to be submitted to the Department of Environmental Protection pursuant to this Agreement shall be submitted timely in accordance with 2 CFR 200.512, section 215.97, F.S., and Chapters 10.550 (local governmental entities) or 10.650 (nonprofit and for-profit organizations), Rules of the Auditor General, as applicable. 5. Recipients, when submitting financial reporting packages to the Department of Environmental Protection for audits done in accordance with 2 CFR 200, Subpart F-Audit Requirements, or Chapters 10.550 (local governmental entities) and 10.650 (non and for-profit organizations), Rules of the Auditor General, should indicate the date and the reporting package was delivered to the recipient correspondence accompanying the reporting package.
SUBMISSION OF REPORTS All applicable study reports shall be submitted in preliminary form for approval by the State before a final report is issued. The State's comments on the Engineer's preliminary report must be addressed in the final report.
NOTIFICATIONS AND SUBMISSION OF REPORTS Unless otherwise stated in writing after the Effective Date, all notifications and reports required under this IA shall be submitted to the following entities: Administrative and Civil Remedies Branch Office of Counsel to the Inspector General Office of Inspector General U.S. Department of Health and Human Services Xxxxx Building, Room 5527 000 Xxxxxxxxxxxx Xxxxxx, XX Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 Facsimile: (000) 000-0000 LFAC: Xxxxxxx X. Xxxxx, DPM 0000 Xxxxxxxxxxx Xx. X-000 Xxxxxxxxx, XX 00000 Telephone: (000) 000-0000 Email: xx.xxxxx@xxxxx.xxx Unless otherwise specified, all notifications and reports required by this IA may be made by electronic mail, overnight mail, hand delivery, or other means, provided that there is proof that such notification was received. Upon request by OIG, LFAC may be required to provide OIG with an additional copy of each notification or report required by this IA in OIG’s requested format (electronic or paper).
Electronic Execution; Electronic Records; Counterparts This Agreement, any Loan Document and any other Communication, including Communications required to be in writing, may be in the form of an Electronic Record and may be executed using Electronic Signatures. Each of the Loan Parties and each of the Administrative Agent and each Lender Party agrees that any Electronic Signature on or associated with any Communication shall be valid and binding on such Person to the same extent as a manual, original signature, and that any Communication entered into by Electronic Signature, will constitute the legal, valid and binding obligation of such Person enforceable against such Person in accordance with the terms thereof to the same extent as if a manually executed original signature was delivered. Any Communication may be executed in as many counterparts as necessary or convenient, including both paper and electronic counterparts, but all such counterparts are one and the same Communication. For the avoidance of doubt, the authorization under this paragraph may include, without limitation, use or acceptance of a manually signed paper Communication which has been converted into electronic form (such as scanned into PDF format), or an electronically signed Communication converted into another format, for transmission, delivery and/or retention. The Administrative Agent and each of the Lender Parties may, at its option, create one or more copies of any Communication in the form of an imaged Electronic Record (“Electronic Copy”), which shall be deemed created in the ordinary course of such Person’s business, and destroy the original paper document. All Communications in the form of an Electronic Record, including an Electronic Copy, shall be considered an original for all purposes, and shall have the same legal effect, validity and enforceability as a paper record. Notwithstanding anything contained herein to the contrary, neither the Administrative Agent, L/C Issuer nor Swing Line Lender is under any obligation to accept an Electronic Signature in any form or in any format unless expressly agreed to by such Person pursuant to procedures approved by it; provided, further, without limiting the foregoing, (a) to the extent the Administrative Agent, L/C Issuer and/or Swing Line Lender has agreed to accept such Electronic Signature, the Administrative Agent and each of the Lender Parties shall be entitled to rely on any such Electronic Signature purportedly given by or on behalf of any Loan Party and/or any Lender Party without further verification and (b) upon the request of the Administrative Agent or any Lender Party, any Electronic Signature shall be promptly followed by such manually executed counterpart. Neither the Administrative Agent, L/C Issuer nor Swing Line Lender shall be responsible for or have any duty to ascertain or inquire into the sufficiency, validity, enforceability, effectiveness or genuineness of any Loan Document or any other agreement, instrument or document (including, for the avoidance of doubt, in connection with the Administrative Agent’s, L/C Issuer’s or Swing Line Lender’s reliance on any Electronic Signature transmitted by telecopy, emailed .pdf or any other electronic means). The Administrative Agent, L/C Issuer and Swing Line Lender shall be entitled to rely on, and shall incur no liability under or in respect of this Agreement or any other Loan Document by acting upon, any Communication (which writing may be a fax, any electronic message, Internet or intranet website posting or other distribution or signed using an Electronic Signature) or any statement made to it orally or by telephone and believed by it to be genuine and signed or sent or otherwise authenticated (whether or not such Person in fact meets the requirements set forth in the Loan Documents for being the maker thereof). Each of the Loan Parties and each Lender Party hereby waives (i) any argument, defense or right to contest the legal effect, validity or enforceability of this Agreement, any other Loan Document based solely on the lack of paper original copies of this Agreement, such other Loan Document, and (ii) waives any claim against the Administrative Agent, each Lender Party and each Related Party for any liabilities arising solely from the Administrative Agent’s and/or any Lender Party’s reliance on or use of Electronic Signatures, including any liabilities arising as a result of the failure of the Loan Parties to use any available security measures in connection with the execution, delivery or transmission of any Electronic Signature.
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.
