WO1998027500A1 - Computer executable workflow control system - Google Patents
Computer executable workflow control system Download PDFInfo
- Publication number
- WO1998027500A1 WO1998027500A1 PCT/US1997/023600 US9723600W WO9827500A1 WO 1998027500 A1 WO1998027500 A1 WO 1998027500A1 US 9723600 W US9723600 W US 9723600W WO 9827500 A1 WO9827500 A1 WO 9827500A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- item
- work
- definitional data
- networked
- operator
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 97
- 230000008520 organization Effects 0.000 claims abstract description 78
- 238000012545 processing Methods 0.000 claims abstract description 42
- 230000008569 process Effects 0.000 claims description 39
- 230000001419 dependent effect Effects 0.000 claims description 10
- 238000012546 transfer Methods 0.000 claims description 7
- 238000007726 management method Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 5
- 238000013500 data storage Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- KWYUFKZDYYNOTN-UHFFFAOYSA-M potassium hydroxide Substances [OH-].[K+] KWYUFKZDYYNOTN-UHFFFAOYSA-M 0.000 description 4
- 101100115215 Caenorhabditis elegans cul-2 gene Proteins 0.000 description 3
- 230000002250 progressing effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/10—Office automation; Time management
-
- 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
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
Definitions
- the invention relates generally to computer executable workflow management and control systems and more particularly to computer system executable methods for controlling access to, or processing of, a work item in a database of workflow work items stored by the computer system.
- work items for execution from a database of unexecuted work items.
- work items represent tasks such as filling out documents, returning telephone calls to potential or existing customers, initiating transactions, or similar duties.
- Work items may arrive at the database from outside the organization or from inside the organization or both. For example, if the organization provides financial services, the work items may relate to client account maintenance, buy and sell orders, internal management directives, and the like.
- Efficiency gains can be accomplished by implementing a workflow management system that automates a process for distributing the work items to the members of the organization (i.e., operators) .
- the work items are stored in a database.
- definitional data Associated with the work items is definitional data.
- the definitional data includes a plurality of definitional data items. Each definitional data item includes, for example: information about steps
- nodes in a process for manipulating the work item
- information about a characteristic of a list i.e., a queue associated with a node
- information about a rule specifying a protocol for executing the work item such as a display characteristic for the work item
- a node typically represents a single task in a work environment; for example, the single task may be "submitting new account applications.” More particularly, a node represents a unit step of work specified in one or more processes; for example, a process for handling new account applications may have a node representing a unit step being "new account application approval.” Each node may be used in more than one process and may be associated with a department having responsibility for the single task or unit step of work.
- each member of the organization i.e., each operator
- a computer station such as a personal computer.
- the computer stations are connected to a computer system running a workflow application program.
- the operator requests a work item from the database.
- a work item is assigned, processed, displayed in accordance with the definitional data, and then completed by the operator, a new work item is provided from the database to the computer station in response to another request from the computer station.
- Some organizations are structured into separate sub-organizations such as departments or divisions or separate business units, with each such sub-organization requiring some control over access to and processing of the sub-organization's work items.
- the sub- organizations may require different sets of rules governing the flow of work items but may also need to share work items.
- the work items may be shared by making and distributing copies of the work items. In such cases, it is necessary to keep track of the copies and also to ensure cross-database consistency of definitional data concerning the shared work items.
- One proposed system allows a single database to be used to store the work items of different sub- organizations.
- each sub- organization maintains general access rules unrelated to the specific type of business activity performed by the sub-organization.
- the access rules maintained by each sub-organization are provided specifically to prevent access by the sub- organization to work items not pertaining to the sub- organization.
- a change in the structure of the organization or one of the sub-organizations typically requires changes to each sub-organization's access rules.
- a computer system executable method for controlling access to, or processing of, a work item.
- the work item is stored in a database of work items for subsequent execution by at least one operator.
- the database (perhaps along with some computing resources associated with the database) is used by a plurality of organizations.
- the operator belongs to one of the organizations.
- the method stores in a memory a plurality of organization identifiers. Each one of the organization identifiers is associated with a corresponding one of the organizations. Definitional data items are also stored in the memory. Each one of the definitional data items is associated with the one of the organizational identifiers.
- the method provides the operators with access to, or allows the operators to be affected by, one of the definitional data items only if the operator is associated with the same organization identifier associated with the definitional data item.
- the definitional data item controls access to, or processing of, the work item.
- each organization has its own identifier and the definitional data item is associated with one of the identifiers (and hence with a specific organization) , establishment of, and subsequent change to, work item flow through a single workflow system used by different organizations is facilitated.
- an additional organization may be added simply by associating the additional organization with an additional organization identifier in the first memory section.
- the method allows efficient use of the workflow system's storage facilities, because multiple organizations' definitional data items may be stored together while remaining logically separate as a result of the organization identifiers.
- Implementations of this aspect of the invention may include one or more of the following features.
- the memory may store a data structure relating each one of the plurality of operators with one of the organization identifiers; and one of the operators of the organization may be provided with access to, or may be affected by, one of the definitional data items only if the data structure stored in the third memory section associates the one of the operators with the same organization identifier associated with the one of the definitional data items.
- the definitional data item may include: information about a node corresponding to a step in a process for manipulating the work item; a rule specifying a display, transfer, or processing characteristic for the work item; information about a characteristic of the operator; information about a characteristic of a queue associated with a node; or information about a setup component such as an item-type code, a status code, or a value group.
- another computer system executable method is provided for controlling access to, or processing of, work items .
- the work items are stored in a database of work items for subsequent execution by operators.
- the method includes storing in a memory: information defining nodes (e.g., steps, departments, persons) available for use in processing the work items; and a programmable data structure defining an organizational relationship between selected ones of the stored nodes to control the access to, or processing of, the work item.
- the data structure is programmed to provide the organizational relationship between the nodes to control access to, and processing of, the work item by an operator.
- This method allows the progression of work items within an organization to be controlled in accordance with a programmable organizational structure. Such method facilitates assuring that work items are accessible to only selected operators in the organization.
- Implementations of this aspect of the invention may include one or more of the following features.
- the organizational relationship may be hierarchal or matrix- oriented.
- the operator may be associated with one of the nodes where each node may correspond to a step in a process for manipulating the work item within the organization or sub-organization.
- the method may further include storing definitional data items used in controlling access to, or processing of, the work item.
- a computer system executable method is provided for controlling access to, or processing of, a work item.
- the work item is stored in a database of work items for subsequent execution by an operator in accordance with definitional data stored in the database.
- the method includes storing in a hierarchy memory section a networked data structure (e.g., a tree data structure) having networked entries (e.g., tree entries) .
- the networked data structure corresponds to an organization having nodes for manipulation of work items.
- the nodes correspond to steps used to process a work item and may represent, for example, departments within an organization or sub-organization, or persons within a department.
- the organization is organized hierarchally and each networked entry corresponds to one of the nodes.
- a process memory section stores a process table specifying a sequence of steps for manipulating the work item by the nodes.
- a definitional data item memory section stores a definitional data item associated with the nodes.
- access and processing control is made robust by allowing the organization to establish such control at a time when the organization is setting up (i.e., defining) a workflow system for manipulating work items or is modifying the setup of the workflow system, as opposed to checking each such work item at a subsequent time as mentioned before.
- FIG. 1 is a block diagram of a computer system for execution of the methods according to the invention
- FIGs . 2-4 are flow diagrams of methods for controlling access to a workflow work item in a database of work items stored by the computer system of FIG. 1 according to the invention
- FIGs. 5-7 are block diagrams of data structures and organizational structures used in the methods of FIGs. 2-4;
- FIG. 8 is an organizational chart useful in understanding features of the invention
- FIG. 9 is a block diagram of a data structure used to control workflow in an organization having the organizational chart shown in FIG. 8;
- FIGs. 10 and 11 are diagrams useful in understanding the workflow process for the organization having the organizational chart shown in FIG. 8. Description of the Preferred Embodiments Referring now to FIG. 1, a computer system 16 is shown programmed to execute methods shown in FIGs. 2-4 for controlling access to, or processing of, a work item 10.
- the work item 10 is stored in a database 14 of work items 10 for subsequent execution by an operator, not shown, belonging to an organization.
- the operator here exemplified by a person, may in fact be multiple persons or one or more automated operator computer programs .
- the database 14 is used by a plurality of organizations, here sub-organizations of the organization. (It should be understood, however, that the organizations need not be organizationally related to each other - the organizations may merely share the database 14 and perhaps also some computing resources associated with the database 1 . )
- Each step in a process, such as processes 58 ! , 58 2 , 58 3 , shown in FIG. 10, for manipulating the work item 10 is performed in each sub-organization by an operator or operators assigned to the sub-organization.
- the method includes storing in a memory section 37 (FIG. 5) , sub-organization identifiers (ORG ID) .
- Each one of sub- organization identifiers (ORG ID) is associated with a corresponding one of the sub-organizations, here divisions, (i.e., DIV1 , DIV2 , DIV3 , and so on) as shown in FIG. 5.
- Another memory section 39 (FIG.
- FIG. 6 stores a plurality of definitional data items (such as rules 56, 68, 72), each one of the plurality of definitional data items being associated with a corresponding one of the sub-organization identifiers (ORG ID) , as shown in FIG. 6.
- Each one of the definitional data items controls access to, or processing of, the work items.
- Another memory section 41 (FIG. 7) stores a data structure wherein each one of the operators (OP ID) of the organization is associated with one of the sub- organization identifiers (ORG ID), as shown in FIG. 7.
- Each one of the operators (such as operators Al , 01, and so on) of the organization is provided with access to, or is affected by, a definitional data item (e.g., rule 56 or 68) , only if the data structure stored in the memory section 41 associates said one of the operators with the same sub-organization identifier associated with said definitional data item in the memory section 39.
- operator 01 belongs to an organization identified by "ORG ID" as "1" (i.e., from the memory section 37 operator 01 belongs to DIV1) .
- ORG ID as "1”
- definitional data items 56, 68, 72, 75 which is associated with ORG ID "2", here, from memory section 37, DIV2.
- the work item 10 is stored in the database 14 of work items 10 for subsequent execution by one of a plurality of operators (not shown) at one of a plurality of computer stations 12.
- the database 14 of work items 10 may be implemented using an Oracle ® Pyramid ® database system version 7.2.
- the computer system 16 may include a Pyramid ® NILETM computer having eight central processing units and two gigabytes of fast- access memory.
- an operating system such as Data Center Operating System (“DC-OSx") runs on the computer system 16.
- the computer system 16 also runs a workflow application program 20 providing key functions used to provide a workflow management system as, for example, described by the Workflow Management Coalition in Workflow Management Coali tion Terminology & Glossary- Issue 2.0 (1996), incorporated by reference.
- Each one of the computer stations 12 may be a personal computer running an operating system such as
- the computer system 16 and the computer stations 12 are interconnected across a bidirectional data connection bus 18 such as a network connection provided by a computer network using a TCP/IP protocol .
- a work item 10 is stored in the database 14 (step 300) .
- the memory section 37 (FIG. 5) stores an organizations data structure 40 associating a first sub-organization 42 (FIG. 8) , here Division 1 (DIV1) of the organization, with a first identifier (i.e., ORG ID), here "1" 44, and also associating a second sub-organization 46 (FIG. 8) , here Division 2 (DIV2) , with a second identifier, here "2" 47 (step 310) .
- the memory section 39 (FIG.
- the memory section 41 (FIG. 7) stores another data structure such as a rules data structure 48 associating each one of a plurality of definitional data items (to be described) with one of the identifiers, such as a rule 56 with the first identifier ORG ID 1, which corresponds to DIV1 42 (step 320) .
- the memory section 41 (FIG. 7) stores an operator/administrators data structure 50 associating the operator/administrator with one of the identifiers 44, 47 (step 330).
- operator (OP ID) Al having log- in ID Al, is indicated as being an administrator associated with ORG ID 1, and hence, from the memory section 37, with DIV1 42.
- OP ID 02 indicates that such operator/administrator is an operator associated with ORG ID 2 and hence, from the memory section 37, associated with DIV2 46.
- Each operator/administrator hereinafter being referred to as an operator, is then provided with access to one of the definitional data items (e.g., the rule 56), or is affected by said one of the definitional data items only if the operators data structure 50 associates the operator with the same identifier (i.e., the first identifier 44) associated with the one of the definitional data items (i.e., the rule 56) (step 340).
- operator 01 is, from memory section 41, associated with ORG ID 1. From the memory section 37, ORG ID 1 is associated with DIV1 42.
- operator 01 As well as all members in DIV1, are able to process work items defined by rules 56, 68, 72, 74 and 75.
- rule 56 defines a NEW ACCOUNT APPLICATION
- rule 68 defines a NEW ACCOUNT APPROVAL.
- operator 01 can handle new account applications and new account approvals.
- operator 02 and all other operators belonging to DIV2 are able to process work in accordance with rule 77 because such operators are in DIV2 46.
- each sub- organization 42, 46 is shown with a networked data structure, here a tree data structure, having networked entries, here tree entries.
- the tree data structure corresponds to an organization, here a sub-organization, having nodes A-L for manipulation of work items.
- the organization here sub-organization, is organized hierarchally and each tree entry corresponds to one of the nodes.
- the nodes A-L correspond to steps used to process a work item and may represent, for example, departments within the sub-organization or persons within a department. For example, if the nodes are departments, departments represented by Nodes E and F report into the department represented by Node B and the department represented by Node B reports into the department represented by Node A. If the nodes are persons in a department , persons represented by Nodes E and F report into the person represented by Node B and the person represented by Node B reports into the department manager represented by Node A.
- the networked data structure here tree data structure 65, appears in an organization data structure 64 stored in another memory section 73 (FIG. 9) .
- Nodes A- I are shown as belonging within ORG ID 1 (i.e., DIVl 42)
- Nodes J-L are shown as belonging within ORG ID 2 (i.e., DIV2 46).
- Nodes B, C and D are shown as being dependent on Node A;
- Nodes E and F as being dependent on Node B;
- Nodes G and H as being dependent on Node C;
- Node I as being dependent on Node D; and
- Nodes L and K as being dependent on Node J.
- a process table 69 (FIG. 10) specifying sequences of steps for manipulating work items is stored in another memory section (not shown) .
- the work item is to pass from Node A to Node B and then to Node C.
- the work item is to pass from Node B to Node A to Node I.
- the work item is to pass from Node E to Node F and then to Node C.
- the memory section 41 (FIG. 7) stores definitional data items (here operators) associated with the nodes.
- the OP ID Al is associated with Node B, OP 01 with Node K and so forth.
- a request is received to store in the memory section 39 (FIG. 6) a proposed definitional data item (here a rule) associated with one of the nodes, say Node C, to cause a work item to be transferred to Node C after the work item has been processed by Node B.
- a proposed definitional data item here a rule
- access and processing control is made robust by allowing the organization to establish such control at a time when the organization is setting up (i.e., defining) a workflow system for manipulating work items, as opposed to checking each such work item at a subsequent time when such work items are progressing through the system.
- definitional data items may include information about a node, i.e., an "ASSOCIATED NODE".
- definitional data item 56 has as an ASSOCIATED NODE, Node A.
- the system stores a repertoire of nodes 52 1 -52 n available for use in processing the work item.
- each one of the nodes 52 1 -52 n may, for example, correspond to a step in a process.
- nodes 52 1 -52 12 correspond to Nodes A-L, respectively, as indicated.
- exemplary process 58 !
- the sequence of process steps is Node A (i.e., node 52 followed by Node B (i.e., node 52 2 ) followed by Node C (i.e., node 52 x ) .
- the process steps are Node B (i.e., node 52 2 ) followed by Node A (i.e., node 52 x ) followed by Node I (i.e., node 52 12 ) .
- Node B may be used in more than one process.
- the process follows Nodes E, F and C, sequentially; Node C also being used in process 58 ⁇
- the operator is able to use the nodes 52 1 -52 n in one of the processes 58 1 -58 3 only if the operators data structure 50 (FIG. 7) associates the operator with the same identifier (ORG ID) that is associated with the nodes 52 1 -52 n in a nodes data structure 60 stored in another memory section 175 (FIG. 6) . It is noted in comparing the node data structure 60 (FIG. 6) with FIG. 8, that the node data structure 60 is constructed to replicate the organizational relationship shown in FIG. 8.
- nodes data structure 60 associates node E with the first identifier 44 (ORG ID "1"), here identifying Division DIVl 42 (FIG. 8)
- node E is possible only if the operators data structure 50 (FIG. 7) associates the operator with the first identifier ORG ID "1" DIVl 42.
- FIG. 7 such use is possible in the cases of operators "Adminl” and "Operl".
- operator 02 being in DIV2 46 cannot be associated with, or perform a process step represented by, any one of the Nodes A- I in DIVl 42. Rather, such operator 02, being in DIV2 46, can be associated with Nodes J, K, and/or L.
- the definitional data item may include a rule, such as rule 56 (Fig. 6) which specifies a display characteristic (not shown) for the work item 10.
- the work item 10 may involve a new account application and may have various fields providing information such as an amount of money involved, an account number, a name of an accountholder, an indicator of the work item's status, and a due date. If so, the rule 56 may specify that the account number and the name of accountholder should be displayed on a display screen 62 of the operator's computer station 12 in accordance with a predefined set of codes.
- Rule 56 being associated with ORG ID "1" is not able to be used to display the work item 10 to the operator unless the operators data structure 50 associates the operator with the same identifier that is associated with the rule 56 (i.e., only if the operator is in ORG ID "1", DIVl 42).
- the rules data structure 48 associates the rule 56 with the ORG ID "1" 44 associated with the first sub-organization (DIVl) 42 (FIG. 5)
- the operator is able to view the work item 10 on the screen 62 of the operator's computer station 12 only if the operators data structure 50 associates the operator with the ORG ID "1" DIVl 44 identifier. Again, such an association exists in the cases of operators "Adminl" and "Operl".
- the definitional data item includes other information, either in addition to or instead of node or rule information.
- the other information may include, e.g., information about a characteristic of a queue (not shown) associated with one of the nodes 52 1 -52 n .
- the queue is used to keep track of work items 10 that are appropriate for execution in connection with the one of the nodes 52 1 -52 n . For example, if Node J 52 10 represents a department responsible for approving purchase orders, the queue may be associated with Node J 52 10 and may keep a list of purchase order work items awaiting approval by the department.
- the other information may include information about one or more setup components (not shown) including but not limited to item- type codes, status codes, and value groups.
- Each setup component is used by an administrator (not shown) of the workflow system to define how operators may interact with a displayed work item 10.
- the administrator may specify six status codes (including, e.g., "SUBMITTED”, “IN PROGRESS”, “AWAITING APPROVAL” , “APPROVAL DENIED”, “APPROVAL GRANTED”, and “COMPLETED") for indicating the progress of one of the work items 10 in the workflow system, but may also specify using one of the value groups to restrict one of the operators to selecting from among only three of the six.
- access control is provided not only between the sub- organizations 42, 46 as described above but also within each of the first and second sub-organizations 42, 46.
- the work item 10 is stored in the database 14 (step 400) .
- the memory section 175 (FIG. 6) stores information (such as the nodes data structure 60) defining the nodes 52 and the memory section 73 stores a programmed data structure (such as the structure 65) defining an organizational relationship between a first one of the nodes 52 and a second one of the nodes 52 (step 410) .
- This programmed data structure is then used to provide the organizational relationship between the nodes 52 to control access to, and processing of, the work item 10 by one of the operators (step 420) .
- the operator is associated with one of the nodes 52 1 -52 n .
- the operator is associated with one of the nodes 52 1 -52 n .
- Node E 52 5 corresponds to one of the steps, here the step associated with node 52 4 (specifically "E") in one of the processes 58, here process 58 3 for manipulating work items 10.
- the definitional data item (such as a rule) discussed above is associated not only with one of the sub-organizations 42, 46 but also with one of the nodes 52 1 -52 n .
- rule "Rulel” is associated with node A.
- the definitional data item may include a rule specifying a display characteristic for the work item 10, information about a characteristic of the operator, or other information, including information about a characteristic of a queue associated with the first one of the nodes 52 x - 52 n .
- the organization hierarchy data structure 64 stores the tree data structure 65 having tree entries 66A-I (step 500) .
- the tree data structure 65 corresponds to the first sub-organization 42.
- the sub-organization 42 is organized hierarchally and each tree entry 66A-I corresponds to one of the nodes A-I 52 1 -52 9 in the first sub-organization 42.
- the process table 69 specifies a sequence of steps (E-F-C) 54 7 _ 9 in one of the processes 58 3 (step 510) .
- Also stored is the new account approval rule 68 associated with node B 52 2 (step 520) .
- the new account approval rule 68 defines how a new account approval item (not shown) is displayed on the operator's screen 62.
- Node B 52 2 corresponds to tree entry 66B.
- entry 66B defines a subset 70 of the tree entries 66A-66I in the tree data structure 65.
- the subset 70 consists of entry 66B and all the tree entries dependent on entry 66B (i.e., entries 66E, 66F) .
- FIG. 8 shows how the subset 70 corresponds to a portion of DIVl.
- a request is received to store a proposed new rule 72 (step 530) .
- the rule "Rulel" 56 defines how a new account application work item is handled at node E. Executed only if the new account application work item is complete, the proposed new rule 72 is configured to transfer the new account application work item from node E to node F and also to provide the new account approval work item to node F. Such a transfer is intended to allow another operator (not shown) to review the complete new account application and fill out the new account approval work item. Thus, the new rule relies on the new account approval rule 68 and corresponds to step F in the process 58 3 .
- the new rule 72 is configured for transferring information to node F
- the new rule 72 is associated with node F, which corresponds to entry 66F in the tree data structure 65. It is determined whether entry 66F belongs to the subset 70 (step 540) . In fact, entry 66F does belong to the subset 70, producing a positive outcome. Based on the positive outcome of the determination, the new rule 72 is stored (step 550) .
- Another request is received, involving a proposed rule "Rule4" 74.
- the proposed rule 74 is associated with node C and is intended to transfer the new account application to node C if the other operator indicates approval in the new account approval work item.
- the proposed rule 74 also relies on the new account approval rule 68, which relates as described above to the subset 70 including entries 66B, 66E, and 66F.
- the proposed rule 74 will not be stored, because the proposed rule is associated with node C which corresponds to entry 66C which is not included in the subset 70.
- To allow the proposed rule 74 to be stored at least one of two changes must be made.
- the proposed rule 74 is changed to cause the new account application to be transferred not to node C but instead to one of the nodes 52 1 -52 n , here node B 52 2 , E 52 5 , or F 52 6 , corresponding to one of the entries 66B, 66E, or 66F in the subset 70.
- This first change allows the proposed rule 74 to be associated with such a node B 52 2 , E 52 5 , or F 52 6 .
- the subset 70 is replaced with a larger subset that includes entry 66C.
- the larger subset is defined by entry 66A and in fact includes the entire first sub-organization 42 (DIVl) .
- the new account approval rule 68 is associated in the memory section 39 with node A instead of node B.
- each of the memory sections may represent a memory section being physically separate from the others or may represent a logical section of an overall memory (i.e., all memory storage) of the computer system 16.
- each of the memory sections 37, 39, 41, 175 may be made up of any type of data storage media and in fact may be made up of more than one type of data storage media, including volatile data storage media and nonvolatile data storage media.
- Such data storage media types include but are not limited to semiconductor memory (e.g., dynamic RAM, static RAM), magnetic memory (e.g., magnetic tape, hard disk, floppy disk) , optical memory (e.g., CD-ROM), and magneto-optical memory (e.g., writable optical disk) .
- semiconductor memory e.g., dynamic RAM, static RAM
- magnetic memory e.g., magnetic tape, hard disk, floppy disk
- optical memory e.g., CD-ROM
- magneto-optical memory e.g., writable optical disk
- the technique may be implemented in hardware or software, or a combination of both.
- the technique is implemented in computer programs executing on programmable computers that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements) , at least one input device, and at least one output device.
- Program code is applied to data entered using the input device to perform the method described above and to generate output information.
- the output information is applied to one or more output devices.
- Each program is preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system.
- the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language.
- Each such computer program is preferably stored on a storage medium or device (e.g., ROM or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform the procedures described in this document.
- the system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner.
- one of the sub- organizations 42, 44 may not be simply hierarchal but may instead be matrix-oriented so that at least of the nodes 52 is directly dependent from multiple others of the nodes 52.
- whether the operator has access to the definitional data item or is affected by the definitional data item may depend not on whether one of a nodes 52 1 -52 n corresponds to one of entries 66B, 66E, or 66F belonging to the subset 70. Instead, such access may depend on a horizontal position of one of the nodes 52.
- such horizontal positioning divides the nodes 52 into three categories: (1) node A, (2) nodes B, C, D, and (3) nodes E, F, G, H, I.
- whether the operator has access to a particular definitional data item or is affected by the particular definitional data item may depend on whether the operator and the particular definitional data item are associated with the same category.
- the networked data structure may not be a tree data structure but may instead be another type of data structure reflective of nodes organized other than as the hierarchy described above .
- the identifiers are not limited to use in logically separating the workflows of multiple sub-organizations of the same organization as described above.
- the identifiers may also be used for logically separating the workflows of multiple fully-independent organizations. For example, using the identifiers, a workflow services business may use a single work item database supported by a single computer system to manage the workflows of multiple companies even though these companies are not commonly owned and are in fact completely unrelated to each other.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP97954193A EP1008076A4 (en) | 1996-12-18 | 1997-12-18 | Computer executable workflow control system |
AU58035/98A AU5803598A (en) | 1996-12-18 | 1997-12-18 | Computer executable workflow control system |
JP52800898A JP2001506386A (en) | 1996-12-18 | 1997-12-18 | Computer-executable workflow control system |
CA002275399A CA2275399C (en) | 1996-12-18 | 1997-12-18 | Computer executable workflow control system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/769,503 US6006193A (en) | 1996-12-18 | 1996-12-18 | Computer executable workflow control system |
US08/769,503 | 1996-12-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1998027500A1 true WO1998027500A1 (en) | 1998-06-25 |
Family
ID=25085640
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1997/023600 WO1998027500A1 (en) | 1996-12-18 | 1997-12-18 | Computer executable workflow control system |
Country Status (7)
Country | Link |
---|---|
US (1) | US6006193A (en) |
EP (1) | EP1008076A4 (en) |
JP (4) | JP2001506386A (en) |
AU (1) | AU5803598A (en) |
CA (1) | CA2275399C (en) |
NZ (1) | NZ336796A (en) |
WO (1) | WO1998027500A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6795071B2 (en) | 1999-12-03 | 2004-09-21 | Dcs, Inc. | Method of managing workflow information |
Families Citing this family (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6058380A (en) * | 1995-12-08 | 2000-05-02 | Mellon Bank, N.A. | System and method for electronically processing invoice information |
SE9603304D0 (en) * | 1996-09-11 | 1996-09-11 | Pharmacia & Upjohn Ab | Process for purifying a compound |
US6256651B1 (en) * | 1997-06-20 | 2001-07-03 | Raja Tuli | Time management workflow software |
US6338074B1 (en) * | 1997-07-23 | 2002-01-08 | Filenet Corporation | System for enterprise-wide work flow automation |
JP3624657B2 (en) * | 1997-11-07 | 2005-03-02 | 株式会社日立製作所 | Management computer or computer system |
US7155498B1 (en) | 1997-11-07 | 2006-12-26 | Hitachi, Ltd. | Computer operation management system |
US6119149A (en) * | 1998-06-05 | 2000-09-12 | I2 Technologies, Inc. | System and process allowing collaboration within and between enterprises for optimal decision making |
CA2337847A1 (en) * | 1998-07-17 | 2000-01-27 | Starkey International | Facility management system |
US6278988B1 (en) * | 1998-11-12 | 2001-08-21 | Pitney Bowes Inc. | Multiple job entry points for document production control and reporting |
IE20000336A1 (en) * | 1999-06-30 | 2001-03-21 | Phoenix Technology Patent Dev | A work flow management system |
US6952741B1 (en) * | 1999-06-30 | 2005-10-04 | Computer Sciences Corporation | System and method for synchronizing copies of data in a computer system |
US6728590B1 (en) | 1999-07-14 | 2004-04-27 | Nec Electronics, Inc. | Identifying wafer fabrication system impacts resulting from specified actions |
US6766212B1 (en) * | 1999-07-14 | 2004-07-20 | Nec Electronics, Inc. | Identifying relationships among constituent parts of a wafer fabrication system |
US7693844B1 (en) * | 1999-10-29 | 2010-04-06 | Computer Sciences Corporation | Configuring processing relationships among entities of an organization |
US8606588B1 (en) | 1999-11-23 | 2013-12-10 | Accenture Global Services Limited | Merger and acquisition knowledgebase |
US6581039B2 (en) * | 1999-11-23 | 2003-06-17 | Accenture Llp | Report searching in a merger and acquisition environment |
US6671692B1 (en) | 1999-11-23 | 2003-12-30 | Accenture Llp | System for facilitating the navigation of data |
US6671693B1 (en) | 1999-11-23 | 2003-12-30 | Accenture Llp | System for effectively collecting and disseminating data |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7401131B2 (en) * | 2000-05-22 | 2008-07-15 | Verizon Business Global Llc | Method and system for implementing improved containers in a global ecosystem of interrelated services |
US7096222B2 (en) * | 2000-09-01 | 2006-08-22 | Borland Software Corporation | Methods and systems for auto-instantiation of storage hierarchy for project plan |
WO2002029682A1 (en) * | 2000-10-02 | 2002-04-11 | International Projects Consultancy Services, Inc. | Object-based workflow system and method |
US7653566B2 (en) * | 2000-11-30 | 2010-01-26 | Handysoft Global Corporation | Systems and methods for automating a process of business decision making and workflow |
US6892376B2 (en) * | 2001-03-20 | 2005-05-10 | International Business Machines Corporation | Flexible infrastructure for managing a process |
US7100147B2 (en) * | 2001-06-28 | 2006-08-29 | International Business Machines Corporation | Method, system, and program for generating a workflow |
US7069536B2 (en) * | 2001-06-28 | 2006-06-27 | International Business Machines Corporation | Method, system, and program for executing a workflow |
US7043714B2 (en) * | 2001-06-28 | 2006-05-09 | International Business Machines Corporation | Method, system, and program for using objects in data stores during execution of a workflow |
US7047535B2 (en) | 2001-07-30 | 2006-05-16 | International Business Machines Corporation | Method, system, and program for performing workflow related operations using an application programming interface |
US7296056B2 (en) * | 2001-07-30 | 2007-11-13 | International Business Machines Corporation | Method, system, and program for selecting one user to assign a work item in a workflow |
US7698427B2 (en) | 2001-07-30 | 2010-04-13 | International Business Machines Corporation | Method, system, and program for transferring data from an application engine |
US7228547B2 (en) * | 2001-07-30 | 2007-06-05 | International Business Machines Corporation | Method, system, and program for enabling access to a plurality of services |
GB2390446A (en) * | 2002-07-02 | 2004-01-07 | Hewlett Packard Co | Apparatus for analysing electronic representations of business processes |
US7653562B2 (en) * | 2002-07-31 | 2010-01-26 | Sap Aktiengesellschaft | Workflow management architecture |
US7805327B1 (en) * | 2002-07-31 | 2010-09-28 | Sap Aktiengesellschaft | Transformations between combined and individual workflows |
US6819965B2 (en) | 2002-09-09 | 2004-11-16 | Kimball International, Inc. | Electronic work instruction object oriented system and method |
US7769645B1 (en) | 2002-11-25 | 2010-08-03 | Xcm Development, Llc | Tax return outsourcing and systems for protecting data |
US7171664B2 (en) * | 2002-12-16 | 2007-01-30 | International Business Machines Corporation | Content management system and method of employing extensible workflow entities with user-defined attributes in an object-oriented framework |
CA2527897C (en) * | 2003-06-04 | 2020-12-22 | Fair Isaac Corporation | Relational logic management system |
US8239233B1 (en) | 2003-07-17 | 2012-08-07 | Xcm Development, Llc | Work flow systems and processes for outsourced financial services |
US20050055583A1 (en) * | 2003-09-05 | 2005-03-10 | Matsushita Electric Industrial Co., Ltd. | Data management apparatus, data management method and program thereof |
US8650152B2 (en) * | 2004-05-28 | 2014-02-11 | International Business Machines Corporation | Method and system for managing execution of data driven workflows |
US20070011234A1 (en) * | 2004-07-29 | 2007-01-11 | Xcm Development, Llc | Computer conferencing system and features |
US8554599B2 (en) * | 2005-03-25 | 2013-10-08 | Microsoft Corporation | Work item rules for a work item tracking system |
US8126760B2 (en) * | 2005-03-25 | 2012-02-28 | Microsoft Corporation | Work item tracking system for projects |
US8073724B2 (en) * | 2005-12-02 | 2011-12-06 | Saudi Arabian Oil Company | Systems program product, and methods for organization realignment |
US20070192379A1 (en) * | 2006-01-27 | 2007-08-16 | William Derek Finley | Method of analyzing information flow within an organization |
WO2007132547A1 (en) * | 2006-05-16 | 2007-11-22 | Fujitsu Limited | Job model generation program, job model generation method, and job model generation device |
US7765476B2 (en) * | 2006-08-28 | 2010-07-27 | Hamilton Sundstrand Corporation | Flexible workflow tool including multi-lingual support |
US8683490B2 (en) * | 2007-02-15 | 2014-03-25 | Microsoft Corporation | Computer system events interface |
US8271998B2 (en) * | 2007-04-27 | 2012-09-18 | International Business Machines Corporation | Dynamic discovery and definition of mappings of parameters used by service oriented architecture services at runtime |
EP2073155A1 (en) * | 2007-12-20 | 2009-06-24 | Siemens Aktiengesellschaft | Controlling the re-execution of a rule branch |
US20090182607A1 (en) * | 2008-01-16 | 2009-07-16 | Morinville Paul V | Approver Identification Using Multiple Hierarchical Role Structures |
US8676627B2 (en) * | 2008-12-04 | 2014-03-18 | International Business Machines Corporation | Vertical process merging by reconstruction of equivalent models and hierarchical process merging |
US9963954B2 (en) | 2012-11-16 | 2018-05-08 | Saudi Arabian Oil Company | Caliper steerable tool for lateral sensing and accessing |
US10402295B1 (en) * | 2013-05-31 | 2019-09-03 | Staples, Inc. | Automated determination, notification, and acquisition of peripheral-related items |
US20150254679A1 (en) * | 2014-03-07 | 2015-09-10 | Genesys Telecommunications Laboratories, Inc. | Vendor relationship management for contact centers |
US10133996B2 (en) * | 2014-04-22 | 2018-11-20 | International Business Machines Corporation | Object lifecycle analysis tool |
US20160034516A1 (en) * | 2014-07-29 | 2016-02-04 | Corporate Data Design, Inc. | Method and system for analysis of an object |
JP6202653B1 (en) * | 2016-12-27 | 2017-09-27 | 株式会社ビー・キューブ | Computer system, management method and program |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301320A (en) * | 1991-06-28 | 1994-04-05 | Digital Equipment Corporation | Workflow management and control system |
US5319543A (en) * | 1992-06-19 | 1994-06-07 | First Data Health Services Corporation | Workflow server for medical records imaging and tracking system |
US5319777A (en) * | 1990-10-16 | 1994-06-07 | Sinper Corporation | System and method for storing and retrieving information from a multidimensional array |
US5535322A (en) * | 1992-10-27 | 1996-07-09 | International Business Machines Corporation | Data processing system with improved work flow system and method |
US5630069A (en) * | 1993-01-15 | 1997-05-13 | Action Technologies, Inc. | Method and apparatus for creating workflow maps of business processes |
US5706452A (en) * | 1995-12-06 | 1998-01-06 | Ivanov; Vladimir I. | Method and apparatus for structuring and managing the participatory evaluation of documents by a plurality of reviewers |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5208748A (en) * | 1985-11-18 | 1993-05-04 | Action Technologies, Inc. | Method and apparatus for structuring and managing human communications by explicitly defining the types of communications permitted between participants |
US5182705A (en) * | 1989-08-11 | 1993-01-26 | Itt Corporation | Computer system and method for work management |
US5168444A (en) * | 1989-11-15 | 1992-12-01 | Teknekron Transportation Systems | Shipment system including processing of document images |
US5191525A (en) * | 1990-01-16 | 1993-03-02 | Digital Image Systems, Corporation | System and method for extraction of data from documents for subsequent processing |
US5191522A (en) * | 1990-01-18 | 1993-03-02 | Itt Corporation | Integrated group insurance information processing and reporting system based upon an enterprise-wide data structure |
US5446740A (en) * | 1993-12-17 | 1995-08-29 | Empire Blue Cross/Blue Shield | Method of and apparatus for processing data at a remote workstation |
EP0697662B1 (en) * | 1994-08-15 | 2001-05-30 | International Business Machines Corporation | Method and system for advanced role-based access control in distributed and centralized computer systems |
-
1996
- 1996-12-18 US US08/769,503 patent/US6006193A/en not_active Expired - Lifetime
-
1997
- 1997-12-18 EP EP97954193A patent/EP1008076A4/en not_active Ceased
- 1997-12-18 WO PCT/US1997/023600 patent/WO1998027500A1/en active Application Filing
- 1997-12-18 NZ NZ336796A patent/NZ336796A/en not_active IP Right Cessation
- 1997-12-18 CA CA002275399A patent/CA2275399C/en not_active Expired - Lifetime
- 1997-12-18 JP JP52800898A patent/JP2001506386A/en active Pending
- 1997-12-18 AU AU58035/98A patent/AU5803598A/en not_active Abandoned
-
2008
- 2008-04-09 JP JP2008101821A patent/JP2008186478A/en active Pending
-
2009
- 2009-06-08 JP JP2009137060A patent/JP5113119B2/en not_active Expired - Lifetime
-
2011
- 2011-06-15 JP JP2011133444A patent/JP2011175683A/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5319777A (en) * | 1990-10-16 | 1994-06-07 | Sinper Corporation | System and method for storing and retrieving information from a multidimensional array |
US5301320A (en) * | 1991-06-28 | 1994-04-05 | Digital Equipment Corporation | Workflow management and control system |
US5319543A (en) * | 1992-06-19 | 1994-06-07 | First Data Health Services Corporation | Workflow server for medical records imaging and tracking system |
US5535322A (en) * | 1992-10-27 | 1996-07-09 | International Business Machines Corporation | Data processing system with improved work flow system and method |
US5630069A (en) * | 1993-01-15 | 1997-05-13 | Action Technologies, Inc. | Method and apparatus for creating workflow maps of business processes |
US5706452A (en) * | 1995-12-06 | 1998-01-06 | Ivanov; Vladimir I. | Method and apparatus for structuring and managing the participatory evaluation of documents by a plurality of reviewers |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6795071B2 (en) | 1999-12-03 | 2004-09-21 | Dcs, Inc. | Method of managing workflow information |
US6798413B1 (en) | 1999-12-03 | 2004-09-28 | Dcs, Inc. | Workflow management system |
Also Published As
Publication number | Publication date |
---|---|
JP5113119B2 (en) | 2013-01-09 |
AU5803598A (en) | 1998-07-15 |
CA2275399C (en) | 2009-12-29 |
US6006193A (en) | 1999-12-21 |
JP2009230762A (en) | 2009-10-08 |
JP2011175683A (en) | 2011-09-08 |
JP2008186478A (en) | 2008-08-14 |
EP1008076A4 (en) | 2004-03-17 |
NZ336796A (en) | 2001-03-30 |
EP1008076A1 (en) | 2000-06-14 |
CA2275399A1 (en) | 1998-06-25 |
JP2001506386A (en) | 2001-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6006193A (en) | Computer executable workflow control system | |
AU2001249273B2 (en) | Method and system for top-down business process definition and execution | |
US6151583A (en) | Workflow management method and apparatus | |
CA2275279C (en) | Computer executable workflow resource management system | |
US7096222B2 (en) | Methods and systems for auto-instantiation of storage hierarchy for project plan | |
US7043714B2 (en) | Method, system, and program for using objects in data stores during execution of a workflow | |
US20050027582A1 (en) | Project modelling and management tool | |
AU2001249273A1 (en) | Method and system for top-down business process definition and execution | |
US20030195789A1 (en) | Method for incorporating human-based activities in business process models | |
US8805919B1 (en) | Multi-hierarchical reporting methodology | |
WO2003010700A2 (en) | Method and tool for achieving data consistency in an enterprise resource planning system | |
EP0774725A2 (en) | Method and apparatus for distributing conditional work flow processes among a plurality of users | |
US20080077466A1 (en) | System and method of providing snapshot to support approval of workflow changes | |
EP0793184A2 (en) | Method and apparatus for distributing work flow processes among a plurality of users | |
US7302483B1 (en) | Job analysis and workflow application | |
Talapov et al. | The leading role of the customer in the organization of the information modeling process | |
US8943034B2 (en) | Data change management through use of a change control manager | |
US20020087439A1 (en) | Method and system for electronically qualifying supplier parts | |
AU3817802A (en) | Computer executable workflow control system | |
JP3667230B2 (en) | Workflow management control device | |
JP2004054557A (en) | Application/retrieval system and method for customize allowance and its program | |
IES20030700A2 (en) | Transaction processing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AU CA CN JP KR MX NZ AM AZ BY KG KZ MD RU TJ TM |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 58035/98 Country of ref document: AU |
|
ENP | Entry into the national phase |
Ref document number: 2275399 Country of ref document: CA Kind code of ref document: A Ref document number: 2275399 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 1998 528008 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 1997954193 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1997954193 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 336796 Country of ref document: NZ |
|
WWP | Wipo information: published in national office |
Ref document number: 1997954193 Country of ref document: EP |