JP2020181621A - Schedule management program, schedule management method, and schedule management device - Google Patents

Abstract

To manage related tasks in association with each other.SOLUTION: A schedule management program for managing a schedule allows a computer to execute processing for receiving selection of a first task from among a plurality of types of tasks. The schedule management program allows the computer to execute processing for receiving designation of one or more tasks associated with the first task. The schedule management program allows the computer to execute processing for storing, in a storage unit, the first task and the one or more tasks, in response to designation of a time in a schedule regarding the first task, as a schedule in association with the designated time.SELECTED DRAWING: Figure 13F

Description

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

Schedule management software that manages schedules has been used conventionally. In such schedule management software, various tasks such as preparation for a visit to a customer, a visit to a customer, and a schedule for calling a customer are registered together with a scheduled date and time.

JP 2012-248072

However, although the conventional schedule management software can grasp the scheduled date and time of the registered task by the worker, it may be difficult to grasp the related task. For example, a related task may be registered in the task. For example, an insurance agent may encounter related tasks such as printing an insurance design document, preparing a catalog, and preparing a souvenir when preparing for a visit to a customer. Although the insurance salesperson can grasp each task by registering each task in the schedule management software, it is difficult to grasp the relationship between the tasks. Although the preparation for the visit of the insurance salesperson has been explained as an example, such a problem generally occurs when managing the schedule of related tasks.

In one aspect, it is an object of the present invention to provide a schedule management program, a schedule management method, and a schedule management device capable of associating and managing related tasks.

In the first plan, the schedule management program that manages the schedule accepts the selection of the first task from a plurality of types of tasks on the computer, registers one or more customer information as the first task, and registers. It accepts the designation of one or more tasks to be associated with each one or more customer information, and is associated with each of the one or more customer information and each customer information according to the time specification in the schedule for the first task. A process of storing one or more tasks as a schedule in the storage unit in association with the designated time is executed.

According to one embodiment of the present invention, there is an effect that related tasks can be associated and managed.

FIG. 1 is a diagram showing an example of a schematic configuration of a schedule system according to a first embodiment. FIG. 2 is a diagram showing an example of the configuration of the server device. FIG. 3 is a diagram showing an example of a data structure of user information. FIG. 4 is a diagram showing an example of a data structure of customer information. FIG. 5 is a diagram showing an example of a data structure of telephone contact information. FIG. 6 is a diagram showing an example of a data structure of menu information. FIG. 7 is a diagram showing an example of a data structure of main schedule information. FIG. 8 is a diagram showing an example of a data structure of sub-schedule information. FIG. 9 is a diagram showing an example of a data structure of task information. FIG. 10 is a diagram showing an example of a data structure of comparative performance information. FIG. 11 is a diagram showing an example of a data structure of automatically added task information. FIG. 12 is a diagram showing an example of a data structure of movement information. FIG. 13A is a diagram showing an example of a schedule screen. FIG. 13B is a diagram showing an example of a schedule screen. FIG. 13C is a diagram showing an example of a schedule screen. FIG. 13D is a diagram showing an example of a schedule screen. FIG. 13E is a diagram showing an example of a schedule screen. FIG. 13F is a diagram showing an example of a schedule screen. FIG. 14A is a diagram showing an example of displaying the target value and the actual value of the task. FIG. 14B is a diagram showing an example of displaying the required value of the task. FIG. 14C is a diagram showing an example of displaying the presence / absence of undisplayed tasks. FIG. 14D is a diagram showing an example of display of sub tasks. FIG. 14E is a diagram showing an example of display of sub tasks. FIG. 14F is a diagram showing an example of a schedule screen. FIG. 15 is a diagram showing an example of a data structure of main schedule information to which tasks are automatically added. FIG. 16A is a diagram showing an example of a schedule screen. FIG. 16B is a diagram showing an example of a schedule screen. FIG. 16C is a diagram showing an example of a schedule screen. FIG. 16D is a diagram showing an example of a schedule screen. FIG. 16E is a diagram showing an example of a schedule screen. FIG. 16F is a diagram showing an example of a schedule screen. FIG. 17A is a flowchart showing the flow of the task registration process. FIG. 17B is a flowchart showing the flow of the schedule display process. FIG. 17C is a flowchart showing the flow of the automatic registration process. FIG. 18 is a diagram showing a computer that executes a schedule management program.

Hereinafter, examples of the schedule management program, the schedule management method, and the schedule management device according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment. Then, each embodiment can be appropriately combined as long as the processing contents do not contradict each other.

[System configuration]
First, an example of the schedule system 10 according to the first embodiment will be described. FIG. 1 is a diagram showing an example of a schematic configuration of a schedule system according to a first embodiment. As shown in FIG. 1, the schedule system 10 includes a user terminal 11 and a server device 12. In this embodiment, the server device 12 corresponds to the schedule management device.

The schedule system 10 is a system that manages the user's schedule. In this embodiment, a case where the user manages the schedule of the insurance salesperson will be described as an example. Insurance agents visit customers to sell and sell insurance. In addition, the insurance salesperson performs various preparatory work for sales and sales of insurance at the office of the insurance company. The user terminal 11 is communicably connected to the server device 12 via the network N. As one aspect of the network N, any kind of communication network such as LAN (Local Area Network), VPN (Virtual Private Network), and mobile communication network can be adopted regardless of whether it is wired or wireless.

The user terminal 11 is a device possessed by an insurance salesperson who is a user. For example, the user terminal 11 is a mobile terminal device such as a smartphone or a tablet terminal. The insurance salesperson accesses the server device 12 using the user terminal 11, registers the action schedule and achievements, and manages the schedule.

The server device 12 is a computer that provides a schedule service for managing the schedule to the user. The schedule service may be provided by one computer, or may be provided by a computer system using a plurality of computers. In this embodiment, a case where the schedule service is provided by one server device 12 will be described as an example.

[Server device]
Next, the configuration of the server device 12 according to the first embodiment will be described. FIG. 2 is a diagram showing an example of the configuration of the server device. As shown in FIG. 2, the server device 12 includes a communication unit 20, a storage unit 21, and a control unit 22.

The communication unit 20 is an interface that controls communication with other devices. The communication unit 20 transmits and receives various information to and from other devices via the network N. As the communication unit 20, a network interface card such as a LAN card can be adopted.

The storage unit 21 is a storage device such as a hard disk, an SSD (Solid State Drive), or an optical disk. The storage unit 21 may be a semiconductor memory in which data such as a RAM (Random Access Memory), a flash memory, and an NVSRAM (Non Volatile Static Random Access Memory) can be rewritten. Further, the storage unit 21 may be an external server that stores and provides data.

The storage unit 21 stores various programs. In addition, the storage unit 21 stores various data used in various programs. For example, the storage unit 21 includes user information 30, customer information 31, telephone contact information 32, menu information 33, main schedule information 34, sub-schedule information 35, task information 36, and comparison record information 37. , Automatically added task information 38 and movement information 39 are stored.

The user information 30 is data that stores information about a user who manages the schedule. In this embodiment, as the user who manages the schedule, information about the insurance salesperson is stored in the user information 30.

FIG. 3 is a diagram showing an example of a data structure of user information. As shown in FIG. 3, the user information 30 has items such as "user ID", "user name", and "work location address". Each item of the user information 30 shown in FIG. 3 is an example, and may have other items.

The item of the user ID is an area for storing the identification information for identifying the insurance salesperson. An insurance salesperson is given a unique user ID (identification) as identification information. In the item of user ID, the user ID given to the insurance salesperson is stored. The user name item is an area for storing the user's name. The work address item is an area for storing the work address where the insurance salesperson works. For example, in the example of FIG. 3, the insurance salesperson whose user name is "user A" shows that the user ID is "001" and the work address is "XX, XX city, XX prefecture".

The customer information 31 is data that stores information about the customer. In this embodiment, the customer information 31 stores information about the customer who sold the insurance and the customer who operates the insurance by the insurance salesperson.

FIG. 4 is a diagram showing an example of a data structure of customer information. As shown in FIG. 4, the customer information 31 has items such as "customer ID", "customer name", "user ID in charge", "telephone number", and "address". It should be noted that each item of the customer information 31 shown in FIG. 4 is an example, and may have other items.

The item of the customer ID is an area for storing the identification information for identifying the customer. A unique customer ID is given to the customer as identification information. In the item of customer ID, the customer ID given to the customer is stored. The customer name item is an area for storing the customer's name. The item of the user ID in charge is an area for storing the user ID of the insurance salesperson in charge of the customer. The telephone number item is an area for storing the customer's telephone number. The address item is an area for storing the customer's address. For example, in the example of FIG. 4, a customer whose customer name is "customer A" has a customer ID of "0001", a user ID of an insurance salesperson in charge of "001", and a telephone number of "XXX-XXXXX". -XXXXX ", indicating that the address is" XX, XX City, XX Prefecture ".

The telephone contact information 32 is data that stores information about the customer. In this embodiment, information about the customer to be contacted by the insurance agent by telephone is stored in the telephone contact information 32. The insurance agent is notified by the company of the customers to be contacted by telephone, such as customers whose insurance is about to expire. For example, the telephone contact information 32 is generated by the system of the insurance company by extracting the customers to be contacted by each insurance salesperson, and is stored in the storage unit 21.

FIG. 5 is a diagram showing an example of a data structure of telephone contact information. As shown in FIG. 5, the telephone contact information 32 has items such as "user ID in charge", "contact target date", "customer ID", "insurance", and "contact status". Each item of the telephone contact information 32 shown in FIG. 5 is an example, and may have other items.

The item of the user ID in charge is an area for storing the user ID of the insurance salesperson in charge of telephone communication. The contact target date item is an area for storing the date of the target for making a telephone contact to the customer. The item of the customer ID is an area for storing the customer ID of the customer to be contacted. The insurance item is an area for storing the insurance that the customer has. The contact status item is an area for storing the status of telephone contact. For example, in the example of FIG. 5, the insurance salesperson whose user ID is "001" is the target of telephone contact with the customers whose customer IDs are "0001", "0002", and "0003" on June 30, 2016. Indicates that you are a customer. In addition, the customer whose customer ID is "0001" indicates that he / she has not taken out insurance and has completed the telephone contact.

The menu information 33 is data that stores information about the menu to be displayed when the schedule is registered. In this embodiment, various actions performed by the insurance salesperson who can register in the schedule, such as preparing for a visit to the customer, visiting the customer, and scheduling a call to the customer, are stored in the menu information 33 as tasks. ..

FIG. 6 is a diagram showing an example of a data structure of menu information. As shown in FIG. 6, the menu information 33 has items such as "selected task", "order", and "display task". Each item of the menu information 33 shown in FIG. 6 is an example, and may have other items.

The item of the selected task is an area for storing the task selected in the schedule registration. The order item is an area for storing the order in which tasks are displayed in the menu. The display task item is an area for storing the task to be displayed in the menu. Here, in this embodiment, in the schedule registration, the task to be displayed next in the menu is changed according to the task selected in the menu. In the menu information 33, a task to be displayed on the menu is registered so that a task frequently associated with the selected task is displayed on the menu according to the task selected on the menu. For example, in the menu information 33, the task to be displayed in the menu when the task is not selected in the schedule registration is registered as the item of the selected task as "None". Further, in the menu information 33, the task to be displayed in the menu when the task is selected in the schedule registration is registered as the selected task item. For example, in the example of FIG. 6, when a task is not selected in the schedule registration, each task of "telephone", "preparation for visit", and the like is stored as a task to be displayed in the menu. Further, in the example of FIG. 6, when "telephone" is selected in the schedule registration, each task of "catalog", "souvenir", etc. is stored as a task to be displayed in the menu.

The main schedule information 34 and the sub-schedule information 35 are data that store information about the task for which the schedule has been registered. Here, the task that the insurance agent registers in the schedule may include a task associated with the task. In this embodiment, the task that is the subject of each time is managed as the main task in the schedule, and the task associated with the main task and associated with it is managed as the sub task. The main schedule information 34 stores information about the main task registered in the schedule. The sub-schedule information 35 stores information about the sub-tasks registered in the schedule.

FIG. 7 is a diagram showing an example of a data structure of main schedule information. As shown in FIG. 7, the main schedule information 34 has items such as "user ID", "main task ID", "task", "start date and time", "end date and time", and "customer ID". Each item of the main schedule information 34 shown in FIG. 7 is an example, and may have other items.

The user ID item is an area for storing the user ID of the insurance salesperson who registered the task. The item of the main task ID is an area for storing identification information for identifying the subject task registered in the schedule. When the insurance agent registers a task in the schedule, the registered task is given a unique task ID as identification information for identifying the registered task. In the item of main task ID, the task ID of the subject task registered in the schedule is stored. The task item is an area for storing the type of the subject task registered in the schedule. The start date / time item is an area for storing the start date / time of the subject task registered in the schedule. The end date / time item is an area for storing the end date / time of the subject task registered in the schedule. The item of the customer ID is an area for storing the customer ID of the customer who is the target of the subject task registered in the schedule. In the customer ID item, when the subject task registered in the schedule is a work for a specific customer, the customer ID of the specific customer is stored, and the subject task registered in the schedule is for the specific customer. If it is not work, "-" is stored. For example, in the example of FIG. 7, the insurance salesperson with the user ID “001” is the task of “telephone” with the task ID “00001” from 10:00 on June 30, 2016 to 11:00 on June 30, 2016. Indicates that is registered in the schedule. Further, since the item of the customer ID is "-", the task of "telephone" indicates that the work is not for a specific customer.

FIG. 8 is a diagram showing an example of a data structure of sub-schedule information. As shown in FIG. 8, the sub-schedule information 35 has items such as “main task ID”, “customer ID”, “sub-task ID”, and “task”. Each item of the sub-schedule information 35 shown in FIG. 8 is an example, and may have other items.

The item of the main task ID is an area for storing the task ID of the main task to which the sub task is associated. The customer ID item is an area for storing the customer ID of the customer who is the target of the sub task. In the customer ID item, if the sub-task is work for a specific customer, the customer ID of the specific customer is stored, and if the sub-task is not work for a specific customer, "-" is stored. .. The item of the subtask ID is an area for storing the task ID of the subtask registered in association with the main task. The task item is an area for storing the types of sub-tasks registered in association with the main task. For example, in the example of FIG. 8, it is shown that the task of "memo" having the task ID of "10001" is registered in the schedule for the main task having the task ID of "00002".

The task information 36 is data that stores information about the task registered in the schedule. In this embodiment, information about the main task and the sub task registered in the schedule are both stored in the task information 36.

FIG. 9 is a diagram showing an example of a data structure of task information. As shown in FIG. 9, the task information 36 has items such as “task ID”, “target value”, “cost”, and “processing status”. Each item of the task information 36 shown in FIG. 9 is an example, and may have other items.

The task ID item is an area for storing the task IDs of the main task and the sub task registered in the schedule. The target value item is an area for storing the target number of cases to be processed by the insurance agent in the registered main task and sub task. The target number may be set for each type of task, or may be registered by an insurance salesperson. The target number is stored in the target value item. The cost item is an area for storing costs incurred in the registered main task and sub task. The processing status item is an area for storing the processing status of the registered main task and sub task. In the processing status item, "-" is stored when the task work is unprocessed, and "completed" is stored when the task work is completed. For example, in the example of FIG. 9, the task with the task ID of "00001" has a target number of "10", the cost incurred is "0" yen, and the work is unprocessed.

The comparison result information 37 is data that stores information about the results to be compared by each task. In this embodiment, when an insurance salesperson registers a task, the actual results to be compared with the registered task are displayed. The performance to be compared may be the past performance of the same insurance salesperson as the insurance salesperson of the logged-in user ID, or the past performance of another insurance salesperson. For example, the comparison performance information 37 may store the average of the performances of the insurance salesperson of the logged-in user ID in the past predetermined period. Further, for example, the comparative performance information 37 may store the performance of the task of the insurance salesperson having excellent results as a sample.

FIG. 10 is a diagram showing an example of a data structure of comparative performance information. As shown in FIG. 10, the comparison result information 37 has items such as “task” and “number of comparison targets”. Each item of the comparative result information 37 shown in FIG. 10 is an example, and may have other items.

The task item is an area for storing the type of task to be compared. The number of comparison targets is an area for storing the actual number of processed tasks of the task to be compared. For example, in the example of FIG. 10, the telephone task indicates that the number of actual processing cases to be compared is "10".

The automatically added task information 38 is data that stores information about tasks that can be automatically added. Here, the insurance agent may register important tasks such as tasks related to the customer in the schedule, but may not register arbitrary tasks such as tasks related to the insurance agent himself. Therefore, in this embodiment, it is possible to automatically add a predetermined arbitrary task to be performed regularly to the schedule.

FIG. 11 is a diagram showing an example of a data structure of automatically added task information. As shown in FIG. 11, the automatically added task information 38 has items such as “task”, “allowable time zone”, and “time width”. Each item of the automatically added task information 38 shown in FIG. 11 is an example, and may have other items.

The task item is an area for storing the types of tasks that can be added automatically. The item of the allowable time zone is an area for storing the time zone in which the addition of the task is permitted. The time width item is an area for storing the time of the time width required by the task. For example, in the example of FIG. 11, it is shown that the morning assembly task can be automatically added in the time zone from 9:00 to 10:00 if there is a vacancy of 30 minutes.

The movement information 39 is data that stores information related to the movement task. Here, the insurance salesperson moves by visiting a customer or the like. The movement information 39 stores information about a movement task such as a visit to a customer.

FIG. 12 is a diagram showing an example of a data structure of movement information. As shown in FIG. 12, the movement information 39 has items such as "task ID", "departure place", "arrival place", "route", and "cost". Each item of the movement information 39 shown in FIG. 12 is an example, and may have other items.

The task ID item is an area for storing the task ID of the moving task. The origin item is an area that stores the origin of the move. The destination item is an area that stores the destination of the move. The route item is an area for storing the travel route from the departure point to the arrival point. The cost item is an area that stores the cost of traveling from the place of departure to the place of arrival. For example, in the example of FIG. 12, the movement task whose task ID is "00007" has a departure place of "XX prefecture XX city XX", an arrival place of "XX prefecture XX city AA", and a movement route of "XXXXXX". It shows that the cost is "370" yen.

The control unit 22 is a device that controls the server device 12. As the control unit 22, an electronic circuit such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit) or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array) can be adopted. The control unit 22 has an internal memory for storing programs and control data that define various processing procedures, and executes various processing by these. The control unit 22 functions as various processing units by operating various programs. For example, the control unit 22 has a display control unit 50, a reception unit 51, a registration unit 52, and an acquisition unit 53.

The display control unit 50 controls the display of various types of information. For example, when the display control unit 50 receives access from the user terminal 11, it controls to transmit various operation screen information to the access source user terminal 11 and display the operation screen on the access source user terminal 11. For example, the display control unit 50 displays the login screen on the user terminal 11 in response to the access from the user terminal 11, inputs the user ID, and accepts the login. When the login is successful, the display control unit 50 controls the user terminal 11 to display various screens such as an operation screen. For example, the display control unit 50 causes the user terminal 11 to display a schedule screen displaying the schedule of the insurance salesperson of the input user ID.

FIG. 13A is a diagram showing an example of a schedule screen. The example of FIG. 13A shows an example of the schedule screen displayed on the user terminal 11. The schedule screen 100 has a header area 101 provided at the top of the schedule screen 100 and a main area 102 for displaying the schedule. The header area 101 is provided with a date area 103 for displaying a date and a weather display area 104 for displaying weather information.

In the date area 103, the date of the login date is displayed as the initial display. Further, the date area 103 is provided with switching icons 103A on the left and right sides of the date, and the displayed date can be changed by the switching icon 103A. In the main area 102, the schedule of the date displayed in the date area 103 is displayed. The insurance agent can also check the schedule of past and future dates by operating the switching icon 103A to change the displayed date.

In the weather display area 104, the weather information corresponding to the position of the user terminal 11 is displayed. For example, the display control unit 50 acquires the position information of the user terminal 11 from the user terminal 11 and transmits the weather information corresponding to the position of the position information of the user terminal 11 to the weather display area 104 from the external server that provides the weather information. Display it.

In the main area 102, the time is displayed in order in the horizontal direction, and the flow of time is expressed. Further, the main area 102 is provided with a menu icon 110, a cost icon 111, a trash can icon 112, and a simulation icon 113.

The menu icon 110 is an icon that instructs the display of tasks that can be registered in the schedule. The cost icon 111 is an icon instructing the display of the cost incurred. The trash can icon 112 is an icon for deleting a task. In this embodiment, the task to be deleted is deleted from the schedule by moving the task to be deleted to the trash can icon 112 while keeping the selected state and deselecting the task. The simulation icon 113 is an icon instructing the addition of a task that can be automatically added to the schedule.

The reception unit 51 accepts various operations. For example, the reception unit 51 receives various operations by receiving various operation information on the operation screen from the user terminal 11. For example, the reception unit 51 accepts various operations related to the schedule in response to the operation on the schedule screen 100. For example, the reception unit 51 receives a display instruction for a task that can be registered in the schedule by selecting the menu icon 110 on the schedule screen 100.

When the display control unit 50 receives the selection operation of the menu icon 110, the display control unit 50 displays the tasks that can be added to the schedule on the schedule screen 100 based on the menu information 33.

FIG. 13B is a diagram showing an example of a schedule screen. The example of FIG. 13B shows a state in which the menu icon 110 is selected. For example, as shown in FIG. 13B, when the task is not selected, the display control unit 50 reads out the task whose selected task item is "None" from the menu information 33. Then, the display control unit 50 displays icons 120 (120A to 120I) indicating the read tasks in order around the menu icon 110. Icon 120A represents a telephone task. Icon 120B represents a visit preparation task. Icon 120C represents a customer visit task. Icon 120D represents a taxi movement task. Icon 120E represents the task of moving the train. The icon 120F indicates the task of moving the bicycle. Icon 120G represents a walking task. Icon 120H represents a lunch task. Icon 120I represents a resting task.

The reception unit 51 accepts the selection of tasks to be added to the schedule. For example, the reception unit 51 accepts the selection of a task to be added to the schedule from a plurality of types of tasks by the selection operation of the icons 120A to 120I on the schedule screen 100. In addition, the reception unit 51 accepts the designation of the start time and end time of the task to be added to the schedule. For example, the reception unit 51 accepts the designation of the start time and the end time by moving the icon of the task to be added to the schedule to the time position in the selected state.

For example, when an insurance agent adds a task to a schedule, he or she moves the task to be added to the start time position while keeping it selected, and deselects the task. FIG. 13C is a diagram showing an example of a schedule screen. The example of FIG. 13C shows a state in which the operation of moving to 10 o'clock with the icon 120A selected is performed, the start time is 10 o'clock, and the telephone task is added to the schedule. The display control unit 50 displays the sub-area 105 for setting the added task in the lower half of the main area 102. The time is also displayed in order in the horizontal direction in the sub area 105. In the example of FIG. 13C, the start time of 10 o'clock is displayed in the sub area 105 together with the telephone task icon 121.

In the sub area 105, it is possible to specify the end time of the added task. Further, in the sub-area 105, it is possible to specify a task to be associated with the added task. When a task is selected from the menu icon 110 and a task is added, the display control unit 50 displays a frequently associated task associated with the added task as a task that can be added. For example, as shown in FIG. 13C, when a telephone task is selected, the display control unit 50 reads out a task whose selected task item is "telephone" from the menu information 33. Then, the display control unit 50 displays icons 130 (130A to 130G) indicating the read tasks in order around the menu icon 110. Icon 130A represents the task of preparing an insurance catalog. Icon 130B shows the task of preparing souvenirs. The icon 130C indicates a task of registering the content to be notified to the customer. Icon 130D indicates a task for registering the contents of the memo. Icon 130E represents the task of preparing an insurance design document. The icon 130F indicates a task for registering expenses. The icon 130G shows a task of registering an appointment with a customer.

When the insurance agent specifies the end time of the added task, the insurance agent moves the icon 121 displayed in the sub area 105 to the end time position while keeping the selected state, and cancels the selection. FIG. 13D is a diagram showing an example of a schedule screen. The example of FIG. 13D shows a state in which the operation of moving to 11 o'clock with the icon 121 selected is performed and the end time of the telephone task is designated as 11 o'clock. The display control unit 50 displays the end time of 11 o'clock in the sub area 105 together with the telephone task icon 122.

In addition, when associating a task associated with a task added to the schedule, the insurance salesperson moves the task to be associated to the position of the sub-area 105 while keeping the task to be selected, and deselects the task. FIG. 13E is a diagram showing an example of a schedule screen. The example of FIG. 13E shows a state in which the memo, design document, catalog, and souvenir tasks are associated with the visit preparation task. The display control unit 50 displays the icon 123 of each task of the memo, the design document, the catalog, and the souvenir in the sub area 105.

When the reception unit 51 accepts the addition of the task to the schedule, the registration unit 52 registers the added task in the storage unit 21. For example, when the main task is added, the registration unit 52 assigns a unique task ID to the added main task. Then, the registration unit 52 sets the user ID of the insurance salesperson who registered the task, the task ID of the added main task, the main task, the start date and time of the main task, and the end date and time of the main task in the main schedule information 34. to register. When the customer who is the target of the main task is specified, the registration unit 52 registers the customer ID of the customer who is the target of the task in the main schedule information 34, and when the target customer is not specified. , The customer ID is registered in the main schedule information 34 as "-". The designation of the target customer will be described later. Further, the registration unit 52 registers a record in the task information 36 with the task ID of the added main task.

Further, for example, when a sub task is added, the registration unit 52 assigns a unique task ID to the added sub task. Then, the registration unit 52 registers the task ID of the main task, the task ID of the sub task, and the sub task associated with the added sub task in the sub schedule information 35. When a customer who is the target of the sub task is specified, the registration unit 52 registers the sub task in the sub schedule information 35 for each customer ID of the customer who is the target of the task, and the target customer If not specified, the sub task is registered in the sub-schedule information 35 with the customer ID as "-". As a result, when a sub task is added, the main task and each sub task are stored in the storage unit 21 as a schedule in association with each other.

When the main area 102 is selected after the task is registered in the schedule on the schedule screen 100, the display control unit 50 displays the registered task in the main area 102. For example, the display control unit 50 displays the registered main task. When a sub task associated with the main task is registered, the display control unit 50 displays the sub task in association with the main task. FIG. 13F is a diagram showing an example of a schedule screen. The example of FIG. 13F shows a state in which two visits are registered as the main tasks: telephone call, visit preparation. The display control unit 50 displays a schedule bar displaying a bar 140 in which the name corresponding to the main task is described at the position and length corresponding to the time zone of the main task for each registered main task. .. For example, the display control unit 50 displays the bar 140 in the time range of the main area 102 corresponding to the start date and time and the end date and time of the main task. Further, the display control unit 50 displays the icon 141 of the main task corresponding to the bar 140 for each main task. When a sub task associated with the main task is registered, the display control unit 50 displays the icon 142 of the accompanying sub task around the icon 141 of the main task.

For the tasks registered in the schedule, it is possible to set the target number of cases to be processed by the insurance agent as a target value. The target number may be automatically set from the past performance of the insurance salesperson, a fixed value may be set, or the insurance salesperson may be able to register. For example, the target number of each task may be the average or maximum value of the insurance agent's past performance for a given period of time for the same type of task. Further, the target value of each task may be registered by an insurance salesperson by displaying an operation screen such as a software keyboard on which numerical values can be input when registering the task. The registration unit 52 registers the target number of tasks in the task information 36.

In this embodiment, the icon 141 of the main task is displayed on the schedule screen 100 at a height corresponding to the target.

The acquisition unit 53 acquires various types of information. For example, the acquisition unit 53 acquires the target number of main tasks from the task information 36 for each main task. Further, when the sub task is registered in association with the main task, the acquisition unit 53 also acquires the target number of sub tasks associated with the main task from the task information 36.

The display control unit 50 weights and adds a predetermined number of weights according to the type of the task for each main task, and obtains a target value for each main task. The display control unit 50 displays the icons 141 of the main tasks at heights corresponding to the calculated target values. In the example of FIG. 13F, a line 143 connecting the icons 141 of the main tasks at a height corresponding to the target value is shown.

Further, in this embodiment, the past results of the main task are displayed on the schedule screen 100.

For example, the acquisition unit 53 acquires the number of processed results of the actual results to be compared with the main task from the comparison actual information 37 for each main task. In addition, when the sub task is registered in association with the main task, the acquisition unit 53 also acquires the number of processed achievements to be compared with the sub task associated with the main task from the comparison achievement information 37. ..

The display control unit 50 assigns a predetermined weight according to the type of task to each main task, weights and adds the number of actual processing cases, and obtains the actual value for each main task. The display control unit 50 displays the past achievements at the same time position as the icon 141 of the main task at a height corresponding to the calculated actual value. In the example of FIG. 13F, a line 144 connecting past achievements at a height corresponding to the actual value is shown. The display control unit 50 may display the target value and the actual value of the task. FIG. 14A is a diagram showing an example of displaying the target value and the actual value of the task. The example of FIG. 14A shows the case where the target value and the actual value are displayed for the main task.

The reception unit 51 accepts the operation of registering the incurred cost for the task registered in the schedule. The registration unit 52 registers the registered cost in the cost item of the task information 36 for the task for which the cost is registered. In addition, the reception unit 51 accepts a process completion operation for the task registered in the schedule. The registration unit 52 registers "completed" in the processing status item of the task information 36 for the task that has received the operation of processing completion.

The reception unit 51 may accept input of information related to task execution such as the number of processed tasks for the task registered in the schedule. When the information regarding the execution of the task is input, the display control unit 50 may update and display the remaining necessary values until the target value is reached. FIG. 14B is a diagram showing an example of displaying the required value of the task. The example of FIG. 14B shows the case where the remaining required values until the target value is reached are displayed for the main task.

Further, the reception unit 51 may accept the setting of the target by changing the height of the icon 141 of the main task displayed on the schedule screen 100. For example, the task icon 141 makes it possible to change the display position. When the height of the task icon 141 is changed, the registration unit 52 changes and registers the target number of tasks according to the changed height. For example, the registration unit 52 divides the changed target value by a predetermined weight according to the type of the task whose target value has been changed to obtain the target number of tasks and registers it in the task information 36. When the target value of the main task to which the sub task is attached is changed, the registration unit 52 may register the changed target value in the task information 36 as the target number of the main task.

When a large number of sub-tasks are associated with the main task and the associated sub-tasks cannot be displayed around the main task, the display control unit 50 can identify the presence or absence of undisplayed tasks. Or display a mark. FIG. 14C is a diagram showing an example of displaying the presence / absence of undisplayed tasks. In the example of FIG. 14C, a mark 145 indicating that there is an undisplayed sub task is displayed for the main task.

When the mark 145 is selected, the display control unit 50 displays a sub task. FIG. 14D is a diagram showing an example of display of sub tasks. In the example of FIG. 14D, the icon 142 of the sub task associated with the main task is displayed in a balloon.

The display control unit 50 may display the undisplayed sub-tasks by moving the displayed sub-tasks arranged around the main task. FIG. 14E is a diagram showing an example of display of sub tasks. In the example of FIG. 14E, the undisplayed sub-task is displayed in the surroundings by rotating the sub-task around the main task.

In addition, the reception unit 51 may be able to accept customers who are the targets of task processing. For example, the reception unit 51 accepts a customer to be processed for the main task registered in the schedule. For example, the display control unit 50 reads the customer in charge of the insurance salesperson of the logged-in user ID from the customer information 31 and displays the customer list. The reception unit 51 accepts customers to be processed from the customer list. The registration unit 52 registers the customer ID of the customer to be processed in the customer ID item of the main schedule information 34. In addition, the reception unit 51 may accept the registration of sub-tasks for each customer to be processed. FIG. 14F is a diagram showing an example of a schedule screen. In the example of FIG. 14F, a plurality of customers are registered for the main task of visit preparation, and the registered customers corresponding to the icon 141 of the main task of visit preparation are displayed in a balloon. In addition, the icon of the sub task registered as "Remarks" is displayed for each customer. For example, the reception unit 51 accepts the registration of the sub task by moving the sub task to be added from the menu icon 110 to the position of "Remarks" while keeping it in the selected state and canceling the selection. When a customer who is the target of the sub task is specified, the registration unit 52 registers the customer ID of the customer who is the target of the task in the sub schedule information 35.

By the way, for example, an insurance salesperson registers and manages tasks such as preparing for a visit to a customer, visiting a customer, and scheduling a call to a customer, but lunch, moving to a destination, morning assembly, daily report, etc. Creation etc. may not be registered as a task.

Therefore, in this embodiment, it is possible to add a task that can be automatically added to the schedule. For example, the insurance agent selects the simulation icon 113 on the schedule screen 100 when adding a task that can be automatically added to the schedule.

When the reception unit 51 accepts the selection operation of the simulation icon 113, the registration unit 52 adds the task that can be automatically added to the schedule based on the automatic addition task information 38. For example, the registration unit 52 refers to the automatically added task information 38, and for each registered automatically addable task, is within the permissible time zone and other than the time zone corresponding to the task registered in the schedule. In, it is determined whether or not the time of the time width required by the task that can be added automatically can be secured. Then, the registration unit 52 can automatically add the task when the time width required by the task that can be automatically added can be secured in a time zone other than the time zone corresponding to the task registered in the schedule. Automatically schedule tasks. The registration unit 52 registers the tasks that can be automatically added as the main tasks in the main schedule information 34 and the task information 36.

Further, when the reception unit 51 accepts the selection operation of the simulation icon 113, the registration unit 52 automatically adds the task of movement to the schedule. For example, if the task of visiting the customer is registered in the schedule and there is no task of moving to the address of the customer before the task of visiting the customer, the registration unit 52 performs the task of moving to the address of the customer. Add automatically. Further, when the task of visiting the customer is registered in the schedule and there is no task of moving to the work address where the insurance salesperson works after that, the registration unit 52 performs the task of moving to the work address. Add automatically. For example, the registration unit 52 specifies the address where the main task is performed according to the time for each main task registered in the schedule. In this embodiment, the visiting task uses the address where the task is performed as the address of the visited customer. The registration unit 52 identifies the address of the visited customer with reference to the customer information 31. For the main task other than the visit, the address of the place of work where the insurance agent works is the address where the task is performed. The registration unit 52 refers to the user information 30 to specify the work address where the insurance salesperson with the logged-in user ID works. Then, the registration unit 52 determines, for each main task registered in the schedule, whether there is a task of moving to the address where the main task is performed before the main task. In addition, the registration unit 52 sets the reference place where the schedule starts and the reference place where the schedule ends as the work address where the insurance salesperson of the user ID works, according to the schedule, before the visit task. May determine if there is a task to move to the address of the visited customer, or if there is a task to move to the work address before the daily report task. For example, the registration unit 52 determines whether there is a task of moving from the reference place where the schedule starts to the address of the visited customer and from the address of the visited customer to the reference place where the schedule ends according to the schedule. judge.

When there is no movement task, the registration unit 52 automatically schedules and registers the task of moving to the address where the task is performed before the task. For example, the registration unit 52 uses an external server that provides a movement route search service to search for a movement route and cost by designating a movement source address and a movement destination address, and uses the searched movement route and cost. Register the move task. For example, the registration unit 52 arrives at a predetermined time before the start time of the visiting task (for example, 10 minutes before), or after a predetermined time (for example, 10 minutes) after the end time of the task before the visiting task. ) Is set as the departure time, the movement route is searched, and the movement task is automatically registered. The registration unit 52 registers each movement task as the main task in the main schedule information 34 and the movement information 39.

The registration unit 52 may register the lunch task after registering the movement task first. For example, the registration unit 52 searches for a movement route and moves by setting a predetermined time before the start time of the visiting task as the arrival time or a predetermined time after the end time of the task before the visiting task as the departure time. Register the task automatically. Then, the registration unit 52 may register the lunch task when it is possible to secure the time width required by the lunch task other than the time zone corresponding to the task registered in the schedule.

By the way, the user may have each behavioral characteristic in the behavior of the schedule. For example, an insurance agent may have a behavioral characteristic of moving to a destination as soon as the previous task is completed, or a behavioral characteristic of moving to a destination immediately before the start time of the visit. There is.

Therefore, the registration unit 52 may register the task according to the behavioral characteristics of the user or the set rules. For example, the registration unit 52 registers the movement task near the scheduled completion time of the task before the movement task or sets the movement task according to the behavior characteristics of the user or the set rule. On the other hand, the task of the move may be registered or controlled closer to the scheduled start time of the subsequent task. The user's behavioral characteristics may be preset by the user as a rule, or may be obtained from a past schedule. For example, the registration unit 52 reads the past schedule of the insurance salesperson of the logged-in user ID from the main schedule information 34, and specifies the behavioral characteristics of the insurance salesperson. Then, the registration unit 52 may register the task of movement with the specified behavioral characteristics. For example, the registration unit 52 specifies at what timing the task of movement in the past predetermined period (for example, one month) was performed with respect to the task before and after the task of movement. For example, the registration unit 52 obtains the time interval between the task before the movement task and the movement task, and obtains the frequency distribution of the time interval every predetermined time width (for example, 5 minutes). In addition, the registration unit 52 obtains the time interval between the task of movement and the task after the task of movement, and obtains the frequency distribution of the time interval for each predetermined time width. Then, the registration unit 52 registers the task of movement so as to have the same timing as the most frequent timing. For example, when the time interval between the task before the move task and the time interval between the move tasks is most frequently 6 to 10 minutes, the registration unit 52 starts with 6 from the end time of the task before the move task. The task of movement is registered with the time when any of minutes to 10 minutes has passed (for example, the central 8 minutes) as the departure time. The registration unit 52 may specify the behavioral characteristics from the past movement tasks included in the time zone for each predetermined time zone, and register the movement tasks according to the behavioral characteristics for each time zone. The time zone may be the same time interval, for example, an hourly time zone. Further, the time zone may be a time zone in consideration of lunch time and non-lunch time, for example, a time zone before 12:00, a time zone from 12:00 to 14:00, and a time zone after 14:00. Further, the registration unit 52 may specify the behavior characteristic from the past movement task that has moved to the same address as the movement task to be added, and register the movement task with the specified behavior characteristic.

Further, the registration unit 52 may control the movement route so as to move by the transportation means frequently used for movement according to the behavior characteristics of the user or the set rule. For example, the registration unit 52 refers to the movement information 39, reads out a past route having the same movement source address and movement destination address, and obtains the frequency for each means of transportation used. In addition, the address of the move source and the address of the move destination are treated as the same in a predetermined range such as in the same town even if they do not completely match the address of the move source and the address of the move destination in the past, respectively. Then, the registration unit 52 uses an external server that provides a movement route search service to search for the movement route and cost by designating the most frequent means of transportation, the address of the movement source, and the address of the movement destination. Register the task of travel with the travel route and cost. As a result, the movement route is searched by the transportation means often used for moving from the address of the movement source to the address of the movement destination.

In addition, the registration unit 52 searches for restaurants that are candidates for lunch according to the scheduled position at the time of the lunch task for the lunch task, and uses the information about the searched restaurants as lunch information for the lunch task. It may be stored in the storage unit 21 in association with each other. For example, the registration unit 52 sets the address of the destination of the move task before the lunch task or the address of the departure point of the move task after the lunch task as the scheduled position at the time of the lunch task. Identify. The registration unit 52 specifies the scheduled position and the time of the lunch task, and uses an external server that provides a restaurant search service to eat and drink that is close to the specified position and the lunch task time is included in the business hours. Search for a store. The registration unit 52 may store the searched restaurant name, restaurant location, telephone number, menu, and the like as lunch information in the storage unit 21 in association with the lunch task. The registration unit 52 may search for restaurants and register lunch tasks according to the user's behavioral characteristics or set rules. The user's behavioral characteristics may be preset by the user as a rule, or may be obtained from a past schedule. For example, the registration unit 52 reads the past schedule of the insurance salesperson of the logged-in user ID from the main schedule information 34, and from the lunch information associated with the lunch task, the genre of the restaurant that is frequently used. To identify. The registration unit 52 uses an external server that provides a restaurant search service to search for restaurants of the genre that is close to the specified location, has lunch task time included in business hours, and is used most frequently. You may.

As a result, for example, when the automatic addition task information 38 is in the state of FIG. 11, the morning assembly task is automatically added in the time zone from 9:00 to 10:00 if there is a vacancy of 30 minutes. Also, during the time period from 12:00 to 14:00, if there is a free time of 30 minutes, a lunch task will be added automatically. In addition, daily report tasks are automatically added if there is a 30-minute vacancy between 17:00 and 19:00. In addition, the task of moving is automatically added. FIG. 15 is a diagram showing an example of a data structure of main schedule information to which tasks are automatically added. The example of FIG. 15 shows a state in which a task is automatically added from the state of FIG. 7.

The display control unit 50 displays the schedule including the automatically added task on the schedule screen 100. FIG. 16A is a diagram showing an example of a schedule screen. In the example of FIG. 16A, bars 140 and icons 141 for morning assembly, lunch, daily reports, and moving tasks are added to the schedule from the state of FIG. 13F.

The reception unit 51 accepts changes in the start date and time and end date and time of the task to which the bar 140 has moved by moving the task bar 140 displayed on the schedule screen 100 as a selected state. When the registration unit 52 accepts the movement of the task bar 140, the registration unit 52 changes the start date and time and the end date and time stored in the main schedule information 34 for the task to which the bar 140 has moved according to the time at the position of the movement destination. For example, when the bar 140 is changed to a position at an earlier time, the registration unit 52 re-searches the movement route with the time corresponding to the start position of the bar 140 as the departure time, and sets the movement route of the movement task. change. Further, when the bar 140 is changed to a position at a later time, the registration unit 52 re-searches the movement route with the time corresponding to the rear end position of the bar 140 as the arrival time, and changes the movement route of the movement task. To do. Further, when the period of the moved task and the automatically added task overlap due to the movement of the bar 140, the registration unit 52 may re-register the automatically added task.

When the task icon displayed on the schedule screen 100 is selected, the display control unit 50 causes the schedule screen 100 to display various information related to the task of the selected icon.

For example, when the movement task icon 141 is selected, the display control unit 50 reads the movement route of the movement task of the selected icon 141 from the movement information 39 and displays the movement route. FIG. 16B is a diagram showing an example of a schedule screen. In the example of FIG. 16B, a route map showing the movement route in association with the movement task is displayed in a balloon.

Further, for example, when the lunch task icon 141 is selected, the display control unit 50 reads out the lunch information corresponding to the lunch task of the selected icon 142 from the storage unit 21, and the lunch information. Is displayed. FIG. 16C is a diagram showing an example of a schedule screen. In the example of FIG. 16C, a map showing the names and locations of restaurants is displayed in balloons in association with the lunch task.

Further, for example, when the telephone task icon 141 is selected, the display control unit 50 displays information on the customer to be contacted by telephone on the scheduled day by the insurance salesperson with the logged-in user ID. For example, the display control unit 50 reads out from the telephone contact information 32 the customer ID of the customer to whom the insurance agent of the logged-in user ID makes a telephone contact on the scheduled day, the insurance that the customer subscribes to, and the status of the telephone contact. .. Further, the display control unit 50 reads out the customer name and telephone number corresponding to the customer ID from the customer information 31. Then, the display control unit 50 displays the customer name of the customer to be contacted by telephone, the insurance to which the customer subscribes, the telephone number, and the status of telephone contact. FIG. 16D is a diagram showing an example of a schedule screen. In the example of FIG. 16D, the customer name of the customer to be contacted by telephone in association with the task of telephone, the insurance to which the customer subscribes, the telephone number, and the status of telephone contact are displayed in a balloon. In this embodiment, it is possible to add a customer to be contacted by telephone by selecting the add button 146.

Further, for example, the display control unit 50 displays information assisting the creation of the daily report when the icon 141 of the daily report task is selected. For example, the display control unit 50 displays the tasks registered according to the schedule, the time of the task start date and time, and the time of the task end date and time. FIG. 16E is a diagram showing an example of a schedule screen. In the example of FIG. 16E, each task registered in association with the task of the daily report, the time of the start date and time of the task, and the time of the end date and time of the task are displayed in balloons. In addition, each task is provided with a voice input button 147 so that it is possible to input a notice in a dialogue with the customer by voice. The content input by voice is converted into text by voice recognition, and is output as a report together with the display content of each task displayed in a balloon by a predetermined operation.

Further, for example, the display control unit 50 displays the notification items of the notification items from the company notified from the system of the insurance company when the icon 141 of the morning assembly task is selected.

Further, for example, when the cost icon 111 is selected, the display control unit 50 displays the cost incurred in each task registered in the schedule. FIG. 16F is a diagram showing an example of a schedule screen. In the example of FIG. 16F, the costs incurred in each task registered in the schedule in association with the cost icon 111 are displayed in a balloon. The costs incurred in each task can be tabulated separately on the cost screen for one week, one month, one year, etc., and can be output as data that can be used for final tax returns.

In this embodiment, among the tasks registered in the schedule, the tasks of the date and time before the current date and time are treated as the actual results. Insurance agents can register achievements by moving and modifying each task registered in the schedule. In addition, each task registered in the schedule may be moved or modified from the user terminal 11 of the insurance salesperson based on the location information. For example, the acquisition unit 53 acquires location information from the user terminal 11 of the insurance salesperson. The registration unit 52 may move or modify each task registered in the schedule based on the acquired location information. For example, the registration unit 52 may move or modify the movement task based on the acquired position information.

[Processing flow]
Next, the flow of various processes executed by the server device 12 according to this embodiment will be described. First, the flow of the task registration process in which the server device 12 accepts the registration of the task in the schedule will be described. FIG. 17A is a flowchart showing the flow of the task registration process. The task registration process shown in FIG. 17A is executed at a predetermined timing, for example, at the timing when the selection operation of the menu icon 110 on the schedule screen 100 is accepted.

The display control unit 50 reads a task whose selected task item is "None" from the menu information 33, and displays an icon 120 indicating the read task in order around the menu icon 110 (S10). ).

The reception unit 51 determines whether or not the selection operation of the icon 120 has been accepted (S11). When the selection operation of the icon 120 is not accepted (S11 negative), the reception unit 51 determines whether or not the selection operation of the main area 102 is accepted (S12). When the selection operation of the main area 102 is accepted (S12 affirmative), the process ends.

On the other hand, when the selection operation of the main area 102 is not accepted (S12 negation), the process proceeds to S11 described above.

On the other hand, when the selection operation of the icon 120 is accepted (S11 affirmative), the reception unit 51 determines whether or not the selected icon 120 is deselected in the main area 102 (S13). When the selected icon 120 is not deselected in the main area 102 (S13 negative), the process proceeds to S11 described above.

On the other hand, when the selected icon 120 is deselected in the main area 102 (S13 affirmative), the reception unit 51 sets the task of the deselected icon 120 as the main task and positions it at the deselected position. The corresponding time is specified as the start time of the main task (S14).

The display control unit 50 displays the sub area 105 in the lower half of the main area 102 (S15). The reception unit 51 determines whether or not the designation of the end time of the main task has been accepted in the sub area 105 (S16). When the designation of the end time is not accepted (S16 negative), the reception unit 51 determines whether or not the selection operation of the main area 102 is accepted (S17). When the selection operation of the main area 102 is accepted (S17 affirmative), the process ends.

On the other hand, when the selection operation of the main area 102 is not accepted (S17 negation), the process proceeds to S16 described above.

On the other hand, when the designation of the end time is accepted (S16 affirmative), the registration unit 52 assigns a unique task ID to the main task and registers the information about the main task in the main schedule information 34 and the task information 36. (S18).

The display control unit 50 reads a task whose main task is a selected task item from the menu information 33, and displays an icon 130 indicating the read task in order around the menu icon 110 (S19). ).

The reception unit 51 determines whether or not the selection operation of the icon 130 has been accepted (S20). When the selection operation of the icon 130 is not accepted (S20 negative), the reception unit 51 determines whether or not the selection operation of the main area 102 is accepted (S21). When the selection operation of the main area 102 is accepted (S21 affirmative), the process ends.

On the other hand, when the selection operation of the main area 102 is not accepted (S21 is denied), the process proceeds to S20 described above.

On the other hand, when the selection operation of the icon 130 is accepted (S20 affirmation), the reception unit 51 determines whether or not the selected icon 130 is deselected in the sub area 105 (S22). If the selected icon 130 is not deselected in the sub-region 105 (S22 negative), the process proceeds to S20 described above.

On the other hand, when the selected icon 130 is deselected in the sub area 105 (S22 affirmative), the registration unit 52 assigns a unique task ID to the task of the icon 130 as a sub task, and assigns a unique task ID to the task of the main task. Information about the sub task is registered in the sub schedule information 35 and the task information 36 in association with the ID (S23), and the process proceeds to S19 described above.

Next, the flow of the display process in which the server device 12 displays the schedule in which the task is registered will be described. FIG. 17B is a flowchart showing the flow of display processing. The display process shown in FIG. 17B is executed at a predetermined timing, for example, at the timing when the selection operation of the main area 102 of the schedule screen 100 is accepted.

The display control unit 50 reads out from the main schedule information 34 the main task whose start date / time or end date / time includes the date in the date area 103 (S50). The display control unit 50 determines whether or not the number of read main tasks is zero (S51). When the number of read main tasks is zero (S51 affirmative), the process ends.

On the other hand, when the number of read main tasks is not zero (S51 negative), the display control unit 50 sets the time range of the main area 102 corresponding to the start date and time and end date and time of the main task for each main task. The bar 140 is displayed on the screen (S52).

The display control unit 50 reads out the sub tasks associated with each main task from the sub schedule information 35 (S53).

The acquisition unit 53 acquires the target number of each main task and the target number of sub-tasks associated with each main task from the task information 36 (S54). The display control unit 50 weights and adds a predetermined number of weights according to the type of task for each main task, and calculates a target value for each main task (S55). The display control unit 50 displays the icon 141 of the main task corresponding to the bar 140 of each main task at a height corresponding to the calculated target value (S56). Further, when there is a sub task associated with the main task, the display control unit 50 displays the icon 142 of the accompanying sub task around the icon 141 of the main task (S57).

The acquisition unit 53 acquires from the comparison result information 37 the number of actual processes to be compared with each main task and the number of actual processes to be compared with the sub tasks associated with each main task ( S58).

The display control unit 50 weights and adds a predetermined weight according to the type of the task for each main task, and calculates the actual value for each main task (S59).

The display control unit 50 displays a line 143 indicating a target value in which the icon 141 of the main task is connected at a height corresponding to the target value (S60). Further, the display control unit 50 displays a line 144 indicating the past achievements connecting the past achievements at the height corresponding to the calculated actual value at the same time position as the icon 141 of the main task (S61). ), End the process. As shown in FIG. 14A, the display control unit 50 may display the target value and the actual value for each main task. Further, as shown in FIG. 14B, the display control unit 50 may display the remaining required values until the target value is reached for each main task.

Next, the flow of the automatic registration process in which the server device 12 automatically registers the task in the schedule will be described. FIG. 17C is a flowchart showing the flow of the automatic registration process. The automatic registration process shown in FIG. 17C is executed at a predetermined timing, for example, at the timing when the selection operation of the simulation icon 113 is accepted.

For each main task registered in the schedule, the registration unit 52 specifies an address where the main task is performed according to the time (S100). The visiting task uses the address where the task is performed as the address of the visited customer. For the main task other than the visit, the address of the place of work where the insurance agent works is the address where the task is performed.

For each main task registered in the schedule, the registration unit 52 determines whether there is a task of moving to the address where the main task is performed before the main task (S101).

The registration unit 52 reads the past schedule of the insurance salesperson of the logged-in user ID from the main schedule information 34, and identifies the behavioral characteristics of the insurance salesperson (S102).

When there is a main task without a move task, the registration unit 52 registers the task of moving to the address where the main task is performed before the main task in the schedule according to the behavioral characteristics of the user ( S103).

The registration unit 52 refers to the automatically added task information 38, and for each registered automatically addable task, within the permissible time zone and other than the time zone corresponding to the task registered in the schedule. It is determined whether or not the time of the time width required by the task that can be automatically added can be secured (S104). When the time width required by the automatically addable task can be secured, the registration unit 52 sets the automatically addable task as the main task in the main schedule information 34 and the task information 36. Register (S105) and end the process.

[effect]
The server device 12 according to the embodiment accepts the selection of the main task from a plurality of types of tasks. The server device 12 accepts the designation of one or more sub-tasks associated with the main task. The server device 12 stores the main task and one or a plurality of sub-tasks in the storage unit 21 as a schedule in association with the designated time according to the time designation in the schedule for the main task. .. As a result, the server device 12 can manage the related tasks in association with each other.

Further, when the server device 12 according to the embodiment displays the schedule to be stored in the storage unit 21, one or a plurality of sub tasks are arranged and displayed around the main task. As a result, the server device 12 can easily grasp and present related tasks.

Further, the server device 12 according to the embodiment displays a character or a mark that can identify the presence or absence of an undisplayed sub-task among one or a plurality of sub-tasks. As a result, the server device 12 can easily grasp and present the presence / absence of undisplayed sub-tasks.

Further, the server device 12 according to the embodiment displays undisplayed sub-tasks by moving the displayed sub-tasks arranged around the main task among one or a plurality of sub-tasks. .. As a result, the server device 12 can display the undisplayed sub-tasks with a simple and easy-to-understand operation.

Further, the server device 12 according to the embodiment accepts the selection of the main task from the plurality of types of tasks. The server device 12 registers one or more customer information as the main task. For example, the server device 12 accepts one or more customers to be processed for the main task registered in the schedule, and registers one or more customers in relation to the main task as shown in FIG. 14F. To do. The server device 12 accepts the designation of one or a plurality of sub tasks to be associated with each of the registered one or a plurality of customer information. The server device 12 sets one or more customer information and one or more sub-tasks associated with each customer information at the specified time, depending on the time specified in the schedule for the main task. It is associated and stored in the storage unit 21 as a schedule. As a result, the server device 12 can manage the related tasks in association with a plurality of customer information.

Although the embodiments relating to the disclosed device have been described so far, the disclosed technique may be implemented in various different forms other than the above-described embodiments. Therefore, other examples included in the present invention will be described below.

For example, in the above embodiment, the case of managing the schedule of the insurance salesperson as a user has been described as an example. However, users are not limited to insurance agents.

Further, in the above embodiment, the case where the flow of time is expressed in the horizontal direction and the schedule expressing the target value of the task and the past actual value is displayed in the vertical direction has been described as an example. However, it is not limited to this. For example, a schedule may be displayed in which the flow of time is expressed in the vertical direction and the target value of the task and the past actual value are expressed in the horizontal direction. In addition, a schedule expressing only one of the task target value and the past actual value may be displayed.

Further, in the above embodiment, the case where the colors of the marks corresponding to the tasks are the same has been described as an example. However, it is not limited to this. For example, the color of the mark corresponding to the task may be changed according to the type of the task. For example, for tasks related to customers such as visits to customers, tasks related to users such as morning assemblies and daily reports, and automatically added tasks, the color of the mark corresponding to the task may be changed.

Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific state of distribution / integration of each device is not limited to the one shown in the figure, and all or part of the device is functionally or physically distributed in arbitrary units according to various loads and usage conditions. It can be integrated and configured. For example, the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 may be integrated or divided as appropriate. Further, the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 may be distributed and executed by a plurality of server devices. Further, the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 are all or any part thereof realized by the CPU and a program that is analyzed and executed by the CPU, or by wired logic. It can be realized as hardware.

[Schedule Management Program]
Further, the various processes described in the above-described embodiment can also be realized by executing a program prepared in advance in a computer system such as a personal computer or a workstation. Therefore, an example of a computer system that executes a program having the same function as that of the above embodiment will be described below. FIG. 18 is a diagram showing a computer that executes a schedule management program.

As shown in FIG. 18, the computer 300 includes a CPU 310, an HDD (Hard Disk Drive) 320, and a RAM (Random Access Memory) 340. Each part of these 310-340 is connected via the bus 400.

The HDD 320 stores in advance a schedule management program 320A that exhibits the same functions as each processing unit of the server device 12 of the above embodiment. For example, the schedule management program 320A that exerts the same functions as the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 of the above embodiment is stored. The schedule management program 320A may be separated as appropriate.

In addition, the HDD 320 stores various data. For example, the HDD 320 stores an OS and various data.

Then, the CPU 310 reads the schedule management program 320A from the HDD 320 and executes it to execute the same operations as the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 of the embodiment. That is, the schedule management program 320A executes the same operations as the display control unit 50, the reception unit 51, the registration unit 52, and the acquisition unit 53 of the embodiment.

The schedule management program 320A described above does not necessarily have to be stored in the HDD 320 from the beginning. For example, a program can be programmed into a "portable physical medium" such as a flexible disk (FD), Compact Disk Read Only Memory (CD-ROM), Digital Versatile Disk (DVD), magneto-optical disk, or IC card inserted into a computer 300. I will remember it. Then, the computer 300 may read the program from these and execute the program.

Further, the program is stored in an "other computer (or server)" connected to the computer 300 via a public line, the Internet, a LAN, a WAN, or the like. Then, the computer 300 may read the program from these and execute the program.

10 Schedule system 11 User terminal 12 Server device 20 Communication unit 21 Storage unit 22 Control unit 30 User information 31 Customer information 32 Telephone contact information 33 Menu information 34 Main schedule information 35 Sub-schedule information 36 Task information 37 Comparison record information 38 Automatic addition task Information 39 Movement information 50 Display control unit 51 Reception unit 52 Registration unit 53 Acquisition unit

Claims (3)

In the schedule management program that manages the schedule
Accepts the selection of the first task from multiple types of tasks,
Register one or more customer information as the first task,
Accepts the designation of one or more tasks to be associated with each of the registered one or more customer information,
According to the time designation in the schedule for the first task, the one or more customer information and the one or more tasks associated with each customer information are associated with the designated time. Stored in the storage unit as the schedule,
A schedule management program characterized by having a computer execute processing. In the schedule management method for managing the schedule,
Accepts the selection of the first task from multiple types of tasks,
Register one or more customer information as the first task,
Accepts the designation of one or more tasks to be associated with each of the registered one or more customer information,
According to the time designation in the schedule for the first task, the one or more customer information and the one or more tasks associated with each customer information are associated with the designated time. Stored in the storage unit as the schedule,
A schedule management method characterized in that processing is performed by a computer. The first reception section that accepts the selection of the first task from multiple types of tasks,
A first registration unit that registers one or more customer information as the first task, and
A second reception unit that accepts the designation of one or more tasks to be associated with each of the registered one or more customer information.
Depending on the time designation in the schedule for the first task, the one or more customer information and the one or more tasks associated with each customer information are associated with the designated time. The second registration unit to be registered in the storage unit as a schedule,
A schedule management device characterized by having.

Images