JP2022087634A - Information processing device, request management system, and program - Google Patents

Abstract

To provide an information processing device that can call attention to a notice that work is urged to be completed.SOLUTION: An information processing device 10 that communicates with a first terminal device 30 operated by a requester requesting work and a second terminal device 30 operated by a worker performing the work includes: a work request transmission unit that communicates with the second terminal device and requests the worker to perform the work requested by the communication with the first terminal device; a work completion reception unit that receives completion of the work by communicating with the second terminal device; and an information transmission control unit that transmits a notice that the work is urged to be completed to a destination at the second terminal device, for a request for which the work completion reception unit has not received the completion of the work. The information transmission control unit causes the notice that the work is urged to be completed to include a first character string related to the request and a second character string corresponding to information set by the requester.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information processing apparatus, a request management system, and a program.

A request management system is known in which a requester requests a worker to perform work, and the worker performs the requested work and reports the completion of the work. The request management system manages the progress of work for each request.

When the completion of the work is not registered, the information processing device of the request management system can send a message to the requested worker to urge the completion of the work in order to prompt the completion of the work (for example, Patent Document 1). reference.). Patent Document 1 discloses a technique for switching a notification time for prompting the completion of work based on weight information for each preset user.

However, in the conventional technique, there is a problem that attention is not drawn to prompting the completion of the work. That is, conventionally, the fact that the information processing device prompts the completion of the work is a mechanical text that only gives a notification, and there have been cases where the worker does not read it.

In view of the above problems, it is an object of the present invention to provide an information processing apparatus capable of calling attention to prompting the completion of work.

In view of the above problems, the present invention is an information processing device that communicates with a first terminal device operated by a client requesting work and a second terminal device operated by a worker performing the work. The work requested by communication with the first terminal device is the work requested by communication with the second terminal device and a work request transmission unit that communicates with the second terminal device to request the worker. The work completion reception unit that accepts the completion of the work, and the information transmission control unit that sends the second terminal device to the destination to urge the completion of the work for the request that the work completion reception unit has not accepted the completion of the work. The information transmission control unit is characterized by including a first character string related to a request and a second character string corresponding to the information set by the requester in order to prompt the completion of the work. ..

It is possible to provide an information processing device that can call attention to the fact that the work is urged to be completed.

It is a figure explaining the e-mail which a request management server sends to a terminal device of a worker. It is a figure which shows the system configuration example of the request management system. It is a figure which shows the hardware configuration example of the request management server. It is a figure which shows the hardware configuration example of a terminal apparatus. This is an example of a diagram for explaining the functions of the request management server and the terminal device of the request management system by dividing them into blocks. This is an example of a diagram illustrating the flow of data in a request management system. This is an example of a sequence diagram showing the procedure for the request management system to manage requests. It is a figure which shows an example of the work request information input screen displayed by the terminal apparatus of a requester. It is a figure which shows an example of the answer input screen displayed by the terminal apparatus of a worker. This is an example of a sequence diagram showing a procedure in which a request management server sends an e-mail prompting the completion of work to a terminal device of a worker. It is a figure which shows an example of the e-mail prompting the completion of work, and the Web page prompting the completion of work. This is an example of a sequence diagram showing a procedure for a requester to register a subject tag in user data. It is a figure which shows an example of the user data input screen displayed by the terminal apparatus of a requester. It is a figure which shows an example of the work request information input screen displayed by the terminal apparatus of a requester. This is an example of a sequence diagram showing a procedure in which a request management server sends an e-mail prompting the completion of work to a terminal device of a worker. It is a figure which shows an example of the user data input screen displayed by the terminal apparatus of a requester. It is a figure which shows an example of the e-mail which prompts the completion of work, which is displayed by the terminal apparatus of a worker (Mr. B). It is a figure which shows an example of the e-mail which prompts the completion of the work displayed by the terminal device of a worker (Mr. C). It is a figure which shows an example of the e-mail which prompts the completion of the work displayed by the terminal device of a worker (Mr. A). This is an example of a sequence diagram showing the procedure for the request management system to manage requests. It is a figure which shows an example of the work request notification mail displayed by the terminal device of a worker. This is an example of a sequence diagram showing the procedure for the request management system to manage requests. It is a figure which shows an example of the e-mail which informs the request of work displayed by the terminal device of a worker.

Hereinafter, as an example of the embodiment for carrying out the present invention, the request management system and the information transmission method performed by the request management system will be described with reference to the drawings.

FIG. 1 is a diagram illustrating an e-mail transmitted by a request management server 10 to a worker's terminal device 30 in response to a requester's operation. The relationship between the requester and the worker may be, for example, a relationship in which the requester knows the worker's e-mail address. Therefore, the requester and the worker can use the request management system 1 if they are friends or colleagues. Further, when the user can belong to a group in the request management system 1, the request management system 1 can limit the workers to whom the requester can request the work to the same group as the requester. In this case, the group is, for example, a company, department, development team, and so on. Further, the group may be a tenant, and the request management system 1 can charge an individual or a tenant. The tenant means information indicating a customer who shares the same software with a plurality of customers, that is, a company or the like which is a set of customers.

(1) The requester operates the terminal device 30 (an example of the first terminal device) and registers the work request information for requesting the work to the worker in the request management server 10.

(2) The worker's terminal device 30 (an example of the second terminal device) receives a work request by e-mail or the like. The worker usually performs the work according to the content of the request, operates the terminal device 30, and registers the work completion information indicating that the work is completed in the request management server 10.

(3) There may be a case where the worker does not perform the work and does not register the work completion information in the request management server 10, or the worker does not register the work completion information in the request management server 10 even if the work is performed. In such a case, the request management server 10 transmits to the operator's terminal device 30 that the work is urged to be completed.

The request management server 10 of the present embodiment sets the subject of the e-mail to prompt the completion of the work based on the work request information (delivery date, subject tag, request worker, etc.) input by the requester. For example, if the subject tag set by the requester when registering the request is "Urgent", the request management system 1 sets "Urgent" as the subject of the e-mail. In FIG. 1, "Please answer about [Urgent] **" is the subject, and "Urgent" is set at the beginning of the subject.

As described above, according to the request management server 10 of the present embodiment, the subject to prompt the completion of the work is set based on the information input by the requester, so that attention can be drawn to read the e-mail.

<Terminology>
A request means asking a person to do the work. Work means to work or work by working the body or brain. Since the request management system 1 manages the progress of the work, the worker registers the completion of the work in the request management system 1.

Requests can be completed simply by looking at the title and body of the email, or the title and body of the email tell you what work to do (for example, a request with a title such as "Please enter your attendance". ) And some of the work to be done cannot be understood without looking at the details of the request. In this embodiment, the content of the work may be anything. In addition, for a request that is completed simply by looking at the title and body of the e-mail, the answer is work.

The subject is the name of the item to be treated as one group. In this embodiment, the subject of e-mail will be described as an example. The subject may be referred to as a title, a heading, or the like.

The information that prompts the completion of the work may be information that the worker can understand. Prompting for the completion of work is communicated, for example, by language or other symbols. In addition to Japanese and English sentences, codes, symbols, pictograms, etc. may be used to prompt the completion of the work. In this embodiment, an embodiment in which an e-mail prompting the completion of work is transmitted will be described. However, the request management server may notify by SNS (Social Network System). Further, the request management system 1 may send a push notification from a smartphone or the like to prompt the completion of the work. Encouraging the completion of work is also called a reminder, a reminder, a reminder, or a reminder.

The first string is information about the request set in the subject of the email. This information includes the fact that it is an e-mail regarding the request for work. The first character string may be set by the user or may be predetermined. Conventionally, the first character string may not be highly alert.

The second character string is a character string set separately from the first character string. The second character string is set according to the information set by the requester. The information set by the requester may be any information set by the requester in the request management system 1 by operating the terminal device 30. The second character string is set from, for example, the work request information input at the time of request, the user data registered by the requester, or the like.

<System configuration example>
FIG. 2 is a diagram showing a system configuration example of the request management system 1. The request management system 1 includes a request management server 10, a mail server 20, a terminal device 30 (terminal device 30a, terminal device 30b, terminal device 30c, etc.), and a work management server 40. The request management server 10, the mail server 20, the terminal device 30, and the work management server 40 are connected to each other so as to be able to communicate with each other via the communication network 50.

A server is a computer or software that functions to provide information and processing results in response to a request from a client.

The request management server 10 is one or more information processing devices having a work request management function. For example, the request management server 10 receives work request information from the terminal device 30 operated by the requester and registers it in the request management data. The request management server 10 sends a work request notification mail addressed to the worker's mail address to the mail server 20. Further, the request management server 10 receives work completion information from the terminal device 30 operated by the worker and updates the progress status of the request management data. The progress of the present embodiment is, for example, whether or not there is a response to complete the work and the date and time of the response.

The mail server 20 is a server device having a function of sending and receiving e-mail. For example, the mail server 20 receives a work request notification mail from the request management server 10 and sends it to the terminal device 30 operated by the worker (in both POP3 and IMAP, the worker's terminal device connects to the mail server and sends the work request notification mail. If there is an e-mail addressed to the worker, the worker's terminal device 30 can receive the e-mail). The same applies to other emails.

The terminal device 30 is a terminal device 30 for using the functions provided by the request management server 10, the mail server 20, or the work management server 40 in response to the operation of the user who is the requester or the worker. The terminal device 30 is a general term for cases where individual terminals such as the terminal device 30a, the terminal device 30b, the terminal device 30c, and the like are not distinguished. The user who uses the terminal device 30 can be a requester who requests work, or can be a worker who receives a work request. That is, each user can be a requester for one task and a worker for another task.

The work management server 40 is a server device for a user who is a worker to perform work. For example, the work management server 40 when the work content is an attendance input is a server device that provides an attendance management function. Various servers can be the work management server 40 depending on the work.

The communication network 50 is a communication network by wireless communication or wired communication. Specifically, the communication network 50 may be the Internet, WAN (Wide Area Network), LAN (Local Area Network), VPN (Virtual Private Network), or a combination thereof.

The request management server 10, the mail server 20, and the work management server 40 may exist in a cloud on the Internet, an on-premises cloud, or simply on-premises. The cloud is a technique in which a user uses resources on a network without being aware of specific hardware resources.

<Hardware configuration example>
<< Request Management Server >>
FIG. 3 is a diagram showing an example of the hardware configuration of the request management server 10. As shown in FIG. 3, the request management server 10 is constructed by a computer, and has a CPU 101, a ROM 102, a RAM 103, an HD 104, an HDD (Hard Disk Drive) controller 105, a display 106, and an external device connection I / F (Interface) 108. , Network I / F 109, data bus 110, keyboard 111, pointing device 112, DVD-RW (Digital Versatile Disk Rewritable) drive 114, and media I / F 116.

Of these, the CPU 101 controls the operation of the entire request management server 10. The ROM 102 stores a program used for driving the CPU 101 such as an IPL (Initial Program Loader). The RAM 103 is used as a work area of the CPU 101. The HD 104 stores various data such as programs. The HDD controller 105 controls reading or writing of various data to the HD 104 according to the control of the CPU 101. The display 106 displays various information such as cursors, menus, windows, characters, or images.

The external device connection I / F 108 is an interface for connecting various external devices. The external device in this case is, for example, a device such as a USB (Universal Serial Bus) memory or a printer. The network I / F 109 is an interface for data communication with the mail server 20, the terminal device 30, and the like via the communication network 50. The data bus 110 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 101 shown in FIG.

Further, the keyboard 111 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 112 is a kind of input means for selecting or executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 114 controls reading or writing of various data to the DVD-RW 113, which is an example of a removable recording medium. The DVD-RW 113 may be a DVD-R or the like. The media I / F 116 controls reading or writing (storage) of data to the media 115 such as a flash memory.

The mail server 20 and the work management server 40 may have the same hardware configuration as the request management server 10.

<< Terminal device >>
The terminal device 30 may have the same hardware configuration as the request management server 10, and may be a smartphone, a wearable PC, a desktop PC, or the like. The terminal device 30 may be an MFP (Multifunction Peripheral), an IWB (Interactive White Board: a white board having an electronic blackboard function capable of mutual communication), or a PJ (Projector) as long as the device can use the browser function. : Projector) or digital signage or the like.

As an example, the hardware configuration when the terminal device 30 is a smartphone is shown.

FIG. 4 is a diagram showing an example of the hardware configuration of the terminal device 30. The terminal device 30 includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 304, a CMOS sensor 305, an image sensor I / F 306, an acceleration / direction sensor 307, a media I / F 309, and a GPS receiving unit 311.

Of these, the CPU 301 controls the operation of the entire terminal device 30. The ROM 302 stores a program used to drive the CPU 301 such as the CPU 301 or IPL. The RAM 303 is used as a work area of the CPU 301. The EEPROM 304 reads or writes various data such as a smartphone program according to the control of the CPU 301. The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a kind of built-in imaging means for acquiring image data by imaging a subject (mainly a self-image) under the control of the CPU 301. The CMOS sensor may be an image pickup means such as a CCD (Charge Coupled Device) sensor.

The image sensor I / F 306 is a circuit that controls the drive of the CMOS sensor 305. The acceleration / orientation sensor 307 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect the geomagnetism. The media I / F 309 controls reading or writing (storage) of data to the recording medium 308 such as a flash memory. The GPS receiving unit 311 receives a GPS signal from a GPS satellite.

Further, the terminal device 30 includes a long-distance communication circuit 312, a CMOS sensor 313, an image pickup element I / F 314, a microphone 315, a speaker 316, a sound input / output I / F 317, a display 318, and an external device connection I / F (Interface) 319. It includes a short-range communication circuit 320, an antenna 320a of the short-range communication circuit 320, and a touch panel 321.

Of these, the long-distance communication circuit 312 is a circuit that communicates with the request management server 10, the mail server 20, the work management server 40, and the like via the communication network 50 via the wireless network. The CMOS sensor 313 is a kind of built-in image pickup means for capturing an image of a subject and obtaining image data under the control of the CPU 301. The image sensor I / F 314 is a circuit that controls the drive of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts an electric signal into physical vibration to produce sounds such as music and voice.

The sound input / output I / F 317 is a circuit that processes sound signal input / output between the microphone 315 and the speaker 316 under the control of the CPU 301. The display 318 is a kind of display means such as a liquid crystal display or an organic EL (Electro Luminescence) for displaying an image of a subject, various icons, and the like. The external device connection I / F 319 is an interface for connecting various external devices. The short-range communication circuit 320 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a kind of input means for operating the terminal device 30 by the user pressing the display 318.

Further, the terminal device 30 includes a bus line 310. The bus line 310 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 301 shown in FIG.

<About functions>
Next, the functions of each device will be described with reference to FIG. FIG. 5 is an example of a diagram in which the functions of the request management server 10 and the terminal device 30 of the request management system 1 are described by dividing them into blocks.

The request management server 10 has a communication unit 11, an information transmission control unit 17, and a request management unit 18. Further, the request management unit 18 has an input reception unit 12, a work request transmission unit 13, a work completion reception unit 14, a screen information generation unit 15, and a work completion notification unit 16. Each functional unit of the request management server 10 is a function or means realized by the CPU 101 executing an instruction included in one or more programs installed in the request management server 10.

The communication unit 11 transmits and receives various information to and from the terminal device 30 or the work management server 40. For example, the communication unit 11 transmits a Web page for inputting work request information to the terminal device 30, and receives work request information from the terminal device 30. The communication unit 11 transmits the work request notification mail to the terminal device 30 of the worker. Further, when the communication unit 11 receives the work completion information from the terminal device 30 of the worker, the communication unit 11 sends a work completion notification mail to the terminal device 30 of the requester. Further, the communication unit 11 sends an e-mail prompting the completion of the work to the terminal device 30 of the worker as needed.

The input receiving unit 12 receives information input by the user's operation from the terminal device 30 via the communication unit 11. For example, the input receiving unit 12 receives work request information from the terminal device 30 operated by the user who is the requester, and registers it in the request management data storage unit 22.

The work request transmission unit 13 transmits a work request notification email to the worker's email address (send to the mail server) based on the work request information registered in the request management data storage unit 22 via the communication unit 11. do).

The work completion reception unit 14 receives a work completion report from the worker's terminal device 30 via the communication unit 11. For example, the work completion reception unit 14 receives the work completion information from the terminal device 30 operated by the worker, and updates the response contents and the response date values managed by the request management data storage unit 22.

The work completion notification unit 16 notifies the requester's terminal device 30 of the completion of the work via the communication unit 11. For example, the work completion notification unit 16 sends a work completion notification e-mail to the e-mail address of the work requester (sends to the mail server) for the request for which the work completion information has been received.

The screen information generation unit 15 generates information on the screen displayed by the terminal device 30. Specifically, the screen information generation unit 15 generates screen information of a Web page for the terminal device 30 to display various screens described later. The screen information is transmitted as, for example, an HTTP (Hypertext Transfer Protocol) response, and is described in a language such as HTML (Hypertext Markup Language), JavaScript (registered trademark), and CSS (Cascade Style Sheet). The screen information is provided as a web page or a web application. A Web application refers to software or a mechanism thereof that operates by coordinating a program in a programming language (for example, JavaScript (registered trademark)) that operates on a browser with a program on the Web server side and is executed on the browser. The request management server 10 can dynamically change a web page by a web application.

The information transmission control unit 17 transmits an e-mail urging the worker to complete the work to the terminal device 30 of the worker via the communication unit 11. Such emails are sometimes referred to as reminders. Further, since the e-mail is transmitted using, for example, the e-mail mechanism, the information transmission control unit 17 sends an e-mail prompting the completion of the work to the mail address of the work requester to the mail server.

Further, the request management server 10 has a storage unit 19 built in the HD 104, the RAM 103, or the like shown in FIG. The storage unit 19 has a user data storage unit 21 and a request management data storage unit 22.

表１はユーザデータ記憶部２１に記憶されているユーザデータを模式的に示す。ユーザデータは、依頼管理システム１のユーザに関する情報が登録されている。例えば、ユーザデータ記憶部２１は、ユーザＩＤ、ユーザ名、及び、メールアドレス、の項目を有している。
・ユーザＩＤは、ユーザ（依頼者又は作業者）を識別するための識別情報である。
・ユーザ名は、ユーザの一般的な氏名など示すテキストである。
・メールアドレスは、ユーザの電子メールアドレスである。

Table 1 schematically shows the user data stored in the user data storage unit 21. In the user data, information about the user of the request management system 1 is registered. For example, the user data storage unit 21 has items of a user ID, a user name, and an e-mail address.
-The user ID is identification information for identifying a user (requester or worker).
-The user name is a text indicating the general name of the user.
-The email address is the user's email address.

The user data in Table 1 is just an example, and in addition to being shown in Table 1, it may include a password, a department, a group, a performance rate of past work, and the like. A group is a group of users who can request work.

表２は依頼管理データ記憶部２２に記憶されている依頼管理データを模式的に示す。依頼管理データには、依頼管理システム１の作業依頼情報と作業完了情報が登録されている。例えば、依頼管理データ記憶部２２は、作業依頼ＩＤ、タイトル、依頼内容、納期、件名タグ、依頼者、作業者、回答内容、及び、回答日の各項目を有している。
・作業依頼ＩＤは、作業依頼を識別するための識別情報である。なお、ＩＤはIdentificationの略であり識別子や識別情報という意味である。ＩＤは複数の対象から、ある特定の対象を一意的に区別するために用いられる名称、符号、文字列、数値又はこれらのうち１つ以上の組み合わせをいう。
・タイトルは、依頼の名称である。
・依頼内容は、依頼者が入力した具体的な依頼内容である。
・納期は、依頼者が指定した作業の完了期限である。例えば、納期は年月日及び時分である。
・件名タグは、依頼者が指定した、電子メールの件名に設定される文字列である。電子メールの件名に件名タグの値が設定される。例えば、件名タグは「至急」「☆☆☆」「◇◇◇」など、作業者の注意を喚起する文字列（文字だけでなく、記号、数字、アルファベット等を含む）であるとよい。
・依頼者は、依頼者を識別するための識別情報（表１のユーザＩＤ又はユーザ名）である。
・作業者は、依頼者が設定した、作業者を識別するための識別情報（表１のユーザＩＤ又はユーザ名）である。
・回答内容は、作業者が回答した内容である。回答内容は、必ずしも作業者が入力するとは限らず、「完了」などを示す情報が登録される場合がある。
・回答日は、作業が完了した日時を示す。依頼管理サーバ１０は、作業完了情報を受信すると、回答日の項目に作業完了情報の受信日時を設定する。

Table 2 schematically shows the request management data stored in the request management data storage unit 22. The work request information and work completion information of the request management system 1 are registered in the request management data. For example, the request management data storage unit 22 has items such as a work request ID, a title, a request content, a delivery date, a subject tag, a requester, a worker, a reply content, and a reply date.
-The work request ID is identification information for identifying the work request. ID is an abbreviation for Identification and means an identifier or identification information. An ID refers to a name, a code, a character string, a numerical value, or a combination thereof used to uniquely distinguish a specific object from a plurality of objects.
-The title is the name of the request.
-The request content is the specific request content entered by the requester.
-The delivery date is the deadline for completing the work specified by the client. For example, the delivery date is the date and hour.
-The subject tag is a character string specified by the requester and set in the subject of the e-mail. The subject tag value is set in the subject of the email. For example, the subject tag may be a character string (including not only characters but also symbols, numbers, alphabets, etc.) that draws the attention of the operator, such as "urgent", "☆☆☆", and "◇◇◇".
-The requester is identification information (user ID or user name in Table 1) for identifying the requester.
-The worker is the identification information (user ID or user name in Table 1) set by the requester for identifying the worker.
-The content of the answer is the content that the worker answered. The answer content is not always entered by the worker, and information indicating "completion" or the like may be registered.
-The answer date indicates the date and time when the work was completed. When the request management server 10 receives the work completion information, the request management server 10 sets the reception date and time of the work completion information in the item of the reply date.

Of the request management data in Table 2, the items of title, request content, delivery date, subject tag, requester, and worker are work request information. The response content and response date are work completion information. Further, the data for one row of Table 1 or Table 2 may be referred to as a record.

For records with work request ID = 1, the title is "About XX", the content of the request is "Please answer about XX", the delivery date is "2019/12/20", the requester is Mr. A, and the worker is B. Is. The subject tag is "Urgent".

For records with work request ID = 2, the title is "About XX", the content of the request is "Please answer about XX", the delivery date is "2019/12/20", the requester is Mr. A, and the worker is C. Is. That is, Mr. A has made the same request to Mr. B and Mr. C. Also, in the record with work request ID = 2, Mr. B has already answered "□□" on "2019/12/19". The subject tag is "☆☆☆".

For records with work request ID = 3, the title is "About △△", the request content is "How about △", the delivery date is "2019/12/27", the requester is Mr. B, and the worker is Mr. C. be. The subject tag is "◇◇◇".

Workers may overlook or forget that they have received a request. Therefore, the request management server 10 generates an e-mail urging the worker to complete the work and notifies the worker.

<< Terminal device >>
The terminal device 30 has a communication unit 31, a display control unit 32, and an operation reception unit 33. Each functional unit included in the terminal device 30 is a function or means realized by the CPU 301 executing an instruction included in one or more programs installed in the terminal device 30. This program may be a Web browser or a dedicated application (software).

The communication unit 31 transmits / receives various information to / from the request management server 10, the mail server 20, or the work management server 40 (an example of the second communication unit). For example, the communication unit 31 of the terminal device 30 operated by the requester transmits the work request information input by the requester to the request management server 10. The communication unit 31 of the terminal device 30 operated by the requester receives the work completion notification mail. Further, the communication unit 31 of the terminal device 30 operated by the worker receives a work request notification mail and an e-mail urging the completion of the work from the mail server 20. The communication unit 31 of the terminal device 30 operated by the operator transmits the work completion information to the request management server 10.

The display control unit 32 displays various information received by the communication unit 31 on the display 318. For example, the display control unit 32 of the terminal device 30 operated by the requester displays a Web page or the like for inputting work request information. The display control unit 32 of the terminal device 30 operated by the operator displays a work request notification mail, an e-mail prompting the completion of the work, and the like. The display control unit 32 of the terminal device 30 operated by the operator displays a Web page or the like for inputting work completion information.

The operation reception unit 33 receives an operation by a user as a requester or a worker. For example, the operation reception unit 33 of the terminal device 30 operated by the requester accepts the input operation of the work request information. Further, the operation reception unit 33 of the terminal device 30 operated by the operator accepts input of work completion information (for example, answer contents).

<Overall flow>
FIG. 6 is a diagram illustrating a data flow in the request management system 1. Note that FIG. 6 does not describe the transmission of an e-mail urging the completion of the work.
(1) The requester sends work request information to the request management server 10.
(2) The request management server 10 registers work request information in the request management data storage unit 22.
(3) The request management server 10 acquires the worker's e-mail address from the user data storage unit 21.
(4) The request management system 1 sends a work request notification mail to the terminal device 30 operated by the worker.
(5) The worker performs the work and sends the work completion information to the request management server 10. The work may be different from the work completion information, or the transmission of the work completion information itself may be the work.
(6) The request management server 10 registers work completion information in the request management data storage unit 22.
(7) The request management server 10 acquires the requester's e-mail address from the user data storage unit 21.
(8) The request management server 10 sends a work completion notification mail to the terminal device 30 operated by the requester.

<Operation of request management system>
FIG. 7 is an example of a sequence diagram showing a procedure in which the request management system 1 manages requests.

S1: The requester operates the terminal device 30 to communicate the terminal device 30 with the request management server 10. The requester logs in to the request management server 10 by entering, for example, a user name and a password. The display control unit 32 of the requester's terminal device 30 displays a work request information input screen to be described later in response to the requester's operation. FIG. 8 shows an example of the work request information input screen.

When the requester inputs the work request information on the work request information input screen, the operation reception unit 33 of the terminal device 30 accepts the input. Further, when the requester inputs a transmission operation, the communication unit 31 transmits the work request information to the request management server 10. The requester inputs "title", "request content", "delivery date", "subject tag", and "worker". The "requester" is automatically determined by logging in.

S2: The communication unit 11 of the request management server 10 receives the work request information, the input reception unit 12 assigns the work request ID, and the "title", "request content", "delivery date", "subject tag", "worker", and "worker" The "requester" is registered in the request management data storage unit 22.

S3: The worker logs in to the request management server 10 by entering, for example, a user name and a password. The worker operates the terminal device 30 to confirm the request to himself / herself and communicates with the request management server 10. As a result, the communication unit 31 of the terminal device 30 of the worker sends a confirmation request for the work request to the request management server 10. The confirmation request of the work request means to request the presence or absence of the work request to the worker and the work request information when there is a work request.

S4: The communication unit 11 of the request management server 10 receives the confirmation request of the work request, and the work request transmission unit 13 searches the request management data storage unit 22 for the record associated with the worker. The record to be searched may be all records associated with the worker, or may be only records having no value in the "at the time of answer" item.

S5: The communication unit 11 of the request management server 10 transmits a list of work request information to the terminal device 30 of the worker.

In FIG. 7, the worker consciously starts communication with the request management server 10, but as described in FIG. 6, the request management server 10 sends an e-mail to the worker's terminal device 30 as a destination. By doing so, it is also possible to send a work request notification email to the effect that the work has been requested. Therefore, the worker can grasp that the work has been requested by two methods.

S6: The communication unit 31 of the terminal device 30 of the worker receives the list of work request information, and the display control unit 32 displays the answer input screen according to the operation of the worker. An example of the answer input screen is shown in FIG. The worker inputs the answer contents to the work request information for which the work is completed. The work may be simply to answer or press the completed button. The operation reception unit 33 accepts the input of the answer contents. The communication unit 31 of the terminal device 30 of the worker transmits the reply contents for each work request information to the request management server 10.

S7: The communication unit 11 of the request management server 10 receives the response content for each work request information, and the work completion reception unit 14 sets the terminal in the "response content" item of the record specified by the work request ID of the work request information. The answer content transmitted from the device 30 is set.

S8: Next, the requester operates the terminal device 30 to communicate the terminal device 30 with the request management server 10. As a result, the communication unit 31 of the requester's terminal device 30 transmits a response confirmation request to the request management server 10. The response confirmation request means requesting the work request information requested by the requester. The requester can selectively display the work request information in which the "answer content" is registered or the work request information in which the "answer content" is not registered.

S9: The communication unit 11 of the request management server 10 receives the response confirmation request, and the work completion notification unit 16 searches the request management data storage unit 22 for the response data associated with the requester.

S10: The work completion notification unit 16 of the request management server 10 requests a list of responses (records including "answer content" and "response date") associated with the requester via the communication unit 11. It is transmitted to the terminal device 30 of.

In FIG. 7, the requester consciously starts communication with the request management server 10, but as described in FIG. 6, the request management server 10 sends an e-mail to the requester's terminal device 30. By doing so, it is possible to send a work completion notification email to the effect that the work has been completed. Therefore, the client can know that the work has been completed in two ways.

<Screen example>
FIG. 8 shows an example of the work request information input screen 400 displayed by the requester's terminal device 30. The work request information input screen 400 is a screen for the requester to input work request information. The requester inputs information about the request on the work request information input screen 400. The information transmission control unit 17 sets the information input on the work request information input screen 400 to prompt the completion of the work.

The work request information input screen 400 has a title column 401, a request content column 402, a delivery date column 403, a subject tag column 404, a worker column 405, and a creation button 406.
-The title column 401 is a column in which the requester inputs the title of the work request information.
-The request content column 402 is a column in which the requester inputs the request content of the work request information.
-The delivery date column 403 is a column in which the requester inputs the delivery date of the request.
-The subject tag field 404 is a field in which the requester inputs the subject tag of the work request information.
The worker column 405 is a column in which the requester inputs the worker of the work request information.
-The creation button 406 is a button for the requester to input work request information.

FIG. 9 shows an example of the answer input screen 410 displayed by the operator's terminal device 30. The answer input screen 410 is displayed by connecting the terminal device 30 of the worker to the URL described in the work request notification mail or the work prompting e-mail (remind mail). Alternatively, the answer input screen 410 is displayed in a transition manner when the worker selects arbitrary work request information from the list of work request information. The answer input screen 410 has a request content column 411, an answer column 412, and an answer button 413.
-The request content column 411 is a column for displaying the request content of the work request information.
-Answer column 412 is a column in which the worker inputs the content of the answer.
-The answer button 413 is a button for the operator to input the transmission of the answer content.

<Sending an email prompting you to complete the work>
Next, with reference to FIG. 10, a procedure for sending an e-mail prompting the completion of the work will be described. FIG. 10 is an example of a sequence diagram showing a procedure in which the request management server 10 sends an e-mail prompting the completion of work to the terminal device 30 of the worker.

S11: The information transmission control unit 17 of the request management server 10 periodically executes the following processing. The commuter pass may be, for example, every 15 minutes. The information transmission control unit 17 may be executed at a fixed time or at a timing when the load of the request management server 10 is small, not at regular intervals.

S12: The information transmission control unit 17 acquires a record with a blank response date from the request management data storage unit 22. The information transmission control unit 17 may acquire all the records for which the response date is blank at once, or may acquire one record at a time.

S13: The information transmission control unit 17 identifies a record whose delivery date is within a predetermined period or a record whose delivery date has passed. The information transmission control unit 17 acquires the worker of this record. Alternatively, the information transmission control unit 17 specifies the work request transmission unit designated by the requester. In this case, the requester displays a screen as shown in FIG. 9 after the request, and requests the request management server 10 to send an e-mail prompting the completion of the work.

S14: The information transmission control unit 17 generates an e-mail prompting the completion of the work. That is, the information transmission control unit 17 acquires the worker's e-mail address acquired in step S13 from the user data storage unit 21, and creates an e-mail addressed to this e-mail address. Further, the information transmission control unit 17 acquires a title and a subject tag from the work request information and sets them in the subject of this e-mail. The information transmission control unit 17 uses the request content, delivery date, requester, and worker of the work request information to generate the body of the e-mail.

The information transmission control unit 17 sets a subject tag at the beginning of the subject when generating an email, for example. In the record of work request ID = 1 in Table 2, the subject tag set by Mr. A is "urgent". Therefore, the information transmission control unit 17 sets "Urgent" as the subject of the e-mail.

S15: The information transmission control unit 17 transmits the e-mail generated in step S14 to the mail server to the terminal device 30 of the worker.

FIG. 11A is an example of an e-mail displayed by the worker's terminal device 30 prompting the completion of the work. The e-mail has a subject 221, a worker 222, a text 223, a requester 224, a request content 225, a delivery date 226, and a URL 227.
-The subject 221 has a subject tag 221a and a title 221b included in the work request information. This makes it easier for the email to catch the eye of the worker. The subject tag 221a may be set in a color such as red, which has a high alertness. In addition, the character size may be larger than other characters, or may be displayed in bold or italics. The request management server 10 may add predetermined characters or the like in addition to the information input by the requester.
-Worker 222 is a "worker" of work request information.
-The text 223 is a sentence to urge the completion of the work.
-Requester 224 is a "requester" of work request information.
-Request content 225 is the "request content" of the work request information.
-Delivery date 226 is the "delivery date" of the work request information.
-URL 227 is a link to the answer input screen 410 of FIG. The id is a work request ID, and the request management server 10 displays an answer input screen 410 that accepts an answer to the work request ID = 1 on the terminal device 30.

Workers can check the email to know that they should work (answer) early.

As shown in FIG. 11B, the terminal device 30 of the worker can also display a message prompting the completion of the work on the Web page. In FIG. 11B, the Web page displays the title 228. The title 228 has a subject tag and a title of work request information. The worker operates the terminal device 30 to connect the terminal device 30 to the request management server 10 and displays the work request information to himself / herself. At this time, the screen information generation unit 15 of the request management server 10 sets the "subject tag" in the <title> tag of HTML. By doing so, even when the worker connects the worker's terminal device 30 to the request management server 10, the subject can be displayed on the Web page. Web pages are more likely to catch the eyes of workers.

<Main effect>
As described above, since the request management server 10 of the present embodiment sets the information input by the requester as the subject of the e-mail prompting the completion of the work, it is possible to call attention to read the e-mail.

In this embodiment, the request management system 1 for setting the value of the subject tag of the user data storage unit 21 to the subject of the e-mail prompting the completion of the work will be described.

In this embodiment, the components with the same reference numerals have the same functions, and therefore the description of the components once described may be omitted or only the differences may be described.

The request management server 10 of this embodiment has a subject tag in the user data storage unit 21.

表３はユーザデータ記憶部２１に記憶されているユーザデータを模式的に示す。表３の説明では主に表１との相違を説明する。表３のユーザデータは件名タグの項目を有している。件名タグは、依頼者が電子メールの件名に設定したい内容として予め設定しておくことができる。したがって、本実施例では依頼時に依頼者が件名タグを設定しなくてよい。

Table 3 schematically shows the user data stored in the user data storage unit 21. The description of Table 3 mainly describes the differences from Table 1. The user data in Table 3 has a subject tag item. The subject tag can be preset as the content that the requester wants to set in the subject of the e-mail. Therefore, in this embodiment, the requester does not have to set the subject tag at the time of request.

表４は依頼管理データ記憶部２２に記憶されている依頼管理データを模式的に示す。表４の説明では主に表２との相違を説明する。表４の依頼管理データは件名タグの項目を有していない。件名タグはユーザデータに設定されているためである。

Table 4 schematically shows the request management data stored in the request management data storage unit 22. The description of Table 4 mainly describes the differences from Table 2. The request management data in Table 4 does not have a subject tag item. This is because the subject tag is set in the user data.

<Registration of subject tag in user data>
FIG. 12 is an example of a sequence diagram showing a procedure in which a requester registers a subject tag in user data.

S21: The requester operates the terminal device 30 to communicate the terminal device 30 with the request management server 10. The requester logs in to the request management server 10. The display control unit 32 of the requester's terminal device 30 displays the user data input screen in response to the requester's operation. FIG. 13 shows an example of the user data input screen. When the requester inputs user data including a subject tag on the user data input screen, the operation reception unit 33 of the terminal device 30 accepts the input. Further, when the requester inputs a transmission operation, the communication unit 31 transmits the user data to the request management server 10. The requester inputs a "user name", "email address", and "subject tag". The "user ID" is automatically determined by login.

S22: The communication unit 11 of the request management server 10 receives the user data, and the input reception unit 12 registers the user data in the user data storage unit 21 in association with the user ID. If it has already been registered, it will be overwritten.

FIG. 13 is an example of the user data input screen 230 displayed by the requester's terminal device 30. The user data input screen 230 is displayed when the requester connects the requester's terminal device 30 to the request management server 10 and performs a predetermined operation. The information transmission control unit 17 sets the value (subject tag) of a predetermined item of the user data of the requester to prompt the completion of the work.

The user data input screen 230 has a user name field 231, an e-mail address field 232, a subject tag field 233, and a save button 234.
-The user name field 231 is a field in which the requester inputs his / her own user name. It is preferable that the user name of the requester is automatically displayed by logging in.
-The e-mail address field 232 is a field in which the requester inputs the requester's e-mail address. It is recommended that the requester's email address is automatically displayed by logging in.
-The subject tag field 233 is a field in which the requester inputs the subject tag.
The save button 234 is a button for the terminal device 30 to send the user data input by the requester to the request management server 10.

The procedure for the request management system 1 to manage requests may be the same as in FIG. 7. However, the requester does not need to enter the subject tag when requesting work. Therefore, in this embodiment, the work request information input screen is different from that in FIG.

FIG. 14 shows an example of the work request information input screen 240 displayed by the requester's terminal device 30. In the description of FIG. 14, the difference from FIG. 8 will be described. The work request information input screen 240 of FIG. 14 has a title column 241, a request content column 242, a delivery date column 243, a worker column 244, and a creation button 245. Therefore, the work request information input screen 240 of FIG. 14 does not have a subject tag field. This is because the subject tag is registered in the user data.

<Sending an email prompting you to complete the work>
Next, with reference to FIG. 15, the procedure for sending an e-mail prompting the completion of the work will be described in this embodiment. FIG. 15 is an example of a sequence diagram showing a procedure in which the request management server 10 sends an e-mail prompting the completion of work to the terminal device 30 of the worker. In the description of FIG. 14, the difference from FIG. 10 will be mainly described. In FIG. 14, steps S34 and S35 are different from those in FIG.

S34: The information transmission control unit 17 acquires the worker's e-mail address from the user data storage unit 21. Further, the information transmission control unit 17 acquires the subject tag of the requester from the user data storage unit 21.

S35: The information transmission control unit 17 generates an e-mail prompting the completion of the work. The information transmission control unit 17 sets the title of the work request information and the subject tag of the requester in the subject of the e-mail. Further, the information transmission control unit 17 generates the body of the e-mail by using the request content, the delivery date, the requester, and the worker of the work request information.

In Table 3, the subject tag set by Mr. A is "Urgent". Therefore, the information transmission control unit 17 sets "Urgent" as the subject of the e-mail. The e-mail prompting the completion of the work is the same as in FIG. 11 (a).

In this embodiment, the subject tag set in the user data of the requester is set in the e-mail, but the information transmission control unit 17 sets the subject tag set in the user data of the worker in the e-mail. You may. Workers can easily notice the subject tag that they have set.

<Main effect>
As described above, in the request management server 10 of the present embodiment, in addition to the effect of the first embodiment, the requester can set the subject tag in advance, so that it is not necessary to set the subject tag at the time of request.

In this embodiment, the request management system 1 in which the requester can set the item of the request management data in the subject tag in advance will be described.

In this embodiment, the components with the same reference numerals have the same functions, and therefore the description of the components once described may be omitted or only the differences may be described.

The request management server 10 of this embodiment has a subject tag in the user data storage unit 21.

表５はユーザデータ記憶部２１に記憶されているユーザデータを模式的に示す。表５の説明では主に表３との相違を説明する。表５のユーザデータは件名タグの項目を有している。件名タグは、依頼者が電子メールの件名に設定したい内容として予め設定しておくことができる。そして、本実施例では件名タグとして、例えば、作業依頼情報に含まれる作業者名、納期、又は、納期までの期間を依頼者が選択できる。

Table 5 schematically shows the user data stored in the user data storage unit 21. The description of Table 5 mainly describes the differences from Table 3. The user data in Table 5 has a subject tag item. The subject tag can be preset as the content that the requester wants to set in the subject of the e-mail. Then, in this embodiment, the requester can select, for example, the worker name, the delivery date, or the period until the delivery date included in the work request information as the subject tag.

表６は依頼管理データ記憶部２２に記憶されている依頼管理データを模式的に示す。表６の説明では主に表４との相違を説明する。本実施例の依頼管理データにおいても件名タグの項目を有していない。件名タグはユーザデータにより指示されるためである。

Table 6 schematically shows the request management data stored in the request management data storage unit 22. The description of Table 6 mainly describes the differences from Table 4. The request management data of this embodiment does not have a subject tag item either. This is because the subject tag is indicated by user data.

<Registration of subject tag in user data>
The procedure for the requester to register the subject tag in the user data may be the same as in FIG. However, since the requester can select the subject tag, the user data input screen is different from that in FIG.

FIG. 16 is an example of the user data input screen 250 displayed by the requester's terminal device 30. The user data input screen 250 has a user name field 251, an e-mail address field 252, a subject tag field 253, and a save button 254. In the explanation of FIG. 16, the difference from FIG. 13 will be mainly described. The subject tag field 253 of FIG. 16 displays the request management data items in a pull-down menu format so that they can be selected. The subject tag field 253 can display, for example, a worker, a delivery date, or a period until the delivery date. The period until the delivery date is not the item of request management data itself, but it can be calculated from the delivery date.

The requester can arbitrarily select a subject tag that is unlikely to be overlooked by the worker from the worker, the delivery date, or the period until the delivery date. In this way, the requester sets the item of information about the request in the predetermined item of the user data. The information transmission control unit 17 acquires the value of the information item related to the request, which is set in the predetermined item of the user data of the requester, from the information related to the request, and sets it to prompt the completion of the work.

The procedure for the request management system 1 to manage requests may be the same as in FIG. 7. In addition, the requester does not need to enter the subject tag when requesting work. Therefore, the work request information input screen 240 may be the same as in FIG.

<Sending an email prompting you to complete the work>
The procedure for the request management server 10 to send an e-mail prompting the completion of the work to the terminal device 30 of the worker is the same as in FIG. However, the processing of steps S34 and S35 is different from that of the second embodiment.

S34: The information transmission control unit 17 acquires the worker's e-mail address from the user data storage unit 21. Further, the information transmission control unit 17 acquires the subject tag of the requester from the user data storage unit 21.

S35: The information transmission control unit 17 generates an e-mail prompting the completion of the work. The information transmission control unit 17 determines which item of the request management data the subject tag of the requester is. The information transmission control unit 17 acquires the value of the item of the request management data specified by the subject tag of the user data. The information transmission control unit 17 sets the title of the work request information and the value of the acquired request management data item in the subject of the e-mail. Further, the information transmission control unit 17 generates the body of the e-mail by using the request content, the delivery date, the requester, and the worker of the work request information.

In Table 5, the subject tag set by Mr. A is "worker". Therefore, the information transmission control unit 17 sets the worker of the request management data as the subject of the e-mail. An e-mail prompting the completion of the work is shown in FIG.

FIG. 17 is an example of an e-mail 260 displayed by the terminal device 30 of the worker (Mr. B) to prompt the completion of the work. In the explanation of FIG. 17, the difference from FIG. 11A will be mainly described. In the e-mail of FIG. 17, a worker is set in the subject 261. The worker with the subject 261 is obtained from the worker item in the work request information. Workers have their name in the subject line, so they can be careful not to overlook the email. Workers can check the email to know that they should work (answer) early.

Further, in Table 5, the subject tag set by Mr. B is "delivery date". Therefore, the information transmission control unit 17 sets the delivery date of the request management data in the subject of the e-mail. An e-mail prompting the completion of the work is shown in FIG.

FIG. 18 is an example of an e-mail 270 displayed by the terminal device 30 of the worker (Mr. C) to prompt the completion of the work. In the e-mail 270 of FIG. 18, the subject 271 is set to "delivery date December 20". Workers can check the email carefully as the delivery date is near. Workers can check the email to know that they should work (answer) early.

Further, in Table 5, the subject tag set by Mr. C is "the period until the delivery date". Therefore, the information transmission control unit 17 sets the difference between the delivery date of the request management data and the current date in the subject of the e-mail. Assuming that the delivery date is December 20, 2019 and the current date is December 18, 2019, the delivery date is two days.

When the subject tag is the period until the delivery date, the information transmission control unit 17 may convert the period until the delivery date into a predetermined subject. Table 7 is an example of conversion data in which the information transmission control unit 17 converts the period until the delivery date into a predetermined subject.

表７は、算出された納期までの期間と件名タグが対応付けて登録された変換データを示す。情報送信制御部１７は算出した納期までの期間を表７にて対応付けられている件名タグに変換する。

Table 7 shows the conversion data registered in which the calculated period until the delivery date and the subject tag are associated with each other. The information transmission control unit 17 converts the calculated period until the delivery date into the subject tag associated with the table 7.

FIG. 19 is an example of an e-mail 280 displayed by the terminal device 30 of the worker (Mr. A) to prompt the completion of the work. In the e-mail 280 of FIG. 19, "2 days left" is set in the subject 281. The worker can confirm the period until the delivery date (for example, the number of days) and understand that the work (answer) should be performed at an early stage.

In this embodiment, the value of the work request information item corresponding to the subject tag (work request information item) set in the user data of the requester is set in the e-mail, but the information transmission control unit 17 is used. The value of the work request information item corresponding to the subject tag set in the user data of the worker may be set in the e-mail. Workers can easily notice the subject tag that they have set.

<Main effect>
As described above, in addition to the effect of the first embodiment, the request management server 10 of the present embodiment states that the requester is less likely to overlook the e-mail from the worker, the delivery date, or the period until the delivery date. You can select any subject tag that you think. The requester can set the subject according to the work request information in the e-mail.

In this embodiment, the request management system 1 that applies the method of setting the subject of the first embodiment to the work request notification mail will be described.

In this embodiment, the components with the same reference numerals have the same functions, and therefore the description of the components once described may be omitted or only the differences may be described.

<Operation of request management system 1>
FIG. 20 is an example of a sequence diagram showing a procedure in which the request management system 1 manages requests. In the description of FIG. 20, the description will be made based on Tables 1 and 2 of the first embodiment.

S41: The requester operates the terminal device 30 to communicate the terminal device 30 with the request management server 10. The requester logs in to the request management server 10. The display control unit 32 of the requester's terminal device 30 displays a work request information input screen (see FIG. 8) in response to the requester's operation. When the requester inputs the work request information on the work request information input screen, the operation reception unit 33 of the terminal device 30 accepts the input. Further, when the requester inputs a transmission operation, the communication unit 31 transmits the work request information to the request management server 10. The requester inputs "title", "request content", "delivery date", "subject tag", and "worker". The "requester" is automatically determined by logging in.

S42: The communication unit 11 of the request management server 10 receives the work request information, the input reception unit 12 assigns the work request ID, and the "title", "request content", "delivery date", "subject tag", "worker", and "worker" The "requester" is registered in the request management data storage unit 22.

S43: The work request transmission unit 13 sets the subject tag and title included in the work request information in the subject of the work request notification email. The information transmission control unit 17 generates the body of the work request notification mail using the request content, delivery date, requester, and worker of the work request information.

S44: The work request transmission unit 13 transmits the work request notification mail to the mail server via the communication unit 11 with the worker's mail address as the destination.

FIG. 21 is an example of the work request notification mail 290 displayed by the worker's terminal device 30. The work request notification mail 290 has a subject 291 and a worker name 292, a text 293, a requester 294, a title 295, a delivery date 296, and a URL 297.
-The subject 291 has a subject tag 291a and a title 291b. The subject tag 291a makes it easier for workers to catch the email.
-The worker name 292 is the "worker" of the work request information.
-The text 293 is a sentence to the effect that the work request has been received.
-Requester 294 is a "requester" of work request information.
-Title 295 is a "title" of work request information.
-Delivery date 296 is the "delivery date" of the work request information.
-URL 297 is a link to the answer input screen 410 of FIG.

The worker can check the e-mail to know that the work (answer) should be done.

<Main effect>
As described above, in the request management server 10 of the present embodiment, in addition to the effects of the first to third embodiments, the request management server 10 prompts the completion of the work by inputting the information input by the requester also in the work request notification email. It is set in the subject line of the email so that you can be alerted to read the email.

In this embodiment, the request management system 1 that applies the contents of the second and third embodiments to the work request notification mail will be described.

In this embodiment, the components with the same reference numerals have the same functions, and therefore the description of the components once described may be omitted or only the differences may be described.

<Operation of request management system>
FIG. 22 is an example of a sequence diagram showing a procedure in which the request management system 1 manages requests. In the description of FIG. 22, the description will be made based on Tables 5 and 6 of the third embodiment.

S51: Same as steps S41 and S42 in FIG. 20, but the requester does not need to input the "subject tag" in the work request information. This is because the subject tag has already been registered in the user data as shown in Table 5.

S52: The communication unit 11 of the request management server 10 receives the work request information, the input reception unit 12 assigns the work request ID, and sets the "title", "request content", "delivery date", "worker", and "requester". Register in the request management data storage unit 22.

S53: The work request transmission unit 13 acquires the user data of the requester from the user data storage unit 21.

S54: The work request transmission unit 13 acquires an item of request management data specified by the subject tag of the user data of the requester, and acquires the value of this item from the request management data. The work request transmission unit 13 sets the subject tag and title included in the work request information in the subject of the work request notification email. The information transmission control unit 17 uses the request content, delivery date, requester, and worker of the work request information to generate the body of the work request notification mail.

S55: The work request transmission unit 13 sends a work request notification email to the mail server via the communication unit 11 with the worker's email address as the destination.

FIG. 23 is an example of an e-mail displayed by the worker's terminal device 30 to notify the work request. FIG. 23 (a) shows e-mail 420 when the subject tag is a worker, FIG. 23 (b) shows e-mail 430 when the subject tag is due date, and FIG. 23 (c) shows e-mail 430 when the subject tag is due date. E-mail 440 for the period of is shown respectively.

The items included in the e-mail 420 of FIG. 23 (a) are the same as those of FIG. 17, and the worker is set in the subject 421. The items included in the e-mail 430 of FIG. 23 (b) are the same as those of FIG. 18, and the delivery date is set in the subject 431. The items included in the e-mail 440 of FIG. 23 (c) are the same as those of FIG. 19, and the period until the delivery date is set in the subject 441.

Therefore, the request notification mail is easily noticed by the worker, and the worker can easily understand that the work (answer) should be performed even when the request notification mail is received.

<Main effect>
As described above, in the request management server 10 of the present embodiment, in addition to the effects of the first to fourth embodiments, the request management server 10 completes the work based on the information input by the requester in the work request notification email. You can set the subject of the e-mail to remind you to read the e-mail.

<Other application examples>
Although the best mode for carrying out the present invention has been described above with reference to examples, the present invention is not limited to these examples, and various modifications are made without departing from the gist of the present invention. And substitutions can be made.

For example, in the present embodiment, an example in which the terminal device 30 mainly displays a screen on a Web browser has been described, but the terminal device 30 may execute a dedicated application on the request management server. In this case, the request management server may send a push notification instead of an e-mail to prompt the completion of the work. For example, the request management server pushes the URL to the terminal device 30 of the worker. When the worker presses the URL, the terminal device 30 connects to the Web page as shown in FIG. 11B.

Further, the user data in Table 5 may be generated by machine learning. For example, user data can be created by the learning device learning the correspondence between the user's attributes and the request management data items set by the user.

Further, the configuration example shown in FIG. 5 is divided according to the main functions in order to facilitate understanding of the processing by the terminal device 30 and the request management server 10. The present invention is not limited by the method of dividing the processing unit or the name. The processing of the terminal device 30 and the request management server 10 can be further divided into more processing units according to the processing content. Further, one processing unit can be divided so as to include more processing.

Also, the group of devices described in the examples is only one of a plurality of computing environments for implementing the embodiments disclosed herein. In one embodiment, the request management server 10 includes a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other over any type of communication link, including networks, shared memory, and the like, and perform the processes disclosed herein.

Further, the request management server 10 can be configured to share the processing steps disclosed in the present embodiment, for example, FIGS. 7, 10 and the like in various combinations. For example, the process executed by a predetermined unit may be executed by a plurality of information processing devices included in the request management server 10. Further, the request management server 10 may be integrated into one server device or may be divided into a plurality of devices.

Each function of the embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" as used herein is a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array) and conventional circuit modules.

1 Request management system 10 Request management server 30 Terminal equipment

Japanese Unexamined Patent Publication No. 2014-127171

Claims (11)

An information processing device that communicates with a first terminal device operated by a requester who requests work and a second terminal device operated by a worker who performs the work.
A work request transmission unit that communicates with the second terminal device and requests the worker to perform the work requested by communication with the first terminal device.
A work completion reception unit that accepts the completion of the work by communicating with the second terminal device,
The work completion receiving unit has an information transmission control unit that transmits to the destination the second terminal device to urge the completion of the work for a request for which the completion of the work has not been accepted.
The information transmission control unit includes an information processing device including a first character string related to a request and a second character string corresponding to the information set by the requester in order to prompt the completion of the work. .. The information set by the requester is the information input on the screen where the requester inputs the information related to the request, and the information transmission control unit uses the information as the second character string to prompt the completion of the work. The information processing apparatus according to claim 1, wherein the information processing apparatus is set to the effect. The information set by the requester is the user data of the requester.
The first aspect of the present invention is characterized in that the information transmission control unit sets the value of a predetermined item of the user data of the requester as the second character string to prompt the completion of the work. Information processing equipment. The requester sets an item of information about the request in a predetermined item of the user data, and sets the item of information about the request.
The information transmission control unit acquires the value of the information item related to the request, which is set in the predetermined item of the user data of the requester, from the information related to the request, and obtains the value as the second character string. The information processing apparatus according to claim 3, wherein the information processing apparatus is set to prompt the completion of work. The information processing apparatus according to claim 4, wherein the item of information regarding the request is the name of the worker. The information processing apparatus according to claim 4, wherein the item of information regarding the request is a delivery date. The requester sets a period until the delivery date in a predetermined item of the user data, and sets the period until the delivery date.
The information transmission control unit acquires the delivery date from the information related to the request based on the delivery date set in the predetermined item of the user data of the requester, and the period from the current date to the delivery date. The information processing apparatus according to claim 4, wherein is set as the second character string to prompt the completion of the work. The work request transmission unit responds to the first character string related to the request and the information set by the requester so as to request the worker for the work requested by communication with the first terminal device. Set the second character string,
The information processing device according to any one of claims 1 to 7, wherein the second terminal device is transmitted to a destination. The information transmission control unit generates an e-mail to prompt the completion of the work.
In any one of claims 1 to 7, the subject of the e-mail is set to a first character string relating to the request and a second character string corresponding to the information set by the requester. The information processing device described. A communication unit that communicates with the first terminal device operated by the requester requesting the work and the second terminal device operated by the worker performing the work.
A work request transmission unit that communicates with the second terminal device and requests the worker to perform the work requested by communication with the first terminal device.
A work completion reception unit that accepts the completion of the work by communicating with the second terminal device,
The work completion reception unit has an information transmission control unit that transmits to the destination the second terminal device to urge the completion of the work for a request for which the completion of the work has not been accepted.
The information transmission control unit includes an information processing device including a first character string related to the request and a second character string corresponding to the information set by the requester in order to prompt the completion of the work.
The second terminal device,
A second communication unit that receives a message prompting the completion of the work,
A display control unit that displays to the effect that the work received by the second communication unit is prompt to be completed.
A request management system that has a program to function as. An information processing device that communicates with the first terminal device operated by the requester requesting the work and the second terminal device operated by the worker performing the work.
A work request transmission unit that communicates with the second terminal device and requests the worker to perform the work requested by communication with the first terminal device.
A work completion reception unit that accepts the completion of the work by communicating with the second terminal device,
For a request for which the work completion reception unit has not received the completion of the work, the information transmission control unit for transmitting the second terminal device to the destination to prompt the completion of the work is made to function.
The information transmission control unit is a program characterized in that a first character string relating to a request and a second character string corresponding to information set by the requester are included in order to prompt the completion of the work.

Images