JP6642101B2 - Work management device and program - Google Patents

Description

  The present invention relates to a work management device and a program.

  2. Description of the Related Art Conventionally, a ToDo management device that manages tasks (work contents) to be performed by a user is known. As a ToDo management device, there is a ToDo management device that prioritizes execution of a plurality of tasks and proposes the tasks to a user in descending order of priority.

  For example, in a ToDo list in which tasks are shared by a plurality of users, it is monitored whether each user has processed each task, and the total number of users having the same task and the There is known a ToDo list creation device that calculates the ratio of the number of processed tasks to the number of processed persons, and calculates the priority for the processing of the task based on this value (see Patent Document 1). The tasks to be performed in the priority order of the created ToDo list are suggested to the user.

JP 2010-92204 A

  However, in the above-mentioned conventional ToDo list creation device, the priorities of tasks according to the execution statuses of a plurality of users can be managed. There is a possibility that the task cannot be executed depending on the situation of the object to be executed, such as the situation of the object, the partner, the external factor, and the like, which are already outside business hours.

  An object of the present invention is to derive a priority to go to a facility or a priority to contact a facility for each work content based on work contents (tasks) and open schedule information or business schedule information of a facility where the work contents are performed. Is to do so.

In order to solve the above problem, the work management device of the present invention, when a plurality of work contents to be performed by the user on the day in association with the identification information of the facility where the work contents are performed is registered, Information acquisition means for acquiring the opening schedule information or business schedule information on the day at the facility where the work content is implemented for each of the plurality of work contents based on the identification information, and the information acquisition means Priority deriving means for deriving a priority to go to the facility or a priority to contact the facility based on the opening schedule information or the business schedule information for each of the work contents,
It is characterized by having.

  According to the present invention, a priority to go to a facility or a priority to contact a facility is derived for each work content based on the work content (task) and the opening schedule information or the business schedule information of the facility where the work content is performed. be able to.

FIG. 1 is a block diagram illustrating a task management system according to an embodiment of the present invention. FIG. 3 is a block diagram illustrating a functional configuration of a server. FIG. 2 is a block diagram illustrating a functional configuration of the terminal device. (A) is a figure showing composition of a target DB. (B) is a diagram showing a configuration of a task list DB. (A) is a flowchart showing a task input process. (B) is a flowchart showing a task registration process. It is a flowchart which shows the deadline calculation process of a task registration process. (A) is a flowchart showing a display update request process. (B) is a flowchart showing a display update process. It is a figure showing an example of transition of a display screen of a terminal unit.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The present invention is not limited to the illustrated example.

  The device configuration of the present embodiment will be described with reference to FIGS. First, a task management system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram illustrating a task management system 1 according to the present embodiment.

  The task management system 1 includes a server 10 as a work management device and a terminal device 20. The server 10 is a server on the cloud, and manages information on tasks as work items performed by the user of the terminal device 20. The server 10 is connected to a communication network N. The communication network N is the Internet, but may be another network such as a LAN (Local Area Network).

  The terminal device 20 is a portable terminal device owned by a user such as a store owner of a private store or a manager of a private company. Here, description will be made assuming that the terminal device 20 is a tablet PC (Personal Computer), but the terminal device 20 is not limited to this, and may be a smartphone, a mobile phone, a PDA (Personal Digital Assistant), a notebook PC, or the like. Alternatively, it may be another portable terminal device. Further, the terminal device 20 receives an operation input by the user, transmits the input to the server 10, and displays information received from the server 10. The terminal device 20 is connected to the communication network N via a base station on the communication network N, an access point (both not shown), and the like.

  Note that the task management system 1 has a configuration in which the server 10 manages information relating to a task of a user of one terminal device 20, but is not limited to this. The task management system 1 may include a plurality of terminal devices 20, and the server 10 may integrally manage information on tasks of each user of the plurality of terminal devices 20.

  Next, a functional configuration inside the server 10 will be described with reference to FIG. FIG. 2 is a block diagram illustrating a functional configuration of the server 10.

  As shown in FIG. 2, the server 10 includes a CPU (Central Processing Unit) 11 as an information acquisition unit, a priority derivation unit, and a second position information acquisition unit, an operation unit 12, and a RAM (Random Access Memory) 13. , A display unit 14, a storage unit 15, a transmission unit, a communication unit 16 as a first position information acquisition unit, and a clock unit 17. Each part of the server 10 is connected via a bus 18.

The CPU 11 controls each unit of the server 10. The CPU 11 reads out a specified program from the system program and the application program stored in the storage unit 15 and expands the specified program on the RAM 13, and executes various processes in cooperation with the program.

  The operation unit 12 has a key input unit such as a keyboard and a pointing device such as a mouse, receives a key input and a position input, and outputs operation information to the CPU 11.

  The RAM 13 is a volatile memory, and forms a work area for temporarily storing various data and programs. The display unit 14 includes an LCD (Liquid Crystal Display), an EL (Electro Luminescent) display, and the like, and performs various displays according to display information instructed by the CPU 11.

  The storage unit 15 includes a hard disk drive (HDD), a solid state drive (SSD), and the like, and is a storage unit that can write and read data and programs. In particular, the storage unit 15 stores a task registration program 151, a display update program 152, a target DB (DataBase) 30, and a task list DB 40, which will be described later.

  The communication unit 16 includes a network card or the like, is communicatively connected to the communication network N, and performs communication with devices on the communication network N. The CPU 11 can communicate with the terminal device 20 on the communication network N via the communication unit 16.

  The clock unit 17 is a real-time clock, measures the current time, and outputs the current time information to the CPU 11.

  Next, a functional configuration of the terminal device 20 will be described with reference to FIG. FIG. 3 is a block diagram illustrating a functional configuration of the terminal device 20.

  The terminal device 20 includes a CPU 21, an operation unit 22, a RAM 23, a display unit 24, a storage unit 25, a wireless communication unit 26, and a positioning unit 27. Each part of the terminal device 20 is connected via a bus 28.

  The CPU 21, the RAM 23, and the display unit 24 are the same as the CPU 11, the RAM 13, and the display unit 14 of the server 10, and thus, a duplicate description will be omitted, and different portions will be mainly described.

  The CPU 21 controls each unit of the terminal device 20. The operation unit 22 has a touch panel provided on a display screen of the display unit 24, receives a touch input from a user, and outputs operation information to the CPU 21.

  The storage unit 25 includes a flash memory, an EEPROM (Electrically Erasable Programmable ROM) and the like, and is a storage unit in which data and programs can be written and read. In particular, the storage unit 25 stores a task input program 251 and a display update request program 252.

  The wireless communication unit 26 includes an antenna, a modulation / demodulation circuit, a signal processing circuit, and the like, and transmits and receives information to and from a base station, an access point, and the like on the communication network N by radio waves. For this reason, the CPU 21 can communicate with the server 10 via the base station, the access point, and the like on the communication network N by the wireless communication unit 26.

  The positioning unit 27 includes an antenna, a demodulation unit, a signal processing circuit, and the like, receives GPS signals transmitted from a plurality of GPS (Global Positioning System) satellites, and measures the position of the terminal device 20 using the GPS signals. And outputs the measured latitude / longitude information to the CPU 21 as current position information of the terminal device 20 (user).

  Next, the target DB 30 and the task list DB 40 stored in the storage unit 15 of the server 10 will be described with reference to FIG. FIG. 4A is a diagram illustrating a configuration of the target DB 30. FIG. 4B is a diagram showing a configuration of the task list DB 40.

  As shown in FIG. 4A, the target DB 30 has items of a target ID 31, a target name 32, an address 33, a store holiday 34, a valid start time 35, a valid end time 36, and a main transportation means 37.

  The target ID 31 is identification information for identifying a target (destination) as an execution target for performing the task. Specifically, the target is a facility such as a store where a task such as a telephone call or a visit is performed, a person or a group where a task such as a meeting or a meeting is performed. The target name 32 is the name of the target of the target ID 31. The address 33 is the address of the target of the target ID 31.

  The store holiday 34 is a regular holiday (day of the week) of the target (facility or the like) of the target ID 31. The effective start time 35 is a start time at which task execution is effective, such as the business start time of the target with the target ID 31 and the visitable start time. The effective end time 36 is an end time at which the task execution is effective, such as the business end time of the target with the target ID 31 and the visitable end time. The main transportation means 37 is identification information of the main transportation means used when the user moves to the address 33 in performing the task of the target ID 31. In the main transportation means 37, for example, it is assumed that 0 is a walk, 1 is a car, 2 is a train, and 3 is a bus.

  As shown in FIG. 4B, the task list DB 40 stores items of a task ID 41, a Do keyword 42, a target ID 43, an input deadline 44, a calculation deadline 45, a transportation means 46 for calculation, a calculated travel time 47, and a task detail 48. Have.

  The task ID 41 is identification information of each task registered in the ToDo list, which is a list of tasks to be performed by the user having the terminal device 20. The task list DB 40 stores a record of each task of the task ID 41 and a task input order of the task ID 41 (descending order).

The Do keyword 42 is a keyword related to the action of the user included in the details of the task content of the task ID 41 (task details 48). The Do keyword 42 includes a Go keyword such as “go” related to an action involving movement and a keyword such as “do” related to an action involving no movement.
The target ID 43, like the target ID 31 shown in FIG. 4A, is identification information for identifying a target (a destination) as an execution target for performing a task.

  The input deadline 44 is the execution deadline input by the user corresponding to the task of the task ID 41, and is information on the date of the execution deadline, or information on the date of the execution deadline and the designated time. The calculation deadline 45 is a display deadline of the task corresponding to the task of the task ID 41 and calculated by the server 10 in consideration of the travel time of the transportation means and the notification delay time from the input deadline 44 by the user. The notification grace time is a predetermined time indicating how far before the effective end time of the target the user is notified of the task execution proposal, and is, for example, 30 minutes. It is assumed that the notification delay time is set in the server 10 in advance according to a user's setting input in the terminal device 20. The notification delay time is a fixed time for each task, but is not limited to this, and may be set differently for each task.

The calculation means of transportation 46 is identification information of the means of transportation used to calculate the calculation deadline 45 in the execution of the task with the task ID 41. It is assumed that the numbers representing the respective transportation means of the calculation transportation means 46 are the same as those of the main transportation means 37. The calculated travel time 47 is, in the execution of the task with the task ID 41, the travel by the transport means 46 for calculation from the current position information (at the time of the last update of the display of the ToDo list) of the terminal device 20 to the address of the destination target. Time. The task details 48 are detailed information of the contents of the task of the task ID 41.

  Next, the operation of the task management system 1 will be described with reference to FIGS. FIG. 5A is a flowchart showing the task input processing. FIG. 5B is a flowchart showing the task registration process. FIG. 6 is a flowchart illustrating the deadline calculation process of the task registration process. FIG. 7A is a flowchart illustrating the display update request process. FIG. 7B is a flowchart illustrating the display update process. FIG. 8 is a diagram illustrating an example of transition of the display screen of the terminal device 20.

  With reference to FIG. 5A, a task input process executed by the terminal device 20 will be described. The task input process is a process of inputting task information, registering the task information in the server 10, and displaying task list information as a Todo list in which tasks to be performed based on the registered task information are arranged in order. In response to input of target information (target name, address, store holiday, valid start time, valid end time, main transportation means) from the user via the operation unit 22 of the terminal device 20 in advance, and transmission of the target information to the server 10 Then, it is assumed that the target information is received by the server 10, a target ID is assigned to the target information, and the target information is stored in a record of the target DB 30 in the storage unit 15, and the target DB 30 is registered.

  In the terminal device 20, triggered by input of a task input process execution instruction from a user via the operation unit 22 as a trigger, the CPU 21 cooperates with the task input program 251 read from the storage unit 25 and appropriately developed in the RAM 23. Task input processing.

  First, the CPU 21 receives task information input by the user via the operation unit 22 (step S11). The input task information includes information indicating the detailed contents of the task registered by the user as a Todo management target and information indicating the execution deadline of the task. The task information may further include information indicating a means of transportation necessary for performing the task, and information of a target name indicating a target (target) for performing the task. In addition, as the task execution deadline, not only the deadline date but also time designation can be input. In addition, the target name, the verb (call, go, etc.), the candidate of the item of the date and the designated time are displayed on the display unit 23, and the user selects and inputs the candidate of each item via the operation unit 22, respectively. It may be configured to input the task details and the execution deadline. Then, the CPU 21 causes the positioning unit 27 to measure the current position of the terminal device 20, and acquires the current position information from the positioning unit 27 (Step S12).

  Then, the CPU 21 transmits the task information input in step S11 and the current position information obtained in step S12 to the server 10 via the wireless communication unit 26 (step S13). Then, the CPU 21 receives the task list information from the server 10 via the wireless communication unit 26 (Step S14). The task list information includes task information (task details, execution deadlines, calculation deadlines, transportation means, travel time) of tasks sorted in the order in which they should be displayed at that time as a ToDo list, and task state display information of each task. And The task status display information of each task is a normal display in which the task has not passed the calculation deadline, and the first state in which the task with the Go keyword has passed the calculation deadline but has not passed the start time of the travel time until the execution deadline. Either the highlighting, the second highlighting in which the task with the Go keyword has passed the start time of the movement time until the execution deadline, or the task without the Go keyword has passed the calculation deadline. The second highlighting is a stronger highlighting than the first highlighting. It should be noted that a configuration may be adopted in which the first highlighting is performed when a task without a Go keyword has passed the calculation deadline.

  Then, the CPU 21 displays the ToDo list screen on the display unit 24 according to the task list information received in step S14 (step S15), and ends the task input processing. In step S15, for example, the task details in the order in which the task list information is to be executed are displayed in a ToDo list screen arranged in order from top to bottom. When the task status display information is the first highlight, the first highlight is displayed. When the task status display information is the second highlight, the second highlight is displayed. indicate. For example, by selecting and inputting the task details on the ToDo list screen, the execution deadline of the task, the calculation deadline, the means of transportation, the travel time, the effective start time of the target, the effective end time, and the like are displayed.

  Next, a task registration process executed by the server 10 will be described with reference to FIG. In the task registration process, the server 10 registers the input task information in the task list DB 40 in response to the task input process, and sorts the tasks by the calculation deadline in consideration of the movement time and the notification delay time of each task. This is a process of returning task list information to the terminal device 20.

  In the server 10, the CPU 11 reads out the storage unit 15 from the storage unit 15, triggered by the reception of the task information and the current position information transmitted from the terminal device 20 by the communication unit 16, corresponding to step S <b> 13 of FIG. The task registration processing is executed in cooperation with the task registration program 151 appropriately developed in the RAM 13.

  First, the CPU 11 receives the task information and the current position information transmitted from the terminal device 20 through the communication unit 16 (Step S21). Then, the CPU 11 stores the task information received in step S21 in the task list DB 40 of the storage unit 15 (step S22). In step S22, the CPU 11 assigns a new task ID to the task of the task information, extracts the Do keyword and the target name from the task details of the task information, and uses the target DB 30 to correspond to the extracted target name 32. The target ID 31 is obtained. Then, the CPU 11 calculates the task ID 41, the Go keyword 42, the target ID 43, the input deadline 44, the traffic for calculation, the new task ID, the extracted Do keyword, the acquired target ID, the execution deadline of the task information, the means of transportation, and the task details. The means 46 stores the new details in the task details 48. When there is no transportation in the task information, the CPU 11 acquires the main transportation 37 corresponding to the acquired target ID 31 by using the target DB 30 and stores it in the transportation for calculation 46.

  Then, the CPU 11 performs a time limit calculation process (step S23). Here, the deadline calculation processing in step S23 will be described with reference to FIG. First, the CPU 11 selects a record of one unselected task from the task list DB 40 (step S31). Then, the CPU 11 determines whether or not the Do keyword 42 of the record of the task selected in step S31 includes a Go keyword such as “go” related to an action involving movement (step S32). That is, the Go keyword is a keyword that means moving, such as “go”, “go”, “move”, and the like. In step S32, the Go keyword includes the content of the Do keyword 42 of the record of the selected task. It is determined whether or not these keywords are included.

If there is a Go keyword (step S32; YES), the CPU 11 uses the current position information received in step S21 and the data of the record of the task selected in step S31 to determine the movement time of the selected task. The calculated time is set to the calculated movement time 47 of the record of the task (step S33). In step S33, the CPU 11 acquires the latitude / longitude information from the address 33 of the target DB 30 corresponding to the target ID 43 of the task selected in step S31 by Web search, DB search in which the address and the latitude / longitude information are associated, or the like. By calculating the distance between the acquired latitude and longitude information and the current position information received in step S21, and dividing the calculated distance by the speed information corresponding to the calculation means of transportation 46 of the selected task, Calculate the travel time.

  Then, the CPU 11 determines whether or not the input time limit 44 of the task selected in step S31 has a designated time (step S34). If there is a designated time (step S34; YES), the CPU 11 subtracts the calculated travel time 47 and the preset notification delay time from the input time limit 44 including the designated time of the task selected in step S31, and sets the calculated time limit. It is calculated and set as the calculation deadline 45 of the record of the task (step S35).

  If there is no designated time (step S34; NO), the CPU 11 calculates the calculated moving time 47 and the preset notification delay time from the valid end time 36 of the target DB 30 corresponding to the target ID 43 of the task selected in step S31. Then, the calculation deadline is calculated, and the calculated deadline is set to the calculation deadline 45 of the record of the task (step S36).

  When there is no Go keyword (step S32; NO), the CPU 11 subtracts a preset notification grace time from the effective end time 36 of the target DB 30 corresponding to the target ID 43 of the task selected in step S31, and sets the calculation deadline. It is calculated and set to the calculation deadline 45 of the record of the task (step S37).

  Then, the CPU 11 determines whether or not there is a record of the task not selected in step S31 (step S38). When there is a record of an unselected task (step S38; YES), the process proceeds to step S31. When there is no unselected task record (step S38; NO), the term calculation process ends.

  Returning to FIG. 5B, the CPU 11 acquires the current time information from the clock unit 17 and sorts the records of the task list DB 40 changed in step S23 in the order of the calculation deadline 45 to generate task information. The task status display information of each task is generated from the input deadline 44, the calculation deadline 45, and the current time information, and the task status display information is added to the rearranged task information to generate task list information (step S24).

  In step S24, the CPU 11 sorts the records of the task list DB 40 changed in step S23 in the order of the deadline of the calculation deadline 45, the task details 48 in the deadline order, and the execution deadline (the input deadline 44 when there is a designated time). If there is no designated time, the effective end time 36), the calculation deadline 45, the calculating means 46, the calculated travel time 47, the target effective start time 35, the effective end time 36, and the like are generated. Further, the CPU 11 sets a normal display for each task of the sorted task information when the obtained current date and time information has not passed the calculation deadline 45, has the Go keyword, and calculates the obtained current date and time information. If the start time of the travel time until the implementation deadline has not elapsed since the time limit 45 has elapsed, the first highlighting is set, the Go keyword is present, and the acquired current date and time information indicates the start of the travel time until the implementation time limit. When the time has passed, or when there is no Go keyword and the obtained current date and time information has passed the calculation deadline, the second emphasis is set and task state display information of each task is generated.

  Then, the CPU 11 transmits the task list information generated in step S24 to the terminal device 20 via the communication unit 16, corresponding to step S15 in FIG. 5A (step S25), and ends the task registration process. I do.

In the task input process and the task registration process, the specified time of the execution time limit (input time limit) input to the terminal device 20 is outside the valid time of the target (before the valid start time 35 or after the valid end time 36) or in the store. In the case of the holiday 34, the server 10 causes the terminal device 20 to display that the input time limit is outside the target valid time or the store holiday, and prompts the user so that the input time limit is within the target valid time or other than the store holiday. A configuration for prompting re-input may be adopted.

  Further, in the task input process and the task registration process, when the target information of the task to be registered is not in the target DB 30, the server 10 performs a keyword search on the Web for the target name in the task details or in the target, and searches for the address, shop holiday, and so on. Alternatively, a configuration may be adopted in which search results such as effective hours (business hours) are displayed on the terminal device 20 to prompt the user to input target information for registration, and the input target information is registered in the target DB 30.

  Next, a display update request process executed by the terminal device 20 will be described with reference to FIG. The display update request process is a process of requesting the server 10 to update the displayed ToDo list, and displaying the task list information as the updated ToDo list. The display update request process is repeatedly executed at a predetermined cycle.

  In the terminal device 20, triggered by the execution timing of a predetermined period of the display update request process being triggered, the CPU 21 cooperates with the display update request program 252 read out from the storage unit 25 and appropriately developed in the RAM 23 to update the display update. Perform request processing. In addition, the CPU 21 may execute the display update request process, triggered by input of an instruction to execute the display update request process from the user via the operation unit 22.

  Step S41 is the same as step S12 in FIG. Then, the CPU 21 transmits the current position information acquired in step S41 to the server 10 via the wireless communication unit 26 (step S42). Steps S43 and S44 are the same as steps S14 and S15 in FIG.

  Next, a display update process executed by the server 10 will be described with reference to FIG. The display update process is a process in which the server 10 updates the task list information and returns it to the requesting terminal device 20 in response to the display update request process.

  In the server 10, corresponding to step S42 in FIG. 7A, triggered by the start of receiving the current position information from the terminal device 20 via the communication unit 16, the CPU 11 reads out from the storage unit 15 and The display update processing is executed in cooperation with the display update program 152 developed in the RAM 13.

  First, the CPU 11 completes receiving the current position information via the communication unit 16 (step S51). Then, the CPU 11 performs a time limit calculation process (step S52). The term calculation process of step S52 is the same as the term calculation process of FIG. However, in step S52, the current position information acquired in step S51 is used. Steps S53 and S54 are the same as steps S24 and S25 in FIG.

  When the task is performed by the user, the completed task is input via the operation unit 22 of the terminal device 20, and the task ID is transmitted to the server 10. The server 10 deletes the record of the task list DB 40 of the executed task ID 41 received from the terminal device 20. Further, when the current time information has passed the task execution deadline, the server 10 may delete the record in the task list DB 40 of the task ID 41 of the task whose execution deadline has passed.

  Next, a transition example of the display screen of the terminal device 20 will be described with reference to FIG. Here, for the sake of simplicity, the description is made on the assumption that the calculation time limit does not change. However, in practice, the calculation time limit also changes according to the movement of the user.

  First, it is assumed that task information is not registered until 8:00 on May 22. Then, as shown in FIG. 8, at 8:30 on the same day, a task input process and a task registration process are executed, and a task T1 having a Go keyword of “Go to the hall D” and a task T1 of “Call the customer A” are displayed. Task information of the task T2 having no Go keyword is registered. The calculation deadline, execution deadline (designated time), and travel time of the task T1 are 13:30, 15:00, and 1 hour. The calculation deadline and the execution deadline (valid end time) of the task T2 are 17:30 and 18:00. For this reason, on the ToDo list screen 301 displayed on the terminal device 20, the tasks T1 and T2 are displayed in descending order of the calculation deadlines in the order of tasks T1 and T2.

  At 9:00 on the same day, a task input process and a task registration process are executed, task information of a new task T3 having a Go keyword of “go to the C store” is registered, and the ToDo list screen 302 is displayed on the terminal device 20. Is displayed. The calculation deadline, execution deadline (valid end time), and travel time of task T3 are assumed to be 19:00, 20:00, and 30 minutes. For this reason, on the ToDo list screen 302, tasks T1, T2, and T3 are displayed in order according to the calculation deadline.

  At 10:30 on the same day, a task input process and a task registration process are executed, task information of a new task T4 having no Go keyword of “order to B store” is registered, and the ToDo list screen 303 is displayed on the terminal device 20. Is displayed. The calculation deadline and the execution deadline (valid end time) of the task T4 are 18:30 and 19:00. Therefore, on the ToDo list screen 303, the tasks T1, T2, T4, and T3 are displayed in order according to the calculation deadline.

  Then, at 13:30 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 304 is displayed on the terminal device 20. On the ToDo list screen 304, since the current time has passed the calculation deadline of the task T1, the task T1 is displayed in the first highlighted display.

  Then, at 14:00 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 305 is displayed on the terminal device 20. On the ToDo list screen 305, the current time has passed the calculation time limit of the task T1 and the start time 14:00 of the travel time of 1 hour until the execution time limit 15:00 has passed, so the task T1 is displayed in the second highlighted display. . Immediately after this, it is assumed that the task T1 is performed by the user.

  Then, at 15:30 on the same day, the display update request processing and the display update processing are executed, and the ToDo list screen 306 is displayed on the terminal device 20. In the ToDo list screen 306, the task T1 has been deleted by execution.

  Then, at 17:30 on the same day, the display update request processing and the display update processing are executed, and the ToDo list screen 307 is displayed on the terminal device 20. On the ToDo list screen 307, since the current time has passed the calculation deadline of the task T2, the task T2 is displayed in the second highlighted display. Immediately after this, it is assumed that the task T2 is performed by the user.

  At 18:00 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 308 is displayed on the terminal device 20. In the ToDo list screen 308, the task T2 has been deleted by execution.

  At 18:30 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 309 is displayed on the terminal device 20. On the ToDo list screen 309, the task T4 is displayed in the second highlight because the current time has passed the calculation deadline of the task T4. Immediately after this, it is assumed that the task T4 has been performed by the user.

  At 19:00 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 310 is displayed on the terminal device 20. On the ToDo list screen 310, the task T4 is deleted by execution, and the current time has passed the calculation deadline of the task T3. Therefore, the task T3 is displayed in the first highlighted state.

  At 19:30 on the same day, a display update request process and a display update process are executed, and the ToDo list screen 311 is displayed on the terminal device 20. On the ToDo list screen 311, the current time has passed the calculation time limit of the task T3 and has passed the start time of 30 minutes of the travel time until the execution time limit of 20:00, so the task T3 is displayed in the second highlighted display. Immediately after this, it is assumed that the task T3 has been performed by the user.

  At 20:30 on the same day, a display update request process and a display update process are executed, and a ToDo list screen is displayed on the terminal device 20, but no task information is included.

  As described above, according to the present embodiment, when a plurality of tasks to be performed by the user on the day are registered in association with the target ID of the facility where the task is performed, the server 10 The effective end time 36 as the opening schedule information or the business schedule of the day at the facility where the task is performed is acquired for each of the plurality of tasks, and the priority to go to the facility based on the acquired effective end time 36 is obtained. A calculation deadline as a priority or a priority for contacting a facility is derived for each task.

  For this reason, a calculation deadline as a priority to go to a facility or a priority to contact a facility can be derived for each task based on the open schedule information or the business schedule of the task and the facility where the task is performed.

  Further, the server 10 transmits the task list information based on the derived calculation deadline to the terminal device 20 as a portable terminal configured to be portable by the user. Therefore, by displaying the task list information based on the calculation deadline on the terminal device 20, the user can easily visually recognize the task list information based on the calculation deadline.

  Further, the server 10 acquires the current position information of the terminal device 20, and derives a calculation deadline as a priority based on the current position information. Therefore, an appropriate calculation deadline based on the current position information of the terminal device 20 can be derived.

  Further, the server 10 acquires the address 33 as the location information of the facility based on the target ID, and derives the calculation deadline based on the acquired address 33. Therefore, it is possible to derive an appropriate calculation deadline based on the facility address 33.

  In addition, the server 10 derives the calculation deadline as the time at which the task should be completed or the time at which the task should arrive at the facility. For this reason, it is possible to prompt the user to end the task or arrive at the facility by the calculation deadline (task list information based on the calculation deadline).

  In the above description, an example in which the HDD and the SSD of the storage unit 15 are used as the computer-readable medium of the program according to the present invention has been disclosed, but the present invention is not limited to this example. As another computer-readable medium, a portable recording medium such as a flash memory or a CD-ROM can be applied. Further, as a medium for providing the data of the program according to the present invention via a communication line, a carrier wave (carrier wave) is also applied to the present invention.

The description in the above embodiment is an example of the work management apparatus and the program according to the present invention, and the present invention is not limited to this.

  For example, in the above embodiment, the server 10 is configured to execute the task registration process and the display update process. However, the present invention is not limited to this. For example, the server 10 is configured to store the target DB 30 and the task list DB 40, and the terminal device 20 reads out the data of the target DB 30 and the task list DB 40 of the server 10, and performs the same processing as the task registration processing and the display update processing. It is good also as a structure which performs.

  Further, in the above embodiment, when the execution time limit has elapsed without executing the task, the task information of the task is deleted from the task list DB 40 and deleted from the Todo list screen. However, the present invention is not limited to this. Not something. For example, the server 10 may be configured to leave the task information of the task on the Todo list screen without deleting the task information from the task list DB 40 when the execution time limit has elapsed without the task being executed. For example, the configuration may be such that the server 10 deletes the task information of the deleted task from the task list DB 40 in response to the task deletion operation by the user via the terminal device 20.

  In the above-described embodiment, the server 10 sorts the task information of all the tasks in the task list DB 40 by the calculation deadline to create the task list information. However, the present invention is not limited to this. For example, among tasks registered by the server 10, tasks that are determined to be performed are given the highest priority, and task information of tasks other than the tasks determined to be performed in the task list DB 40 is calculated based on the calculation deadline. The task list information may be created by rearranging the tasks.

  Further, in the above-described embodiment, the valid start time and the valid end time of the target are used as the status regarding the execution target of the task, but the present invention is not limited to this. For example, another situation such as the weather around the implementation target or the distance to the implementation target may be used as the situation regarding the implementation target.

  Further, in the above-described embodiment, a case occurs in which the calculation deadline is close in time for a plurality of tasks. In this case, the configuration is such that the user selects and executes the task, but the present invention is not limited to this. . For example, when the calculation deadline is near for a plurality of tasks, the configuration may be such that the notification delay time of each task whose calculation deadline is close in time is different according to an operation input from the user, other information, or the like.

  Further, it goes without saying that the detailed configuration and detailed operation of each component of the task management system 1 in the above embodiment can be appropriately changed without departing from the spirit of the present invention.

Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and equivalents thereof.
In the following, the inventions described in the claims first attached to the application form of this application are appended. The item numbers of the appended claims are as set forth in the claims originally attached to the application for this application.
(Appendix)
<Claim 1>
When a plurality of work contents to be performed by the user on the day are registered in association with the identification information of the facility where the work contents are performed, the plurality of work contents are determined for each of the plurality of work contents based on the identification information. Information acquisition means for acquiring the opening schedule information or business schedule information of the day at the facility where the work is performed,
Priority deriving means for deriving a priority to go to the facility or a priority to contact the facility based on the opening schedule information or the business schedule information acquired by the information acquiring means for each work content,
A work management device comprising:
<Claim 2>
The work management device according to claim 1, further comprising a transmission unit configured to transmit a priority derived by the priority derivation unit to a portable terminal configured to be portable by a user.
<Claim 3>
A first position information acquisition unit that acquires current position information of the portable terminal;
The work management device according to claim 2, wherein the priority deriving unit derives the priority based on current position information of the mobile terminal acquired by the first position information acquiring unit. .
<Claim 4>
A second position information acquisition unit that acquires position information of the facility based on the identification information,
4. The work according to claim 1, wherein the priority deriving unit derives the priority based on the location information of the facility acquired by the second location information acquiring unit. Management device.
<Claim 5>
5. The work management device according to claim 1, wherein the priority deriving unit derives the priority as a time at which the work should be completed or a time at which the work should arrive at the facility. 6.
<Claim 6>
Computer
When a plurality of work contents to be performed by the user on the day are registered in association with the identification information of the facility where the work contents are performed, the plurality of work contents are determined for each of the plurality of work contents based on the identification information. Information acquisition means for acquiring the opening schedule information or business schedule information of the day at the facility where the work content is performed,
Priority deriving means for deriving a priority to go to the facility or a priority to contact the facility based on the opening schedule information or the business schedule information acquired by the information acquiring means for each work content,
Program to function as

1 task management system 10 server 11 CPU
12 Operation unit 13 RAM
14 display unit 15 storage unit 16 communication unit 17 clock unit 18 bus 20 terminal device 21 CPU
22 operation unit 23 RAM
24 display unit 25 storage unit 26 wireless communication unit 27 positioning unit 28 bus N communication network

Claims (6)

When a plurality of work contents to be performed by the user on the day are registered in association with the identification information of the facility where the work contents are performed, the plurality of work contents are determined for each of the plurality of work contents based on the identification information. Information acquisition means for acquiring the opening schedule information or business schedule information of the day at the facility where the work is performed,
Priority deriving means for deriving a priority to go to the facility or a priority to contact the facility based on the opening schedule information or the business schedule information acquired by the information acquiring means for each work content,
A work management device comprising:   The work management device according to claim 1, further comprising a transmission unit configured to transmit a priority derived by the priority derivation unit to a portable terminal configured to be portable by a user. A first position information acquisition unit that acquires current position information of the portable terminal;
The work management device according to claim 2, wherein the priority deriving unit derives the priority based on current position information of the mobile terminal acquired by the first position information acquiring unit. . A second position information acquisition unit that acquires position information of the facility based on the identification information,
4. The work according to claim 1, wherein the priority deriving unit derives the priority based on the location information of the facility acquired by the second location information acquiring unit. Management device.   5. The work management device according to claim 1, wherein the priority deriving unit derives the priority as a time at which the work should be completed or a time at which the work should arrive at the facility. 6. Computer
When a plurality of work contents to be performed by the user on the day are registered in association with the identification information of the facility where the work contents are performed, the plurality of work contents are determined for each of the plurality of work contents based on the identification information. Information acquisition means for acquiring the opening schedule information or business schedule information of the day at the facility where the work content is performed,
Priority deriving means for deriving a priority to go to the facility or a priority to contact the facility based on the opening schedule information or the business schedule information acquired by the information acquiring means for each work content,
Program to function as