Common use of EODUF Physical File Characteristics Clause in Contracts

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access via FTP. The EODUF messages will be intermingled among Image Access’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access VMT via FTP. The EODUF messages will be intermingled among Image AccessVMT’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access ComSouth via FTP. The EODUF messages will be intermingled among Image AccessComSouth’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access Esodus via FTP. The EODUF messages will be intermingled among Image AccessEsodus’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access TeraBlue via FTP. The EODUF messages will be intermingled among Image AccessTeraBlue’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access Phone Home via FTP. The EODUF messages will be intermingled among Image AccessPhone Home’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth AT&T determines the Secure FTP mailbox is nearing capacity levels, BellSouth may AT&Tmay move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access FPB via FTP. The EODUF messages will be intermingled among Image AccessFPB’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access CTI via FTP. The EODUF messages will be intermingled among Image AccessCTI’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access RGW via FTP. The EODUF messages will be intermingled among Image AccessRGW’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.