WO2003029920A2 - Systeme et procede permettant d'ameliorer l'efficacite operationnelle au moyen d'une preparation automatisee - Google Patents

Systeme et procede permettant d'ameliorer l'efficacite operationnelle au moyen d'une preparation automatisee Download PDF

Info

Publication number
WO2003029920A2
WO2003029920A2 PCT/US2002/030733 US0230733W WO03029920A2 WO 2003029920 A2 WO2003029920 A2 WO 2003029920A2 US 0230733 W US0230733 W US 0230733W WO 03029920 A2 WO03029920 A2 WO 03029920A2
Authority
WO
WIPO (PCT)
Prior art keywords
event
automation
rule
user
automation rule
Prior art date
Application number
PCT/US2002/030733
Other languages
English (en)
Other versions
WO2003029920A3 (fr
Inventor
Zdenek Becka
Ravi Srinath Gorur
Borna Safa
Roderick Peter Silton
Michael Baker Yost
Original Assignee
Intersect Software Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/073,142 external-priority patent/US20030065546A1/en
Priority claimed from US10/073,141 external-priority patent/US20030074090A1/en
Priority claimed from US10/073,151 external-priority patent/US20030078821A1/en
Application filed by Intersect Software Corporation filed Critical Intersect Software Corporation
Priority to AU2002337725A priority Critical patent/AU2002337725A1/en
Publication of WO2003029920A2 publication Critical patent/WO2003029920A2/fr
Publication of WO2003029920A3 publication Critical patent/WO2003029920A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates generally to enterprise management, and more specifically to a system and method for improving operational efficiency through process automation. Discussion of the Related Art Operational efficiency is a key component of a successful organization.
  • Operational overhead is incurred any time an individual within an organization expends time and resources performing an administrative function that detracts from their primary job focus.
  • process automation is enabled through rules that can be bound to system objects.
  • FIG. 1 is a hierarchical organization of system objects.
  • FIG. 2 is an illustration of the relationship between rules and event sources.
  • FIG. 3 is an embodiment of a rule definition user interface screen.
  • FIG. 4 is an embodiment of a user interface that enables binding of rules to other system objects.
  • FIG. 5 is an embodiment of a workflow activity domain model.
  • FIG. 6 is a workflow state diagram.
  • automation tools are based on the concept of rules. Rules give individuals a mechanism to specify actions that can be automatically executed based on the occurrence of specified events. Examples of various actions include notifications (e.g., email), running queries, creating new system objects, etc., while examples of various events include changes in an attribute or association of a system object, expiration of a timer, external events, etc.
  • rules are based on an event-condition-action (ECA) model.
  • ECA event-condition-action
  • occurrence of an event of interest and the satisfaction of some set of conditions causes the execution of a set of actions.
  • the event and condition components form the scheduling part of the rule and set up the environment context necessary for performing the actions of the rule.
  • events are things that happen in a system. Events are created by event sources. Rules listen for events of interest that occur in the system.
  • event sources include system objects that represent various items such as activities, containers, contracts, resources, and external systems.
  • Activities represent work within an organization.
  • Various work-related activity objects can be defined, such as project, summary task, task, and workflow objects.
  • a project activity is an association of activities that are focused on completing some objective. Projects do not have work associated with them directly but are the incorporation of several smaller units of work. Projects can be larger in scale and have some corporate visibility associated with them.
  • Summary tasks are similar to projects as they represent a collection of smaller activities. Summary tasks generally do not have corporate visibility but they are used to summarize work in progress. Tasks are the smallest unit of activity and represent the building blocks of projects and summary tasks.
  • workflow activities represent activities that have pre-defined workflows and processes associated with them.
  • the predefined workflows can be specified in terms of workflow states, with transitions between workflow states being governed by a workflow state machine.
  • Containers represent a group of system objects.
  • Containers can act as a parent in a structural association (e.g., folder, project, summary task) and can take multiple children system objects.
  • Structural associations allow containers to be used in organizing a system object repository in a hierarchical tree.
  • FIG. 1 A graphical illustration of a hierarchical system object repository is provided in FIG. 1.
  • the Root folder includes projects A and D.
  • Project A includes projects B and C, which further include tasks E-G and H-I, respectively.
  • Project D further includes task J.
  • the structural association relationship between folders, projects, and tasks enables the organization of work-related activities.
  • contracts represent agreements between entities within an organization. Typically, this agreement is for a first entity to deliver some product and/or service to a second entity within some time frame.
  • the entity that delivers the product and/or service is referred to as the "provider" of a contract.
  • the entity that is to receive the product and/or service is referred to as the "customer” of a contract.
  • the time frame the product and/or service will be delivered is referred to as the due date of the contract.
  • the contract object can also include a Contract State attribute that identifies a state of the contract (e.g., proposed, agreed, delivered, and completed), where movement between the various contract states is governed by a contract state machine.
  • activity objects, container objects, and contract objects being examples of event sources, can be used to initiate some action that is defined by a rule.
  • a change in the expected due date of an activity, a change in the set of tasks within a project, or a change in a state of a contract can represent an event within the system that gives rise to an automated action (e.g., email notification).
  • rules use triggers to select events of interest.
  • Possible triggers include a system object attribute change trigger, a system object association change trigger, a timer expiration trigger, a system object delete trigger, a problem domain specific trigger, and an external event trigger.
  • a system object attribute change trigger selects those events that represent changes to a named attribute. The attribute change trigger would specify an attribute that is selected from a list of valid system object attribute.
  • a system object association change trigger selects those events that represent changes to the named association.
  • the association change trigger would specify a named association.
  • Examples of association changes include an association element added (e.g., new child), an association element deleted (e.g., participant removed), and an association changed (e.g., parent changed).
  • a timer expiration trigger allows the user to add a time driven event to any event source with which the rule is bound.
  • the timer expiration trigger itself does not perform any timing. It does, however, contain data to provide some default information for the creation and starting of the timer at the time of binding to the event source.
  • Attribute-based timers can be based on a time/date attribute of the event source (e.g., due date). Independent timers, on the other hand, are based on a timeout value that is entered at the time the timer expiration trigger is being created or updated. The timeout value can be independent of any event source. Independent timers may also be periodic. Independent timers can be absolute in that the date and time of expiration is fixed (e.g., 26 Nov 2001 at 12 PM), or can be relative to the time of binding (e.g., in 3 days).
  • a system object delete trigger selects those events that represent deletion of the named system object.
  • a problem domain specific trigger supports the creation of rules based on concepts at a level higher than system object attributes. Problem domain specific triggers can provide a simpler way to build rules based on problem domain concepts. These triggers allow rules such as "Notify me when all my predecessors complete" to be created.
  • an external event trigger selects those events that occur outside of the system.
  • triggers can be grouped together in a trigger set.
  • a trigger set can have a "type" that indicates that the trigger set contains triggers that only apply to a single system object type.
  • the set of potential triggers for a container object is different from the set of potential triggers for an activity object.
  • a trigger set of a folder type would include only triggers suitable for a folder object.
  • An attribute trigger can be defined by specifying the name of a system object attribute.
  • an activity object attribute change trigger could specify an activity object attribute, such as the due date.
  • the due date attribute for the associated activity object i.e., the event source
  • the trigger would match.
  • Any quantity of the potential attribute change triggers available for the particular system object type can be specified.
  • Timer triggers indicate that the condition is to be evaluated when a timer expires.
  • the user can set the desired timer expiration to an explicit value or to be based on one of the event source's date/time fields. Timer triggers may therefore contain some additional information to determine the desired timer expiration value.
  • a context of the rule is set. This event context provides a system object for condition evaluation and action execution. Rule conditions use the event context to further refine whether the event is of interest.
  • rules are constructed so that the rule contains a potential context.
  • the rule has appropriate triggers defined for a specific event source type.
  • the rule may be defined with appropriate triggers for a task activity object.
  • Rules are then associated with a particular event source. When the particular event source actually produces an event and the event matches the trigger, then the system object for the event source becomes the event context for the rule.
  • the trigger framework supports listening for changes in a single type of event source and reacts to events from a single event source at a time.
  • a user can create a rule that may be bound to multiple event sources of a particular event source type. The rule would then respond to event sources one at a time and would not include a condition that references event contexts generated by other event sources.
  • the rule condition is evaluated against the provided system object attributes.
  • conditions permit further evaluation of the context to support increased control (filtering) of when actions should be performed.
  • Conditions can include one or more terms that evaluate to a true or false. Terms are combined with logical operators to produce a true/false value for the entire condition. Examples of possible logical operators are illustrated in Table 1.
  • Table 1 In addition, operators for problem domain specific conditions can be defined. Examples of possible operators are illustrated in Table 2.
  • response actions perform one or more actions on either the system object specified in the event context or some arbitrary, a priori specified, system object.
  • all response actions for a single rule are performed as a single transaction. If a particular command fails to execute correctly then all commands for that rule would be aborted with a log message being generated. If multiple rules exist for a single event then the response actions may be executed as separate transactions, or may be performed as a single transaction. If they are performed as a single transaction, then all response actions would follow an all succeed or all fail mode of operation.
  • supported response actions include Create, Update, Bind, Unbind, Copy, Execute, and Notify actions.
  • the Create action creates an instance of the specified system object
  • the Update action Updates an attribute of the specified system object
  • the Bind action binds one or more system objects to another system object
  • the Unbind action unbinds one or more system objects from another system object
  • the Copy action copies a system object
  • the Execute action causes the action (e.g., triggering of a rule) defined by the target system object or target external system command (e.g., execute a program) to be performed
  • the Notify action sends a notification of a given type (e.g., e-mail) to one or more recipients. Details of an example syntax for these response actions are provided in Appendix A.
  • rule storm a cascade of rules (or "rule storm") being launched.
  • This cascade may be a large finite sequence of rules or an infinite sequence of rules (e.g., a loop).
  • the system should have a mechanism in place to ensure that rule triggers can be canceled when the system detects a rising cascade of rules. This mechanism thereby ensures that the system will not be overwhelmed by a rule storm.
  • actions can be both event context sensitive and event context invariant.
  • the results of actions that are event context sensitive depend on the context in which the actions are performed. For example, a notification can be sent to the participants of THIS activity, where THIS activity is not known at rule creation time, but at rule evaluation time (i.e., when the event context is determined). Thus, if the rule is evaluated in the context of the task "Eat Lunch", then only the participants of the task "Eat Lunch” are notified.
  • rule In general, the context sensitive nature of the rule enables rules to be flexibly applied to the various system objects that exist within the system. For example, rules can be specified with notification actions that are applicable to specific roles (e.g., project leader, quality assurance representative, etc.) that are used throughout the organization. These roles would then be resolved to particular users in the particular context to which the rule was applied.
  • roles e.g., project leader, quality assurance representative, etc.
  • rules can be created by individual users. Rule creation therefore enables customization of the process automation tools to the desires of the individual. In this manner, process automation can be introduced in an incremental, bottom-up fashion into the organization. Incremental development can be based on rules that are reasonably small in scope.
  • a ruleset system object is provided.
  • the ruleset contains system object references to rule and ruleset system objects.
  • the ruleset can then be bound to event sources in a manner similar to the binding of a rule to event sources. This means that all the rules in the ruleset would be evaluated in the context provided by the event source.
  • rules and rulesets are not useful unless they are associated with one or more event sources. This process is called binding and creates an automation association between the rule/ruleset and an event source.
  • the automation association between the rule/ruleset and the event source represents a relationship between system objects where the system objects are not necessarily organized hierarchically.
  • This form of general association is based on a system object reference, which is in essence a handle, or soft link from one of the system objects in the association to the other system object in the association.
  • automation binding is used to indicate which rules are applicable to the event source and hold for each rule, event source pair. Binding a rule to an event source sets the rule to listen for events from that event source. Binding a ruleset to an event source sets up all member element rules in the ruleset to listen for events from that event source.
  • rule 210 is bound to an event source 260 via rule binding 240.
  • event source 260 can be a container 270, an activity 280, or a contract 290.
  • Each of container 270, activity 280, and contract 290 are specific types of system objects 230.
  • ruleset 220 is bound to event source 260 via rule binding 250.
  • Ruleset 220 is itself a group of rules 210 and rulesets 220. It should be noted that while not shown, a rule can also be bound to an event timer.
  • rule object 210 includes the attributes listed in Table 3. These attributes can be defined in the context of a user interface that enables a user to create or edit a rule.
  • User interface screen 300 includes an event source type field 310 and a rule definition section 320.
  • Event source type field 310 indicates that a rule definition is being prepared for a "Task" activity event source.
  • Rule definition section 320 further includes event, condition, and action component sections 322, 324, 326, respectively.
  • Event component section 322 is used to specify a particular event generated by the event source.
  • the specified event is based on a system object attribute change trigger that identifies a change in the State attribute for the Task activity.
  • the task also has a Workflow State attribute that includes states such as outline, write, review, edit, and complete.
  • Condition component section 324 specifies two conditions to be evaluated upon detection of a change in the State attribute of the Task. First, it is determined whether the Workflow State attribute is in the "write” state. Second, it is determined whether the State attribute is in the "Ready” state. In effect, these two conditions are used to determine the point in time at which a document, that is being prepared in the Write state of a workflow, is ready to be reviewed. If both of these conditions evaluate to True (i.e., logical AND), then the specified rule actions would be initiated.
  • condition component section 324 can include a set of terms that each potentially evaluate to true or false, a statically true condition can also be specified. This statically true condition would ensure that the occurrence of the event specified in event component section 322 would always lead to the initiation of the specified rule actions specified in action component section 326.
  • Action component section 326 is used to specify the rule actions that are to be performed upon the satisfaction of the conditions in condition component section 324.
  • three different actions are specified.
  • a notification action is provided that is designed to notify a recipient of the task deliverable that the Workflow State attribute has changed to a value of "review.”
  • an update action is provided that is designed to change the Workflow State attribute of the Task object to a value of "review.”
  • a second update action is provided that is designed to change the State attribute of the Task object to a value of "Active.” In combination, these actions automatically provide status information to a future receiver of the task deliverable and update the status attributes of the Task object.
  • rule After the rule is defined, it can be stored in a rules repository either locally or in a centralized location.
  • a listing of defined rules would be displayed in a user interface that enables a user to create associations between rules and other system objects (e.g., container, activity, contracts). The creation of associations by the users serves to implement the desired automation into the system.
  • User interface screen 400 includes two user interface screen portions 410, 420.
  • User interface screen portion 410 includes a hierarchical structure of folder objects, thereby organizing ongoing work within the organization.
  • Within the "Enhancements" folder of the "Product Development” folder is a listing of tasks. These tasks include User Interface, Functionality, Reliability, and Documentation tasks.
  • User interface screen portion 420 includes a Rules folder.
  • the Rules folder includes a listing of four rules that have been generated. A rule within the Rule folder of user interface screen portion 420 may be bound to a task (or other suitable system object) by dragging the particular rule icon to the particular task.
  • FIG. 4 An embodiment of a user interface that enables the binding of rules to other system objects.
  • Rule 4 can be dragged to the Documentation task over path 430. Upon completion of this dragging motion, Rule 4 is bound to the Documentation task and becomes a listener of the events that are generated by the Documentation task. It should be noted that user interface screen 400 can also be used to bind rulesets to particular system objects. In the context of the embodiment of FIG. 4, the ruleset could be represented by a distinctive icon within Rules folder 420.
  • binding of rules or rulesets to system objects is a function of association creation. Accordingly, other user interface mechanisms can be designed to facilitate an association of particular rules to particular system objects. For example, pop-up windows that are generated on a right-mouse click can be used to select one or more rules to be associated with a particular system object.
  • association creation can be enabled automatically through personal rule bindings.
  • Personal rule bindings enable customization of the rules that are automatically associated with a particular system object once an individual is associated with that system object. In general, these personal rule bindings can be dependent on the type of system object, the role of the user, or any other variable that defines a relationship between the user and the system object.
  • a user can define a first set of rules that are to be automatically associated with any task activity that the user is associated with, and a second set of rules that are to be automatically associated with any project activity that the user is associated with.
  • a user can define a third set of rules that are to be automatically associated with any system object in which the user is taking on the role of point of contact, and a fourth set of rules that are to be automatically associated with any system object in which the user is taking on the role of an interested observer.
  • rules and rulesets that are bound to system objects operate under the authority of the user that created the association.
  • the user attributed with the association creation is able to maintain a virtual presence in the system through the rules and rulesets that operate under his authority.
  • the rules and rulesets therefore include a security credential associated with the user attributed with the association creation.
  • This security credential provides the appropriate permission for the operation of the rules and rulesets within the defined security framework.
  • the specific type of security credential is implementation dependent.
  • the security credential is the user ID.
  • rules represent a basic building block upon which process automation can be developed. These building blocks can be defined by individual users to address their particular automation needs. In this manner, process automation is introduced in an incremental, bottom-up fashion into the organization.
  • Process automation can also be achieved in an incremental, bottom-up fashion through the creation of workflow activities.
  • workflow activities represent activities that have pre-defined workflows and processes associated with them.
  • Workflow activities can be used to automate both simple and complex workflows.
  • workflows can be defined to govern a process for proper review and distribution of draft and final versions of system documentation.
  • workflow activities enable users to configure and automate activities that include a series of steps and decision points.
  • Workflow activities can also perform a number of automation functions based on events and conditions that occur in the system.
  • a user interface enables users to define a workflow that includes a series of steps as well as conditions for progressing through the series of steps. Portions of the workflow (e.g., notifications, form completion, etc.) can also be automated.
  • a workflow activity is based on a workflow (WF) Base element (a data template), a WF Template element (a behavior template), and a WF Instance element (an actual deliverable/piece of work).
  • WF workflow
  • FIG. 5 illustrates workflow activity domain model 500.
  • WF Base 510 is a conceptual component that supports multiple schemas for WF Instances.
  • WF Base 510 functions as a schema template for a future WF Instance system object 530.
  • WF Base type 521 -523 for each WF Instance 530.
  • WF Instance 530 is the behavior wrapper for an actual deliverable. It is a system object with the same schema as a particular WF Base 521- 523 and follows the workflow behavior specified by WF template 520.
  • WF Instances 530 are created by users to provide guidance and automation during the work required to produce a deliverable.
  • WF Instances 530 are generally created on an ad hoc basis.
  • each WF Instance 530 maps directly to one WF Base type 521- 523. While WF Instances 530 are the system objects created by users, the WF Base 510 determines the schema and any relationships the WF Instance 530 can participate in.
  • WF Base 510 provides a framework on which a workflow can be placed. Fields are customized to support the specific problem or deliverable being modeled by the workflow activity. WF Base 510 is a template for the data within a workflow activity. WF Base 510 is not generally visible to the user.
  • WF Base 510 is based on a task system object schema that is illustrated in FIG. 5, shown through the relationship of system object 540, activity object 550, and task object 560.
  • WF Instances 530 created from a WF Base type 521-523 have both the task system object schema and behavior.
  • WF base 510 includes the activity attributes provided in Table 4.
  • WF Base 510 has the Activity attributes of Table 3 as well as the additional workflow-related attributes of Table 6.
  • WF Template 520 is a system object that includes the description of how a specific type of work or deliverable is produced. It specifies the workflow (and its component states and the flows between states), roles, and rules used for action automation.
  • a WF Template 530 is a general description applicable to all instances of the work or deliverable and uses a specific WF Base (schema).
  • WF Template 520 is a "behavior template" that can be created and modified by individual users. A WF Template 520 should exist before any workflow activities can be instantiated.
  • a workflow specification includes, for each state in the workflow, the information of Table 6.
  • Participant Bindings represent the binding of a workflow state to a resource 570 (see FIG. 5).
  • the Participant Pool set is the union of all responsible parties for all states in the workflow.
  • resources 570 can include users, roles, and teams, each of which can be assigned to activities, receive notifications, and otherwise interact with the system. It should be noted that resources 570 can also represent inanimate objects as well. As the workflow activity participants represent those resources 570 that are responsible for the workflow activity during a particular state, the participants member set (i.e., the Resources working on the workflow activity) can change on a per workflow state basis.
  • a team provides information about a group of users bound together for some common cause. That cause could be organizational (i.e. common manager), role related (common type of work), task related (common deliverable), or other cause (e.g. common location, etc.). Teams enable the assignment of entire groups of users to activities and rules. Teams also enable the description of the organizational structure of the user community. Roles, on the other hand, represent a mechanism for assigning work items and automation actions to users indirectly. Roles are useful to help convey responsibility, and ease automation configuration. Roles are significant in that they may be assigned as participants to activities and rules and then resolved to an actual user independently within various scopes of the organization. For example the quality assurance (QA) representative for Project X may be Sue, while that same role for Project Y may be Fred. One set of rules and rule actions from the corporate handbook that pertain to a project's QA representative can thus be applied to tasks in both projects without need for change.
  • QA quality assurance
  • resource assignments to workflow activities are enabled through the use of local scope roles called workflow actors (WAs).
  • WAs provide various benefits to workflow activities, including support of WF Template 520 re-use, simplification of the process of creating WF Instances 530, provision of relevant interaction details to resources assigned to WF Instances 530, and abstraction of users from the details of WF Template 520 that do not apply to the user's interaction with WF Instances 530.
  • WAs are declared in WF Template 520 and can be associated with one or more workflow activity states.
  • a WA's scope is the WF Template 520 and hence any instantiated WF Instances 530.
  • a WF Instance 530 can only access the WAs declared in that WF Template 520.
  • WAs are resolved to resources on a per WF Instance basis, generally at "instantiation time".
  • WAs can support multiple resolutions, thereby enabling a WA to resolve to a list of one or more resources.
  • a WA includes Name and Description attributes.
  • the Name attribute is the name that is used within WF Template 520 and displayed to the user. This Name must be unique within a given WF Template 520.
  • the Description attribute contains an overall description of the WA. This description can be designed to provide enough information to allow the instantiator of the workflow activity to resolve the WA to the appropriate resource(s) and also to describe WA's responsibilities in each of the workflow activity states to which it is assigned.
  • WAs can also be referenced by rules/rulesets that are built against WF Template 520.
  • Rules/Rulesets for a workflow state enable automation actions to be incorporated into the workflow.
  • rules can be based on events and conditions that occur in the system.
  • rules/rulesets can be used in a variety of ways. In a simple example, a rule can be used to simply notify a resource that a workflow state deliverable has been completed. More generally, a rule/ruleset can be used in the process for producing the deliverable within the workflow state itself (e.g., form completion, document forwarding, status alerts, etc.).
  • Exit Criteria for a workflow state generally refers to a mechanism designed to generate information to be used for the determination of a possible state change.
  • the exit criteria is modeled as a set of questions, each of which resolves to a boolean result. More generally, the exit criteria can include rule-type conditions that can be evaluated on the WF instance to automatically generate information to be used for the determination of a possible state change.
  • Exit Criteria generally allows the workflow to enforce certain conditions before a state transition can occur.
  • Defined exit criteria should be evaluated on attempted exit transitions from a workflow state to contiguous next states.
  • Exit criteria can be completely automated, completely user driven or a combination of both.
  • Automated exit criteria should support arbitrary conditions on the workflow activity attributes and need not require any user data to be entered at evaluation time.
  • User- driven exit criteria can offer users questions that can be evaluated to a boolean result. For example, simple yes/no type questions can be supported. The various exit criteria can be logically combined to produce a final exit criteria response.
  • workflow state information also includes Next State information.
  • Next State information can be either an explicit state name or decision point details. An explicit name would provide the identity of the next state once the exit criteria have been satisfied.
  • a decision point is modeled as a set of possible target states (Target Set) from which the next state can be chosen from.
  • Decision points can be completely automated, completely user driven or a combination of both.
  • Automated decision points should support arbitrary conditions on the workflow activity attributes and should not require any user data to be entered at evaluation time.
  • User-driven decision points may offer users questions that can be evaluated to resolve exactly one out of many potential destination states.
  • workflows can be specified using a graphical user interface.
  • FIG. 6 illustrates an embodiment of a user interface screen 600, which enables the specification of workflow states and transitions.
  • User interface screen 600 includes a workflow display portion 610 and a workflow component section 620.
  • Workflow component section 620 includes a listing of workflow components that can be used to create a workflow specification.
  • the workflow component listing includes state, decision point, and split/join components. Selected workflow components can be used to create a workflow by "dragging and dropping" components into the workflow display portion 610.
  • FIG. 6 illustrates the "dragging and dropping" of a join component into workflow display portion 610 using path 630.
  • workflow component section 620 can be designed to include a variety of additional workflow components (e.g., resource or rule components). The specific selection of components in workflow component section 620 would be dependent on the level of specificity desired at the graphical-construction level.
  • workflow component specifications can be defined by the user through pop-up forms or other interface mechanisms that enable a direct or indirect specification of a portion of the workflow.
  • the workflow that is displayed in workflow display portion 610 represents one example of a possible workflow construction.
  • the workflow as defined includes states, decision points (which allow iterations and OR-splits), iterations (repeating a sequence of component states), OR-splits (single flow segment splits into two or more mutually exclusive segments), and OR-joins (two or more flow segments join to become one).
  • a state can be used to represent an activity (e.g., task), the completion of which would lead to a transition to a next state.
  • the exit criteria, participants, rules, etc. for that particular state can be defined, for example, by filling in one or more forms that are presented to the user when the state icon is selected.
  • a decision point would need to be defined to enable selection of the actual next state.
  • the conditions for the particular decision point can also be defined, for example, by filling in one or more forms that are presented to the user when the decision point icon is selected.
  • workflow specification can be generated and customized using the features of a particular user interface.
  • Workflow activities that have been created by a user can also be shared with other users, thereby encouraging rapid adoption of "best practices.” This proliferation of workflow activities also helps ensure consistency in the process execution across the organization.
  • workflow activities can be assigned by team leaders to team members (or by users to themselves) in a manner similar to the assignment of any task.
  • workflow activities can be sent to a user and displayed in that user's task manager in a manner similar to an email or task listing (e.g., Microsoft Outlook listing).
  • email or task listing e.g., Microsoft Outlook listing
  • workflow activities represent tasks having associated workflow behavior.
  • the only interaction with a conventional static task is a user's designation of completion of the static task (e.g., checkbox selection that removes the task from the task manager).
  • completion of the static task e.g., checkbox selection that removes the task from the task manager.
  • satisfaction of one or more conditions e.g., completion of a draft document
  • workflow activities cannot be designated as complete until each step in the workflow has been completed.
  • the status of the uncompleted workflow activity can also be reported to interested parties (e.g., team leaders). These status reports can be designed to provide an indication of the extent to which the workflow activity has been completed. This status reporting is significantly more valuable as compared to the binary status information (completed/not completed) of a static task.
  • ⁇ Source System Object ⁇ is a specific reference to a System Object. May be a reference to a System Object in context, newly created System Object, or, a direct reference to any supported System Object chosen via the user interface at rule creation time.
  • ⁇ name ⁇ may be string literal or a reference to an attribute of a System Object available in the context.
  • ⁇ path ⁇ may be selected via the user interface or the parent attribute of a System Object available in the context.
  • Example copy eat lunch to /plan-of-the day/done execute Causes the action defined by the target System Object or external system command to be performed.
  • ⁇ System Object ⁇ is a specific reference to a System Object. May be a reference to a System Object in context, newly created System Object, or, a direct reference to any supported System Object chosen via the user interface at rule creation time.
  • ⁇ parameters ⁇ is a list of System Object specific parameters
  • ⁇ External Command ⁇ is a reference to an external command.
  • the command should be recognizable by the host operating system.
  • the System can provide a configurable base directory from which these commands could be run.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Operations Research (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention répond aux besoins susmentionnés en mettant au point un mécanisme qui améliore l'efficacité opérationnelle au moyen d'une préparation automatisée. Selon un mode de réalisation, la préparation automatisée est validée au moyen de règles qui peuvent être liées à des objets système.
PCT/US2002/030733 2001-09-28 2002-09-27 Systeme et procede permettant d'ameliorer l'efficacite operationnelle au moyen d'une preparation automatisee WO2003029920A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002337725A AU2002337725A1 (en) 2001-09-28 2002-09-27 System and method for improving operational efficiency through process automation

Applications Claiming Priority (12)

Application Number Priority Date Filing Date Title
US32519501P 2001-09-28 2001-09-28
US32519401P 2001-09-28 2001-09-28
US32521801P 2001-09-28 2001-09-28
US60/325,195 2001-09-28
US60/325,194 2001-09-28
US60/325,218 2001-09-28
US10/073,141 2002-02-13
US10/073,151 2002-02-13
US10/073,142 US20030065546A1 (en) 2001-09-28 2002-02-13 System and method for improving management in a work environment
US10/073,141 US20030074090A1 (en) 2001-09-28 2002-02-13 System and method for improving operational efficiency through process automation
US10/073,142 2002-02-13
US10/073,151 US20030078821A1 (en) 2001-09-28 2002-02-13 System and method for identifying individuals having a desired skill set

Publications (2)

Publication Number Publication Date
WO2003029920A2 true WO2003029920A2 (fr) 2003-04-10
WO2003029920A3 WO2003029920A3 (fr) 2004-04-08

Family

ID=27557087

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2002/030731 WO2003029918A2 (fr) 2001-09-28 2002-09-27 Systeme et procede permettant d'ameliorer la gestion dans un environnement de travail
PCT/US2002/030733 WO2003029920A2 (fr) 2001-09-28 2002-09-27 Systeme et procede permettant d'ameliorer l'efficacite operationnelle au moyen d'une preparation automatisee
PCT/US2002/030732 WO2003029919A2 (fr) 2001-09-28 2002-09-27 Systeme et procede permettant d'identifier des individus presentant un ensemble de qualifications souhaitees

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2002/030731 WO2003029918A2 (fr) 2001-09-28 2002-09-27 Systeme et procede permettant d'ameliorer la gestion dans un environnement de travail

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US2002/030732 WO2003029919A2 (fr) 2001-09-28 2002-09-27 Systeme et procede permettant d'identifier des individus presentant un ensemble de qualifications souhaitees

Country Status (2)

Country Link
AU (3) AU2002330116A1 (fr)
WO (3) WO2003029918A2 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5870545A (en) * 1996-12-05 1999-02-09 Hewlett-Packard Company System and method for performing flexible workflow process compensation in a distributed workflow management system
US5937388A (en) * 1996-12-05 1999-08-10 Hewlett-Packard Company System and method for performing scalable distribution of process flow activities in a distributed workflow management system
US5999911A (en) * 1995-06-02 1999-12-07 Mentor Graphics Corporation Method and system for managing workflow
US6041306A (en) * 1996-12-05 2000-03-21 Hewlett-Packard Company System and method for performing flexible workflow process execution in a distributed workflow management system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5117353A (en) * 1989-05-05 1992-05-26 Staff-Plus, Inc. System for use in a temporary help business
US5592375A (en) * 1994-03-11 1997-01-07 Eagleview, Inc. Computer-assisted system for interactively brokering goods or services between buyers and sellers
US5826244A (en) * 1995-08-23 1998-10-20 Xerox Corporation Method and system for providing a document service over a computer network using an automated brokered auction
US6141653A (en) * 1998-11-16 2000-10-31 Tradeaccess Inc System for interative, multivariate negotiations over a network
US6336105B1 (en) * 1998-11-16 2002-01-01 Trade Access Inc. System and method for representing data and providing electronic non-repudiation in a negotiations system
US6275812B1 (en) * 1998-12-08 2001-08-14 Lucent Technologies, Inc. Intelligent system for dynamic resource management
US6408337B1 (en) * 1999-05-14 2002-06-18 Coca-Cola Company Engagement of non-employee workers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5999911A (en) * 1995-06-02 1999-12-07 Mentor Graphics Corporation Method and system for managing workflow
US5870545A (en) * 1996-12-05 1999-02-09 Hewlett-Packard Company System and method for performing flexible workflow process compensation in a distributed workflow management system
US5937388A (en) * 1996-12-05 1999-08-10 Hewlett-Packard Company System and method for performing scalable distribution of process flow activities in a distributed workflow management system
US6041306A (en) * 1996-12-05 2000-03-21 Hewlett-Packard Company System and method for performing flexible workflow process execution in a distributed workflow management system

Also Published As

Publication number Publication date
WO2003029919A2 (fr) 2003-04-10
AU2002330116A1 (en) 2003-04-14
AU2002337724A1 (en) 2003-04-14
WO2003029919A3 (fr) 2004-03-25
WO2003029920A3 (fr) 2004-04-08
AU2002337725A1 (en) 2003-04-14
WO2003029918A3 (fr) 2004-05-13
WO2003029918A2 (fr) 2003-04-10

Similar Documents

Publication Publication Date Title
US20030074090A1 (en) System and method for improving operational efficiency through process automation
AU2001249273B2 (en) Method and system for top-down business process definition and execution
US6122633A (en) Subscription within workflow management systems
Abbott et al. Experiences with workflow management: issues for the next generation
US9772754B2 (en) Collaborative network-based graphical progress management tool
US8296170B2 (en) Process management system and method
US8095411B2 (en) Guided procedure framework
US7849052B2 (en) Electronic document manager
US7197740B2 (en) Pattern-based software design
US6820118B1 (en) Method and system for providing a linkage between systems management systems and applications
US20060085245A1 (en) Team collaboration system with business process management and records management
US6832201B1 (en) Method and system for optimizing request shipping in workflow management systems
AU2001249273A1 (en) Method and system for top-down business process definition and execution
US20050038687A1 (en) Business communication solutions
US20120310699A1 (en) Approach and tool blending ad-hoc and formal workflow models in support of different stakeholder needs
JP2006099728A (ja) 共同アプリケーションにおけるワークフローの関連付け
US20080295101A1 (en) Electronic document manager
JPH05197573A (ja) タスク指向パラダイムによるタスク管理システム
JP2007515016A (ja) 自動化されたワークフローサービスシステム及びそのサービスを提供する方法
US7640312B2 (en) Method, system, and program product for managing communications pursuant to an information technology (IT) migration
US8037140B2 (en) System, method and program product for managing communications pursuant to an information technology (IT) migration
US7711717B2 (en) Achieving recurring item recordings from calendaring applications over LOB systems
EP2915131A1 (fr) Gestion de cas en utilisant des entités actives dans un réseau social
WO2003029920A2 (fr) Systeme et procede permettant d'ameliorer l'efficacite operationnelle au moyen d'une preparation automatisee
US11756000B2 (en) Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG UZ VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP