Common use of ODUF Physical File Characteristics Clause in Contracts

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to <<customer_short_name>> via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed 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 holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery. 6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and <<customer_short_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_short_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_short_name>> will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be <<customer_short_name>>’s responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to <<customer_short_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_short_name>> will be the responsibility of <<customer_short_name>>. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_short_name>>’s end for the purpose of data transmission will be the responsibility of <<customer_short_name>>. 6.2.3 If <<customer_short_name>> utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of <<customer_short_name>>.

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to <<customer_short_name>> via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) 175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery. 6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and <<customer_short_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_short_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_short_name>> will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be <<customer_short_name>>’s 's responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to <<customer_short_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_short_name>> will be the responsibility of <<customer_short_name>>. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_short_name>>’s > end for the purpose of data transmission will be the responsibility of <<customer_short_name>>. 6.2.3 If <<customer_short_name>> utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of <<customer_short_name>>.

ODUF Physical File Characteristics. 6.2.1 12.7.2.1 ODUF will be distributed to <<customer_short_name>> CUSTOMER via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte Version: 2Q05 T-MBR 09/08/05 format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox mailbox is nearing capacity levels, BellSouth may move the customer CUSTOMER to CONNECT:Direct file delivery. 6.2.2 12.7.2.2 If the customer CUSTOMER is moved, moved to CONNECT:Direct Direct, data circuits (private line or dial-up) will be required between BellSouth and <<customer_short_name>> CUSTOMER for the purpose of data transmission. Where a dedicated line is required, <<customer_short_name>> CUSTOMER will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_short_name>> CUSTOMER will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be <<customer_short_name>>CUSTOMER’s responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to <<customer_short_name>>CUSTOMER. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_short_name>> CUSTOMER will be the responsibility of <<customer_short_name>>CUSTOMER. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_short_name>>CUSTOMER’s end for the purpose of data transmission will be the responsibility of <<customer_short_name>>CUSTOMER. 6.2.3 12.7.2.3 If <<customer_short_name>> CUSTOMER utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of <<customer_short_name>>CUSTOMER.

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to <<customer_short_name>> via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed 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 holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth AT&T determines the Secure FTP Mailbox is nearing capacity levels, BellSouth AT&T may move the customer to CONNECT:Direct file delivery. 6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth AT&T and <<customer_short_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_short_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. AT&T. <<customer_short_name>> will also be responsible for any charges associated with this line. Equipment required on the BellSouth AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be <<customer_short_name>>’s responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth AT&T data center by BellSouth AT&T and the associated charges assessed to <<customer_short_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_short_name>> will be the responsibility of <<customer_short_name>>. Associated equipment on the BellSouth AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_short_name>>’s end for the purpose of data transmission will be the responsibility of <<customer_short_name>>. 6.2.3 If <<customer_short_name>> utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of <<customer_short_name>>.