Abstract: An architecture, system, and method are provided for a commitment loop solution for on demand business activity management. A Business Performance Management (BPM) loop is defined as a set of nodes each relating to different tasks for processing performance management trigger data generated by a business entity in real time, where the beginning or sensing element of the loop is triggered by a token (representing a business event from a business process) and the ending or executing element provides a business action to be implemented by the business entity. The token is passed from node to node sequentially in a particular order around the loop. Processing of the data represented by the token is governed by policies, which can be changed dynamically and follow a life cycle. On demand business activity management of larger aggregates of business entities (i.e.

Abstract: A model-driven approach is used in Business Solution Monitoring and Control environment. The solution is first described by the high level abstract Platform Independent Model (PIM), which is independent from platform and implementation technologies. This PIM is presented as a Directed Acyclic Graph (DAG) that is constructed by a series of models described in XML. Then the PIM is decomposed into several sub-processes that can be easily transformed into an executable representation, such as BPEL (Business Process Execution Language) or JAVA. BPEL is used as the example to show the model transformation.

Abstract: Meta-Rules are a special set of business rules whose purpose is to enable business rules selection and subsequent rule invocation by a business rules manager. Contained within a Meta-Rule are business policy and other information that enables the selection of a business rule used by a business application. Meta-rules allow the system to dynamically select and identify specific business rules to be executed within a given business application. By enabling a higher level of abstraction, and relying on rules to resolve specific business rule selection and invocations, Meta-rules further separate the binding of business knowledge and practice from application programming logic. The application programmer is freed from having specific knowledge of the business rule; all that is required is an assertion that a rule is to be used.

Abstract: A model-driven and QoS-aware infrastructure facilitates the scalable composition of Web services in highly dynamic environments. An exception management framework supports two modes of exception management for business processes, providing a novel policy-driven approach to exception management implemented in the system infrastructure. Exception management is implemented in the system infrastructure, with exception handling policies supplied by individual business processes. Using the exception management framework, developers define exception policies in a declarative manner. Before a business process is executed, the service composition middleware integrates the exception policies with normal business logic to generate a complete process schema. This policy driven-approach can significantly reduce the development time of business processes through its separation of the development of the business logic and the exception handling policies.

Abstract: Automomic business processes management solutions have capabilities to adapt themselves to changes in the business environment. These autonomic business solutions are built by wiring together autonomic solution components called BPbots (Business Process robots). BPbots are granular solution components representing an aspect of a business process. In general, BPbots consist of two parts, an execution module and a managerial module. The execution module represents the standard, non-autonomic solution component, such as a standard process flow model describing the long-running flow or business adapter describing the communication of the solution with service providers (such as applications). The managerial module is responsible for the autonomic behavior of the BPbot. The managerial component has the ability to monitor the execution module, analyze the performance, plan new, more appropriate execution patterns and change the behavior of the execution module according to the new plan.

Abstract: Query routing is based on identifying the preeminent search systems and data sources for each of a number of information domains. This involves assigning a weight to each search system or data source for each of the information domains. The greater the weight, the more preeminent a search system or data source is in a particular information domain. These weights Wi{1=0, 1,2, . . . N] are computed through a recursive learning process employing meta processing. The meta learning process involves simultaneous interrogation of multiple search systems to take advantage of the cross correlation between the search systems and data sources. In this way, assigning a weight to a search system takes into consideration results obtained about other search systems so that the assigned weights reflect the relative strengths of each of the systems or sources in a particular information domain. In the present process, a domain dataset used as an input to query generator.

Abstract: An enterprise system includes a plurality of artifacts (e.g., persons, objects, databases, autonomous elements, intelligent agents, information systems, etc), and a smart distance (e.g., a distance which may optimize the performance of the enterprise system) between the plurality of artifacts.

Abstract: A method, system, and computer program product for associating events. A provided event dataset includes events occurring in each of N successive time intervals (N?3). Association rules pertaining to successive events in the event dataset are deduced. Sequences of events are generated from the association rules. Clusters of the sequences of events are formed. Sequences of the clusters are created. The clusters of the sequences may be used: to identify at least one event occurring in a time interval of the N time intervals as being a probable cause of at least one event occurring in a later-occurring time interval of the N time intervals; or to predict an occurrence of at least one event in a time interval occurring after the N time intervals, wherein the at least one event had occurred within the N time intervals.

Abstract: Systems and methods for monitoring and controlling business level SLAs (Service level Agreements), and more particularly, systems and method for monitoring and controlling business level SLAs using probe points, KPIs (Key Performance Indicators) and business commitments. An XML (extensible Markup Language)-based specification referred to as BPCL (Business Process Commitment Language) is used to describe business commitments. BPCL specifications are used by a business process management (BPM) system to configure, monitor, and control business processes based on business commitments. Business Commitments and BPCL provide a path toward model-based management for dynamic e-business solutions.

Abstract: A method (and structure) to automate business decisions by computer, including capturing an event predetermined to be relevant to a defined set of business decisions by computer. The event is automatically processed by the computer to extract, transform and enrich relevant data for the business decisions. The extracted relevant data is forwarded, immediately upon processing the event, to one or more appropriate decision making modules in the computer.

Abstract: A system and method for supporting Product Lifecycle Management over a distributed service network topology that connects a hierarchy of functional domains, each domain having a service ontology and one or more service composition schemas defined by the service ontology. Each service composition schema models a business process in its domain. Descriptions of services provided to each domain are published to a service repository by providers of the services, in conformity with one of the service composition schemas. There is a business process proxy provided by the service provider for each service description, which encapsulates for public access the internal processes of the service provider. The invention makes use of an event messaging protocol that enables service collaboration and ad-hoc workflow composition. Each business process is implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules.

Abstract: Query routing is based on identifying the preeminent search systems and data sources for each of a number of information domains. This involves assigning a weight to each search system or data source for each of the information domains. The greater the weight, the more preeminent a search system or data source is in a particular information domain. These weights Wi{1=0, 1,2, . . . N] are computed through a recursive learning process employing meta processing. The meta learning process involves simultaneous interrogation of multiple search systems to take advantage of the cross correlation between the search systems and data sources. In this way, assigning a weight to a search system takes into consideration results obtained about other search systems so that the assigned weights reflect the relative strengths of each of the systems or sources in a particular information domain. In the present process, a domain dataset used as an input to query generator.

Abstract: A system and method for providing specified electronic commerce services to users, in particular e-Logistics services, services which are available in the marketplace from a variety of service providers whose electronic commerce systems are incompatible. There is provided a user/customer interface to the specified electronic commerce services, called a Common Alliance Interface, and a distinct interface for service providers of the specified electronic commerce services. Between the two interfaces is a business process layer which integrates one or more components of the specified electronic commerce services, these integrated components thereby being transparent to users. The service provider obtains access to users of the Common Alliance Interface by updating entries in a UDDI registry. There is further provided a service template which the service provider can modify to provide an adaptation layer between their legacy application and the business process layer.