TWI476709B - Work flow management system and method - Google Patents

Description

Work flow management system and method

The present invention relates to a workflow management system and method, and more particularly to a workflow management system and method for managing the transfer of a work flow object within an organizational structure.

In the case of a medium and large enterprise group, the speed of the company's scale and the rapid increase of process complexity, electronic document signing and delivery systems need to have accurate and rapid response capabilities.

The current business process management, administrative process planners and technical department process designers cannot be combined. Daily complex and error-prone process clusters, when each organization or individual needs are raised (such as document disclosure, requisition, signing, survey statistics, and even leave signing, etc.), in personal intent, authority, events, and objects , sorting, statute and path logic layout need to be re-set. In the complicated and large-scale re-assembly process, not only the relevant personnel need to invest a lot of manpower, but the excessive load often causes work delays, serious mistakes, and low efficiency of business operations. Significant losses caused by high risks.

As a result, the huge risks of cumbersome, messy assembly and manual intervention of the company's daily processes need to be improved.

One of the objects of the present invention is to make any node in the organizational structure not be limited to a fixed path, and the system can dynamically capture the nodes to be included in the path point according to the set path when the object is delivered.

Another object of the present invention is to clarify and simplify the nodes and their relationships in the workflow structure to achieve intelligent process automation of central control, dynamic capture, and rapid branch extension.

In order to achieve the above and other objects, the present invention provides an operational process management system for use in For managing a transfer process of an operational process object in an organizational structure, the operational process management system includes: a metadata database for storing data of each node in the organizational structure and for storing and operating between the nodes At least one work flow template, each work flow template has a plurality of path points, each path point has at least one node, each work flow template defines a group of data to which each node belongs; an input module, Receiving the work flow object; and an authorization engine connecting the metadata data library and the input module, the authorization engine comprising: a work flow template selection unit for using the at least one job The process template generates a main process path for running the work flow object between the route points; and a work flow expansion unit is coupled to the work flow template selection unit for responding according to the feedback of the nodes in each path point The node that is fed back expands a process to the higher order according to the restriction of the group data to which it belongs and its node data. Diameter, to run the workflow object, and a sub flow path after the return to the main flow path is completed.

In order to achieve the above and other objects, the present invention further provides a workflow management method for generating a workflow path of a work flow object, comprising the following steps: A. selecting a work flow template corresponding to the work flow object; Running the work flow object according to each path point of the main process path of the work flow template; C, when the path point of the main flow path has a plurality of nodes of the same level, in the group to which the first feedback node belongs, According to the order data of the feedback node, a process path is extended to the high order direction; and D, the work flow object is run according to the sub-process path, and after the operation is completed, returning to step B to continue to run the next path point, wherein The operation flow template is to specify a sequence rule between the plurality of nodes in the operation of the operation process object, the work flow template has a plurality of path points, each path point has at least one node, and each operation flow template defines each node to belong to a group of information.

In an embodiment, the method further includes: a field setting unit, configured to connect the metadata database, and configured to set a level order data between the nodes, the field setting unit includes: a first field setting unit, For setting an organization structure serial number value of each node in an organizational structure; a second field setting unit is configured to set a node serial number value of each node in the organizational structure; The three-column setting unit is configured to set a pre-stage node number value according to the previous order information of each node in the organization structure; the fourth field setting unit is used to attach each node to other nodes. According to the attached node, a dependent node serial number value is set; the fifth field setting unit is configured to set an inheritance node serial number value according to the serial number value of the inherited node when each of the node nodes inherits other nodes; And a sixth field setting unit for setting the name of each of the nodes.

In this way, with the help of the model of the 預鑄 and the control mechanism of the group data, the static node data has dynamic expansion flexibility, which not only has a high degree of reorganization and extension in the process, but also can be more important in mergers and acquisitions and enterprises. It is better to play a better role in organizational change such as merge and acquisition, regulation, and new establishment. This is also the effect of model reusability and process application scalability.

In order to fully understand the objects, features and advantages of the present invention, the present invention will be described in detail by the following specific embodiments and the accompanying drawings.

First, please refer to Fig. 1, which is a functional block diagram of a work flow management system in an embodiment of the present invention. In the embodiment of the present invention, a transfer program for managing a work flow object in an organizational structure includes: a metadata database 130, an input module 110, and an authorization engine 120. The organizational structure can be the existing class structure of the client, for example, the hierarchical relationship between departments, the hierarchical relationship between positions, or the hierarchical relationship between different company organizations, and the organizational structure can be constructed by a tree structure. The input module 110 can be connected to other computers through an input interface (eg, a network interface) in the computer device to receive the work flow object. The authorization engine 120 can be a storage medium in the computer device, and store an application that can perform the corresponding function action.

The metadata database 130 is used to store data of each node in the organizational structure, such as storage media in a computer device. Each link in the organizational structure can be viewed as a node, such as an employee, supervisor, etc., and the node information is in a further embodiment. It can include: department information, job information, work flow template design information, and work flow template entity data.

The metadata database 130 can be used to store at least one workflow model running between the nodes. Each workflow template has multiple path points, and each path point can include at least one node, and each operation flow template is Define a group of data to which each node belongs. That is, when the work flow object runs according to the specification of the work flow template at each route point, at least one pair of paths can be expanded based on the node of the route point and the group to which the node belongs.

The input module 110 is configured to receive the work flow object.

The authorization engine 120 is coupled to the metadata database 130 and the input module 110. The authorization engine 120 includes a workflow template selection unit 122 and a workflow extension unit 124.

The workflow template selection unit 122 is configured to generate a main flow path between the path points according to the at least one work flow template.

The job flow expansion unit 124 links the work flow template selection unit 122 to run the work flow object and is used to return to the main flow path after the completion of the sub-process path.

When the work flow object enters a route point having only a single node, the work flow expansion unit 124 according to the feedback of the single node, for example, the signing of the work flow object, according to the limitation of the group data to which the single node belongs The node data expands a process path to the high-order direction, that is, the work process template can limit the highest level of operation of the work flow object in the sub-process path by the limitation of the group data, and The node sequence of the single node is used to bring out the sequence of each node when the sub-process path is running.

On the other hand, when the workflow object enters a path point having a plurality of nodes, the workflow extension unit 124 is based on the node that is first fed back, according to the section of the first feedback. The restriction of the group data to which the point belongs and the node data thereof, as described above, expand a flow path to the higher order. Therefore, in the embodiment of the present invention, a plurality of sub-process paths can be dynamically set, and the sub-process path is dynamically selected according to the node that is first fed back. At the same time, when a node with feedback is generated, the feedback of the remaining nodes will no longer be valid, and even can be set to no longer feedback. For example, when a supervisor has signed a file, it is located at the same level. Although another supervisor has received the notice of the document to be signed, the other supervisor has been unable to sign the document.

Next, please refer to FIG. 2, which is a schematic flowchart of a workflow management method according to an embodiment of the present invention. The workflow management method in an embodiment of the present invention can be run on the foregoing system, and the method includes the following steps: A: selecting a work flow template corresponding to the work flow object; B, according to the main flow path of the work flow template Each path point runs the work flow object; C, according to the order data of the feedback node, expands a flow path to the high order direction, wherein when the path point has a plurality of nodes of the same level, performing the C1 step, when the path When the node does not have a node with the same level, the C2 step is performed to expand the corresponding sub-process path; and D, the operation flow object is run according to the sub-process path, and step D1 is performed to determine whether all the path points are After the operation is completed, return to step B and continue to run the next path point when the operation is not completed.

Wherein, the workflow process specification is a sequence rule between the plurality of nodes in the operation of the operation process object, the work flow template has a plurality of path points, each path point has at least one node, and each operation flow template defines each node A group of materials to which it belongs.

Accordingly, in the embodiment of the present invention, the definition of each path point in the work flow template, the setting of the node of each path point, and the group data in the work flow template are used. Set as a kind of model, so that the traditional workflow can be flexibly modified and focused on assembly, without having to re-engineer a workflow or spend a considerable amount of time to modify the process path points one by one to achieve central control and dynamics. Intelligent process automation design with interception and rapid expansion of the sub-process path.

In addition, in a further embodiment, the field setting unit 132 may be further included. The field setting unit 132 is coupled to the metadata database 130 and includes: first to six field setting units. These field setting units are only one embodiment for implementing the foregoing systems and methods, and other field setting rules may also be applied to the systems and methods of the foregoing embodiments.

The first field setting unit is configured to set an organization structure serial number value of each node in an organizational structure; the second field setting unit is configured to set a node serial number value of each node in the organizational structure; The three-column setting unit is configured to set a pre-stage node number value according to the previous order information of each node in the organization structure; the fourth field setting unit is used to attach each node to other nodes according to The attached node sets an attached node serial number value; the fifth field setting unit is configured to set an inheritance node serial number value according to the serial number value of the inherited node when each of the node nodes inherits other nodes; and sixth The field setting unit is used to set the name of each of these nodes.

The field data structure used in the embodiment of the present invention can be used when the information of any node in the data structure is changed, for example, a supervisor leaves the job, and the node information is updated correspondingly, so that the transferred work flow object can be correctly operated.

In the embodiment, the node data may include department information, job information, operation process template design data, and operation process template entity data.

When the node data includes department information, the first field setting unit is configured to designate the same organizational structure as the same classification and set the same classification serial number; the second field setting unit is used for the node The serial number value is specified as a department serial number. The third field setting unit is configured to designate the previous information as the superior department of the department and set the department serial number of the upper department to be the previous node number value; the fourth field setting unit is And the fifth column setting unit is configured to specify the external system serial number value as the inheritance when the department information is imported by the external system. The node number value; and the sixth field setting unit is used to set the node name of the department information as the department name.

For example, when the node data contains departmental information, the relationship between the department and the department can be recorded. Each field data corresponds to each field setting unit, as shown in Table 1 below:

Please also match the departmental structure relationship diagram represented by the node data in Figure 3. When the node data contains job information, the first field setting unit is used to designate the same organizational structure as the same classification and set the same classification. a serial number value; the second field setting unit is configured to specify the node serial number value as a job serial number value; the third field setting unit is configured to designate the previous order information as the position of the job direct supervisor and set The job number of the directly-administrated supervisor has the value of the previous-stage node number, and the third-field setting unit does not specify the previous-stage node number value when the position is the highest-level supervisor position; the fourth field setting The unit is configured to set the department serial number of the department to which the job belongs according to the department information to the attached node serial number; and the fifth field setting unit is configured to specify the external information when the job information is imported by the external system. The serial number of the part system is the serial number of the inherited node; and the sixth field setting unit is used to set the node name of the job information as the job title.

For example, when the node data contains job information, the relationship between the position and the position can be recorded. Each field data corresponds to each field setting unit, as shown in Table 2 below:

Please also match the job structure relationship diagram represented by the node data in Figure 4, when the node data contains the workflow design information, the first field setting unit is used to designate the same path process as the same group data and Setting the same group serial number value; the second field setting unit is used to set a node serial number value of each node in the organizational structure; the third field setting unit is used under the organizational structure, according to each a node prior information, setting a previous node number value; the fourth field setting unit is configured to set the dependency node number according to the attached main process path when the workflow template design data system is a sub-process path Value, the fourth field setting unit is used to not set the dependency node serial number when the workflow template design data is the main process path; the fifth field setting unit is used to design the data system in the workflow template When inheriting department information or job information, the serial number of the inherited node is set to the department serial number value or the job serial number value; and the sixth field setting unit is used to set the name of each of the nodes.

For example, when the data of the nodes includes the design process information of the design period (Info Path-Design), each field data corresponds to each field setting unit, as shown in Table 3 below:

Please also use the design information of the design process including the design period in Figure 5. A schematic diagram of a process path for each field data expansion. When the node data includes entity work flow information, the first field setting unit is configured to designate the same path flow as the same group and set the same group serial value; The second field setting unit is configured to specify the node serial number value as a department serial number value; the third field setting unit is configured to designate the previous order information as a superior department of the department and set the upper department to have The department serial number value is the previous order node serial number value; the fourth field setting unit is configured to set the attached node serial number value according to the attached main flow path when the work flow template entity data system is the secondary flow path. The fourth field setting unit is configured to not set the dependency node serial number value when the workflow process entity data system is the main process path; the fifth field setting unit is used in the operation process template entity data inheritance department When the information, job information, or work flow template design data is set, the serial number of the inherited node is set to the department serial number value, the job serial number value, or the job flow model. Node number value of design information; and the sixth field line setting means for setting the node name in the sector of information for the department name.

Please also use the process path diagram of each field data when the physical operation process information is included in Figure 6. When the node data contains the entity work flow information (Info Path-RunTime), each field data corresponds to each column. The bit setting unit is as shown in Table 4 below:

Accordingly, when the foregoing node data is set for each node via each field setting unit, the actual implementation steps are as follows:

A. Find job flow design information corresponding to the operation process object. That is, look for the information transfer path (Query Info Path-Design) of the workflow design period applicable to the workflow object.

B. Copy the workflow design information into an entity workflow information. That is, the information path design information (Info Path-Design) is copied into the entity path information (Info Path-RunTime), and the field 1 and field 2 will be designed according to the new workflow process during the copying process. (Info Path-Design) Given the new group data and node number, the second field of Info Path-Design is copied to field 5 of the Info Path-RunTime.

C. According to the association between the node stored in the fifth field setting unit and the node in the workflow design information, and the relationship between the second and third field setting units in the workflow design information, the first The relationship between the second and fourth field setting units adjusts the previous node number value and the attached node number value in the third and fourth field setting units in the entity workflow information. That is, according to the relevance of the five nodes in the Info Path-Design, and the relationship between the second and the third in the Info Path-Design. And the relevance of field 2 and field four, adjust the value of field three and column four of Info Path-RunTime to reconstruct a complete data transmission path.

D. Scan the complete data delivery path from the starting point, and repeat steps B and C when inheriting. That is, the complete data transmission path is scanned from the starting point. If it is "inheritance", the above steps B and C should be repeated according to the fields A~D of the node, and the path generated at this time is the entity operation flow information ( Sub processes in Info Path-RunTime). That is, the field 4 with the embedded main delivery path (as root processes) in the entity job flow information is marked as the value of the field 2 of the "inheritance" node, and the node field of the starting point of the complete data transmission path is three , the value of the field 2 marked as the "inheritance" node.

E. When the inheritance flag setting unit is set to the embedded main delivery path (as root processes), all values of the sub-passing path are set, and the inherited node is deleted. That is, if the field D value of the "inherit" node is the embedded main delivery path, then the fourth row of all nodes of the first-order pass path of the sub-passing path completed in step D is marked as the same as the column of the "inheritance" node. Bit four. The node field of the start point of the child transfer path is three, indicating the same field as the "inherit" node, and the third field of the node under the "inherit" node is marked as the same as the field of the end of the child transfer path, and Delete the Inherit node after completion.

F. Perform the transfer of the work flow object. That is, the information transfer is performed when it is passed to the "inherit" node, whether it is the same as when the step D is performed. If it is different, the sub-passing path generated in step D is deleted, and step D is performed again.

Next, please refer to FIG. 7 , which is a schematic diagram of the principle of dynamic self-assembly adopted in the embodiment of the present invention. The “A→B _X3 →C” on the left side of Figure 7 represents the partial path point of the main flow path under a certain process flow template, where “B _X3 ” represents the path point with multiple nodes. The right side of Figure 3 is the expansion of the "B _X3 " path point. It can be seen that the nodes of the same level in the "B _X3 " path point have "B ₁₃ ", "B ₂₃ ", and "B ₃₃ ", that is, All three nodes can perform the sign-off action. Once a node signs the core, other nodes can no longer perform the sign-off action. For example, the node "B ₂₃ " signifies the pass. At this time, the workflow extension unit 124 expands the limit of the group data corresponding to the "B ₂₃ " node and the node data specification according to the feedback "B ₂₃ " node. For the sub-process path, for example: "B ₂₃ → B ₂₂ → B ₂₁ ", after the "B ₂₁ " node is checked, it returns to the main flow path and continues to the next path point "C".

In summary, the tree structure of the “main process path and the branch process path of the branch” in the process is dominated by the process engine, and the data is acquired by using the metadata database and the workflow template database. The overall performance of the next show, and achieve significant effects such as manual savings, reduced error rate, and improved accuracy.

The invention has been described above in terms of the preferred embodiments, and it should be understood by those skilled in the art that the present invention is not intended to limit the scope of the invention. It should be noted that variations and permutations equivalent to those of the embodiments are intended to be included within the scope of the present invention. Therefore, the scope of protection of the present invention is defined by the scope of the patent application.

100‧‧‧Workflow Management System

110‧‧‧Input module

120‧‧‧Authorization Engine

122‧‧‧Workflow process template selection unit

124‧‧‧Workflow expansion unit

130‧‧‧ metadata database

132‧‧‧Field setting unit

A~D, C1, C2, D1‧‧‧ steps

Figure 1 is a functional block diagram of a job flow management system in accordance with an embodiment of the present invention.

FIG. 2 is a schematic flow chart of a workflow management method according to an embodiment of the present invention.

Figure 3 is a diagram showing the department structure relationship represented by the node data in the embodiment of the present invention.

Figure 4 is a diagram showing the job structure relationship represented by the node data in the embodiment of the present invention.

FIG. 5 is a schematic flow chart showing the development of each field data when the design information of the design process is included in the embodiment of the present invention.

FIG. 6 is a schematic flow chart showing the development of each field data when the entity operation flow information is included in the embodiment of the present invention.

Figure 7 is a schematic diagram showing the principle of dynamic self-assembly employed in the embodiment of the present invention.

100‧‧‧Workflow Management System

110‧‧‧Input module

120‧‧‧Authorization Engine

122‧‧‧Workflow process template selection unit

124‧‧‧Workflow expansion unit

130‧‧‧ metadata database

132‧‧‧Field setting unit

Claims (8)

An operation process management system is used for managing a transfer process of an operation process object in an organization structure, the work process management system includes: a metadata database for storing each node data in the organization structure and used for Storing at least one work flow template running between the nodes, each work flow template having a plurality of path points, each path point having at least one node, each work flow template defining a group to which each node belongs An input module for receiving the work flow object; and an authorization engine for linking the metadata database and the input module, the authorization engine comprising: a workflow process template selection unit, configured to The at least one work flow template generates a main flow path for running the work flow object between the route points; and a work flow expansion unit is coupled to the work flow template selection unit for each node according to each path point Feedback, correspondingly the node that is fed back to the higher order according to the limit of the group data to which it belongs and its node data Expanding a process path to run the work flow object and returning to the main flow path after the completion of the sub-process path; wherein, when the path point of the main flow path has a plurality of nodes of the same level, In the group to which the node that is the first feedback is located, according to the order data of the feedback node, the direction to the high order The sub-process path is expanded, and when the node with feedback is generated, the remaining nodes will no longer be valid. The operating process management system of claim 1, further comprising: a field setting unit, configured to link the metadata database, and configured to set the order data between the nodes, the field setting unit The method includes: a first field setting unit, configured to set an organization structure serial number value of each node in an organizational structure; and a second field setting unit, configured to set a node of each node in the organizational structure The third column setting unit is used to set a previous node number value according to the previous order information of each node in the organization structure; the fourth field setting unit is used to attach to each node. When the other nodes are connected, the node number is attached according to the attached node; the fifth field setting unit is used to set an inheritance according to the serial number value of the inherited node when each of the nodes inherits other nodes. The node number value; and the sixth field setting unit are used to set the name of each of the nodes. For example, in the operation process management system described in claim 2, the node data includes a department information, wherein the first field setting unit is used to designate the same organizational structure as the same category. The same category number value is determined; the second field setting unit is configured to specify the node serial number value as a department serial number value; the third field setting unit is configured to designate the previous order information as the superior of the department. The department further sets the department serial number of the superior department to be the previous node serial number value; the fourth field setting unit is configured to set the attached node serial number value according to the department serial number value of the superior department; and the fifth column The bit setting unit is configured to specify, when the department information is imported by the external system, the serial number of the external system is the inherited node serial number value; and the sixth field setting unit is configured to set the node name of the department information to Department name. For example, in the operation process management system described in claim 3, the node data includes job information, wherein the first field setting unit is used to designate the same organizational structure as the same classification and set the same classification serial number. The second field setting unit is configured to specify the node serial number value as a job serial number value; the third field setting unit is configured to designate the previous order information as the position of the job direct supervisor and set the direct membership The job number of the supervisor position has the value of the previous node number, and the third field setting unit does not specify the previous node number value when the position is the highest-level supervisor position; the fourth field setting unit is Used to set the position of the position based on the department information The department serial number of the door is the attached node serial number value; and the fifth field setting unit is configured to specify the external system serial number value as the inherited node serial number value when the job information is imported by the external system; The sixth field setting unit is used to set the node name of the job information as the job title. For example, in the operation process management system described in claim 4, the node data includes a workflow template design data, wherein the first field setting unit is configured to designate the same path process as the same group data and Setting the same group serial number value; the fourth field setting unit is configured to set the attached node serial value according to the attached main flow path when the workflow template design data system is the secondary flow path, the fourth field The setting unit is further configured to: when the workflow template design data system is the main process path, the attachment node serial number value is not set; and the fifth field setting unit is used to inherit department information or job information in the operation flow template design data system. When the inheritance node number is set to the department serial number value or the job serial number value. For example, in the operation process management system described in claim 5, the node data includes a work flow template entity data, wherein the first field setting unit is configured to designate the same path flow as the same group and set Same group serial number value; The fourth field setting unit is configured to set the attached node serial number according to the attached main flow path when the work flow template entity data system is a secondary flow path, and the fourth field setting unit is used for the operation When the process template entity data is the main process path, the dependency node serial number value is not set; and the fifth field setting unit is used when the operation process template entity data department inherits department information, job information or work flow template design data. Set the serial number of the inherited node to the department serial number value, the job serial number value, or the node serial number value of the job flow template design data. An operation process management method is used for generating a process path of a work flow object, comprising the following steps: A, selecting a work flow template corresponding to the work flow object; B, each of the main flow paths according to the work flow template The path point runs the work flow object; C. When the path point of the main flow path has a plurality of nodes of the same level, in the group to which the first feedback node belongs, according to the order of the feedback node, the direction is higher. Expanding a process path, and when the node with feedback is generated, the remaining nodes will no longer be valid; and D, running the work flow object according to the sub-process path, and returning to step B after the operation is completed Running the next path point, where the job flow template is to specify the operation between the plurality of nodes of the process flow object The order rule, the job flow template has a plurality of path points, each path point has at least one node, and each job flow template defines a group of materials to which each node belongs. The work flow management method of claim 7, wherein in step C, when the path point of the main flow path has a singular node, in the group to which the feedback belongs, according to the order of the feedback nodes Data, the sub-process path is extended to the higher order.