Technical Requirements. 7.3.2.1 BellSouth will offer to AFN any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process AFN’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by AFN, BellSouth shall provide AFN with a list of the customer data items, which AFN would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of AFN data to the LIDB shall be solely at the direction of AFN. Such direction from AFN will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN data upon AFN’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN customer records will be missing from LIDB, as measured by AFN audits. BellSouth will audit AFN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN within one (1) business day of audit. Once reconciled records are received back from AFN, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN in writing. 7.3.2.13 BellSouth shall provide AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN the screening information associated with LIDB Data Screening of AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Interconnection Agreement, Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 15.4.2.1 BellSouth shall process AFNITC^DeltaCom’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ITC^DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 15.4.2.2 Within two (2) weeks after a request by AFNITC^DeltaCom, BellSouth shall provide AFN ITC^DeltaCom with a list of the customer data items, items which AFN ITC^DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 15.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 15.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 15.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 15.4.2.6 All additions, updates and deletions of AFN ITC^DeltaCom data to the LIDB shall be solely at the direction of AFNITC^DeltaCom. Such direction from AFN ITC^DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 15.4.2.7 BellSouth shall provide priority updates to LIDB for AFN ITC^DeltaCom data upon AFNITC^DeltaCom’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 15.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ITC^DeltaCom customer records will be missing from LIDB, as measured by AFN ITC^DeltaCom audits. BellSouth will audit AFN ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated AFN ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to AFN ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from AFNITC^DeltaCom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more 4 States Attachment 2 Clean 12-17-01 than 500 records are received, BellSouth will contact AFN ITC^DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 15.4.2.9 BellSouth shall perform backup and recovery of all of AFNITC^DeltaCom’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 15.4.2.10 BellSouth shall provide AFN ITC^DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN ITC^DeltaCom and BellSouth.
7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of AFN ITC^DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN ITC^DeltaCom in writing.
7.3.2.13 15.4.2.12 BellSouth shall provide AFN ITC^DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ITC^DeltaCom the screening information associated with LIDB Data Screening of AFN ITC^DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ITC^DeltaCom under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119.
7.3.2.14 15.4.2.13 BellSouth shall accept queries to LIDB associated with AFN ITC^DeltaCom customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 15.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 15.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Clec Agreement, Clec Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN PLI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNPLI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN PLI what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNPLI, BellSouth shall provide AFN PLI with a list of the customer data items, which AFN PLI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN PLI data to the LIDB shall be solely at the direction of AFNPLI. Such direction from AFN PLI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN data upon AFN▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN PLI customer records will be missing from LIDB, as measured by AFN PLI audits. BellSouth will audit AFN PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN PLI within one (1) business day of audit. Once reconciled records are received back from AFNPLI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN PLI to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNPLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN PLI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN PLI in writing.
7.3.2.13 BellSouth shall provide AFN PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN PLI the screening information associated with LIDB Data Screening of AFN PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN PLI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN PLI customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Interconnection Agreement, Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN <customer_short_name> any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFN<customer_short_name>’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN <customer_short_name> what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFN<customer_short_name>, BellSouth shall provide AFN <customer_short_name> with a list of the customer data items, which AFN <customer_short_name> would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN <customer_short_name> data to the LIDB shall be solely at the direction of AFN<customer_short_name>. Such direction from AFN <customer_short_name> will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN <customer_short_name> data upon AFN<customer_short_name>’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN <customer_short_name> customer records will be missing from LIDB, as measured by AFN <customer_short_name> audits. BellSouth will audit AFN <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN <customer_short_name> contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from AFN<customer_short_name>, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN <customer_short_name> to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN<customer_short_name>’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN <customer_short_name> with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN <customer_short_name> and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN <customer_short_name> data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide AFN <customer_short_name> performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN <customer_short_name> the screening information associated with LIDB Data Screening of AFN <customer_short_name> data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN <customer_short_name> under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN <customer_short_name> customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Interconnection Agreement, Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN US LEC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 13.4.2.1 BellSouth shall process AFNUS LEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN US LEC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 13.4.2.2 Within two (2) weeks after a request by AFNUS LEC, BellSouth shall provide AFN US LEC with a list of the customer data items, items which AFN US LEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 13.4.2.6 All additions, updates and deletions of AFN US LEC data to the LIDB shall be solely at the direction of AFNUS LEC. Such direction from AFN US LEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for AFN US LEC data upon AFNUS LEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN US LEC customer records will be missing from LIDB, as measured by AFN US LEC audits. BellSouth will audit AFN US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated AFN US LEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to AFN US LEC within one (1) business day of audit. Once reconciled records are received back from AFNUS LEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN US LEC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of AFNUS LEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 13.4.2.10 BellSouth shall provide AFN US LEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN US LEC and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of AFN US LEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN US LEC in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide AFN US LEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN US LEC the screening information associated with LIDB Data Screening of AFN US LEC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN US LEC under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119.
7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with AFN US LEC customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Clec Agreement, Clec Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN MRC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNMRC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN MRC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNMRC, BellSouth shall provide AFN MRC with a list of the customer data items, which AFN MRC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN MRC data to the LIDB shall be solely at the direction of AFNMRC. Such direction from AFN MRC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN MRC data upon AFNMRC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN MRC customer records will be missing from LIDB, as measured by AFN MRC audits. BellSouth will audit AFN MRC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN MRC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN MRC within one (1) business day of audit. Once reconciled records are received back from AFNMRC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN MRC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNMRC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN MRC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN MRC and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN MRC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN MRC in writing.
7.3.2.13 BellSouth shall provide AFN MRC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN MRC the screening information associated with LIDB Data Screening of AFN MRC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN MRC under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN MRC customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Interconnection Agreement, Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNITC^DeltaCom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ITC^DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNITC^DeltaCom, BellSouth shall provide AFN ITC^DeltaCom with a list of the customer data items, which AFN ITC^DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN ITC^DeltaCom data to the LIDB shall be solely at the direction of AFNITC^DeltaCom. Such direction from AFN ITC^DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN ITC^DeltaCom data upon AFNITC^DeltaCom’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ITC^DeltaCom customer records will be missing from LIDB, as measured by AFN ITC^DeltaCom audits. BellSouth will audit AFN ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from AFNITC^DeltaCom, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN ITC^DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNITC^DeltaCom’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN ITC^DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ITC^DeltaCom and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN ITC^DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ITC^DeltaCom in writing.
7.3.2.13 BellSouth shall provide AFN ITC^DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ITC^DeltaCom the screening information associated with LIDB Data Screening of AFN ITC^DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ITC^DeltaCom under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN ITC^DeltaCom customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 2 contracts
Sources: Interconnection Agreement, Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Micro-Comm what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNMicro-Comm, BellSouth shall provide AFN Micro-Comm with a list of the customer data items, which AFN Micro-Comm would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Micro-Comm data to the LIDB shall be solely at the direction of AFNMicro-Comm. Such direction from AFN Micro-Comm will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Micro-Comm data upon AFNMicro-Comm’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Micro- Comm customer records will be missing from LIDB, as measured by AFN Micro-Comm audits. BellSouth will audit AFN Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Micro-Comm within one (1) business day of audit. Once reconciled records are received back from AFNMicro-Comm, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Micro-Comm to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNMicro-Comm’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Micro-Comm with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Micro-Comm and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Micro-Comm data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Micro-Comm in writing.
7.3.2.13 BellSouth shall provide AFN Micro-Comm performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Micro-Comm the screening information associated with LIDB Data Screening of AFN Micro-Comm data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Micro-Comm under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Micro-Comm customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Symtelco any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNSymtelco’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Symtelco what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNSymtelco, BellSouth shall provide AFN Symtelco with a list of the customer data items, which AFN Symtelco would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Symtelco data to the LIDB shall be solely at the direction of AFNSymtelco. Such direction from AFN Symtelco will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Symtelco data upon AFNSymtelco’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Symtelco customer records will be missing from LIDB, as measured by AFN Symtelco audits. BellSouth will audit AFN Symtelco records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Symtelco contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Symtelco within one (1) business day of audit. Once reconciled records are received back from AFNSymtelco, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Symtelco to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNSymtelco’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Symtelco with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Symtelco and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Symtelco data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Symtelco in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Symtelco performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Symtelco at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Symtelco the screening information associated with LIDB Data Screening of AFN Symtelco data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Symtelco under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Symtelco customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN EZ Phone any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNEZ Phone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN EZ Phone what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNEZ Phone, BellSouth shall provide AFN EZ Phone with a list of the customer data items, which AFN EZ Phone would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN EZ Phone data to the LIDB shall be solely at the direction of AFNEZ Phone. Such direction from AFN EZ Phone will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN EZ Phone data upon AFNEZ Phone’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN EZ Phone customer records will be missing from LIDB, as measured by AFN EZ Phone audits. BellSouth will audit AFN EZ Phone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN EZ Phone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN EZ Phone within one (1) business day of audit. Once reconciled records are received back from AFNEZ Phone, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN EZ Phone to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNEZ Phone’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN EZ Phone with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN EZ Phone and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN EZ Phone data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN EZ Phone in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN EZ Phone performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN EZ Phone at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN EZ Phone the screening information associated with LIDB Data Screening of AFN EZ Phone data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN EZ Phone under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN EZ Phone customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Clearwave Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Clearwave Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNClearwave Communications, BellSouth shall provide AFN Clearwave Communications with a list of the customer data items, which AFN Clearwave Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Clearwave Communications data to the LIDB shall be solely at the direction of AFNClearwave Communications. Such direction from AFN Clearwave Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Clearwave Communications data upon AFNClearwave Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Clearwave Communications customer records will be missing from LIDB, as measured by AFN Clearwave Communications audits. BellSouth will audit AFN Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from AFNClearwave Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Clearwave Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNClearwave Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Clearwave Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Clearwave Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Clearwave Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Clearwave Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Clearwave Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Clearwave Communications the screening information associated with LIDB Data Screening of AFN Clearwave Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Clearwave Communications under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Clearwave Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Clearwave Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Clearwave Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNClearwave Communications, BellSouth shall provide AFN Clearwave Communications with a list of the customer data items, which AFN Clearwave Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Clearwave Communications data to the LIDB shall be solely at the direction of AFNClearwave Communications. Such direction from AFN Clearwave Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Clearwave Communications data upon AFNClearwave Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Clearwave Communications customer records will be missing from LIDB, as measured by AFN Clearwave Communications audits. BellSouth will audit AFN Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from AFNClearwave Communications, BellSouth ▇▇▇▇▇▇▇▇▇ will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN Clearwave Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNClearwave Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Clearwave Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Clearwave Communications and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Clearwave Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Clearwave Communications in writing.
7.3.2.13 BellSouth shall provide AFN Clearwave Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Clearwave Communications the screening information associated with LIDB Data Screening of AFN Clearwave Communications data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Clearwave Communications under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Clearwave Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN PBT any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNPBT’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN PBT what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNPBT, BellSouth shall provide AFN PBT with a list of the customer data items, which AFN PBT would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN PBT data to the LIDB shall be solely at the direction of AFNPBT. Such direction from AFN PBT will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN PBT data upon AFNPBT’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN PBT customer records will be missing from LIDB, as measured by AFN PBT audits. BellSouth will audit AFN PBT records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN PBT contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN PBT within one (1) business day of audit. Once reconciled records are received back from AFNPBT, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN PBT to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNPBT’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN PBT with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN PBT and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN PBT data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN PBT in writing.
7.3.2.13 BellSouth shall provide AFN PBT performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN PBT at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN PBT the screening information associated with LIDB Data Screening of AFN PBT data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN PBT under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN PBT customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN AmTel any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNAmTel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN AmTel what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNAmTel, BellSouth shall provide AFN AmTel with a list of the customer data items, which AFN AmTel would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN AmTel data to the LIDB shall be solely at the direction of AFNAmTel. Such direction from AFN AmTel will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN AmTel data upon AFNAmTel’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN AmTel customer records will be missing from LIDB, as measured by AFN AmTel audits. BellSouth will audit AFN AmTel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN AmTel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN AmTel within one (1) business day of audit. Once reconciled records are received back from AFNAmTel, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN AmTel to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNAmTel’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN AmTel with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN AmTel and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN AmTel data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN AmTel in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN AmTel performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN AmTel at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN AmTel the screening information associated with LIDB Data Screening of AFN AmTel data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN AmTel under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN AmTel customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN FeroNetworks what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNFeroNetworks, BellSouth shall provide AFN FeroNetworks with a list of the customer data items, which AFN FeroNetworks would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN FeroNetworks data to the LIDB shall be solely at the direction of AFNFeroNetworks. Such direction from AFN FeroNetworks will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN FeroNetworks data upon AFNFeroNetworks’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN FeroNetworks customer records will be missing from LIDB, as measured by AFN FeroNetworks audits. BellSouth will audit AFN FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN FeroNetworks within one (1) business day of audit. Once reconciled records are received back from AFNFeroNetworks, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN FeroNetworks to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNFeroNetworks’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN FeroNetworks with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN FeroNetworks and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN FeroNetworks data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN FeroNetworks in writing.
7.3.2.13 BellSouth shall provide AFN FeroNetworks performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN FeroNetworks the screening information associated with LIDB Data Screening of AFN FeroNetworks data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN FeroNetworks under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN FeroNetworks customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNNex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Nex-Phon what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNNex-Phon, BellSouth shall provide AFN Nex- Phon with a list of the customer data items, which AFN Nex-Phon would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Nex-Phon data to the LIDB shall be solely at the direction of AFNNex-Phon. Such direction from AFN Nex-Phon will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Nex-Phon data upon AFNNex- Phon’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Nex-Phon customer records will be missing from LIDB, as measured by AFN Nex-Phon audits. BellSouth will audit AFN Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Nex-Phon within one (1) business day of audit. Once reconciled records are received back from AFNNex-Phon, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Nex-Phon to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNNex-Phon’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Nex-Phon with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Nex-Phon and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Nex-Phon data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Nex-Phon in writing.
7.3.2.13 BellSouth shall provide AFN Nex-Phon performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Nex-Phon the screening information associated with LIDB Data Screening of AFN Nex-Phon data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Nex-Phon under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Nex-Phon customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Rent-A-Line any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNRent-A-Line’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Rent-A-Line what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNRent-A-Line, BellSouth shall provide AFN Rent-A-Line with a list of the customer data items, which AFN Rent-A-Line would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Rent-A-Line data to the LIDB shall be solely at the direction of AFNRent-A-Line. Such direction from AFN Rent-A-Line will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Rent-A-Line data upon AFNRent- A-Line’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Rent-A- Line customer records will be missing from LIDB, as measured by AFN Rent-A-Line audits. BellSouth will audit AFN Rent-A-Line records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Rent-A-Line contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Rent-A-Line within one (1) business day of audit. Once reconciled records are received back from AFNRent-A-Line, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Rent- A-Line to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNRent-A-Line’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Rent-A-Line with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Rent-A-Line and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Rent-A-Line data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Rent-A-Line in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Rent-A-Line performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Rent-A-Line at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Rent-A-Line the screening information associated with LIDB Data Screening of AFN Rent-A-Line data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Rent-A-Line under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Rent-A-Line customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCBX One-Stop, BellSouth shall provide AFN CBX One-Stop with a list of the customer data items, which AFN CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN CBX One-Stop data to the LIDB shall be solely at the direction of AFNCBX One-Stop. Such direction from AFN CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN CBX One-Stop data upon AFNCBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CBX One-Stop customer records will be missing from LIDB, as measured by AFN CBX One- Stop audits. BellSouth will audit AFN CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from AFNCBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN CBX One-Stop and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN CBX One-Stop in writing.
7.3.2.13 BellSouth shall provide AFN CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CBX One-Stop the screening information associated with LIDB Data Screening of AFN CBX One-Stop data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CBX One-Stop under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN CBX One-Stop customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN DPI Teleconnect any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNDPI Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN DPI Teleconnect what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNDPI Teleconnect, BellSouth shall provide AFN DPI Teleconnect with a list of the customer data items, which AFN DPI Teleconnect would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN DPI Teleconnect data to the LIDB shall be solely at the direction of AFNDPI Teleconnect. Such direction from AFN DPI Teleconnect will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN DPI Teleconnect data upon AFNDPI Teleconnect’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN DPI Teleconnect customer records will be missing from LIDB, as measured by AFN DPI Teleconnect audits. BellSouth will audit AFN DPI Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN DPI Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN DPI Teleconnect within one (1) business day of audit. Once reconciled records are received back from AFNDPI Teleconnect, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN DPI Teleconnect to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNDPI Teleconnect’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN DPI Teleconnect with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN DPI Teleconnect and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN DPI Teleconnect data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN DPI Teleconnect in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN DPI Teleconnect performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN DPI Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN DPI Teleconnect the screening information associated with LIDB Data Screening of AFN DPI Teleconnect data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN DPI Teleconnect under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN DPI Teleconnect customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN CCI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CCI what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCCI, BellSouth shall provide AFN CCI with a list of the customer data items, which AFN CCI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN CCI data to the LIDB shall be solely at the direction of AFNCCI. Such direction from AFN CCI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN CCI data upon AFNCCI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CCI customer records will be missing from LIDB, as measured by AFN CCI audits. BellSouth will audit AFN CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN CCI within one (1) business day of audit. Once reconciled records are received back from AFNCCI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN CCI to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCCI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN CCI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN CCI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN CCI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN CCI in writing.
7.3.2.13 BellSouth shall provide AFN CCI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CCI the screening information associated with LIDB Data Screening of AFN CCI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CCI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN CCI customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN ▇▇▇▇▇▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFN▇▇▇▇▇▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ▇▇▇▇▇▇▇▇.▇▇▇ what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFN▇▇▇▇▇▇▇▇.▇▇▇, BellSouth shall provide AFN ▇▇▇▇▇▇▇▇.▇▇▇ with a list of the customer data items, which AFN ▇▇▇▇▇▇▇▇.▇▇▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN ▇▇▇▇▇▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of AFN▇▇▇▇▇▇▇▇.▇▇▇. Such direction from AFN ▇▇▇▇▇▇▇▇.▇▇▇ will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN ▇▇▇▇▇▇▇▇.▇▇▇ data upon AFN▇▇▇▇▇▇▇▇.▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ▇▇▇▇▇▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by AFN ▇▇▇▇▇▇▇▇.▇▇▇ audits. BellSouth will audit AFN ▇▇▇▇▇▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ▇▇▇▇▇▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN ▇▇▇▇▇▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from AFN▇▇▇▇▇▇▇▇.▇▇▇, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN ▇▇▇▇▇▇▇▇.▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN in writing.
7.3.2.13 BellSouth shall provide AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN the screening information associated with LIDB Data Screening of AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN MTS Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNMTS Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN MTS Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNMTS Communications, BellSouth shall provide AFN MTS Communications with a list of the customer data items, which AFN MTS Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN MTS Communications data to the LIDB shall be solely at the direction of AFNMTS Communications. Such direction from AFN MTS Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN MTS Communications data upon AFNMTS Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN MTS Communications customer records will be missing from LIDB, as measured by AFN MTS Communications audits. BellSouth will audit AFN MTS Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN MTS Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN MTS Communications within one (1) business day of audit. Once reconciled records are received back from AFNMTS Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN MTS Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNMTS Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN MTS Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN MTS Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN MTS Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN MTS Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN MTS Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN MTS Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN MTS Communications the screening information associated with LIDB Data Screening of AFN MTS Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN MTS Communications under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN MTS Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Covad any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Covad what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFN▇▇▇▇▇, BellSouth shall provide AFN Covad with a list of the customer data items, which AFN Covad would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Covad data to the LIDB shall be solely at the direction of AFNCovad. Such direction from AFN Covad will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Covad data upon AFNCovad’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Covad customer records will be missing from LIDB, as measured by AFN Covad audits. BellSouth will audit AFN Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Covad within one (1) business day of audit. Once reconciled records are received back from AFNCovad, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN ▇▇▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCovad’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Covad with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Covad and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Covad data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ▇▇▇▇▇ in writing.
7.3.2.13 BellSouth shall provide AFN Covad performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Covad the screening information associated with LIDB Data Screening of AFN Covad data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Covad under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Covad customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN FLATEL what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNFLATEL, BellSouth shall provide AFN FLATEL with a list of the customer data items, which AFN FLATEL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN FLATEL data to the LIDB shall be solely at the direction of AFNFLATEL. Such direction from AFN FLATEL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN FLATEL data upon AFNFLATEL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN FLATEL customer records will be missing from LIDB, as measured by AFN FLATEL audits. BellSouth will audit AFN FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN FLATEL within one (1) business day of audit. Once reconciled records are received back from AFNFLATEL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN FLATEL to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNFLATEL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN FLATEL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN FLATEL and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN FLATEL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN FLATEL in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN FLATEL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN FLATEL the screening information associated with LIDB Data Screening of AFN FLATEL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN FLATEL under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN FLATEL customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Advantage Group any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNAdvantage Group’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Advantage Group what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNAdvantage Group, BellSouth shall provide AFN Advantage Group with a list of the customer data items, which AFN Advantage Group would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Advantage Group data to the LIDB shall be solely at the direction of AFNAdvantage Group. Such direction from AFN Advantage Group will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Advantage Group data upon AFNAdvantage Group’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Advantage Group customer records will be missing from LIDB, as measured by AFN Advantage Group audits. BellSouth will audit AFN Advantage Group records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Advantage Group contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Advantage Group within one (1) business day of audit. Once reconciled records are received back from AFNAdvantage Group, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Advantage Group to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNAdvantage Group’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Advantage Group with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Advantage Group and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Advantage Group data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Advantage Group in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Advantage Group performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Advantage Group at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Advantage Group the screening information associated with LIDB Data Screening of AFN Advantage Group data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Advantage Group under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Advantage Group customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Pilgrim Telephone any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNPilgrim Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Pilgrim Telephone what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNPilgrim Telephone, BellSouth shall provide AFN Pilgrim Telephone with a list of the customer data items, which AFN Pilgrim Telephone would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Pilgrim Telephone data to the LIDB shall be solely at the direction of AFNPilgrim Telephone. Such direction from AFN Pilgrim Telephone will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Pilgrim Telephone data upon AFNPilgrim Telephone’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Pilgrim Telephone customer records will be missing from LIDB, as measured by AFN Pilgrim Telephone audits. BellSouth will audit AFN Pilgrim Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Pilgrim Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Pilgrim Telephone within one (1) business day of audit. Once reconciled records are received back from AFNPilgrim Telephone, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN Pilgrim Telephone to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNPilgrim Telephone’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Pilgrim Telephone with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Pilgrim Telephone and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Pilgrim Telephone data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Pilgrim Telephone in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Pilgrim Telephone performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Pilgrim Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Pilgrim Telephone the screening information associated with LIDB Data Screening of AFN Pilgrim Telephone data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Pilgrim Telephone under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Pilgrim Telephone customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN FeroNetworks what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNFeroNetworks, BellSouth shall provide AFN FeroNetworks with a list of the customer data items, which AFN FeroNetworks would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN FeroNetworks data to the LIDB shall be solely at the direction of AFNFeroNetworks. Such direction from AFN FeroNetworks will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN FeroNetworks data upon AFNFeroNetworks’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN FeroNetworks customer records will be missing from LIDB, as measured by AFN FeroNetworks audits. BellSouth will audit AFN FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN FeroNetworks within one (1) business day of audit. Once reconciled records are received back from AFNFeroNetworks, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN FeroNetworks to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNFeroNetworks’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN FeroNetworks with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN FeroNetworks and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN FeroNetworks data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN FeroNetworks in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN FeroNetworks performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN FeroNetworks the screening information associated with LIDB Data Screening of AFN FeroNetworks data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN FeroNetworks under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN FeroNetworks customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN ONS any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNONS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ONS what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNONS, BellSouth shall provide AFN ONS with a list of the customer data items, which AFN ONS would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN ONS data to the LIDB shall be solely at the direction of AFNONS. Such direction from AFN ONS will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN ONS data upon AFNONS’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ONS customer records will be missing from LIDB, as measured by AFN ONS audits. BellSouth will audit AFN ONS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ONS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN ONS within one (1) business day of audit. Once reconciled records are received back from AFNONS, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN ONS to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNONS’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN ONS with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ONS and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN ONS data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ONS in writing.
7.3.2.13 BellSouth shall provide AFN ONS performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ONS at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ONS the screening information associated with LIDB Data Screening of AFN ONS data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ONS under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN ONS customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Seven Bridges any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFN’s Seven ▇▇▇▇▇▇▇’▇ customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Seven Bridges what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNSeven Bridges, BellSouth shall provide AFN Seven Bridges with a list of the customer data items, which AFN Seven Bridges would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Seven Bridges data to the LIDB shall be solely at the direction of AFNSeven Bridges. Such direction from AFN Seven Bridges will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Seven Bridges data upon AFN’s Seven ▇▇▇▇▇▇▇’▇ request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Seven Bridges customer records will be missing from LIDB, as measured by AFN Seven Bridges audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN Seven Bridges records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Seven Bridges contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Seven Bridges within one (1) business day of audit. Once reconciled records are received back from AFNSeven Bridges, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN Seven ▇▇▇▇▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s Seven ▇▇▇▇▇▇▇’▇ data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Seven Bridges with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Seven Bridges and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Seven Bridges data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Seven ▇▇▇▇▇▇▇ in writing.
7.3.2.13 BellSouth shall provide AFN Seven Bridges performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Seven Bridges at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Seven Bridges the screening information associated with LIDB Data Screening of AFN Seven Bridges data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Seven Bridges under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Seven Bridges customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Starlink any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNStarlink’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Starlink what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNStarlink, BellSouth shall provide AFN Starlink with a list of the customer data items, which AFN Starlink would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Starlink data to the LIDB shall be solely at the direction of AFNStarlink. Such direction from AFN Starlink will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Starlink data upon AFNStarlink’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Starlink customer records will be missing from LIDB, as measured by AFN Starlink audits. BellSouth will audit AFN Starlink records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Starlink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Starlink within one (1) business day of audit. Once reconciled records are received back from AFNStarlink, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Starlink to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNStarlink’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Starlink with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Starlink and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Starlink data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Starlink in writing.
7.3.2.13 BellSouth shall provide AFN Starlink performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Starlink at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Starlink the screening information associated with LIDB Data Screening of AFN Starlink data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Starlink under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Starlink customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN OnePoint any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNOnePoint’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN OnePoint what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNOnePoint, BellSouth shall provide AFN OnePoint with a list of the customer data items, which AFN OnePoint would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN OnePoint data to the LIDB shall be solely at the direction of AFNOnePoint. Such direction from AFN OnePoint will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN OnePoint data upon AFNOnePoint’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN OnePoint customer records will be missing from LIDB, as measured by AFN OnePoint audits. BellSouth will audit AFN OnePoint records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN OnePoint contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN OnePoint within one (1) business day of audit. Once reconciled records are received back from AFNOnePoint, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN OnePoint to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNOnePoint’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN OnePoint with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN OnePoint and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN OnePoint data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN OnePoint in writing.
7.3.2.13 BellSouth shall provide AFN OnePoint performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN OnePoint at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN OnePoint the screening information associated with LIDB Data Screening of AFN OnePoint data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN OnePoint under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN OnePoint customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Nexus any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNNexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Nexus what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNNexus, BellSouth shall provide AFN Nexus with a list of the customer data items, which AFN Nexus would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Nexus data to the LIDB shall be solely at the direction of AFNNexus. Such direction from AFN Nexus will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Nexus data upon AFNNexus’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Nexus customer records will be missing from LIDB, as measured by AFN Nexus audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Nexus within one (1) business day of audit. Once reconciled records are received back from AFNNexus, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN Nexus to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNNexus’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Nexus with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Nexus and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Nexus data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Nexus in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Nexus performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Nexus the screening information associated with LIDB Data Screening of AFN Nexus data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Nexus under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Nexus customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN GSC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNGSC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN GSC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNGSC, BellSouth shall provide AFN GSC with a list of the customer data items, which AFN GSC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN GSC data to the LIDB shall be solely at the direction of AFNGSC. Such direction from AFN GSC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN GSC data upon AFNGSC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN GSC customer records will be missing from LIDB, as measured by AFN GSC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN GSC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN GSC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN GSC within one (1) business day of audit. Once reconciled records are received back from AFNGSC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN GSC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNGSC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN GSC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN GSC and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN GSC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN GSC in writing.
7.3.2.13 BellSouth shall provide AFN GSC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN GSC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN GSC the screening information associated with LIDB Data Screening of AFN GSC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN GSC under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN GSC customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Comm South any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNComm South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Comm South what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNComm South, BellSouth shall provide AFN Comm South with a list of the customer data items, which AFN Comm South would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Comm South data to the LIDB shall be solely at the direction of AFNComm South. Such direction from AFN Comm South will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Comm South data upon AFNComm South’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Comm South customer records will be missing from LIDB, as measured by AFN Comm South audits. BellSouth will audit AFN Comm South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Comm South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Comm South within one (1) business day of audit. Once reconciled records are received back from AFNComm South, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Comm South to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNComm South’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Comm South with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Comm South and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Comm South data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Comm South in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Comm South performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Comm South at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Comm South the screening information associated with LIDB Data Screening of AFN Comm South data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Comm South under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Comm South customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Preferred any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNPreferred’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Preferred what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNPreferred, BellSouth shall provide AFN Preferred with a list of the customer data items, which AFN Preferred would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Preferred data to the LIDB shall be solely at the direction of AFNPreferred. Such direction from AFN Preferred will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Preferred data upon AFNPreferred’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Preferred customer records will be missing from LIDB, as measured by AFN Preferred audits. BellSouth will audit AFN Preferred records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Preferred contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Preferred within one (1) business day of audit. Once reconciled records are received back from AFNPreferred, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Preferred to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNPreferred’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Preferred with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Preferred and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Preferred data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Preferred in writing.
7.3.2.13 BellSouth shall provide AFN Preferred performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Preferred at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Preferred the screening information associated with LIDB Data Screening of AFN Preferred data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Preferred under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Preferred customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN TeleConex any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNTeleConex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN TeleConex what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNTeleConex, BellSouth shall provide AFN TeleConex with a list of the customer data items, which AFN TeleConex would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN TeleConex data to the LIDB shall be solely at the direction of AFNTeleConex. Such direction from AFN TeleConex will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN TeleConex data upon AFNTeleConex’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN TeleConex customer records will be missing from LIDB, as measured by AFN TeleConex audits. BellSouth will audit AFN TeleConex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN TeleConex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN TeleConex within one (1) business day of audit. Once reconciled records are received back from AFNTeleConex, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN TeleConex to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNTeleConex’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN TeleConex with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN TeleConex and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN TeleConex data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN TeleConex in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN TeleConex performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN TeleConex at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN TeleConex the screening information associated with LIDB Data Screening of AFN TeleConex data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN TeleConex under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN TeleConex customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Clec Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN ITC/\DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 15.4.2.1 BellSouth shall process AFN’s customer ITC/\DeltaCom's Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ITC/\DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 15.4.2.2 Within two (2) weeks after a request by AFNITC/\DeltaCom, BellSouth shall provide AFN ITC/\DeltaCom with a list of the customer data items, items which AFN ITC/\DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 15.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 15.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 15.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 15.4.2.6 All additions, updates and deletions of AFN ITC/\DeltaCom data to the LIDB shall be solely at the direction of AFNITC/\DeltaCom. Such direction from AFN ITC/\DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 15.4.2.7 BellSouth shall provide priority updates to LIDB for AFN ITC/\DeltaCom data upon AFN’s ITC/\DeltaCom's request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 15.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ITC/\DeltaCom customer records will be missing from LIDB, as measured by AFN ITC/\DeltaCom audits. BellSouth will audit AFN ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated AFN ITC/\DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to AFN ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from AFNITC/\DeltaCom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN ITC/\DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 15.4.2.9 BellSouth shall perform backup and recovery of all of AFN’s ITC/\DeltaCom's data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 15.4.2.10 BellSouth shall provide AFN ITC/\DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN ITC/\DeltaCom and BellSouth.
7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of AFN ITC/\DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN ITC/\DeltaCom in writing.
7.3.2.13 15.4.2.12 BellSouth shall provide AFN ITC/\DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ITC/\DeltaCom the screening information associated with LIDB Data Screening of AFN ITC/\DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ITC/\DeltaCom under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119.
7.3.2.14 15.4.2.13 BellSouth shall accept queries to LIDB associated with AFN ITC/\DeltaCom customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 15.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 15.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN EPICUS any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNEPICUS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN EPICUS what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNEPICUS, BellSouth shall provide AFN EPICUS with a list of the customer data items, which AFN EPICUS would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN EPICUS data to the LIDB shall be solely at the direction of AFNEPICUS. Such direction from AFN EPICUS will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN EPICUS data upon AFNEPICUS’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN EPICUS customer records will be missing from LIDB, as measured by AFN EPICUS audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN EPICUS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN EPICUS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN EPICUS within one (1) business day of audit. Once reconciled records are received back from AFNEPICUS, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN EPICUS to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNEPICUS’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN EPICUS with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN EPICUS and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN EPICUS data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN EPICUS in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN EPICUS performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN EPICUS at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN EPICUS the screening information associated with LIDB Data Screening of AFN EPICUS data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN EPICUS under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN EPICUS customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN BTI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNBTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN BTI what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNBTI, BellSouth shall provide AFN BTI with a list of the customer data items, which AFN BTI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN BTI data to the LIDB shall be solely at the direction of AFNBTI. Such direction from AFN BTI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN BTI data upon AFNBTI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN BTI customer records will be missing from LIDB, as measured by AFN BTI audits. BellSouth will audit AFN BTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN BTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN BTI within one (1) business day of audit. Once reconciled records are received back from AFNBTI, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN BTI to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNBTI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN BTI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN BTI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN BTI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN BTI in writing.
7.3.2.13 BellSouth shall provide AFN BTI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN BTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN BTI the screening information associated with LIDB Data Screening of AFN BTI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN BTI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN BTI customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN U-Dial any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNU-Dial’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN U-Dial what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNU-Dial, BellSouth shall provide AFN U-Dial with a list of the customer data items, which AFN U-Dial would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN U-Dial data to the LIDB shall be solely at the direction of AFNU-Dial. Such direction from AFN U-Dial will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN U-Dial data upon AFNU-Dial’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN U-Dial customer records will be missing from LIDB, as measured by AFN U-Dial audits. BellSouth will audit AFN U-Dial records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN U-Dial contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN U-Dial within one (1) business day of audit. Once reconciled records are received back from AFNU-Dial, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN U-Dial to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNU-Dial’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN U-Dial with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN U-Dial and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN U-Dial data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN U-Dial in writing.
7.3.2.13 BellSouth shall provide AFN U-Dial performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN U-Dial at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN U-Dial the screening information associated with LIDB Data Screening of AFN U-Dial data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN U-Dial under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN U-Dial customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Gateway any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNGateway’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Gateway what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNGateway, BellSouth shall provide AFN Gateway with a list of the customer data items, which AFN Gateway would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Gateway data to the LIDB shall be solely at the direction of AFNGateway. Such direction from AFN Gateway will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Gateway data upon AFNGateway’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Gateway customer records will be missing from LIDB, as measured by AFN Gateway audits. BellSouth will audit AFN Gateway records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Gateway contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Gateway within one (1) business day of audit. Once reconciled records are received back from AFNGateway, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Gateway to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNGateway’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Gateway with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Gateway and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Gateway data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Gateway in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Gateway performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Gateway at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Gateway the screening information associated with LIDB Data Screening of AFN Gateway data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Gateway under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Gateway customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN OptiLink any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 13.4.2.1 BellSouth shall process AFNOptiLink’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN OptiLink what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 13.4.2.2 Within two (2) weeks after a request by AFNOptiLink, BellSouth shall provide AFN OptiLink with a list of the customer data items, items which AFN OptiLink would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 13.4.2.6 All additions, updates and deletions of AFN OptiLink data to the LIDB shall be solely at the direction of AFNOptiLink. Such direction from AFN OptiLink will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for AFN OptiLink data upon AFNOptiLink’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN OptiLink customer records will be missing from LIDB, as measured by AFN OptiLink audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN OptiLink records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated AFN OptiLink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis- matches to AFN OptiLink within one (1) business day of audit. Once reconciled records are received back from AFNOptiLink, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN OptiLink to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of AFNOptiLink’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 13.4.2.10 BellSouth shall provide AFN OptiLink with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable time period as negotiated between AFN OptiLink and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of AFN OptiLink data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN OptiLink in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide AFN OptiLink performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN OptiLink at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN OptiLink the screening information associated with LIDB Data Screening of AFN OptiLink data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN OptiLink under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119.
7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with AFN OptiLink customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Quality Telephone any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNQuality Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Quality Telephone what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNQuality Telephone, BellSouth shall provide AFN Quality Telephone with a list of the customer data items, which AFN Quality Telephone would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Quality Telephone data to the LIDB shall be solely at the direction of AFNQuality Telephone. Such direction from AFN Quality Telephone will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Quality Telephone data upon AFNQuality Telephone’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Quality Telephone customer records will be missing from LIDB, as measured by AFN Quality Telephone audits. BellSouth will audit AFN Quality Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Quality Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Quality Telephone within one (1) business day of audit. Once reconciled records are received back from AFNQuality Telephone, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Quality Telephone to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNQuality Telephone’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Quality Telephone with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Quality Telephone and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Quality Telephone data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Quality Telephone in writing.
7.3.2.13 BellSouth shall provide AFN Quality Telephone performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Quality Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Quality Telephone the screening information associated with LIDB Data Screening of AFN Quality Telephone data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Quality Telephone under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Quality Telephone customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN FLATEL what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNFLATEL, BellSouth shall provide AFN FLATEL with a list of the customer data items, which AFN FLATEL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN FLATEL data to the LIDB shall be solely at the direction of AFNFLATEL. Such direction from AFN FLATEL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN FLATEL data upon AFNFLATEL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN FLATEL customer records will be missing from LIDB, as measured by AFN FLATEL audits. BellSouth will audit AFN FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN FLATEL within one (1) business day of audit. Once reconciled records are received back from AFNFLATEL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN FLATEL to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNFLATEL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN FLATEL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN FLATEL and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN FLATEL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN FLATEL in writing.
7.3.2.13 BellSouth shall provide AFN FLATEL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN FLATEL the screening information associated with LIDB Data Screening of AFN FLATEL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN FLATEL under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN FLATEL customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Micro-Comm what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNMicro-Comm, BellSouth shall provide AFN Micro-Comm with a list of the customer data items, which AFN Micro-Comm would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Micro-Comm data to the LIDB shall be solely at the direction of AFNMicro-Comm. Such direction from AFN Micro-Comm will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Micro-Comm data upon AFNMicro-Comm’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Micro- Comm customer records will be missing from LIDB, as measured by AFN Micro-Comm audits. BellSouth will audit AFN Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Micro-Comm within one (1) business day of audit. Once reconciled records are received back from AFNMicro-Comm, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Micro-Comm to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNMicro-Comm’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Micro-Comm with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Micro-Comm and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Micro-Comm data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Micro-Comm in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Micro-Comm performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Micro-Comm the screening information associated with LIDB Data Screening of AFN Micro-Comm data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Micro-Comm under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Micro-Comm customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN ICG any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNICG’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ICG what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNICG, BellSouth shall provide AFN ICG with a list of the customer data items, which AFN ICG would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN ICG data to the LIDB shall be solely at the direction of AFNICG. Such direction from AFN ICG will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN ICG data upon AFNICG’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ICG customer records will be missing from LIDB, as measured by AFN ICG audits. BellSouth will audit AFN ICG records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ICG contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN ICG within one (1) business day of audit. Once reconciled records are received back from AFNICG, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN ICG to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNICG’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN ICG with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ICG and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN ICG data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ICG in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN ICG performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ICG at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ICG the screening information associated with LIDB Data Screening of AFN ICG data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ICG under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN ICG customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN COMTECH21 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNCOMTECH21’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN COMTECH21 what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNCOMTECH21, BellSouth shall provide AFN COMTECH21 with a list of the customer data items, which AFN COMTECH21 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN COMTECH21 data to the LIDB shall be solely at the direction of AFNCOMTECH21. Such direction from AFN COMTECH21 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN COMTECH21 data upon AFNCOMTECH21’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN COMTECH21 customer records will be missing from LIDB, as measured by AFN COMTECH21 audits. BellSouth will audit AFN COMTECH21 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN COMTECH21 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN COMTECH21 within one (1) business day of audit. Once reconciled records are received back from AFNCOMTECH21, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN COMTECH21 to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNCOMTECH21’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN COMTECH21 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN COMTECH21 and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN COMTECH21 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN COMTECH21 in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN COMTECH21 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN COMTECH21 at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN COMTECH21 the screening information associated with LIDB Data Screening of AFN COMTECH21 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN COMTECH21 under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN COMTECH21 customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Clec Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN ▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFN▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ▇▇▇.▇▇▇ what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFN▇▇▇.▇▇▇, BellSouth shall provide AFN ▇▇▇.▇▇▇ with a list of the customer data items, which AFN ▇▇▇.▇▇▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN ▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of AFN▇▇▇.▇▇▇. Such direction from AFN ▇▇▇.▇▇▇ will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN ▇▇▇.▇▇▇ data upon AFN▇▇▇.▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by AFN ▇▇▇.▇▇▇ audits. BellSouth will audit AFN ▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN ▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from AFN▇▇▇.▇▇▇, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN ▇▇▇.▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFN▇▇▇.▇▇▇’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN ▇▇▇.▇▇▇ with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ▇▇▇.▇▇▇ and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN ▇▇▇.▇▇▇ data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ▇▇▇.▇▇▇ in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN ▇▇▇.▇▇▇ performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ▇▇▇.▇▇▇ at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ▇▇▇.▇▇▇ the screening information associated with LIDB Data Screening of AFN ▇▇▇.▇▇▇ data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ▇▇▇.▇▇▇ under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN ▇▇▇.▇▇▇ customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNCBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNCBX One-Stop, BellSouth shall provide AFN CBX One-Stop with a list of the customer data items, which AFN CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN CBX One-Stop data to the LIDB shall be solely at the direction of AFNCBX One-Stop. Such direction from AFN CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN CBX One-Stop data upon AFNCBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CBX One-Stop customer records will be missing from LIDB, as measured by AFN CBX One- Stop audits. BellSouth will audit AFN CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from AFNCBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNCBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN CBX One-Stop and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN CBX One-Stop in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CBX One-Stop the screening information associated with LIDB Data Screening of AFN CBX One-Stop data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CBX One-Stop under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN CBX One-Stop customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Lightning Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNLightning Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Lightning Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNLightning Communications, BellSouth shall provide AFN Lightning Communications with a list of the customer data items, which AFN Lightning Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Lightning Communications data to the LIDB shall be solely at the direction of AFNLightning Communications. Such direction from AFN Lightning Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Lightning Communications data upon AFNLightning Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Lightning Communications customer records will be missing from LIDB, as measured by AFN Lightning Communications audits. BellSouth will audit AFN Lightning Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Lightning Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Lightning Communications within one (1) business day of audit. Once reconciled records are received back from AFNLightning Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Lightning Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNLightning Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Lightning Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Lightning Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Lightning Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Lightning Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Lightning Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Lightning Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Lightning Communications the screening information associated with LIDB Data Screening of AFN Lightning Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Lightning Communications under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Lightning Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN CCI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CCI what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCCI, BellSouth shall provide AFN CCI with a list of the customer data items, which AFN CCI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN CCI data to the LIDB shall be solely at the direction of AFNCCI. Such direction from AFN CCI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN CCI data upon AFNCCI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CCI customer records will be missing from LIDB, as measured by AFN CCI audits. BellSouth will audit AFN CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN CCI within one (1) business day of audit. Once reconciled records are received back from AFNCCI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN CCI to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCCI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN CCI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN CCI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN CCI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN CCI in writing.
7.3.2.13 BellSouth shall provide AFN CCI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CCI the screening information associated with LIDB Data Screening of AFN CCI data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CCI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN CCI customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 1.2.1 BellSouth also will offer to AFN CLEC any additional capabilities that are developed for LIDB LIBD during the life of this Agreement.
7.3.2.2 1.2.2 BellSouth shall process AFNCLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CLEC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 1.2.3 Within two (2) weeks after a request by AFNCLEC, BellSouth shall provide AFN CLEC with a list of the customer data items, items which AFN CLEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 1.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 1.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 1.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.year.
7.3.2.7 1.2.7 All additions, updates and deletions of AFN CLEC data to the LIDB shall be solely at the direction of AFNCLEC. Such direction from AFN CLEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation).
7.3.2.8 1.2.8 BellSouth shall provide priority updates to LIDB for AFN CLEC data upon AFNCLEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 1.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CLEC customer records will be missing from LIDB, as measured by AFN CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated AFN CLEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to AFN CLEC within one (1) business day of audit. Once reconciled records are received back from AFNCLEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN CLEC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 1.2.10 BellSouth shall perform backup and recovery of all of AFNCLEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 1.2.11 BellSouth shall provide AFN CLEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN CLEC and BellSouth.
7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of AFN CLEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN CLEC in writing.
7.3.2.13 1.2.13.1 BellSouth shall provide AFN CLEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CLEC the screening information associated with LIDB Data Screening of AFN CLEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CLEC under the BFR/NBR Process as set forth in Attachment 11.Bona Fide Request process.
7.3.2.14 1.2.14 BellSouth shall accept queries to LIDB associated with AFN CLEC customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 1.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.within
Appears in 1 contract
Sources: Lidb Storage Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Excel any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNExcel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Excel what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNExcel, BellSouth shall provide AFN Excel with a list of the customer data items, which AFN Excel would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Excel data to the LIDB shall be solely at the direction of AFNExcel. Such direction from AFN Excel will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Excel data upon AFNExcel’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Excel customer records will be missing from LIDB, as measured by AFN Excel audits. BellSouth will audit AFN Excel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Excel contact person to resolve the status of the records and BellSouth AMENDMENT EXHIBIT 1 Attachment 2 Page 52 will update system appropriately. BellSouth will refer record of mismatches to AFN Excel within one (1) business day of audit. Once reconciled records are received back from AFNExcel, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Excel to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNExcel’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Excel with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Excel and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Excel data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Excel in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Excel performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Excel at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Excel the screening information associated with LIDB Data Screening of AFN Excel data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Excel under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Excel customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Grande any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFN▇▇▇▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Grande what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNGrande, BellSouth shall provide AFN Grande with a list of the customer data items, which AFN Grande would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Grande data to the LIDB shall be solely at the direction of AFNGrande. Such direction from AFN Grande will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Grande data upon AFNGrande’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Grande customer records will be missing from LIDB, as measured by AFN Grande audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN Grande records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Grande contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Grande within one (1) business day of audit. Once reconciled records are received back from AFNGrande, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Grande to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNGrande’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Grande with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Grande and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Grande data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Grande in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Grande performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Grande at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Grande the screening information associated with LIDB Data Screening of AFN Grande data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Grande under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Grande customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Think 12 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNThink 12’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Think 12 what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNThink 12, BellSouth shall provide AFN Think 12 with a list of the customer data items, which AFN Think 12 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Think 12 data to the LIDB shall be solely at the direction of AFNThink 12. Such direction from AFN Think 12 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Think 12 data upon AFNThink 12’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Think 12 customer records will be missing from LIDB, as measured by AFN Think 12 audits. BellSouth will audit AFN Think 12 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Think 12 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Think 12 within one (1) business day of audit. Once reconciled records are received back from AFNThink 12, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Think 12 to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNThink 12’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Think 12 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Think 12 and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Think 12 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Think 12 in writing.
7.3.2.13 BellSouth shall provide AFN Think 12 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Think 12 at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Think 12 the screening information associated with LIDB Data Screening of AFN Think 12 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Think 12 under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Think 12 customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNNex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Nex-Phon what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNNex-Phon, BellSouth shall provide AFN Nex- Phon with a list of the customer data items, which AFN Nex-Phon would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN Nex-Phon data to the LIDB shall be solely at the direction of AFNNex-Phon. Such direction from AFN Nex-Phon will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN Nex-Phon data upon AFNNex- Phon’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Nex-Phon customer records will be missing from LIDB, as measured by AFN Nex-Phon audits. BellSouth will audit AFN Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN Nex-Phon within one (1) business day of audit. Once reconciled records are received back from AFNNex-Phon, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN Nex-Phon to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNNex-Phon’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN Nex-Phon with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Nex-Phon and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN Nex-Phon data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Nex-Phon in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN Nex-Phon performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Nex-Phon the screening information associated with LIDB Data Screening of AFN Nex-Phon data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Nex-Phon under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN Nex-Phon customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN US South any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNUS South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN US South what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNUS South, BellSouth shall provide AFN US South with a list of the customer data items, which AFN US South would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN US South data to the LIDB shall be solely at the direction of AFNUS South. Such direction from AFN US South will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN US South data upon AFNUS South’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN US South customer records will be missing from LIDB, as measured by AFN US South audits. BellSouth will audit AFN US South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN US South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN US South within one (1) business day of audit. Once reconciled records are received back from AFNUS South, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN US South to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN in writing.
7.3.2.13 BellSouth shall provide AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN the screening information associated with LIDB Data Screening of AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN MyLineToo any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNMyLineToo’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN MyLineToo what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNMyLineToo, BellSouth shall provide AFN MyLineToo with a list of the customer data items, which AFN MyLineToo would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN MyLineToo data to the LIDB shall be solely at the direction of AFNMyLineToo. Such direction from AFN MyLineToo will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN MyLineToo data upon AFNMyLineToo’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN MyLineToo customer records will be missing from LIDB, as measured by AFN MyLineToo audits. BellSouth will audit AFN MyLineToo records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN MyLineToo contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN MyLineToo within one (1) business day of audit. Once reconciled records are received back from AFNMyLineToo, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN MyLineToo to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNMyLineToo’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN MyLineToo with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN MyLineToo and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN MyLineToo data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN MyLineToo in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN MyLineToo performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN MyLineToo at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN MyLineToo the screening information associated with LIDB Data Screening of AFN MyLineToo data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN MyLineToo under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN MyLineToo customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN TWTC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNTWTC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN TWTC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNTWTC, BellSouth shall provide AFN TWTC with a list of the customer data items, which AFN TWTC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN TWTC data to the LIDB shall be solely at the direction of AFNTWTC. Such direction from AFN TWTC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN TWTC data upon AFNTWTC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN TWTC customer records will be missing from LIDB, as measured by AFN TWTC audits. BellSouth will audit AFN TWTC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN TWTC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN TWTC within one (1) business day of audit. Once reconciled records are received back from AFNTWTC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN TWTC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNTWTC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN TWTC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN TWTC and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN TWTC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN TWTC in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN TWTC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN TWTC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN TWTC the screening information associated with LIDB Data Screening of AFN TWTC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN TWTC under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN TWTC customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCBX One-Stop, BellSouth shall provide AFN CBX One-Stop with a list of the customer data items, which AFN CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN CBX One-Stop data to the LIDB shall be solely at the direction of AFNCBX One-Stop. Such direction from AFN CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN CBX One-Stop data upon AFNCBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CBX One-Stop customer records will be missing from LIDB, as measured by AFN CBX One- Stop audits. BellSouth will audit AFN CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from AFNCBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN CBX One-Stop and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN CBX One-Stop in writing.
7.3.2.13 BellSouth shall provide AFN CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CBX One-Stop the screening information associated with LIDB Data Screening of AFN CBX One-Stop data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CBX One-Stop under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN CBX One-Stop customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNLevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Level 3 what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNLevel 3, BellSouth shall provide AFN Level 3 with a list of the customer data items, which AFN Level 3 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Level 3 data to the LIDB shall be solely at the direction of AFNLevel 3. Such direction from AFN Level 3 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Level 3 data upon AFNLevel 3’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Level 3 customer records will be missing from LIDB, as measured by AFN Level 3 audits. BellSouth will audit AFN Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Level 3 within one (1) business day of audit. Once reconciled records are received back from AFNLevel 3, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN Level 3 to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNLevel 3’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Level 3 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Level 3 and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Level 3 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Level 3 in writing.
7.3.2.13 BellSouth shall provide AFN Level 3 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Level 3 the screening information associated with LIDB Data Screening of AFN Level 3 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Level 3 under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Level 3 customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Telstar Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNTelstar Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Telstar Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNTelstar Communications, BellSouth shall provide AFN Telstar Communications with a list of the customer data items, which AFN Telstar Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Telstar Communications data to the LIDB shall be solely at the direction of AFNTelstar Communications. Such direction from AFN Telstar Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Telstar Communications data upon AFNTelstar Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Telstar Communications customer records will be missing from LIDB, as measured by AFN Telstar Communications audits. BellSouth will audit AFN Telstar Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Telstar Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Telstar Communications within one (1) business day of audit. Once reconciled records are received back from AFNTelstar Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Telstar Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNTelstar Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Telstar Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Telstar Communications and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Telstar Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Telstar Communications in writing.
7.3.2.13 BellSouth shall provide AFN Telstar Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Telstar Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Telstar Communications the screening information associated with LIDB Data Screening of AFN Telstar Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Telstar Communications under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Telstar Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Cinergy any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCinergy’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Cinergy what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCinergy, BellSouth shall provide AFN Cinergy with a list of the customer data items, which AFN Cinergy would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Cinergy data to the LIDB shall be solely at the direction of AFNCinergy. Such direction from AFN Cinergy will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Cinergy data upon AFNCinergy’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Cinergy customer records will be missing from LIDB, as measured by AFN Cinergy audits. BellSouth will audit AFN Cinergy records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Cinergy contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Cinergy within one (1) business day of audit. Once reconciled records are received back from AFNCinergy, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Cinergy to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCinergy’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Cinergy with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Cinergy and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Cinergy data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Cinergy in writing.
7.3.2.13 BellSouth shall provide AFN Cinergy performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Cinergy at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Cinergy the screening information associated with LIDB Data Screening of AFN Cinergy data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Cinergy under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Cinergy customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN NGTelecom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNNGTelecom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN NGTelecom what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNNGTelecom, BellSouth shall provide AFN NGTelecom with a list of the customer data items, which AFN NGTelecom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN NGTelecom data to the LIDB shall be solely at the direction of AFNNGTelecom. Such direction from AFN NGTelecom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN NGTelecom data upon AFNNGTelecom’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN NGTelecom customer records will be missing from LIDB, as measured by AFN NGTelecom audits. BellSouth will audit AFN NGTelecom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN NGTelecom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN NGTelecom within one (1) business day of audit. Once reconciled records are received back from AFNNGTelecom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN NGTelecom to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN in writing.
7.3.2.13 BellSouth shall provide AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN the screening information associated with LIDB Data Screening of AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNLevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Level 3 what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFN▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ shall provide AFN Level 3 with a list of the customer data items, which AFN ▇▇▇▇▇ ▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Level 3 data to the LIDB shall be solely at the direction of AFNLevel 3. Such direction from AFN Level 3 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN data upon AFN▇▇▇▇▇ ▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇ ▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Level 3 customer records will be missing from LIDB, as measured by AFN Level 3 audits. BellSouth will audit AFN Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Level 3 within one (1) business day of audit. Once reconciled records are received back from AFN▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN Level 3 to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNLevel 3’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Level 3 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Level 3 and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Level 3 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Level 3 in writing.
7.3.2.13 BellSouth shall provide AFN Level 3 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Level 3 the screening information associated with LIDB Data Screening of AFN Level 3 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Level 3 under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Level 3 customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Covad any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNCovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Covad what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNCovad, BellSouth shall provide AFN Covad with a list of the customer data items, which AFN Covad would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Covad data to the LIDB shall be solely at the direction of AFNCovad. Such direction from AFN Covad will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Covad data upon AFNCovad’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Covad customer records will be missing from LIDB, as measured by AFN Covad audits. BellSouth will audit AFN Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Covad within one (1) business day of audit. Once reconciled records are received back from AFNCovad, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN Covad to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNCovad’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Covad with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Covad and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Covad data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Covad in writing.
7.3.2.13 BellSouth shall provide AFN Covad performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Covad the screening information associated with LIDB Data Screening of AFN Covad data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Covad under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Covad customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Kinetix any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNKinetix’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Kinetix what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNKinetix, BellSouth shall provide AFN Kinetix with a list of the customer data items, which AFN Kinetix would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Kinetix data to the LIDB shall be solely at the direction of AFNKinetix. Such direction from AFN Kinetix will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Kinetix data upon AFNKinetix’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Kinetix customer records will be missing from LIDB, as measured by AFN Kinetix audits. BellSouth will audit AFN Kinetix records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Kinetix contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Kinetix within one (1) business day of audit. Once reconciled records are received back from AFNKinetix, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Kinetix to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNKinetix’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Kinetix with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Kinetix and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Kinetix data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Kinetix in writing.
7.3.2.13 BellSouth shall provide AFN Kinetix performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Kinetix at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Kinetix the screening information associated with LIDB Data Screening of AFN Kinetix data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Kinetix under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Kinetix customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN ProNet any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNProNet’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ProNet what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNProNet, BellSouth shall provide AFN ProNet with a list of the customer data items, which AFN ProNet would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN ProNet data to the LIDB shall be solely at the direction of AFNProNet. Such direction from AFN ProNet will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN ProNet data upon AFNProNet’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ProNet customer records will be missing from LIDB, as measured by AFN ProNet audits. BellSouth will audit AFN ProNet records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ProNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN ProNet within one (1) business day of audit. Once reconciled records are received back from AFNProNet, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN ProNet to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNProNet’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN ProNet with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ProNet and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN ProNet data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ProNet in writing.
7.3.2.13 BellSouth shall provide AFN ProNet performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ProNet at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ProNet the screening information associated with LIDB Data Screening of AFN ProNet data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ProNet under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN ProNet customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Southern Digital any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNSouthern Digital’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Southern Digital what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNSouthern Digital, BellSouth shall provide AFN Southern Digital with a list of the customer data items, which AFN Southern Digital would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Southern Digital data to the LIDB shall be solely at the direction of AFNSouthern Digital. Such direction from AFN Southern Digital will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Southern Digital data upon AFNSouthern Digital’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Southern Digital customer records will be missing from LIDB, as measured by AFN Southern Digital audits. BellSouth will audit AFN Southern Digital records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Southern Digital contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Southern Digital within one (1) business day of audit. Once reconciled records are received back from AFNSouthern Digital, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact AFN Southern Digital to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNSouthern Digital’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Southern Digital with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Southern Digital and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Southern Digital data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Southern Digital in writing.
7.3.2.13 BellSouth shall provide AFN Southern Digital performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Southern Digital at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Southern Digital the screening information associated with LIDB Data Screening of AFN Southern Digital data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Southern Digital under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Southern Digital customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 1.2.1 BellSouth also will offer to AFN CLEC any additional capabilities that are developed for LIDB LIBD during the life of this Agreement.
7.3.2.2 1.2.2 BellSouth shall process AFNCLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN CLEC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 1.2.3 Within two (2) weeks after a request by AFNCLEC, BellSouth shall provide AFN CLEC with a list of the customer data items, items which AFN CLEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 1.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 1.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 1.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 1.2.7 All additions, updates and deletions of AFN CLEC data to the LIDB shall be solely at the direction of AFNCLEC. Such direction from AFN CLEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation).
7.3.2.8 1.2.8 BellSouth shall provide priority updates to LIDB for AFN CLEC data upon AFNCLEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 1.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN CLEC customer records will be missing from LIDB, as measured by AFN CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated AFN CLEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to AFN CLEC within one (1) business day of audit. Once reconciled records are received back from AFNCLEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN CLEC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 1.2.10 BellSouth shall perform backup and recovery of all of AFNCLEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 1.2.11 BellSouth shall provide AFN CLEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN CLEC and BellSouth.
7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of AFN CLEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN CLEC in writing.
7.3.2.13 1.2.13.1 BellSouth shall provide AFN CLEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN CLEC the screening information associated with LIDB Data Screening of AFN CLEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN CLEC under the BFR/NBR Process as set forth in Attachment 11Bona Fide Request process.
7.3.2.14 1.2.14 BellSouth shall accept queries to LIDB associated with AFN CLEC customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 1.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.within
Appears in 1 contract
Sources: Lidb Storage Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN FPB any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNFPB’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN FPB what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNFPB, BellSouth shall provide AFN FPB with a list of the customer data items, which AFN FPB would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN FPB data to the LIDB shall be solely at the direction of AFNFPB. Such direction from AFN FPB will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN FPB data upon AFNFPB’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN FPB customer records will be missing from LIDB, as measured by AFN FPB audits. BellSouth will audit AFN FPB records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN FPB contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN FPB within one (1) business day of audit. Once reconciled records are received back from AFNFPB, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN FPB to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNFPB’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN FPB with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN FPB and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN FPB data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN FPB in writing.
7.3.2.13 BellSouth shall provide AFN FPB performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN FPB at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN FPB the screening information associated with LIDB Data Screening of AFN FPB data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN FPB under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN FPB customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN UTI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNUTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN UTI what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNUTI, BellSouth shall provide AFN UTI with a list of the customer data items, which AFN UTI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN UTI data to the LIDB shall be solely at the direction of AFNUTI. Such direction from AFN UTI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN UTI data upon AFNUTI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN UTI customer records will be missing from LIDB, as measured by AFN UTI audits. BellSouth will audit AFN UTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN UTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN UTI within one (1) business day of audit. Once reconciled records are received back from AFNUTI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN UTI to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNUTI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN UTI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN UTI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN UTI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN UTI in writing.
7.3.2.13 BellSouth shall provide AFN UTI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN UTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN UTI the screening information associated with LIDB Data Screening of AFN UTI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN UTI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN UTI customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN OnePoint Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNOnePoint Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN OnePoint Communications what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNOnePoint Communications, BellSouth shall provide AFN OnePoint Communications with a list of the customer data items, which AFN OnePoint Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN OnePoint Communications data to the LIDB shall be solely at the direction of AFNOnePoint Communications. Such direction from AFN OnePoint Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN OnePoint Communications data upon AFNOnePoint Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN OnePoint Communications customer records will be missing from LIDB, as measured by AFN OnePoint Communications audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN OnePoint Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN OnePoint Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN OnePoint Communications within one (1) business day of audit. Once reconciled records are received back from AFNOnePoint Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN OnePoint Communications to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNOnePoint Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN OnePoint Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN OnePoint Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN OnePoint Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN OnePoint Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN OnePoint Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN OnePoint Communications at least at parity with BellSouth Customer Data. BellSouth ▇▇▇▇▇▇▇▇▇ shall obtain from AFN OnePoint Communications the screening information associated with LIDB Data Screening of AFN OnePoint Communications data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN OnePoint Communications under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN OnePoint Communications customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN ConnectNow! any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNConnectNow!’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN ConnectNow! what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNConnectNow!, BellSouth shall provide AFN ConnectNow! with a list of the customer data items, which AFN ConnectNow! would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN ConnectNow! data to the LIDB shall be solely at the direction of AFNConnectNow!. Such direction from AFN ConnectNow! will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN ConnectNow! data upon AFNConnectNow!’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN ConnectNow! customer records will be missing from LIDB, as measured by AFN ConnectNow! audits. BellSouth will audit AFN ConnectNow! records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN ConnectNow! contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN ConnectNow! within one (1) business day of audit. Once reconciled records are received back from AFNConnectNow!, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact AFN ConnectNow! to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNConnectNow!’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN ConnectNow! with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN ConnectNow! and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN ConnectNow! data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN ConnectNow! in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN ConnectNow! performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN ConnectNow! at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN ConnectNow! the screening information associated with LIDB Data Screening of AFN ConnectNow! data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN ConnectNow! under the BFR/NBR Process process as set forth in Attachment 11.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN ConnectNow! customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to AFN AmeriMex any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process AFNAmeriMex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN AmeriMex what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 9.2.3 Within two (2) weeks after a request by AFNAmeriMex, BellSouth shall provide AFN AmeriMex with a list of the customer data items, which AFN AmeriMex would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 9.2.7 All additions, updates and deletions of AFN AmeriMex data to the LIDB shall be solely at the direction of AFNAmeriMex. Such direction from AFN AmeriMex will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for AFN AmeriMex data upon AFNAmeriMex’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN AmeriMex customer records will be missing from LIDB, as measured by AFN AmeriMex audits. BellSouth will audit AFN AmeriMex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN AmeriMex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to AFN AmeriMex within one (1) business day of audit. Once reconciled records are received back from AFNAmeriMex, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN AmeriMex to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of AFNAmeriMex’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 9.2.11 BellSouth shall provide AFN AmeriMex with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN AmeriMex and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of AFN AmeriMex data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN AmeriMex in writing.
7.3.2.13 9.2.13 BellSouth shall provide AFN AmeriMex performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN AmeriMex at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN AmeriMex the screening information associated with LIDB Data Screening of AFN AmeriMex data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN AmeriMex under the BFR/NBR Process as set forth in Attachment 11process.
7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with AFN AmeriMex customer records and shall return responses in accordance with industry standards.
7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN BCFL any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNBCFL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN BCFL what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNBCFL, BellSouth shall provide AFN BCFL with a list of the customer data items, which AFN BCFL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN BCFL data to the LIDB shall be solely at the direction of AFNBCFL. Such direction from AFN BCFL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN BCFL data upon AFNBCFL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN BCFL customer records will be missing from LIDB, as measured by AFN BCFL audits. BellSouth will audit AFN BCFL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN BCFL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN BCFL within one (1) business day of audit. Once reconciled records are received back from AFNBCFL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN BCFL to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNBCFL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN BCFL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN BCFL and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN BCFL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN BCFL in writing.
7.3.2.13 BellSouth shall provide AFN BCFL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN BCFL at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN BCFL the screening information associated with LIDB Data Screening of AFN BCFL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN BCFL under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN BCFL customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN Excel PCHP any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process AFNExcel PCHP’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN Excel PCHP what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 Within two (2) weeks after a request by AFNExcel PCHP, BellSouth shall provide AFN Excel PCHP with a list of the customer data items, which AFN Excel PCHP would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.
7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.
7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.
7.3.2.7 All additions, updates and deletions of AFN Excel PCHP data to the LIDB shall be solely at the direction of AFNExcel PCHP. Such direction from AFN Excel PCHP will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN Excel PCHP data upon AFNExcel PCHP’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN Excel PCHP customer records will be missing from LIDB, as measured by AFN Excel PCHP audits. BellSouth will audit AFN Excel PCHP records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN Excel PCHP contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN Excel PCHP within one (1) business day of audit. Once reconciled records are received back from AFNExcel PCHP, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN Excel PCHP to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFNExcel PCHP’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN Excel PCHP with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN Excel PCHP and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN Excel PCHP data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN Excel PCHP in writing.
7.3.2.13 BellSouth shall provide AFN Excel PCHP performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN Excel PCHP at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN Excel PCHP the screening information associated with LIDB Data Screening of AFN Excel PCHP data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN Excel PCHP under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN Excel PCHP customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to AFN US LEC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 13.4.2.1 BellSouth shall process AFNUS LEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN US LEC what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 13.4.2.2 Within two (2) weeks after a request by AFNUS LEC, BellSouth shall provide AFN US LEC with a list of the customer data items, items which AFN US LEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 13.4.2.6 All additions, updates and deletions of AFN US LEC data to the LIDB shall be solely at the direction of AFNUS LEC. Such direction from AFN US LEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for AFN US LEC data upon AFNUS LEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN US LEC customer records will be missing from LIDB, as measured by AFN US LEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit AFN US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated AFN US LEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to AFN US LEC within one (1) business day of audit. Once reconciled records are received back from AFNUS LEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact AFN US LEC to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of AFNUS LEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 13.4.2.10 BellSouth shall provide AFN US LEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between AFN US LEC and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of AFN US LEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by AFN US LEC in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide AFN US LEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN US LEC the screening information associated with LIDB Data Screening of AFN US LEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN US LEC under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119.
7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with AFN US LEC customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Clec Agreement
Technical Requirements. 7.3.2.1 8.2.1 BellSouth will offer to AFN GulfPines any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 8.2.2 BellSouth shall process AFN’s customer GulfPines’ Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to AFN GulfPines what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 8.2.3 Within two (2) weeks after a request by AFNGulfPines, BellSouth shall provide AFN GulfPines with a list of the customer data items, which AFN GulfPines would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.
7.3.2.4 8.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) 30 minutes per year.
7.3.2.5 8.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year.
7.3.2.6 8.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.
7.3.2.7 8.2.7 All additions, updates and deletions of AFN GulfPines data to the LIDB shall be solely at the direction of AFNGulfPines. Such direction from AFN GulfPines will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).
7.3.2.8 BellSouth shall provide priority updates to LIDB for AFN data upon AFN’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.
7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of AFN customer records will be missing from LIDB, as measured by AFN audits. BellSouth will audit AFN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated AFN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to AFN within one (1) business day of audit. Once reconciled records are received back from AFN, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact AFN to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 BellSouth shall perform backup and recovery of all of AFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.
7.3.2.11 BellSouth shall provide AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between AFN and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by AFN in writing.
7.3.2.13 BellSouth shall provide AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from AFN the screening information associated with LIDB Data Screening of AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to AFN under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with AFN customer records and shall return responses in accordance with industry standards.
7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.
7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.
Appears in 1 contract
Sources: Interconnection Agreement