CROSS DOMAIN INTEGRATION IN PRODUCT LIFECYCLE MANAGEMENT

• US 20140288994A1
• Filed: 03/19/2013
• Published: 09/25/2014
• Est. Priority Date: 03/19/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Derebail, Annap, Rajasekharan, Amaresh, Singh, Man Mohan
• Granted Patent: US 10,346,777 B2
• Time in Patent Office: Days
• US Class Current: 705/7.26
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals

Abstract

Cross-domain integration within product lifecycle management can include providing a plurality of finite state machines (FSMs), wherein each FSM is associated with one business object of an integration flow between a first enterprise information system and a second enterprise information system. Each FSM defines a plurality of lifecycle states of the associated business object. A business rule can be associated with each lifecycle state of each FSM. For each FSM, the associated business rules are independent of the FSM. For a selected lifecycle state of each FSM, the associated business rule defines a condition causing a transition from the selected lifecycle state to a next lifecycle state of the FSM. A network of the plurality of FSMs is established by providing communication links among individual ones of the plurality of FSMs according to the business rules. The communication links define the integration flow.

Claims

1-8. -8. (canceled)

9. A system comprising:

a processor programmed to initiate executable operations comprising;

providing a plurality of finite state machines, wherein each finite state machine is associated with one business object of an integration flow between a first enterprise information system and a second enterprise information system, and wherein each finite state machine defines a plurality of lifecycle states of the associated business object;

associating a business rule with each lifecycle state of each finite state machine, wherein for each finite state machine, the associated business rules are independent of the finite state machine, and wherein for a selected lifecycle state of each finite state machine, the associated business rule defines a condition causing a transition from the selected lifecycle state to a next lifecycle state of the finite state machine; and

establishing a network of the plurality of finite state machines by providing communication links among individual ones of the plurality of finite state machines according to the business rules, wherein the communication links define the integration flow.

10. The system of claim 9, wherein the processor is further programmed to initiate an executable operation comprising:

processing, using a selected one of the plurality of finite state machines, a business object associated with the selected finite state machine as part of the integration flow.

11. The system of claim 9, wherein the business rule specifies the next lifecycle state.

12. The system of claim 9, wherein the processor is further programmed to initiate an executable operation comprising:

receiving a user input specifying a business rule modification that changes the condition necessary to transition from the selected lifecycle state to the next lifecycle state for at least one finite state machine.

13. The system of claim 9, wherein the processor is further programmed to initiate an executable operation comprising:

receiving a user input specifying a business rule modification that changes an ordering of the selected lifecycle state and the next lifecycle state within at least one finite state machine.

14. The system of claim 9, wherein the business rules are editable by a user of the system.

15. The system of claim 9, wherein the processor is further programmed to initiate an executable operation comprising:

associating a business rule with a selected finite state machine specifying exception handling.

16. The system of claim 10, wherein processing, using a selected one of the plurality of finite state machines, a business object associated with the selected finite state machine as part of the integration flow comprises:

performing at least one of a schema modification or a content modification on the business object according to a business rule associated with the selected finite state machine.

17. A computer program product for cross domain integration in product lifecycle management, the computer program product comprising a computer readable storage medium having program code stored thereon, the program code executable by a processor to perform a method comprising:

providing, using the processor, a plurality of finite state machines, wherein each finite state machine is associated with one business object of an integration flow between a first enterprise information system and a second enterprise information system, and wherein each finite state machine defines a plurality of lifecycle states of the associated business object;

associating, using the processor, a business rule with each lifecycle state of each finite state machine, wherein for each finite state machine, the associated business rules are independent of the finite state machine, and wherein for a selected lifecycle state of each finite state machine, the associated business rule defines a condition causing a transition from the selected lifecycle state to a next lifecycle state of the finite state machine; and

establishing, using the processor, a network of the plurality of finite state machines by providing communication links among individual ones of the plurality of finite state machines according to the business rules, wherein the communication links define the integration flow.

18. The computer program product of claim 17, wherein the method further comprises:

processing, using a selected one of the plurality of finite state machines executing on a processor, a business object associated with the selected finite state machine as part of the integration flow.

19. The computer program product of claim 17, wherein the business rule specifies the next lifecycle state.

20. The computer program product of claim 17, wherein the method further comprises:

receiving a user input specifying a business rule modification that changes the condition necessary to transition from the selected lifecycle state to the next lifecycle state of at least one finite state machine;

or

receiving a user input specifying a business rule modification that changes an ordering of the selected lifecycle state and the next lifecycle state within at least one finite state machine.