JP2012138014A - Authority management system, authority management method and authority management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an authority management system, an authority management method and an authority management program for properly managing a decision-making authority on applications.SOLUTION: A controller 21 of an application management server 20 performs a registration processing of authority transfer for transferring authority from a primary person who has the authority to another person in a company. In an approver registration processing, the controller 21 extracts candidates for the authority based on categories, obtains a piece of information on a default approver, who is selected by a person in a company, who has a possibility to make an application, from client servers 10, and stores the information in an approver registration data storage part 24. In an application receiving processing, approver candidates including a default approver are extracted based on an application content and attendance information of the default approver is obtained. The applicant selects an approver based on the attendance information. The controller 21 regularly transmits an approval request. Also, in a case where there is an urgent application request or a decision request includes a large amount of contents to be confirmed, a notice is made to an approver.

Description

  The present invention relates to an authority management system, an authority management method, and an authority management program for managing an approval authority for 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 circulated electronically via a network, and confirmation work for approval / disapproval is performed. However, when applications that require confirmation of content concentrate on a specific authority, the burden of confirmation increases and the approval process may be delayed.

  Therefore, the approval authority may transfer the authority processing to another person to distribute the approval process. Therefore, an electronic document circulation system that considers a case where a document authorizer delegates the authorization authority has been studied (for example, see Patent Document 1). In the electronic document circulation system described in this document, a decision route for circulating an electronic document is set in advance. When the creator of the electronic document selects a circulator or authorizer who requests approval or approval after document creation, it is determined whether the author is an authorizer before authority transfer. If it is an authorizer before authority delegation, an identification display indicating that it is an authorizer before authority delegation is displayed and a decision route is set.

  In addition, a document management apparatus for reliably managing an electronic document even when there is an organizational change or the like has been studied (for example, see Patent Document 2). When managing an electronic document, the document management apparatus described in this document stores authority information associated with the ID of the electronic document as management information. The authorized person can perform work such as revision of the electronic document. When the authorized person leaves the position of managing the electronic document due to personnel changes or the like, the management authority of the electronic document is transferred to the next authorized person.

JP 2004-21273 A (first page, FIG. 2) International Publication No. 2006/137124 (first page, FIG. 9)

  When setting the authority, as described in Patent Document 1, there may be a case where only the authorized person can make a decision. However, in the case of a full-time decision, if this authorized person is absent, the confirmation work for the approval request content may be delayed. In particular, when there is a time limit for the approval, it is necessary to check in consideration of this time limit. Therefore, in order to distribute the load, a plurality of authorized persons (original authorized person and authorized person who has received the delegated authority) may be set by authority delegation. There may be a plurality of original authorized persons. In this case, it is necessary to specify an authorized person (authorizer) who confirms the contents of the approval request. In addition, when a plurality of authorized persons are set, the applicant may want to select an approver for various applications.

In addition, there are cases where personnel changes frequently occur within a company. In such a personnel change, it is desirable that the approval can be taken over smoothly even if the authority changes.
The present invention has been made to solve the above-described problems, and it is an object of the present invention to provide an authority management system, an authority management method, and an authority management program for accurately managing an approval authority for an application.

  In order to solve the above-mentioned problem, the invention described in claim 1 includes an authority having an approval authority corresponding to the application content, and authority management information storage means for storing authority information about the delegation destination of the approval authority. , An authority management system comprising an authorizer registration information storage means for storing default authorizer information for making an approval for each application, and a control means for managing the approval for the application, wherein the control means is provided from a client terminal. A means for authenticating the authorized person who has accessed, identifying a candidate for delegation capable of delegating a decision-making authority in accordance with the application contents in the authorized person, and outputting to the client terminal; A means for registering as an authorized person to whom an authority to approve the application contents is delegated in the authority management information storage means; Authenticating the applicant who accessed from the client terminal, based on the application content acquired from the client terminal, in the authority management information storage means to identify the authorized person who can make a decision, and output to the client terminal as a candidate for decision And a means for registering an authorized person selected from among the candidates for authorizer as a default authorizer for the contents of the application in the authorizer registration information storage means.

  The invention described in claim 2 is the authority management system according to claim 1, further comprising application management information storage means for storing application management information in which an authorizer is registered for each application, wherein the control means includes: When connected to a time management system that stores time information of an authorized person, and when the control unit authenticates an applicant who has accessed from a client terminal and obtains an application from the client terminal, the authorizer registration information storage unit The default authorizer is identified using the above, the attendance information of the default authorizer is acquired from the attendance management system, output to the client terminal, and application management information including the authorizer information acquired from the client terminal is obtained. The gist of the invention is that it further comprises means for recording in the application management information storage means.

  According to a third aspect of the present invention, in the authority management system according to the second aspect, when the control means determines that the default decision maker cannot make a decision based on the attendance information, the right management information storage means The present invention further includes means for registering another authorized person recorded in the application management information storage means as the approver of the application.

  According to a fourth aspect of the present invention, in the authority management system according to the third aspect of the present invention, when the attendance information is not scheduled to arrive by the deadline for application in the attendance information, the final decision is made by the default finalizer. The gist is to determine that it is not possible.

  The invention according to claim 5 is the authority management system according to any one of claims 2 to 4, wherein the control means records the application recorded in the application management information storage means according to the contents of the application. Means for calculating the load for confirming the details of the requested approval request, and means for notifying the authorizer of the application when the load exceeds a reference value. And further comprising.

  According to a sixth aspect of the present invention, in the authority management system according to any one of the first to fifth aspects, when the control means obtains transfer information about the delegating source authority, the authority The gist of the present invention is that it further includes means for setting a takeover period as an effective period for the authority of the authority stored in the management information storage means.

  The invention according to claim 7 is the authority management system according to any one of claims 1 to 6, wherein when the control means acquires transfer information about the authority as a delegation source, the authority The gist of the present invention is that it further comprises means for changing the delegation source authorized person stored in the management information storage means to a new authorized person based on the transfer information.

  The invention according to claim 8 is the authority management system according to any one of claims 1 to 7, wherein when the control means acquires transfer information about the authority of the delegation destination, the authority The gist of the invention is that it further comprises means for deleting the authority of the delegation destination stored in the management information storage means.

  The invention described in claim 9 is an authority having approval authority corresponding to the contents of the application, authority management information storage means storing authority information about the delegation destination of the approval authority, and default approval for making approval for each application A method for managing an application using an authority management system including an authorizer registration information storage unit that stores information on an applicant and a control unit that manages an approval for an application, wherein the control unit includes a client Authenticating the authorized person accessed from the terminal, identifying the delegation destination candidate who can delegate the approval authority in accordance with the application content in the authorized person, and outputting to the client terminal, and among the delegation destination candidates Registering the selected user as an authorized person to whom the authority to approve the application content is delegated in the authority management information storage means; The client terminal authenticates the applicant who has accessed from the client terminal, identifies the authorized person who can make a decision in the authorization management information storage means based on the application contents acquired from the client terminal, and uses the client terminal as a candidate for decision And the step of registering the authorized person selected from among the candidates for authorizer as the default authorizer for the application contents in the authorizer registration information storage means. .

  The invention according to claim 10 is an authority having an approval authority corresponding to the contents of the application, an authority management information storing means for storing authority information about the delegation destination of the approval authority, and a default approval for making an approval for each application A program for managing an application using an authority management system including an authorizer registration information storage unit that stores person information and a control unit that manages approval for an application, the control unit being a client Means for authenticating an authorized person who has accessed from a terminal, specifying a candidate for delegation to which authority can be delegated in accordance with the application contents in the authorized person, and outputting to the client terminal, selected among the candidates for delegation A means for registering the authorized user as an authorized person to whom the authority to approve the application is delegated in the authority management information storage means; The client terminal authenticates the applicant who has accessed from the ant terminal, identifies the authorized person who can make a decision in the authorization management information storage unit based on the application content acquired from the client terminal, and uses the client terminal as a candidate for decision making The authority is selected as the default authorizer for the contents of the application as means for registering in the authorizer registration information storage unit.

(Function)
According to the invention described in claim 1, 9 or 10, the control means authenticates the authorized person who has accessed from the client terminal, and specifies the delegation destination candidate who can delegate the decision-making authority in accordance with the application contents in the authorized person. And output to the client terminal. Then, the user selected from among the transferee candidates is registered in the authority management information storage means as the authority who has been granted the authority to approve application contents. Furthermore, the applicant who has accessed from the client terminal is authenticated, and based on the application contents acquired from the client terminal, the authority management information storage means identifies the authorized person who can make a decision, and assigns it to the client terminal as a candidate for decision making. Output. Then, the authority selected from among the candidates for the authorizer is registered in the authorizer registration information storage unit as the default authorizer for the application contents. Thereby, the authority delegation destination can be set, and the applicant can select the authorizer from the authority candidates.

According to the invention described in claim 2, when the control unit authenticates the applicant who has accessed from the client terminal and acquires the application from the client terminal, the control unit specifies the default authorizer using the authorizer registration information storage unit. . Then, the default authorizer's attendance information is acquired from the attendance management system, output to the client terminal, and the application management information including the authorizer information acquired from the client terminal is recorded in the application management information storage means. Thereby, it is possible to determine the authorizer in consideration of the attendance information of the authorizer.

  According to the third aspect of the present invention, when the control means determines that the default decision maker cannot make a decision based on the attendance information, the other authorized person recorded in the authority management information storage means is approved for application. Registered in the application management information storage means. Thereby, another authorized person can make a decision according to the attendance information.

  According to the fourth aspect of the present invention, when the default authorizer is not scheduled to attend the office by the deadline for application, the default authorizer determines that the judgment cannot be made by the default authorizer. On the other hand, if the default authorizer determines that the judgment cannot be made by the application deadline, the other authorized person recorded in the authority management information storage means is registered as the authorizer. Thereby, the approver can be determined in consideration of the approval deadline.

  According to the invention described in claim 5, the control means loads a load for confirming the requested approval request content for each approver recorded in the application management information storage means according to the application content. calculate. When the load exceeds the reference value, the approver is notified that there has been an application. Receiving notifications for each application to the approver can be cumbersome for the approver. On the other hand, if many applications are notified at once, the burden of confirmation work may become excessive. Therefore, in consideration of the load of the authorizer, the approval request can be notified collectively for a predetermined number of applications.

  According to the sixth aspect of the present invention, when the control means acquires the transfer information about the authorized person who is the delegation source, the validity period for the authority of the authorized person stored in the authorized management information storage means Set the takeover period as. Thereby, even when there is a personnel change of the original authorized person, it is possible to perform authority management in consideration of the takeover period.

  According to the seventh aspect of the present invention, when the control unit acquires the transfer information about the delegation source authority, the delegation source authority stored in the authority management information storage unit is used as the transfer information. Change to a new authorized person based on this. As a result, the delegated authority can be maintained even when the original authority person is transferred.

  According to the eighth aspect of the present invention, when the control unit obtains the transfer information about the delegation destination authority, the delegation destination authority stored in the authority management information storage unit is deleted. As a result, the delegated authority can be deleted.

  According to the present invention, it is possible to accurately manage a decision-making authority regarding an application.

The system schematic of embodiment of this invention. It is explanatory drawing of the data used by this embodiment, (a) is an organization table management data storage part, (b) is an authority management data storage part, (c) is an authorizer registration data storage part, (d) is application Explanatory drawing of the data recorded on the management data storage part. 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.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, a description will be given of an authority management system, an authority management method, and an authority management program that are used for managing authority to make an approval for an application submitted by a member (employee) in an organization (company). In the following, “user” is a user of this system, and includes both the applicant and the approver. “Applicant” indicates a person who makes an application, and an authorized person indicates a person who has a decision-making authority. Those who have been delegated authority from the original authority are also included in the authority. The “authorizer” is a person who is selected by the applicant among the authorized persons and who approves the application.

  In the present embodiment, as shown in FIG. 1, an application management server 20 as an authority management system is used to manage the authority to make an application decision. The application management server 20 is connected to the client terminal 10, the personnel management server 30, and the attendance management server 40 via a network.

  The client terminal 10 is a computer terminal (applicant terminal, authority terminal) used by an employee such as an applicant or an authorized person (including an authorizer). The applicant creates various applications using the client terminal 10. The authorized person uses the client terminal 10 to confirm the content of the approval request. Then, the approver performs an approval input, a return input, a rejection input, and the like based on the content of the approval request. 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 application management server 20 is a server computer for supporting authority management processing of various applications, application processing by the applicant, and approval processing by the approver. The application management server 20 includes a control unit 21, an organization table management data storage unit 22, an authority management data storage unit 23 as an authority management information storage unit, an authorizer registration data storage unit 24 as an authorizer registration information storage unit, an application An application management data storage unit 25 is provided as management information storage means.

  Here, the control unit 21 includes a control unit including a CPU, a RAM, a ROM (not shown), etc., and processes (user authentication stage, delegation registration stage, authorizer registration stage, application acceptance) described later. Stage, finalizer decision stage, final decision management stage, application notification stage, transfer management stage, etc.). Then, as shown in FIG. 1, the control unit 21 executes a user authentication unit 211, a delegation registration unit 212, an authorizer registration unit 213, an application reception unit 214, an authorizer information acquisition unit 215, by executing an authority management program. It functions as an approval management unit 216, an application notification unit 217, and a transfer management unit 218.

  The user authentication unit 211 executes processing for authenticating a user from the client terminal 10. The user authentication unit 211 acquires user authentication information (employee code and password) from the client terminal 10. Further, the user authentication unit 211 acquires authentication information (employee code and password) of each user from a user management data storage unit (not shown). Then, by comparing with the authentication information acquired from the client terminal 10, the accessed employee is specified.

  The delegation registration unit 212 executes processing for managing delegation of decision authority for various applications. In the present embodiment, as will be described later, a process for registering an employee to be delegated by an authorized person is supported.

  The approver registration means 213 executes processing for registering an employee (authorizer) who approves each employee's application. In the present embodiment, as will be described later, an employee who may make an application supports processing in the case where an authorizer is registered in advance.

  The application receiving unit 214 executes a process of receiving an application from each employee. The application receiving unit 214 includes a category management table in which the application contents of various applications are associated with the category to which the application contents belong. The category of the present embodiment includes “HR”, “Attendance”, “Cost”, and the like. For example, the application content “vacation application” belongs to the “Attendance” category, and the application content “Travel Expenses” is “Cost”. Belonging to the category.

As will be described later, the authorizer information acquisition unit 215 executes processing for acquiring information regarding the authorizer stored for each applicant of each application.
The approval management unit 216 executes processing for managing approval for each application based on an instruction from the approver.

  The application notifying unit 217 executes processing for notifying each authorizer that there has been an application. The application notifying unit 217 acquires a contact address (for example, an e-mail address) associated with each employee code from the user management data storage unit. The application notification means 217 holds data related to a regular notification time (for example, 15:00 every day) for periodically notifying the approver of the presence or absence of an application. The application notifying unit 217 holds data related to a grace standard value for evaluating the length of the grace period until the approval deadline. Further, the application notifying unit 217 holds a load evaluation table in which a value (load weight value) obtained by evaluating the load for the confirmer to confirm the content is recorded for each application content. The application notifying unit 217 holds data related to the load reference value for evaluating the load of confirmation work of the authorizer.

  The change management unit 218 executes processing for updating the registration of the authorized person when the personnel change is acquired. This transfer management means 218 holds data relating to the number of transfer days in order to give a period for taking over the decision to the transfer person.

  As shown in FIG. 2A, the organization table management data storage unit 22 stores an organization table management record 220 for managing the organization to which a member (employee) of this organization (company) belongs. This organization chart management record 220 is recorded when an organization chart determined by personnel management is registered. The organization chart management record 220 includes data relating to employee codes, department codes, post codes, and qualification codes.

Data relating to an identifier for identifying each employee is recorded in the employee code data area.
In the department code data area, data relating to an identifier for identifying the department to which the employee belongs is recorded.

In the post code data area, data relating to an identifier for specifying a role in this organization is recorded.
In the qualification code data area, data relating to an identifier for specifying the qualification of the employee is recorded. With this qualification, it is possible to specify the scope of granting the application approval authority in this organization.

As shown in FIG. 2B, the authority management data storage unit 23 stores an authority management record 230 related to employees who have an approval authority in each organization. This authority management record 230 is recorded when a job title or qualification is registered based on personnel information or when authority delegation is registered. This authority management record 230 is originally configured to include data related to the authorized person, department code, category, delegation destination, delegation condition, and validity period.

  In the original authorized person data area, data relating to an identifier (employee code) for identifying an employee who has the original decision making authority (authorization authority of the delegation source) is recorded. This authorized person can delegate authority to other employees.

In the department code data area, data relating to an identifier for identifying an organization for which the authorized person originally has the decision authority is recorded.
In the category data area, data relating to an identifier for specifying a category including various applications for which the authorized person originally has the decision-making authority is recorded. In this embodiment, “HR”, “Attendance”, and “Cost” are used as categories.

In the delegation destination data area, data relating to an identifier (employee code) for identifying an employee whose authority is originally delegated by the authorized person is recorded.
In the delegation condition data area, data relating to conditions under which authorization can be made at the authority delegation destination is recorded. In the present embodiment, a flag (always delegation flag or absence delegation flag) is recorded in the delegation destination for discriminating between the case where permanent approval is permitted and the case where authority is delegated only when the original approver is absent. Is done.
In the effective period data area, data related to the effective period of the authority originally authorized is recorded.

  As shown in FIG. 2C, the authorizer registration data storage unit 24 stores an authorizer registration record 240 regarding the authorizer of the application from each employee. The authorizer registration record 240 is recorded when the authorizer registration process is performed by each employee. The authorizer registration record 240 includes data regarding employee codes, categories, and authorizers.

In the employee code data area, data relating to an identifier for identifying an employee who makes various applications is recorded.
In the category data area, data relating to an identifier for specifying the type of application is recorded.

  In the authorizer data area, data relating to an identifier (employee code) for identifying the authorizer (default authorizer) who performs approval for the application of the employee in this category is recorded. If no default authorizer is registered, this authorizer data area is blank.

  The application management data storage unit 25 stores an application management record 250 for managing applications received from employees, as shown in FIG. This application management record 250 is recorded when an application is accepted from the client terminal 10 of the applicant. The application management record 250 includes data relating to an application reception code, an applicant, a category, contents of an approval request, an approval deadline, an approver, a status, and a history.

In the application reception code data area, data related to an identifier for specifying each received application is recorded.
In the applicant data area, data relating to an identifier (employee code) for identifying the employee (applicant) who has made this application is recorded.

In the category data area, data relating to an identifier for specifying the type of application content is recorded.
In the approval request content data area, the application content and data related to the content requested for approval in this application are recorded. The authorizer confirms this content and decides whether or not to approve.

In the approval time limit data area, data relating to an identifier for specifying a time limit for approval for this application is recorded.
In the approver data area, data relating to an identifier for identifying an employee (authorizer) who performs approval for this application is recorded.

  In the status data area, data relating to an identifier for specifying the status of the application is recorded. In the present embodiment, flags indicating “waiting for confirmation”, “approval”, “return”, and “reject” are recorded in the status data area.

  In the history data area, data relating to the history of the application is recorded. In this history data area, the date (year / month / day) when the predetermined procedure was performed by the applicant or the finalist and the details of the procedure (application, confirmation, etc.) are recorded.

  The personnel management server 30 is a computer system that manages personnel information of employees of this company. The personnel management server 30 executes processing for providing organization chart information and personnel change information. This organization chart information includes an employee code, a department code, a job title code, and a qualification code. The organization table information is recorded in the organization table management data storage unit 22 described above. The personnel change information includes the date of issue, the date of change, the employee code of the transferor, the department code of the transfer source and the transfer destination, and the job title code.

  The attendance management server 40 is a computer system (attendance management system) that manages attendance information of each employee. The attendance management server 40 manages a work schedule for each employee code registered by the client terminal 10. Based on this work schedule, it is possible to specify the work status of employees (attended status, attendance schedule, vacation schedule, business trip schedule, etc.).

  A processing procedure in the case of managing approval authority and various applications using the system configured as described above will be described with reference to FIGS. Here, description will be made in the order of authority transfer registration processing, authorizer registration processing, application acceptance processing, authorizer notification processing, and transfer management processing.

(Authority transfer registration process)
First, the authority transfer registration process will be described with reference to FIG. Here, the original authorized person uses the client terminal 10 to access the application management server 20 in order to register delegation of approval authority.

  In this case, the control part 21 of the application management server 20 performs a user authentication process (step S1-1). Specifically, the user authentication unit 211 of the control unit 21 outputs an authentication screen on the display of the client terminal 10. The user enters the employee code and password on this authentication screen. When a transmission instruction is input, the client terminal 10 transmits an authentication request to the application management server 20. This authentication request includes the employee code and password entered on the authentication screen. Then, the user authentication unit 211 performs user authentication using the employee code and password acquired from the client terminal 10. If the user authentication cannot be performed, an error message is transmitted to the client terminal 10.

On the other hand, when the user authentication is completed, the user authentication unit 211 acquires the organization table management record 220 in which this employee code is recorded from the organization table management data storage unit 22, and the department code and the qualification code of this employee To get. Then, the user authentication unit 211 outputs a menu screen corresponding to the qualification code on the display of the client terminal 10. In the case of an employee who has authority in the qualification code, an authority delegation registration button, an authority registration button, an application button, and an approval process button are included in the menu screen. On the other hand, in the case of an employee who has no authority in the qualification code, an authorizer registration button and an application button are included in the menu screen. Here, it is assumed that the user (authorized person) selects the authority transfer registration button on the menu screen. In this case, the client terminal 10 transmits an authority transfer registration screen request to the application management server 20.

  The control unit 21 of the application management server 20 that has received the authority transfer registration screen request executes a category specifying process (step S1-2). Specifically, the delegation registration unit 212 of the control unit 21 extracts the authority management record 230 in which the authenticated employee code is originally recorded in the authority data area from the authority management data storage unit 23. Then, the delegation registration unit 212 identifies the category recorded in the authority management record 230. Next, the delegation registration unit 212 creates a category list for displaying the identified categories as a list. Then, a category selection screen in which each category can be selected in the category list is generated and output to the display of the client terminal 10. This category selection screen includes a selection button for selecting each category. The user selects a category to which authority is delegated on the category selection screen. In this case, the client terminal 10 transmits selection information about the selected category to the application management server 20.

  Next, the control unit 21 of the application management server 20 executes a process for extracting candidates for delegation based on the category (step S1-3). Specifically, the delegation registration unit 212 of the control unit 21 extracts the organization table management record 220 of the employees of the organization to which the originally authorized person belongs from the organization table management data storage unit 22. Then, the delegation registration unit 212 uses the extracted organization table management record 220 to identify the employee code of the employee (delegation destination candidate) in which the qualification code that can grant the authorization authority in this category is recorded.

  Next, the control part 21 of the application management server 20 performs the output process of a transfer destination candidate (step S1-4). Specifically, the delegation registration unit 212 of the control unit 21 generates a delegation destination selection screen that lists the identified delegation destination candidates, and outputs them to the display of the client terminal 10.

  Next, the control unit 21 of the application management server 20 executes a transfer destination acquisition process (step S1-5). Specifically, the authorized person selects an employee whose authority is to be delegated on the delegation destination selection screen. Furthermore, on the delegation destination selection screen, a delegation condition (always delegation or delegation when absent) for selecting authority is selected. Then, the client terminal 10 transmits selection information including the employee code selected on the transfer destination selection screen and transfer conditions to the application management server 20. The delegation registration unit 212 of the control unit 21 acquires the employee code and delegation conditions selected as the delegation destination from the client terminal 10.

  Next, the control part 21 of the application management server 20 performs the registration process of a transfer subject person (step S1-6). Specifically, the delegation registration unit 212 of the control unit 21 records the delegation destination employee code and delegation conditions acquired from the client terminal 10 in the authority management record 230 of this category.

(Approver registration process)
Next, the authorizer registration process will be described with reference to FIG. Here, an employee who may make various applications uses the client terminal 10 to access the application management server 20 in order to register an approver for various applications.

In this case, the control part 21 of the application management server 20 performs a user authentication process similarly to step S1-1 (step S2-1). When user authentication is completed, user authentication means 2
11 outputs the menu screen to the display of the client terminal 10. Here, the user selects the authorizer registration button on the menu screen. In this case, the client terminal 10 transmits a requester registration screen request to the application management server 20.

  The control unit 21 of the application management server 20 that has received the requester registration screen request executes a category specifying process (step S2-2). Specifically, the authorizer registration unit 213 of the control unit 21 creates a category list for displaying a list of various application categories. Then, a category selection screen in which each category can be selected in the category list is generated and output to the display of the client terminal 10. The user selects a category on the category selection screen. Then, the client terminal 10 transmits the selected category information to the application management server 20.

  Next, the control unit 21 of the application management server 20 executes an authority candidate extraction process based on the category (step S2-3). Specifically, the authorizer registration unit 213 of the control unit 21 extracts an authority management record 230 in which the department code and category to which the user belongs is recorded from the authority management data storage unit 23. Then, the authorizer registration unit 213 acquires the employee code recorded in the original authorized person data area of the authorized management record 230. Further, the authorizer registration means 213 acquires the employee code recorded in the delegation destination data area of the authority management record 230 in which the delegation flag is always recorded in the delegation condition data area.

  Next, the control unit 21 of the application management server 20 executes an output process for the authorizer candidate (step S2-4). Specifically, the authorizer registration unit 213 of the control unit 21 creates a candidate list for displaying a list of employee codes acquired from the authority management record 230 in the previous step as candidates of authorizers. Then, an authorizer selection screen that allows each candidate to be selected in the candidate list is generated and output to the display of the client terminal 10.

  Next, the control unit 21 of the application management server 20 executes a default authorizer acquisition process (step S2-5). Specifically, the user selects an authorizer (default authorizer) who makes an approval for his application on the authorizer selection screen. The client terminal 10 transmits the employee code information of the authorizer selected on the authorizer selection screen to the application management server 20. The authorizer registration unit 213 of the control unit 21 acquires the employee code selected as the default authorizer from the client terminal 10.

  Next, the control unit 21 of the application management server 20 executes a default authorizer registration process (step S2-6). Specifically, the authorizer registration unit 213 of the control unit 21 stores the employee code of the default authorizer acquired from the client terminal 10 in the employee code of the user and the authorizer data area of the category authorizer registration record 240. Record.

(Application acceptance process)
Next, the application acceptance process will be described with reference to FIG. Here, an employee (applicant) who makes various applications accesses the application management server 20 to make various applications using the client terminal 10.

  In this case, the control part 21 of the application management server 20 performs a user authentication process similarly to step S1-1 (step S3-1). When the user authentication is completed, the user authentication unit 211 outputs a menu screen to the display of the client terminal 10. Here, the user selects an application button on the menu screen. In this case, the client terminal 10 transmits an application screen request to the application management server 20.

Next, the control unit 21 of the application management server 20 executes an application reception process (step S3).
-2). Specifically, the application reception unit 214 of the control unit 21 outputs an application reception screen to the display of the client terminal 10. This application reception screen is provided with a selection button for selecting application contents. Then, the user selects a selection button for the desired application content. In this case, the client terminal 10 transmits a reception screen request for the selected application content to the application management server 20.

  The application reception unit 214 that has received the application reception screen request outputs a reception screen for the selected application to the display of the client terminal 10. This reception screen is provided with input fields for inputting necessary items (contents of approval request) and approval deadlines. The user inputs necessary items on this application reception screen. Further, when setting a time limit for approval, the time limit for approval is input on the application reception screen. Then, the client terminal 10 transmits the input approval request content to the application management server 20.

  Next, the control unit 21 of the application management server 20 executes a candidate decision process based on the application content (step S3-3). Specifically, the application receiving unit 214 of the control unit 21 uses the category management table to specify a category corresponding to the application content, and takes over the application received by the authorizer information acquiring unit 215. The authorizer information obtaining unit 215 extracts the authorizer registration record 240 in which the applicant's employee code and the application category are recorded from the authorizer registration data storage unit 24. Then, the authorizer information acquisition unit 215 acquires the employee code recorded in the authorizer data area of the authorizer registration record 240.

  Further, the authorizer information acquisition unit 215 uses the authority management data storage unit 23 to extract the authority management record 230 in which the department code and category of the department to which the applicant belongs are recorded. Then, the authorizer information acquisition unit 215 acquires the employee code originally recorded in the authority data area and the transferee data area from the authority management record 230. With this employee code, it is possible to confirm the validity of the authority of the default authorizer and specify other authorized persons.

In addition, the authorized person who has passed the expiration date of the authorized management record 230 is excluded from the candidates for the final decision makers.
Further, when the authorizer data area of the authorizer registration record 240 is blank, the default authorizer cannot be identified, and therefore all authorized persons are identified as candidate authorizers. When an application is made using such an authorizer registration record 240, the authorizer information acquisition unit 215 prompts the client terminal 10 to re-execute the authorizer registration process.

  Next, the control unit 21 of the application management server 20 executes a process for acquiring time information of the default authorizer (step S3-4). Specifically, the authorizer information acquisition unit 215 of the control unit 21 acquires the work schedule for the employee code recorded in the authorizer data area of the authorizer registration record 240 from the attendance management server 40. Here, the work schedule after that day is acquired.

  Next, the control part 21 of the application management server 20 performs the determination process of an authorizer based on attendance information (step S3-5). Specifically, the authorizer information acquisition unit 215 of the control unit 21 creates an authorizer candidate list for displaying a list of default authorizers and other authorized persons. Then, an authorizer selection screen in which each authorizer candidate can be selected in the authorizer candidate list is generated and output to the display of the client terminal 10. The work schedule acquired from the attendance management server 40 is included in this authorizer selection screen. If the authority is originally registered as the default approver, and this default approver is absent (business trip or vacation) and the delegation flag is stored in the delegation condition data area, the authorizer The information acquisition unit 215 outputs the employee code of the delegation destination as a default authorizer.

  If the applicant determines that the approval decision can be made in the work schedule of the default approver, the applicant specifies the default approver as the approver. On the other hand, if it is determined in the work schedule that the decision cannot be made, another authorized person (originally authorized person or delegation employee) is identified as the authorized person. Then, the client terminal 10 transmits the authorizer information selected by the applicant to the application management server 20.

  The control unit 21 of the application management server 20 that has received the authorizer information executes an application registration process (step S3-6). Specifically, the application accepting unit 214 of the control unit 21 generates an application management record 250 to which an application acceptance code is assigned, sets the applicant to the approval deadline, and records the application management record 250 in the application management data storage unit 25. In this case, the “waiting for confirmation” flag is recorded in the status data area, and the application date is recorded in the history data area.

(Authorizer notification process)
Next, the authorizer notification process will be described with reference to FIG.
First, the control unit 21 of the application management server 20 executes a determination process as to whether there is an unapproved application (step S4-1). Specifically, the application notifying unit 217 of the control unit 21 searches the application management data storage unit 25 for the application management record 250 in which the “waiting for confirmation” flag is recorded in the status data area.

Here, when the application is not registered (in the case of “NO” in step S4-1), the control unit 21 of the application management server 20 ends the authorizer notification process.
On the other hand, when the application is registered (in the case of “YES” in step S4-1), the control unit 21 of the application management server 20 executes a determination process as to whether or not the regular notification time has passed (step S41). S4-2). Specifically, the application notification unit 217 of the control unit 21 obtains the current time from the system timer and compares the current time with the regular notification time to determine whether the regular notification time has elapsed.

  When the regular notification time has elapsed (in the case of “YES” in step S4-2), notification processing is executed (step S4-3). Specifically, the application notification unit 217 of the control unit 21 acquires the contact information of each authorizer recorded in all the application management records 250 from the user management data storage unit. Then, the application notifying unit 217 transmits an approval request including a message indicating that there is an application waiting for confirmation. Upon receiving this approval request, the approver accesses the application management server 20 and performs an approval process to be described later.

  On the other hand, when the regular notification time has not elapsed (in the case of “NO” in step S4-2), the control unit 21 of the application management server 20 repeats the following processing for each authorizer who has an unapproved application. And execute.

  Here, the control part 21 of the application management server 20 performs the determination process about whether there exists a urgent application (step S4-4). Specifically, the application notifying unit 217 of the control unit 21 specifies a record with the closest approval deadline in the application management record 250 of the authorizer. Then, the application notifying unit 217 calculates the length of the grace period until this decision deadline, and compares it with the grace standard value. Here, when the length of the grace period until the approval deadline is less than the grace standard value, it is determined that there is a rush application.

  When it is determined that there is a rush application (in the case of “YES” in step S4-4), the control unit 21 of the application management server 20 executes a notification process (step S4-7). Specifically, the application notifying unit 217 of the control unit 21 acquires the contact information of the authorizer recorded in the application management record 250 from the user management data storage unit. Then, the application notifying unit 217 transmits an approval request including a message indicating that there is an application waiting for confirmation.

  On the other hand, if it is determined that there is no rush application (in the case of “NO” in step S4-4), the control unit 21 of the application management server 20 executes a confirmation workload calculation process for the application to be approved (step S4-4). S4-5). Specifically, the application notifying unit 217 of the control unit 21 acquires a load weight value corresponding to the application content from the load evaluation table for the application of each extracted application management record 250. Then, the application notifying unit 217 calculates a load sum value by summing the load weight values of the respective applications.

  Next, the control part 21 of the application management server 20 performs the determination process about whether the load sum value of a confirmation operation | work is more than a load reference value (step S4-6). Specifically, the application notifying unit 217 of the control unit 21 compares the calculated load sum value with the load reference value to determine whether or not the load sum value of the confirmation work is greater than or equal to the load reference value.

  When the total load value of the confirmation work is equal to or greater than the load reference value (“YES” in step S4-6), the control unit 21 of the application management server 20 executes notification processing (step S4-7).

  On the other hand, when the load total value of the confirmation work is less than the load reference value (in the case of “NO” in step S4-6), the control unit 21 of the application management server 20 ends the process for the authorizer. Then, the processes of steps S4-4 to S4-7 are repeated for each authorizer of the unapproved application management record 250.

(Decision processing)
Next, the approval process will be described. Here, the approver who has received the approval request uses the client terminal 10 to access the application management server 20 in order to confirm the approval request content and determine whether or not to approve.

  In this case, the control unit 21 of the application management server 20 executes user authentication processing. Then, the user selects an approval process button on the menu screen. In this case, the client terminal 10 transmits an approval process screen request to the application management server 20.

  When the approval process screen request is received, the control unit 21 of the application management server 20 executes an unapproved application list display process. Specifically, the approval management means 216 of the control unit 21 extracts an application management record 250 for an unconfirmed application in which the employee code of the authorizer is recorded from the application management data storage unit 25. Then, the approval management means 216 outputs an approval processing screen displaying a list of approval request contents recorded in the extracted application management record 250 to the display of the client terminal 10.

  The approver uses the client terminal 10 to input “approval”, “return”, or “reject”. Then, the approval management unit 216 of the control unit 21 receives a confirmation result notification about the application from the client terminal 10. This confirmation result notification includes an instruction of “Approve”, “Return” or “Reject”.

  When the confirmation result notification includes a “return” instruction or a “reject” instruction, the control unit 21 of the application management server 20 executes a return process or a rejection process. Specifically, the approval management unit 216 of the control unit 21 records a “return” flag or a “reject” flag as a status in the application management record 250. Next, the approval management unit 216 acquires the contact information of the applicant recorded in the application management record 250 from the user management data storage unit. Then, the approval management unit 216 transmits a message notifying that the application has been returned or rejected to the contact information. In the case of a refund, the applicant will reapply as necessary.

  On the other hand, when the approval result notification includes an “approval” instruction, the control unit 21 of the application management server 20 executes a determination result notification process. Specifically, the approval management means 216 of the control unit 21 records an “approval” flag as a status in the application management record 250. Next, the approval management means 216 transmits a message notifying that the application has been approved to the contact information of the applicant recorded in the application management record 250.

(Change management process)
Next, the change management process will be described with reference to FIG.
The control unit 21 of the application management server 20 executes change information acquisition processing (step S5-1). Specifically, the change management means 218 of the control unit 21 acquires personnel change information from the personnel management server 30. This personnel change information includes the date of issue, the date of change, the employee code of the transferor, the department code of the transfer source and the transfer destination, and the position code.

  Next, the control unit 21 of the application management server 20 executes a process for searching for a transferee who has delegated authority (step S5-2). Specifically, the transfer management means 218 of the control unit 21 acquires the employee code recorded in the original authorized person data area of the authorized management record 230. Then, the change management unit 218 searches for the employee code of the originally authorized person (delegation source) in the personnel change information.

  Next, the control part 21 of the application management server 20 performs the determination process about whether there exists a transfer of a transfer origin (step S5-3). Specifically, the transfer management means 218 of the control unit 21 determines that there is a transfer of the delegation source when the employee code of the originally authorized person (delegation source) is included in the personnel change information. .

  When it is determined that there is a transfer of the transfer source (in the case of “YES” in step S5-3), the control unit 21 of the application management server 20 executes a new authority person registration process (step S5-4). Specifically, the transfer management means 218 of the control unit 21 specifies an employee who has the same department as the delegation source, in the personnel change information, who is the delegation source department. Then, the transfer management unit 218 generates an authority management record 230 in which the identified employee code is originally recorded in the authorized person data area, and records it in the authorized management data storage unit 23. In this case, the same data as the authority management record 230 of the transferee from this department is recorded in the department code, category, and delegation destination data areas.

  Next, the control unit 21 of the application management server 20 executes a transfer authority update process (step S5-5). Specifically, the change management means 218 of the control unit 21 calculates an effective period obtained by adding the number of days taken over to the transfer date of the transfer person from this department. Then, the change management unit 218 records the effective period in the authority management record 230 of the transfer person.

  Further, the transfer management means 218 searches the approver registration data storage unit 24 for the approver registration record 240 in which the employee code of the transferor is recorded in the approver data area. When the authorizer registration record 240 is extracted, the transfer management unit 218 deletes the employee code recorded in the authorizer data area.

  Next, the control unit 21 of the application management server 20 executes a process for searching for a transferee who has been delegated authority (step S5-6). Specifically, the transfer management means 218 of the control unit 21 acquires the employee code recorded in the delegation destination data area of the authority management record 230. Then, the transfer management means 218 searches for the employee code of the delegation destination in the personnel transfer information.

Next, the control part 21 of the application management server 20 performs the determination process about whether there is a transfer of a transfer destination (step S5-7). Specifically, the transfer management means 218 of the control unit 21 determines that there is a transfer of the delegation destination when the employee code of the delegation destination is included in the personnel change information.

  When there is a transfer of the delegation destination (in the case of “YES” in step S5-7), the control unit 21 of the application management server 20 executes a delegation destination authority deletion process (step S5-8). Specifically, the transfer management unit 218 of the control unit 21 deletes the employee code recorded in the delegation destination data area of the authority management record 230.

  Further, the transfer management means 218 searches the authorizer registration data storage unit 24 for the authorizer registration record 240 in which the transferee employee code is recorded in the authorizer data area. When the authorizer registration record 240 is extracted, the transfer management unit 218 deletes the employee code recorded in the authorizer data area.

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, authority delegation registration processing is executed. In this process, the authority management record 230 that originally records the authorized person and the employee code of the delegation destination is registered in the authority management data storage unit 23. As a result, an employee whose authority has been delegated from the original authority can be determined as an authorizer.

  (2) In this embodiment, an authorizer registration process is executed. In this process, an authorizer registration record 240 in which an authorizer who confirms his / her approval request content is recorded is registered in the authorizer registration data storage unit 24. As a result, an employee who may apply may register an authorizer in advance.

  (3) In the present embodiment, in the application reception process, the control unit 21 of the application management server 20 extracts the finalizer candidate based on the application content (step S3-3), and obtains the default finalizer's attendance information. (Step S3-4) is executed. As a result, it is possible to determine whether or not the default decision maker can make a decision.

  And the control part 21 of the application management server 20 performs the determination process of an authorizer based on attendance information (step S3-5). Specifically, the authorizer information acquisition unit 215 of the control unit 21 creates an authorizer candidate list for displaying a list of default authorizers and other authorized persons. As a result, when it is difficult to make a judgment by the default authorizer, another authorized person can be selected as the authorizer.

  (4) In this embodiment, in the authorizer notification process, when an application is registered (in the case of “YES” in step S4-1), the control unit 21 of the application management server 20 has passed the regular notification time. A determination process is performed as to whether or not it is being performed (step S4-2). If the regular notification time has elapsed (in the case of “YES” in step S4-2), a notification process is executed (step S4-3). Thereby, it is possible to periodically notify the authorizer that there is an application.

  Furthermore, the control part 21 of the application management server 20 performs the determination process about whether there exists a urgent application (step S4-4). When it is determined that there is a rush application (in the case of “YES” in step S4-4), the control unit 21 of the application management server 20 executes a notification process (step S4-7). As a result, it is possible to quickly respond to an application that has to make a final decision in a hurry.

Furthermore, the control part 21 of the application management server 20 performs the determination process about whether the load total value of a confirmation operation | work is more than a load reference value (step S4-6). When the total load value of the confirmation work is equal to or greater than the load reference value (“YES” in step S4-6), the control unit 21 of the application management server 20 executes notification processing (step S4-7). This makes it possible to notify the approval request before the burden of the confirmation work becomes excessive, while reducing the complexity for the approver by notifying them collectively.

  (5) In this embodiment, when it is determined in the transfer management process that there is a transfer of the delegation source (“YES” in step S5-3), the control unit 21 of the application management server 20 A registration process (step S5-4) and a transferer authority update process (step S5-5) are executed. Thereby, even when the original authorized person is transferred, the approval for the application can be taken over efficiently.

  Furthermore, when there is a transfer of the delegation destination (in the case of “YES” in step S5-7), the control unit 21 of the application management server 20 executes a deauthorization process of the delegation destination whose authority has been delegated (step S5-7). S5-8). Thereby, accurate authority management can be performed for personnel changes.

In addition, you may change each said embodiment as follows.
In the above-described embodiment, the control unit 21 of the application management server 20 performs the process for extracting candidate candidates for delegation based on the category (step S1-3). Here, the delegation registration unit 212 uses the extracted organization table management record 220 to identify the employee code of the employee (delegation destination candidate) in which the qualification code that can grant the authorization authority in this category is recorded. In this case, the identification of the person who can be granted the authorization authority is not limited to that based on the qualification code. For example, job title code, years of service, etc. can be used. In this case, conditions for granting the authorization authority are recorded in the delegation registration unit 212. Furthermore, information (for example, years of service) for determining this grantable condition is stored in the organization chart management data storage unit 22.

  In the above embodiment, the authority management data storage unit 23 stores the authority management record 230 related to employees who have the authority to approve in each organization. In this delegation condition data area, a flag (always delegation flag or absentee delegation flag) for identifying whether the delegation destination always accepts approval and delegating authority only when the original approver is absent ) Is recorded. On the other hand, it may be possible to set as a delegation condition that an authorized person originally approves when the delegating authority is absent.

  In the above embodiment, when it is determined that there is a rush application (“YES” in step S4-4), the control unit 21 of the application management server 20 executes notification processing (step S4-7). Here, for a predetermined application content, the notification process (step S4-7) may be executed without determining the approval deadline. In this case, the application notifying means 217 holds the application content that is the subject of immediate notification processing.

  In the above embodiment, the control unit 21 of the application management server 20 executes a confirmation workload calculation process for the application to be approved (step S4-5). And the control part 21 of the application management server 20 performs the determination process about whether the load total value of confirmation work is more than a load reference value (step S4-6). Here, the load reference value may be determined for each authorizer. In this case, a load reference value data storage unit that records the load reference value for each authorized person is provided. Then, the determination is performed by comparing the load sum value with the load reference value for each authorizer.

Further, the load reference value may be changed according to the situation of the authorizer. For example, when the attendee's attendance information is acquired and absence information due to vacation or business trip is registered within a predetermined period, the control unit 21 performs a process of reducing the load reference value at a predetermined rate. This makes it possible to notify that there is an application before the authorizer is absent.

  In the above-described embodiment, in the application reception process, the control unit 21 of the application management server 20 executes the determination process for the finalizer based on the attendance information (Step S3-5). Specifically, the application receiving unit 214 of the control unit 21 outputs the work schedule acquired from the attendance management server 40 to the display of the client terminal 10. Then, the client terminal 10 transmits the authorizer information selected by the applicant to the application management server 20. Instead of this, the application management server 20 may determine the authorizer. Hereinafter, the process of determining the authorizer according to the attendance information of the authorized person will be described with reference to FIG.

  First, the control part 21 of the application management server 20 performs a user authentication process (step S6-1). Specifically, the user authentication unit 211 of the control unit 21 executes a user authentication process as in step S1-1.

  Next, similarly to steps S3-2 to S3-4, the control unit 21 of the application management server 20 receives an application reception process (step S6-2), and a process for extracting a finalizer candidate based on the application content (step S6). -3) The default finalist's attendance information acquisition process (step S6-4) is executed.

  Next, the control unit 21 of the application management server 20 executes a determination process as to whether or not the default approver can make an approval determination (step S6-5). Specifically, the authorizer information acquisition unit 215 of the control unit 21 compares the acquired attendance schedule with the approval deadline input on the application screen. In the default authorizer's attendance information, if the attendance schedule is recorded by the due date, the authorizer information obtaining unit 215 determines that the default authorizer can make a judgment. On the other hand, if the attendance schedule is not recorded by the time limit for approval in the attendance information of the default approver, the default approver determines that the approval cannot be made.

  When it is determined by the default authorizer that the judgment can be made (in the case of “YES” in step S6-5), the control unit 21 of the application management server 20 executes a default authorizer setting process (step S6-6). Specifically, the application accepting unit 214 of the control unit 21 records the employee code of the default authorizer in the authorizer data area of the application management record 250.

  On the other hand, if it is determined by the default authorizer that the decision cannot be made (in the case of “NO” in step S6-5), the control unit 21 of the application management server 20 executes processing for acquiring attendance information of other authorized persons ( Step S6-7). Specifically, the authorizer information acquisition unit 215 of the control unit 21 uses the authority management data storage unit 23 to be an employee who belongs to the department to which the applicant belongs and has the qualification that the category of the application can be approved. Search for employees. Then, the authorizer information acquisition unit 215 acquires the employee's attendance information from the attendance management server 40.

  Next, the control unit 21 of the application management server 20 executes a determination process as to whether another authorized person can make a decision on approval (step S6-8). Specifically, the authorizer information acquisition means 215 of the control unit 21 compares the attendance schedule in the attendance information acquired from the attendance management server 40 with the approval deadline to determine whether another authority can make an approval decision. judge.

  If there is a schedule of work before the deadline for approval and another authorized person can make a decision on the decision (in the case of “YES” in step S6-8), the control unit 21 of the application management server 20 performs the setting process for the other authorized person. Execute (Step S6-9). Specifically, the application receiving unit 214 of the control unit 21 records the employee code of another authorized person in the approver data area of the application management record 250.

Next, the control unit 21 of the application management server 20 executes an application registration process (step S6).
-10). Specifically, the application receiving unit 214 of the control unit 21 records the generated application management record 250 in the application management data storage unit 25.

On the other hand, when it is determined that the approval decision cannot be made by another authorized person (in the case of “NO” in step S6-8), the control unit 21 of the application management server 20 executes an output process for alerting the applicant. (Step S6-11). Specifically, the application receiving unit 214 of the control unit 21 outputs a message indicating that there is no authorized person who can confirm the application by the deadline for approval to the client terminal 10 of the applicant. After confirming this message, the applicant searches for another authorized person and requests approval.
Thereby, based on the attendance information, the authorizer for the application can be registered so as to be in time for the due date.

  In the above-described embodiment, in the application reception process, the control unit 21 of the application management server 20 executes the determination process for the finalizer based on the attendance information (Step S3-5). In addition, when an employee's attendance schedule is changed, a warning may be issued for an application in which the employee is an approver. A response process when the attendance schedule is changed will be described with reference to FIG.

  Here, the control part 21 of the application management server 20 performs the acquisition process of an attendance change information of an authorized person (step S7-1). Specifically, the approval management means 216 of the control unit 21 acquires attendance information about an employee who has newly registered a business trip schedule or an employee who has registered a vacation schedule from the attendance management server 40. Then, the approval management means 216 extracts the attendance information of the employee registered as an authorized person (originally authorized person, delegation employee) in the authority management data storage unit 23 from the attendance information whose attendance schedule has been changed. To do.

  Next, the control unit 21 of the application management server 20 executes an application specifying process registered as an authorizer (step S7-2). Specifically, the approval management means 216 of the control unit 21 searches the application management data storage unit 25 for an application management record 250 in which the employee code of the authorized person whose attendance schedule has been changed is recorded in the authorizer data area. To do.

When the application management record 250 registered as the authorizer is detected, the following processing is repeated for each application.
Here, the control unit 21 of the application management server 20 executes a determination process as to whether or not an approval determination can be made within the approval time limit (step S7-3). Specifically, the approval management unit 216 of the control unit 21 compares the attendance schedule acquired from the attendance management server 40 with the approval deadline registered in the application management record 250. If the attendance schedule is recorded by the time limit for approval in this attendee's attendance information, the application accepting unit 214 determines that the registered authorizer can make an approval decision. On the other hand, if the attendance information of the registered authorizer is no longer scheduled to enter the office by the due date of the authorisation, it is judged that the authorizer cannot make a judgment.

If it is determined that the approval decision can be made within the approval deadline (in the case of “YES” in step S7-3), the processing for this application is terminated.
On the other hand, when it is determined that the approval decision is not possible within the approval deadline (in the case of “NO” in step S7-3), the control unit 21 of the application management server 20 performs other processing similar to steps S6-7 to S6-8. An authority person's attendance information acquisition process (step S7-4) and a determination process (step S7-5) as to whether another authority person can make a decision on approval are executed.

  When it is determined that the approval decision cannot be made even by another authorized person (in the case of “NO” in step S7-5), the control unit 21 of the application management server 20 outputs a warning output to the applicant as in step S6-11. Processing is executed (step S7-6).

  On the other hand, when it is determined that the other authorized person can make the decision (“YES” in step S7-5), the control unit 21 of the application management server 20 executes the setting process for the other authorized person (step S7). -7). Specifically, the application receiving unit 214 of the control unit 21 records the employee code of another authorized person in the approver data area of the application management record 250.

Next, the control part 21 of the application management server 20 performs a change notification process (step S7-8). Specifically, the application reception unit 214 of the control unit 21 notifies the applicant's contact information that the authorizer has been changed.
The above processing is repeated for each application.
As a result, an appropriate authorizer can be set according to the change in the attendance schedule.

  In the above embodiment, in the finalizer registration process, the control unit 21 of the application management server 20 executes a default finalizer acquisition process (step S2-5). Here, the default authorizer may be registered in accordance with the approval record. This authorizer registration process will be described with reference to FIG.

Here, the control part 21 of the application management server 20 performs a user authentication process similarly to step S1-1 (step S8-1).
Next, similarly to steps S2-2 to S2-3, the control unit 21 of the application management server 20 performs the category specifying process (step S8-2) to the finalizer candidate extracting process based on the category (step S8-). 3) is executed.

  Next, the control unit 21 of the application management server 20 executes a determination process for the priority order of the candidates for the final applicant according to the application status (step S8-4). Specifically, the authorizer registration unit 213 of the control unit 21 acquires a processing result for an application for which the specified authority candidate has been approved. Here, the application management record 250 in which the employee code of the authority candidate is recorded and the flag of “Approved” or “Return” is recorded is extracted from the application management data storage unit 25.

  Then, the authorizer registration unit 213 calculates the approval rate by dividing the number of approved applications by the total number. The priority may be determined using the time required from application to confirmation (approval or return). In this case, a high priority is set for the candidate for the authorizer who takes a short time to confirm.

  Next, the control unit 21 of the application management server 20 executes an output process for the authorizer candidate (step S8-5). Specifically, the authorizer registration unit 213 of the control unit 21 creates a candidate list for displaying a list of acquired employee codes as authorizer candidates. In this candidate list, the approval rate is included for each finalist candidate. Then, an authorizer selection screen that enables selection of each candidate in the candidate list is generated and transmitted to the client terminal 10.

Next, the control unit 21 of the application management server 20 performs the default settler acquisition process (step S8-6) and the default settler registration process (step S8-7) as in steps S2-5 to S2-6. Execute.
Thereby, the employee who makes an application can register an appropriate default authorizer in consideration of the application status.

  In the above embodiment, the transfer management process is performed based on the transfer information of the department to which the user belongs. The change information to be subjected to the change management process is not limited to the change of the department to which the user belongs. For example, transfer management processing may be performed by acquiring transfer information such as retirement, leave of absence, and demotement.

  Also, transfer information such as promotion and reinstatement may be acquired, and the authority transfer registration process and the authorizer registration process may be re-executed. Specifically, a candidate for delegation having a qualification code that can newly grant a decision-making authority is registered in the organization table management data storage unit 22 by promotion or reinstatement. When the organization table management data storage unit 22 detects registration of a new candidate for delegation in the organization table management data storage unit 22, the control unit 21 of the application management server 20 re-executes the authority delegation registration process and the authorizer registration process. In this case, an organization in which the candidate for delegation is newly registered is specified, and a message that prompts the original authority of the organization to reexecute the authority delegation registration process is transmitted. In addition, when a new delegation target person is registered, a message urging re-execution of the authority delegation registration process is sent to employees who may make various applications in the organization to which the delegation target person belongs. .

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Application management server, 21 ... Control part, 211 ... User authentication means, 212 ... Delegation registration means, 213 ... Approver registration means, 214 ... Application reception means, 215 ... Approver information acquisition means, 216 ... Approval management means, 217 ... Application notification means, 218 ... Change management means, 22 ... Organization table management data storage section, 23 ... Authority management data storage section, 24 ... Approver registration data storage section, 25 ... Application management data storage Department, 30 ... HR management server, 40 ... Attendance management server.

Claims (10)

An authority management information storage means for storing authority information about the authority of approval corresponding to the application content and authority information about the delegation destination of the authority of approval;
Approver registration information storage means storing default approver information for making approval for each application;
An authority management system comprising a control means for managing approval of an application,
The control means is
Means for authenticating an authorized person accessed from a client terminal, identifying a delegation destination candidate who can delegate approval authority in accordance with the application content in the authorized person, and outputting to the client terminal;
For the user selected among the candidates for delegation, means for registering as an authorized person in which the authority to approve the application content is delegated in the authority management information storage means;
The client terminal authenticates the applicant who has accessed from the client terminal, identifies the authorized person who can make a decision in the authorization management information storage unit based on the application contents acquired from the client terminal, and uses the client terminal as a candidate for decision making Means for outputting to
An authority management system comprising: means for registering an authorized person selected among the authorizer candidates as a default authorizer for the application content in the authorizer registration information storage means. Application management information storage means for storing application management information in which the approver is registered for each application is further provided,
The control means is connected to an attendance management system storing attendance information of each authorized person,
The control means is
When authenticating an applicant who has accessed from a client terminal and obtaining an application from the client terminal, the default authorizer is identified using the authorizer registration information storage means,
Obtaining the default authorizer's attendance information from the attendance management system and outputting it to the client terminal,
2. The authority management system according to claim 1, further comprising means for recording application management information including the authorizer information acquired from the client terminal in the application management information storage means.   If the control means determines that the default authorizer cannot make a decision based on the attendance information, the application management information is set as another authorizer recorded in the authority management information storage means as the authorizer of the application. The authority management system according to claim 2, further comprising means for registering in the storage means.   4. The authority management system according to claim 3, wherein in the attendance information, when the default authorizer does not plan to attend the office by the application approval deadline, the default authorizer determines that the approval decision cannot be made. The control means is
In accordance with the application content, means for calculating a load for confirming the requested approval request content for each approver of the application recorded in the application management information storage means,
The authority according to any one of claims 2 to 4, further comprising means for notifying the approver that an application has been made when the load exceeds a reference value. Management system. In the case where the control means acquires transfer information about the authority of the transfer source, a means for setting a transfer period as an effective period for the authority of the authority stored in the authority management information storage means The authority management system according to any one of claims 1 to 5, further comprising:   When the control means acquires transfer information about the transferee authority, the transfer authority stored in the authority management information storage means is changed to a new authority based on the transfer information. The authority management system according to any one of claims 1 to 6, further comprising:   The control means further comprises means for deleting the authority of the delegation destination stored in the authority management information storage means when the transfer information about the authority of the delegation destination is acquired. The authority management system according to any one of 1 to 7. An authority management information storage means for storing authority information about the authority of approval corresponding to the application content and authority information about the delegation destination of the authority of approval;
Approver registration information storage means storing default approver information for making approval for each application;
A method for managing an application using an authority management system having a control means for managing approval of an application,
The control means is
Authenticating an authorized person accessed from a client terminal, identifying a delegation destination candidate who can delegate approval authority in response to the application content in the authorized person, and outputting to the client terminal;
For the user selected among the candidates for delegation, the authority management information storage means registers as an authorized person who has been delegated the authority to approve the application contents;
The client terminal authenticates the applicant who has accessed from the client terminal, identifies the authorized person who can make a decision in the authorization management information storage unit based on the application contents acquired from the client terminal, and uses the client terminal as a candidate for decision making To output to,
Registering the authorized person selected from among the authorizer candidates as a default authorizer for the application content in the authorizer registration information storage means. An authority management information storage means for storing authority information about the authority of approval corresponding to the application content and authority information about the delegation destination of the authority of approval;
Approver registration information storage means storing default approver information for making approval for each application;
A program for managing an application using an authority management system having a control means for managing approval for the application,
The control means;
Means for authenticating an authorized person who has accessed from a client terminal, and identifying a delegation destination candidate who can delegate decision-making authority corresponding to the application content in the authorized person, and outputting to the client terminal;
Means for registering as an authorized person to whom the authority to approve the application contents is delegated in the authority management information storage means for the user selected among the candidates for delegation;
The client terminal authenticates the applicant who has accessed from the client terminal, identifies the authorized person who can make a decision in the authorization management information storage unit based on the application contents acquired from the client terminal, and uses the client terminal as a candidate for decision making Means for outputting to
An authority management program that causes an authorized person selected from among the authorizer candidates to function as a means for registering in the authorizer registration information storage means as a default authorizer for the application content.

Images