File Layout. The Parties will exchange Data using the mutually agreed upon file layouts below. The Parties may edit and/or change the File Layout as considered necessary.
File Layout. Start End Length A/N Data Element
File Layout. Pages A-2 through A-6 contain the NACHA file layout required. It is understood that the file layout requirements set forth below on pages A-2 through A-6 are subject to changes and amendments that might be made from time to time by NACHA, and that such changes and amendments will be binding upon Bank and Company if and when made. Bank shall promptly notify Company of any such changes or amendments. NACHA FILE LAYOUT FILE HEADER RECORD Field Number Field Name Incl. Req’ment Contents Length Position Description 1 Record Type M “1” 1 01-01 “1” for Header 2 Priority Code R “01” 2 02-03 Reserved for future use - Use “01” for now 3 Immediate Destination M bTTTTAAAAC 10 04-13 ABA Number of the ACH receiving point for which the file is destined - “061100606” (position 4 should be left blank) 4 Immediate Origin M bTTTTAAAAC 10 14-23 This can be left blank 5 File Creation Date M YYMMDD 6 24-29 The date the file is created and/or transmitted to Synovus 6 File Creation Time O HHMM 4 30-33 Expressed as “HHMM” 24 hour clock format - Optional 7 File ID Modifier M Uppercase A-2 Numeric 0-9 1 34-34 Digit to differentiate between files with the same creation date. Only upper case A-Z and numeric 0-9 permitted. 8 Record Size M “094 3 35-37 “094” should be the record length 9 Blocking Factor M “10” 2 38-39 Defines the number of physical blocks in the file including both the file header and file control records. Must be 10.
File Layout. Department of Licensing will provide to the Licensee vehicle Data contained in DOL database using the mutually agreed upon file layout below. DOL reserves the right to edit and/or change the File Layout as considered necessary to the functions of DOL, with notice to the Licensee. • Method of Access/Transfer: Once an established Secure Data Transfer connection with the host computer at Licensee location is confirmed, DOL will provide Data listed in File Layout list below, to Licensee. • Delivery Method: (insert delivery method) • Frequency of Data Delivery: (insert frequency)
File Layout. The Parties will exchange Data using the mutually agreed upon file layouts below. The Parties may edit and/or change the File Layout as considered necessary. Method of Access/Transfer: [Describe transmission method and any applicable processes]. Frequency of Data Delivery: [Frequency]. [Example columns for data description below] Element Name Short Description Length Type Data Descriptions and Usages Exhibit __ Certification of Disposal of Confidential Information NAME OF RECEIVING PARTY: CONTRACT #: ___________________________________ (Receiving Party) herby certifies that the data described below, received as a part of the data provided in accordance with the contract listed above have been disposed of. You certify that you returned or destroyed all identified confidential information received from [Disclosing Party], or created, maintained, or received by you on behalf of [Disclosing Party]. You certify that you did not retain any copies of this confidential information.. Description of Information Date of Destruction or Return: Method(s) of disposal: Disposed by: Signature Date Printed Name:
File Layout. The Parties will exchange Data using the mutually agreed upon file layouts below. The Parties may edit and/or change the File Layout as considered necessary. Method of Access/Transfer: Once an established Secure Data Transfer connection with the host computer at Contractor’s location is confirmed, HCA will provide Data listed in File Layout list below, to Contractor. Delivery Method: Secure File Transfer Frequency of Data Delivery: HCA will transmit Data [Frequency]. Costs: [(This will likely be N/A)] [Example below – use what is received in Technical Design Specification] Element Name Friendly Name Length Type Data Descriptions and Usages Attachment 1: Data Security Requirements Definitions In addition to the definitions set out in the Data Use, Security, and Confidentiality Schedule, the definitions below apply to this Attachment.
