JP5508471B2 - Approval management system, approval management method, and approval management program - Google Patents

Description

  The present invention relates to an approval management system, an approval management method, and an approval management program for performing circulation management for approving an application.

  An electronic workflow system may be used in an approval process in an organization such as a company. In this electronic workflow system, various applications created by the applicant are electronically distributed via a network, and confirmation work for approval is performed.

  In view of this, an approval support system for supporting an approval process efficiently and reliably while using a paper document such as a slip has been studied (for example, see Patent Document 1). In the approval support system described in this document, in the drafting process, the approval support server executes a slip printing process. On this voucher mount, a slip code and a barcode encoded with the registration date and time are printed. In the approval process, the control unit acquires the barcode data, and compares the registration date and time of the slip record with the date and time acquired from the barcode. If they match, an approval registration process is performed. When a completion notification is received from the drafting department approver terminal, an approval omission confirmation process is executed. If an unapproved voucher that has been pre-processed at the same time is searched for in the case for which approval processing has been performed this time, and an unapproved approval management record that has been pre-processed at the same time remains, the drafting department approver The confirmation screen output process is executed on the terminal display.

  In addition, a work application management system for efficiently performing a work application for a work target system and a determination on the accuracy of work contents has been studied (for example, see Patent Document 2). In the work application management system described in this document, the control unit of the approval management server searches for a template of the application form in the application template information storage unit when acquiring the work content from the client terminal in the application process. And a control part provides the model of an application form to a client terminal. In the work record confirmation process, the control unit determines whether there is a mismatch between the work record and the work application. If there is a discrepancy, alert the applicant or worker. When the application for approval of the work result is acquired in the work post-processing, the control unit compares the work result with the application content. If the contents do not match, either the original application correction process or the additional work application process is executed as the difference complement process.

Japanese Patent Laying-Open No. 2008-9772 (first page, FIG. 1) JP 2011-215726 A (first page, FIG. 1)

  In the workflow described in the above-described patent document, circulation processing is performed in a predetermined order from application to final approval. Here, when a new workflow is generated, it is difficult to use the existing workflow, and it is necessary to create a new workflow from the beginning. In particular, a plurality of similar workflows may be used in an organization. Even in this case, if a plurality of workflows are created separately, it is difficult to quickly and efficiently manage the workflow. A series of business processes may be composed of a plurality of business steps. In the conventional workflow management, there is only the circulation process that is finally approved from the application in units of individual business steps. Regarding the circulation process of business processes in which individual business steps are bundled in a parallel or sequential relationship, It was not considered. In addition, business requirements such as approval conditions in the business process may be changed, but customization such as addition of functions is required individually. The preparation period and cost burden for this have been issues.

  The present invention has been made to solve the above-described problems, and provides an approval management system, an approval management method, and an approval management program for efficiently realizing circulation management for approving an application. .

In order to solve the above-mentioned problems, the invention described in claim 1 is directed to a business process storage unit that records a business process in which a plurality of business steps are combined with respect to an applicant's application, and a circulation for each business step. A circulation route storage unit that records a circulation route for identifying the destination in order, and in each business step, records the items and input contents included in the document used for circulation of this business step, and the content of the circulation state An approval management system comprising an individual information storage unit and a control unit connected to a client terminal of an applicant and a recipient approver, and generated based on an application acquired from the client terminal of the applicant by document input contents for items included in recorded in the individual information storage section, business processes of the document using the business process storage unit Identified, and circulated apply to the circulation destination approver, obtains authorization information from the approver performs the circulation process of registering circulated state to the individual information storage unit, the business According to the usage conditions of each business step constituting the process, the input content for the item included in the new document generated in each business step is recorded in the individual information storage unit, and in the individual information storage unit, The gist is to continue the circulation process until approval information is acquired from all approvers of circulation destinations in all the business steps constituting the business process of the application.

  The invention according to claim 2 is the approval management system according to claim 1, further comprising a grace period storage unit that records a grace period for approval, and the control unit uses the grace period each time. The gist is to calculate the approval deadline at the attachment destination, and to output a list in which the application information circulated to the circulation destination is rearranged based on the approval deadline at the client terminal of the approver of the circulation destination To do.

  According to a third aspect of the present invention, in the approval management system according to the second aspect, a final approval scheduled date which is an approval deadline at the last circulation destination is calculated for the application, and the final approval desired date and the final When the final approval date is later than the final approval date, a reminder is output to the client terminal of the applicant.

  In the approval management system according to claim 2 or 3, when the approval information about the application is acquired from the client terminal of the approver of the circulation destination in the approval management system according to claim 2 or 3, The gist is to readjust the approval deadline of the recipient based on the current date and the grace period.

  According to a fifth aspect of the present invention, in the approval management system according to any one of the second to fourth aspects, the schedule information of the approver of the circulation destination is acquired, and the approver's The gist is to output attention information to the client terminal when it is determined that the approval cannot be made by the approval deadline.

  According to a sixth aspect of the present invention, in the approval management system according to any one of the second to fifth aspects, the personnel change information of the approver of the distribution destination is acquired, and the change included in the personnel change information The gist is to output caution information to the client terminal for an application within a reference number of days from the scheduled date to the approval deadline.

  The invention according to claim 7 is the approval management system according to any one of claims 2 to 6, wherein the personnel change information of the approver of the distribution destination is acquired, and the approval included in the personnel change information For a person, the prior approver is specified in the circulation route recorded in the circulation route storage unit, the approval deadline of the preceding approver is specified, and the approval deadline of the preceding approver is included in the personnel change information The gist is to delete an application later than the scheduled transfer date from the approval list output to the client terminal of the approver of the distribution destination.

  According to an eighth aspect of the present invention, in the approval management system according to any one of the second to seventh aspects, a critical path in each business process is specified, and a distribution destination of a business step constituting the critical path is specified. The gist is to calculate the approval deadline of the approver, and to calculate the approval deadline of the approver who is the circulation destination of the business step parallel to the critical path based on the approval deadline of the critical path.

The invention described in claim 9 relates to a business process storage unit that records a business process in which a plurality of business steps are combined with respect to an applicant's application, and a time for specifying a circulation destination for each business step. A circulation route storage unit that records the attached route, an individual information storage unit that records the items and input contents included in the document used for circulation of the business step and the content of the circulation state in each business step, and the applicant And an approval management system comprising a control unit connected to the client terminal of the approver of the distribution destination, wherein the control unit is connected to the client terminal of the applicant. the entries for the items included in the document is generated based on the acquired application recorded in the individual information storage section, said using said business process storage unit documentation Identify cement business processes, the by circulated apply against circulation destination approver, obtains authorization information from the approver, the circulation registers the circulated state to the individual information storage unit process And , according to the usage conditions of each business step constituting the business process, the input contents for the items included in the new document generated in each business step are recorded in the individual information storage unit, and the individual information in the storage unit, and be required to continue the circulation process until the approval information from all approvers circulation destination in all operation steps constituting a business process of the application.

The invention described in claim 10 relates to a business process storage unit that records a business process that is a combination of a plurality of business steps for an applicant's application, and a process for sequentially specifying a distribution destination for each business step. A circulation route storage unit that records the attached route, an individual information storage unit that records the items and input contents included in the document used for circulation of the business step and the content of the circulation state in each business step, and the applicant And an approval management system comprising a control unit connected to the client terminal of the approver of the distribution destination, and a program for managing the approval from the client terminal of the applicant the entries for the items included in the document is generated based on the acquired application recorded in the individual information storage section, prior to using the business process storage unit Identify business process documents, the then circulated apply against circulation destination approver, obtains authorization information from the approver, the circulation registers the circulated state to the individual information storage unit process And , according to the usage conditions of each business step constituting the business process, the input contents for the items included in the new document generated in each business step are recorded in the individual information storage unit, and the individual information in the storage unit, and summarized in that to serve as a means to continue the circulation process until the approval information from all approvers circulation destination in all operation steps constituting a business process of the application.

(Function)
According to the invention of claim 1, 9 or 10, based on the application acquired from the client terminal of the applicant, the business process is identified using the business process storage unit, and the circulation route storage unit is used, The circulation destination in the business step included in the business process is specified, the application is circulated to the approver of the circulation destination, and the circulation process of acquiring the approval information from the approver is performed. In this case, the circulation process is continued until approval information is obtained from all approvers of the circulation destination in the business steps constituting the business process of the application. Thereby, the application can be circulated in consideration of the business steps constituting the business process.

  According to the second aspect of the invention, the approval deadline at each circulation destination is calculated using the grace period, and the application information distributed to the circulation destination is approved at the client terminal of the circulation destination approver. Output a list that is sorted based on the deadline. Thereby, the approver can perform the approval work in consideration of the approval deadline.

  According to the third aspect of the present invention, the final approval scheduled date that is the approval deadline at the last circulation destination for the application is calculated. Then, the final approval date of the application is compared with the final approval date, and if the final approval date is later than the final approval date, an alert is output to the client terminal of the applicant. This can alert you to applications that may be delayed in final approval.

  According to the invention described in claim 4, when the approval information about the application is acquired from the client terminal of the approver of the distribution destination, the approval date of the subsequent distribution destination in the business process is set to the current date and the grace period. Readjust based on period. Thereby, the approval deadline of the subsequent circulation destination can be adjusted based on the progress.

  According to the invention described in claim 5, the schedule information of the approver of the circulation destination is acquired. Then, in the schedule information, when it is determined that the approval cannot be made by the approver's approval deadline, attention information is output to the client terminal. Thereby, it is possible to alert an application that is difficult to approve in consideration of the approver's schedule.

  According to the sixth aspect of the present invention, the personnel change information of the approver of the distribution destination is acquired. Then, for the application within the reference number of days from the scheduled transfer date to the approval deadline included in the personnel change information, attention information is output to the client terminal. Thereby, when personnel changes are near, prompt approval can be promoted by calling attention.

  According to the seventh aspect of the invention, the personnel change information of the approver of the distribution destination is acquired. Next, for the approver included in the personnel change information, the prior approver is specified in the circulation route recorded in the circulation route storage unit, and the approval deadline of the prior approver is identified. Then, an application whose approval date for the preceding approver is later than the scheduled transfer date included in the personnel change information is deleted from the approval list output to the client terminal of the approver of the circulation destination. As a result, it is possible to prevent the applicant who is likely to change the approver at the approval time from showing to the prospective transferee.

  According to the eighth aspect of the invention, the critical path in each business process is specified, and the approval deadline of the approver who is the circulation destination of the business step constituting the critical path is calculated. Then, the approval deadline of the approver who distributes the business steps parallel to the critical path is calculated based on the approval deadline of the critical path. As a result, it is possible to calculate the approval deadline for circulation performed in parallel with the critical path in consideration of the approval deadline for the critical path.

  According to the present invention, it is possible to provide an approval management system, an approval management method, and an approval management program for efficiently realizing circulation management for approving an application.

The system schematic of embodiment of this invention. Explanatory drawing of the relationship between the business process of this embodiment, and a business step. Explanatory drawing of the document state of this embodiment. It is explanatory drawing of the specific example of the business process of this embodiment, Comprising: (a) is a business process with respect to serious nonconformity, (b) is explanatory drawing of the business process with respect to minor nonconformity. It is explanatory drawing of the data used by this embodiment, (a) is a setting information memory | storage part, (b) is a user memory | storage part, (c) is a business process memory | storage part, (d) is recorded on a circulation route memory | storage part. Explanatory drawing of made data. Explanatory drawing of the screen transition of this embodiment. It is explanatory drawing of the data used by this embodiment, Comprising: The explanatory drawing of the data recorded on the screen memory | storage part, the separate information storage part, and the template file. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the screen used by this embodiment, Comprising: (a) is an initial setting screen, (b) is a user registration screen, (c) is explanatory drawing of a circulation route registration screen. Explanatory drawing of the detailed work screen and document registration screen which are used by this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment. Explanatory drawing of the process sequence of other embodiment.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In this embodiment, the application submitted by the applicant will be described as an approval management system, an approval management method, and an approval management program for supporting the approval performed by the approver.

  In the present embodiment, as shown in FIG. 1, an approval management server 20 as an approval management system is used to support approval management of an application. The approval management server 20 is connected to the client terminal 10 and the directory management server 40 via a network.

  In the present embodiment, as shown in FIG. 2, one application (job) is approved using one business process. This business process is composed of a plurality of business steps (1 to n). In each business step, circulation (contact and approval) to departments, positions and individuals determined in the circulation route is performed. When mandatory approval is completed in each business step, circulation (contact or approval) is performed in the next business step. When the final approval in the business step is finished, the circulation is finished.

  In each business step, a document used for circulation is generated. In this embodiment, as will be described later, a document is generated by setting a value (attribute) for an item (genus) included in the document. Here, FIG. 3 shows the state of the document. When a document is created for the first time, it is in a “Creating” state. When the creation of the document is completed and the start of circulation is input, the state of “circulating” is entered. In this case, application and document circulation are performed based on a predetermined circulation route. Then, if the document being “circulated” is rejected by the approval process, the state is “rejected”. Further, when the “circulating” document is canceled, the “circulating cancellation” state is entered. When all the approvers approve the “circulating” document, the state becomes “complete”.

  A specific example of the approval management method will be described with reference to FIG. FIG. 4 shows a response to the nonconformity report. FIG. 4A shows a business process for a serious nonconformity, and FIG. 4B shows a business process for a minor nonconformity.

  When the sales department makes an application for a serious nonconformity, a business process composed of three business steps (nonconformity reporting step, nonconformity handling step, nonconformity prevention step) is executed. First, in the non-conformity reporting step, a job about application for a serious non-conformance and a non-conformance report document attached with a product status file are created and circulation is started. This nonconformity report document is communicated to the manufacturing department and the quality control department based on the circulation route. On the condition that this communication is completed, the process shifts to a non-conformance handling step which is the next business step. Here, in the manufacturing department, a document about nonconformity handling with a cause repair file describing the cause of nonconformity and repair is created and circulation is started. This document is circulated in the quality management section based on the circulation route and the content is confirmed. When the approval in the quality control department is completed, it is distributed to the sales department based on the circulation route. Furthermore, the process proceeds to the next non-conformance prevention step, which is subject to approval by the quality management unit. In this case, the manufacturing department creates a document about non-conformity prevention with a precautionary measure file describing preventive measures for preventing nonconformity, and starts circulation. The document of this preventive measure is approved by the quality control department based on the circulation route. Upon completion of approval in the quality control department, the business process of serious nonconformity is terminated.

On the other hand, when an application for minor nonconformity is made in the sales department, a business process composed of two business steps (nonconformity reporting step, nonconformity handling step) is executed. First, in the non-conformity reporting step, a job for application for minor non-conformance and a document for non-conformance report are created and circulation is started. In this case, the file is not attached, and contact and approval are performed based on the circulated document (application contents). Also in this case, the nonconformity report document is communicated to the manufacturing department and the quality control department based on the circulation route. Transition to the non-conformance handling step, which is the next business step, on the condition of contacting the manufacturing department. Here, the manufacturing department creates a document about nonconformity handling that describes the cause and repair of nonconformity, and starts circulation. This nonconformity response is circulated in the quality control section and the content is confirmed. Distributed to the Sales Department subject to approval by the Quality Management Department. The non-conformance business process is terminated by distribution to the sales department.
In this way, a plurality of business steps that are partially common can be combined to form two business processes according to the purpose.

Next, the configuration of the approval management system will be described.
The client terminal 10 is a computer terminal used by an administrator of the approval management server 20, an applicant, or a circulation destination user such as an approver. The administrator of the approval management server 20 uses the client terminal 10 to perform initial settings, user registration, circulation route registration, and the like in the approval management server 20. The applicant makes various applications using the client terminal 10. A circulation destination user such as an approver or a confirmer uses the client terminal 10 to confirm the application content. Then, the approver confirms the contents of the document and inputs approval, denial, cancellation, or the like. The client terminal 10 includes a display unit configured from a display (not shown) and the like, and an input unit configured from a keyboard, a pointing device, and the like.

  The directory management server 40 is a computer system that provides a directory service that stores and retrieves information about resources on the network and their attributes. The directory management server 40 collectively manages users and network resources. For this reason, a user database storing information on users and organizations using the network is provided.

  In the user database, a user management record for managing users who use the approval management server 20 is recorded. This user management record is recorded when user registration is performed. In the user management record, data relating to employee code, name, contact information, affiliation, title, and authentication code is recorded.

In the employee code data area, data relating to an identifier (for example, an employee number) for identifying each employee is recorded.
Data relating to the name of the user is recorded in the name data area.
In the contact data area, data related to the user's contact information (for example, mail address or telephone number) is recorded.

In the affiliation data area, data relating to an identifier for specifying the department to which the user belongs is recorded.
In the post data area, data relating to an identifier for specifying the post of the user is recorded. With this position, the authorization authority can be specified.
In the authentication code data area, data related to authentication information (for example, a password) when performing user authentication is recorded.

  The approval management server 20 is a server computer for managing the approval of applications (jobs) registered with the applicant. As shown in FIG. 1, the approval management server 20 includes a control unit 21, a setting information storage unit 22, a user storage unit 23, a business process storage unit 24, a circulation route storage unit 25, a screen storage unit 26, and an individual information storage. A portion 27 is provided.

  Here, the control unit 21 includes a control unit including a CPU, a RAM, a ROM (not shown), etc., and processes (setting management stage, user authentication stage, screen control stage, application management stage, (Each process such as approval management stage). As shown in FIG. 1, the control unit 21 functions as a setting management unit 211, a user authentication unit 212, a screen control unit 213, an application management unit 214, and an approval management unit 215 by executing the approval management program.

The setting management unit 211 executes a registration process of setting information for initial setting, user registration, and circulation route registration for using the approval management server 20.
The user authentication unit 212 executes a process for authenticating the user of the client terminal 10. The user authentication unit 212 acquires user authentication information (employee code and authentication code) from the client terminal 10. Further, the user authentication unit 212 uses the directory management server 40 to specify the accessed user. If user authentication cannot be performed, an error message is transmitted to the client terminal 10. When user authentication is successful, the use of the approval management server 20 is permitted.

The screen control unit 213 provides various screens for application and approval to the client terminal 10 and executes processing for acquiring information input to the various screens in the client terminal 10.
The application management unit 214 executes processing for managing the application by the applicant.
The approval management unit 215 executes processing for managing approval by the approver.

  In addition, the control unit 21 holds a grace period table (grace period storage unit) that defines a grace period (number of days) until approval is made in correspondence with the position of the approver. By using this grace period table, the approval deadline can be calculated from the current date and the grace period corresponding to the position of each approver.

  As shown in FIG. 5A, an initial setting information file 220 for using the approval management server 20 is recorded in the setting information storage unit 22. The initial setting information file 220 is registered when the initial setting is performed by the administrator of the approval management server 20. The initial setting information file 220 records information on business process settings, ledger settings, menu settings, system definition settings, screen definition settings, label settings, message settings, and mail settings.

  In the business process setting information, information on the business process name, business process description, automatic numbering method (initial number and numbering rule), and business step (step ID) included in the business process are recorded.

In the ledger setting information, data on various ledger formats provided to the user (items to be displayed in the ledger, etc.) and data on the user who displays the ledger are recorded.
In the menu setting information, data related to items included in the menu screen when the user accesses is recorded.

  In the system definition setting information, setting information about the operating environment of the approval management server 20 is recorded. For example, domain setting of the approval management server 20, password conditions (expiration date and password length), directory setting, and the like can be performed.

  In the screen definition setting information, setting information for controlling each screen is recorded. For example, the automatic numbering method of the circulation route set on the circulation route registration screen, the minimum value of automatic numbering, the default value, and the like are set. In addition, on the approval screen, whether or not multiple approvals are performed for a plurality of approvals at a time is set.

In the label setting information, data relating to labels fixedly arranged on each screen is recorded.
In the message setting information, a success message and an error message at the time of processing execution are recorded.

  In the mail setting information, data relating to the content of mail transmitted at the start of circulation or approval is recorded. Specifically, it is possible to set a step for sending a mail (step specification), a mail type, a title, a text, and the like.

  As shown in FIG. 5B, a user management record 230 for managing users of the approval management server 20 is recorded in the user storage unit 23. This user management record 230 is recorded when a user is registered by an administrator. The user management record 230 includes data on employee ID, e-mail address, administrator, first and last name (kanji), affiliation (1) to affiliation (n), position, position affiliation, and authority group.

Data relating to an identifier for identifying each user is recorded in the employee ID data area.
In the mail address data area, data related to the contact (mail address) used by the user is recorded.

In the administrator data area, a flag for specifying the presence or absence of administrator authority is recorded.
In the first and last name (kanji) data area, data relating to the kanji notation of the name of the user is recorded.

  Data related to the user's affiliation is recorded in the affiliation (1) to affiliation (n) data area. In the present embodiment, organization names are recorded in each data area in order from the upper organization to the lower organization. “Affiliation (1)” has a department name (for example, “Manufacturing Department”), “Affiliation (2)” has a team name (for example, “First Team”), and “Affiliation (3)” has The section name (for example, “second section”) belonging to this team is recorded.

  In the post data area, data relating to the post of the user is recorded. For example, “Department Manager”, “Team Manager”, “Section Manager”, etc. are used as positions. If there is no title, this data area is left blank.

  In the post affiliation data area, data relating to an identifier for specifying the affiliation to which the user's post is given is recorded. For example, “Affiliation (1)” for “General Manager”, “Affiliation (2)” for “Team Manager”, “Affiliation (3)” for “Manager”, etc. Is done.

  In the authority group data area, data relating to an identifier for specifying the use authority of the approval management server 20 for this user is recorded. For example, the viewing authority for a specific ledger is set.

  As shown in FIG. 5C, the business process storage unit 24 records a business process management record 240 for managing business steps constituting the business process. This business process management record 240 is registered at the time of initial setting. The business process management record 240 includes a business ID, a description, and data regarding step IDs (1) to (n).

Data relating to an identifier for specifying the business process is recorded in the business ID data area.
In the explanation data area, explanation of the contents of the business process is recorded. For example, descriptions such as “working with serious nonconformity” and “workflow with minor nonconformity” are used.

  In the step ID data area, data relating to an identifier for specifying a business step constituting this business process is recorded. In the case of a plurality of business steps, step IDs for specifying all the business steps are recorded in the order of execution.

  As shown in FIG. 5D, a circulation route management record 250 is recorded in the circulation route storage unit 25. The circulation route management record 250 records a circulation route for distributing a document for a registered job. The circulation route management record 250 is recorded when a circulation route is registered by the administrator. The circulation route management record 250 is associated with the route ID, business ID, step ID, registrant, and circulation destination information (circulation classification, mandatory / optional designation, employee name, group name, affiliation, position) Containing data about. A plurality of circulation destinations can be registered in one business process and business step.

In the route ID data area, data relating to an identifier for specifying the circulation route is recorded.
In the business ID and step ID data area, data relating to an identifier for specifying a business process and a business step to which the circulation route is applied is recorded.
In the registrant data area, data relating to the employee who registered the circulation route is recorded.

  Data for specifying the work at the circulation destination is recorded in the circulation classification data area. In the present embodiment, “contact”, “approval (1)”, “approval (2)”..., “Distribution” is recorded. Here, “contact” indicates a circulation destination to notify registration contents by e-mail when circulation starts. “Approval (1)” indicates a circulatory destination that is first approved at the start of circulation. “Approval (i)” indicates a circulation destination where the approval is made when the approvals of all the approvers set by “approval (i-1)” and “required” are completed. “Distribution” indicates a distribution destination to which a document regarding a job is distributed when the approval of all the approvers is completed.

The mandatory / optional designation data area is a classification for identifying mandatory or optional work (for example, approval work) at the circulation destination.
In the employee name data area, an identifier for specifying a circulation destination (user) who performs the work specified in the circulation classification is recorded. Here, the user to be distributed can be specified using the department, title, and employee name.

In the group name data area, an identifier for specifying the group to which the user at the distribution destination belongs is recorded.
In the affiliation data area, data for specifying the department to which the user at the distribution destination belongs is recorded.
In the position data area, data relating to the position of the user at the distribution destination is recorded.

  As shown in FIG. 6, screen data used when the approval management server 20 is used is recorded in the screen storage unit 26. This screen data is registered when the screen layout is determined by the user (administrator). As shown in FIG. 6, the screen storage unit 26 includes a top screen 610, a document registration screen 611, a circulation start screen 612, a ledger screen 613, an approval screen 614, a retrieval screen 615, a circulation progress detail screen 616, an approver. A change screen 617 and the like are recorded.

  The top screen 610 is a screen that is displayed first when user authentication is completed. The top screen 610 includes display fields for contents set in the menu definition (for example, “wait for work”, “work selection”, “notification display”, etc.).

  The document registration screen 611 is a screen for registering a job or document for application. This screen displays the contents set on the detailed work screen described later. In the document registration screen 611, an attribute (value) input corresponding to the genus (item) can be set in association with the job ID and document ID.

  In the circulation start screen 612, a circulation route of an application (job) created using the document registration screen 611 is displayed. Then, it is possible to input circulation start and circulation cancellation for this job.

On the ledger screen 613, a ledger that displays a list of registered jobs and documents is displayed.
The approval screen 614 is a screen for the approver to confirm the application contents and input approval approval / disapproval. The approval screen 614 includes an icon for inputting approval or denial. Furthermore, a comment input field at the time of approval is also included.

The recovery screen 615 is a screen for the applicant to recover the application (job) for which circulation has started. On this screen, input the necessity of recovery.
On the circulation progress detail screen 616, the progress status in the circulation route is displayed for the designated application (job). This circulation progress detail screen 616 includes circulation classification, required / optional designation, name (creator or approver), department (creator or approver's affiliation), approval date (only when approved), approval Each display column of the comment of the hour is included.

  The approver change screen 617 is a screen for changing the default approver. For example, when it is difficult for the original approver to input approval, another user can be set as an approver under a predetermined condition. The self-approval prohibition function prohibits the approval route with the applicant himself as the approval authority. Specifically, when “circulation start” on the circulation start screen is pressed, an error occurs if the final approver of the circulation route is a logged-in user.

  The circulation route setting screen 621 is a screen for setting a normal circulation route. This circulation route setting screen 621 includes an input field for setting a circulation classification, required / optional designation, department, job title, employee name, and the like.

In the circulation category column, “contact”, “approval (1)” to “approval (n)”, and “distribution” are set.
In the Mandatory / Optional field, specify the required or optional for the work to be distributed.
In the fields of department, title, and employee name, information for identifying the department to which the information is to be distributed, the title of the user to whom the information is to be distributed, and the user to whom the information is to be distributed is set.

The proxy approval setting screen 622 is a screen for setting an approver who performs proxy approval for an approver of a normal circulation route.
The maintenance screen 623 is used when the administrator confirms the login status of the user. Further, when system maintenance is performed, login by a general user is suppressed by setting a system maintenance mode.

  As shown in FIG. 7, the screen data 260 recorded in the screen storage unit 26 is composed of a display screen and a style sheet. The display screen and the style sheet are arranged in a matrix from a plurality of fields, as will be described later.

In the style sheet, genus species and properties are recorded for field positions.
The field position is information for specifying the place where the field is arranged on the screen.
The genus species is information for specifying the item of the value input on the display screen.

The property is information regarding the condition of the value to be entered in this field.
In the display screen, an input column for an attribute (value) to be input is provided for the field position.
In this manner, the preset genus and the attribute (value) input on the screen are associated with each other via the screen data.

  In the individual information storage unit 27, as shown in FIG. 7, individual management data 270 for managing the applied job (application information) is recorded. This individual management data 270 is recorded when an application is registered. The individual management data 270 includes data related to the management ID, genus species, and attributes.

  In the management ID data area, data relating to an identifier for specifying this job is recorded. Here, the management ID is composed of a combination of “job ID” or “job ID and document ID”. A job ID is set for the contents common to all job business processes. On the other hand, “job ID and document ID” are set for the contents of some business steps constituting the job business process.

In the genus / species data area, an identifier for specifying the registered attribute (value) item is recorded. For example, data relating to a job ID, a subject, a registrant, a registered department, a registration date, a document ID, and the like are recorded as the genus for the job ID. In addition, as an arbitrary genus, it is possible to set a final approval date for the application. Furthermore, as the progress status, the step ID of the current business step, the registrant of the current business step, the circulation destination (including the approver), each distribution status (incomplete, waiting for work, approved, contacted, distributed) Etc.) and the approval deadline of each approver. For example, in a business process corresponding to nonconformity, a failure rank, a system name, an influence level, a failure content, a work situation, etc. are included as genus types.
Information input to the genus species is recorded in the attribute (value) data area. Numerical values, texts, and the like are recorded in this data area.

  The individual management data 270 recorded in the individual information storage unit 27 can be registered using a spreadsheet file. In this case, as shown in FIG. 7, a template file 265 of a spreadsheet file is prepared. The template file 265 includes a main worksheet and a format worksheet. In the format worksheet, similar to the style sheet described above, the species and properties are set for the field position. In the main worksheet, an attribute (value) can be set at the same field position in the format worksheet. For such a template file 265, a spreadsheet file in which attributes (values) are set is imported into the approval management server 20. In this case, the control unit 21 of the approval management server 20 generates the individual management data 270 in which the attribute (value) set in the main worksheet is recorded for the genus set in the format worksheet. Register in the storage unit 27.

  The individual management data 270 recorded in the individual information storage unit 27 can also be output to a spreadsheet file. Also in this case, the template file 265 shown in FIG. 7 is used. In the format worksheet, the genus and properties are set for the field position. In the main worksheet, a form frame is provided, and an attribute (value) can be set at the same field position in the format worksheet. Then, the job ID and document ID are specified, the individual management data 270 registered in the individual information storage unit 27 is extracted, and the attribute (value) is set from the approval management server 20 to the template file 265. Export to a spreadsheet file.

(Overview of the whole)
Next, the overall outline will be described with reference to FIG.
First, the control unit 21 of the approval management server 20 executes a system setting process (step S1-1). Specifically, the administrator uses the client terminal 10 to activate an approval management program stored in the approval management server 20. In this case, the setting management unit 211 of the control unit 21 of the approval management server 20 displays the initial setting screen 500 shown in FIG. 9A on the display of the client terminal 10. On this initial setting screen 500, initial settings can be made for business processes, ledgers, menus, system definitions, screen definitions, labels, messages, and mails. The initial setting screen 500 includes menu buttons for selecting business processes to mail. When a specific menu button is selected, a work screen for performing initial settings for the selected menu is displayed.

  On the work screen of the business process, the name of the business process, the description of the business process, the automatic numbering method, and the business steps included in the business process can be set. Further, a detailed work screen 510 described later in FIG. 10 is displayed for the set business step. By using this detailed work screen 510, a screen used at the time of application or approval can be generated.

On the ledger work screen, the ledger setting information for the job ledger and document ledger can be entered.
On the menu work screen, menu setting information for the menu screen when the user accesses can be input.

On the system definition work screen, system definition setting information regarding the operating environment of the approval management server 20 can be input.
In the screen definition work screen, screen definition setting information for controlling each execution screen can be input.

On the label work screen, it is possible to input label setting information about the label of the icon arranged on each screen.
On the message work screen, a message for executing the process can be input.
In the mail work screen, it is possible to input mail setting information regarding the contents of mail transmission.

When the initial setting completion input is performed on each work screen, the setting management unit 211 of the control unit 21 records each setting information in the setting information storage unit 22.
Here, a detailed work screen 510 used for setting a business process will be described with reference to FIG. In the detailed work screen 510, a screen (for example, a document registration screen 611) used for application or approval is generated. The detailed work screen 510 includes a screen configuration area 511, a field attribute setting area 512, and a step common setting area 513.

  In the screen configuration area 511, the layout of the screen displayed in the application or approval is set. This layout is composed of a plurality of fields arranged in a matrix. Then, each field is specified, and the contents of the field are specified in the field attribute setting area 512.

In the field attribute setting area 512, the following settings are performed.
In the “row” column and the “column” column, a field for setting an attribute is specified.
In the “type” column, the display format set in this field is designated. For example, “text”, “text (scroll)”, “dialog”, “drop-down”, and the like can be designated.

In the “Label” column, a label to be pasted in this field is set.
In the “attribute” column, the genus of the attribute (value) to be displayed or input is set in this field.

In the “attribute details” column, if the attribute requires a parameter name, the parameter name is selected or set.
In the “input restriction” column, the input condition of this field is set. Here, “required”, “arbitrary”, “display only”, “required (manual input not possible)”, “arbitrary (impossible manual input)”, etc. are selected.

In the “drop-down” column, an arbitrary drop-down name is designated when “drop-down” is selected in the “type” column.
In the “dialog” column, an arbitrary dialog name is set when “dialog” is selected in the “type” column.

In the “initial value” column, a default value in this field is set.
In the “height” column, the field height is set in pixels when “text (scroll)” is designated as the type.

  In the “minimum value” column and “maximum value” column, the minimum value and the maximum value allowed in this field are set. Registration or circulation start cannot be performed by entering a value that deviates from this range.

In the “Past Future” field, the extent to which the input date exceeds the current point is set as an error. In this case, “-n” is set if an error is to be input if a date that exceeds the past n days is input, and “n” is set to an error if a date that exceeds n days in the future is input.
In the “Help” column, a description for displaying the description of the value to be input in the field by mouse over is set. The “past future” column and the “help” column are displayed by scrolling the field attribute setting area 512.

In the step common setting area 513, the following settings are performed.
In the “step ID” column, an identifier for specifying a business step constituting the business process is set.

In the “step name” field, the name of the business step is set.
In the “Repeat Step” field, “Repeat” is selected when document registration is repeated in this business step.

In the “previous file copy” field, the step ID of the file copy source is set.
In the “file name” column, a template file name for creating a document is set.

In the “main sheet” field, the name of the worksheet in the template file for transferring or acquiring the value to the document is set.
In the “format” column, a worksheet name in a template file that defines a format for transferring or obtaining a value in a document is set.

  In the “Previous Step” field, when the document registration of this business step is restricted depending on the state of the previous step, the step ID of the previous business step that is a use condition is set.

In the “previous step state” column, the state in the previous business step is set as a use condition.
In the “document ID automatic numbering” column, when a document ID is automatically numbered at the time of document creation, the document ID automatic numbering rule is set.

In the “document subject automatic generation” column, a generation rule for automatically generating a document subject at the time of document generation is set.
In the “automatic numbering” field, when automatically assigning the file name of the created document, the numbering rule is set.

In the “Upload” column, whether to allow the user to change the file name when uploading a document is specified.
In the “Style” column, a screen style name is defined.
In “function of third button”, “circulation request” is selected when circulation is required for the document created in this step. Select “Register” if no circulation is required.

  In the “reference mode” column, when referring to the document registered from the approval screen or the ledger, it is selected whether the document registration screen 611 is displayed in the reference mode or the document is displayed.

In the “circulation route ID” column, an identifier (circulation route ID) for specifying the circulation route of the document created in this business step is set.
In the “circulation route ID (affiliation 1)” column, it is set when a circulation route is determined in advance for one affiliation unit.

In the “electronic stamp format” field, the electronic stamp format is set when the electronic stamp function is used.
In the “Create Document at Distribution” column, a step ID for automatically creating a document is set.

In the “approval deadline” column, an approval deadline for each step is set.
In the “next approval deadline (step)” column and the “next approval deadline (days)” column, a reminder function is set for each step.
In the “same affiliation control” column, the affiliation between the job creator and the document creator can be controlled.

  With this detailed work screen 510, a document registration screen 611 shown in FIG. 10 is generated and registered in the screen storage unit 26. As described with reference to FIG. 7, the document registration screen 611 includes a style sheet, and the attribute type and property set on the detailed work screen 510 are recorded for the field position. Then, the value (attribute) input on the document registration screen 611 is associated with the genus and registered in the individual information storage unit 27.

  Next, as shown in FIG. 8, the control unit 21 of the approval management server 20 executes a user registration process (step S1-2). Specifically, the administrator uses the client terminal 10 to instruct user registration. In this case, the setting management unit 211 of the control unit 21 outputs the user registration screen 501 shown in FIG. 9B to the display of the client terminal 10. On this user registration screen 501, registration, correction, and deletion of user information (applicant, approver, administrator) can be performed. In the user registration, data related to employee ID to authority group is registered as described above. In this case, the control unit 21 of the approval management server 20 records the registered user information in the user storage unit 23. In the correction and deletion, it is possible to specify a registered user and correct the registered content or delete the user registration.

Next, the control unit 21 of the approval management server 20 executes a circulation route registration process (step S1-3). Specifically, the administrator uses the client terminal 10 to instruct circulation route registration. In this case, the setting management unit 211 of the control unit 21 outputs a circulation route registration screen 502 shown in FIG. 9C to the display of the client terminal 10. On this circulation route registration screen 502, new registration, correction, duplication, and deletion of circulation routes for applications can be performed. In the case of new registration, set the circulation category, mandatory / optional designation, and employee name (user). In this case, the control unit 21 of the approval management server 20 records the set circulation route information in the circulation route storage unit 25.
Thus, the pre-registration for using the approval management server 20 is finished.

  When registering a job or document for application, the applicant accesses the approval management server 20 using the client terminal 10. Then, after performing user authentication, new registration is instructed in the work selection on the top screen 610.

  In this case, the control unit 21 of the approval management server 20 executes job registration processing (step S1-4). Specifically, the application management unit 214 of the control unit 21 generates individual management data 270 in which a job ID and a document ID are assigned to each genus and attribute combination set on the document registration screen 611. Register in the individual information storage unit 27. This process will be described later with reference to FIG. In the client terminal 10, the circulation start input is performed using the circulation start screen 612. Here, it is also possible to change the approver. This process will be described later with reference to FIG.

  The controller 21 of the approval management server 20 that has acquired the circulation start information executes a progress update process (step S1-5). Specifically, the application management unit 214 of the control unit 21 indicates “in progress” as the progress status of the individual management data 270 in which the job ID and document ID in which the circulation start is input are recorded in the individual information storage unit 27. ".

When approving the application, the approver uses the client terminal 10 to access the approval management server 20 to perform user authentication.
In this case, the control unit 21 of the approval management server 20 executes an approval process (step S1-6). Specifically, the screen control unit 213 of the control unit 21 displays a job progress management list recorded in the individual information storage unit 27 on the top screen 610. This process will be described later with reference to FIG. Then, the approver selects an approval target in the progress management list in the client terminal 10. Furthermore, using the approval screen 614, the application content is confirmed and approval input is performed. This process will be described later with reference to FIG.

  Next, the control unit 21 of the approval management server 20 executes a progress update process (step S1-7). Specifically, the approval management unit 215 of the control unit 21 registers “approved” as the progress status of the individual management data 270 in which the job ID and document ID that have been input for approval are recorded in the individual information storage unit 27. .

(Screen control processing)
Next, the screen control process will be described with reference to FIG. This screen control process is executed when the applicant registers a document or when the approver performs an approval process. In any case, the approval management server 20 is accessed using the client terminal 10.

  In this case, the control unit 21 of the approval management server 20 executes user authentication processing (step S2-1). Specifically, the user authentication unit 212 of the control unit 21 outputs a user authentication screen on the display of the client terminal 10 and acquires an employee code and an authentication code from the client terminal 10. Then, the user authentication unit 212 uses the directory management server 40 to collate the acquired employee code and authentication code. If the verification fails, login is rejected.

  When the user authentication is completed, the control unit 21 of the approval management server 20 executes a progress list display process (step S2-2). Specifically, the screen control means 213 of the control unit 21 displays a list of jobs waiting for the user on the top screen. This process will be described later with reference to FIG.

  Next, the control unit 21 of the approval management server 20 executes processing target selection processing from the progress list (step S2-3). Specifically, when the job displayed in the progress list is selected, the screen control unit 213 of the control unit 21 acquires the job ID and document ID of the selected application from the client terminal 10. When registering a job for a new application, a business process to be newly registered is selected on the top screen. In this case, the screen control unit 213 acquires the business ID of the business process selected on the client terminal 10.

  Next, the control unit 21 of the approval management server 20 executes a display screen usage control process (step S2-4). Specifically, when the screen control unit 213 of the control unit 21 acquires the job ID and document ID from the client terminal 10, the individual management in which the job ID and document ID are recorded from the individual information storage unit 27. Data 270 is extracted, and using the individual management data 270, the business ID and step ID for the current business step are specified. Next, the screen control unit 213 acquires screen data associated with the business ID and step ID from the screen storage unit 26. Then, use conditions (“previous step”, “previous step state”) are acquired in the properties of the screen data.

  Here, when the use condition is set, the screen control unit 213 specifies the status of the business step of the previous step ID in the individual information storage unit 27 in this job ID. Then, the screen control unit 213 makes the screen of the selected business step usable when the identified state of the previous business step matches the usage condition. If the usage conditions do not match, the screen control unit 213 rejects the processing of the business step.

  When a business ID for a new application is acquired from the client terminal 10, the screen control unit 213 uses the business process storage unit 24 to identify the business process management record 240 in which the selected business ID is recorded. To do. Next, the screen control unit 213 acquires screen data associated with the first step ID from the screen storage unit 26 in the business process management record 240.

  Next, the control unit 21 of the approval management server 20 executes an attribute acquisition process for the genus set on the screen (step S2-5). Specifically, the screen control unit 213 of the control unit 21 identifies the genus set in the style sheet of the screen that can be used in this business step. Further, the screen control unit 213 acquires, from the individual information storage unit 27, the attribute (value) associated with the job ID of the selected application as the management ID for the specified genus. Further, the screen control unit 213 acquires, from the individual information storage unit 27, the attribute (value) associated with the specified application job ID and document ID as the management ID for the specified genus.

  Next, the control unit 21 of the approval management server 20 executes screen display processing (step S2-6). Specifically, the screen control means 213 of the control unit 21 generates a display screen in which the acquired attribute (value) is pasted to the field in which the genus is set in the style sheet. Then, the screen control means 213 outputs the generated display screen to the display of the client terminal 10.

  Next, the client terminal 10 executes input processing (step S2-7). Specifically, in the client terminal 10, a desired attribute (value) is input to a specific field of the display screen output on the display. The client terminal 10 temporarily stores the input attribute (value).

  In this case, the client terminal 10 executes a property check process (step S2-8). Specifically, the client terminal 10 confirms the appropriateness of the input information using the property set in this field in the style sheet. If the conditions set in the property are satisfied, a success message of property check is output. On the other hand, if the condition set in the property is not met, an error message is output.

When the input is completed, the completion input is performed on the display screen.
In this case, the client terminal 10 executes a check entry omission check process for essential items (step S2-9). Specifically, the client terminal 10 uses the properties set in each field of the style sheet to check for missing attribute input for the essential genus. If the conditions set in the property are satisfied, a success message for missing check is output. On the other hand, if the condition set in the property is not met, an error message is output. In this embodiment, the property check and the omission check are performed in the client terminal 10, but may be performed in the control unit 21 of the approval management server 20. In this case, the screen control means 213 of the control unit 21 obtains information input from the client terminal 10 and compares it with the property of each field to perform property check and omission check.

  Next, the control unit 21 of the approval management server 20 executes a data registration process (step S2-10). Specifically, the screen control unit 213 of the control unit 21 acquires data input in the client terminal 10. Here, an attribute (value) is acquired in association with a genus species. Then, the screen control unit 213 generates the individual management data 270 in which the attribute (value) is recorded in association with the genus type in association with the job ID and the document ID, and registers them in the individual information storage unit 27.

  Next, the control unit 21 of the approval management server 20 executes a progress update process (step S2-11). Specifically, the screen control unit 213 of the control unit 21 updates “being created” as the progress status of the individual management data 270 for this job stored in the individual information storage unit 27.

(Application registration process)
Next, the application registration process will be described with reference to FIG. Here, it is executed when new registration is selected on the top screen displayed on the display of the client terminal 10. In this case, the screen control unit 213 of the control unit 21 outputs the document registration screen 611 to the display of the client terminal 10.

  First, the control unit 21 of the approval management server 20 executes application acceptance processing (step S3-1). Specifically, the screen control unit 213 of the control unit 21 acquires the application content set on the document registration screen 611. In this case, the screen control unit 213 takes over the process to the application management unit 214.

  Next, the control unit 21 of the approval management server 20 executes business process identification processing based on the application (step S3-2). Specifically, the application management unit 214 of the control unit 21 identifies a business process based on the business ID on the document registration screen 611.

  Next, the control unit 21 of the approval management server 20 executes a normal grace period setting process for each approver (step S3-3). Specifically, the application management unit 214 of the control unit 21 acquires the circulation route in the identified business process from the circulation route storage unit 25. Next, the application management unit 214 identifies the post of each approver included in the circulation route. Then, the application management unit 214 acquires a grace period associated with each specified position from the grace period table.

  Next, the control unit 21 of the approval management server 20 executes a final approval scheduled date calculation process (step S3-4). Specifically, the application management unit 214 of the control unit 21 acquires the current date from the system timer, and sequentially adds a grace period to each approver included in the circulation route with respect to the current date. Calculate the approval deadline. Then, the application management unit 214 calculates the approval deadline of the final approver as the final approval scheduled date.

  Next, the control unit 21 of the approval management server 20 executes output processing for the final approval scheduled date (step S3-5). Specifically, the application management unit 214 of the control unit 21 outputs a confirmation screen on the display of the client terminal 10. This confirmation screen includes an icon for selecting whether or not adjustment is necessary for the final approval date as well as the calculated final approval date. Furthermore, when the application final approval date is registered in the individual management data 270 recorded in the individual information storage unit 27, the application management unit 214 compares the final approval approval date with the final approval approval date. . When the final approval date is later than the final approval date, a message for calling attention is included in the confirmation screen.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether or not deadline adjustment is necessary (step S3-6). Specifically, the application management unit 214 of the control unit 21 determines whether adjustment is necessary based on the icon selected on the confirmation screen.

  When the “adjustment unnecessary” icon is selected and it is determined that the deadline adjustment is not necessary (in the case of “NO” in step S3-6), the control unit 21 of the approval management server 20 executes registration processing for each approval deadline. (Step S3-7). Specifically, the application management unit 214 of the control unit 21 associates the approval deadline calculated for each approver included in the circulation route with the employee code of each approver in the individual information storage unit 27. sign up. Specifically, the individual management data 270 in which the employee ID of the approver and the approval deadline for each business step are recorded as attributes for each business step is generated and recorded in the individual information storage unit 27.

  On the other hand, when the “adjustment necessary” icon is selected and it is determined that the deadline adjustment is necessary (in the case of “YES” in step S3-6), the control unit 21 of the approval management server 20 executes the adjustment screen output process. (Step S3-8). Specifically, the application management unit 214 of the control unit 21 outputs a time limit adjustment screen on the display of the client terminal 10. This deadline adjustment screen includes the approval deadline calculated for each approver. Then, this approval deadline is allowed to be corrected in the client terminal 10. The applicant adjusts the approval deadline of each approver on the adjustment screen output on the display of the client terminal 10 in consideration of the scheduled final approval date.

  Next, the control unit 21 of the approval management server 20 executes registration processing for each adjusted approval deadline (step S3-9). Specifically, the application management unit 214 of the control unit 21 acquires the approval deadline set on the deadline adjustment screen from the client terminal 10. Then, the application management unit 214 records the adjusted approval deadline in the individual information storage unit 27 in association with the employee code of each approver. Here, individual management data 270 in which the approver's employee ID and the approval deadline for each business step are recorded as attributes for each business step is generated and recorded in the individual information storage unit 27.

(Approver change process)
Next, the approver change process will be described with reference to FIG. Here, it is assumed that the approver set in the normal circulation route is changed to another approver.

  First, the controller 21 of the approval management server 20 executes an approver change input process (step S4-1). Specifically, the application to be changed is specified on the circulation progress detail screen 616 displayed on the display of the client terminal 10. Then, using the client terminal 10, an approver change icon is selected. In this case, the screen control unit 213 of the control unit 21 outputs the approver change screen 617 on the display of the client terminal 10. Then, the user designates a new approver on the approver change screen 617.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether the affiliation belongs to the same department (step S4-2). Specifically, the application management unit 214 of the control unit 21 acquires the newly registered approver user management record 230 and the original approver user management record 230 from the user storage unit 23. Then, the application management unit 214 uses the acquired user management record 230 to compare the department of the newly registered approver with the department of the original approver.

  When it is determined that the newly registered approver's department and the approver's department before the change are not the same (if “NO” in step S4-2), the control unit 21 of the approval management server 20 Then, a confirmation notification process is executed (step S4-3). Specifically, the application management unit 214 of the control unit 21 acquires the mail address of the approver before the change from the user management record 230. Then, the application management unit 214 transmits an e-mail for notifying that a change input has been made to this e-mail address. The original approver who confirmed this e-mail determines whether or not the change can be made. If there is no problem, a change permission notification is returned to the approval management server 20. When the change permission notification is received from the client terminal 10 of the approver before the change, the control unit 21 of the approval management server 20 executes the processes after step S4-6.

  On the other hand, when it is determined that the department to which the newly registered approver belongs and the department to which the approver before the change belongs are the same (in the case of “YES” in step S4-2), the control unit 21 of the approval management server 20 Performs a determination process as to whether or not the authority level is equal or higher (step S4-4). Specifically, the application management unit 214 of the control unit 21 uses the acquired user management record 230 to compare the newly registered position of the approver and the position of the approver before the change.

  When it is determined that the position of the newly registered approver is lower than the position of the approver before the change and the authority level is low (in the case of “NO” in step S4-4), the control unit 21 of the approval management server 20 Executes change rejection processing (step S4-5). Specifically, the application management unit 214 of the control unit 21 outputs a message indicating that the approver cannot be changed to the client terminal 10.

  On the other hand, when it is determined that the newly registered approver's title is higher than or equal to the post of the approver before the change and the authority level is equal to or higher (in the case of “YES” in step S4-4), the approval management server 20 The control unit 21 executes change registration processing (step S4-6). Specifically, the application management unit 214 of the control unit 21 newly adds the employee code of the designated approver before the change in the individual management data 270 in which the job ID is recorded in the individual information storage unit 27. Change to the employee code of the specified approver.

  Next, the control unit 21 of the approval management server 20 executes a normal grace period setting process for each approver (step S4-7). Specifically, the application management unit 214 of the control unit 21 identifies an approver who is an indispensable approver and has not been approved. Then, the application management unit 214 acquires a grace period corresponding to each approver's position from the grace period table.

  Next, the control unit 21 of the approval management server 20 executes a final approval scheduled date calculation process (step S4-8). Specifically, the application management unit 214 of the control unit 21 obtains the current date and time from the system timer, and calculates the final approval scheduled date by adding the grace period of the unapproved approver.

  Next, similarly to steps S3-6 to S3-9, the control unit 21 of the approval management server 20 determines whether or not deadline adjustment is necessary (step S4-9), registration processing for each approval deadline (steps). S4-10), adjustment screen output processing (step S4-11), and adjustment processing for each approved approval deadline (step S4-12).

(Progress list management process)
Next, the progress list management process will be described with reference to FIG.
First, the control unit 21 of the approval management server 20 executes a user specifying process (step S5-1). Specifically, the user authentication unit 212 of the control unit 21 specifies the user by performing user authentication based on the employee code and the authentication code acquired from the client terminal 10.

  Next, the control unit 21 of the approval management server 20 executes an application extraction process in which the user is an approver (step S5-2). Specifically, the screen control means 213 of the control unit 21 extracts the individual management data 270 of the job in which the employee code of the authenticated user is registered as the approver in the individual information storage unit 27. Then, the screen control unit 213 identifies the job ID based on the management ID recorded in the extracted individual management data 270.

  Next, the control unit 21 of the approval management server 20 executes an approval schedule list creation process (step S5-3). Specifically, the screen control unit 213 of the control unit 21 creates an approval schedule list in which the extracted jobs are displayed as a list. Here, the screen control unit 213 extracts the individual management data 270 in which the job ID is recorded from the individual information storage unit 27. Then, the screen control means 213 displays the progress status of each job using the individual management data 270 in this approval schedule list.

  Next, the control unit 21 of the approval management server 20 executes a rearrangement process in the order of close approval deadlines (step S5-4). Specifically, the screen control means 213 of the control unit 21 uses the extracted individual management data 270 to specify the approval deadline of each job that is waiting for work for this user. Then, the screen control unit 213 rearranges the jobs in order from the approval schedules with the closest approval deadlines.

  Next, the control unit 21 of the approval management server 20 executes an approval schedule list display process (step S5-5). Specifically, the screen control means 213 of the control unit 21 outputs the created approval schedule list as “waiting for work” on the top screen 610.

(Processing at the time of approval)
Next, the approval process will be described with reference to FIG. Here, it is executed when the approver inputs the approval.

  First, the control unit 21 of the approval management server 20 executes an acquisition process of approval information (step S6-1). Specifically, the screen control means 213 of the control unit 21 acquires the approval information input on the approval screen from the client terminal 10 of the approver. In this case, the screen control unit 213 takes over the process to the approval management unit 215.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether or not all business steps have been completed (step S6-2). Specifically, the approval management means 215 of the control unit 21 makes a determination based on the progress status of the individual management data 270 recorded in the individual information storage unit 27. Here, in the business step recorded in the business process storage unit 24, when the approval of all the circulation destinations is completed, it is determined that all the business steps have been completed.

  When it is determined that all business steps are finished (in the case of “YES” in step S6-2), the control unit 21 of the approval management server 20 executes a completion notification process (step S6-3). Specifically, the approval management means 215 of the control unit 21 specifies the employee code of the applicant using the individual management data 270 recorded in the approved job ID in the individual information storage unit 27. Next, the approval management unit 215 extracts the user management record 230 in which the identified employee code is recorded from the user storage unit 23, and acquires an email address. Then, the approval management means 215 transmits an e-mail for notifying that the final approval has been completed to this e-mail address.

  On the other hand, when it is determined that all business steps have not been completed (in the case of “NO” in step S6-2), the control unit 21 of the approval management server 20 determines whether or not the current business step has been completed. Is executed (step S6-4). Specifically, the approval management unit 215 of the control unit 21 makes a determination based on the progress status specified in the individual information storage unit 27 using the individual management data 270 in which the approved job ID is recorded. Here, in the current business step, if the approval of the circulation destination whose circulation category is essential is completed, it is determined that the current business step is completed.

  When it is determined that the current business step has been completed (in the case of “YES” in step S6-4), the control unit 21 of the approval management server 20 executes a deployment process to the next business step (step S6-5). ). Specifically, the approval management means 215 of the control unit 21 specifies the next business step of this job in the business process storage unit 24. On the other hand, when it is determined that the current business step has not been completed (in the case of “NO” in step S6-4), the control unit 21 of the approval management server 20 expands the next business step (step S6- 5) is skipped.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether or not there is a deployable circulation destination (step S6-6). Specifically, the approval management unit 215 of the control unit 21 uses the individual management data 270 in which the approved job ID is recorded when the current job step is not finished, The next circulation destination is searched in. In addition, when expanded to the next business step, the first circulation destination is searched in a new business step.

When it is determined that there is no distribution destination that can be expanded (NO in step S6-6), the control unit 21 of the approval management server 20 ends the approval process.
On the other hand, when it is determined that there is a distributable distribution destination (in the case of “YES” in step S6-6), the control unit 21 of the approval management server 20 performs a determination process as to whether the distribution destination is an approver. Execute (Step S6-7). Specifically, the approval management means 215 of the control unit 21 specifies the circulation category of the next circulation destination in the circulation route storage unit 25, and determines whether or not the person is the approver based on the circulation category.

  If it is determined that the circulation destination is not an approver (“NO” in step S6-7), the control unit 21 of the approval management server 20 executes a circulation registration process (step S6-8). . Specifically, the approval management unit 215 of the control unit 21 circulates as a progress status to a new distribution destination of the individual management data 270 in which the job ID and document ID are recorded in the individual information storage unit 27. Register the status (contacted, distributed, etc.).

  On the other hand, when it is determined that the distribution destination is the approver (“YES” in step S6-7), the control unit 21 of the approval management server 20 executes the readjustment process for the approval deadline (step S6-9). . Specifically, the approval management means 215 of the control unit 21 acquires the current date from the system timer.

  Next, the approval management unit 215 acquires a grace period for the subsequent approver from the grace period table. Then, the approval management unit 215 adds the grace period sequentially for each approver for the current date, recalculates the approval deadline, and the individual information storage unit 27 records the approval deadline. The management data 270 is updated.

  Next, the control unit 21 of the approval management server 20 executes a deployment registration process for the next approver (step S6-10). Specifically, the approval management means 215 of the control unit 21 registers the waiting for work in the individual management data 270 in which the progress status of the approver is recorded in the individual information storage unit 27.

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, a business process is composed of a plurality of business steps. In each business step, circulation (contact and approval) to departments, positions and individuals determined in the circulation route is performed. In the approval process, when it is determined that all business steps have not been completed (in the case of “NO” in step S6-2), it is determined that the current business step has been completed (step S6-). 4, in the case of “YES”), the control unit 21 of the approval management server 20 executes the expansion process to the next business step (step S <b> 6-5). Thus, by configuring a single business process from a plurality of business steps, it is possible to ensure a degree of freedom in configuring the business process. Therefore, a new business process can be efficiently created by combining existing business steps.

  (2) In this embodiment, the value (attribute) input on the document registration screen 611 is associated with the genus and registered in the individual information storage unit 27. In the individual information storage unit 27, individual management data 270 for managing a job for which approval has been applied is recorded. The individual management data 270 includes data related to the management ID, genus species, and attributes. Thereby, since the genus species and the attribute (value) are stored in association with each other, the degree of freedom in changing the data configuration such as increasing the genus species can be increased. Therefore, it is possible to reduce the load of data structure correction work.

  (3) In the present embodiment, the control unit 21 of the approval management server 20 executes a display screen usage control process (step S2-4). Specifically, the screen control unit 213 of the control unit 21 acquires the usage conditions (“previous step”, “previous step state”) in the properties of the screen data recorded in the screen storage unit 26. If the usage conditions are set, the screen control unit 213 specifies the status of the business step of the previous step ID in the individual information storage unit 27 in this job ID. Then, the screen control unit 213 makes the screen of the selected business step usable when the identified state of the previous business step matches the usage condition. As a result, it is possible to limit information input and display in the business step using the property set in the screen data.

  (4) In this embodiment, the control part 21 of the approval management server 20 performs a screen display process (step S2-6). Specifically, the screen control means 213 of the control unit 21 generates a display screen in which the acquired attribute (value) is pasted to the field in which the genus is set in the style sheet. Thereby, a display screen can be output using the attribute (value) recorded in the individual information storage unit 27.

  (5) In this embodiment, the control unit 21 of the approval management server 20 executes a normal grace period setting process for each approver (step S3-3). Thereby, according to an approver's attribute, the approval time limit of each approver can be set.

  (6) In the present embodiment, the control unit 21 of the approval management server 20 executes output processing for the final approval scheduled date (step S3-5). When the “adjustment necessary” icon is selected and it is determined that deadline adjustment is necessary (in the case of “YES” in step S3-6), the control unit 21 of the approval management server 20 executes an adjustment screen output process ( Step S3-8). Thereby, the approval deadline of each approver can be adjusted in consideration of the final approval scheduled date.

  (7) In this embodiment, when it is determined in the approver change process that the newly registered approver's department and the approver's department before the change are not the same ("NO" in step S4-2) ”), The control unit 21 of the approval management server 20 executes a confirmation notification process (step S4-3). This allows the application to be deployed to other departments with the consent of the original approver.

  (8) In this embodiment, when it is determined in the approver change process that the newly registered approver's job title is higher than the approver job before the change and the authority level is equal or higher (step S4-4). In the case of “YES”), the control unit 21 of the approval management server 20 executes a change registration process (step S4-6). Thereby, the approver can be changed efficiently according to the authority level.

  (9) In this embodiment, in the approver change process, the control unit 21 of the approval management server 20 executes a process for calculating the final approval date (step S4-8). Then, the control unit 21 of the approval management server 20 determines whether or not deadline adjustment is necessary (step S4-9), registration processing for each approval deadline (step S4-10), and adjustment screen output processing (step S4). -11) The registration process of each adjusted approval deadline (step S4-12) is executed. Thereby, even when the approver is changed, the approval deadline can be adjusted in consideration of the scheduled final approval date.

  (10) In the present embodiment, in the progress list management process, the control unit 21 of the approval management server 20 executes the rearrangement process in the order of the approval deadlines (step S5-4). Thereby, the approver can perform the approval work in consideration of the approval deadline.

  (11) In the present embodiment, in the approval process, the control unit 21 of the approval management server 20 executes an approval deadline readjustment process (step S6-9). Thereby, the approval deadline of the subsequent circulation destination can be adjusted according to the progress status.

In addition, you may change each said embodiment as follows.
In the above embodiment, in the progress list management process, the rearrangement process is executed in the order in which the approval deadlines are close (step S5-4). In addition to this, the approver may be alerted according to the approver's schedule. In this case, a schedule management server for managing a user (employee) schedule is used. In this schedule management server, event periods that cannot be approved, such as vacation and business trip schedule information, are registered in association with the employee code of the user. Then, the progress list management process shown in FIG. 16 is executed.

  Here, similarly to steps S5-1 to S5-4, the control unit 21 of the approval management server 20 performs the sorting process (step S7-) in the order from the user specifying process (step S7-1) to the approval deadline. 4) is executed.

  Next, the control unit 21 of the approval management server 20 executes a user schedule acquisition process (step S7-5). Specifically, the screen control means 213 of the control unit 21 acquires the approver's schedule (event period) from the schedule management server for the period from the current date to the latest approval deadline.

  Next, the control unit 21 of the approval management server 20 executes a collation process between the schedule and the approval deadline (step S7-6). Specifically, the screen control unit 213 of the control unit 21 uses the individual management data 270 in which the job ID of each job is recorded in the individual information storage unit 27 to approve the preceding approver immediately before this approver. Get a deadline. Next, the screen control unit 213 calculates an approval period from the approval date limit of the preceding approver to the approval date limit of the approver. Then, the screen control unit 213 compares the calculated approval period with an event period in which an event that cannot be approved is registered.

  Next, the control unit 21 of the approval management server 20 executes an alerting process (step S7-7). Specifically, the screen control means 213 of the control unit 21 identifies an application whose approval period is satisfied with the event period. Then, the screen control unit 213 adds caution information in the approval schedule list to the identified application.

And the control part 21 of the approval management server 20 performs the display process of an approval schedule list similarly to step S5-5 (step S7-8).
Thereby, it is possible to alert an application that is difficult to approve in consideration of the approver's schedule.

  This alerting may be performed in the application registration process. Specifically, when the approval deadline of each approver is calculated for the application, the application management unit 214 of the control unit 21 acquires the schedule of each approver. Next, the application management unit 214 calculates the approval period of each approver (the period from the approval date of the previous approver to the approval date of each approver). Next, the application management unit 214 acquires the schedule (event period) of each approver from the schedule management server. And it compares with the event period when the event which cannot respond to approval in each approver was registered. Here, the application management unit 214 alerts the applicant when the approval period is satisfied by the event period.

  Further, the timing for making this alert is not limited to the progress list management process. For example, it may be performed when the approver is changed during the business process or when an event period during which the approver cannot approve is registered. Specifically, when the approval management unit 215 of the control unit 21 detects a change of the approver or an event registration of each approver, the individual management in which the approver is registered using the individual information storage unit 27. Data 270 is searched. Then, the approval management unit 215 uses the extracted individual management data 270 to compare the approval period of the approver with the event period. Then, the approval management means 215 alerts the applicant when the approval period is satisfied with the event period.

  In the above embodiment, the approval deadline of each approver is calculated using the grace period table. In this grace period table, data relating to a grace period for calculating an approval deadline from the current date is recorded in association with the position of each approver. Here, the grace period may be changed according to the approver's schedule. In this case, event information registered for each approver is acquired from the schedule management server. In each approver, the grace period is extended or shortened so that the event periods do not overlap with respect to all the approval periods. Thereby, the approval time limit according to an approver's schedule can be set.

  In the above embodiment, in the progress list management process, the control unit 21 of the approval management server 20 executes a display process of the approval schedule list (step S5-5). Here, in the case where an advance explanation is given to the approver for the application content, a prior explanation may be displayed in the approval schedule list. In this case, in the application registration process, the approver included in the circulation route is specified, and the pre-explained information is input for the approver who made the prior explanation. In this case, the previously explained flag is recorded in the individual management data 270 in which the job ID and the approver's employee code are recorded in the individual information storage unit 27. Then, the screen control means 213 of the control unit 21 outputs the pre-explained information to the approver's approval schedule list in which the pre-explained flag is recorded. As a result, the approver can efficiently approve in consideration of the prior explanation.

  Further, for the approver in which the pre-explained flag is recorded, the grace period for calculating the approval deadline may be shortened. In this case, information for calculating the shortened grace period is registered in the grace period table for the application that has been explained in advance. And the application management means 214 of the control part 21 calculates the shortened grace period about the approver in which the prior explained flag was recorded in step S4-7. Thereby, when prior explanation is given, quick circulation can be performed by advancing the approval deadline.

  In the above embodiment, in the progress list management process, the rearrangement process is executed in the order in which the approval deadlines are close (step S5-4). In addition to this, an approval schedule list may be created in consideration of personnel changes. In this case, a personnel management server that manages personnel changes of users (employees) is used. In this personnel management server, the scheduled transfer date and personnel details are registered in association with the employee code of the user. Then, the progress list management process shown in FIG. 17 is executed.

  Here, similarly to steps S5-1 to S5-4, the control unit 21 of the approval management server 20 performs the sorting process (step S8-) in the order from the user specifying process (step S8-1) to the approval deadline. 4) is executed.

  Next, the control unit 21 of the approval management server 20 executes personnel change information acquisition processing (step S8-5). Specifically, the screen control means 213 of the control unit 21 accesses the personnel management server and acquires personnel change information (scheduled change date and destination) of this user (here, the approver).

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether or not there is a change schedule (step S8-6). Specifically, the screen control unit 213 of the control unit 21 determines whether or not there is a personnel change of the approver based on the personnel change information acquired from the personnel management server.

  When it is determined that there is a change schedule (in the case of “YES” in step S8-6), the control unit 21 of the approval management server 20 executes a process for specifying an application whose approval deadline is within a predetermined number of days from the scheduled transfer date ( Step S8-7). Specifically, the screen control means 213 of the control unit 21 calculates the approval period from the approval deadline of the immediately preceding approver to the approval deadline of this approver. Then, the screen control unit 213 compares the scheduled change date included in the personnel change information with the approval period, and identifies an application whose scheduled change date is included in the approval period.

  Next, the control unit 21 of the approval management server 20 executes a warning process (step S8-8). Specifically, the screen control means 213 of the control unit 21 adds caution information indicating that the scheduled change date is close in the approval schedule list to the specified application.

  Next, the control unit 21 of the approval management server 20 executes an identification process for an application whose approval deadline is later than a predetermined number of days from the scheduled transfer date (step S8-9). Specifically, the screen control unit 213 of the control unit 21 identifies an application whose approval deadline (first day of the approval period) of the immediately preceding prior approver is later than the scheduled transfer date.

  Next, the control unit 21 of the approval management server 20 executes a deletion process from the approval schedule list (step S8-10). Specifically, the screen control unit 213 of the control unit 21 deletes the identified application from the approval schedule list.

  When it is determined that there is no change schedule (in the case of “NO” in step S8-6), the control unit 21 of the approval management server 20 skips the processes of steps S8-7 to S8-10. In addition, even if there is a personnel change schedule, in the case of promotion in the same department, the processing in steps S8-7 to S8-10 may be skipped.

Next, the control part 21 of the approval management server 20 performs the display process of an approval schedule list similarly to step S5-5 (step S8-11).
Thereby, when personnel changes are near, prompt approval can be promoted by alerting the approver. In addition, an application in which an approver may change at the time of approval can be prevented from being shown to a person who is scheduled to change.

  This alerting may be performed in the application registration process. Specifically, when the approval deadline of each approver is calculated for the application, the screen control unit 213 acquires the transfer information of each approver. Next, the screen control means 213 calculates the approval period of each approver (the period from the approval deadline of the previous approver to the approval deadline of each approver), and the scheduled transfer date included in the transfer information of each approver Compare. The screen control unit 213 alerts the applicant when the application from the scheduled transfer date to the approval deadline is within the standard number of days or when the scheduled transfer date is later than the approval period.

  In the above embodiment, in the application registration process, the control unit 21 of the approval management server 20 executes a final approval scheduled date calculation process (step S3-4) and a final approval scheduled date output process (step S3-5). To do. And based on the input in the client terminal 10, the control part 21 of the approval management server 20 performs the determination process about whether deadline adjustment is required (step S3-6). Here, the approval management server 20 may adjust the approval deadline. In this case, the individual management data 270 in which the management ID (job ID) and the desired final approval date are recorded is registered in the individual information storage unit 27 at the time of application. Furthermore, the compression rate for shortening the grace period is recorded in the grace period table. Then, the application registration process shown in FIG. 18 is executed.

  Here, similarly to steps S3-1 to S3-4, the control unit 21 of the approval management server 20 receives an application reception process (step S9-1), and identifies a business process based on the application (step S9-2). ), A process for setting a normal grace period for each approver (step S9-3) and a process for calculating a final approval date (step S9-4) are executed.

  Next, the control unit 21 of the approval management server 20 performs a determination process as to whether or not it is in time for the final approval desired date (step S9-5). Specifically, the application management means 214 of the control unit 21 uses the individual information storage unit 27 to obtain the final approval desired date from the individual management data 270 in which the job ID for this application is recorded, and to calculate the final Compare with the date of approval.

  When it is determined that the final approval date is before the final approval date and is in time for the final approval date (“YES” in step S9-5), the control unit 21 of the approval management server 20 performs step S3-7. Similarly, the registration process for each approval deadline is executed (step S9-6).

  On the other hand, when it is determined that the final approval date is later than the final approval date and is not in time for the final approval date (“NO” in step S9-5), the control unit 21 of the approval management server 20 The grace period compression process is executed every time (step S9-7). Specifically, the application management unit 214 of the control unit 21 calculates a modified grace period obtained by multiplying the grace period recorded in the grace period table by a predetermined compression rate.

  Next, the control unit 21 of the approval management server 20 executes recalculation processing of the final approval scheduled date (step S9-8). Specifically, the application management unit 214 of the control unit 21 sequentially calculates an approval deadline obtained by adding a correction grace period to each approver included in the circulation route with respect to the current date. Then, the application management unit 214 again calculates the approval deadline of the final approver as the final approval scheduled date.

Next, the control part 21 of the approval management server 20 performs the determination process about whether it is in time for the final approval desired date similarly to step S9-5 (step S9-9).
When it is determined that the final approval date is before the final approval date and is in time for the final approval date (in the case of “YES” in step S9-9), the control unit 21 of the approval management server 20 determines each approval time limit. Registration processing is executed (step S9-6).

On the other hand, when it is determined that the final approval date is later than the final approval date and is not in time for the final approval date (“NO” in step S9-9), the control unit 21 of the approval management server 20 performs step S3. Similarly to S-8 and S3-9, an adjustment screen output process (step S9-10) and a registration process of each adjusted approval deadline (step S9-11) are executed.
Thereby, the grace period can be adjusted and the approval deadline which meets the final approval desired date can be set according to the situation.

  Further, the final approval scheduled date may be periodically recalculated during the business process. Then, when the final approval date calculated by applying the normal grace period is in time for the final approval desired date, the approval deadline of each approver is reset using the normal grace period. As a result, when the approval is made ahead of schedule, it can be returned to the normal grace period.

  In the above embodiment, the approval deadline of each approver is calculated using the grace period table. Here, a plurality of business steps may be performed in parallel in one business process. In this case, the approval deadline may be calculated in consideration of business steps performed in parallel. Here, the critical path until the final approval is specified, and the approval deadline of each business step is set using the required period of the business step that constitutes the critical path. This application registration process will be described with reference to FIG.

  Here, the control unit 21 of the approval management server 20 receives the application reception process (step S10-1) and the business process identification process based on the application (step S10-) as in steps S3-1 and S3-2. 2) is executed.

  Next, the control unit 21 of the approval management server 20 executes a required period calculation process for each business step (step S10-3). The approver included in each business step is specified, and the grace period of each approver is calculated using the grace period table. Then, the application management unit 214 sums up the grace period for each business step and calculates the required period for each business step.

  Next, the control unit 21 of the approval management server 20 executes critical process identification processing for the business process (step S10-4). Specifically, the application management unit 214 of the control unit 21 specifies a business step having a common “previous step” in the property of the document registration screen 611. Then, when the same business step is used as a use condition, the application management unit 214 identifies these business steps as business steps (parallel business steps) performed in parallel. Then, the application management unit 214 compares the required time periods of the identified business steps, and specifies the longer required time period as a critical path.

  Next, the control unit 21 of the approval management server 20 executes an approval deadline setting process for the approver included in the critical path (step S10-5). Specifically, the application management unit 214 of the control unit 21 calculates the approval deadline using the grace period of the approver included in the business step of the identified critical path. Then, the application management unit 214 registers this approval deadline in the individual management data 270 of the individual information storage unit 27.

  Next, the control unit 21 of the approval management server 20 executes an approval deadline setting process for the parallel job step (step S10-6). Specifically, the application management unit 214 of the control unit 21 sets the approval deadline of the parallel job step in the individual management data 270 of the individual information storage unit 27 according to the approval deadline of the critical path job step.

  Next, the control part 21 of the approval management server 20 performs the calculation process of the last approval scheduled date similarly to step S3-4 (step S10-7). In this case, the final approval date is calculated using the grace period of the business step included in the critical path.

Then, similarly to steps S3-6 to S3-9, the control unit 21 of the approval management server 20 determines whether or not deadline adjustment is necessary (step S10-8), registration processing for each approval deadline (step S10). -9), an adjustment screen output process (step S10-10), and a registration process (step S10-11) for each adjusted approval deadline.
Thereby, the approval deadline can be set in consideration of the critical path.

  In the above embodiment, an approval schedule list waiting for work is displayed in the progress list management process. In addition to this, when there is no time margin before the approval deadline, the approver may be alerted. In this case, a warning message is transmitted to the e-mail address of the approver. The confirmation process of the approval deadline will be described with reference to FIG.

  Here, first, the control unit 21 of the approval management server 20 executes a deadline imminent job extraction process (step S11-1). Specifically, the approval management means 215 of the control unit 21 acquires the current date and time from the system timer. Next, the approval management unit 215 uses the individual management data 270 recorded in the individual information storage unit 27 to compare the approval deadline with the current date and time for each application. If the time margin from the current date to the approval deadline is equal to or less than the reference value, the approval management unit 215 extracts the job as a deadline imminent job.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether there is a deadline job (step S11-2). Specifically, the approval management unit 215 of the control unit 21 determines that there is an expiring job when an application whose time margin from the current date to the approval deadline is less than or equal to a reference value is specified.

If it is determined that there is no deadline imminent job (in the case of “NO” in step S11-2), the control unit 21 of the approval management server 20 ends the confirmation process of the approval deadline.
On the other hand, if it is determined that there is a deadline imminent job ("YES" in step S11-2), the control unit 21 of the approval management server 20 executes mail transmission processing (step S11-3). Specifically, the approval management unit 215 of the control unit 21 acquires the mail address of the approver of the deadline imminent job from the user storage unit 23. Then, the approval management means 215 transmits an e-mail for notifying that there is a deadline job to this e-mail address.

Then, the following processing is repeated for each deadline imminent job.
The control unit 21 of the approval management server 20 executes standby processing (step S11-4). Specifically, the approval management means 215 of the control unit 21 waits for a predetermined period after transmitting the e-mail. Here, the approver's client terminal 10 receives an e-mail for notifying that there is a deadline job, and the approver opens the e-mail. In this case, the client terminal 10 transmits an opening notification to the approval management server 20. The control unit 21 of the approval management server 20 that has received the opening notification records the reception confirmation information in the individual management data 270 of the individual information storage unit 27 in association with the job ID and document ID of the deadline imminent job.

  Next, the control unit 21 of the approval management server 20 executes a determination process as to whether or not reception has been confirmed (step S11-5). Specifically, the approval management means 215 of the control unit 21 determines that the reception has been confirmed when the reception confirmation information is registered in the individual management data 270 of the individual information storage unit 27.

If it is determined that the reception has been confirmed (in the case of “YES” in step S11-5), the process for this deadline imminent job is terminated.
On the other hand, when it is determined that the reception has not been confirmed (in the case of “NO” in step S11-5), the control unit 21 of the approval management server 20 executes another contact method specifying process (step S11-6). Specifically, the approval management unit 215 of the control unit 21 acquires other contact information associated with the employee code of the approver from the directory management server 40.

Next, the control part 21 of the approval management server 20 performs a contact process (step S11-7). Specifically, the approval management unit 215 of the control unit 21 transmits a message indicating that there is a deadline job using the acquired other contact information.
As a result, approval of a deadline imminent job can be urged.

  In addition to the mail transmission process (step S11-3), such an e-mail may be transmitted a plurality of times. For example, it is transmitted not only before the approval deadline but also at a predetermined time after the approval deadline has passed. Further, the e-mail may be transmitted a plurality of times before the approval deadline or after the approval deadline has passed. In this case, the e-mail transmission timing is recorded in the mail setting information recorded in the setting information storage unit 22.

  Further, the transmission content, destination, and transmission setting may be changed according to the transmission timing. Also in this case, the setting information storage unit 22 records the transmission content, the destination, and the transmission setting in the mail setting information in association with the transmission timing. Here, in the transmission contents, the text and title are changed. The destination is set to be transmitted not only to the approver himself but also to the related parties (for example, a boss or an administrator) according to the transmission timing (for example, re-transmission). In this case, the control unit 21 of the approval management server 20 acquires e-mail addresses of related persons of the approver from the user storage unit 23 based on the affiliation and job title of the approver. Further, in the transmission setting after the expiration of the deadline, a reception notification (open notification) setting or importance setting may be performed according to the transmission timing.

  In the above embodiment, the control unit 21 of the approval management server 20 executes a warning process (step S7-7). The output destination of the caution information is not limited to the approver's client terminal 10, and may be output to the applicant's client terminal 10, for example. In this case, the control unit 21 of the approval management server 20 periodically compares the approval deadline of various applications with the current date. When the control unit 21 of the approval management server 20 detects an application that cannot be approved, the control unit 21 specifies the contact information of the applicant of this application and transmits an e-mail for alerting.

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Approval management server, 21 ... Control part, 211 ... Setting management means, 212 ... User authentication means, 213 ... Screen control means, 214 ... Application management means, 215 ... Approval management means, 22 ... Setting information Storage unit, 23 ... user storage unit, 24 ... business process storage unit, 25 ... circulation route storage unit, 26 ... screen storage unit, 27 ... individual information storage unit, 40 ... directory management server.

Claims (10)

For the applicant's application, a business process storage unit that records a business process that combines multiple business steps,
For each business step, a circulation route storage unit that records a circulation route for specifying a circulation destination in turn,
In each business step, an individual information storage unit that records the items and input contents included in the document used for circulation of this business step, and the content of the circulation status;
An approval management system comprising a control unit connected to a client terminal of an applicant and a transferee approver,
The control unit is
The input contents for the items included in the document generated based on the application acquired from the applicant's client terminal are recorded in the individual information storage unit, and the business process of the document is specified using the business process storage unit ,
Circulate the application to the approver of the circulation destination, obtain approval information from the approver, perform a circulation process of registering the circulation state in the individual information storage unit ,
In accordance with the usage conditions of each business step constituting the business process, the input contents for the items included in the new document generated in each business step are recorded in the individual information storage unit, and in the individual information storage unit The approval management system is characterized in that the distribution process is continued until approval information is acquired from all approvers of distribution destinations in all the business steps constituting the application business process. A grace period storage unit that records a grace period for approval;
The control unit is
Using the grace period, calculate the approval deadline at each circulation destination,
The approval management according to claim 1, wherein a list obtained by rearranging application information distributed to the distribution destination based on the approval deadline is output at a client terminal of a distribution destination approver. system. Calculate the final approval date, which is the approval deadline at the final distribution destination for the application,
Compare the final approval desired date of the application with the final approval scheduled date,
The approval management system according to claim 2, wherein when the final approval date is later than the final approval date, a warning is output to the client terminal of the applicant.   When the approval information about the application is acquired from the client terminal of the approver of the transfer destination, the approval deadline of the subsequent transfer destination in the business process is readjusted based on the current date and the grace period. The approval management system according to claim 2 or 3. Obtain the schedule information of the approver of the distribution destination,
5. The caution information is output to the client terminal when it is determined in the schedule information that approval cannot be made by the approval deadline of the approver. 5. Approval management system described. Obtain personnel transfer information of the approver of the distribution destination,
6. The caution information is output to the client terminal for an application within a reference number of days from the scheduled date of change to the approval deadline included in the personnel change information. Approval management system described. Obtain personnel transfer information of the approver of the distribution destination,
For the approver included in the personnel transfer information, the preceding approver is identified in the circulation route recorded in the circulation route storage unit,
Identify the deadline for approval of the preceding approver,
The application whose deadline for approval of the preceding approver is later than the scheduled transfer date included in the personnel change information is deleted from the approval list output to the client terminal of the approver of the circulation destination, The approval management system according to any one of claims 2 to 6. Identify critical paths in each business process,
Calculate the approval deadline of the approver of the distribution destination of the business steps that constitute the critical path,
8. The approval deadline of an approver who is a distribution destination of a business step parallel to the critical path is calculated based on the approval deadline of the critical path. Approval management system. For the applicant's application, a business process storage unit that records a business process that combines multiple business steps,
For each business step, a circulation route storage unit that records a circulation route for specifying a circulation destination in turn,
For each business step, the items included in the document used to distribute this business step
Individual information storage unit that records the contents of eyes, input contents, and circulation status;
A method for managing approval using an approval management system comprising a control unit connected to a client terminal of an applicant and a transferee approver,
The control unit is
The input contents for the items included in the document generated based on the application acquired from the applicant's client terminal are recorded in the individual information storage unit, and the business process of the document is specified using the business process storage unit ,
Circulate the application to the approver of the circulation destination, obtain approval information from the approver, perform a circulation process of registering the circulation state in the individual information storage unit ,
In accordance with the usage conditions of each business step constituting the business process, the input contents for the items included in the new document generated in each business step are recorded in the individual information storage unit, and in the individual information storage unit approval management method, characterized by continuing the circulation processing from all the approvers circulation destination in all operation steps constituting a business process of the application until the approval information. For the applicant's application, a business process storage unit that records a business process that combines multiple business steps,
For each business step, a circulation route storage unit that records a circulation route for specifying a circulation destination in turn,
In each business step, an individual information storage unit that records the items and input contents included in the document used for circulation of this business step, and the content of the circulation status;
A program for managing approval using an approval management system including a control unit connected to a client terminal of an applicant and a transferee approver,
The control unit
The input contents for the items included in the document generated based on the application acquired from the applicant's client terminal are recorded in the individual information storage unit, and the business process of the document is specified using the business process storage unit ,
Circulate the application to the approver of the circulation destination, obtain approval information from the approver, perform a circulation process of registering the circulation state in the individual information storage unit ,
In accordance with the usage conditions of each business step constituting the business process, the input contents for the items included in the new document generated in each business step are recorded in the individual information storage unit, and in the individual information storage unit approval management program for causing to function as a means to continue the circulation process until the approval information from all approvers circulation destination in all operation steps constituting a business process of the application.