Technical Requirements. 7.3.2.1 BellSouth will offer to <customer_short_name> any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process <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 <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 <customer_short_name>, BellSouth shall provide <customer_short_name> with a list of the customer data items, which <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 <customer_short_name> data to the LIDB shall be solely at the direction of <customer_short_name>. Such direction from <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 <customer_short_name> data upon <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 <customer_short_name> customer records will be missing from LIDB, as measured by <customer_short_name> audits. BellSouth will audit <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <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 <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from <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 <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 <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 <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 <customer_short_name> and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing. 7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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 <customer_short_name> PLI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>PLI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>PLI, BellSouth shall provide <customer_short_name> PLI with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> PLI data to the LIDB shall be solely at the direction of <customer_short_name>PLI. Such direction from <customer_short_name> 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 <customer_short_name> data upon <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 <customer_short_name> PLI customer records will be missing from LIDB, as measured by <customer_short_name> PLI audits. BellSouth will audit <customer_short_name> PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> PLI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>PLI, 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 <customer_short_name> 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 <customer_short_name>PLI’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 <customer_short_name> 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 <customer_short_name> PLI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> PLI in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> PLI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> PLI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>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 <customer_short_name> 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 <customer_short_name>ITC^DeltaCom, BellSouth shall provide <customer_short_name> ITC^DeltaCom with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> ITC^DeltaCom data to the LIDB shall be solely at the direction of <customer_short_name>ITC^DeltaCom. Such direction from <customer_short_name> 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 <customer_short_name> ITC^DeltaCom data upon <customer_short_name>ITC^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 <customer_short_name> ITC^DeltaCom customer records will be missing from LIDB, as measured by <customer_short_name> ITC^DeltaCom audits. BellSouth will audit <customer_short_name> ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ITC^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 <customer_short_name> 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 <customer_short_name>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; 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 <customer_short_name> 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 <customer_short_name> ITC^DeltaCom and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ITC^DeltaCom in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ITC^DeltaCom the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>ITC^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 <customer_short_name> 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 <customer_short_name>ITC^DeltaCom, BellSouth shall provide <customer_short_name> ITC^DeltaCom with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> ITC^DeltaCom data to the LIDB shall be solely at the direction of <customer_short_name>ITC^DeltaCom. Such direction from <customer_short_name> 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 <customer_short_name> ITC^DeltaCom data upon <customer_short_name>ITC^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 <customer_short_name> ITC^DeltaCom customer records will be missing from LIDB, as measured by <customer_short_name> ITC^DeltaCom audits. BellSouth will audit <customer_short_name> ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ITC^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 <customer_short_name> 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 <customer_short_name>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 <customer_short_name> 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 <customer_short_name> ITC^DeltaCom and BellSouth.
7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ITC^DeltaCom in writing.
7.3.2.13 15.4.2.12 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ITC^DeltaCom the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name>US LEC, BellSouth shall provide <customer_short_name> US LEC with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> US LEC data to the LIDB shall be solely at the direction of <customer_short_name>US LEC. Such direction from <customer_short_name> 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 <customer_short_name> US LEC data upon <customer_short_name>US 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 <customer_short_name> US LEC customer records will be missing from LIDB, as measured by <customer_short_name> US LEC audits. BellSouth will audit <customer_short_name> US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> US LEC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name> US LEC and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> US LEC in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide <customer_short_name> 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 <customer_short_name> US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> US LEC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> MRC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>MRC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>MRC, BellSouth shall provide <customer_short_name> MRC with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> MRC data to the LIDB shall be solely at the direction of <customer_short_name>MRC. Such direction from <customer_short_name> 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 <customer_short_name> MRC data upon <customer_short_name>MRC’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 <customer_short_name> MRC customer records will be missing from LIDB, as measured by <customer_short_name> MRC audits. BellSouth will audit <customer_short_name> MRC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> MRC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> MRC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>MRC, 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 <customer_short_name> 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 <customer_short_name>MRC’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 <customer_short_name> 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 <customer_short_name> MRC and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> MRC in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> MRC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> MRC under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> AFN any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>AFN’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>AFN, BellSouth shall provide <customer_short_name> AFN with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> AFN data to the LIDB shall be solely at the direction of <customer_short_name>AFN. Such direction from <customer_short_name> 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 <customer_short_name> AFN data upon <customer_short_name>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 <customer_short_name> AFN customer records will be missing from LIDB, as measured by <customer_short_name> AFN audits. BellSouth will audit <customer_short_name> AFN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> AFN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> AFN within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>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 <customer_short_name> 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 <customer_short_name>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 <customer_short_name> 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 <customer_short_name> AFN and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> AFN in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> AFN the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> AFN under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> ACN any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>ACN’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> ACN 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 <customer_short_name>ACN, BellSouth shall provide <customer_short_name> ACN with a list of the customer data items, which <customer_short_name> ACN 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 <customer_short_name> ACN data to the LIDB shall be solely at the direction of <customer_short_name>ACN. Such direction from <customer_short_name> ACN 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 <customer_short_name> ACN data upon <customer_short_name>ACN’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 <customer_short_name> ACN customer records will be missing from LIDB, as measured by <customer_short_name> ACN audits. BellSouth will audit <customer_short_name> ACN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ACN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ACN within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ACN, 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 <customer_short_name> ACN 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 <customer_short_name>ACN’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 <customer_short_name> ACN 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 <customer_short_name> ACN and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> ACN 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 <customer_short_name> ACN in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> ACN 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 <customer_short_name> ACN at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ACN the screening information associated with LIDB Data Screening of <customer_short_name> ACN 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 <customer_short_name> ACN 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 <customer_short_name> ACN 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 8.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>’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 <customer_short_name> 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 <customer_short_name>GulfPines, BellSouth shall provide <customer_short_name> GulfPines with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> GulfPines data to the LIDB shall be solely at the direction of <customer_short_name>GulfPines. Such direction from <customer_short_name> 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 <customer_short_name> data upon <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 <customer_short_name> customer records will be missing from LIDB, as measured by <customer_short_name> audits. BellSouth will audit <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <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 <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from <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 <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 <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 <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 <customer_short_name> and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>TWTC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>TWTC, BellSouth shall provide <customer_short_name> TWTC with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> TWTC data to the LIDB shall be solely at the direction of <customer_short_name>TWTC. Such direction from <customer_short_name> 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 <customer_short_name> TWTC data upon <customer_short_name>TWTC’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 <customer_short_name> TWTC customer records will be missing from LIDB, as measured by <customer_short_name> TWTC audits. BellSouth will audit <customer_short_name> TWTC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> TWTC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> TWTC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>TWTC, 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 <customer_short_name> 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 <customer_short_name>TWTC’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 <customer_short_name> 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 <customer_short_name> TWTC and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> TWTC in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> TWTC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> TWTC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Columbus Local any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Columbus Local’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Columbus Local 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 <customer_short_name>Columbus Local, BellSouth shall provide <customer_short_name> Columbus Local with a list of the customer data items, which <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local data to the LIDB shall be solely at the direction of <customer_short_name>Columbus Local. Such direction from <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local data upon <customer_short_name>Columbus Local’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 <customer_short_name> Columbus Local customer records will be missing from LIDB, as measured by <customer_short_name> Columbus Local audits. BellSouth will audit <customer_short_name> Columbus Local records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Columbus Local contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Columbus Local within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Columbus Local, 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 <customer_short_name> ▇▇▇▇▇▇▇▇ Local 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 <customer_short_name>Columbus Local’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 <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Columbus Local the screening information associated with LIDB Data Screening of <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local 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 <customer_short_name> Columbus Local 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 <customer_short_name> Tel West any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Tel West’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Tel West 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 <customer_short_name>Tel West, BellSouth shall provide <customer_short_name> Tel West with a list of the customer data items, which <customer_short_name> Tel West 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 <customer_short_name> Tel West data to the LIDB shall be solely at the direction of <customer_short_name>Tel West. Such direction from <customer_short_name> Tel West 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 <customer_short_name> Tel West data upon <customer_short_name>Tel West’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 <customer_short_name> Tel West customer records will be missing from LIDB, as measured by <customer_short_name> Tel West audits. BellSouth will audit <customer_short_name> Tel West records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Tel West contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Tel West within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Tel West, 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 <customer_short_name> Tel West 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 <customer_short_name>Tel West’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 <customer_short_name> Tel West 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 <customer_short_name> Tel West and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Tel West 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 <customer_short_name> Tel West in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Tel West 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 <customer_short_name> Tel West at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Tel West the screening information associated with LIDB Data Screening of <customer_short_name> Tel West 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 <customer_short_name> Tel West 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 <customer_short_name> Tel West 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 <customer_short_name> Telstar Communications any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Telstar Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Telstar Communications, BellSouth shall provide <customer_short_name> Telstar Communications with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Telstar Communications data to the LIDB shall be solely at the direction of <customer_short_name>Telstar Communications. Such direction from <customer_short_name> 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 <customer_short_name> Telstar Communications data upon <customer_short_name>Telstar 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 <customer_short_name> Telstar Communications customer records will be missing from LIDB, as measured by <customer_short_name> Telstar Communications audits. BellSouth will audit <customer_short_name> Telstar Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Telstar Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Telstar Communications within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Telstar 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 <customer_short_name> 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 <customer_short_name>Telstar 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 <customer_short_name> 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 <customer_short_name> Telstar Communications and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Telstar Communications in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Telstar Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Telstar Communications the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 1.2.1 BellSouth also will offer to <customer_short_name> 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 <customer_short_name>CLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>CLEC, BellSouth shall provide <customer_short_name> CLEC with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> CLEC data to the LIDB shall be solely at the direction of <customer_short_name>CLEC. Such direction from <customer_short_name> 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 <customer_short_name> CLEC data upon <customer_short_name>CLEC’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 <customer_short_name> CLEC customer records will be missing from LIDB, as measured by <customer_short_name> CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated <customer_short_name> 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 <customer_short_name> CLEC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CLEC, 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 <customer_short_name> 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 <customer_short_name>CLEC’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 <customer_short_name> 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 <customer_short_name> CLEC and BellSouth.
7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CLEC in writing.
7.3.2.13 1.2.13.1 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CLEC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Kinetix any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Kinetix’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Kinetix, BellSouth shall provide <customer_short_name> Kinetix with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Kinetix data to the LIDB shall be solely at the direction of <customer_short_name>Kinetix. Such direction from <customer_short_name> 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 <customer_short_name> Kinetix data upon <customer_short_name>Kinetix’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 <customer_short_name> Kinetix customer records will be missing from LIDB, as measured by <customer_short_name> Kinetix audits. BellSouth will audit <customer_short_name> Kinetix records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Kinetix contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Kinetix within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Kinetix, 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 <customer_short_name> 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 <customer_short_name>Kinetix’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 <customer_short_name> 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 <customer_short_name> Kinetix and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Kinetix in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Kinetix at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Kinetix the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Kinetix under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>Nexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Nexus, BellSouth shall provide <customer_short_name> Nexus with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Nexus data to the LIDB shall be solely at the direction of <customer_short_name>Nexus. Such direction from <customer_short_name> 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 <customer_short_name> Nexus data upon <customer_short_name>Nexus’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 <customer_short_name> Nexus customer records will be missing from LIDB, as measured by <customer_short_name> Nexus audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Nexus within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Nexus, 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 <customer_short_name> 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 <customer_short_name>Nexus’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 <customer_short_name> 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 <customer_short_name> Nexus and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Nexus in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Nexus the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Starlink any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Starlink’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Starlink 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 <customer_short_name>Starlink, BellSouth shall provide <customer_short_name> Starlink with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> Starlink data to the LIDB shall be solely at the direction of <customer_short_name>Starlink. Such direction from <customer_short_name> 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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> Starlink data upon <customer_short_name>Starlink’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 <customer_short_name> Starlink customer records will be missing from LIDB, as measured by <customer_short_name> Starlink audits. BellSouth will audit <customer_short_name> Starlink records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Starlink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Starlink within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Starlink, 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 <customer_short_name> Starlink 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 <customer_short_name>Starlink’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 <customer_short_name> 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 <customer_short_name> Starlink and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Starlink in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Starlink at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Starlink the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Starlink 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 <customer_short_name> Starlink 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 <customer_short_name> BCFL any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>BCFL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>BCFL, BellSouth shall provide <customer_short_name> BCFL with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> BCFL data to the LIDB shall be solely at the direction of <customer_short_name>BCFL. Such direction from <customer_short_name> 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 <customer_short_name> BCFL data upon <customer_short_name>BCFL’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 <customer_short_name> BCFL customer records will be missing from LIDB, as measured by <customer_short_name> BCFL audits. BellSouth will audit <customer_short_name> BCFL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> BCFL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> BCFL within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>BCFL, 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 <customer_short_name> 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 <customer_short_name>BCFL’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 <customer_short_name> 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 <customer_short_name> BCFL and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> BCFL in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> BCFL at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> BCFL the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> BCFL under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name>US LEC, BellSouth shall provide <customer_short_name> US LEC with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> US LEC data to the LIDB shall be solely at the direction of <customer_short_name>US LEC. Such direction from <customer_short_name> 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 <customer_short_name> US LEC data upon <customer_short_name>US 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 <customer_short_name> US LEC customer records will be missing from LIDB, as measured by <customer_short_name> US LEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> US LEC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name>US 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 <customer_short_name> 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 <customer_short_name> US LEC and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> US LEC in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide <customer_short_name> 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 <customer_short_name> US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> US LEC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 BellSouth will offer to <customer_short_name> UTI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>UTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>UTI, BellSouth shall provide <customer_short_name> UTI with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> UTI data to the LIDB shall be solely at the direction of <customer_short_name>UTI. Such direction from <customer_short_name> 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 <customer_short_name> UTI data upon <customer_short_name>UTI’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 <customer_short_name> UTI customer records will be missing from LIDB, as measured by <customer_short_name> UTI audits. BellSouth will audit <customer_short_name> UTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> UTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> UTI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>UTI, 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 <customer_short_name> 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 <customer_short_name>UTI’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 <customer_short_name> 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 <customer_short_name> UTI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> UTI in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> UTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> UTI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> UTI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> Sail Networks any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Sail Networks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Sail Networks 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 <customer_short_name>Sail Networks, BellSouth shall provide <customer_short_name> Sail Networks with a list of the customer data items, which <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks data to the LIDB shall be solely at the direction of <customer_short_name>Sail Networks. Such direction from <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks data upon <customer_short_name>Sail Networks’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 <customer_short_name> Sail Networks customer records will be missing from LIDB, as measured by <customer_short_name> Sail Networks audits. BellSouth will audit <customer_short_name> Sail Networks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Sail Networks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Sail Networks within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Sail Networks, 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 <customer_short_name> Sail Networks 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 <customer_short_name>Sail Networks’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 <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Sail Networks the screening information associated with LIDB Data Screening of <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks 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 <customer_short_name> Sail Networks 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 <customer_short_name> ONS any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>’s ONS’ customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> ONS 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 <customer_short_name>ONS, BellSouth shall provide <customer_short_name> ONS with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> ONS data to the LIDB shall be solely at the direction of <customer_short_name>ONS. Such direction from <customer_short_name> 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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> ONS data upon <customer_short_name>’s ONS’ 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 <customer_short_name> ONS customer records will be missing from LIDB, as measured by <customer_short_name> ONS audits. BellSouth will audit <customer_short_name> ONS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ONS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ONS within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ONS, 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 <customer_short_name> ONS 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 <customer_short_name>’s ONS’ 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 <customer_short_name> 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 <customer_short_name> ONS and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ONS in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ONS at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ONS the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> ONS 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 <customer_short_name> ONS 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 <customer_short_name> Nexus any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Nexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Nexus 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 <customer_short_name>Nexus, BellSouth shall provide <customer_short_name> Nexus with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> Nexus data to the LIDB shall be solely at the direction of <customer_short_name>Nexus. Such direction from <customer_short_name> 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 BellSouth shall provide priority updates to LIDB for <customer_short_name> Nexus data upon <customer_short_name>Nexus’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 <customer_short_name> Nexus customer records will be missing from LIDB, as measured by <customer_short_name> Nexus audits. BellSouth will audit <customer_short_name> Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Nexus within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Nexus, 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 <customer_short_name> Nexus 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 <customer_short_name>Nexus’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 <customer_short_name> 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 <customer_short_name> Nexus and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Nexus in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Nexus the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Nexus under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> Nexus 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 <customer_short_name> Cinergy any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Cinergy’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Cinergy, BellSouth shall provide <customer_short_name> Cinergy with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Cinergy data to the LIDB shall be solely at the direction of <customer_short_name>Cinergy. Such direction from <customer_short_name> 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 <customer_short_name> Cinergy data upon <customer_short_name>Cinergy’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 <customer_short_name> Cinergy customer records will be missing from LIDB, as measured by <customer_short_name> Cinergy audits. BellSouth will audit <customer_short_name> Cinergy records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Cinergy contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Cinergy within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Cinergy, 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 <customer_short_name> 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 <customer_short_name>Cinergy’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 <customer_short_name> 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 <customer_short_name> Cinergy and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Cinergy in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Cinergy at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Cinergy the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Cinergy under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> NGTelecom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>NGTelecom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>NGTelecom, BellSouth shall provide <customer_short_name> NGTelecom with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> NGTelecom data to the LIDB shall be solely at the direction of <customer_short_name>NGTelecom. Such direction from <customer_short_name> 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 <customer_short_name> NGTelecom data upon <customer_short_name>NGTelecom’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 <customer_short_name> NGTelecom customer records will be missing from LIDB, as measured by <customer_short_name> NGTelecom audits. BellSouth will audit <customer_short_name> NGTelecom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> NGTelecom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> NGTelecom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>NGTelecom, 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 <customer_short_name> 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 <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 <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 <customer_short_name> and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>FeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>FeroNetworks, BellSouth shall provide <customer_short_name> FeroNetworks with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> FeroNetworks data to the LIDB shall be solely at the direction of <customer_short_name>FeroNetworks. Such direction from <customer_short_name> 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 <customer_short_name> FeroNetworks data upon <customer_short_name>FeroNetworks’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 <customer_short_name> FeroNetworks customer records will be missing from LIDB, as measured by <customer_short_name> FeroNetworks audits. BellSouth will audit <customer_short_name> FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> FeroNetworks within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>FeroNetworks, 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 <customer_short_name> 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 <customer_short_name>FeroNetworks’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 <customer_short_name> 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 <customer_short_name> FeroNetworks and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> FeroNetworks in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> FeroNetworks the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX One-Stop, BellSouth shall provide <customer_short_name> CBX One-Stop with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> CBX One-Stop data to the LIDB shall be solely at the direction of <customer_short_name>CBX One-Stop. Such direction from <customer_short_name> 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 <customer_short_name> CBX One-Stop data upon <customer_short_name>CBX 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 <customer_short_name> CBX One-Stop customer records will be missing from LIDB, as measured by <customer_short_name> CBX One- Stop audits. BellSouth will audit <customer_short_name> CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name> CBX One-Stop and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CBX One-Stop in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CBX One-Stop the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> GSC any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>GSC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>GSC, BellSouth shall provide <customer_short_name> GSC with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> GSC data to the LIDB shall be solely at the direction of <customer_short_name>GSC. Such direction from <customer_short_name> 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 <customer_short_name> GSC data upon <customer_short_name>GSC’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 <customer_short_name> GSC customer records will be missing from LIDB, as measured by <customer_short_name> GSC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> GSC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> GSC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> GSC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>GSC, 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 <customer_short_name> 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 <customer_short_name>GSC’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 <customer_short_name> 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 <customer_short_name> GSC and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> GSC in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> GSC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> GSC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> GSC under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 BellSouth will offer to <customer_short_name> ONS any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>ONS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>ONS, BellSouth shall provide <customer_short_name> ONS with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> ONS data to the LIDB shall be solely at the direction of <customer_short_name>ONS. Such direction from <customer_short_name> 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 <customer_short_name> ONS data upon <customer_short_name>ONS’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 <customer_short_name> ONS customer records will be missing from LIDB, as measured by <customer_short_name> ONS audits. BellSouth will audit <customer_short_name> ONS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ONS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ONS within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ONS, 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 <customer_short_name> 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 <customer_short_name>ONS’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 <customer_short_name> 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 <customer_short_name> ONS and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ONS in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ONS at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ONS the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> ONS under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Covista any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Covista’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Covista 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 <customer_short_name>Covista, BellSouth shall provide <customer_short_name> Covista with a list of the customer data items, which <customer_short_name> Covista 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 <customer_short_name> Covista data to the LIDB shall be solely at the direction of <customer_short_name>Covista. Such direction from <customer_short_name> Covista 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 <customer_short_name> Covista data upon <customer_short_name>Covista’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 <customer_short_name> Covista customer records will be missing from LIDB, as measured by <customer_short_name> Covista audits. BellSouth will audit <customer_short_name> Covista records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Covista contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Covista within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Covista, 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 <customer_short_name> Covista 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 <customer_short_name>Covista’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 <customer_short_name> Covista 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 <customer_short_name> Covista and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Covista 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 <customer_short_name> Covista in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Covista 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 <customer_short_name> Covista at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Covista the screening information associated with LIDB Data Screening of <customer_short_name> Covista 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 <customer_short_name> Covista 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 <customer_short_name> Covista 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 <customer_short_name> FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>FLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>FLATEL, BellSouth shall provide <customer_short_name> FLATEL with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> FLATEL data to the LIDB shall be solely at the direction of <customer_short_name>FLATEL. Such direction from <customer_short_name> 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 <customer_short_name> FLATEL data upon <customer_short_name>FLATEL’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 <customer_short_name> FLATEL customer records will be missing from LIDB, as measured by <customer_short_name> FLATEL audits. BellSouth will audit <customer_short_name> FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> FLATEL within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>FLATEL, 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 <customer_short_name> 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 <customer_short_name>FLATEL’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 <customer_short_name> 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 <customer_short_name> FLATEL and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> FLATEL in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> FLATEL the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> FLATEL under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> BSE any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>BSE’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> BSE 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 <customer_short_name>BSE, BellSouth shall provide <customer_short_name> BSE with a list of the customer data items, which <customer_short_name> BSE 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 <customer_short_name> BSE data to the LIDB shall be solely at the direction of <customer_short_name>BSE. Such direction from <customer_short_name> BSE 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 <customer_short_name> BSE data upon <customer_short_name>BSE’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 <customer_short_name> BSE customer records will be missing from LIDB, as measured by <customer_short_name> BSE audits. BellSouth will audit <customer_short_name> BSE records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> BSE contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> BSE within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>BSE, 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 <customer_short_name> BSE 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 <customer_short_name>BSE’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 <customer_short_name> BSE 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 <customer_short_name> BSE and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> BSE 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 <customer_short_name> BSE in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> BSE 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 <customer_short_name> BSE at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> BSE the screening information associated with LIDB Data Screening of <customer_short_name> BSE 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 <customer_short_name> BSE 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 <customer_short_name> BSE 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 <customer_short_name> NationNET any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>NationNET’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> NationNET 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 <customer_short_name>NationNET, BellSouth shall provide <customer_short_name> NationNET with a list of the customer data items, which <customer_short_name> NationNET 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 <customer_short_name> NationNET data to the LIDB shall be solely at the direction of <customer_short_name>NationNET. Such direction from <customer_short_name> NationNET 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 <customer_short_name> NationNET data upon <customer_short_name>NationNET’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 <customer_short_name> NationNET customer records will be missing from LIDB, as measured by <customer_short_name> NationNET audits. BellSouth will audit <customer_short_name> NationNET records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> NationNET contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> NationNET within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>NationNET, 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 <customer_short_name> NationNET 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 <customer_short_name>NationNET’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 <customer_short_name> NationNET 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 <customer_short_name> NationNET and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> NationNET 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 <customer_short_name> NationNET in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> NationNET 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 <customer_short_name> NationNET at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> NationNET the screening information associated with LIDB Data Screening of <customer_short_name> NationNET 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 <customer_short_name> NationNET under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> NationNET 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 <customer_short_name> 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 <customer_short_name>AmTel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>AmTel, BellSouth shall provide <customer_short_name> AmTel with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> AmTel data to the LIDB shall be solely at the direction of <customer_short_name>AmTel. Such direction from <customer_short_name> 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 <customer_short_name> AmTel data upon <customer_short_name>AmTel’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 <customer_short_name> AmTel customer records will be missing from LIDB, as measured by <customer_short_name> AmTel audits. BellSouth will audit <customer_short_name> AmTel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> AmTel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> AmTel within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>AmTel, 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 <customer_short_name> 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 <customer_short_name>AmTel’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 <customer_short_name> 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 <customer_short_name> AmTel and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> AmTel in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> AmTel at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> AmTel the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <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 <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ 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 <customer_short_name>▇▇▇▇▇▇▇▇.▇▇▇, BellSouth shall provide <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ with a list of the customer data items, which <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 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 <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of <customer_short_name>▇▇▇▇▇▇▇▇.▇▇▇. Such direction from <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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ data upon <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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ audits. BellSouth will audit <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <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 <customer_short_name> ▇▇▇▇▇▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>▇▇▇▇▇▇▇▇.▇▇▇, 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 <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 <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 <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 <customer_short_name> and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>MTS Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>MTS Communications, BellSouth shall provide <customer_short_name> MTS Communications with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> MTS Communications data to the LIDB shall be solely at the direction of <customer_short_name>MTS Communications. Such direction from <customer_short_name> 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 <customer_short_name> MTS Communications data upon <customer_short_name>MTS 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 <customer_short_name> MTS Communications customer records will be missing from LIDB, as measured by <customer_short_name> MTS Communications audits. BellSouth will audit <customer_short_name> MTS Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> MTS Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> MTS Communications within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>MTS 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 <customer_short_name> 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 <customer_short_name>MTS 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 <customer_short_name> 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 <customer_short_name> MTS Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> MTS Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> MTS Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> MTS Communications the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>’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 <customer_short_name> 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 <customer_short_name>ITC/\DeltaCom, BellSouth shall provide <customer_short_name> ITC/\DeltaCom with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom data to the LIDB shall be solely at the direction of <customer_short_name>ITC/\DeltaCom. Such direction from <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom data upon <customer_short_name>’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 <customer_short_name> ITC/\DeltaCom customer records will be missing from LIDB, as measured by <customer_short_name> ITC/\DeltaCom audits. BellSouth will audit <customer_short_name> ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ITC/\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 <customer_short_name> 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 <customer_short_name>’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 <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom and BellSouth.
7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom in writing.
7.3.2.13 15.4.2.12 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ITC/\DeltaCom the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>EPICUS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>EPICUS, BellSouth shall provide <customer_short_name> EPICUS with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> EPICUS data to the LIDB shall be solely at the direction of <customer_short_name>EPICUS. Such direction from <customer_short_name> 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 <customer_short_name> EPICUS data upon <customer_short_name>EPICUS’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 <customer_short_name> EPICUS customer records will be missing from LIDB, as measured by <customer_short_name> EPICUS audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> EPICUS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> EPICUS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> EPICUS within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>EPICUS, 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 <customer_short_name> 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 <customer_short_name>EPICUS’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 <customer_short_name> 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 <customer_short_name> EPICUS and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> EPICUS in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> EPICUS at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> EPICUS the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Hotline any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Hotline’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Hotline 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 <customer_short_name>Hotline, BellSouth shall provide <customer_short_name> Hotline with a list of the customer data items, which <customer_short_name> Hotline 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 <customer_short_name> Hotline data to the LIDB shall be solely at the direction of <customer_short_name>Hotline. Such direction from <customer_short_name> Hotline 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 <customer_short_name> Hotline data upon <customer_short_name>Hotline’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 <customer_short_name> Hotline customer records will be missing from LIDB, as measured by <customer_short_name> Hotline audits. BellSouth will audit <customer_short_name> Hotline records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Hotline contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Hotline within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Hotline, 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 <customer_short_name> Hotline 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 <customer_short_name>Hotline’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 <customer_short_name> Hotline 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 <customer_short_name> Hotline and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Hotline 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 <customer_short_name> Hotline in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Hotline 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 <customer_short_name> Hotline at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Hotline the screening information associated with LIDB Data Screening of <customer_short_name> Hotline 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 <customer_short_name> Hotline 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 <customer_short_name> Hotline 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 <customer_short_name> NationNET 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 <customer_short_name>NationNET’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> NationNET 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 <customer_short_name>NationNET, BellSouth shall provide <customer_short_name> NationNET with a list of the customer data items, items which <customer_short_name> NationNET 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 <customer_short_name> NationNET data to the LIDB shall be solely at the direction of <customer_short_name>NationNET. Such direction from <customer_short_name> NationNET 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 13.4.2.7 BellSouth shall provide priority updates to LIDB for <customer_short_name> NationNET data upon <customer_short_name>NationNET’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 <customer_short_name> NationNET customer records will be missing from LIDB, as measured by <customer_short_name> NationNET audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> NationNET records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> NationNET contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to <customer_short_name> NationNET within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>NationNET, 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 <customer_short_name> NationNET 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 <customer_short_name>NationNET’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 <customer_short_name> NationNET 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 <customer_short_name> NationNET and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> NationNET 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 <customer_short_name> NationNET in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide <customer_short_name> NationNET 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 <customer_short_name> NationNET at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> NationNET the screening information associated with LIDB Data Screening of <customer_short_name> NationNET 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 <customer_short_name> NationNET 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 <customer_short_name> NationNET 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 <customer_short_name> PBT any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>PBT’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>PBT, BellSouth shall provide <customer_short_name> PBT with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> PBT data to the LIDB shall be solely at the direction of <customer_short_name>PBT. Such direction from <customer_short_name> 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 <customer_short_name> PBT data upon <customer_short_name>PBT’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 <customer_short_name> PBT customer records will be missing from LIDB, as measured by <customer_short_name> PBT audits. BellSouth will audit <customer_short_name> PBT records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> PBT contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> PBT within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>PBT, 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 <customer_short_name> 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 <customer_short_name>PBT’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 <customer_short_name> 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 <customer_short_name> PBT and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> PBT in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> PBT at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> PBT the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> PBT under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> ACI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>ACI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> ACI 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 <customer_short_name>ACI, BellSouth shall provide <customer_short_name> ACI with a list of the customer data items, which <customer_short_name> ACI 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 <customer_short_name> ACI data to the LIDB shall be solely at the direction of <customer_short_name>ACI. Such direction from <customer_short_name> ACI 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 <customer_short_name> ACI data upon <customer_short_name>ACI’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 <customer_short_name> ACI customer records will be missing from LIDB, as measured by <customer_short_name> ACI audits. BellSouth will audit <customer_short_name> ACI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ACI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ACI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ACI, 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 <customer_short_name> ACI 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 <customer_short_name>ACI’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 <customer_short_name> ACI 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 <customer_short_name> ACI and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> ACI 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 <customer_short_name> ACI in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> ACI 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 <customer_short_name> ACI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ACI the screening information associated with LIDB Data Screening of <customer_short_name> ACI 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 <customer_short_name> ACI 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 <customer_short_name> ACI 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 <customer_short_name> 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 <customer_short_name>Symtelco’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Symtelco, BellSouth shall provide <customer_short_name> Symtelco with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Symtelco data to the LIDB shall be solely at the direction of <customer_short_name>Symtelco. Such direction from <customer_short_name> 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 <customer_short_name> Symtelco data upon <customer_short_name>Symtelco’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 <customer_short_name> Symtelco customer records will be missing from LIDB, as measured by <customer_short_name> Symtelco audits. BellSouth will audit <customer_short_name> Symtelco records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Symtelco contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Symtelco within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Symtelco, 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 <customer_short_name> 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 <customer_short_name>Symtelco’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 <customer_short_name> 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 <customer_short_name> Symtelco and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Symtelco in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Symtelco at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Symtelco the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 BellSouth will offer to <customer_short_name> Time Warner 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 <customer_short_name>’s customer Time ▇▇▇▇▇▇’▇ Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Time Warner 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 <customer_short_name>Time Warner, BellSouth shall provide <customer_short_name> Time Warner with a list of the customer data items, items which <customer_short_name> Time Warner 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 <customer_short_name> Time Warner data to the LIDB shall be solely at the direction of <customer_short_name>Time Warner. Such direction from <customer_short_name> Time Warner 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 <customer_short_name> Time Warner data upon <customer_short_name>Time Warner’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 <customer_short_name> Time Warner customer records will be missing from LIDB, as measured by <customer_short_name> Time Warner audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> Time Warner records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> Time Warner contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to <customer_short_name> Time Warner within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Time Warner, 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 <customer_short_name> Time ▇▇▇▇▇▇ 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 <customer_short_name>Time Warner’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 <customer_short_name> Time Warner 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 <customer_short_name> Time Warner and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> Time Warner 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 <customer_short_name> Time Warner in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide <customer_short_name> Time Warner 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 <customer_short_name> Time Warner at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Time Warner the screening information associated with LIDB Data Screening of <customer_short_name> Time Warner 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 <customer_short_name> Time Warner 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 <customer_short_name> Time Warner 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: Bellsouth / Clec Agreement
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> 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 <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX One-Stop, BellSouth shall provide <customer_short_name> CBX One-Stop with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> CBX One-Stop data to the LIDB shall be solely at the direction of <customer_short_name>CBX One-Stop. Such direction from <customer_short_name> 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 <customer_short_name> CBX One-Stop data upon <customer_short_name>CBX 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 <customer_short_name> CBX One-Stop customer records will be missing from LIDB, as measured by <customer_short_name> CBX One- Stop audits. BellSouth will audit <customer_short_name> CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name> CBX One-Stop and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CBX One-Stop in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CBX One-Stop the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>Lightning Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Lightning Communications, BellSouth shall provide <customer_short_name> Lightning Communications with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Lightning Communications data to the LIDB shall be solely at the direction of <customer_short_name>Lightning Communications. Such direction from <customer_short_name> 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 <customer_short_name> Lightning Communications data upon <customer_short_name>Lightning 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 <customer_short_name> Lightning Communications customer records will be missing from LIDB, as measured by <customer_short_name> Lightning Communications audits. BellSouth will audit <customer_short_name> Lightning Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Lightning Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Lightning Communications within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Lightning 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 <customer_short_name> 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 <customer_short_name>Lightning 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 <customer_short_name> 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 <customer_short_name> Lightning Communications and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Lightning Communications in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Lightning Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Lightning Communications the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Micro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Micro-Comm, BellSouth shall provide <customer_short_name> Micro-Comm with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Micro-Comm data to the LIDB shall be solely at the direction of <customer_short_name>Micro-Comm. Such direction from <customer_short_name> 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 <customer_short_name> Micro-Comm data upon <customer_short_name>Micro-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 <customer_short_name> Micro- Comm customer records will be missing from LIDB, as measured by <customer_short_name> Micro-Comm audits. BellSouth will audit <customer_short_name> Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Micro-Comm within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Micro-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 <customer_short_name> 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 <customer_short_name>Micro-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 <customer_short_name> 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 <customer_short_name> Micro-Comm and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Micro-Comm in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Micro-Comm the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 BellSouth will offer to <customer_short_name> Quality Telephone any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Quality Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Quality Telephone, BellSouth shall provide <customer_short_name> Quality Telephone with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Quality Telephone data to the LIDB shall be solely at the direction of <customer_short_name>Quality Telephone. Such direction from <customer_short_name> 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 <customer_short_name> Quality Telephone data upon <customer_short_name>Quality 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 <customer_short_name> Quality Telephone customer records will be missing from LIDB, as measured by <customer_short_name> Quality Telephone audits. BellSouth will audit <customer_short_name> Quality Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Quality Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Quality Telephone within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Quality 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 <customer_short_name> 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 <customer_short_name>Quality 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 <customer_short_name> 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 <customer_short_name> Quality Telephone and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Quality Telephone in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Quality Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Quality Telephone the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Budget 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 <customer_short_name>Budget Phone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Budget 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 <customer_short_name>Budget Phone, BellSouth shall provide <customer_short_name> Budget Phone with a list of the customer data items, which <customer_short_name> Budget 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 <customer_short_name> Budget Phone data to the LIDB shall be solely at the direction of <customer_short_name>Budget Phone. Such direction from <customer_short_name> Budget 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 <customer_short_name> Budget Phone data upon <customer_short_name>Budget 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 <customer_short_name> Budget Phone customer records will be missing from LIDB, as measured by <customer_short_name> Budget Phone audits. BellSouth will audit <customer_short_name> Budget Phone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Budget Phone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Budget Phone within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Budget 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 <customer_short_name> Budget 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 <customer_short_name>Budget 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 <customer_short_name> Budget 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 <customer_short_name> Budget Phone and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Budget 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 <customer_short_name> Budget Phone in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Budget 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 <customer_short_name> Budget Phone at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Budget Phone the screening information associated with LIDB Data Screening of <customer_short_name> Budget 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 <customer_short_name> Budget 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 <customer_short_name> Budget 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 16.3.2.1 BellSouth will offer to <customer_short_name> Nexus any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 16.3.2.2 BellSouth shall process <customer_short_name>Nexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Nexus what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 16.3.2.3 Within two (2) weeks after a request by <customer_short_name>Nexus, BellSouth shall provide <customer_short_name> Nexus with a list of the customer data items, which <customer_short_name> 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 16.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 16.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 16.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 16.3.2.7 All additions, updates and deletions of <customer_short_name> Nexus data to the LIDB shall be solely at the direction of <customer_short_name>Nexus. Such direction from <customer_short_name> 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 16.3.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> Nexus data upon <customer_short_name>Nexus’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 16.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> Nexus customer records will be missing from LIDB, as measured by <customer_short_name> Nexus audits. BellSouth will audit <customer_short_name> Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Nexus within one one
(1) business day of audit. Once reconciled records are received back from <customer_short_name>Nexus, 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 <customer_short_name> Nexus to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 16.3.2.10 BellSouth shall perform backup and recovery of all of <customer_short_name>Nexus’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 16.3.2.11 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nexus and BellSouth.
7.3.2.12 16.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Nexus in writing.
7.3.2.13 16.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Nexus the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Nexus under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 16.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> Nexus customer records and shall return responses in accordance with industry standards.
7.3.2.15 16.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 <customer_short_name> ▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <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 <customer_short_name> ▇▇▇.▇▇▇ 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 <customer_short_name>▇▇▇.▇▇▇, BellSouth shall provide <customer_short_name> ▇▇▇.▇▇▇ with a list of the customer data items, which <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 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 <customer_short_name> ▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of <customer_short_name>▇▇▇.▇▇▇. Such direction from <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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> ▇▇▇.▇▇▇ data upon <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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> ▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by <customer_short_name> ▇▇▇.▇▇▇ audits. BellSouth will audit <customer_short_name> ▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <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 <customer_short_name> ▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>▇▇▇.▇▇▇, 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 <customer_short_name> ▇▇▇.▇▇▇ 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 <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 9.2.11 BellSouth shall provide <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 <customer_short_name> ▇▇▇.▇▇▇ and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> ▇▇▇.▇▇▇ in writing.
7.3.2.13 9.2.13 BellSouth shall provide <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 <customer_short_name> ▇▇▇.▇▇▇ at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ▇▇▇.▇▇▇ the screening information associated with LIDB Data Screening of <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 <customer_short_name> ▇▇▇.▇▇▇ 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 <customer_short_name> ▇▇▇.▇▇▇ 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 <customer_short_name> BAK any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>BAK’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> BAK 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 <customer_short_name>BAK, BellSouth shall provide <customer_short_name> BAK with a list of the customer data items, which <customer_short_name> BAK 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 <customer_short_name> BAK data to the LIDB shall be solely at the direction of <customer_short_name>BAK. Such direction from <customer_short_name> BAK 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 <customer_short_name> BAK data upon <customer_short_name>BAK’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 <customer_short_name> BAK customer records will be missing from LIDB, as measured by <customer_short_name> BAK audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> BAK records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> BAK contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> BAK within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>BAK, 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 <customer_short_name> BAK 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 <customer_short_name>BAK’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 <customer_short_name> BAK 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 <customer_short_name> BAK and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> BAK 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 <customer_short_name> BAK in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> BAK 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 <customer_short_name> BAK at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> BAK the screening information associated with LIDB Data Screening of <customer_short_name> BAK 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 <customer_short_name> BAK 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 <customer_short_name> BAK 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 <customer_short_name> 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 <customer_short_name>Pilgrim Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Pilgrim Telephone, BellSouth shall provide <customer_short_name> Pilgrim Telephone with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Pilgrim Telephone data to the LIDB shall be solely at the direction of <customer_short_name>Pilgrim Telephone. Such direction from <customer_short_name> 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 <customer_short_name> Pilgrim Telephone data upon <customer_short_name>Pilgrim 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 <customer_short_name> Pilgrim Telephone customer records will be missing from LIDB, as measured by <customer_short_name> Pilgrim Telephone audits. BellSouth will audit <customer_short_name> Pilgrim Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Pilgrim Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Pilgrim Telephone within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Pilgrim 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 <customer_short_name> 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 <customer_short_name>Pilgrim 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 <customer_short_name> 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 <customer_short_name> Pilgrim Telephone and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Pilgrim Telephone in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Pilgrim Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Pilgrim Telephone the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>Excel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Excel, BellSouth shall provide <customer_short_name> Excel with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Excel data to the LIDB shall be solely at the direction of <customer_short_name>Excel. Such direction from <customer_short_name> 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 <customer_short_name> Excel data upon <customer_short_name>Excel’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 <customer_short_name> Excel customer records will be missing from LIDB, as measured by <customer_short_name> Excel audits. BellSouth will audit <customer_short_name> Excel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> Excel within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Excel, 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 <customer_short_name> 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 <customer_short_name>Excel’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 <customer_short_name> 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 <customer_short_name> Excel and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Excel in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Excel at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Excel the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Southern Light any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Southern Light’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Southern Light 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 <customer_short_name>Southern Light, BellSouth shall provide <customer_short_name> Southern Light with a list of the customer data items, which <customer_short_name> Southern Light 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 <customer_short_name> Southern Light data to the LIDB shall be solely at the direction of <customer_short_name>Southern Light. Such direction from <customer_short_name> Southern Light 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 <customer_short_name> Southern Light data upon <customer_short_name>Southern Light’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 <customer_short_name> Southern Light customer records will be missing from LIDB, as measured by <customer_short_name> Southern Light audits. BellSouth will audit <customer_short_name> Southern Light records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Southern Light contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Southern Light within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Southern Light, 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 <customer_short_name> Southern Light 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 <customer_short_name>Southern Light’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 <customer_short_name> Southern Light 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 <customer_short_name> Southern Light and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Southern Light 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 <customer_short_name> Southern Light in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Southern Light 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 <customer_short_name> Southern Light at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Southern Light the screening information associated with LIDB Data Screening of <customer_short_name> Southern Light 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 <customer_short_name> Southern Light 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 <customer_short_name> Southern Light 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 <customer_short_name> 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 <customer_short_name>MyLineToo’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>MyLineToo, BellSouth shall provide <customer_short_name> MyLineToo with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> MyLineToo data to the LIDB shall be solely at the direction of <customer_short_name>MyLineToo. Such direction from <customer_short_name> 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 <customer_short_name> MyLineToo data upon <customer_short_name>MyLineToo’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 <customer_short_name> MyLineToo customer records will be missing from LIDB, as measured by <customer_short_name> MyLineToo audits. BellSouth will audit <customer_short_name> MyLineToo records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> MyLineToo contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> MyLineToo within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>MyLineToo, 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 <customer_short_name> 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 <customer_short_name>MyLineToo’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 <customer_short_name> 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 <customer_short_name> MyLineToo and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> MyLineToo in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> MyLineToo at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> MyLineToo the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> CCI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>CCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> CCI 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 <customer_short_name>CCI, BellSouth shall provide <customer_short_name> CCI with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> CCI data to the LIDB shall be solely at the direction of <customer_short_name>CCI. Such direction from <customer_short_name> 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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> CCI data upon <customer_short_name>CCI’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 <customer_short_name> CCI customer records will be missing from LIDB, as measured by <customer_short_name> CCI audits. BellSouth will audit <customer_short_name> CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> CCI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CCI, 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 <customer_short_name> CCI 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 <customer_short_name>CCI’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 <customer_short_name> 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 <customer_short_name> CCI and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CCI in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CCI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> CCI 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 <customer_short_name> CCI 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 <customer_short_name> 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 <customer_short_name>EZ Phone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>EZ Phone, BellSouth shall provide <customer_short_name> EZ Phone with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> EZ Phone data to the LIDB shall be solely at the direction of <customer_short_name>EZ Phone. Such direction from <customer_short_name> 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 <customer_short_name> EZ Phone data upon <customer_short_name>EZ 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 <customer_short_name> EZ Phone customer records will be missing from LIDB, as measured by <customer_short_name> EZ Phone audits. BellSouth will audit <customer_short_name> EZ Phone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> EZ Phone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> EZ Phone within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>EZ 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 <customer_short_name> 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 <customer_short_name>EZ 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 <customer_short_name> 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 <customer_short_name> EZ Phone and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> EZ Phone in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> EZ Phone at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> EZ Phone the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Unity Acquisition any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Unity Acquisition’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Unity Acquisition 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 <customer_short_name>Unity Acquisition, BellSouth shall provide <customer_short_name> Unity Acquisition with a list of the customer data items, which <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition data to the LIDB shall be solely at the direction of <customer_short_name>Unity Acquisition. Such direction from <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition data upon <customer_short_name>Unity Acquisition’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 <customer_short_name> Unity Acquisition customer records will be missing from LIDB, as measured by <customer_short_name> Unity Acquisition audits. BellSouth will audit <customer_short_name> Unity Acquisition records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Unity Acquisition contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Unity Acquisition within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Unity Acquisition, 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 <customer_short_name> Unity Acquisition 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 <customer_short_name>Unity Acquisition’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 <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Unity Acquisition the screening information associated with LIDB Data Screening of <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition 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 <customer_short_name> Unity Acquisition 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 <customer_short_name> Southern Telcom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Southern Telcom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Southern Telcom 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 <customer_short_name>Southern Telcom, BellSouth shall provide <customer_short_name> Southern Telcom with a list of the customer data items, which <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom data to the LIDB shall be solely at the direction of <customer_short_name>Southern Telcom. Such direction from <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom data upon <customer_short_name>Southern Telcom’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 <customer_short_name> Southern Telcom customer records will be missing from LIDB, as measured by <customer_short_name> Southern Telcom audits. BellSouth will audit <customer_short_name> Southern Telcom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Southern Telcom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Southern Telcom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Southern Telcom, 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 <customer_short_name> Southern Telcom 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 <customer_short_name>Southern Telcom’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 <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Southern Telcom the screening information associated with LIDB Data Screening of <customer_short_name> Southern Telcom 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 <customer_short_name> Southern Telcom under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> Southern Telcom 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 <customer_short_name> CCI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>CCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>CCI, BellSouth shall provide <customer_short_name> CCI with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> CCI data to the LIDB shall be solely at the direction of <customer_short_name>CCI. Such direction from <customer_short_name> 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 <customer_short_name> CCI data upon <customer_short_name>CCI’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 <customer_short_name> CCI customer records will be missing from LIDB, as measured by <customer_short_name> CCI audits. BellSouth will audit <customer_short_name> CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> CCI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CCI, 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 <customer_short_name> 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 <customer_short_name>CCI’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 <customer_short_name> 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 <customer_short_name> CCI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CCI in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CCI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> CCI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>CLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>CLEC, BellSouth shall provide <customer_short_name> CLEC with a list of the customer data items, items which <customer_short_name> 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 <customer_short_name> CLEC data to the LIDB shall be solely at the direction of <customer_short_name>CLEC. Such direction from <customer_short_name> 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 <customer_short_name> CLEC data upon <customer_short_name>CLEC’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 <customer_short_name> CLEC customer records will be missing from LIDB, as measured by <customer_short_name> CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated <customer_short_name> 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 <customer_short_name> CLEC within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CLEC, 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 <customer_short_name> 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 <customer_short_name>CLEC’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 <customer_short_name> 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 <customer_short_name> CLEC and BellSouth.
7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CLEC in writing.
7.3.2.13 1.2.13.1 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CLEC the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> SPARDI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>SPARDI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> SPARDI 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 <customer_short_name>SPARDI, BellSouth shall provide <customer_short_name> SPARDI with a list of the customer data items, which <customer_short_name> SPARDI 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 <customer_short_name> SPARDI data to the LIDB shall be solely at the direction of <customer_short_name>SPARDI. Such direction from <customer_short_name> SPARDI 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 <customer_short_name> SPARDI data upon <customer_short_name>SPARDI’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 <customer_short_name> SPARDI customer records will be missing from LIDB, as measured by <customer_short_name> SPARDI audits. BellSouth will audit <customer_short_name> SPARDI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> SPARDI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> SPARDI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>SPARDI, 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 <customer_short_name> SPARDI 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 <customer_short_name>SPARDI’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 <customer_short_name> SPARDI 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 <customer_short_name> SPARDI and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> SPARDI 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 <customer_short_name> SPARDI in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> SPARDI 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 <customer_short_name> SPARDI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> SPARDI the screening information associated with LIDB Data Screening of <customer_short_name> SPARDI 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 <customer_short_name> SPARDI 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 <customer_short_name> SPARDI 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 <customer_short_name> Preferred any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Preferred’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Preferred, BellSouth shall provide <customer_short_name> Preferred with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Preferred data to the LIDB shall be solely at the direction of <customer_short_name>Preferred. Such direction from <customer_short_name> 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 <customer_short_name> Preferred data upon <customer_short_name>Preferred’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 <customer_short_name> Preferred customer records will be missing from LIDB, as measured by <customer_short_name> Preferred audits. BellSouth will audit <customer_short_name> Preferred records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Preferred contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Preferred within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Preferred, 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 <customer_short_name> 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 <customer_short_name>Preferred’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 <customer_short_name> 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 <customer_short_name> Preferred and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Preferred in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Preferred at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Preferred the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> Preferred under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 BellSouth will offer to <customer_short_name> Connect! any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 14.4.2.1 BellSouth shall process <customer_short_name>Connect!’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Connect! what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 14.4.2.2 Within two (2) weeks after a request by <customer_short_name>Connect!, BellSouth shall provide <customer_short_name> Connect! with a list of the customer data items, items which <customer_short_name> Connect! 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 14.4.2.3 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 14.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 14.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 14.4.2.6 All additions, updates and deletions of <customer_short_name> Connect! data to the LIDB shall be solely at the direction of <customer_short_name>Connect!. Such direction from <customer_short_name> Connect! 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 14.4.2.7 BellSouth shall provide priority updates to LIDB for <customer_short_name> Connect! data upon <customer_short_name>Connect!’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 14.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> Connect! customer records will be missing from LIDB, as measured by <customer_short_name> Connect! audits. BellSouth will audit <customer_short_name> Connect! records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> Connect! contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Connect! within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Connect!, 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 <customer_short_name> Connect! to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 14.4.2.9 BellSouth shall perform backup and recovery of all of <customer_short_name>Connect!’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 14.4.2.10 BellSouth shall provide <customer_short_name> Connect! 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 <customer_short_name> Connect! and BellSouth.
7.3.2.12 14.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> Connect! 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 <customer_short_name> Connect! in writing.
7.3.2.13 14.4.2.12 BellSouth shall provide <customer_short_name> Connect! 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 <customer_short_name> Connect! at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Connect! the screening information associated with LIDB Data Screening of <customer_short_name> Connect! 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 <customer_short_name> Connect! under the BFRBona Fide Request/NBR New Business Process as set forth in Attachment 11General Terms and Conditions .
7.3.2.14 14.4.2.13 BellSouth shall accept queries to LIDB associated with <customer_short_name> Connect! customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 14.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 14.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 9.2.1 BellSouth will offer to <customer_short_name> Utility USA any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Utility USA’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Utility USA 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 <customer_short_name>Utility USA, BellSouth shall provide <customer_short_name> Utility USA with a list of the customer data items, which <customer_short_name> Utility USA 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 <customer_short_name> Utility USA data to the LIDB shall be solely at the direction of <customer_short_name>Utility USA. Such direction from <customer_short_name> Utility USA 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 <customer_short_name> Utility USA data upon <customer_short_name>Utility USA’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 <customer_short_name> Utility USA customer records will be missing from LIDB, as measured by <customer_short_name> Utility USA audits. BellSouth will audit <customer_short_name> Utility USA records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Utility USA contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Utility USA within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Utility USA, 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 <customer_short_name> Utility USA 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 <customer_short_name>Utility USA’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 <customer_short_name> Utility USA 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 <customer_short_name> Utility USA and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Utility USA 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 <customer_short_name> Utility USA in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Utility USA 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 <customer_short_name> Utility USA at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Utility USA the screening information associated with LIDB Data Screening of <customer_short_name> Utility USA 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 <customer_short_name> Utility USA 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 <customer_short_name> Utility USA 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 <customer_short_name> ProNet any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>ProNet’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>ProNet, BellSouth shall provide <customer_short_name> ProNet with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> ProNet data to the LIDB shall be solely at the direction of <customer_short_name>ProNet. Such direction from <customer_short_name> 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 <customer_short_name> ProNet data upon <customer_short_name>ProNet’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 <customer_short_name> ProNet customer records will be missing from LIDB, as measured by <customer_short_name> ProNet audits. BellSouth will audit <customer_short_name> ProNet records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ProNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ProNet within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ProNet, 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 <customer_short_name> 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 <customer_short_name>ProNet’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 <customer_short_name> 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 <customer_short_name> ProNet and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ProNet in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ProNet at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ProNet the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> ProNet under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 <customer_short_name> Southern Digital any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Southern Digital’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Southern Digital, BellSouth shall provide <customer_short_name> Southern Digital with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Southern Digital data to the LIDB shall be solely at the direction of <customer_short_name>Southern Digital. Such direction from <customer_short_name> 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 <customer_short_name> Southern Digital data upon <customer_short_name>Southern 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 <customer_short_name> Southern Digital customer records will be missing from LIDB, as measured by <customer_short_name> Southern Digital audits. BellSouth will audit <customer_short_name> Southern Digital records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Southern Digital contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Southern Digital within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Southern 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 <customer_short_name> 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 <customer_short_name>Southern 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 <customer_short_name> 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 <customer_short_name> Southern Digital and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Southern Digital in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Southern Digital at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Southern Digital the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Southern Telecom any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Southern Telecom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Southern Telecom 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 <customer_short_name>Southern Telecom, BellSouth shall provide <customer_short_name> Southern Telecom with a list of the customer data items, which <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom data to the LIDB shall be solely at the direction of <customer_short_name>Southern Telecom. Such direction from <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom data upon <customer_short_name>Southern Telecom’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 <customer_short_name> Southern Telecom customer records will be missing from LIDB, as measured by <customer_short_name> Southern Telecom audits. BellSouth will audit <customer_short_name> Southern Telecom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Southern Telecom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Southern Telecom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Southern Telecom, 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 <customer_short_name> Southern Telecom 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 <customer_short_name>Southern Telecom’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 <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Southern Telecom the screening information associated with LIDB Data Screening of <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom 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 <customer_short_name> Southern Telecom 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 <customer_short_name> 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 <customer_short_name>Comm South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Comm South, BellSouth shall provide <customer_short_name> Comm South with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Comm South data to the LIDB shall be solely at the direction of <customer_short_name>Comm South. Such direction from <customer_short_name> 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 <customer_short_name> Comm South data upon <customer_short_name>Comm 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 <customer_short_name> Comm South customer records will be missing from LIDB, as measured by <customer_short_name> Comm South audits. BellSouth will audit <customer_short_name> Comm South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Comm South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Comm South within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Comm 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 <customer_short_name> 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 <customer_short_name>Comm 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 <customer_short_name> 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 <customer_short_name> Comm South and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Comm South in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Comm South at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Comm South the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> NTBS any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>NTBS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> NTBS 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 <customer_short_name>NTBS, BellSouth shall provide <customer_short_name> NTBS with a list of the customer data items, which <customer_short_name> NTBS 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 <customer_short_name> NTBS data to the LIDB shall be solely at the direction of <customer_short_name>NTBS. Such direction from <customer_short_name> NTBS 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 <customer_short_name> NTBS data upon <customer_short_name>NTBS’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 <customer_short_name> NTBS customer records will be missing from LIDB, as measured by <customer_short_name> NTBS audits. BellSouth will audit <customer_short_name> NTBS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> NTBS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> NTBS within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>NTBS, 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 <customer_short_name> NTBS 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 <customer_short_name>NTBS’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 <customer_short_name> NTBS 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 <customer_short_name> NTBS and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> NTBS 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 <customer_short_name> NTBS in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> NTBS 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 <customer_short_name> NTBS at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> NTBS the screening information associated with LIDB Data Screening of <customer_short_name> NTBS 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 <customer_short_name> NTBS 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 <customer_short_name> NTBS 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 <customer_short_name> Deland Actel any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Deland Actel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Deland Actel 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 <customer_short_name>Deland Actel, BellSouth shall provide <customer_short_name> Deland Actel with a list of the customer data items, which <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel data to the LIDB shall be solely at the direction of <customer_short_name>Deland Actel. Such direction from <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel data upon <customer_short_name>Deland Actel’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 <customer_short_name> Deland Actel customer records will be missing from LIDB, as measured by <customer_short_name> Deland Actel audits. BellSouth will audit <customer_short_name> Deland Actel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Deland Actel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Deland Actel within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Deland Actel, 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 <customer_short_name> Deland Actel 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 <customer_short_name>Deland Actel’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 <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Deland Actel the screening information associated with LIDB Data Screening of <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel 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 <customer_short_name> Deland Actel 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 <customer_short_name> FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>FeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>FeroNetworks, BellSouth shall provide <customer_short_name> FeroNetworks with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> FeroNetworks data to the LIDB shall be solely at the direction of <customer_short_name>FeroNetworks. Such direction from <customer_short_name> 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 <customer_short_name> FeroNetworks data upon <customer_short_name>FeroNetworks’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 <customer_short_name> FeroNetworks customer records will be missing from LIDB, as measured by <customer_short_name> FeroNetworks audits. BellSouth will audit <customer_short_name> FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> FeroNetworks within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>FeroNetworks, 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 <customer_short_name> 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 <customer_short_name>FeroNetworks’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 <customer_short_name> 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 <customer_short_name> FeroNetworks and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> FeroNetworks in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> FeroNetworks the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> FeroNetworks under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Victory any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Victory’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Victory 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 <customer_short_name>Victory, BellSouth shall provide <customer_short_name> Victory with a list of the customer data items, which <customer_short_name> Victory 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 <customer_short_name> Victory data to the LIDB shall be solely at the direction of <customer_short_name>Victory. Such direction from <customer_short_name> Victory 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 <customer_short_name> Victory data upon <customer_short_name>Victory’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 <customer_short_name> Victory customer records will be missing from LIDB, as measured by <customer_short_name> Victory audits. BellSouth will audit <customer_short_name> Victory records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Victory contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Victory within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Victory, 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 <customer_short_name> Victory 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 <customer_short_name>Victory’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 <customer_short_name> Victory 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 <customer_short_name> Victory and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Victory 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 <customer_short_name> Victory in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Victory 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 <customer_short_name> Victory at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Victory the screening information associated with LIDB Data Screening of <customer_short_name> Victory 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 <customer_short_name> Victory 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 <customer_short_name> Victory 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 <customer_short_name> 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 <customer_short_name>Micro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Micro-Comm, BellSouth shall provide <customer_short_name> Micro-Comm with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Micro-Comm data to the LIDB shall be solely at the direction of <customer_short_name>Micro-Comm. Such direction from <customer_short_name> 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 <customer_short_name> Micro-Comm data upon <customer_short_name>Micro-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 <customer_short_name> Micro- Comm customer records will be missing from LIDB, as measured by <customer_short_name> Micro-Comm audits. BellSouth will audit <customer_short_name> Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Micro-Comm within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Micro-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 <customer_short_name> 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 <customer_short_name>Micro-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 <customer_short_name> 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 <customer_short_name> Micro-Comm and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Micro-Comm in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Micro-Comm the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>ICG’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>ICG, BellSouth shall provide <customer_short_name> ICG with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> ICG data to the LIDB shall be solely at the direction of <customer_short_name>ICG. Such direction from <customer_short_name> 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 <customer_short_name> ICG data upon <customer_short_name>ICG’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 <customer_short_name> ICG customer records will be missing from LIDB, as measured by <customer_short_name> ICG audits. BellSouth will audit <customer_short_name> ICG records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> ICG contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> ICG within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ICG, 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 <customer_short_name> 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 <customer_short_name>ICG’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 <customer_short_name> 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 <customer_short_name> ICG and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ICG in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ICG at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ICG the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 8.2.1 BellSouth will offer to <customer_short_name> DukeNet any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 8.2.2 BellSouth shall process <customer_short_name>DukeNet’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> DukeNet 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 <customer_short_name>DukeNet, BellSouth shall provide <customer_short_name> DukeNet with a list of the customer data items, which <customer_short_name> DukeNet 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 <customer_short_name> DukeNet data to the LIDB shall be solely at the direction of <customer_short_name>DukeNet. Such direction from <customer_short_name> DukeNet 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 8.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> DukeNet data upon <customer_short_name>DukeNet’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 8.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> DukeNet customer records will be missing from LIDB, as measured by <customer_short_name> DukeNet audits. BellSouth will audit <customer_short_name> DukeNet records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> DukeNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to <customer_short_name> DukeNet within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>DukeNet, 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 <customer_short_name> DukeNet to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 8.2.10 BellSouth shall perform backup and recovery of all of <customer_short_name>DukeNet’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 8.2.11 BellSouth shall provide <customer_short_name> DukeNet with LIDB reports of data data, which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between <customer_short_name> DukeNet and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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 1 contract
Sources: Telecommunications
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> Ruddata any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Ruddata’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Ruddata 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 <customer_short_name>Ruddata, BellSouth shall provide <customer_short_name> Ruddata with a list of the customer data items, which <customer_short_name> Ruddata 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 <customer_short_name> Ruddata data to the LIDB shall be solely at the direction of <customer_short_name>Ruddata. Such direction from <customer_short_name> Ruddata 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 <customer_short_name> Ruddata data upon <customer_short_name>Ruddata’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 <customer_short_name> Ruddata customer records will be missing from LIDB, as measured by <customer_short_name> Ruddata audits. BellSouth will audit <customer_short_name> Ruddata records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Ruddata contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Ruddata within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Ruddata, 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 <customer_short_name> Ruddata 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 <customer_short_name>Ruddata’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 <customer_short_name> Ruddata 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 <customer_short_name> Ruddata and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Ruddata 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 <customer_short_name> Ruddata in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Ruddata 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 <customer_short_name> Ruddata at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Ruddata the screening information associated with LIDB Data Screening of <customer_short_name> Ruddata 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 <customer_short_name> Ruddata 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 <customer_short_name> Ruddata 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 <customer_short_name> ▇▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <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 <customer_short_name> ▇▇▇▇ 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 <customer_short_name>▇▇▇▇, BellSouth shall provide <customer_short_name> ▇▇▇▇ with a list of the customer data items, which <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 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 <customer_short_name> ▇▇▇▇ data to the LIDB shall be solely at the direction of <customer_short_name>▇▇▇▇. Such direction from <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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> ▇▇▇▇ data upon <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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> ▇▇▇▇ customer records will be missing from LIDB, as measured by <customer_short_name> ▇▇▇▇ audits. BellSouth will audit <customer_short_name> ▇▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <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 <customer_short_name> ▇▇▇▇ within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Reed, 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 <customer_short_name> ▇▇▇▇ 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 <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 9.2.11 BellSouth shall provide <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 <customer_short_name> ▇▇▇▇ and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> ▇▇▇▇ in writing.
7.3.2.13 9.2.13 BellSouth shall provide <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 <customer_short_name> ▇▇▇▇ at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ▇▇▇▇ the screening information associated with LIDB Data Screening of <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 <customer_short_name> ▇▇▇▇ 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 <customer_short_name> ▇▇▇▇ 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 <customer_short_name> PLI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>PLI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> PLI 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 <customer_short_name>PLI, BellSouth shall provide <customer_short_name> PLI with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> PLI data to the LIDB shall be solely at the direction of <customer_short_name>PLI. Such direction from <customer_short_name> 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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> data upon <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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> PLI customer records will be missing from LIDB, as measured by <customer_short_name> PLI audits. BellSouth will audit <customer_short_name> PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> PLI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>PLI, 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 <customer_short_name> PLI 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 <customer_short_name>PLI’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 <customer_short_name> 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 <customer_short_name> PLI and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> PLI in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> PLI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> PLI 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 <customer_short_name> PLI 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 <customer_short_name> 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 <customer_short_name>TeleConex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>TeleConex, BellSouth shall provide <customer_short_name> TeleConex with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> TeleConex data to the LIDB shall be solely at the direction of <customer_short_name>TeleConex. Such direction from <customer_short_name> 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 <customer_short_name> TeleConex data upon <customer_short_name>TeleConex’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 <customer_short_name> TeleConex customer records will be missing from LIDB, as measured by <customer_short_name> TeleConex audits. BellSouth will audit <customer_short_name> TeleConex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> TeleConex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> TeleConex within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>TeleConex, 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 <customer_short_name> 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 <customer_short_name>TeleConex’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 <customer_short_name> 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 <customer_short_name> TeleConex and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> TeleConex in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> TeleConex at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> TeleConex the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Seven Bridges any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>’s Seven ▇▇▇▇▇▇▇’▇ customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Seven Bridges, BellSouth shall provide <customer_short_name> Seven Bridges with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Seven Bridges data to the LIDB shall be solely at the direction of <customer_short_name>Seven Bridges. Such direction from <customer_short_name> 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 <customer_short_name> Seven Bridges data upon <customer_short_name>’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 <customer_short_name> Seven Bridges customer records will be missing from LIDB, as measured by <customer_short_name> Seven Bridges audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> Seven Bridges records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Seven Bridges contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Seven Bridges within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Seven 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 <customer_short_name> 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 <customer_short_name>’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 <customer_short_name> 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 <customer_short_name> Seven Bridges and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Seven ▇▇▇▇▇▇▇ in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Seven Bridges at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Seven Bridges the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Triarch Marketing any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Triarch Marketing’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Triarch Marketing 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 <customer_short_name>Triarch Marketing, BellSouth shall provide <customer_short_name> Triarch Marketing with a list of the customer data items, which <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing data to the LIDB shall be solely at the direction of <customer_short_name>Triarch Marketing. Such direction from <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing data upon <customer_short_name>Triarch Marketing’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 <customer_short_name> Triarch Marketing customer records will be missing from LIDB, as measured by <customer_short_name> Triarch Marketing audits. BellSouth will audit <customer_short_name> Triarch Marketing records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Triarch Marketing contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Triarch Marketing within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Triarch Marketing, 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 <customer_short_name> Triarch Marketing 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 <customer_short_name>Triarch Marketing’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 <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Triarch Marketing the screening information associated with LIDB Data Screening of <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing 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 <customer_short_name> Triarch Marketing 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 <customer_short_name> Excel PCHP any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Excel PCHP’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Excel PCHP, BellSouth shall provide <customer_short_name> Excel PCHP with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Excel PCHP data to the LIDB shall be solely at the direction of <customer_short_name>Excel PCHP. Such direction from <customer_short_name> 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 <customer_short_name> Excel PCHP data upon <customer_short_name>Excel 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 <customer_short_name> Excel PCHP customer records will be missing from LIDB, as measured by <customer_short_name> Excel PCHP audits. BellSouth will audit <customer_short_name> Excel PCHP records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Excel PCHP contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Excel PCHP within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Excel 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 <customer_short_name> 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 <customer_short_name>Excel 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 <customer_short_name> 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 <customer_short_name> Excel PCHP and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Excel PCHP in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Excel PCHP at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Excel PCHP the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 9.2.1 BellSouth will offer to <customer_short_name> Velocity any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>Velocity’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Velocity 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 <customer_short_name>Velocity, BellSouth shall provide <customer_short_name> Velocity with a list of the customer data items, which <customer_short_name> Velocity 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 <customer_short_name> Velocity data to the LIDB shall be solely at the direction of <customer_short_name>Velocity. Such direction from <customer_short_name> Velocity 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 <customer_short_name> Velocity data upon <customer_short_name>Velocity’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 <customer_short_name> Velocity customer records will be missing from LIDB, as measured by <customer_short_name> Velocity audits. BellSouth will audit <customer_short_name> Velocity records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Velocity contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Velocity within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Velocity, 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 <customer_short_name> Velocity 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 <customer_short_name>Velocity’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 <customer_short_name> Velocity 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 <customer_short_name> Velocity and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Velocity 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 <customer_short_name> Velocity in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Velocity 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 <customer_short_name> Velocity at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Velocity the screening information associated with LIDB Data Screening of <customer_short_name> Velocity 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 <customer_short_name> Velocity 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 <customer_short_name> Velocity 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 6.1.2.1 BellSouth will offer to <customer_short_name> Frankfort Plant Board any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 6.1.2.2 BellSouth shall process <customer_short_name>Frankfort Plant Board’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Frankfort Plant Board what additional functions (if any) are performed by LIDB in the BellSouth network.
7.3.2.3 6.1.2.3 Within two (2) weeks after a request by <customer_short_name>Frankfort Plant Board, BellSouth shall provide <customer_short_name> Frankfort Plant Board with a list of the customer data items, items which <customer_short_name> Frankfort Plant Board 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 6.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 6.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 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 6.1.2.7 All additions, updates and deletions of <customer_short_name> Frankfort Plant Board data to the LIDB shall be solely at the direction of <customer_short_name>Frankfort Plant Board. Such direction from <customer_short_name> Frankfort Plant Board 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 6.1.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> Frankfort Plant Board data upon <customer_short_name>Frankfort Plant Board’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 6.1.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> Frankfort Plant Board customer records will be missing from LIDB, as measured by <customer_short_name> Frankfort Plant Board audits. BellSouth will audit <customer_short_name> Frankfort Plant Board records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> Frankfort Plant Board contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to <customer_short_name> Frankfort Plant Board within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Frankfort Plant Board, 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 <customer_short_name> Frankfort Plant Board to negotiate a time frame for the updates, not to exceed three (3) business days.
7.3.2.10 6.1.2.10 BellSouth shall perform backup and recovery of all of <customer_short_name>Frankfort Plant Board’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 6.1.2.11 BellSouth shall provide <customer_short_name> Frankfort Plant Board 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 <customer_short_name> Frankfort Plant Board and BellSouth.
7.3.2.12 6.1.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Frankfort Plant Board 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 <customer_short_name> Frankfort Plant Board in writing.
7.3.2.13 6.1.2.13 BellSouth shall provide <customer_short_name> Frankfort Plant Board 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 - 0/1XX wholly or partially owned by <customer_short_name> Frankfort Plant Board at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Frankfort Plant Board the screening information associated with LIDB Data Screening of <customer_short_name> Frankfort Plant Board 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 <customer_short_name> Frankfort Plant Board under the BFRBona Fide Request/NBR New Business Process as set forth in Attachment 11General Terms and Conditions .
7.3.2.14 6.1.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> Frankfort Plant Board customer records records, and shall return responses in accordance with industry standards.
7.3.2.15 6.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 6.1.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 <customer_short_name> CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX One-Stop, BellSouth shall provide <customer_short_name> CBX One-Stop with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> CBX One-Stop data to the LIDB shall be solely at the direction of <customer_short_name>CBX One-Stop. Such direction from <customer_short_name> 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 <customer_short_name> CBX One-Stop data upon <customer_short_name>CBX 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 <customer_short_name> CBX One-Stop customer records will be missing from LIDB, as measured by <customer_short_name> CBX One- Stop audits. BellSouth will audit <customer_short_name> CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name>CBX 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 <customer_short_name> 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 <customer_short_name> CBX One-Stop and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CBX One-Stop in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CBX One-Stop the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Think 12 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Think 12’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Think 12, BellSouth shall provide <customer_short_name> Think 12 with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Think 12 data to the LIDB shall be solely at the direction of <customer_short_name>Think 12. Such direction from <customer_short_name> 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 <customer_short_name> Think 12 data upon <customer_short_name>Think 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 <customer_short_name> Think 12 customer records will be missing from LIDB, as measured by <customer_short_name> Think 12 audits. BellSouth will audit <customer_short_name> Think 12 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Think 12 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Think 12 within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Think 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 <customer_short_name> 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 <customer_short_name>Think 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 <customer_short_name> 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 <customer_short_name> Think 12 and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Think 12 in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Think 12 at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Think 12 the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>Nex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Nex-Phon, BellSouth shall provide <customer_short_name> Nex- Phon with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Nex-Phon data to the LIDB shall be solely at the direction of <customer_short_name>Nex-Phon. Such direction from <customer_short_name> 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 <customer_short_name> Nex-Phon data upon <customer_short_name>Nex- 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 <customer_short_name> Nex-Phon customer records will be missing from LIDB, as measured by <customer_short_name> Nex-Phon audits. BellSouth will audit <customer_short_name> Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Nex-Phon within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Nex-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 <customer_short_name> 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 <customer_short_name>Nex-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 <customer_short_name> 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 <customer_short_name> Nex-Phon and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Nex-Phon in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Nex-Phon the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> US South any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>US South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>US South, BellSouth shall provide <customer_short_name> US South with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> US South data to the LIDB shall be solely at the direction of <customer_short_name>US South. Such direction from <customer_short_name> 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 <customer_short_name> US South data upon <customer_short_name>US 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 <customer_short_name> US South customer records will be missing from LIDB, as measured by <customer_short_name> US South audits. BellSouth will audit <customer_short_name> US South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> US South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> US South within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>US 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 <customer_short_name> 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 <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 <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 <customer_short_name> and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <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 <customer_short_name> in writing.
7.3.2.13 BellSouth shall provide <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 <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <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 <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 <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.three
Appears in 1 contract
Sources: Interconnection Agreement
Technical Requirements. 7.3.2.1 BellSouth will offer to <customer_short_name> Aero any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Aero’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Aero 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 <customer_short_name>Aero, BellSouth shall provide <customer_short_name> Aero with a list of the customer data items, which <customer_short_name> Aero 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 <customer_short_name> Aero data to the LIDB shall be solely at the direction of <customer_short_name>Aero. Such direction from <customer_short_name> Aero 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 <customer_short_name> Aero data upon <customer_short_name>Aero’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 <customer_short_name> Aero customer records will be missing from LIDB, as measured by <customer_short_name> Aero audits. BellSouth will audit <customer_short_name> Aero records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Aero contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Aero within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Aero, 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 <customer_short_name> Aero 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 <customer_short_name>Aero’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 <customer_short_name> Aero 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 <customer_short_name> Aero and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Aero 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 <customer_short_name> Aero in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> Aero 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 <customer_short_name> Aero at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Aero the screening information associated with LIDB Data Screening of <customer_short_name> Aero 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 <customer_short_name> Aero under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> Aero 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 <customer_short_name> FPB any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 9.2.2 BellSouth shall process <customer_short_name>FPB’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> FPB 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 <customer_short_name>FPB, BellSouth shall provide <customer_short_name> FPB with a list of the customer data items, which <customer_short_name> 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 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 <customer_short_name> FPB data to the LIDB shall be solely at the direction of <customer_short_name>FPB. Such direction from <customer_short_name> 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 9.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> FPB data upon <customer_short_name>FPB’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 <customer_short_name> FPB customer records will be missing from LIDB, as measured by <customer_short_name> FPB audits. BellSouth will audit <customer_short_name> FPB records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> FPB contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> FPB within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>FPB, 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 <customer_short_name> FPB 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 <customer_short_name>FPB’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 <customer_short_name> 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 <customer_short_name> FPB and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> FPB in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> FPB at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> FPB the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> FPB 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 <customer_short_name> FPB 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 <customer_short_name> 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 <customer_short_name>Advantage Group’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Advantage Group, BellSouth shall provide <customer_short_name> Advantage Group with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Advantage Group data to the LIDB shall be solely at the direction of <customer_short_name>Advantage Group. Such direction from <customer_short_name> 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 <customer_short_name> Advantage Group data upon <customer_short_name>Advantage 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 <customer_short_name> Advantage Group customer records will be missing from LIDB, as measured by <customer_short_name> Advantage Group audits. BellSouth will audit <customer_short_name> Advantage Group records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Advantage Group contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Advantage Group within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Advantage 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 <customer_short_name> 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 <customer_short_name>Advantage 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 <customer_short_name> 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 <customer_short_name> Advantage Group and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Advantage Group in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Advantage Group at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Advantage Group the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Metro 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 <customer_short_name>Metro Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> Metro 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 <customer_short_name>Metro Teleconnect, BellSouth shall provide <customer_short_name> Metro Teleconnect with a list of the customer data items, which <customer_short_name> Metro 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 <customer_short_name> Metro Teleconnect data to the LIDB shall be solely at the direction of <customer_short_name>Metro Teleconnect. Such direction from <customer_short_name> Metro Teleconnect 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 <customer_short_name> Metro Teleconnect data upon <customer_short_name>Metro 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 <customer_short_name> Metro Teleconnect customer records will be missing from LIDB, as measured by <customer_short_name> Metro Teleconnect audits. BellSouth will audit <customer_short_name> Metro Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Metro Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Metro Teleconnect within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Metro 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 <customer_short_name> Metro 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 <customer_short_name>Metro 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 <customer_short_name> Metro 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 <customer_short_name> Metro Teleconnect and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> Metro 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 <customer_short_name> Metro Teleconnect in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> Metro 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 <customer_short_name> Metro Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Metro Teleconnect the screening information associated with LIDB Data Screening of <customer_short_name> Metro 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 <customer_short_name> Metro 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 <customer_short_name> Metro 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 <customer_short_name> Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Nex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>Nex-Phon, BellSouth shall provide <customer_short_name> Nex- Phon with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Nex-Phon data to the LIDB shall be solely at the direction of <customer_short_name>Nex-Phon. Such direction from <customer_short_name> 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 <customer_short_name> Nex-Phon data upon <customer_short_name>Nex- 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 <customer_short_name> Nex-Phon customer records will be missing from LIDB, as measured by <customer_short_name> Nex-Phon audits. BellSouth will audit <customer_short_name> Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Nex-Phon within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Nex-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 <customer_short_name> 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 <customer_short_name>Nex-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 <customer_short_name> 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 <customer_short_name> Nex-Phon and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Nex-Phon in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Nex-Phon the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name>DPI Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>DPI Teleconnect, BellSouth shall provide <customer_short_name> DPI Teleconnect with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> DPI Teleconnect data to the LIDB shall be solely at the direction of <customer_short_name>DPI Teleconnect. Such direction from <customer_short_name> 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 <customer_short_name> DPI Teleconnect data upon <customer_short_name>DPI 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 <customer_short_name> DPI Teleconnect customer records will be missing from LIDB, as measured by <customer_short_name> DPI Teleconnect audits. BellSouth will audit <customer_short_name> DPI Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> DPI Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> DPI Teleconnect within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>DPI 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 <customer_short_name> 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 <customer_short_name>DPI 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 <customer_short_name> 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 <customer_short_name> DPI Teleconnect and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> DPI Teleconnect in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> DPI Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> DPI Teleconnect the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> CCI any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>CCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>CCI, BellSouth shall provide <customer_short_name> CCI with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> CCI data to the LIDB shall be solely at the direction of <customer_short_name>CCI. Such direction from <customer_short_name> 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 <customer_short_name> CCI data upon <customer_short_name>CCI’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 <customer_short_name> CCI customer records will be missing from LIDB, as measured by <customer_short_name> CCI audits. BellSouth will audit <customer_short_name> CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> CCI within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>CCI, 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 <customer_short_name> 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 <customer_short_name>CCI’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 <customer_short_name> 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 <customer_short_name> CCI and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> CCI in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> CCI the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> CCI under the BFR/NBR Process as set forth in Attachment 11.
7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> 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 BellSouth will offer to <customer_short_name> ITC/\DeltaCom 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 <customer_short_name>’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 <customer_short_name> ITC/\DeltaCom 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 <customer_short_name>ITC/\DeltaCom, BellSouth shall provide <customer_short_name> ITC/\DeltaCom with a list of the customer data items, items which <customer_short_name> 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 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 <customer_short_name> ITC/\DeltaCom data to the LIDB shall be solely at the direction of <customer_short_name>ITC/\DeltaCom. Such direction from <customer_short_name> 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 13.4.2.7 BellSouth shall provide priority updates to LIDB for <customer_short_name> ITC/\DeltaCom data upon <customer_short_name>’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 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> ITC/\DeltaCom customer records will be missing from LIDB, as measured by <customer_short_name> ITC/\DeltaCom audits. BellSouth will audit <customer_short_name> ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>ITC/\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 <customer_short_name> ITC/\DeltaCom 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 <customer_short_name>’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 13.4.2.10 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom and BellSouth.
7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom in writing.
7.3.2.13 13.4.2.12 BellSouth shall provide <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> ITC/\DeltaCom the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> ITC/\DeltaCom 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 <customer_short_name> ITC/\DeltaCom 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
Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to <customer_short_name> 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 <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 <customer_short_name> 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 <customer_short_name>Grande, BellSouth shall provide <customer_short_name> Grande with a list of the customer data items, which <customer_short_name> 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 <customer_short_name> Grande data to the LIDB shall be solely at the direction of <customer_short_name>Grande. Such direction from <customer_short_name> 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 <customer_short_name> Grande data upon <customer_short_name>Grande’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 <customer_short_name> Grande customer records will be missing from LIDB, as measured by <customer_short_name> Grande audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit <customer_short_name> Grande records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Grande contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to <customer_short_name> Grande within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>Grande, 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 <customer_short_name> 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 <customer_short_name>Grande’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 <customer_short_name> 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 <customer_short_name> Grande and BellSouth.
7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Grande in writing.
7.3.2.13 9.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Grande at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Grande the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement.
7.3.2.2 BellSouth shall process <customer_short_name>Level 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> 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 <customer_short_name>▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ shall provide <customer_short_name> Level 3 with a list of the customer data items, which <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 <customer_short_name> Level 3 data to the LIDB shall be solely at the direction of <customer_short_name>Level 3. Such direction from <customer_short_name> 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 <customer_short_name> data upon <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 <customer_short_name> Level 3 customer records will be missing from LIDB, as measured by <customer_short_name> Level 3 audits. BellSouth will audit <customer_short_name> Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> Level 3 within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>▇▇▇▇▇ ▇, 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 <customer_short_name> 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 <customer_short_name>Level 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 <customer_short_name> 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 <customer_short_name> Level 3 and BellSouth.
7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> 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 <customer_short_name> Level 3 in writing.
7.3.2.13 BellSouth shall provide <customer_short_name> 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 <customer_short_name> Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> Level 3 the screening information associated with LIDB Data Screening of <customer_short_name> 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 <customer_short_name> 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 <customer_short_name> 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