Patent US6567783B1 successfully refreshed from Google Patents.
← Back to Patent Explorer
US6567783B1 Expired / Lapsed US ⏱️ 0.0 years remaining

Communication across one or more enterprise boundaries regarding the occurrence of a workflow event

Assignee: Blue Yonder Group Inc
•
Filing: 1998-09-18
•
Granted: 2003-05-20
•
Expires: 2018-09-18
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A computer implemented method for workflow communication is provided. The method includes the following steps. First, one or more workflows are executed. Then an event manger is triggered on the occurrence of a predefined event on the workflow. Finally, a message based on the event is formulated and sent to a fixed group.

Inventors

  • 👤 Ranjit N. Notani
  • 👤 Abhay V. Parasnis
  • 👤 Mark B. Whipple

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-02 17:15
CPC Classifications
G; G06; G06Q; G06Q10/00; G06Q10/06; G06F; G06F9/00; G06F9/06; G06F9/46; G06Q10/063; G06Q10/0631; G06Q10/06316; G06Q10/10

Claims Analysis

Total Claims: 23
Claim 1
Independent Claim 381 words
A method for multi-enterprise workflow communication, comprising: executing at least a portion of a workflow at a first enterprise; in response to execution of the at least a portion of the workflow at the first enterprise, triggering a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and based on that occurrence of the event and according to a first underlying parameterized workflow, communicating a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiating an instance of the second underlying parameterized workflow.
Claim 2
Independent Claim 381 words
A method for multi-enterprise workflow communication, comprising: executing at least a portion of a workflow at a first enterprise; in response to execution of the at least a portion of the workflow at the first enterprise, triggering a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and based on that occurrence of the event and according to a first underlying parameterized workflow, communicating a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiating an instance of the second underlying parameterized workflow.
Claim 3
Dependent Claim 25 words
The method of claim 1 , wherein the message is sent only to second enterprises in the group that have subscribed to receive such messages.
Claim 4
Dependent Claim 24 words
The method of claim 1 , wherein the message is sent individually to all the second enterprises of the group in a point-to-point manner.
Claim 5
Dependent Claim 20 words
The method of claim 1 , wherein the event comprises the arrival at the first enterprise of a business document.
Claim 6
Dependent Claim 14 words
The method of claim 1 , wherein the workflow comprises an automated system-to-system workflow.
Claim 7
Dependent Claim 14 words
The method of claim 1 , wherein the workflow comprises a user-interface work flow.
Claim 8
Independent Claim 372 words
A system for multi-enterprise workflow communication, comprising: a workflow manager at a first enterprise operable to manage operations associated with execution of at least a portion of a workflow at the first enterprise and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and the event manager at the first enterprise operable to, based on that occurrence of the event and according to a first underlying parameterized workflow, communicate a plurality of messages to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and the workflow manager at the first enterprise operable to, based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiate an instance of the second underlying parameterized workflow.
Claim 9
Independent Claim 372 words
A system for multi-enterprise workflow communication, comprising: a workflow manager at a first enterprise operable to manage operations associated with execution of at least a portion of a workflow at the first enterprise and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and the event manager at the first enterprise operable to, based on that occurrence of the event and according to a first underlying parameterized workflow, communicate a plurality of messages to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and the workflow manager at the first enterprise operable to, based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiate an instance of the second underlying parameterized workflow.
Claim 10
Dependent Claim 25 words
The system of claim 7 , wherein the message is sent only to second enterprises in the group that have subscribed to receive such messages.
Claim 11
Dependent Claim 24 words
The system of claim 7 , wherein the message is sent individually to all the second enterprises of the group in a point-to-point manner.
Claim 12
Dependent Claim 20 words
The system of claim 7 , wherein the event comprises the arrival at the first enterprise of a business document.
Claim 13
Dependent Claim 14 words
The system of claim 7 , wherein the workflow comprises an automated system-to-system workflow.
Claim 14
Dependent Claim 13 words
The system of claim 7 , wherein the workflow comprises a user-interface workflow.
Claim 15
Dependent Claim 392 words
Software for multi-enterprise workflow communication, the software being embodied in a computer-readable medium and when executed operable to: execute at least a portion of a workflow at a first enterprise; in response to execution of the at least a portion of the workflow at the first enterprise, trigger a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and based on that occurrence of the event and according to a first underlying parameterized workflow, communicate a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiate an instance of the second underlying parameterized workflow.
Claim 16
Dependent Claim 392 words
Software for multi-enterprise workflow communication, the software being embodied in a computer-readable medium and when executed operable to: execute at least a portion of a workflow at a first enterprise; in response to execution of the at least a portion of the workflow at the first enterprise, trigger a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and based on that occurrence of the event and according to a first underlying parameterized workflow, communicate a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiate an instance of the second underlying parameterized workflow.
Claim 17
Dependent Claim 25 words
The software of claim 13 , wherein the message is sent only to second enterprises in the group that have subscribed to receive such messages.
Claim 18
Dependent Claim 24 words
The software of claim 13 , wherein the message is sent individually to all the second enterprises of the group in a point-to-point manner.
Claim 19
Dependent Claim 20 words
The software of claim 13 , wherein the event comprises the arrival at a first enterprise of a business document.
Claim 20
Dependent Claim 14 words
The software of claim 13 , wherein the workflow comprises an automated system-to-system workflow.
Claim 21
Dependent Claim 13 words
The software of claim 13 , wherein the workflow comprises a user-interface workflow.
Claim 22
Independent Claim 389 words
A system for multi-enterprise workflow communication, comprising: means for executing at least a portion of a workflow at a first enterprise; means for, in response to execution of the at least a portion of the workflow at the first enterprise, triggering a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and means for, based on that occurrence of the event and according to a first underlying parameterized workflow, communicating a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and means for, based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiating an instance of the second underlying parameterized workflow.
Claim 23
Independent Claim 389 words
A system for multi-enterprise workflow communication, comprising: means for executing at least a portion of a workflow at a first enterprise; means for, in response to execution of the at least a portion of the workflow at the first enterprise, triggering a workflow manager at the first enterprise operable to manage operations associated with the workflow and to access an event manager at the first enterprise on an occurrence of a predefined event in the workflow; and means for, based on that occurrence of the event and according to a first underlying parameterized workflow, communicating a plurality of messages from the event manager at the first enterprise to a particular group of a plurality of second enterprises with which the first enterprise collaborates to notify the second enterprises in the particular group of that occurrence of the event: the first underlying parameterized workflow requiring for its operation parameterized data sufficient to particularize the first underlying parameterized workflow, each particularization of the first underlying parameterized workflow according to associated parameterized data comprising a separate instance of the first underlying parameterized workflow; the particular group of second enterprises being one of a plurality of groups of second enterprises, the first underlying parameterized workflow being particular to the particular group of second enterprises; the messages being communicated substantially simultaneously to the second enterprises in the particular group; each message being communicated to a corresponding one of the second enterprises in the particular group according to a corresponding instance of the first underlying parameterized workflow, the corresponding instance being particular to the corresponding one of the second enterprises in the particular group; each message containing parameterized data specific to that occurrence of the event and also specific to the corresponding one of the second enterprises in the particular group, the parameterized data in the message sufficient to particularize the first underlying parameterized workflow to yield the corresponding instance; each message being communicated to the corresponding one of the second enterprises in the particular group across an enterprise boundary of the first enterprise and across an enterprise boundary of the corresponding one of the second enterprises in the particular group; and means for, based on that occurrence of the event and according to a second underlying parameterized workflow different from the first underlying parameterized workflow, initiating an instance of the second underlying parameterized workflow.

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2006-05-19 2006-11-18 2007-05-20 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2010-05-19 2010-11-18 2011-05-20 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2014-05-19 2014-11-18 2015-05-20 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag