Abstract: A service engagement map may be generated based on data collected associated with the service transition and delivery processes. The service engagement map may be refined iteratively by discovering additional data associated with the service transition and delivery processes and updating the service engagement map according to the additional data. Engagement metrics may be computed based on the service engagement map and presented. The service engagement map may also be presented visually.

Abstract: Assignment scheduling for service projects, in one aspect, may comprise preparing input parameter data for servicing a client service request; generating a schedule for servicing the client service request by executing an optimization algorithm with the input parameter data; determining whether the schedule is acceptable by the client; and repeating automatically the preparing, the generating, the transmitting and the determining until it is determined that the schedule is acceptable by the client, wherein each iteration automatically prepares different input parameter data for inputting to the optimization algorithm and generates a different schedule based on the different input parameter data.

Abstract: Assignment scheduling for service projects, in one aspect, may comprise preparing input parameter data for servicing a client service request; generating a schedule for servicing the client service request by executing an optimization algorithm with the input parameter data; determining whether the schedule is acceptable by the client; and repeating automatically the preparing, the generating, the transmitting and the determining until it is determined that the schedule is acceptable by the client, wherein each iteration automatically prepares different input parameter data for inputting to the optimization algorithm and generates a different schedule based on the different input parameter data.

Abstract: Techniques are disclosed for capturing and visualizing data lineage in content management systems. For example, a method comprises the following steps. A plurality of data sets is received. Each of the data sets is associated with a party and comprises a plurality of information. A set of lineage data about one or more of the data sets is received. The lineage data comprises information about the history of a particular data set. A user interface is presented that conveys a representation of one or more of the plurality of received data sets and at least a portion of the lineage data about the history of one or more of the data sets. A command is received at the user interface to merge or unmerge two data sets in the plurality of data sets. Two or more data sets in the plurality of data sets are merged or unmerged based on the received command.

Abstract: A service engagement map may be generated based on data collected associated with the service transition and delivery processes. The service engagement map may be refined iteratively by discovering additional data associated with the service transition and delivery processes and updating the service engagement map according to the additional data. Engagement metrics may be computed based on the service engagement map and presented. The service engagement map may also be presented visually.

Abstract: Techniques are disclosed for extracting information through analysis of provenance data. For example, a computer-implemented method of extracting information regarding an execution of an enterprise process comprises the following steps. Provenance data is generated, wherein the provenance data is based on collected data associated with an actual end-to-end execution of the enterprise process and is indicative of a lineage of one or more data items. A provenance graph is generated that provides a visual representation of the generated provenance data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. At least a portion of the generated provenance data from the graph is analyzed so as to extract information about the execution of the enterprise process based on the analysis.

Abstract: Assignment scheduling for service projects, in one aspect, may comprise preparing input parameter data for servicing a client service request; generating a schedule for servicing the client service request by executing an optimization algorithm with the input parameter data; determining whether the schedule is acceptable by the client; and repeating automatically the preparing, the generating, the transmitting and the determining until it is determined that the schedule is acceptable by the client, wherein each iteration automatically prepares different input parameter data for inputting to the optimization algorithm and generates a different schedule based on the different input parameter data.

Abstract: Assignment scheduling for service projects, in one aspect, may comprise preparing input parameter data for servicing a client service request; generating a schedule for servicing the client service request by executing an optimization algorithm with the input parameter data; determining whether the schedule is acceptable by the client; and repeating automatically the preparing, the generating, the transmitting and the determining until it is determined that the schedule is acceptable by the client, wherein each iteration automatically prepares different input parameter data for inputting to the optimization algorithm and generates a different schedule based on the different input parameter data.

Abstract: The present invention relates to a Workflow Management System or a computer system with comparable functionality (WFMS). More particularly the invention relates to a method or means for generating a runtime compliant partner process for a given original process, wherein both processes are dedicated to interact with each other. In order to provide a method for generating a runtime compliant partner process for a given original process, which is easier understandable for a process developer, it is proposed to perform the steps of: Step 1: Identifying all activities of the original process interacting with the partner process, Step 2: Determining if an activity is able to be mirrored by a mechanism supported by the business process language, e.g. BPEL, Step 2.1: If yes, generating the mirrored activity and creating a respective activity name, Step 2.1: If not, using a predetermined mathematical method for dissecting such an activity that into a set of sub-activities, which can be mirrored, Step 2.2.

Abstract: A computer implemented method, apparatus, and computer usable program product for processing application code. In one embodiment, a call is received to invoke a set of methods of annotated application code. The annotated application code includes a set of annotations specifying a selection of the set of methods. A selected method from the set of methods is invoked in response to determining that the call is valid according to the set of annotations. Thereafter, a subsequent set of valid methods for execution is identified based upon an annotation associated with the selected method.

Abstract: An embodiment of the invention provides a method for service management, wherein resources that have performed tasks in at least two of a first category, a second category, and at least one additional category are identified. A plurality of correlation sums are determined where the correlation sum includes at least two categories, wherein the correlation sums are added together to produce a correlation value. A correlation product for each correlation sum is calculated based on the respective correlation sum and the number of resources that have performed tasks with respect to the correlation sum. A quotient is calculated for each correlation sum based on the respective correlation product and the correlation value. The categories are grouped into clusters with a clustering module based on the quotients; and, resources are associated with the clusters based on task performance history of the resources.

Abstract: An embodiment of the invention provides a method for service management, wherein resources that have performed tasks in at least two of a first category, a second category, and at least one additional category are identified. A plurality of correlation sums are determined where the correlation sum includes at least two categories, wherein the correlation sums are added together to produce a correlation value. A correlation product for each correlation sum is calculated based on the respective correlation sum and the number of resources that have performed tasks with respect to the correlation sum. A quotient is calculated for each correlation sum based on the respective correlation product and the correlation value. The categories are grouped into clusters with a clustering module based on the quotients; and, resources are associated with the clusters based on task performance history of the resources.

Abstract: Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process.

Abstract: A method, system and computer program product for determining health of a case. The method includes the steps of: obtaining at least one correlated trace from (i) task descriptions or (ii) data related to the task descriptions or a process instance; calculating at least one current metric using (i) the task descriptions, (ii) the data, (iii) the correlated trace or (iv) a first model; calculating at least one prognostic metric using a second model; and creating at least one combination metric from the current metric and the prognostic metric; where at least one of the steps is carried out using a computer device.

Abstract: A state machine program is generated from a state machine. The state machine has states, transitions and events. A basic structure for the state machine program is generated. The basic structure has therein a structure that operates in non-final states. A statement is generated within the structure for detecting an event. A statement is generated within the structure for evaluating the detected event based on a current state to identify if the current state is valid for the detected event. A statement is generated within the structure for determining a next state if the current state is valid. A statement is generated within the structure for transitioning the current state to the next state.

Abstract: Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process.

Abstract: Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process.

Abstract: Techniques are disclosed for capturing and visualizing data lineage in content management systems. For example, a method comprises the following steps. A plurality of data sets is received. Each of the data sets is associated with a party and comprises a plurality of information. A set of lineage data about one or more of the data sets is received. The lineage data comprises information about the history of a particular data set. A user interface is presented that conveys a representation of one or more of the plurality of received data sets and at least a portion of the lineage data about the history of one or more of the data sets. A command is received at the user interface to merge or unmerge two data sets in the plurality of data sets. Two or more data sets in the plurality of data sets are merged or unmerged based on the received command.

Abstract: Techniques are disclosed for influencing behavior of enterprise operations during process enactment using provenance data. For example, a computer-implemented method of influencing a behavior of an enterprise process comprises the following steps. Provenance data is generated, wherein the provenance data is based on collected data associated with at least a partial actual execution of the enterprise process and is indicative of a lineage of one or more data items. A provenance graph is generated that provides a visual representation of the generated provenance data, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. At least a portion of the generated provenance data from the graph is analyzed to generate an execution pattern corresponding to the at least partial actual execution of the enterprise process. The execution pattern is compared to one or more previously stored patterns.

Abstract: Techniques are disclosed for capturing, storing, querying and analyzing provenance data for automatic discovery of enterprise process information. For example, a computer-implemented method for managing a process associated with an enterprise comprises the following steps. Data associated with an actual end-to-end execution of an enterprise process is collected. Provenance data is generated based on at least a portion of the collected data, wherein the provenance data is indicative of a lineage of one or more data items. A provenance graph that provides a visual representation of the generated provenance data is generated, wherein nodes of the graph represent records associated with the collected data and edges of the graph represent relations between the records. The generated provenance graph is stored in a repository for use in analyzing the enterprise process.