Method and apparatus for product lifecycle management in a distributed environment enabled by dynamic business process composition and execution by rule inference

• US 20040162741A1
• Filed: 02/07/2003
• Published: 08/19/2004
• Est. Priority Date: 02/07/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Zeng, Liangzhao, Zhang, Liang-Jie, Lei, Hui, Chang, Henry, Jeng, Jun-Jang, Flaxer, David
• Application Number:
  US10/359,732
• Publication Number:
  US 20040162741A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/10 Office automation; Time management

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. For each business process there is a business flow manager that dynamically composes ad-hoc workflow prior to execution and dynamically modifies the ad-hoc workflow as the business process executes. The business flow manager uses backward-chain inferencing and then forward-chain inferencing to generate the ad-hoc workflows, based on user identification of a target task. The business flow manager is able to stop execution of the workflow and regenerate a workflow for remaining tasks in response to events received over the network from service providers, and is also able to detect conflicts in the workflows at composition time and at execution time.

Claims

1. A system for supporting Product Lifecycle Management, comprising:

a distributed service network topology;

a hierarchy of functional domains connected within said topology, each domain having a service ontology and one or more service composition schemas defined by said service ontology, each service composition schema modeling a business process in said domain;

wherein descriptions of services provided to each domain is published to a service repository by providers of said services, said descriptions conforming to at least one of said service composition schemas;

a business process proxy for each said service description, said proxy encapsulating internal processes of the provider of said services;

an event messaging protocol enabling service collaboration and ad-hoc workflow composition, each said business process being implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules; and

for each said business process a business flow manager enabling dynamic composition of said ad-hoc workflow prior to execution and dynamic modification of said ad-hoc workflow as said business process executes, said business flow manager using a business rule inferencing framework for generating said ad-hoc workflows, said framework being able to stop execution of said workflow and regenerate said workflow in response to events distributed over said network topology using said messaging protocol, said framework also being able to detect conflicts in said workflows at composition time and at execution time.

2. The system of claim 1, wherein each said business flow manager further comprises:

a workflow engine that dynamically creates workflow schemas through a combination of backward-chain inference and forward-chain inference;

a workflow execution framework using rule inference that supports ad-hoc workflow through iterative analysis during execution time;

a business process model that allows dynamic modifications of business processes both at composition time and execution time; and

a set of business rule templates for creating business rules modeling business logic.

3. The system of claim 2, wherein a plurality of workflow schemas are created conforming to the business rules, and the dynamic workflow engine further comprises:

means for selecting one schema from said plurality based on a quality of service metric; and

means for starting the selected workflow schema and for triggering rule inference upon receipt of events from service providers.

4. The system of claim 2, wherein the set of business rule templates comprises:

user authorization rules giving the service schema that end users are authorized to use;

schema management rules used to dynamically create workflow schemas;

service provider selection rules that establish criteria and analytic function used in evaluating service providers;

execution management rules to control the execution of tasks;

service coordination rules for specifying the temporal connection among tasks being executed; and

data source rules for specifying how tasks are to obtain data.

5. The system of claim 3, wherein said business process model allows a user to change the selected schema by adding or deleting tasks or by adding or deleting transitions, the system then automatically generates additional business rules representing the user changes.

6. The system of claim 5, wherein said user changes are responsive to a conflict among business rules which causes the selected workflow schema to fail.

7. The system of claim 3, wherein the selected workflow schema fails in response to a conflict among business rules, the system then automatically generates an alternative workflow schema and migrates the selected workflow schema to the alternative workflow schema.

8. The system of claim 1, wherein said distributed service network topology is implemented using XML documents transported across HTTP.

9. The system of claim 8, wherein said distributed service network is implemented as a virtual private web.

10. A method for supporting Product Lifecycle Management, comprising the steps of:

determining one or more service ontologies, each said ontology belonging to a functional domain, said functional domains being organized in a hierarchy and connected over a distributed service network topology;

defining one or more service composition schemas from each said service ontology, each service composition schema modeling a business process in said service ontology'"'"'s domain, wherein descriptions of services provided to each domain is published to a service repository by providers of said services, said descriptions conforming to at least one of said service composition schemas;

for each said service description, encapsulating in a business process proxy by said service provider of one or more internal processes of the service provider, said proxy providing public access to said internal processes;

using an event messaging protocol to enable service collaboration and ad-hoc workflow composition, each said business process being implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules;

using said service repository to identify service providers for said tasks; and

for each said business process, using a business flow manager to dynamically compose said ad-hoc workflow prior to execution and dynamically modify said ad-hoc workflow as said business process executes, said business flow manager using a business rule inferencing engine for generating said ad-hoc workflows, said framework being able to stop execution of said workflow and regenerate said workflow in response to events distributed over said network topology using said messaging protocol, said framework also being able to detect conflicts in said workflows at composition time and at execution time.

11. The method of claim 10, further comprising the steps of:

dynamically creating workflow schemas through a combination of backward-chain inference and forward-chain inference, and

iteratively analyzing workflow execution and regenerating said workflow schemas in response to said analysis,

wherein each said business flow manager further comprises;

a business process model that allows dynamic modifications of business processes both at composition time and execution time; and

a set of business rule templates for creating business rules modeling business logic.

12. The method of claim 11, wherein a plurality of workflow schemas are created conforming to the business rules, and further comprising the steps:

selecting one schema from said plurality based on a quality of service metric; and

starting the selected workflow schema and triggering rule inference upon receipt of events from service providers.

13. The method of claim 11, wherein the set of business rule templates comprises:

user authorization rules giving the service schema that end users are authorized to use;

schema management rules used to dynamically create workflow schemas;

service provider selection rules that establish criteria and analytic function used in evaluating service providers;

execution management rules to control the execution of tasks;

service coordination rules for specifying the temporal connection among tasks being executed; and

data source rules for specifying how tasks are to obtain data.

14. The method of claim 11, wherein said business process model allows a user to change the selected schema by adding or deleting tasks or by adding or deleting transitions, the business flow manager then automatically generating additional business rules representing the user changes.

15. The method of claim 14, wherein said user changes are responsive to a conflict among business rules which causes the selected workflow schema to fail.

16. The method of claim 12, wherein the selected workflow schema fails in response to a conflict among business rules, the business flow manager then automatically generating an alternative workflow schema and migrating the selected workflow schema to the alternative workflow schema.

17. The method of claim 10, wherein said distributed service network topology is implemented using XML documents transported across HTTP.

18. The method of claim 17, wherein said distributed service network is implemented as a virtual private web.

19. A computer readable medium containing code for supporting Product Lifecycle Management in a distributed environment, the code implementing the steps of:

determining one or more service ontologies, each said ontology belonging to a functional domain, said functional domains being organized in a hierarchy and connected over a distributed service network topology;

defining one or more service composition schemas from each said service ontology, each service composition schema modeling a business process in said service ontology'"'"'s domain, wherein descriptions of services provided to each domain is published to a service repository by providers of said services, said descriptions conforming to at least one of said service composition schemas;

for each said service description, encapsulating in a business process proxy by said service provider of one or more internal processes of the service provider, said proxy providing public access to said internal processes;

using an event messaging protocol to enable service collaboration and ad-hoc workflow composition, each said business process being implemented by an ad-hoc workflow comprised of one or more tasks connected by one or more business rules;

using said service repository to identify service providers for said tasks; and

for each said business process, using a business flow manager to dynamically compose said ad-hoc workflow prior to execution and dynamically modify said ad-hoc workflow as said business process executes, said business flow manager using a business rule inferencing engine for generating said ad-hoc workflows, said framework being able to stop execution of said workflow and regenerate said workflow in response to events distributed over said network topology using said messaging protocol, said framework also being able to detect conflicts in said workflows at composition time and at execution time.