Business request support system

Abstract

To enable smooth business request when requesting business to a specific department.SOLUTION: In a business request support system, employees U are divided into a plurality of departments D, and each employee U is connected to a support server 3 via a communication terminal 2 so as to be able to communicate freely. The support server 3 comprises: an employee information database that stores identification information of the employees U belonging to each department D and identification information of the communication terminals 2 of the employees U, and stores information regarding the authority of each employee U; and a support task that stores request information input by the employee U including a business content to be requested and a request target department D, and provides information including the request information with the business content in which the department D, to which the employee U belongs, is the request target department D, to the employee U in response to access from the employee U who has a predetermined authority.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a task request support system for supporting requests for tasks performed within the same company or the like. [Background technology]

[0002] For example, in a company, requests for work and reports on them are often made by electronic mail (hereafter simply referred to as "email"). In such cases, the email request is often received by the head of the organization or department, and the following procedure must be followed: First, the head must forward the received email to the person in charge of the actual work, and then the person in charge must carry out the work based on the instructions in the email and report back to the head. The head must then check and approve the report, and the person in charge must report the results of the work to the person who requested the work.

[0003] Meanwhile, a method of proxy purchasing of goods that aims to simplify ordering operations in proxy purchasing services is known (see, for example, Patent Document 1). In this method, when information specifying the goods desired to be purchased is sent from the product purchaser's terminal to the server of the proxy purchasing agent, the server sends a list of goods desired to be procured to the terminal of the procurement contractor. Then, when the procurement contractor sees this list and sends information specifying the goods he / she wishes to undertake to the server, the server sends information to the terminal that sent this information first that the procurement work will be entrusted to him / her. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-80358 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the conventional way of requesting work by email, the department head who received the request had to specify the email address of the person in charge and forward the email, or create a separate deadline table to manage deadlines, which was time-consuming and laborious. Also, when the person in charge sends a report to the person requesting the work, the person in charge needs to get the approval of the department head, but depending on the department head's work situation, it can be time-consuming and laborious to get approval.

[0006] Under these circumstances, there has been a demand for technology that allows smooth requesting and execution of work within the same company, etc. Meanwhile, the method of Patent Document 1 makes it possible to select a procurement contractor suitable for the product desired to be procured from among multiple procurement contractors, but cannot be applied when requesting work or tasks to a specific department, etc.

[0007] SUMMARY OF THE PRESENT EMBODIMENTS An object of the present invention is to provide a task request support system that enables a task request to be smoothly carried out when a task is requested from a specific group. [Means for solving the problem]

[0008] In order to solve the above problem, the invention of claim 1 is a work request support system characterized in that it comprises: a plurality of users divided into a plurality of groups, each user being connected to a support server via a communication terminal so as to be able to communicate freely; a user information storage means for storing identification information of users belonging to each group and identification information of the communication terminals of the users in the support server, as well as information relating to the authority of each user; and a support means for storing request information input by a user, the request information including a work content to be requested and a request destination group, and for providing the user with information including the work content of the request information, with the group to which the user belongs being the request destination group, in response to access from the user having a specified authority.

[0009] The invention of claim 2 is characterized in that, in the business request support system described in claim 1, the support means, when identification information of a user in charge of the business content is input by a user having the specified authority, stores the identification information in association with the business content, and provides the user with information including the business content for which the user is the responsible user in response to access from the user.

[0010] The invention of claim 3 is characterized in that, in the business request support system described in claim 2, the support means stores the processing status of the business content input by the responsible user, and provides the user with the processing status of the business content related to the user in response to access from the user.

[0011] The invention of claim 4 is characterized in that, in the business request support system described in claim 2, the support means stores a completion report regarding the business content input by the responsible user, and provides the completion report to a user who belongs to the same group as the responsible user and has specified authority in response to access from the user.

[0012] The invention of claim 5 is characterized in that, in the business request support system described in claim 4, the support means stores an approval sign for the completion report input by a user having the specified authority, and provides the user with a completion report for business content related to the user, which completion report has an approval sign, in response to access from the user. Effect of the Invention

[0013] According to the invention described in claim 1, when a user who wishes to request a task inputs request information including the task content and the request recipient group to the support server, the request information is stored in the support server. On the other hand, when a user with a predetermined authority accesses the support server, the task content and the like requested to the user's group are provided to the user. In this way, both the user who wishes to request a task and the user who will receive the task request can request a task or receive a task request simply by accessing the support server at any time.

[0014] Moreover, a user who receives a task request can check all the requested task contents, etc., simply by accessing the support server. Also, since only users with predetermined authority can check the task contents, etc., requested to their own group, users with predetermined authority can first check the task contents and select a person in charge appropriate for the task contents, thereby enabling the task to be carried out smoothly. In this way, when a task is requested of a specific group, the request for the task and its execution can be carried out smoothly.

[0015] According to the invention described in claim 2, when a user having a certain authority inputs the identification information of a user in charge of a task into the support server, the identification information is stored in the support server in association with the task. On the other hand, when a user accesses the support server, the task content to be handled by the user is provided to the user. In this way, both a user having a certain authority and a user who is in charge of a task can determine a user in charge and check the task content to be handled simply by accessing the support server at any time. Moreover, a user having a certain authority only needs to input the identification information of the user in charge into the support server, and does not need to specify the email address of the person in charge and forward the email as in the conventional case. In this way, when a task is requested of a specific user, the request for the task and its execution can be carried out smoothly.

[0016] According to the invention described in claim 3, when the user in charge inputs the processing status of the business contents to the support server, this processing status is stored in the support server. On the other hand, when the user accesses the support server, the processing status of business contents related to this user, for example, the processing status of business contents requested by this user or the processing status of business contents requested by this user's group, is provided to this user. In this way, both the user in charge and the user who wants to know the processing status can update or check the processing status by simply accessing the support server at any time. In other words, there is no need to create a separate deadline table to manage deadlines as in the past, and it becomes possible to smoothly carry out the business.

[0017] According to the invention described in claim 4, when the user in charge inputs a completion report of the work contents to the support server, this completion report is stored in the support server. On the other hand, when a user who belongs to the same group as the user in charge and has a predetermined authority accesses the support server, the completion report is provided to this user. In this way, both the user in charge and the user with the predetermined authority can update or check the completion report simply by accessing the support server at any time. Moreover, since only users who belong to the same group as the user in charge and have the predetermined authority can check the completion report, it is possible to prevent other users from seeing the completion report before this user, and to smoothly carry out the work.

[0018] According to the invention described in claim 5, when a user having a predetermined authority inputs an approval sign for the completion report to the support server, the approval sign for the completion report is stored in the support server. On the other hand, when a user accesses the support server, a completion report with an approval sign for a task related to the user, for example, a task requested by the user, is provided to the user. In this way, both the user approving the completion report and the user receiving the completion report can approve the completion report or check the approved completion report at any time simply by accessing the support server. In this way, it is possible to provide only the approved completion report to the requesting user, making it possible to smoothly carry out the task. [Brief description of the drawings]

[0019] [Figure 1] 1 is a schematic configuration diagram showing a task request support system according to an embodiment of the present invention; [Diagram 2] 2 is a schematic block diagram showing a configuration of a support server of the work request support system of FIG. 1. [Diagram 3] 3 is a diagram showing a data configuration of an employee information database of the support server of FIG. 2. [Figure 4] FIG. 3 is a diagram showing a start screen of a support task of the support server of FIG. 2. [Diagram 5] FIG. 3 is a diagram showing a new request task screen of the support server of FIG. 2. [Figure 6] FIG. 3 is a diagram showing a contract task screen of the support server of FIG. 2. [Figure 7] FIG. 3 is a diagram showing a screen of requested tasks of the support server of FIG. 2. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, the present invention will be described based on the illustrated embodiment.

[0021] FIG. 1 is a schematic diagram showing a work request support system 1 according to an embodiment of the present invention. This work request support system 1 is a system for requesting and receiving work requests on one and the same platform. Here, in this embodiment, the case where the request and contract of work is supported within one and the same company will be mainly described, but it is also applicable to the request and contract of work within other organizations or between multiple organizations. Also, it is assumed that multiple employees (users) U in a company are divided into and belong to multiple departments (groups) D, and the requests and contract of work are mainly carried out between the departments D.

[0022] In this work request support system 1, each employee U is connected to a support server 3 so as to be able to communicate freely via a communication terminal 2 assigned to each employee.

[0023] The communication terminal 2 is composed of a general-purpose personal computer, and includes an input unit such as a keyboard and a mouse, a display unit, and a communication unit for communicating with the support server 3. A program for accessing a support task 33 of the support server 3, which will be described later, is installed in the communication terminal 2, and this program is activated by clicking on a predetermined icon displayed on the display unit.

[0024] 2, the support server 3 mainly comprises an employee information database (user information storage means) 31, a business information database (business information storage means) 32, a support task (support means) 33, and a central processing unit 36 ​​that controls these. In this embodiment, the support server 3 is configured as an integrated unit and placed within the company, but it may be configured as a plurality of servers or computers, or as a cloud computer, or some or all of the support task 33 may be provided in the communication terminal 2.

[0025] The employee information database 31 is a database that stores information about employees U belonging to each department D. Specifically, as shown in Fig. 3, a terminal ID 312, department 313, job title 314, and others 315 are stored for each employee ID 311. The employee ID 311 stores identification information of this employee U, that is, the name and employee number, and the terminal ID 312 stores identification information of the communication terminal 2 used by this employee U, that is, the device number and IP address.

[0026] The affiliation 313 stores identification information of the department D to which the employee U belongs, that is, the department name and department number, and the position 314 stores information related to the authority of the employee U. Specifically, the position of the employee U (e.g., the head of the department D or the superior of other employees U) and the authority that the employee U has when accessing the support server 3 (what information the employee U can access) are stored.

[0027] The business information database 32 is a database that stores request information input by an employee U and the processing status of business contents in a support task 33 described later.

[0028] The support task 33 is a task program that provides a common platform for the communication terminal 2 of each employee U and supports requests for work, contracts, etc. First, as described above, it is started when a specific icon is clicked on the communication terminal 2, and an initial screen (menu screen) such as that shown in Figure 4 is displayed on the display unit of the communication terminal 2.

[0029] Next, when employee U requests a new task or work, clicking "New" under "Task Request" on this screen launches a new request task 341 in FIG. 2. Also, when employee U wants to check information on a task that has already been requested, clicking "Requested" under "Task Request" launches a requested task 342 in FIG. 2. Also, when employee U wants to check a task that has been requested by his / her department or him / herself, clicking "Task Contract" launches a contract task 35 in FIG. 2. Also, request task 34 in FIG. 2 is a task for controlling new request task 341 and requested task 342. Below, each task 341, 342, and 35 will be explained according to a general flow of requesting and contracting a task.

[0030] 5 (which is a blank sheet at this point) on the display unit of the communication terminal 2. This request information sheet is a sheet for inputting request information including the business content to be requested and the requested department D (the department to which the business is to be performed?), and allows input of the request subject, request content (business content, multiple questions can be input), deadline, target department (requested department D, multiple questions can be input), proposer, confirmer, approver, etc. Then, when the request information is input by employee U into the request information sheet, this request information (input information on the request information sheet), identification information of employee U who input the request information, identification information of department D, input date, etc. are stored in the business information database 32.

[0031] Here, the signatures (approval signatures) in the confirmer and approver columns are stored by a superior U or a department head U (employee U with prescribed authority) who belongs to the same department D as the employee U who entered the request information reading and filling in the request information sheet. At this time, a message that an approval signature is required may be sent to the communication terminal 2 of the superior U or the department head U. Such a new request task 341 may be activated (accessed) by anyone, or may be activated only by an employee U with prescribed authority.

[0032] The processing contents of the contract task 35 differ depending on the authority of the employee U who starts (accesses) it. First, when an employee U with a certain authority, for example, a head U of a department ? who has the authority to decide who will be in charge of the work, accesses it, information including the work contents of the request information for which the department D to which this head (employee) U belongs is requested department D is provided to this head U. That is, first, as shown in Fig. 6(a), a list of all the work requested to this department ? (contract list) is displayed on the communication terminal 2 of this head U.

[0033] This list includes the subject of each task (the request subject on the request information sheet), the requester (the department that made the request?), the deadline, the person in charge (employee U), the processing status (progress), etc. If the employee U in charge of a task has not been decided, the "person in charge" and "processing status" columns will display "Not set."

[0034] In this display state, when a specific subject is clicked, as shown in Fig. 6(b), a contract information sheet based on the request information sheet corresponding to this subject is displayed on the communication terminal 2 of the department head U. In this way, the department head U can obtain information on the work requested to his / her department D. Here, in addition to the request subject and request contents (report contents described later can be input) deadline and target area on the request information sheet, it is also possible to input the person to handle, processing status, proposer, confirmer, approver, etc.

[0035] Then, in a contract information sheet for a subject for which a person to handle the work (employee U) has not yet been decided, when the department head U inputs the identification information of the employee U in charge of the work content, this identification information is associated with the work content and subject, that is, stored as information for this contract information sheet in the work information database 32. At this time, "Not started" is stored in the "Processing status" column of this contract information sheet.

[0036] On the other hand, when an employee U (a general employee without the prescribed authority) who may be selected as the responsible employee U accesses the contract task 35, information including the work content for this employee U as the responsible employee U is provided to this employee U. That is, a contract list and a contract information sheet in which the identification information of this employee U is stored in the "response" field are displayed on the communication terminal 2 of this employee U. In this way, employee U can obtain information regarding the work requested of him / her.

[0037] Next, this employee U starts the requested work and inputs the processing status of the work content in the "Processing Status" column of the contract information sheet according to the progress of the work, and this processing status is associated with the work content and subject, that is, stored as information of this contract information sheet in the work information database 32. Here, the processing status can be input in any way, but the degree of completion can be expressed as a percentage, or the processing status can be explained in words.

[0038] After that, for example, when a manager U of the same department D as the responsible employee U accesses the contract task 35, the contract list of Fig. 6(a) or the contract information sheet of Fig. 6(b) with the latest processing status entered in the "processing status" column is displayed on the communication terminal 2 of the manager U. In this way, in response to access from the employee U of the requested department D, the processing status of the work contents related to this employee U is provided to this employee U.

[0039] On the other hand, when an employee U of the requesting department D (department ? that requested the work) starts / accesses the requested task 342, first, a list of the work requested by this department ? is displayed on the communication terminal 2, as shown in Fig. 7(a). In this embodiment, when an employee U of the requesting department D who has a certain authority (for example, a department head U) accesses the system, a list of all the work requested by this department ? (request list by department) is displayed, and when an employee U who does not have the certain authority accesses the system, a list of all the work requested by this employee U (who is the initiator) (request list by employee) is displayed.

[0040] This list includes the subject of each task (request subject on the request information sheet), target location, deadline, reporting location, completion rate (processing status), etc. Here, if the target location targets multiple departments D, the reporting location is expressed as (number of reporting departments) / (total number of target departments), and the completion rate is expressed as a percentage of the reporting location. Also, if the target location is a single department D, the reporting location represents the requested department ?, and the completion rate represents the processing status of the above-mentioned contract information sheet. In this way, in response to access from employee U of the requesting department D, the processing status of the work content related to this employee U is provided to this employee U.

[0041] On the other hand, when a responsible employee U of the requested department D completes the requested work and enters a completion report on the work content (report on the questions) in the "Request content / report content" column of the above-mentioned contract information sheet, and also enters completion of the work in the "Processing status" column, this input information is associated with the work content / subject, that is, stored in the business information database 32 as information on this contract information sheet.

[0042] Thereafter, for example, when a superior U or a head U of the department D of the employee U in charge accesses the contract task 35, a contract information sheet in which a completion report has been entered in the "Request content / report content" column and task completion has been entered in the "Processing status" column is displayed on the communication terminal 2. In this way, in response to access from an employee U who belongs to the same department D as the employee U in charge and has prescribed authority, a completion report of the task content related to this employee U is provided to this employee U. Then, when the superior U or a head U looks at the completion report and enters his / her signature (approval signature) in the confirmer column or approver column, this signature is associated with the task content / subject, that is, stored in the task information database 32 as information on this contract information sheet.

[0043] Next, when employee U of requesting department D accesses requested tasks 342 and clicks on a specific subject in the list in Fig. 7(a) (a request list by department or a request list by employee according to employee U's authority), a request content sheet based on the request information sheet corresponding to this subject is displayed on employee U's communication terminal 2, as shown in Fig. 7(b). Here, the request content sheet includes the request subject, request content, deadline, and target area of ​​the request information sheet, as well as a "display report list" button, a "display statistical information" button, a "download" button, etc.

[0044] Then, when the "Display report list" button is clicked, as shown in the request report sheet of FIG. 7(c), the completion report for this task content / subject, which is signed by the superior U or department head U of the requested department D, is obtained from the corresponding contract information sheet and displayed on the communication terminal 2. At this time, if there are multiple target locations, i.e., multiple requested departments D, the completion reports from each requested department D are displayed. In this way, in response to access from employee U, a completion report for the task content related to this employee U, which is signed by an approval, is provided to this employee U. Also, when the "Display statistical information" button is clicked, statistical information such as the processing status and completion report is displayed on the communication terminal 2, and when the "Download" button is clicked, this information is downloaded to the communication terminal 2.

[0045] As described above, according to this work request support system 1, when an employee U who wants to request work inputs request information such as the work content and the requested department D into the support server 3, the request information is stored in the support server 3. On the other hand, when an employee U with a predetermined authority accesses the support server 3, the work content and other information requested from the department D of this employee U is provided to this employee U. In this way, both the employee U who wants to request work and the employee U who will receive the work request can request work or receive a work request simply by accessing the support server 3 at any time.

[0046] Moreover, the employee U who receives the request for work can check all the requested work contents, etc., simply by accessing the support server 3. Also, since only the employee U with the specified authority can check the work contents, etc., requested to his / her own department D, the employee U with the specified authority can first check the work contents and select a person in charge suitable for the work contents, thereby enabling the work to be carried out smoothly. In this way, when requesting work to a specific department D, the request for work and its execution can be carried out smoothly.

[0047] In addition, when an employee U having a certain authority inputs the identification information of the employee U in charge of the work content into the support server 3, this identification information is stored in the support server 3 in association with the work content. On the other hand, when the employee U accesses the support server 3, the work content to be handled by this employee U, etc. are provided to this employee U. In this way, both the employee U having the certain authority and the employee U who is to be in charge of the work can decide the employee U in charge and confirm the work content to be handled by simply accessing the support server 3 at any time. Moreover, the employee U having the certain authority only needs to input the identification information of the employee U in charge into the contract information sheet displayed on the communication terminal 2, and there is no need to specify the email address of the person in charge and forward the email as in the conventional case. In this way, when requesting a work from a specific employee U, it is possible to smoothly request the work and carry it out.

[0048] Also, when the employee U in charge inputs the processing status of the work content into the contract information sheet of the support server 3, this processing status is stored in the support server 3. On the other hand, when the employee U accesses the support server 3, the processing status of the work content related to this employee U, for example, the work content requested by this employee U and the work content requested by the department D of this employee U, is provided to this employee U. In this way, both the employee U in charge and the employee U who wants to know the processing status can update or check the processing status by simply accessing the support server 3 at any time. In other words, there is no need to create a separate deadline table to manage deadlines as in the past, and it is possible to smoothly carry out the execution of work, etc.

[0049] Also, when the employee U in charge inputs a completion report of the work content into the contract information sheet of the support server 3, this completion report is stored in the support server 3. On the other hand, when an employee U who belongs to the same department D as the employee U in charge and has a predetermined authority accesses the support server 3, the completion report is provided to this employee U. In this way, both the employee U in charge and the employee U who has the predetermined authority can update or check the completion report simply by accessing the support server 3 at any time. Moreover, since only the employee U who belongs to the same department D as the employee U in charge and has the predetermined authority can check the completion report, it is possible to prevent other employees U from seeing the completion report before this employee U, and to smoothly carry out the work.

[0050] Furthermore, when an employee U with a certain authority inputs an approval signature for the completion report into the contract information sheet of the support server 3, the approval signature for the completion report is stored in the support server 3. On the other hand, when the employee U accesses the support server 3, a completion report (request report sheet) with an approval signature for the work content related to the employee U, for example, the work content requested by the employee U, is provided to the employee U. In this way, both the employee U approving the completion report and the employee U receiving the completion report can approve the completion report or confirm the approved completion report at any time simply by accessing the support server 3. In this way, it is possible to provide only the approved completion report to the requesting employee U, making it possible to smoothly carry out the work.

[0051] Although the embodiment of the present invention has been described above in detail, the specific configuration is not limited to this embodiment, and even if there are design changes within the scope of the present invention, they are included in the present invention. For example, in the above embodiment, information is input, stored, displayed, and provided via a request information sheet, a contract information sheet, a request content sheet, a request report sheet, etc., but necessary information may be input, stored, displayed, and provided without using these sheets, etc. [Explanation of symbols]

[0052] 1. Business request support system 2. Communication terminals 3 Support Server 31 Employee information database (user information storage means) 32 Business information database (business information storage means) 33 Support tasks (support methods) U Employee (User) D Department (Group)

Claims

1. A plurality of users are divided into a plurality of groups, and each user is connected to a support server via a communication terminal so as to be able to communicate with the support server; The support server, a user information storage means for storing identification information of users belonging to each group and identification information of the communication terminals of the users, and for storing information regarding the authority of each user; a support means for storing request information including a task content to be requested and a request destination group input by a user, and for providing, in response to access from a user having a predetermined authority, information including the task content of the request information with a group to which the user belongs as a request destination group to the user; A task request support system comprising:

2. When the user having the predetermined authority inputs identification information of a user in charge of the task, the support means stores the identification information in association with the task, and In response to an access from a user, provide the user with information including the business content for which the user is a responsible user; 2. The task request support system according to claim 1.

3. The support means stores the processing status of the task content input by the user in charge, In response to an access from a user, providing the user with the processing status of business content related to the user; 3. The work request support system according to claim 2.

4. The support means stores a completion report regarding the work content input by the user in charge, providing the completion report to a user who belongs to the same group as the user in charge and has a predetermined authority in response to an access from the user; 3. The work request support system according to claim 2.

5. The support means stores an approval sign for the completion report inputted by the user having the predetermined authority, In response to an access from a user, provide the user with a completion report of a task related to the user, the completion report having an approval signature; 5. The work request support system according to claim 4.

Images