Electronic Data Exchange. If requested by CPR the Supplier undertakes to conduct business transactions using electronic data interchange (“EDI”) pursuant to the process identified immediately below. CPR may elect to waive this requirement upon written request by Supplier. Supplier shall submit purchase order related invoices through EDI or ORISS, otherwise invoices shall be sent via email to XX_Xxxxxxxxx@xxx.xx or by mail to: Canadian Pacific Railway Company ATTN: IS Invoicing Team Building #0, 0000 Xxxxx Xxxx Xxxx SE Calgary, AB Canada T2C 4X9 The Parties agree that the following provisions govern EDI:
Electronic Data Exchange. A number of methods of electronic data transmission are available when a partner is ready to exchange files with the Benefits Coordination & Recovery Center (BCRC) in test or production modes. Following is an overview of the most common. The Partner’s assigned Electronic Data Interchange Representative (XXX Rep) at the BCRC will address a Partner’s specific questions and concerns. Data exchange using hard media (e.g., CD) is not permitted. CMS’ preferred method of electronic transmission is Connect:Direct (formerly known as Network Data Mover [NDM]). This system provides a direct file transmission connection to the BCRC mainframe using the CMS Extranet Network and CMS’s private CMSNet. Use of either SNA or TCP/IP is available to submitters connected to Connect:Direct. In addition, CMS has available two secure Internet transmission options. We recommend either of these options for Partners that anticipate having a relatively low volume of data transmissions, and that might find it is a burden to secure a Connect:Direct connection • SFTP: Using SFTP permits automated data transmission and management. A Partner may use any SFTP client as long as it is SSH v2 capable. • HTTPS: There is no additional cost associated with using this method as long as the Internet Explorer browser is used. However, use of HTTPS does not permit automated data management. If a Partner is contemplating a method of data transmission that has not been discussed above, the Partner will need to establish specific alternative data transmission procedures with the BCRC.
Electronic Data Exchange. 21.1. During the provision of the Services, the parties may communicate electronically. However, it is not possible to guarantee that the electronic data transfer can take place entirely securely, without viruses or errors, and consequently such data transmissions could be hacked, falsified, lost, deleted, delayed or made unusable. The parties acknowledge that no system or procedure can completely rule out such risks.
Electronic Data Exchange. Promptly following the Effective Date, the Parties will establish a secure electronic data exchange system through which the Parties may share Know-How to be exchanged by the Parties under this Agreement, including the Know-How transfer obligations of this Section 2.5.
Electronic Data Exchange. A number of methods of electronic data transmission are available when a partner is ready to exchange files with the Benefits Coordination & Recovery Center (BCRC) in test or production modes. Following is an overview of the most common. The Partner’s assigned Electronic Data Interchange Representative (XXX Rep) at the BCRC will address a Partner’s specific questions and concerns. Data exchange using hard media (e.g., CD) is not permitted. CMS’ preferred method of electronic transmission is Connect:Direct (formerly known as Network Data Mover [NDM]) via the CMS Electronic File Transfer (CMS EFT) protocol. This system provides a direct file transmission connection using the CMS Extranet Network and CMS’ private CMSNet. Use of either SNA or TCP/IP is available to submitters connected to Connect:Direct. In addition, CMS has available two secure Internet transmission options. We recommend either of these options for Partners that anticipate having a relatively low volume of data transmissions, and that might find it is a burden to secure a Connect:Direct connection. • SFTP: Using SFTP permits automated data transmission and management. A Partner may use any SFTP client as long as it is SSH v2 capable. • HTTPS: There is no additional cost associated with using this method as long as the Internet Explorer browser is used. However, use of HTTPS does not permit automated data management. If a Partner is contemplating a method of data transmission that has not been discussed above, the Partner will need to establish specific alternative data transmission procedures with the BCRC.
Electronic Data Exchange. (a) For purposes of satisfying Customer requirements and optimizing the flow of business communications among Amkor, CIL, AICL and Customers, Amkor and AICL shall establish, as part of the Foundry Management System or otherwise, an EDE System.
Electronic Data Exchange. Healthcare Provider and Business Associate shall adhere to the electronic data exchange protocols as provided in Health and Human Services Department Standards for Individually Identifiable Health Information, 45 C.F.R. Parts 142.
Electronic Data Exchange. Healthcare Provider and CCUSA shall adhere to the electronic data exchange protocols as required by Health and Human Services Department Standards for Individually Identifiable Health Information.
Electronic Data Exchange. Where the requisite facilities exist, Innovated Leasing and the Customer may by separate agreement (eg: DDR), agree to use electronic data interchange in relation to the agreement. Theft / Loss In the event of the Innovated Leasing supplied Fuel Card being lost / stolen, the customer will be liable for any charges incurred on the Fuel Card for the period specified by the respective (ultimate) fuel card ‘provider’ (eg: Motorpass card) after notice is given to Innovated Leasing and/or the provider of the lost / stolen card.
Electronic Data Exchange. Without prejudice to hubco’s obligations under this Protocol and this Agreement, hubco does not warrant, expressly or impliedly, the integrity of any electronic data delivered in accordance with this Protocol. hubco shall have no liability to the Authority in connection with any corruption or any unintended amendment, modification or alteration of the electronic data in a specified Model which occurs after it has been transmitted by hubco, save where such corruption, amendment, modification or alteration is a result of hubco’s failure to comply with this Protocol.
