Common use of Operations Support Systems for Resold Services Clause in Contracts

Operations Support Systems for Resold Services. 1.1.1 dPi will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi chooses to establish a separate NDM interface, dPi must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPi. GTE itself does not have uniform access to this information electronically. Until GTE and dPi have agreed and established electronic interfaces, dPi agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi directly to GTE's NOMC service representatives. When dPi receives a request for basic services from a new local service customer, dPi will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi sends the confirming LSR. dPi will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi on a real time interface to process vanity numbers while dPi's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPi's account is referred to as the dPi Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi a service completion report. Call records for actual service provided to dPi's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPi's accounts will be generated and transmitted electronically to dPi. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi to issue a xxxx to its end users. 1.1.11 GTE will provide dPi with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPi's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer retention period, dPi shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi places a request for a PIC change via LSR, the billing will be made on dPi account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi end users by rejecting back to the IXC with the dPi OCN. Detail is provided so that dPi can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi NEW PHONE will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi NEW PHONE will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi NEW PHONE chooses to establish a separate NDM interface, dPi NEW PHONE must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by facsimile, E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi NEW PHONE or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi NEW PHONE must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi NEW PHONE will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi NEW PHONE would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi NEW PHONE would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiNEW PHONE. GTE itself does not have uniform access to this information electronically. Until GTE and dPi NEW PHONE have agreed and established electronic interfaces, dPi NEW PHONE agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi NEW PHONE directly to GTE's NOMC service representatives. When dPi NEW PHONE receives a request for basic services from a new local service customer, dPi NEW PHONE will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi NEW PHONE will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi NEW PHONE sends the confirming LSR. dPi NEW PHONE will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi NEW PHONE will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi NEW PHONE through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi NEW PHONE will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi NEW PHONE fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi NEW PHONE of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi NEW PHONE over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi NEW PHONE on a real time interface to process vanity numbers while dPiNEW PHONE's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi NEW PHONE representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi NEW PHONE and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiNEW PHONE's account is referred to as the dPi NEW PHONE Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi NEW PHONE a service completion report. Call records for actual service provided to dPiNEW PHONE's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi NEW PHONE for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiNEW PHONE's accounts will be generated and transmitted electronically to dPiNEW PHONE. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi NEW PHONE to issue a xxxx to its end users. 1.1.11 GTE will provide dPi NEW PHONE with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiNEW PHONE's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer this retention periodis exclusively for NEW PHONE, dPi NEW PHONE shall reimburse GTE for all expenses related to that this retention. 1.1.15 In addition to the LSR delivery process, dPi NEW PHONE will distribute DA directory assistance and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi NEW PHONE places a request for a PIC change via LSR, the billing will be made on dPi NEW PHONE account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi NEW PHONE end users by rejecting back to the IXC with the dPi NEW PHONE OCN. Detail is provided so that dPi NEW PHONE can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi DTI will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi DTI will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi DTI chooses to establish a separate NDM interface, dPi DTI must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by facsimile, E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi DTI or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi DTI must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi DTI will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi DTI would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi DTI would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiDTI. GTE itself does not have uniform access to this information electronically. Until GTE and dPi DTI have agreed and established electronic interfaces, dPi DTI agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi DTI directly to GTE's NOMC service representatives. When dPi DTI receives a request for basic services from a new local service customer, dPi DTI will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi DTI will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi DTI sends the confirming LSR. dPi DTI will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi DTI will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi DTI through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi DTI will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi DTI fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi DTI of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi DTI over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi DTI on a real time interface to process vanity numbers while dPiDTI's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi DTI representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi DTI and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiDTI's account is referred to as the dPi DTI Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi DTI a service completion report. Call records for actual service provided to dPiDTI's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi DTI for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiDTI's accounts will be generated and transmitted electronically to dPiDTI. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi DTI to issue a xxxx to its end users. 1.1.11 GTE will provide dPi DTI with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiDTI's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer this retention periodis exclusively for DTI, dPi DTI shall reimburse GTE for all expenses related to that this retention. 1.1.15 In addition to the LSR delivery process, dPi DTI will distribute DA directory assistance and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi DTI places a request for a PIC change via LSR, the billing will be made on dPi DTI account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi DTI end users by rejecting back to the IXC with the dPi DTI OCN. Detail is provided so that dPi DTI can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi USTELCOM will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi USTELCOM will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi USTELCOM chooses to establish a separate NDM interface, dPi USTELCOM must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi USTELCOM or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi USTELCOM must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi USTELCOM will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi USTELCOM would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi USTELCOM would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiUSTELCOM. GTE itself does not have uniform access to this information electronically. Until GTE and dPi USTELCOM have agreed and established electronic interfaces, dPi USTELCOM agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi USTELCOM directly to GTE's NOMC service representatives. When dPi USTELCOM receives a request for basic services from a new local service customer, dPi USTELCOM will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi USTELCOM will give GTE the new customer's name, service address and type of requested service (i.e., X0R1, X0Bl). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi USTELCOM sends the confirming LSR. dPi USTELCOM will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi USTELCOM will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi USTELCOM through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi USTELCOM will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi USTELCOM fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi USTELCOM of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx hunt groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi USTELCOM over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group hunt xxxup for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi USTELCOM on a real time interface to process vanity numbers while dPiUSTELCOM's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi USTELCOM representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi USTELCOM and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiUSTELCOM's account is referred to as the dPi USTELCOM Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi USTELCOM a service completion report. Call records for actual service provided to dPiUSTELCOM's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi bill xx USTELCOM for resold services along with a summary xxxx masterbill xxxter. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiUSTELCOM's accounts will be generated and transmitted electronically to dPiUSTELCOM. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi USTELCOM to issue a xxxx to bill xx its end users. 1.1.11 GTE will provide dPi USTELCOM with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx bill format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accountsbill xxxounts. 1.1.13 GTE accepts dPiUSTELCOM's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi USTELCOM requires a longer retention period, dPi USTELCOM shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi USTELCOM will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxxbill. As dPi Xx USTELCOM places a request for a PIC change via LSR, the billing will be made on dPi USTELCOM account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi USTELCOM end users by rejecting back to the IXC with the dPi USTELCOM OCN. Detail is provided so that dPi USTELCOM can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi JTC will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi JTC will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi JTC chooses to establish a separate NDM interface, dPi JTC must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi JTC or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi JTC must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi JTC will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi JTC would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi JTC would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiJTC. GTE itself does not have uniform access to this information electronically. Until GTE and dPi JTC have agreed and established electronic interfaces, dPi JTC agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi JTC directly to GTE's NOMC service representatives. When dPi JTC receives a request for basic services from a new local service customer, dPi JTC will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi JTC will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi JTC sends the confirming LSR. dPi JTC will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi JTC will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi JTC through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi JTC will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi JTC fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi JTC of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi JTC over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi JTC on a real time interface to process vanity numbers while dPiJTC's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi JTC representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi JTC and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiJTC's account is referred to as the dPi JTC Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi JTC a service completion report. Call records for actual service provided to dPiJTC's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi JTC for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiJTC's accounts will be generated and transmitted electronically to dPiJTC. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi JTC to issue a xxxx to its end users. 1.1.11 GTE will provide dPi JTC with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiJTC's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi JTC requires a longer retention period, dPi JTC shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi JTC will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi JTC places a request for a PIC change via LSR, the billing will be made on dPi JTC account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi JTC end users by rejecting back to the IXC with the dPi JTC OCN. Detail is provided so that dPi JTC can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi EZPHONE will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi EZPHONE will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi EZPHONE chooses to establish a separate NDM interface, dPi EZPHONE must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-E- mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi EZPHONE or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi EZPHONE must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi EZPHONE will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi EZPHONE would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi EZPHONE would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiEZPHONE. GTE itself does not have uniform access to this information electronically. Until GTE and dPi EZPHONE have agreed and established electronic interfaces, dPi XXXXXXX agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi EZPHONE directly to GTE's NOMC service representatives. When dPi EZPHONE receives a request for basic services from a new local service customer, dPi EZPHONE will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi EZPHONE will give GTE the new customer's name, service address and type of requested service (i.e., X0R1, X0B1). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi XXXXXXX sends the confirming LSR. dPi EZPHONE will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi EZPHONE will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi EZPHONE through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi EZPHONE will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi EZPHONE fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi EZPHONE of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi EZPHONE over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi EZPHONE on a real time interface to process vanity numbers while dPiXXXXXXX's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi EZPHONE representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi EZPHONE and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiEZPHONE's account is referred to as the dPi EZPHONE Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi EZPHONE a service completion report. Call records for actual service provided to dPiEZPHONE's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx bill to dPi EZPHONE for resold services along with a summary xxxx bill master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiEZPHONE's accounts will be generated and transmitted electronically to dPiEZPHONE. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi EZPHONE to issue a xxxx bill to its end users. 1.1.11 GTE will provide dPi EZPHONE with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx bill format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx bill accounts. 1.1.13 GTE accepts dPiEZPHONE's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi EZPHONE requires a longer retention period, dPi EZPHONE shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi EZPHONE will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxxbill. As dPi EZPHONE places a request for a PIC change via LSR, the billing will be made on dPi EZPHONE account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi EZPHONE end users by rejecting back to the IXC with the dPi EZPHONE OCN. Detail is provided so that dPi EZPHONE can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi TELECONEX will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi TELECONEX will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi TELECONEX chooses to establish a separate NDM interface, dPi TELECONEX must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi TELECONEX or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi TELECONEX must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi TELECONEX will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi TELECONEX would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi TELECONEX would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiTELECONEX. GTE itself does not have uniform access to this information electronically. Until GTE and dPi TELECONEX have agreed and established electronic interfaces, dPi TELECONEX agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi TELECONEX directly to GTE's NOMC service representatives. When dPi TELECONEX receives a request for basic services from a new local service customer, dPi TELECONEX will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi TELECONEX will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi TELECONEX sends the confirming LSR. dPi TELECONEX will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi TELECONEX will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi TELECONEX through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi TELECONEX will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi TELECONEX fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi TELECONEX of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi TELECONEX over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi TELECONEX on a real time interface to process vanity numbers while dPiTELECONEX's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi TELECONEX representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi TELECONEX and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiTELECONEX's account is referred to as the dPi TELECONEX Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi TELECONEX a service completion report. Call records for actual service provided to dPiTELECONEX's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi TELECONEX for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiTELECONEX's accounts will be generated and transmitted electronically to dPiTELECONEX. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi TELECONEX to issue a xxxx to its end users. 1.1.11 GTE will provide dPi TELECONEX with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiTELECONEX's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi TELECONEX requires a longer retention period, dPi TELECONEX shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi TELECONEX will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi TELECONEX places a request for a PIC change via LSR, the billing will be made on dPi TELECONEX account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi TELECONEX end users by rejecting back to the IXC with the dPi TELECONEX OCN. Detail is provided so that dPi TELECONEX can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi PCS will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi PCS will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi PCS chooses to establish a separate NDM interface, dPi PCS must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by facsimile, E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi PCS or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi PCS must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi PCS will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi PCS would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi PCS would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiPCS. GTE itself does not have uniform access to this information electronically. Until GTE and dPi PCS have agreed and established electronic interfaces, dPi PCS agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi PCS directly to GTE's NOMC service representatives. When dPi PCS receives a request for basic services from a new local service customer, dPi PCS will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi PCS will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi PCS sends the confirming LSR. dPi PCS will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi PCS will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi PCS through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi PCS will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi PCS fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi PCS of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi PCS over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi PCS on a real time interface to process vanity numbers while dPiPCS's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi PCS representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi PCS and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiPCS's account is referred to as the dPi PCS Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi PCS a service completion report. Call records for actual service provided to dPiPCS's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi PCS for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiPCS's accounts will be generated and transmitted electronically to dPiPCS. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi PCS to issue a xxxx to its end users. 1.1.11 GTE will provide dPi PCS with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiPCS's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer this retention periodis exclusively for PCS, dPi PCS shall reimburse GTE for all expenses related to that this retention. 1.1.15 In addition to the LSR delivery process, dPi PCS will distribute DA directory assistance and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi PCS places a request for a PIC change via LSR, the billing will be made on dPi PCS account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi PCS end users by rejecting back to the IXC with the dPi PCS OCN. Detail is provided so that dPi PCS can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi EZ Talk will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi EZ Talk will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi EZ Talk chooses to establish a separate NDM interface, dPi EZ Talk must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-facsimile, E- mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi EZ Talk or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi EZ Talk must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi EZ Talk will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi EZ Talk would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi EZ Talk would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiEZ Talk. GTE itself does not have uniform access to this information electronically. Until GTE and dPi EZ Talk have agreed and established electronic interfaces, dPi EZ Talk agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi EZ Talk directly to GTE's NOMC service representatives. When dPi EZ Talk receives a request for basic services from a new local service customer, dPi EZ Talk will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi EZ Talk will give GTE the new customer's name, service address and type of requested service (i.e., X0R1, X0B1). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi EZ Talk sends the confirming LSR. dPi EZ Talk will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi EZ Talk will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi EZ Talk through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi EZ Talk will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi EZ Talk fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi EZ Talk of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi EZ Talk over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi EZ Talk on a real time interface to process vanity numbers while dPiEZ Talk's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi EZ Talk representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi EZ Talk and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiEZ Talk's account is referred to as the dPi EZ Talk Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi EZ Talk a service completion report. Call records for actual service provided to dPiEZ Talk's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx bill to dPi EZ Talk for resold services along with a summary xxxx bill master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiEZ Talk's accounts will be generated and transmitted electronically to dPiEZ Talk. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi EZ Talk to issue a xxxx bill to its end users. 1.1.11 GTE will provide dPi EZ Talk with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx bill format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx bill accounts. 1.1.13 GTE accepts dPiEZ Talk's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer this retention periodis exclusively for EZ Talk, dPi EZ Talk shall reimburse GTE for all expenses related to that this retention. 1.1.15 In addition to the LSR delivery process, dPi EZ Talk will distribute DA directory assistance and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxxbill. As dPi EZ Talk places a request for a PIC change via LSR, the billing will be made on dPi EZ Talk account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi EZ Talk end users by rejecting back to the IXC with the dPi EZ Talk OCN. Detail is provided so that dPi EZ Talk can identify the specific charges for rebilling to its end user.

Operations Support Systems for Resold Services. 1.1.1 dPi CDI will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi CDI will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi CDI chooses to establish a separate NDM interface, dPi CDI must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by facsimile, E-mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi CDI or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi CDI must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi CDI will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi CDI would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi CDI would not have the due date or new ne telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiCDI. GTE itself does not have uniform access to this information electronically. Until GTE and dPi CDI have agreed and established electronic interfaces, dPi CDI agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi CDI directly to GTE's NOMC service representatives. When dPi CDI receives a request for basic services from a new local service customer, dPi CDI will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi CDI will give GTE the new customer's name, service address and type of requested service (i.e., X0R1, X0B1). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi CDI sends the confirming LSR. dPi CDI will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi CDI will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi CDI through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi CDI will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi on a real time interface to process vanity numbers while dPi's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPi's account is referred to as the dPi Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi a service completion report. Call records for actual service provided to dPi's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPi's accounts will be generated and transmitted electronically to dPi. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi to issue a xxxx to its end users. 1.1.11 GTE will provide dPi with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPi's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer retention period, dPi shall reimburse GTE for all expenses related to that retention. 1.1.15 In addition to the LSR delivery process, dPi will distribute DA and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi places a request for a PIC change via LSR, the billing will be made on dPi account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi end users by rejecting back to the IXC with the dPi OCN. Detail is provided so that dPi can identify the specific charges for rebilling to its end user.12:00

Operations Support Systems for Resold Services. 1.1.1 dPi Prepaid will also be able to order services for resale, as well as interim number portability, directly from GTE through an electronic interface. To initiate an order for these services, dPi Prepaid will submit a Local Service Request ("LSR") from its data center to GTE's Data Center using an electronic NDM interface. If no NDM interface exists or if dPi Prepaid chooses to establish a separate NDM interface, dPi Prepaid must request an NDM facility. For new entrants that elect not to interface electronically, GTE will accommodate submission of LSR orders by E-facsimile, E- mail, Internet or a dial NDM arrangement. An LSR is very similar to an ASR, except that it will be used exclusively for line-side interconnection requests. GTE will transfer LSRs to GTE's NOMC centralized service order processing center electronically. 1.1.2 Most LSRs will be used either to transfer an existing GTE customer to dPi Prepaid or to request service for a new customer who is not an existing GTE customer. Depending on the situation, different information will be required on the LSR. LSRs for a conversion of a GTE local customer to dPi Prepaid must include information relating to all existing, new and disconnected services for that customer, including the customer's name, type of service desired, location of service and features or options the customer desires. dPi Prepaid will be able to obtain this customer information after GTE has received the customer's written consent as specified in Article IV, Section 8. For service to a new customer who is not an existing GTE customer, the LSR must contain the customer's name, service address, service type, services, options, features and Services data. If known, the LSR should include the telephone number and due date/desired due date. 1.1.3 While dPi Prepaid would have its own customer information and may have the SAG/GTE products on tape from GTE, dPi Prepaid would not have the due date or new telephone number for new customers since that information is contained in GTE's systems. Therefore, a process is required to provide this information to dPiPrepaid. GTE itself does not have uniform access to this information electronically. Until GTE and dPi Prepaid have agreed and established electronic interfaces, dPi Prepaid agrees that an 800 number is the method that will be used. The 800 telephone number will connect dPi Prepaid directly to GTE's NOMC service representatives. When dPi Prepaid receives a request for basic services from a new local service customer, dPi Prepaid will call GTE's NOMC through the 800 number, and, while the new customer is on hold, GTE will provide the due date for service and the new telephone number for that customer. At the same time, dPi Prepaid will give GTE the new customer's name, service address and type of requested service (i.e., X0, X0). GTE will enter that information into its SORCES or SOLAR service ordering systems to be held in suspense until dPi Prepaid sends the confirming LSR. dPi Prepaid will then return to its customer holding on the line and provide the due date and new telephone number. 1.1.4 After concluding the telephone call with the new customer, dPi Prepaid will complete a confirming LSR for the new service and send it electronically to GTE's data center for processing. Upon receipt, GTE will match the LSR with the service order suspended in GTE's system, and if there is a match, GTE will process the LSR. After the LSR is processed, GTE will transmit confirmation electronically to dPi Prepaid through the NDM that the LSR has been processed, providing a record of the telephone number and due date. dPi Prepaid will be required to submit the confirming LSR by 12:00 p.m. each day local time, as defined by the location of the service address. If dPi Prepaid fails to submit the LSR in a timely manner, the suspended LSR will be considered in jeopardy, at which time GTE will assign a new due date upon receipt of the delayed LSR for such customer requests and notify dPi Prepaid of the change. 1.1.5 Number assignments and due date schedules for services other than single line service and xxxx groups up to 12 lines will be assigned within approximately twenty-four (24) hours after GTE's receipt of the LSR using the standard Local Service Confirmation ("LSC") report sent electronically to dPi Prepaid over the NDM, thereby providing a record of the newly established due date. An exception would be a multi-line xxxx group for 12 lines or fewer. The other numbers then will be provided through the normal electronic confirmation process. 1.1.6 The processing of specifically requested telephone numbers (called "vanity numbers") is as follows. GTE will work with dPi Prepaid on a real time interface to process vanity numbers while dPiPrepaid's customer is still on the line. If a number solution can be established expeditiously, it will be done while the customer is still on the line. If extensive time will be required to find a solution, GTE service representatives will work with dPi Prepaid representatives off line as GTE would for its own customers. For all of this, the basic tariff guidelines for providing telephone numbers will be followed. 1.1.7 Once the order for resold service is established, it is moved for provisioning to the next system level. Here, GTE will validate and process the LSR to establish an account for dPi Prepaid and, if GTE continues to provide some residual services to the customer, GTE will maintain a GTE account. In GTE's system, GTE's account is called the Residual Account and dPiPrepaid's account is referred to as the dPi Prepaid Account. If any engineering for the service is necessary, the account would be distributed to the SSCC. Otherwise, it will be distributed for facility assignment. 1.1.8 With the account established and any engineering and facility assignment complete, GTE then will transmit electronically a record to GTE's CZT field personnel if physical interconnection or similar activity is required. The CZTs will provision the service and then electronically confirm such provision in the SOLAR/SORCES system when completed. The accounts then will be transmitted to GTE's Customer Billing Services System ("CBSS"). GTE shall provide to dPi Prepaid a service completion report. Call records for actual service provided to dPiPrepaid's customers on GTE facilities will be transmitted from GTE's switches through some usage rating systems (BIP, UMS), screened and eventually delivered to CBSS for the generation of bills. 1.1.9 CBSS is a different system than CABS, and it is the one that GTE will utilize to produce the required bills for resold services and local number portability. CBSS will create a xxxx to dPi Prepaid for resold services along with a summary xxxx master. Daily unrated records for intraLATA toll usage and local usage (incollect usage data will be provided on rated basis) on dPiPrepaid's accounts will be generated and transmitted electronically to dPiPrepaid. 1.1.10 On resold accounts, GTE will provide usage in EMR format per existing file exchange schedules. The usage billing will be in agreed upon level of detail for dPi Prepaid to issue a xxxx to its end users. 1.1.11 GTE will provide dPi Prepaid with detailed monthly billing information in a paper format until an agreed upon Electronic Data Interchange 811 electronic xxxx format is operational. 1.1.12 State or sub-state level billing will include up to ten (10) summary xxxx accounts. 1.1.13 GTE accepts dPiPrepaid's control reports and agrees to utilize industry standard return codes for unbillable messages. Transmission will occur via the NDM. Tape data will conform to Attachment "A" of the LRDTR. Data will be delivered Monday through Friday except for Holidays as agreed. Data packages will be tracked by invoice sequencing criteria. GTE contacts will be provided for sending/receiving usage files. 1.1.14 GTE will retain data backup for 45 Business Days. To the extent dPi requires a longer this retention periodis exclusively for Prepaid, dPi Prepaid shall reimburse GTE for all expenses related to that this retention. 1.1.15 In addition to the LSR delivery process, dPi Prepaid will distribute DA directory assistance and directory listing information (together sometimes referred to hereafter as "DA/DL information") to GTE via the LSR ordering process over the NDM. GTE will provide listings service via its "listing continuity" offering. 1.1.16 Charges and credits for PIC changes ordered via an LSR will appear on the resale xxxx. As dPi Prepaid places a request for a PIC change via LSR, the billing will be made on dPi Prepaid account associated with each individual end user. GTE will process all PIC changes from IXCs that are received for dPi Prepaid end users by rejecting back to the IXC with the dPi Prepaid OCN. Detail is provided so that dPi Prepaid can identify the specific charges for rebilling to its end user.