System Infrastructure for Electronic Document Exchange Clause Samples

The 'System Infrastructure for Electronic Document Exchange' clause defines the requirements and standards for the technological systems used to facilitate the secure and efficient exchange of electronic documents between parties. It typically outlines the necessary hardware, software, and network protocols that must be in place, and may specify responsibilities for maintaining system compatibility and data integrity. By establishing clear expectations for the electronic infrastructure, this clause ensures reliable communication, reduces the risk of technical disputes, and supports the seamless execution of electronic transactions.
System Infrastructure for Electronic Document Exchange. 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 will be the obligation of each party to determine, for itself, its own System Infrastructure.
View SourceView Similar (2)
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 ▇...
View SourceView Similar (2)
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 will be the obligation of each party to determine, for itself, its own System Infrastructure. 1) The maximum size of an e-mail attachment for exchange of Electronic Documents under this EDP may vary due to e-mail protocols established by the Owner, Engineer, or Contractor. Attachments larger than the e-mail size limits set by any of the parties to this agreement shall 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, 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 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 will cooperatively resolve the issues; but, failing resolution, the Owner is authorized to make and require reasonabl...
View Source

Related to System Infrastructure for Electronic Document Exchange

  • Electronic Documents We may make periodic statements, disclosures, notices, and other documents available to you electronically, and, subject to any delivery and receipt verification procedures required by law, you agree to receive such documents electronically and to check the statements for accuracy. If you believe any such statement contains incorrect information, you must follow the procedures set forth in the Related Agreement(s).

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Electronic Record Search The Reporting Finnish Financial Institution must review electronically searchable data maintained by the Reporting Finnish Financial Institution for any of the following U.S. indicia: a) Identification of the Account Holder as a U.S. citizen or resident; b) Unambiguous indication of a U.S. place of birth; c) Current U.S. mailing or residence address (including a U.S. post office box); d) Current U.S. telephone number; e) Standing instructions to transfer funds to an account maintained in the United States; f) Currently effective power of attorney or signatory authority granted to a person with a U.S. address; or g) An “in-care-of” or “hold mail” address that is the sole address the Reporting Finnish Financial Institution has on file for the Account Holder. In the case of a Preexisting Individual Account that is a Lower Value Account, an “in-care-of” address outside the United States or “hold mail” address shall not be treated as U.S. indicia.

  • WASHINGTON’S ELECTRONIC BUSINESS SOLUTION (WEBS). Contractor represents and warrants that Contractor is registered in Washington’s Electronic Business Solution (WEBS), Washington’s contract registration system and that, all of Contractor’s information therein is current and accurate and that throughout the term of this Contract, Contractor shall maintain an accurate profile in WEBS.

  • ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇.▇▇/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.