Software Requirements for Electronic Document Exchange Clause Samples

The 'Software Requirements for Electronic Document Exchange' clause defines the technical standards and specifications that software must meet to facilitate the secure and effective exchange of electronic documents between parties. This clause typically outlines the required file formats, compatibility with certain platforms or systems, and any necessary security protocols, such as encryption or authentication measures. By establishing these requirements, the clause ensures interoperability, reduces the risk of technical issues, and promotes the smooth and reliable transfer of documents in electronic form.
Software Requirements for Electronic Document Exchange. Limitations 1. Each party will acquire the software necessary to create and transmit and read Electronic Documents received from the other party (and if relevant from third parties). 2. Software and data formats for exchange of Electronic Documents will conform to the requirements set forth in the following Attachment 1 to this EDP, including software version, if listed. Item Electronic Documents Transmittal Means Data Format Note (1) a.1 General communications, transmittal covers, meeting notices, and responses to general information requests for which there is no specific prescribed form. Email EML
View SourceView Similar (3)
Software Requirements for Electronic Document Exchange. Limitations 1. Each party will acquire the software and software licenses necessary to create and transmit Electronic Documents and to read and to use any Electronic Documents received from the other party (and if relevant from third parties), using the software formats required in this section of the EDP. a. Prior to using any updated version of the software required in this section for sending Electronic Documents to the other party, the originating party will first notify and receive concurrence from the other party for use of the updated version or adjust its transmission to comply with this EDP. 2. The parties agree not to intentionally edit, reverse engineer, decrypt, remove security or encryption features, or convert to another format for modification purposes any Electronic Document or information contained therein that was transmitted in a software data format, including Portable Document Format (PDF), intended by sender not to be modified, unless the receiving party obtains the permission of the sending party or is citing or quoting excerpts of the Electronic Document for Project purposes. 3. Software and data formats for exchange of Electronic Documents will conform to the requirements set forth in the following Attachment 1 to this EDP, including software version, if listed.
View SourceView Similar (3)
Software Requirements for Electronic Document Exchange. Item Electronic Documents Transmittal Means Data Format Note (1) a.1 General communications, transmittal covers, meeting notices, and responses to general information requests for which there is no specific prescribed form. Email Email
View Source
Software Requirements for Electronic Document Exchange. Item Electronic Documents Transmittal Means Data Format Note (1) a.1 General communications, transmittal covers, meeting notices, and responses to general information requests for which there is no specific prescribed form. Email EML a.2 Meeting agendas; meeting minutes; RFI’s and Responses to RFI’s; and Construction Contract administrative forms. Email w/ Attach PDF (2) a.3 Contractor’s Submittals (Shop Drawings, “Or Equal” requests, Substitute requests, documentation accompanying Sample submittals and other Submittals) to Owner and ▇▇▇▇▇; and Owner’s and ▇▇▇▇▇’▇ Responses to Contractor’s Submittals, Shop Drawings, Correspondence, and Applications for Payment Email w/ Attach PDF a.4 Correspondence; Interim and Final Versions of reports, layouts, Specifications, Drawings, maps, calculations and spreadsheets, Construction Contract, Bidding/Proposal Documents, and Front- End Construction Contract Documents. Email w/ Attach or LFE PDF (3) a.5 Layouts, plans, maps, and Drawings to be submitted to Owner by ▇▇▇▇▇ for future use and modification Email w/ Attach or LFE DWG a.6 Correspondence, reports, and specifications to be submitted by ▇▇▇▇▇ to Owner for future word processing use and modification Email w/ Attach or LFE DOC DOCX a.7 Spreadsheets and data to be submitted to Owner by ▇▇▇▇▇ for future data processing use and modification ▇▇▇▇▇ can PDF any Spreadsheet. Email w/ Attach or LFE XLS XLSX a.8 Images Email w/ Attach JPG JPEG GIF PNG TIFF BMP a.9 Compressed Files Email w/ Attach ZIP Agreement Owner: City of Bellbrook, OH Page 20 of 30 Exhibits: A, C, E, GP, IR Tank No: ▇▇-▇▇-▇▇-▇▇
View Source
Software Requirements for Electronic Document Exchange. Limitations
View Source

Related to Software Requirements 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).

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • 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.