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: Techniques for generating and executing a performance-aware enterprise component (PAEC) are provided.

Abstract: Process Brokering Services (PBS) are implemented though the concept of Adaptive Documents to facilitate electronic commerce (e-commerce). PBS provides a single point of process control over the various fragmented execution flows and brings together the elements for process integration (views, content, flows) in a unified, scalable architecture on an industry standard platform. The two principal functions of the PBS are brokering of multiple business processes encapsulated in various back-end systems including workflow engines and business applications, and aggregating content from multiple enterprise information systems in the business context and managing the shared access to this based on the roles of the participants. The dynamic services provided by PBS are accessible to clients through the PBS Interface.

Abstract: A method for configuring a software package for an enterprise includes gathering desired To-be configuration requirements for a software package through at least one questionnaire; gathering current As-Is raw data for the enterprise; displaying the To-Be configuration requirements and As-Is raw data; comparing the To-Be configuration requirements and As-Is raw data; selecting final To-Be configuration requirements; and generating and executing configuration code for the software package to pre-configure the software package with the final To-Be configuration requirements.

Abstract: A method (and system) of monitoring business performance using a monitoring artifact includes processing an incoming event using the monitoring artifact.

Abstract: A mechanism is provided for forming a business entity model. A selection of business components is received from a business function model to be selected business components. Activities are found in an industry reference model to be selected activities corresponding to selected business components. Based on the selected activities, industry reference model is scoped to be a scoped industry reference model, which includes reducing business process models in the industry reference model to selected business process models corresponding to selected activities, reducing data models in the industry reference model to selected data models corresponding to use cases of selected activities, and reducing service operations in the industry reference model to selected service operations corresponding to the selected activities. Selected activities and scoped industry reference model are customized.

Abstract: Techniques for generating and executing a performance-aware enterprise component (PAEC) are provided.

Abstract: A system for analyzing a business process integration and management (BPIM) solution includes an assembler which assembles a plurality of solution artifacts to form a platform independent solution template, a simulator which simulates an execution of a BPIM solution based on the platform independent solution template, and an analyzer for analyzing a performance of the BPIM solution.

Abstract: Techniques for modeling a composite application are provided. The techniques include identifying one or more entities that are processed in a user enterprise, identifying one or more actions to be performed during a lifecycle of the one or more entities, and modeling a composite application based on the one or more actions to be performed during a lifecycle of the one or more entities.

Abstract: A software architecture can include an artifact layer and a configuration layer. The artifact layer can contain multiple application independent artifacts. A configuration layer can contain at least one application. The application can include multiple states in which the application executes instructions. The states can exist within execution spaces that are distributed across a network. The application uses artifacts of the artifact layer, which can operate in a state dependent manner.

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: 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 for configuring a software package for an enterprise includes gathering desired To-be configuration requirements for a software package through at least one questionnaire; gathering current As-is raw data for the enterprise; displaying the To-Be configuration requirements and As-is raw data; comparing the To-Be configuration requirements and As-is raw data; selecting final To-Be configuration requirements; and generating and executing configuration code for the software package to pre-configure the software package with the final To-Be configuration requirements.

Abstract: A wireless key is signal, having a key-specific identifier, is received, the key-specific identifier detected, and the signal transmission location is calculated. The signal transmission location is stored based on the detected key-specific identifier. Another instance of the same wireless key signal is received, its key-specific identifier is detected, and the stored signal transmission location is retrieved based on the detected key-specific identifier. Optionally, a wireless key signal is received at a user and repeated at a plurality of locations in a parking facility. A vehicle response is detected, and associated with one of the repeatings of the wireless key signal. A location of the vehicle response is detected based on the repeating with which it is associated.

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: Process Brokering Services (PBS) are implemented though the concept of Adaptive Documents to facilitate electronic commerce (e-commerce). PBS provides a single point of process control over the various fragmented execution flows and brings together the elements for process integration (views, content, flows) in a unified, scalable architecture on an industry standard platform. The two principal functions of the PBS are brokering of multiple business processes encapsulated in various back-end systems including workflow engines and business applications, and aggregating content from multiple enterprise information systems in the business context and managing the shared access to this based on the roles of the participants. The dynamic services provided by PBS are accessible to clients through the PBS Interface.

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: 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: A method (and system) of monitoring business performance using a monitoring artifact includes processing an incoming event using the monitoring artifact

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.