JP6822002B2 - Schedule management device and program - Google Patents

Description

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

Conventionally, a ToDo management device that manages a task (work content) to be performed by a user is known. As a ToDo management device, there is a device that proposes to a user the execution of a task in consideration of the travel time, depending on the positional relationship between the current position and the place where the task is executed.

For example, the current position of the device that functions as the ToDo management device of the user and the position of the destination where the task is performed are determined, and the time it may take for the user to move from the current position to the position of the destination. To judge. Then, if the difference between the current time and the time at which the task should be performed at the destination is the same as or close to the travel time, there is known generation and processing of a task item for notifying the user (see Patent Document 1). As a result, the user can be reminded of the scheduled movement start time for task execution.

Japanese Patent Publication No. 2014-518409

However, in the conventional generation and processing of task items, if the user does not start the movement even after the scheduled movement start time, the task items only remain in an incomplete state. Therefore, there is a problem that the ToDo management is abandoned for the user who does not start the movement even after the scheduled movement start time.

An object of the present invention is to inform the user of an alternative ToDo when it cannot be confirmed as ToDo even though the scheduled movement start time for starting the movement toward the visited destination has passed.

In order to solve the above problem, the schedule management device according to the present invention is a schedule management device that can register the scheduled visit time to the visited destination in association with the location information of the visited destination, and can be registered as the current position information. Based on the movement start scheduled time derivation means for deriving the first deadline time for deriving the movement toward the visit destination, and the first deadline time derived by the movement start scheduled time derivation means for the visit destination. The display control means includes a display control means for displaying the visit schedule information to the effect that the movement should be started in a predetermined display area as the first task to be executed by the user, and the display control means sets the first deadline time or the was when the movement can not be confirmed that towards the elapsed despite the visited the first time limit for a predetermined period of time, should contact to the visited until late the second period time than the first time limit contact schedule information to the effect that, to be displayed on the display area as an alternative task of the first task, wherein the.
Further, in the program according to the present invention, the computer of the schedule management device capable of registering the scheduled visit time to the visited destination in association with the location information of the visited destination is directed to the visited destination based on the current location information. A visit to the effect that the movement should be started toward the visited destination by the first deadline time derived by the movement start scheduled time derivation means for deriving the first deadline time for starting the movement and the first deadline time derived by the movement start scheduled time derivation means. The schedule information is made to function as a display control means for displaying the schedule information in a predetermined display area as a first task to be executed by the user, and the display control means sets the first deadline time or the first deadline time only for a predetermined time. If the movement to the visited destination cannot be confirmed even though the time has passed, the contact schedule information to the effect that the visited destination should be contacted by the second deadline time later than the first deadline time is provided. It is characterized in that it is displayed in the display area as an alternative task of one task.

According to the present invention, it is possible to inform the user of an alternative ToDo when it cannot be confirmed as ToDo even though the scheduled movement start time for starting the movement toward the visited destination has passed.

It is a block diagram which shows the schedule management system of embodiment of this invention. It is a block diagram which shows the physical configuration of a server. It is a block diagram which shows the physical configuration of a terminal device. It is a block diagram which shows the functional structure of the schedule management system. It is a figure which shows the structure of the target DB. It is a figure which shows the structure of a task DB. It is a figure which shows the 1st display example of a task list display screen. It is a figure which shows the 2nd display example of a task list display screen. It is a figure which shows the 3rd display example of a task list display screen. It is a figure which shows the 4th display example of a task list display screen. It is a figure which shows the display example of a new task registration screen. It is a flowchart which shows the task registration process. It is a flowchart which shows the deadline notification processing.

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

The apparatus configuration of the present embodiment will be described with reference to FIGS. 1 to 3. First, the schedule management system 1 of the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing the schedule management system 1 of the present embodiment.

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

The terminal device 20 is a mobile terminal device owned by a user such as a shopkeeper of a private store or a manager of a private company. Here, it is assumed that the terminal device 20 is a tablet PC (Personal Computer), but the present invention is not limited to this, and the terminal device 20 is a smartphone, a mobile phone, a PDA (Personal Digital Assistant), a notebook PC, or the like. It may be another terminal device. Further, the terminal device 20 can receive the operation input from the user and transmit the information to the server 10, and can also receive the information from the server 10 and display it to the user. Further, the terminal device 20 is connected to the communication network N via a base station, an access point (all not shown), or the like on the communication network N.

The schedule management system 1 is configured to manage a schedule for one user, but the schedule management system 1 is not limited to this. For example, by using the identification information given to each user and configuring each user to log in, schedule management for a plurality of users can be realized even from one terminal device 20. Further, the schedule management system 1 is not limited to the configuration including one terminal device 20, and may be provided with a plurality of terminal devices 20.

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

As shown in FIG. 2, the server 10 includes a CPU (Central Processing Unit) 11, an operation unit 12, a RAM (Random Access Memory) 13, a display unit 14, a storage unit 15, and a communication unit 16. Be prepared. Each part of the server 10 is connected via the bus 17.

The CPU 11 controls each part of the server 10. The CPU 11 reads a designated program among the system programs and application programs stored in the storage unit 15 and expands them in 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 key input and position input, and outputs the 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 is composed of an LCD (Liquid Crystal Display), an EL (ElectroLuminescent) display, and the like, and performs various displays according to display information instructed by the CPU 11.

The storage unit 15 is composed of an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like, and is a storage unit capable of writing and reading data and programs. In particular, the storage unit 15 stores the target DB (DataBase) 40 and the task DB (DataBase) 50, which will be described later.

The communication unit 16 is composed of a network card or the like, is connected to the communication network N by communication, and communicates with a device 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.

Next, the physical configuration of the terminal device 20 will be described with reference to FIG. FIG. 3 is a block diagram showing a physical 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, a position information detection unit 27, and a timekeeping unit 28. Each part of the terminal device 20 is connected via a bus 29.

Regarding the CPU 21, RAM 23, and display unit 24, the same parts as the CPU 11, RAM 13, and display unit 14 of the server 10 will be omitted, and different parts will be mainly described.

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

The storage unit 25 is composed of a flash memory, an EEPROM (Electrically Erasable Programmable ROM), or the like, and is a storage unit capable of writing and reading data and programs.

The wireless communication unit 26 is composed of an antenna, a transmission / reception circuit, a signal processing circuit, and the like, and transmits / receives information by radio waves to and from a base station on the communication network N. Therefore, the CPU 21 can communicate with the server 10 by the wireless communication unit 26 via the base station on the communication network N.

The position information detection unit 27 is composed of an antenna, a reception circuit, a signal processing circuit, etc., receives radio waves transmitted from a GPS (Global Positioning System) satellite, acquires a GPS signal, and obtains a GPS signal from the GPS signal at present in the terminal device 20. The current position information is detected by deriving the position (latitude, longitude).

The timekeeping unit 28 is a real-time clock, clocks the current date and time, and outputs current time information indicating the current date and time to the CPU 21.

Next, the functional configuration of the schedule management system 1 will be described with reference to FIG. FIG. 4 is a block diagram showing a functional configuration of the schedule management system 1.

The schedule management system 1 includes an information reception unit 31, a registration information derivation unit 32, a task management unit 33, an alternative task generation unit 34, a current time acquisition unit 35, a task list generation unit 36, and a display unit 37. , Consists of.

The information receiving unit 31 receives input information such as an execution place and an implementation deadline as the contents of the task to be registered from the terminal device 20 via the communication unit 16, which will be described in detail later. The registration information derivation unit 32 derives a deadline for starting an action corresponding to the content of the task. When deriving, information on the execution location of the task stored in the target DB 40, which will be described later, is also used.

The task management unit 33 manages registration, change, and the like of task contents. Specifically, the input information and the derived information are registered as new tasks in the task DB 50 of the storage unit 15 described later. If there is a change in the content of the registered task, the content of the task is changed. For example, when the execution deadline of the registered task has passed, the task whose execution deadline has passed is added to the task contents and changed. Further, for example, when a task that has not been executed by the execution deadline is a replacement target for the alternative task, the alternative task is overwritten with this task, that is, the replacement is performed. The alternative task generation unit 34 generates the contents of the alternative task when the task management unit 33 determines that the alternative task is necessary. The current time acquisition unit 35 acquires the current time required for the task management unit 33 to manage the implementation deadline and the like.

The task list generation unit 36 generates a task list based on the contents of the registered task DB 50. The task list is a list display of registered tasks, and the registered tasks are displayed in an organized state so that the user's schedule can be managed. The task list generated here is, for example, in a format in which tasks are arranged from the top in order of closeness to the deadline, and further, the tasks whose deadlines have passed are highlighted so that the user is alerted. The display unit 37 displays the task list generated by the task list generation unit 36.

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

As shown in FIG. 5A, the target DB 40 has items of a target ID 41, a target name 42, an address 43, an effective start time 44, and an effective end time 45.

The target ID 41 is identification information assigned to identify each target, which is the place where the user performs the task. Specifically, the target is a facility such as a store to which tasks such as telephone calls and visits are implemented, and a person or group to which tasks such as visits and meetings are implemented. The target name 42 is the name of the target where the task is performed, and the address 43 is the specific address of the target.

The valid start time 44 represents the start time of the period during which tasks such as the target business start time and the visitable start time can be performed, and the valid end time 45 is the target business end time and the visitable end time. It represents the end time of the period during which tasks such as etc. can be performed.

The item contents included in the target DB 40 as described above are stored corresponding to each target. For example, the target ID 41 of "customer A" is "001", the address 43 is "Hachioji-shi, Tokyo ...", the valid start time 44 is "9:00", and the valid end time 45 is "18:00". It has become.

As shown in FIG. 5B, the task DB 50 includes task ID 501, movement presence / absence 502, target ID 503, deadline input value 504, deadline derivation value 505, derivation transportation means 506, travel time derivation value 507, task details 508, It has items with a deadline attribute of 509 and a deadline of 510.

The task ID 501 is identification information assigned to identify the tasks to be performed by the user who owns the terminal device 20. A new task ID 501 is given to each task in the order in which the tasks are registered, and information is stored in the task DB 50.

The presence / absence of movement 502 indicates whether or not a movement is necessary to perform the task, and "Yes" is stored when the movement is necessary, and "None" is stored when the movement is not necessary. ing. The target ID 503 corresponds to the target ID 41 shown in FIG. 5A, and is identification information for identifying the target where the task is executed.

The deadline input value 504 is an implementation deadline input by the user, and is information on the date of the implementation deadline, or information on the date of the implementation deadline and the designated time. The deadline derived value 505 is the deadline obtained by subtracting the travel time and the notification grace time from the deadline input value 504. When the deadline is derived by the server 10 and the current time reaches the deadline derived value 505, the corresponding task is highlighted in the task list. Will be done. The notification grace time is a predetermined time indicating how long before the time when the task should be executed before the user is notified, and is, for example, 30 minutes. The notification grace time is set and input by the user from the terminal device 20. Here, the setting is uniform for all tasks, but the setting is not limited to this, and a different time may be set for each task.

The derivation transportation means 506 is identification information of the transportation means used for deriving the deadline derivation value 505. As for the numbers representing each means of transportation for out-licensing, for example, it is assumed that 0 is a walk, 1 is a car, 2 is a train, and 3 is a bus. The travel time derivation value 507 is the travel time in the derivation transportation means 506 from the current position information of the current terminal device 20 to the address of the target of the travel destination in the execution of the task of the task ID 501. The task detail 508 is detailed information on the content of the task. The deadline attribute 509 is information indicating what kind of operation the deadline is specifically the deadline for completion. The deadline 510 is identification information for identifying whether or not the task has passed the deadline derived value 505, and 0 is stored before the deadline and 1 is stored after the deadline.

The item contents included in the task DB 50 are stored corresponding to each task as in the target DB 40. Further, the information registered in the task DB 50 is displayed as a task list, and can be viewed and edited from both the server 10 and the terminal device 20. Further, when a new task is registered in the task DB 50, the registered new task is added to the task list, and when the execution of the task is completed, the information about the corresponding task is deleted from the task DB 50, and the task is executed. Also remove it from the list.

Next, a display example of the task list display screen will be described with reference to FIG. First, the task list display screen 60A shown in FIG. 6A represents a display screen in which no task for which the deadline derivation value 505 has been registered has passed. The task list display screen 60A includes a current time display 61A for displaying the current time, a task addition button 62A for displaying a new task registration screen described later, and a task for displaying the contents of each registered task. Box 63A, task detail display 64A for displaying task details 508, deadline display 65A for displaying deadline attribute 509 and deadline derivation value 505, task edit button 66A for editing registered tasks, and task It has a check box 67A for inputting that the implementation has been completed.

From the current time display 61A, the current time is "May 22, 12:00". Here, it is assumed that the content of the registered task is the content of the task DB 50 of FIG. 5 (b), and the content of the registered target is the content of the target DB 40 of FIG. 5 (a). Further, it is assumed that the task box 63A is displayed side by side from the top in the order in which the deadline derivation value 505 is closest. When there is a task that has been executed in the task list, the user can delete the task from the task list by checking the check box 67A corresponding to the executed task, and the task DB50 The task can also be deleted from.

The task list display screen 60B shown in FIG. 6B shows a display screen when the deadline derivation value 505 of the registered task is approaching. From the current time display 61B, the current time is "May 22, 13:00", which is 30 minutes before the deadline displayed on the deadline display 65B, so it is necessary to carry out the task immediately. Therefore, the urgent display 68B is displayed in the task box 63B of the task whose deadline derivation value 505 is approaching. Here, it is decided to display the urgent display 68B 30 minutes before the deadline derivation value 505, but it is assumed that the timing for displaying the urgent display 68B can be arbitrarily changed.

The task list display screen 60C shown in FIG. 6C represents a display screen when one of the registered tasks has passed the deadline derivation value 505. From the current time display 61C, the current time is "May 22, 13:30", and since the deadline derived value 505 displayed on the deadline display 65C has passed, the task box 63C of the task for which the deadline derived value 505 has passed is displayed. , Filled and highlighted as shown. Therefore, the user can easily notice the task for which the deadline derivation value 505 has passed, and can grasp that the task needs to be executed immediately.

The task list display screen 60D shown in FIG. 6D shows a display screen when the task is not executed even though the deadline derivation value 505 has passed and the task is replaced with an alternative task. The criteria for determining whether or not to replace the task whose deadline derived value 505 has passed with the alternative task will be described using the flowchart described later. On the display screen of FIG. 6 (d), the current time is "May 22, 14:00", and the deadline derived value 505 displayed on the deadline display 65C in FIG. 6 (c) is the notification grace time 30. More than a minute has passed. At this time, if the task that has not been executed is to be replaced with the alternative task, the deadline derivation value 505, task details 508, deadline attribute 509, and deadline 510 of this task are changed. Therefore, "Go to D Kaikan" was displayed on the task detail display 64C in FIG. 6 (c), but in FIG. 6 (d), "D Kaikan" which is the content of the alternative task is displayed on the task detail display 64D. "Call me" is displayed. In addition, the deadline display 65D has also changed to "contact deadline May 22, 15:00", and the alternative display 69D is displayed in the task box 63D of the alternative task so that the task can be seen as an alternative task. Is displayed.

Next, a display example of the new task registration screen will be described with reference to FIG. 7. The new task registration screen is displayed by clicking the add task buttons 62A, 62B, and 62C on the task list display screen of FIG. The new task registration screen 70 shown in FIG. 7 has a task detail input area 71 in which task details 508 are input, a deadline date input area 72A in which the date of the deadline input value 504 is input, and a deadline date input area 72A as the contents of the task to be registered. The deadline time input area 72B in which the time of the input value 504 is input, the execution destination input area 73 in which the target ID 503 is input, the movement presence / absence input area 74 in which the movement presence / absence 502 is input, and the deadline attribute 509 are input. It has a deadline attribute input area 75, a registration button 76 for registering the contents of the input task, and a close button 77 for closing the new task registration screen 70 without registering the contents of the input task. If you want to register a new task, enter the content of the task you want to register in each area and click the registration button 76. When the registration button 76 is clicked, the CPU 11 derives information such as the deadline derivation value 505 from the contents of the input task, and the information is registered in the task DB 50 as a new task. Then, the registered task is added to the task list and displayed on the task list display screen as shown in FIG.

Next, each process of the schedule management system 1 will be described with reference to FIGS. 8 and 9. FIG. 8 is a flowchart showing the task registration process, and FIG. 9 is a flowchart showing the deadline notification process.

The task registration process will be described with reference to FIG. The task registration process is a process of registering the content of the task to be registered in the server 10 by inputting an operation by the operation unit 22 of the terminal device 20, but is not limited to this, and is directly registered from the operation unit 12 of the server 10. You may do. Further, it is assumed that the target information (target name 42, address 43, valid start time 44, valid end time 45) is registered in the target DB 40 in advance by input from the user.

In the terminal device 20, the task registration process is executed by clicking the task addition buttons 62A, 62B, and 62C on the task list display screen of FIG. 6 via the operation unit 22.

First, the CPU 21 receives the content of the task input from the operation unit 22 by the user (step S11). That is, the CPU 21 functions as an information receiving unit 31. The contents of the tasks to be input are movement presence / absence 502, target ID 503, deadline input value 504, task details 508, and deadline attribute 509, but are not limited to these. For example, the target ID 503 may be determined by the server 10 searching for the corresponding target ID 503 from the target DB 40 by accepting the target name 42 from the user. Further, for example, the out-licensing transportation means 506 is configured to be appropriately selected by the server 10, but may be determined by the input of the user. Then, when the content of the input task is received, the current time and the current position information of the terminal device 22 are acquired from the position information detection unit 27 and the timekeeping unit 28 (step S12).

Then, the CPU 21 transmits the input task content, the current time, and the current position information to the server 10 via the wireless communication unit 26. In the server 10, the CPU 11 determines whether or not the input task requires movement based on the movement presence / absence 502 included in the content of the input task.

When the movement presence / absence 502 is “none” (step S13; NO), the CPU 11 derives the deadline derivation value 505 by subtracting the notification grace time from the deadline input value 504. For example, when the deadline input value 504 is "13:00", the notification grace time is 30 minutes, so the deadline derivation value 505 is "12:30". After that, the content of the task is registered in the task DB 50, and the registered task is added to the task list and displayed (step S19). On the other hand, when the presence / absence of movement 502 is "Yes" (step S13; YES), the CPU 11 determines the out-licensing transportation means 506 (step S15). Then, the travel time derivation value 507 is derived based on the determined derivation transportation means 506, and the travel time derivation value 507 derived from the deadline input value 504 and the notification grace time are subtracted to derive the deadline derivation value 505. (Step S16). For example, when the deadline input value 504 is "13:00" and the travel time derived value 507 is "1 hour", the notification grace time is 30 minutes, so the deadline derived value 505 is "11:30". Become. That is, the CPU 11 functions as the registration information derivation unit 32.

Then, if the current time is before the deadline derivation value 505 obtained (step S17; YES), the CPU 11 registers the content of the task in the task DB 50, adds the registered task to the task list, and displays it (step S17; YES). Step S19). That is, the CPU 11 functions as a task management unit 33, a task list generation unit 36, and a display unit 37. However, if the deadline derivation value 505 from which the current time has been obtained has already passed (step S17; NO), the CPU 11 sends a message to the terminal device 20 that the task cannot be registered, and the CPU 21 sends the message to the terminal device 20. The message is displayed on the display unit 24 (step S18).

In step S18, a message that cannot be registered is displayed to the user, but a message indicating that the deadline derivation value 505 has already passed is displayed on the display unit 24, and whether or not to register the task. It may be configured to determine whether or not by the input of the user.

Next, the deadline notification process will be described with reference to FIG. The deadline notification process is a process in which the server 10 notifies the user of a task to be executed by changing the task list display screen with the passage of time. In this flowchart, it is assumed that the task is not executed by the user at all. Further, this deadline notification process is performed for each of a plurality of registered tasks, and it is assumed that a plurality of processes are performed in parallel.
For convenience, the processing for one task will be described here.

First, the CPU 11 of the server 10 acquires the current time from the timing unit 28 of the terminal device 20 via the communication unit 16. That is, the CPU 11 functions as the current time acquisition unit 35. When the obtained current time is 30 minutes before the deadline derived value 505 of the registered task (step S21; YES), the CPU 11 selects 30 of the deadline derived value 505 from the displayed task list. The urgent display 68B is added to the task box of the task that is minutes ago, and the changed task list is displayed on the display unit 24 (step S22). As a result, the user can be notified of the task whose deadline derived value 505 is close.

After that, when the deadline derivation value 505 of the task for which the current time is registered has passed (step S23; YES), the CPU 11 sets the deadline 510 of the task to 1, and the deadline derivation value 505 has passed. To the terminal device 20. Then, the task box of the task whose deadline derivation value 505 has passed is highlighted from the displayed task list by filling it, and the changed task list is displayed on the display unit 24 (step S24). As a result, the user can be notified of the task whose deadline derived value 505 has passed.

After that, when 30 minutes, which is the above-mentioned notification grace time, has elapsed from the deadline derivation value 505 of the task in which the current time is registered (step S25; YES), it is determined whether or not the task has moved 502 (step S26). ).

If the move presence / absence 502 of the task is "none" (step S26; NO), the task remains highlighted until the task is executed. On the other hand, when the presence / absence 502 of the task movement is "Yes" (step S26; YES), the task cannot be completed as scheduled even if the movement is started from the current time, so it is necessary to contact the visited destination. Come out. Therefore, the CPU 11 derives the registered contents in order to register the contact to the visited destination as an alternative task (step; S27). That is, the CPU 11 functions as an alternative task generation unit 34. Specifically, the contents of the deadline derived value 505, the task details 508, the deadline attribute 509, and the deadline 510 are replaced in the contents of the task registered as this task. As the contents to be replaced, the deadline derived value 505 is overwritten with the contents of the deadline input value 504, and the task details 508 are changed to a character string obtained by adding "call to" to the target name 42 corresponding to the target ID 503. The deadline attribute 509 is changed to "contact", and the deadline 510 is returned from 1 to 0. When the content of the registered task is changed, the changed task list is displayed on the display unit 24 (step; S28).

As described above, according to the present embodiment, the server 10 causes the display unit 24 of the terminal device 20 to display the task registered by associating the target ID 503 with the deadline input value 504, and displays the current position information of the terminal device 20. Based on this, the deadline derived value 505 that should start moving toward the target is derived, and if the deadline derived value 505 or the deadline derived value 505 has passed for a predetermined time but the movement cannot be confirmed, the target is contacted. Information to the effect is displayed on the display unit 24. That is, the schedule management system 1 has a display control means and a movement start scheduled time derivation means.

Therefore, when the deadline derivation value 505 for starting the movement toward the visited destination has passed but it cannot be confirmed as ToDo, an alternative ToDo can be notified to the user.

Further, the server 10 changes the registered task into information indicating that the target should be contacted and displays it on the display unit 24. Therefore, the user can easily see the task of contacting the visited destination, which must be performed immediately.

Further, the server 10 registers the task, acquires the current time by the timekeeping unit 28 at the time of registering the task, determines whether or not the deadline derivation value 505 of the registered task is before the current time, and determines the current time. If it is determined to be before, the determination result is displayed. Therefore, it is possible to warn the user of the registration of the task for which the deadline derivation value 505 has already passed.

Further, the server 10 causes the display unit 24 to display information that the task whose deadline derivation value 505 is before the current time cannot be registered. Therefore, it is possible to prevent the registration of the task for which the deadline derivation value 505 has already passed.

The description in the above embodiment is an example of the schedule management device and the program according to the present invention, and is not limited thereto.

For example, in the above embodiment, if the task whose movement presence / absence 502 is “Yes” is not executed even after the deadline derivation value 505 has passed, the task is changed to the contact task to the visited destination, but the task is limited to this. It's not something. For example, regardless of the presence / absence of movement 502, if the task is not executed even after the deadline derivation value 505 has passed, the task may be changed to an alternative task registered in advance for each task. Then, the alternative task is not limited to contacting the visited destination, and may be appropriately changed according to the content of the task details 508.

Further, in the above embodiment, the current position is acquired and the deadline derivation value 505 in consideration of the current position is derived at the time of the task registration process, but the present invention is not limited to this. For example, the deadline derived value 505 may be updated at predetermined time intervals. At the time of updating, the latest current position information may be acquired from the position information detection unit 27, the deadline derivation value 505 based on the information may be derived again, and the latest information may be updated.

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 the equivalent scope thereof.
The inventions described in the claims originally attached to the application of this application are added below. The claims in the appendix are as specified in the claims originally attached to the application for this application.
[Additional Notes]
<Claim 1>
A display control means for displaying the visit schedule information registered in association with the visit destination location information and the scheduled visit time to the visit destination.
A means for deriving the scheduled movement start time, which derives the deadline time for starting the movement toward the visited destination based on the current location information, and
With
The display control means is the visit destination when the movement toward the visit destination cannot be confirmed even though the deadline time derived by the movement start scheduled time derivation means has passed or the deadline time has passed by a predetermined time. schedule management equipment, characterized in that it is displayed in association with the visit schedule information the information that the Company should contact the.
<Claim 2>
The display control means changes the visit schedule information to the information to be contacted and displays the information.
The schedule management device according to claim 1.
<Claim 3>
Registration means for registering the visit schedule information and
The current time acquisition means for acquiring the current time when registering the visit schedule information, and
A determination means for determining whether or not the deadline time derived by the movement start scheduled time derivation means of the visit schedule information registered by the registration means is before the current time acquired by the current time acquisition means, and
A display means for displaying the determination result when the determination means determines that the time is before the current time is further provided.
The schedule management device according to claim 1 or 2.
<Claim 4>
The display means displays information that the visit schedule information cannot be registered.
The schedule management device according to claim 3, wherein the schedule management device is characterized.
<Claim 5>
Computer,
A display control means for displaying the visit schedule information registered in association with the visit destination location information and the scheduled visit time to the visit destination.
A means for deriving the scheduled movement start time, which derives the deadline time for starting the movement toward the visited destination based on the current location information.
To function as
The display control means is the visit destination when the movement toward the visit destination cannot be confirmed even though the deadline time derived by the movement start scheduled time derivation means has passed or the deadline time has passed by a predetermined time. A program characterized by displaying information to the effect that it should be contacted in association with the visit schedule information.

1 Schedule management system 10 Server 11 CPU
12 Operation unit 13 RAM
14 Display unit 15 Storage unit 16 Communication unit 17 Bus 20 Terminal device 21 CPU
22 Operation unit 23 RAM
24 Display unit 25 Storage unit 26 Wireless communication unit 27 Location information detection unit 28 Timekeeping unit 29 Bus N communication network

Claims (4)

It is a schedule management device that can register the scheduled visit time to the visited destination in association with the location information of the visited destination .
A means for deriving the scheduled movement start time, which derives the first deadline time for deriving the movement toward the visited destination based on the current location information, and
Scheduled movement start time The visit schedule information to the effect that the movement should be started toward the visited destination by the first deadline time derived by the derivation means is displayed in a predetermined display area as the first task to be executed by the user. Display control means to make
With
Wherein the display control unit, when the movement or the first time limit first deadline time towards elapsed despite the visited predetermined time can not be confirmed, slower than the first time limit The contact schedule information that the visitor should be contacted by the second deadline time is displayed in the display area as an alternative task of the first task .
A schedule management device characterized by the fact that. The second deadline time is set to the scheduled visit time.
The schedule management device according to claim 1. When displaying the alternative task, the display control means displays a mark indicating that the alternative task is associated with the alternative task.
The schedule management device according to claim 1 or 2. A computer of the schedule management device that can register the scheduled visit time to the visited destination in association with the location information of the visited destination.
A means for deriving the scheduled movement start time, which derives the first deadline time for starting the movement toward the visited destination based on the current location information.
Scheduled movement start time The visit schedule information to the effect that the movement should be started toward the visited destination by the first deadline time derived by the derivation means is displayed in a predetermined display area as the first task to be executed by the user. Display control means,
To function as
The display control means is later than the first deadline time when the movement toward the visited destination cannot be confirmed even though the first deadline time or the first deadline time has passed by a predetermined time. The contact schedule information that the visitor should be contacted by the second deadline time is displayed in the display area as an alternative task of the first task.
A program characterized by that.