Common use of ODUF Physical File Characteristics Clause in Contracts

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 3 contracts

Samples: MFN Agreement, MFN Agreement, MFN Agreement

AutoNDA by SimpleDocs

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 3 contracts

Samples: MFN Agreement, MFN Agreement, MFN Agreement

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox SPARDI via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 2 contracts

Samples: General Terms and Conditions, General Terms and Conditions

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox eXpeTel via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 1 contract

Samples: General Terms and Conditions

AutoNDA by SimpleDocs

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Xxxx via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 1 contract

Samples: General Terms and Conditions

ODUF Physical File Characteristics. 6.2.1 7.2.1 ODUF will be distributed to NuVox Spectrotel via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF 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.

Appears in 1 contract

Samples: General Terms and Conditions

Time is Money Join Law Insider Premium to draft better contracts faster.