Common use of Physical File Characteristics Clause in Contracts

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_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 successfully ongoing will be negotiated on a case by case basis. 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_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> will be the responsibility of <<customer_name>>. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>’s end for the purpose of data transmission will be the responsibility of <<customer_name>>.

Physical File Characteristics. 7.2.1 6.2.1 The Enhanced Optional Daily Usage Feed File will be distributed to <<customer_name>> over their existing Optional via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>’s Optional Daily Usage File (ODUF) messages. The EODUF Feed will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF Daily Usage Feed will be in a non-compacted EMI format (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 dataset per workday per OCN. 7.2.2 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_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 successfully ongoing will be negotiated on a case by case basis. 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_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> will be the responsibility of <<customer_name>>. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>’s > end for the purpose of data transmission will be the responsibility of <<customer_name>>.

Physical File Characteristics. 7.2.1 6.2.1 The Enhanced Optional Daily Usage Feed File will be distributed to <<customer_name>> over their existing Optional via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>’s Optional Daily Usage File (ODUF) messages. The EODUF Feed will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF Daily Usage Feed will be in a non-compacted EMI format (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 dataset per workday per OCN. 7.2.2 6.2.2 Data circuits (private line or dial-up) may will be required between BellSouth and <<customer_name>> for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_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 successfully ongoing will be negotiated on a case by case basis. 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_name>>. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> will be the responsibility of <<customer_name>>. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>’s > end for the purpose of data transmission will be the responsibility of <<customer_name>>.

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed EODUF feed will be distributed to <<customer_name>> Cellutell Communications, Inc. over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>Cellutell Communications, Inc.’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> Cellutell Communications, Inc. for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> Cellutell Communications, Inc. will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> Cellutell Communications, Inc. 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 successfully ongoing will be negotiated on a case by an individual case basis. 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_name>>. Cellutell Communications, Version R4Q01 12/01/01 Inc.. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> Cellutell Communications, Inc. will be the responsibility of <<customer_name>>. Cellutell Communications, Inc.. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>Cellutell Communications, Inc.’s end for the purpose of data transmission will be the responsibility of <<customer_name>>.Cellutell Communications, Inc..

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> Premier Connection, Inc. over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>Premier Connection, Inc.’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> Premier Connection, Inc. for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> Premier Connection, Inc. will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> Premier Connection, Inc. 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 successfully ongoing will be negotiated on a case by case basis. 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_name>>. Premier Connection, Inc.. Version 3Q00: 11/28/00 Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> Premier Connection, Inc. will be the responsibility of <<customer_name>>. Premier Connection, Inc.. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>Premier Connection, Inc.’s end for the purpose of data transmission will be the responsibility of <<customer_name>>.Premier Connection, Inc..

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> NATIONSLINK COMMUNICATIONS over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>’s NATIONSLINK COMMUNICATIONS’ Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> NATIONSLINK COMMUNICATIONS for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> NATIONSLINK COMMUNICATIONS will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> NATIONSLINK COMMUNICATIONS 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 successfully ongoing will be negotiated on a case by case basis. 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_name>>NATIONSLINK COMMUNICATIONS. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> NATIONSLINK COMMUNICATIONS will be the responsibility of <<customer_name>>NATIONSLINK COMMUNICATIONS. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Partiesparties. All equipment, including modems and software, that is required on <<customer_name>>’s NATIONSLINK COMMUNICATIONS’ end for the purpose of data transmission will be the responsibility of <<customer_name>>NATIONSLINK COMMUNICATIONS.

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed EODUF feed will be distributed to <<customer_name>> Speedy Reconnect, Inc. over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>Speedy Reconnect, Inc.’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> Speedy Reconnect, Inc. for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> Speedy Reconnect, Inc. will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> Speedy Reconnect, Inc. 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 successfully ongoing will be negotiated on a case by an individual case basis. 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_name>>. Speedy Reconnect, Inc.. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> Speedy Reconnect, Inc. will be the responsibility of <<customer_name>>. Speedy Reconnect, Inc.. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by Version R4Q01 12/01/01 an individual case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>Speedy Reconnect, Inc.’s end for the purpose of data transmission will be the responsibility of <<customer_name>>.Speedy Reconnect, Inc..

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> D.S.L. Telecom over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>D.S.L. Telecom’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> D.S.L. Telecom for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> D.S.L. Telecom will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> D.S.L. Telecom 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 successfully ongoing will be negotiated on a case by case basis. 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_name>>D.S.L. Telecom. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> D.S.L. Telecom will be the responsibility of <<customer_name>>D.S.L. Telecom. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>D.S.L. Telecom’s end for the purpose of data transmission will be the responsibility of <<customer_name>>D.S.L. Telecom.

Physical File Characteristics. 7.2.1 6.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> Xxxxxxxxx.xxx over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>’s Xxxxxxxxx.xxx's Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> Xxxxxxxxx.xxx for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> Xxxxxxxxx.xxx will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> Xxxxxxxxx.xxx 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 successfully ongoing will be negotiated on a case by case basis. 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_name>>Xxxxxxxxx.xxx. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> Xxxxxxxxx.xxx. will be the responsibility of <<customer_name>>Xxxxxxxxx.xxx. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Partiesparties. All equipment, including modems and software, that is required on <<customer_name>>’s Xxxxxxxxx.xxx. end for the purpose of data transmission will be the responsibility of <<customer_name>>Xxxxxxxxx.xxx.

Physical File Characteristics. 7.2.1 The Enhanced Optional Daily Usage Feed will be distributed to <<customer_name>> A-Tech Telecom, Inc. over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among <<customer_name>>A-Tech Telecom, Inc.’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and <<customer_name>> A-Tech Telecom, Inc. for the purpose of data transmission. Where a dedicated line is required, <<customer_name>> A-Tech Telecom, Inc. will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <<customer_name>> A-Tech Telecom, Inc. 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 successfully ongoing will be negotiated on a case by case basis. 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_name>>. A-Tech Telecom, Inc.. Additionally, all message toll charges associated with the use of the dial circuit by <<customer_name>> A- Tech Telecom, Inc. will be the responsibility of <<customer_name>>. A-Tech Telecom, Inc.. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the Parties. All equipment, including modems and software, that is required on <<customer_name>>A-Tech Telecom, Inc.’s end for the purpose of data transmission will be the responsibility of <<customer_name>>.A-Tech Telecom, Inc..