Tape Load Facility Interface Clause Samples
Tape Load Facility Interface. 4.4.1 Tape Load Facility Interface provides CLEC with unbundled access to Tape Load facilities in those SBC-12STATE ILECs that use such facilities to load data into LIDB and/or the LIDB administrative system. SBC-SWBT is the only SBC-12STATE ILEC that uses Tape Loads.
4.4.2 Tape Load Facility Interface allows CLEC to create and submit magnetic tapes for input into a LIDB administrative system and/or LIDB.
4.4.3 Tape Load Facility Interface is available only for special occurrences, such as CLEC’s initial load of data, updating CLEC’s entire data store for a new LIDB capability, and when CLEC’s updates exceed one hundred thousand (100,000) Line Records over and above CLEC’s normal daily update processing.
4.4.4 CLEC can choose one of two options for using the Tape Load Facility Interface. These options are the Single Tape Option and the Multiple Tape Option.
Tape Load Facility Interface. (A) Tape Load Facility Interface provides LSP with unbundled access to SWBT's Tape Load Facility in the same manner that SWBT accesses this facility. Tape Load Facility Interface allows LSP to create and submit magnetic tapes for input into LIDB.
(B) The Tape Load Facility Interface is not an interface to LVAS. The Tape Load Facility Interface is an entry point to LIDB at the SCP where LIDB resides.
(C) The Tape Load Facility Interface is available only when the amount of information is too large for LVAS to accommodate. Both parties agree that these situations normally occur during the initial load of LSP's information into LIDB or when LIDB is updated for a new product. The Tape Load Facility Interface is not available for ongoing updates of information. LSP may request the Tape Load Facility Interface only when its updates exceed 100,000 line/billing records over and above the LSP's normal daily update processing.
(D) LSP will create its own tapes in formats specified in GR-446-CORE, Issue 2, June 1994, as revised. Such tapes will only include information associated with LSP's line/billing records.
(E) LSP will deliver a separate set of tapes, each having identical information to each SCP node on which LIDB resides. SWBT will provide LSP with the name and address of the SWBT employee designated to receive the tapes at each location. 121
(F) In addition to the tapes LSP will create and deliver to the SCP node locations, LSP shall deliver an additional set of tapes to the LVAS System Administrator so that SWBT can load LSP's updates into LVAS. LSP understand that these additional tapes must contain information identical to the tapes delivered to the SCP nodes, but that the format will differ. SWBT shall provide LSP SWBT-specific documentation for record formations of these additional tapes. SWBT shall use these tapes to create LSP records in LVAS that correspond with the records being loaded into LIDB using the Tape Load Facility Interface. SWBT shall provide LSP with the name and address of the SWBT System Administrator to whom the LVAS update tapes should be sent.
(G) SWBT and LSP shall negotiate mutually agreed upon dates and times for tape loads of LSP data when such loads are the result of an LSP request.
(H) LSP understands and agrees that its record access through the Tape Load Facility Interface is only for LSP's own line/billing records. LSP warrants that it shall not use the Tape Load Facility Interface to modify any group record. LSP further wa...