Abstract: The present invention provides a system and a method for delivering an event from an event publisher to an event subscriber via an event broker. The event broker performs several functions such as receiving an event published by an event publisher of a first domain, assigning a priority based on a second domain to a plurality of subscribers of the second domain, processing the event based on a rule and the priority, and further delivering the event published by the event publisher of the first domain to the plurality of event subscribers of the second domain in accordance with the priority.

Abstract: An arrangement collects data from disparate system back-end sources, such as a contracts system, a billing system, a service provisioning system, and analyzes the data to determine whether any inconsistencies exist. If so, the system issues a modification request to compensate for the inconsistency.

Abstract: A method and apparatus includes automatically correlating indicators already generated by network components to detect and isolate failures that are caused by or related to network components operating on different layers of the open system interconnect (OSI) model. Failure indicators that persist for longer than a specified time window are automatically detected and correlated with one another based on a topology table. The method uses indicators already generated by the network components, obviating the need for software that typically resides on and consumes valuable processing time of network components.

Abstract: The present invention provides a system and a method for delivering an event from an event publisher to an event subscriber via an event broker. The event broker is a web server infrastructure which performs several functions such as receiving the published event on a server, authenticating the publisher with the published event, validating the event with XML schema definition, processing the event based on a set of predefined rules and further delivering the processed event to an authorized event subscriber.

Abstract: A method includes receiving a problem ticket, which contains a priority level indicator and a customer identifier, that describes a telecommunications network event such as a problem. The problem ticket is associated with and transmitted to a workcenter and a portion within the workcenter based on at least anyone of the priority level indicator and the customer identifier. Other personnel are notified about the problem ticket based on the priority level indicator and the customer identifier.

Abstract: A computer system and techniques are disclosed that provide support for the operations of a modern telecommunication services provider. The computer system includes several software modules arranged in layers that are configured to provide services, such as a data access, workflow, and business-management functions. In some preferred embodiments, data cleansing and enterprise-view functionality are provided. An application program interface is also provided that allows a software program to execute software modules contained in the layers to perform specific tasks.

Abstract: Predictive maintenance in a communications environment can be triggered when an anomaly in the call set-up process is detected. In one arrangement, in a VoIP context, the post dial delay (PDD) associated with call set up is monitored. If a link or node has an abnormally high contribution to the PDD it may be designated for predictive maintenance.

Abstract: A method, system, and article of manufacture for cleansing an enterprise database extracts data from an enterprise database, extracts reference data from a most-trusted database, determines discords between the data extracted from the enterprise database and the reference data extracted from the most-trusted database in accordance with a set of business rules, modifies the data extracted from the enterprise database based on the discords, and stores the modified data in the enterprise database. The data may be modified automatically with or without manual intervention. Discords are preferably determined on an atomic level.

Abstract: In accordance with a method of managing work flow, tasks associated with a telecommunications service order from a plurality of worklists of computing source systems are merged into a merged worklist. Each computing source system maintains a respective worklist that includes a task associated with the service order. The tasks of the service order in the merged worklist are prioritized into a prioritized sequence to be completed on a work-when-ready basis. An error in completion of a task associated with a worklist of a source system is detected and a new task to correct the detected error is generated. Further, the worklist of the source system associated with the detected error is updated with the new task and the new task is integrated into a proper position of the prioritized sequence in the merged worklist in accordance with the work-when-ready basis.

Abstract: Computer systems and techniques for predicting a cable failure in a network system begin by receiving a remote alarm indicator followed by a remote alarm indicator clear as a transmission alarm indicator of an intermittent short duration failure on the transmission path of a circuit. If the transmission alarm indicator is of a duration less than or equal to a preset threshold D it is considered an acceptable short hit transmission alarm. When at least N acceptable transmission alarms have been received and the time stamps of the last N acceptable transmission alarms have been recorded, then a determination is made as to whether N acceptable transmission alarms have been received within a preset time period. A moving window time period is calculated as the difference between the time stamp of the present acceptable transmission alarm K and the time stamp of the [(K?N)+1] acceptable transmission alarm. If the difference is less than or equal to T, a cable error signature is indicated.

Abstract: Systems and methods for predicting one or more service problems in a communication network are described. In one implementation, a threshold is set and signal data are collected at an interface component. The collected data are compared to the threshold, and depending on the comparison between the collected data and the threshold, a trend analysis is performed on the collected data.

Abstract: A business process automation system architecture is used to isolate problems in a virtual private network access network. Codified rules and a rules based program are used to determine all equipment from a customer premises equipment to a VPN core access point equipment on a VPN access path and that is associated with a failure. The codified rules also govern the gathering of information on the equipment including determining whether the equipment supports automated diagnostics and the communication protocols used. Extended PING testing is done on the equipment and a status of the extended PING test, link status, line protocol status, and existing loop status is determined. Further testing is automatically run based on the codified rules and the status. The failure is then isolated to the CPE, a local exchange carrier, or a network provider.

Abstract: A method includes issuing a retrieval instruction, such as a database query, to retrieve from a database system a datum associated with a network circuit. Upon receiving the datum from the database system, it is determined, based on the datum received, whether the network circuit is stranded or whether the network circuit is incurring a charge but is not generating sufficient revenue. When the network circuit is stranded, a disconnect instruction to disconnect the network circuit is issued. When the network circuit is incurring a charge but the amount of revenue generated by the network circuit is below a predetermined threshold, a termination instruction to terminate a service associated with the network circuit is issued.

Abstract: A method for identifying high-risk orders associated with a customer that includes the steps of: receiving an order that includes a customer number, an order type and a plurality of entries; identifying a customer contract based on the order type and the customer number, the customer contract having a plurality of terms that correspond to the entries; comparing the entries to corresponding terms using rules; and identifying a high-risk order containing at least one error from the comparison. The method can also include assigning a result code or a result text to the order, which corresponds to the errors that are identified, and changing the rule set by adding or removing rules.

Abstract: An arrangement analyzes a plurality of call detail records and determines that a particular call processing code has occurred a predetermined number of times during a previously defined time interval. The fact of these multiple occurrences of these processing codes is determined to be an indication of a trunk failure. A maintenance request is issued to address the detected failure.

Abstract: A method of modifying a network service comprising, identifying a service to be modified, determining services affected by the identified service; and performing a modification of the service level of at least the identified service, wherein the modification of the service level comprises a logical interruption of at least the identified service.

Abstract: A method includes retrieving a first data set from a billing system configured to facilitate a billing operation associated with a network. The first data set includes a plurality of billing records, which includes a first billing record associated with and including a field identifying a first circuit from a plurality of circuits included within the network. A second data set is retrieved from a configuration management system configured to facilitate an operation associated with the network. The second data set includes a plurality of configuration records, which includes a first configuration record associated with and including a field identifying the first circuit. When the field identifying the first circuit included in the first configuration record differs from the field identifying the first circuit included in the first billing record, a correct identifier associated with the first circuit is determined. When such a discrepancy exists, a report is produced.

Abstract: In accordance with a method of managing work flow, tasks associated with a telecommunications service order from a plurality of worklists of computing source systems are merged into a merged worklist. Each computing source system maintains a respective worklist that includes a task associated with the service order. The tasks of the service order in the merged worklist are prioritized into a prioritized sequence to be completed on a work-when-ready basis. An error in completion of a task associated with a worklist of a source system is detected and a new task to correct the detected error is generated. Further, the worklist of the source system associated with the detected error is updated with the new task and the new task is integrated into a proper position of the prioritized sequence in the merged worklist in accordance with the work-when-ready basis.

Abstract: A method includes retrieving a first data set from a switch within a network, the first data set including a set of switch records. Among the switch records included in the first data set is a first switch record associated with and including a field identifying a first trunk group from a set of trunk groups included within the switch. A second data set is retrieved from a configuration management system configured to facilitate an operation associated with the network. The second data set includes a plurality of configuration records, which includes a first configuration record associated with and including a field identifying the first trunk group. When the field included in the first configuration record differs from the field included in the first switch record a report is produced.

Abstract: A method and system of managing work flow in provisioning service orders is provided, particularly telecommunications service delivery orders, where each service order may include of tasks from different worklists from different sources. The method includes merging the worklists and prioritizing tasks in accordance with work-when-ready work flow. The merged worklist provides an end-to-end view on a graphical user interface of all tasks pending to provision each service order. A change of status of a task results in automatically updating both the native and merged worklists. When a task is completed on the native system, the task is automatically deleted from both worklists. Selected search criteria and sorting fields may be used to narrow the displayed results. New tasks created by exceptions are inserted appropriately into the active worklist. The method eliminates the need for a user to log onto different systems to manually prioritize tasks.