Common use of Exchange of Billing Message Information Clause in Contracts

Exchange of Billing Message Information. 8.10.1 SBC-13STATE will provide LEVEL 3 a specific Daily Usage File (“DUF” or “Usage Extract”) for Resale Services and Network Element usage sensitive services provided hereunder (“Customer Usage Data”). Such Customer Usage Data shall be provided by SBC-13STATE in accordance with Exchange Message Interface (EMI) guidelines supported by OBF. Any exceptions to the supported formats will be noted in the DUF implementation requirements documentation for each SBC- 13STATE owned LEVEL 3. The DUF will include (i) specific daily usage, including both Local Traffic (if and where applicable) and LEC- carried IntraLATA Toll Traffic, in EMI format for usage sensitive services furnished in connection with each Resale Service and Network Element to the extent that similar usage sensitive information is provided to retail End-Users of SBC-13STATE within that state, (ii) with sufficient detail to enable LEVEL 3 to xxxx its End-Users for usage sensitive services furnished by SBC-13STATE in connection with Resale Services and Network Elements provided by SBC-13STATE. Procedures and processes for implementing the interfaces with SBC MIDWEST REGION 5-STATE, SBC CALIFORNIA, SBC NEVADA, SBC CONNECTICUT, and SBC SOUTHWEST REGION 5-STATE will be included in implementation requirements documentation.

Exchange of Billing Message Information. 8.10.1 SBC-13STATE will provide LEVEL 3 a specific Daily Usage File (“DUF” or “Usage Extract”) for Resale Services and Network Element usage sensitive services provided hereunder (“Customer Usage Data”). Such Customer Usage Data shall be provided by SBC-13STATE in accordance with Exchange Message Interface (EMI) guidelines supported by OBF. Any exceptions to the supported formats will be noted in the DUF implementation requirements documentation for each SBC- 13STATE owned LEVEL 3. The DUF will include (i) specific daily usage, including both Local Traffic (if and where applicable) and LEC- carried IntraLATA Toll Traffic, in EMI format for usage sensitive services furnished in connection with each Resale Service and Network Element to the extent that similar usage sensitive information is provided to retail End-Users of SBC-13STATE within that state, (ii) with sufficient detail to enable LEVEL 3 to xxxx bill its End-Users for usage sensitive services furnished by SBC-13STATE in connection with Resale Services and Network Elements provided by SBC-13STATE. Procedures and processes for implementing the interfaces with SBC MIDWEST REGION 5-STATE, SBC CALIFORNIA, SBC NEVADA, SBC CONNECTICUT, and SBC SOUTHWEST REGION 5-STATE will be included in implementation requirements documentation.

Exchange of Billing Message Information. 8.10.1 8.13.1 SBC-13STATE will provide LEVEL 3 CLEC a specific Daily Usage File (“DUF” or “Usage Extract”) for Resale Services and Network Element usage sensitive services provided hereunder (“Customer Usage Data”). Such Customer Usage Data shall be provided by SBC-13STATE in accordance with Exchange Message Interface (EMI) guidelines supported by OBF. Any exceptions to the supported formats will be noted in the DUF implementation requirements documentation for each SBC- 13STATE owned LEVEL 3ILEC. The DUF will shall include (i) specific daily usage, including both Local Traffic (if and where applicable) and LEC- LEC-carried IntraLATA Toll Traffic, in EMI format for usage sensitive services furnished in connection with each Resale Service and Network Element to the extent that similar usage sensitive information is provided to retail End-End Users of SBC-13STATE within that state, (ii) with sufficient detail to enable LEVEL 3 CLEC to xxxx its End-End Users for usage sensitive services furnished by SBC-13STATE in connection with Resale Services and Network Elements provided by SBC-13STATESBC- 13STATE. Procedures and processes for implementing the interfaces with SBC MIDWEST REGION 5-STATE, SBC CALIFORNIA, SBC NEVADA, SBC CONNECTICUTSNET, and SBC SOUTHWEST REGION 5-STATE will be included in implementation requirements documentation.