JP2005141588A - Workflow management server with built-in multi-dimensional database, management method thereof, storage medium and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a workflow management system that can refer to time data and organization, organization at an optional point of time, an approval route and individual, and also perform approval. <P>SOLUTION: A multi-dimensional database 12 stores data on workflow in a state of multi-dimension such as time dimension, organization dimension, approval route dimension and personal dimension. A workflow processing unit performs retrieval for the multi-dimensional database 12 by means of optional past time, thereby enabling reference to the organization, approval route and individual at an optional point of time. Also, the approval can be performed on the basis of the reference results. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a workflow management system for realizing workflow automation, and more particularly to data management by the workflow management system.

  With the development of network technology in recent years, it has become common for many companies to digitize various documents and share these data via a network such as a LAN. Various management systems have been proposed for use in common use. For example, Patent Document 1 discloses a system for collating with a fingerprint in order to improve security in realizing such sharing of data.

One of the major flows in such a management system for sharing data is workflow automation.
Workflow automation automates a series of work flows related to multiple people and multiple business operations. A business procedure (business process) that is performed to accomplish a certain purpose in an organization is defined on a computer, and execution control is performed. Mechanism. Workflow automation is expected to develop as an infrastructure for BPR (Business System Reengineering).

  Workflow automation provides a mechanism for groupware to share information and helps collaborative work in an organization. On the other hand, a single operation is smoothly linked while transferring information between organizations, thereby improving the production efficiency of the entire operation. Increase.

  Looking back on the work at the office, many tasks are made up of partial work of organizations or individuals. Many jobs are started by direct requests from customers, superiors, other departments, or indirect requests determined by procedures.

  The requested person performs the process in accordance with the determined in-house procedure or at the discretion of the individual, and returns the result to the requester or requests another person for further processing. Such job requests are always made through information such as documents, oral responses, and e-mails.

  In this specification, a plurality of operations (workflows) that cooperate with each other through information as described above are referred to as “workflows”. In general, it is said that there are 1500 to 3000 workflows including large and small in a company.

A conventional workflow management system that manages this workflow has a master table for each organization configuration and decision route, and stores the latest organization, decision route, and personal information at that time in this master table. The decision is made based on this master table.
JP-A-11-1195120

  In the conventional workflow management system, if you want to refer back to the past organization, decision route, and individual, the workflow information in the master table has already been updated to the latest information at the current time. It was necessary to refer to stored data different from the above.

Further, in the conventional workflow management system, if an attempt is made to make a decision immediately after a personnel change or the like when the takeover is not completed, the decision must be made based on a new organization.
It is an object of the present invention to provide a workflow management system that can refer to an organization, a decision route, and an individual at an arbitrary point of time by combining time data, organization, decision route, and personal data.

  It is another object of the present invention to provide a workflow management system that can make a decision based on past data such as a decision made in an old affiliation.

  The workflow management server in the system of the present invention is premised on managing a workflow connected to a client via a network, and includes a multidimensional database, a route determination unit, and a notification unit in order to solve the above problems.

The multidimensional database stores workflow data in a multidimensional manner.
The route determining means determines an approval route based on the workflow data for the draft issued by the client.

The notifying means transmits a notification as to whether or not to approve the draft based on the route determined by the route determining means.
The data about the workflow in the multi-dimensional database includes, for example, a time dimension that is recorded for the date and time when a record of another dimension is updated, an organizational dimension that is recorded for an internal organization, and a work item route at the time of approval. It is stored as a record of a decision root dimension and a personal dimension recorded for an individual, and is configured so that a search can be performed for each dimension.

  The multi-dimensional database may include a fact table that stores a link between the time dimension record and the organization dimension, decision route dimension, and personal dimension records. With this configuration, it is possible to increase the search speed and maintain the data.

Further, for example, by constructing the multidimensional database using a HASH method using a search algorithm based on the HASH method, a search for the multidimensional database can be performed using the HASH method.
Further, the system further comprises a reference means for referring to at least one of the organizational structure and the approval route at the arbitrary past time by performing a search on the multidimensional database using an arbitrary past time as a search key. I can do it. Thereby, an arbitrary past state can be referred to.

  The system further comprises a decision making means for making a decision based on at least one of an organization configuration and a decision route in the arbitrary past time by searching the multi-dimensional database using any past time as a search key. I can do it. As a result, a decision can be made in any past state.

  The present invention also includes a riverside storage medium readable by a computer and a program executed by the computer.

  According to the present invention, confirmation of past approval routes and the like is facilitated, confirmation and investigation time is shortened, and paperwork can be smoothly operated. In addition, it is possible to make a decision that has been reversed in the past, and even when the takeover has not been completed, it is possible to make a decision that suits the actual situation.

  In addition, by using the data warehouse technology, an orderly data structure and high-speed processing are possible, and operability and operability can be improved.

FIG. 1 is a principle diagram showing a configuration principle of a workflow management server used in the workflow management system in the present embodiment.
The workflow management server 1 in FIG. 1 includes a workflow processing unit 11 and a multidimensional database 12.

  When a work item is drafted from outside the workflow management server 1 via the network, the workflow processing unit 11 reads information from the multidimensional database 12 and performs a process such as approval according to this information. The multi-dimensional database 12 is a database accessed from the workflow processing unit 11, and the records include the time dimension A recorded for the date and time when the record of other dimensions was updated, the organization dimension B recorded for the in-house system, and the approval. It consists of an approval route dimension C in which the root of the work item is recorded and an individual dimension D in which the system is recorded for each employee, and can be accessed using the data of each dimension as a key. ing.

  In the multi-dimensional database 12, records are added to the time dimension A when the elements of the organization dimension B, the decision root dimension C, and the individual dimension D change, and the organization dimension B, the decision root dimension C, A record of the change difference of the personal dimension D is added. In addition, it is good also as a structure which does not add a difference record at this time but additionally stores all the records at that time as needed.

  In the case of normal approval, the workflow processing unit 11 reads the current record from the multidimensional database 12 and performs approval processing according to this information. In the workflow at this time, an approval process is performed along the information read from the multidimensional database 12.

  In addition, when an organizational change or personnel change has occurred, but a workflow has occurred without taking over, the workflow processing unit 11 determines at which point the workflow is based on information in the multidimensional database 12. The organization dimension B, the decision root dimension C, and the personal dimension D record are read out from the multidimensional database 12 based on the time dimension A record corresponding to that time. In this workflow, an approval process is performed according to the read information.

  Also, when confirming past approval route, confirming past organization, confirming past status such as confirming past job system, etc., search for the multidimensional database 12 using the target item as a key. Confirmation can be performed by reading the corresponding record.

FIG. 2 is a principle diagram showing a configuration example of the multidimensional database 12 of FIG.
The multidimensional database 12 stores a data record 121 and a fact table 122.

  The data record 22 includes a time record group that is a record group corresponding to the time dimension A, an organization record group that is a record group corresponding to the organization dimension B, an approval route record group that is a record group corresponding to the approval route dimension C, and A personal record group which is a record group corresponding to the personal dimension D is stored. The fact table 23 includes a time record group link that is a link to the time record group, an organization record group link that is a link to the organization record group, an approval route record group link that is a link to the approval route record group, and a personal record group. A record group of management records in which data of a personal record group link, which is a link to, is stored in one record is stored. By having this fact table, the multidimensional database 12 can obtain a high search speed and data maintainability.

  When the time to be processed is designated as a search key from the workflow processing unit 11, the multidimensional database 12 searches the record group of the fact table 23 with this search key, and the data record from the time record group link of each record. Reference is made to the time information in the time record group of 22, and the organization corresponding to the data record 22 is used by using the organization record group link, the approval route record group link, and the personal record group link in the record of the fact table for the matched ones. Retrieve records, approval route records, and personal records.

When an organization, a decision route, or an individual is designated as a search key from the workflow processing unit 11, the same processing as that when the above-described time is used as a search key is performed.
The multidimensional database 12 is constructed by adopting a HASH method using a search algorithm based on a so-called HASH method, and realizes high-speed search processing by HASH search.

Next, a specific configuration of the workflow management system in the present embodiment will be described.
FIG. 3 is a diagram showing a specific configuration example of the workflow management system of the present embodiment.
The system shown in FIG. 1 has a configuration in which a plurality of clients 21, a mail server 22, and a workflow management server 23 are connected by a network 24. The mail server 22 may be configured as a function of the workflow management server 23, not as an independent server.

  The client 21 is one of in-house network terminals in which the present system is installed. In this system, a user who is a member of an organization such as an employee issues a draft from the client 21 or via the mail server 22. Give approval / rejection instructions to the received notification. The mail server 22 transmits a notification mail to the E-mAil address instructed from the workflow management server 23. The workflow management server 23 corresponds to the workflow management server 1 of FIG. 1 and manages the workflow generated in this system. The network 24 is an in-house LAN or a public network. When a public network such as the Internet is used for the network 24 or when a public network is partially used when the network 24 is constructed, the network 34, the client 21, the mail server 22, and the workflow management server 23 are The configuration includes a security mechanism (not shown).

  The workflow management server 23 includes a workflow engine 231, a multidimensional database 232, a route management master table 233, an organization configuration master table 234, and a work management table 235. Among these, the workflow engine 231 and the multidimensional database 232 correspond to the workflow processing unit 11 and the multidimensional database 12 of FIG. 1, and the route management master table 233 and the organization configuration master table 234 correspond to the master table.

  The route management master table 233 stores data for determining the processing route of the work item 211 issued by the client 21 in the case of normal approval, and stores the route name, route order, affiliation, and job authority. The The organization configuration master table 234 stores actual destinations, and stores a name, affiliation, job authority, and E-mAil address. The flow management table 235 is a table for recording and managing various information about the drafted work item 211 and the workflow by the work item 211, and draft data corresponding to the drafted work item 211 and its attached file, The name, affiliation, job authority, E-mail address, information indicating approval / rejection for the work item 211, and information indicating completion / cancellation of approval for the work item 211 are stored. It is managed. The route management master table 233 and the organization configuration master table 234 are stored in the memory in the workflow server 23 when the workflow server 23 is started based on information indicating the latest state stored in the multidimensional database 232. Generated.

FIG. 4 is a diagram showing a record configuration example of the multidimensional database 232.
FIG. 4A shows an example of the configuration of data records configured in the multidimensional database 232, and FIG. 4B shows an example of the configuration of the fact table.

  As shown in FIG. 4 (a), the data record is a time dimension A in which the date and time when a record of another dimension is added or updated due to an organizational change, the affiliation (department) of each department, It consists of an organizational dimension B in which information related to the job system such as job authority is recorded, an approval route dimension C in which the workflow route at the time of approval is recorded, and an individual dimension D in which information about each user handled by this system is recorded. ing. Each record in time dimension A contains year, first half / second half, year, month, and day. Each record in organization dimension B contains year, first half / second half, year, month, day, affiliation (department), For each record of the decision authority root dimension C, the year, first half / second half, year, month, day, route name, route order, the affiliation (department) of the authorizer, and the authority authority for each individual dimension D In the record, year, first half / second half, year, month, day, name, affiliation (department), job authority, and E-mail address are recorded. The year, month, day, etc. information in each record indicates the date on which the record was made effective after the organization change, etc. As described later, refer to past organizations, decision routes, and individuals. If you want to do it, the search will be based on this date.

  As shown in FIG. 4B, the fact table stores a link in which the data records in FIG. 4A are associated. In the example of the figure, a link in which each record of the time dimension A is associated with the record of the organization dimension B, the record of the decision root dimension C, and the record of the personal dimension D is shown. For example, the record 1 of the time dimension A is associated with the record 1 and the record 2 of the organization dimension B, the record 1 and the record 2 of the decision root dimension C, and the record 1 and the record 2 of the personal dimension D by the record 1 of the table. .

  When a search is performed on the multidimensional database 232, the fact table is first searched with the search key, and the record in the data record is read using the link in the searched record. By using this fact table, the multidimensional database 232 realizes high speed search.

Next, the operation at the time of normal approval in the system of FIG. 3 will be described.
When the user accesses the drafting screen of the workflow management server 23 from the client 21 and issues a work item 211 (document) of the workflow, the drafted document data is the user's name, affiliation, job authority, E -Stored as draft data in the workflow management table 235 together with the mail address. At this time, the user name, affiliation, job authority, and e-mail address notified from the user together with the work item 211 are registered in the workflow management table 235 in association with the work item 211.

  In response to this, the workflow engine 231 designates a route name, and acquires from the route management master table 233 data on which workflow the work item 211 takes, that is, data on the route order, affiliation, and job authority. To do. Next, based on the data acquired from the route management master table 233, the workflow engine 231 acquires the next specific destination data such as an E-mAil address from the organization configuration master table 234.

The workflow engine 231 transmits a notification e-mail to the effect that the draft has been issued via the mail server 22 to the next destination acquired from the organization configuration master table 234.
The approver who is the recipient of the notification e-mail accesses the approval screen of the workflow management server 23 from his client terminal 21 and inputs approval or rejection for the work item 211. This approval or rejection information is recorded in the workflow management table 235.

  When the approval / rejection information is recorded in the workflow management table 235, the workflow engine 231 acquires data on which workflow route to take next from the route management master table 233. Further, a specific destination is acquired from the organization configuration master table 234 corresponding to the approval / rejection information. Then, a notification e-mail indicating that the draft has been issued is transmitted to the next destination acquired from the organization configuration master table 234 via the mail server 22.

  When the approval / rejection information indicates approval, the workflow engine 231 sends an email to the next approver via the mail server 22 according to the route in the same manner as described above, and the recipient of the notification email is Approve or reject input process. Thereafter, the same processing is repeated up to the final approver, and when the final approver performs input processing of approval or rejection, this processing is completed, and the work item is registered in the workflow management table 235 as completion of approval.

  If a rejection is input midway, the recipient of the notification e-mail corrects the work item and re-issues the draft or deletes the draft. If the draft is deleted, it is registered in the workflow management table 235 as an approval cancellation.

  FIG. 5 is a flowchart showing an operation process of the workflow engine 231 when a draft is made by the client 21. The processing shown in the figure is realized by the CPU in the workflow server 23 executing a program using the memory as a work area.

  When the process shown in FIG. 6 is started, first in step S1, the workflow engine 231 fetches draft data including the work item 211 from the client 21 via the network 24, and stores it in the workflow management table 235 in step S2. To end this process.

  FIG. 6 is a flowchart showing an operation process of the workflow engine 231 when a workflow route is determined for a draft issued by the client 21. The processing in the figure is also realized by the CPU in the workflow server 23 executing a program using the memory as a work area.

When the process shown in FIG. 6 is started, the workflow engine 231 first acquires a route name from the client 21 in step S11.
Next, in step S12, the workflow engine 231 acquires route order, affiliation, and job authority information from the route management master table 233 based on the route name obtained in step S11.

  In step S13, the name and e-mail address of the mail destination are acquired from the organization structure master table 234 using the affiliation and job authority obtained in step S12 as keys, and in step S14, the e-mail address is set as the transmission destination. A notification email is sent and the process is terminated.

  FIG. 7 is a flowchart showing the operation process of the workflow engine 231 in response to the approval / rejection notification from the client 21. The processing in the figure is also realized by the CPU in the workflow server 23 executing a program using the memory as a work area.

  The workflow engine 231 receives approval or rejection notification information from the client 21 via the network 24 as step S21. If the notification information indicates rejection (NO in step S22), rejection is written in the flow management table 235 as information indicating approval / rejection, and the destination determination process shown in FIG. Thus, the drafter who drafted the work item 211 is selected, a notification mail is transmitted, and this process is terminated.

  In step S21, if the received notification letter indicates approval (step S22, YES), the approval is written in the flow management table 235 as information indicating approval / rejection in step S24. If the approval / rejection notification received in step S21 is not from the final approver (step S24, NO), a notification mail is sent for the next destination by the destination determination process shown in FIG. 6 as step S25. Send this to finish this process.

  In step S24, if the approval / rejection notification received in step S21 is from the final approver (YES in step S24), information indicating completion of approval is written in the flow management table 235 in step S27. This process is terminated.

  FIG. 8 is a flowchart showing an operation process of the workflow engine 231 when the approval is stopped. The processing in the figure is also realized by the CPU in the workflow server 23 executing a program using the memory as a work area.

  In step S31, the workflow engine 231 cancels the approval from the client 21 via the network 24 and obtains a draft deletion notification. In step S32, the workflow engine 231 generates a draft for deletion in the flow management table 235. Registration is performed in association with the vote data, and this process ends.

Next, the record addition process of the multidimensional database 232 will be described. In the following description, the record addition process is performed by the workflow engine 231.
In the example shown below, there is an organizational change as an example of adding or changing records by changing individual elements. On May 1, 2000, the manager of the development department changed from Fuji Taro to Jiro Yamada, and Fuji Taro was the manager of the planning department. The case where it becomes is shown as an example.

  FIG. 9 is a diagram showing a configuration example of a record for explaining a case where a record is added and changed by an organization change. FIG. 9A shows a record before the change, and FIG. 9B shows a record added after the change. Show.

  FIG. 9A shows records related to the time dimension A, the organization dimension B, the approval route dimension C, and the personal dimension D as records before the change. In this state, the section manager of the development department is Jiro Yamada. Instead, the contents of the records of the time dimension A and the personal dimension D, which are the differences after the change as shown in FIG.

  If it is desired to speed up the processing in the search processing, a configuration is adopted in which all the records at that time are added and stored instead of the difference. As a result, the time dimension data (year, first half / second half, year, month, day) stored in each record of the organization dimension B, the decision root dimension C, and the individual dimension D are searched and related to the time dimension A. There is no need to specify the records of the organization dimension B, the decision root dimension C, and the personal dimension D, and the processing becomes faster accordingly.

  The newly added record shown in FIG. 9 (b) is a record indicating that the time dimension A was changed on May 1, 2000, and as a record of the personal dimension D, Jiro Yamada A record indicating that it is a manager of the development department and a record where Taro Fuji is the manager of the planning department.

  When the record shown in FIG. 9B is added as a data record of the multi-dimensional database 232, the record of the time dimension A, the record of the personal dimension D shown in FIG. A link that associates the record of the organization dimension B and the record of the decision root dimension C shown in FIG. 3 is generated and stored in the fact table. Accordingly, for example, when the multi-dimensional database 232 is searched using a date before May 1, 2000 as a key, the record shown in FIG. 4A is read out, and the date after May 1, 2000 is also read. When the search is performed, the record shown in FIG. 4A in which the time dimension A record and the personal dimension D record are changed to those shown in FIG. 4B is read.

Next, a case will be described in which an approval process is performed in a state where transfer is not completed immediately after a personnel change or the like.
In the following description, the section manager of the development department was changed from Fuji Taro to Jiro Yamada on May 1, 2000, but the case where the transfer is not implemented will be described as an example. In the following description, search processing for the multidimensional database 232 is performed by the workflow engine 231.

FIG. 10 is a diagram showing a configuration example of a record for explaining the processing in this case.
In the state of the record shown in FIG. 10, when a decision is made by an authorizer as of April 2000, the search is first performed on the multidimensional database 232 using April 2000 as a search key, and the time used for the decision. A record of each dimension of the organization dimension B, the approval route dimension C, and the individual dimension D of April 2000 is determined in the dimension A. In the case of FIG. 10, the record 1 of the time dimension A, the record 1 of the organization dimension B, the record 2 of the decision root dimension C, and the record 1 of the individual dimension D are selected and read from the multidimensional database 232. From this result, Fuji Taro, the finalist as of April 2000, will make the final decision.

As described above, in the system according to this embodiment, the state at an arbitrary time point can be confirmed, and the approval process can be performed in that state.
Next, a case where the past state is confirmed will be described. Note that the various processes in the following description are performed by the workflow engine 231 based on a userized field instruction.

FIG. 11 is a diagram showing a configuration example of a record for explaining processing when confirming a past approval route, organization, and organization.
When it is desired to confirm the past approval route, the approval route on that date can be found by searching the approval route dimension C according to the desired date. For example, in the record structure as shown in FIG. 11, when it is desired to check the approval route of “equipment approval” in the second half of 1999, a search is performed with respect to the approval route dimension C using the second half of 1999 and the equipment approval as a search key. From the records 1 and 2 of the decision route dimension C output from the multi-dimensional database 232 as a search result, it can be seen that the decision route is the manager of the management unit → the manager of the management unit.

When confirming the past organization, the organization dimension B is searched.
For example, when it is desired to know the organization change in the second half of 1999, a search is performed in the organization dimension B using the second half of 1999 as a search key, and the records 1 and 2 of the organization dimension B in FIG. It is output from H.232, and it can be seen from this result that the management department and the research and development department have changed in the second half of 1999.

Further, when confirming the past office system, a search is performed on the personal dimension D.
For example, by searching the personal dimension D using April 2000 as a search key, the record 1 of the personal dimension D in FIG. 11 is output from the multidimensional database 232 as a search result. It turns out that the section manager of the development department is Taro Fuji.

As described above, in the system according to the present embodiment, it is possible to easily confirm the approval route, organization, and status of the organization at an arbitrary past time.
Next, as a specific example of the use of this system, when this system is used in a government agency where the approver's regular personnel changes at the time of change of period, the confirmation of the approval route at any time in the past is shown. 12 will be described.

FIG. 12A shows a record example of a fact table for explaining this example, and FIG. 12B shows a record example of a data record.
When confirming the approval route for equipment approval in the second half of 1999, it can be seen from the fact table in FIG. 12A that the record in the second half of 1999 is record 1. From the decision record group link in the record 1 of the fact table, it can be seen that the corresponding records in the decision route dimension C are the record 1 and the record 2.

  Therefore, when the data of the record 1 and the record 2 is read from the decision root dimension C of the data record group shown in FIG. 12B, the route order No. 1 is in charge of the management department and the second is the manager of the management department. It can be confirmed that the approval route of the equipment approval is the manager in charge of the management department → the manager of the management department.

  Next, as another example of the practical use of this system, in the case where this system is used in a private company, an example of confirming a past decision route in a private company and making a decision in reverse time is shown in FIG. It explains using.

  In this case, for determining the workflow route, the data of the decision root dimension C in the multidimensional database 232 is used instead of the route management master table 233, and the individual dimension D of the multidimensional database 232 is used instead of the organization configuration master table 234. This is different from the normal approval process in that data is used.

  As in the case of the government office described above, when confirming the approval route for equipment approval in the second half of 1999, first, the fact table shown in FIG. 12A is checked, and the record in the second half of 1999 in the fact table is record 1. I understand. From the decision record group link in the record 1 of the fact table, it can be seen that the corresponding records in the decision route dimension C are the record 1 and the record 2.

  Therefore, as in the case of the government office described above, when the data of record 1 and record 2 is read from the decision route dimension C of the data record group shown in FIG. Since it is a section manager, it can be confirmed that the approval route of the facility approval is the manager in charge of the management department → the manager of the management department.

Next, a specific authorizer is identified in the confirmed approval route.
When the manager in charge searches the multi-dimensional database 232, first, from the personal record group link in the record 1 which is the record in the second half of 1999 in the fact table of FIG. Are record 1 and record 2, and record 1 and record 2 of this personal dimension D are read from the data record group in FIG. As a result, Jiro Takahashi is in charge of the management department, and Saburo Suzuki is the manager of the management department. Therefore, Jiro Takahashi drafts the approval and Saburo Suzuki approves the approval.

FIG. 13 is a computer system environment diagram of the workflow server 23.
As shown in FIG. 13, the workflow server 23 in this embodiment includes a CPU 31, a main storage device 32, an auxiliary storage device 33 such as a hard disk, an input / output device (I / O) 34 such as a display and a keyboard, and a network connection device such as a modem. 35 and a medium reading device 36 for reading out the stored contents from a portable storage medium such as a disk or a magnetic tape, and these are connected to each other by a bus 38.

  In the computer system of FIG. 13, a program and data stored in a storage medium 37 such as a magnetic tape, a flexible disk, a CD-ROM, and an MO are read by a medium reading device 36, and this is read as a main storage device 32 or an auxiliary storage device 33. Download to. Based on this program and data, the CPU 31 constructs the route management master table 233, the organization configuration master table 234, and the work management table 235 on the main storage device 32 or the auxiliary storage device 33, and performs various functions by the workflow engine 231. Realize.

  In the computer system of FIG. 13, application software may be exchanged using a storage medium 47 such as a flexible disk. Therefore, the present invention is not limited to a workflow management system and a management method, and is used by a computer-readable storage medium 47 or a computer for causing a computer to perform the functions of the above-described embodiments when used by a computer. It can also be configured as a program to be executed.

  In this case, as shown in FIG. 14, for example, as shown in FIG. 14, the “storage medium” is detachable from a medium driving device 47 such as a CD-ROM, a flexible disk (or may be an MO, DVD, removable hard disk, etc.). A portable storage medium 46, a storage unit (database or the like) 42 in an external device (server or the like) transmitted via the network line 43, or a memory (RAM or hard disk or the like) 45 in the main body 44 of the information processing device 41. Etc. are included. The program stored in the portable storage medium 46 or the storage unit (database or the like) 42 is loaded into a memory (RAM or hard disk or the like) 45 in the main body 44 and executed.

  In addition to the above-mentioned examples of storage media such as CD-ROM and DVD-ROM, blue colors such as Blu-ray Disc (registered trademark) and AOD (Advanced Optical Disc) are also included. It is also possible to implement the present invention using various types of large-capacity storage media that will be developed in the future, such as next-generation optical disk storage media using laser, HD-DVD9 using red laser, and Blue Laser DVD using blue-violet laser. is there.

It is a principle figure which shows the structure principle of a workflow management server. It is a principle figure which shows the structural example of a multidimensional database. It is a figure which shows the specific structural example of the workflow management system of this embodiment. It is a figure which shows the example of a record structure of a multidimensional database. It is a flowchart which shows the operation | movement process of a workflow engine when a draft is made by the client. It is a flowchart which shows the operation process of a workflow engine when determining the route | root of a workflow. It is a flowchart which shows the operation process of the workflow engine with respect to the notification of approval / rejection from a client. It is a flowchart which shows the operation process of the workflow engine at the time of cancellation of approval. It is a figure which shows the structural example of the record for demonstrating the case where a record is added and changed by organization change. It is a figure which shows the structural example of the record for demonstrating the approval process in case transfer is not implemented. It is a figure which shows the structural example of the record for demonstrating the process in the case of confirming the past decision route, organization, and management system. It is a figure which shows the structural example of the record for demonstrating the specific utilization example of the system of this embodiment. It is a computer system environment figure of a workflow server. It is a figure which shows the example of a medium.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1, 23 Workflow management server 11 Workflow processing unit 12, 232 Multidimensional database 121 Data record 122 Fact table 21 Client 22 Mail server 24 Network 231 Workflow engine 233 Route management master table 234 Organization configuration management master table 235 Work management table

Claims (10)

In the workflow management server that manages the workflow connected to the client via the network,
A multi-dimensional database that stores multi-dimensional workflow data, and
Route determination means for determining an approval route based on data about the workflow with respect to drafting by the client;
Based on the route determined by the route determination means, a notification means for transmitting a notification as to whether to approve the draft;
A workflow management server comprising:   The data about the workflow in the multi-dimensional database includes the time dimension recorded for the date and time when the record of other dimensions was updated, the organization dimension recorded for the in-house system, and the work item route at the time of approval. The workflow management server according to claim 1, wherein the workflow management server is stored as a record of an approval route dimension and an individual dimension recorded for an individual.   The system further comprises a reference means for referring to at least one of the organization structure and the approval route in the arbitrary past time by performing a search on the multidimensional database using an arbitrary past time as a search key. The workflow management server according to claim 2.   It further comprises a decision making means for making a decision based on at least one of an organizational structure and a decision route at the arbitrary past time by performing a search on the multidimensional database using an arbitrary past time as a search key. The workflow management server according to claim 2 or 3.   5. The multi-dimensional database includes a fact table storing a link between the time dimension record and the organization dimension, decision root dimension, and personal dimension records. 6. Workflow management server described in.   The multidimensional database is constructed by using a HASH method using a search algorithm based on the HASH method, and the search for the multidimensional database is a HASH search. The workflow management server described. A database device for storing data about a workflow,
Storage means for storing multi-dimensional data about the workflow;
In response to a search key input, search means for searching the storage means with the search key and outputting the result;
A database apparatus comprising: A workflow management method by a workflow management server that manages a workflow connected to a client via a network,
In response to the drafting by the client, the approval route is determined based on the data generated from the data about the workflow in the multi-dimensional database storing the data about the workflow in a multidimensional manner.
A workflow management method comprising: transmitting a notification as to whether or not to approve the draft based on the determined route. A computer-readable storage medium connected to a client via a network and managing a workflow,
A function for determining an approval route based on data generated from the data about the workflow in a multidimensional database for storing the data about the workflow in a multidimensional manner for the draft by the client;
A storage medium readable by the information processing apparatus that stores a program for causing the computer to realize a function of transmitting a notification as to whether to approve the draft based on the determined route. A program executed by a computer for managing a workflow connected to a client via a network,
A function for determining an approval route based on data generated from the data about the workflow in a multidimensional database for storing the data about the workflow in a multidimensional manner for the draft by the client;
A program for causing the computer to realize a function of transmitting, via the network, a notification as to whether to approve the draft based on the determined route.

Images