Common use of System Infrastructure for Electronic Document Exchange Clause in Contracts

System Infrastructure for Electronic Document Exchange. a. Each party will provide hardware, operating system(s) software, internet, e-mail, and large file transfer functions (“System Infrastructure”) at its own cost and sufficient for complying with the EDP requirements. With the exception of minimum standards set forth in this EDP, and any explicit system requirements specified by attachment to this EDP, it is the obligation of each party to determine, for itself, its own System Infrastructure. 1) The maximum size of an email attachment for exchange of Electronic Documents under this EDP is [number] 20.0 MB. Attachments larger than that may be exchanged using large file transfer functions or physical media. 2) Each Party assumes full and complete responsibility for any and all of its own costs, delays, deficiencies, and errors associated with converting, translating, updating, verifying, licensing, or otherwise enabling its System Infrastructure, including operating systems and software, for use with respect to this EDP. b. Each party is responsible for its own system operations, security, back-up, archiving, audits, printing resources, and other Information Technology (“IT”) for maintaining operations of its System Infrastructure during the Project, including coordination with the party’s individual(s) or entity responsible for managing its System Infrastructure and capable of addressing routine communications and other IT issues affecting the exchange of Electronic Documents. c. Each party will operate and maintain industry-standard, industry-accepted, ISO standard, commercial-grade security software and systems that are intended to protect the other party from: software viruses and other malicious software like worms, trojans, ransomware, adware; data breaches; loss of confidentiality; and other threats in the transmission to or storage of information from the other parties, including transmission of Electronic Documents by physical media such as CD/DVD/flash drive/hard drive. To the extent that a party maintains and operates such security software and systems, it shall not be liable to the other party for any breach of system security. d. In the case of disputes, conflicts, or modifications to the EDP required to address issues affecting System Infrastructure, the parties shall cooperatively resolve the issues; but, failing resolution, the Owner is authorized to make and require reasonable and necessary changes to the EDP to effectuate its original intent. If the changes cause additional cost or time to ▇▇▇▇, not reasonably anticipated under the original EDP, ▇▇▇▇ may seek an adjustment in price or time under the appropriate process in the Contract. e. Each party is responsible for its own back-up and archive of documents sent and received during the term of the contract under this EDP, unless this EDP establishes a Project document archive, either as part of a mandatory Project website or other communications protocol, upon which the parties may rely for document archiving during the specified term of operation of such Project document archive. Further, each party remains solely responsible for its own post-project back-up and archive of Project documents after the term of the Contract, or after termination of the Project document archive, if one is established, for as long as required by the Contract and as each party deems necessary for its own purposes. f. If a receiving party receives an obviously corrupted, damaged, or unreadable Electronic Document, the receiving party will advise the sending party of the incomplete transmission. g. The parties will bring any non-conforming Electronic Documents into compliance with the EDP. The parties will attempt to complete a successful transmission of the Electronic Document or use an alternative delivery method to complete the communication. h. The Owner will operate a project information management system (also referred to in this EDP as “Project Website”) for use of Owner, OA, Engineer, and ▇▇▇▇ during the Project for exchange and storage of Project-related communications and information. Except as otherwise provided in this EDP or the General Conditions, use of the Project Website by the parties as described in this Paragraph will be mandatory for exchange of Project documents, communications, submittals, and other Project-related information. The following conditions and standards will govern use of the Project Website: 1) Describe the period of time during which the Project Website will be operated and be available for reliance by the parties; 2) Provide any minimum system infrastructure, software licensing and security standards for access to and use of the Project Website; 3) Describe the types and extent of services to be provided at the Project Website, such as large file transfer, email, communication, and document archives, etc.; and 4) Include any other Project Website attributes that may be pertinent to ▇▇▇▇’▇ use of the facility and pricing of such use.

System Infrastructure for Electronic Document Exchange. a. Each party will provide hardware, operating system(s) software, internet, e-mail, and large file transfer functions (“"System Infrastructure”") at its own cost and sufficient for complying with the EDP requirements. With the exception of minimum standards set forth in this EDP, EDP and any explicit system requirements specified by attachment to this EDP, it is will be the obligation of each party to determine, for itself, its own System Infrastructure. 1) The maximum size of an email e-mail attachment for exchange of Electronic Documents under this EDP is [number] 20.0 10 MB. Attachments larger than that may be exchanged using large file transfer functions or physical media. 2) Each Party assumes full and complete responsibility for any and all of its own costs, delays, deficiencies, and errors associated with converting, translating, updating, verifying, licensing, or otherwise enabling its System Infrastructure, including operating systems and software, for use with respect to this EDP. b. Each party is responsible for its own system operations, security, back-up, archiving, audits, printing resources, and other Information Technology (“"IT”") for maintaining operations of its System Infrastructure during the Project, including coordination with the party’s 's individual(s) or entity responsible for managing its System Infrastructure and capable of addressing routine communications and other IT issues affecting the exchange of Electronic Documents. c. Each party will operate and maintain industry-standard, industry-accepted, ISO ISO- standard, commercial-grade security software and systems that are intended to protect the other party from: software viruses and other malicious software like worms, trojans, ransomware, adware; data breaches; loss of confidentiality; and other threats in the transmission to or storage of information from the other parties, including transmission of Electronic Documents by physical media such as CD/DVD/flash drive/hard drive. To the extent that a party maintains and operates such security software and systems, it shall will not be liable to the other party for any breach of system security. d. In the case of disputes, conflicts, or modifications to the EDP required to address issues affecting System Infrastructure, the parties shall will cooperatively resolve the issues; but, failing resolution, the Owner is authorized to make and require reasonable and necessary changes to the EDP to effectuate its original intent. If the changes cause additional cost or time to ▇▇▇▇Engineer, not reasonably anticipated under the original EDP, ▇▇▇▇ may seek an adjustment in price Engineer shall be entitled to compensation as Additional Services for its costs associated with the revisions to the EDP, delayed adoption of Exhibit L or time under the appropriate process in the Contractimplementation of other Electronic Documents protocols. e. Each party is responsible for its own back-up and archive of documents sent and received during the term of the contract any Project contract/agreement under this EDP, unless this EDP establishes a Project document archive, either as part of a mandatory Project website or other communications protocol, upon which the parties Parties may rely for document archiving during the specified term of operation of such Project project document archive. Further, each party remains solely responsible for its own post-project post- Project back-up and archive of Project documents after the term of the Contractproject documents, or after termination of the Project document archive, if one is established, for as long as required by the Contract and as each party deems necessary for its own purposes, after the term of contract, or termination of the project document archive, if one is established. f. If a receiving party receives an obviously corrupted, damaged, or unreadable Electronic Document, the receiving party will advise the sending party of the incomplete transmission. g. The parties will bring any non-conforming Electronic Documents into compliance with the EDP. The parties will attempt to complete a successful transmission of the Electronic Document or use an alternative delivery method to complete the communication. h. The Owner will operate a project information management system (also referred to in this EDP as “Project Website”) for use of Owner, OA, Engineer, and ▇▇▇▇ during the Project for exchange and storage of Project-related communications and information. Except as otherwise provided in this EDP or the General Conditions, use of the Project Website by the parties as described in this Paragraph will be mandatory for exchange of Project documents, communications, submittals, and other Project-related information. The following conditions and standards will govern use of the Project Website: 1) Describe the period of time during which the Project Website will be operated and be available for reliance by the parties; 2) Provide any minimum system infrastructure, software licensing and security standards for access to and use of the Project Website; 3) Describe the types and extent of services to be provided at the Project Website, such as large file transfer, email, communication, and document archives, etc.; and 4) Include any other Project Website attributes that may be pertinent to ▇▇▇▇’▇ use of the facility and pricing of such use.