Abstract: An exemplary method, for solving a problem with a network element within a network, includes first selecting a first set of pre-existing bots and first executing at least some of the selected first set of bots to change the network element and/or the network to solve the problem. The method further includes conducting a root cause analysis to generate recommendation(s) to correct the problem and in response to the first executing failing to solve the problem: second selecting, based on the recommendation(s), a second set of pre-existing bots to change the network element and/or the network to solve the problem, and second executing at least some of the selected second set of bots to solve the problem. Subsequently, the method includes generating, in response to the second executing failing to solve the problem, instructions to manually change the network element and/or the network to solve the problem.

Abstract: A method is provided in an example embodiment and may include receiving information identifying an anomaly or a predicted outage of a component of a system and requesting a data service for buffered data generated by the component within a timeframe of receiving the information. The method further may include normalizing the buffered data into discrete time units into corresponding distinct units of time and analyzing the buffered data using a machine learning (ML) model to identify a root cause of the anomaly or the predicted outage. The method further may include identifying at least one solution to the identified root cause based on characteristics associated with the root cause of the anomaly or the predicted outage and providing the at least one solution to an automation component to avoid onset of an event that triggers outage of the component or the system.

Abstract: An exemplary method, for preventing an outage in a network, includes collecting network metrics and producing statistical features of the network during a predetermined time window based on statistical analysis of the collected metrics. The method further includes selecting, from the produced statistical features, a first data set of relevant statistical features. Further, the method includes collecting information about a past event, extracting event data from the past event, and vectorizing the extracted event data to form a second data set. The method further includes concatenating the first data set and the second data set to form a third data set and classifying the third data set relative to a model of historical network performance to determine a probability of the outage. Further, the method includes modifying, in response to the probability being above a threshold, the network/activity within the network to avoid onset of the outage.

Abstract: Various embodiments of the present disclosure can include systems, methods, and non-transitory computer readable media configured to aggregate a plurality of threat signatures from a plurality of threat signature data sources. The bit stream data is analyzed, based on the plurality of threat signatures, to detect a first threat in the bit stream data. A result of analyzing the bit stream data is logged as threat analysis log data. The threat analysis log data is analyzed to detect a second threat in the bit stream data. The threat analysis log data may be analyzed based on a heuristic. An action is triggered based on analysis of the bit stream data, or based on heuristic analysis of the threat analysis log data.

Abstract: Methods, mediums, and systems are described for providing a platform coupled to one or more rules engines. The platform may provide runtime rule services to one or more applications. Different rules engines may be used for different types of rules, such as calculations, decisions, process control, transformation, and validation. Rules engines can be added, removed, and reassigned to the platform. When the platform receives a request for services from an application, the platform selects one of the rules engines to handle the request and instructs the selected rules engine to execute the rule. The rules engine may be selected automatically. The platform may be implemented through a service-oriented architecture.

Abstract: Methods, mediums, and systems are described for providing a platform coupled to one or more rules engines. The platform may provide runtime rule services to one or more applications. Different rules engines may be used for different types of rules, such as calculations, decisions, process control, transformation, and validation. Rules engines can be added, removed, and reassigned to the platform. When the platform receives a request for services from an application, the platform selects one of the rules engines to handle the request and instructs the selected rules engine to execute the rule. The rules engine may be selected automatically. The platform may be implemented through a service-oriented architecture.

Abstract: A method includes generating, using a three-dimensional model file corresponding to a facility location, a graphical user interface depicting a virtual representation of the facility location from a first point of view, one or more of a plurality of assets located at the facility location being visible from the first point of view. The method further includes receiving navigation instructions indicating a desire of a user to move within the virtual representation to a second point of view, and updating the graphical user interface to depict a virtual representation of the facility location from the second point of view, a particular asset being visible from the second point of view. The method further includes receiving a user selection of the particular asset, accessing asset information associated with the particular asset, and displaying at least a portion of the accessed asset information.

Abstract: Provided is a method that includes receiving a redirect request from one or more switches of a telecommunications network, receiving, from one or more switches of the telecommunications network, a connect request that requests connection of a transmitter device to a receiver device associated with the normal subscriber number, and configuring the telecommunication network to connect the transmitter device to a receiver device associated with the modified subscriber number, independently of the switch serving the normal receiver device being operable or inoperable. The redirect request comprises a normal subscriber number and a modified subscriber number.

Abstract: Methods and systems for providing vehicle accident information to a computer system are provided. In one embodiment, an impact point of a vehicle accident may be provided to the computer system via a graphical user interface. The computer system may include a memory. The memory may have sets of characteristics regarding one or more past or theoretical accidents. In an embodiment, at least one characteristic in the sets of characteristics may be an impact point. The computer system may display one or more of the impact points in the memory as a graphical image on the graphical user interface. A user may select an impact point of the vehicle accident from the graphical user interface.

Abstract: In some embodiments, a mobile device comprises a network interface, a memory, and a processor. The network interface is operable to transmit communications between the mobile device and a patient data repository, the patient data repository storing information associated with a plurality of patients. The memory is operable to receive, from the patient data repository through the network interface, and store information associated with one or more patients. The processor is configured to receive a selection of a patient from a user; identify information associated with the selected patient stored in the memory; and provide, to an application local to the mobile device, the information associated with the selected patient from the memory.

Abstract: An update system configured to provide software updates, software patches and/or other data packets to one or more computer systems via a network is disclosed. The update system may interact with a network management system, such as an enterprise management system, to distribute data packets and gather configuration information. The update system may generate and send commands to the network management system. The network management system may carry out the commands to distribute data packets and/or gather configuration information.

Abstract: Precedent claims that match a pending claim are identified. A general damages amount is determined based on the likelihood value for at least one of the matching precedent claims. A general damages amount is derived from the likelihood value for at least one of the matching precedent claims. Pending claim adjustments are calculated based on amounts associated with the pending claim. Pending claim adjustments are applied to the general damages amount to determine a recommended settlement amount.

Abstract: Methods and systems are provided for determining and displaying amounts for use in settling insurance claims are disclosed. Closed claims that match an open claim are identified based on one or more characteristics of the open claim. A likelihood value associated with at least one of the matching closed claims is determined. An amount for use by an adjuster in settling the open claim is determined based on the likelihood value for at least one of the matching claims. A most likely amount and most likely range associated with the open claim may be determined based on the likelihood values.

Abstract: Methods and systems are provided for estimating liability in an accident. In an embodiment, the liability estimate may include a base liability and one or more adjustments due to various factors. The base liability may be determined from characteristics including: the configuration of the roadway, the type of accident, right of way, and impact points of each vehicle. The adjustments due to various factors may be determined from conditions of vehicles in the accident, conditions of drivers in the accident, actions of drivers in the accident, and/or environmental conditions in the accident. In one embodiment, a base liability adjusted due to the various factors may exceed a predefined upper or lower bound of liability. In such a case, an absolute liability value may be assigned as the liability estimate.

Abstract: Methods and systems are provided for processing claims. A claim management case is created for an insured in response to a notice of a claim. One or more insurance policies covering the insured are associated with the claim management case. In some embodiments, all of the insurance policies covering the insured are associated with the claim management case. At least one process relating to the claim management case is performed at a claim management case level. The process performed at the claim management case level applies to at least one of the insurance policies associated with the claim management case. The processes performed at the claim management case level may apply to all the insurance policies associated with the claim management case. One or more processes relating to the claim management case are performed at a policy level.

Abstract: Methods and systems are provided for processing claims. A claim management case is created for an insured in response to a notice of a claim. One or more insurance policies covering the insured are associated with the claim management case. At least one process is performed at a claim management case level to fulfill an information requirement that applies to at least two of the insurance policies associated with the claim management case. Claims are adjudicated under the one or more of the insurance policies covering the insured.

Abstract: Methods and systems are provided for processing claims. A hierarchy may be created for claims specific to the insured that includes a claim management case level, a policy level, and a coverage level. The claim management case level may include a claim management case node. The policy level may include one or more policy nodes. Each of the policy nodes may relate to an insurance policy covering the insured. The one or more insurance policies covering the insured are associated with the claim management case. The coverage level may include one or more coverage nodes. Each of the coverage nodes may relate to an insurance coverage covering the insured. Each of the insurance coverages may be associated with one of the insurance policies.

Abstract: Methods and systems are provided for analyzing and assessing documents using a writing profile for documents, such as a payment instrument. A method may include providing a document to a computer system. In an embodiment, the method may further include comparing writing in one or more non-signature information fields of the document to at least one forger writing profile representation. In some embodiments, at least one forger writing profile representation may be obtained from at least one non-signature information field of at least one document that includes forged information. In an embodiment, the document may be identified as a document including forged information from an approximate match of at least one forger writing profile representation with writing in the document.

Abstract: Methods and systems are provided for processing claims. A hierarchy is created including a claim management case level and a policy level. The claim management case level includes a claim management case node. The claim management case node relates to a designee under a first insurance policy. The policy level includes one or more policy nodes. Each of the policy nodes is associated with an insurance policy relating to the designee. At least one process for the claim management case is performed at the claim management case level. The process applies to at least one insurance policy relating to the designee.

Abstract: Methods and systems are provided for adjusting estimates of liability associated with past or theoretical accidents. In an embodiment, the characteristics from an actual accident may be compared to those in a past or theoretical accident. Liability may be estimated from a preassigned liability associated with a nearest matching past or theoretical accident. In one embodiment, liability estimates associated with past or theoretical accidents or characteristics of past or theoretical accidents may be adjusted The characteristics may include: conditions of vehicles in the accident, conditions of drivers in the accident, actions of drivers in the accident, and/or environmental conditions in the accident.