Information processing program, information processing device, and information processing method

Abstract

To provide an information processing program, information processing device, and information processing method capable of providing a user with support for the execution of multiple tasks.SOLUTION: The information processing program causes a computer to perform processing for: outputting multiple jobs necessary for enterprise management and fees for task management of each job; accepting a selection of job; and displaying and outputting a task list for the job and a calendar in which each task is described after the fee for the accepted job has been settled. Preferably, the information processing program includes: accepting a selection of business type; and displaying and outputting the task list and the calendar based on the business type and the task associated with the job.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an information processing program, an information processing device, and an information processing method that support the execution of multiple tasks. [Background technology]

[0002] Workflow systems and task management systems have been proposed as systems that support work requiring the execution of multiple tasks. For example, Patent Document 1 proposes a multitask management system that supports staff to smoothly handle multiple tasks regardless of their level of proficiency. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7179301 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional task management systems are primarily targeted at repetitive tasks. In addition, it takes time to identify the tasks that make up a task and to implement them in a system. For this reason, conventional task management systems are not suitable for tasks that only need to be done once, such as company establishment, and are not suited to identifying tasks and implementing them in a system.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide an information processing device, an information processing method, and an information processing program that are capable of providing a user with assistance in executing multiple tasks. [Means for solving the problem]

[0006] A computer program according to one embodiment of the present application causes a computer to perform the process of outputting tasks necessary for running a number of businesses and fees for managing the tasks of each task, accepting a selection of a task, and, after payment of the fee for the accepted task, displaying and outputting a list of tasks for the task and a calendar on which each task is described. Effect of the Invention

[0007] In one aspect of the present application, assistance in executing multiple tasks can be provided to a user. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of the configuration of a task management system. [Diagram 2] 2 is a block diagram showing an example of a hardware configuration of a management server; [Diagram 3] FIG. 2 is a block diagram showing an example of a hardware configuration of a user terminal. [Figure 4] 3 is a block diagram showing an example of a hardware configuration of an expert terminal; FIG. [Diagram 5] FIG. 11 is an explanatory diagram showing an example of a user DB. [Figure 6] FIG. 11 is an explanatory diagram showing an example of a user attribute DB; [Figure 7] FIG. 11 is an explanatory diagram showing an example of a ticket DB. [Figure 8] FIG. 13 is an explanatory diagram showing an example of a contract DB. [Figure 9] FIG. 11 is an explanatory diagram illustrating an example of an event DB. [Figure 10] FIG. 11 is an explanatory diagram showing an example of a task basic DB. [Figure 11] FIG. 11 is an explanatory diagram showing an example of a task basic DB. [Figure 12] FIG. 11 is an explanatory diagram illustrating an example of a task execution DB. [Figure 13] FIG. 11 is an explanatory diagram illustrating an example of a task execution DB. [Figure 14] FIG. 2 is an explanatory diagram showing an example of a product DB; [Figure 15] FIG. 13 is an explanatory diagram showing an example of a work-in-progress DB; [Figure 16] 13 is a flowchart showing an example of a procedure for ticket purchasing processing. [Figure 17] 13 is a flowchart illustrating an example of a procedure for displaying task details. [Figure 18] 13 is a flowchart illustrating an example of a procedure for a task completion process. [Figure 19] FIG. 13 is an explanatory diagram showing an example of a ticket purchase screen. [Figure 20] FIG. 4 is an explanatory diagram showing an example of a home screen. [Figure 21] FIG. 13 is an explanatory diagram showing an example of a task details screen. [Figure 22] 13 is a flowchart illustrating an example of a procedure for an event addition process. [Figure 23] 13 is a flowchart illustrating an example of a procedure for a task addition process. [Figure 24] 13 is a flowchart illustrating an example of a procedure for a task editing process. [Diagram 25] FIG. 13 is an explanatory diagram showing an example of an event setting screen. [Figure 26] FIG. 13 is an explanatory diagram showing an example of a task setting screen. [Figure 27] FIG. 13 is an explanatory diagram showing an example of a task setting screen. [Figure 28] 13 is a flowchart illustrating an example of a procedure for a task execution process. [Figure 29] FIG. 13 is an explanatory diagram showing another example of the task details screen. [Diagram 30] FIG. 13 is an explanatory diagram illustrating an example of a contract ticket DB. [Diagram 31] 13 is a flowchart showing an example of a procedure for ticket selection processing. [Diagram 32] 13 is a flowchart illustrating an example of a procedure for a user list display process. [Diagram 33] 13 is a flowchart illustrating an example of a procedure for user management processing. [Diagram 34] FIG. 13 is an explanatory diagram showing an example of a user list screen. [Diagram 35] FIG. 13 is an explanatory diagram showing another example of the user list screen. [Diagram 36]FIG. 13 is an explanatory diagram showing an example of a mail sending screen. [Figure 37] FIG. 11 is an explanatory diagram showing another example of the home screen. [Figure 38] FIG. 13 is an explanatory diagram showing an example of a chat screen. [Figure 39] 13 is a flowchart illustrating an example of a procedure for a task registration process. [Diagram 40] FIG. 13 is an explanatory diagram showing an example of a pop-up screen. [Diagram 41] FIG. 13 is an explanatory diagram showing an example of an event setting screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) An embodiment will be described below with reference to the drawings. FIG. 1 is an explanatory diagram showing an example of the configuration of a task management system. The task management system 100 includes a management server 1, a user terminal 2, and an expert terminal 3. Although one user terminal 2 and one expert terminal 3 are shown, there may be multiple of each. The management server 1, the user terminal 2, and the expert terminal 3 are connected to each other via a network N so as to be able to communicate with each other. In addition, the user terminal 2 and the expert terminal 3 can communicate with multiple cloud services 4, and can receive various services. Note that in this embodiment, the expert terminal 3 is not a required component.

[0010] The management server 1 provides a workflow service. The management server 1 is configured with a server computer, a workstation, a PC (Personal Computer), etc. The management server 1 may also be configured with a multicomputer consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of the management server 1 may be realized by a cloud service.

[0011] 2 is a block diagram showing an example of the hardware configuration of the management server 1. The management server 1 includes a control unit 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a reading unit 15. Each component is connected by a bus B.

[0012] The control unit 11 has one or more arithmetic processing devices such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), a GPU (Graphics Processing Unit), etc. The control unit 11 reads out and executes a control program 1P (information processing program, program product) stored in the auxiliary storage unit 13, thereby realizing a functional unit that performs various information processing, control processing, etc. related to the management server 1.

[0013] The main memory unit 12 is a static random access memory (SRAM), a dynamic random access memory (DRAM), a flash memory, etc. The main memory unit 12 mainly temporarily stores data necessary for the control unit 11 to execute arithmetic processing.

[0014] The auxiliary storage unit 13 is a hard disk or a solid state drive (SSD) or the like, and stores the control program 1P and various DBs (databases) necessary for the control unit 11 to execute processing. The auxiliary storage unit 13 stores a user DB 131, a user attribute DB 132, a ticket DB 133, a contract DB 134, an event DB 135, a basic task DB 136, a task execution DB 137, a product DB 138, a work-in-progress DB 139, and a contract ticket DB 13A. The auxiliary storage unit 13 may be separate from the management server 1 and may be an external storage device connected externally. The various DBs and the like stored in the auxiliary storage unit 13 may be stored in a database server or cloud storage different from the management server 1.

[0015] The communication unit 14 communicates with the user terminal 2, the expert terminal 3, or the cloud service 4 via the network N. In addition, the control unit 11 may use the communication unit 14 to download the control program 1P from another computer via the network N or the like, and store it in the auxiliary storage unit 13.

[0016] The reading unit 15 reads the portable storage medium 1a including a CD (Compact Disc)-ROM and a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 15 and store it in the auxiliary storage unit 13. The control unit 11 may also read the control program 1P from the semiconductor memory 1b.

[0017] The user terminal 2 is a terminal used by an end user. The user terminal 2 is configured as a desktop PC (Personal Computer), a notebook PC, a tablet computer, a smartphone, or the like. The end user uses the task management system 100 to execute a job configured of multiple tasks. In the following description, a job is referred to as an event.

[0018] 3 is a block diagram showing an example of the hardware configuration of a user terminal 2. The user terminal 2 includes a control unit 21, a main memory unit 22, an auxiliary memory unit 23, a communication unit 24, an input unit 25, and a display unit 26. Each component is connected by a bus B.

[0019] The control unit 21 has one or more arithmetic processing devices such as a CPU, an MPU, a GPU, etc. The control unit 21 provides various functions by reading and executing a control program 2P (program, program product) stored in the auxiliary storage unit 23.

[0020] The main memory unit 22 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 22 mainly temporarily stores data necessary for the control unit 21 to execute arithmetic processing.

[0021] The auxiliary storage unit 23 is a hard disk or an SSD, etc., and stores various data necessary for the control unit 21 to execute processing. The auxiliary storage unit 23 may be an external storage device that is separate from the user terminal 2 and externally connected. The various DBs, etc. stored in the auxiliary storage unit 23 may be stored in a database server or cloud storage.

[0022] The communication unit 24 communicates with the management server 1 and the cloud service 4 via the network N. In addition, the control unit 21 may use the communication unit 24 to download the control program 2P from another computer via the network N or the like, and store it in the auxiliary storage unit 23.

[0023] The input unit 25 is a keyboard, a mouse, a trackpad, or the like. The display unit 26 includes a liquid crystal display panel, an organic EL (electroluminescence) display panel, or the like. The display unit 26 displays a home screen or the like output by the management server 1. The input unit 25 and the display unit 26 may be integrated to configure a touch panel display. The user terminal 2 may display on an external display device such as a display.

[0024] The expert terminal 3 is a terminal used by an expert who supports or acts on behalf of an end user in performing his / her tasks. The expert terminal 3 is composed of a desktop PC, a notebook PC, a tablet computer, a smartphone, etc. By having the end user use the task management system 100, the expert has the end user perform routine tasks as autonomously as possible, and provides support only for matters that truly require the support of an expert. The expert also checks the progress of the end user's tasks using the task management system 100, and provides support as necessary.

[0025] 4 is a block diagram showing an example of the hardware configuration of the expert terminal. The expert terminal 3 includes a control unit 31, a main memory unit 32, an auxiliary memory unit 33, a communication unit 34, an input unit 35, and a display unit 36. Each component is connected by a bus B. The control unit 31, the main memory unit 32, the auxiliary memory unit 33, the communication unit 34, the input unit 35, and the display unit 36 ​​are similar to the control unit 21, the main memory unit 22, the auxiliary memory unit 23, the communication unit 24, the input unit 25, and the display unit 26 of the user terminal 2, respectively, and therefore description thereof will be omitted. Note that, for the basic functions described first, the expert terminal 3 is not a required component.

[0026] Next, the database used in the task management system 100 will be described. FIG. 5 is an explanatory diagram showing an example of a user DB. The user DB 131 stores static information of users. The user DB 131 includes a user ID column, a name column, a type column, an email column, a corporate form column, a postal code column, a head office location / tax payment location column, a type of business column, a capital amount column, a number of employees column, a business stage column, a start-up date column, and a name column. The user ID column stores a user ID that can uniquely identify a user. The name column stores the name of the user. The name is a company name, a trade name, a pen name, etc. The type column stores the type of the user. For example, the types are general, specialist, etc. General users are users who mainly use the task management system 100 themselves. Specialists are users who mainly allow their customers to use the task management system 100. The email column stores the contact email address of the user. The corporate form column stores the corporate form of the user. For example, 1 indicates a joint stock company. 2 indicates a limited liability company. 3 indicates a general partnership company. 4 indicates a limited partnership. 5 indicates an auditing firm. If the user is a sole proprietor or the like and does not have corporate status, the corporate form column stores 0. The postal code column stores the postal code of the user's head office location, etc. The head office location / tax place column stores the user's head office location and tax place. The industry column stores the user's industry. For example, the Japan Standard Industrial Classification is used for the industry. 3921 shown in FIG. 5 indicates the information processing service industry. The capital amount column stores a value indicating the user's capital amount in a class. The number of employees column stores a value indicating the number of employees, etc. of the user in a class. The business stage column stores a stage indicating the growth stage when the user is mainly a venture company. For example, there are four stages: seed, early, middle, and later. The opening date column stores the date the user opened the business or the date the user plans to open the business. The name column stores the name of the contact person regarding the use of the task management system 100.

[0027] FIG. 6 is an explanatory diagram showing an example of a user attribute DB. The user attribute DB 132 stores information other than the user information stored in the user DB 131. The user attribute DB 132 includes a user ID column, a usage start date and time column, a last login column, a settlement start column, and a settlement end column. The user ID column stores a user ID. The usage start date and time column stores the date and time when the user started using the task management system 100. The last login column stores the date and time when the user last logged in to the task management system 100. The settlement start column stores the start date of the settlement period when the user first performed settlement. The settlement end column stores the end date of the settlement period when the user last performed settlement.

[0028] FIG. 7 is an explanatory diagram showing an example of a ticket DB. The ticket DB 133 stores ticket information that embodies the usage authority of the task management system 100. The ticket DB 133 includes a ticket ID column, a name column, and a fee column. The ticket ID column stores a ticket ID that can uniquely identify a ticket. The name column stores the name of the ticket. The fee column stores the fee of the ticket. This embodiment assumes a subscription service in which a fee is collected monthly during the usage period. The fee stored in the fee column is a monthly fee.

[0029] FIG. 8 is an explanatory diagram showing an example of a contract DB. The contract DB 134 stores ticket purchase information. The contract DB 134 includes a user ID column, a ticket ID column, a self / other column, a proxy ID column, a purchase date column, and a status column. The user ID column stores the user ID of the user who purchases the ticket. The ticket ID column stores the ticket ID of the purchased ticket. The self / other column stores whether the user purchased the ticket directly or from another company. If the ticket was purchased directly, the self / other column stores "our company". If the ticket was purchased from another company, the self / other column stores "other company". The proxy ID column stores the user ID of the user who sold the ticket for tickets purchased from another company. Here, it is assumed that the ticket is mainly sold by an expert, and the user ID is the expert's ID (administrator ID). The purchase date column stores the date the ticket was purchased. The status column stores the status of the ticket. If the monthly fee for the purchased ticket has been paid and the ticket is valid, the status column stores "under contract". If the ticket has been used, the status column stores "Used."

[0030] FIG. 9 is an explanatory diagram showing an example of the event DB. The event DB 135 stores information about events (jobs). The event DB 135 includes an ID column, an event column, a task ID column, a required ticket column, an industry column, and a next event column. The ID column stores an ID that can uniquely identify an event. The event column stores the classification of the event. The event column further includes a large column, a medium column, and a small column. The large column stores the large classification of the event. The medium column stores the medium classification of the event. The small column stores the small classification of the event. The task ID column stores the task ID of the task that constitutes the event. The required ticket column stores the ticket ID of the ticket that needs to be purchased in order to manage the execution of the event in the task management system 100. The industry column stores the industry to which the definition of the event is applicable. This is because even for the same event, the tasks that constitute it may differ depending on the industry. The industry column further includes a large column, a medium column, and a small column. The large column stores the large classification of the industry. The medium column stores the medium classification of the industry. The small column stores the subcategory of the industry. For example, the industry uses the Japan Industrial Classification. In the Japan Industrial Classification, the major categories are A to S. Major category G is the information and communications industry. Medium categories linked to major category G include communications, broadcasting, and information services. Subcategories linked to the information services industry include information processing services, information provision services, market research, opinion polls, and social research, and other information processing and provision services. The next event column stores the ID of the next event that is recommended to be executed.

[0031] 10 and 11 are explanatory diagrams showing an example of the task basic DB. The task basic DB 136 stores information about tasks. The task basic DB 136 includes a task ID column, a task name column, a start column, a deadline column, a previous business day column, a description column, a "must" column, and an industry ID column. The task ID column stores a task ID that can uniquely identify a task. The task name column stores the name of the task. The start column stores the start date when calculating the deadline for completing a task. The start column further includes a base date column and a before / after column. The base date column stores the base date. The founding date is the founding date of the company. The occurrence date is the date on which the event occurred. Monthly only indicates that it is monthly, and the date is determined by the value in the deadline column. The before / after column stores whether the deadline is before or after the start date. + indicates that the deadline is after the start date. - indicates that the deadline is before the start date. The deadline column stores the number of days from the base date to the deadline. In addition, if the base date = every month, the value in the deadline column indicates the date of each month. A deadline column = 5 indicates that the deadline is the 5th of each month. A value of 0 in the deadline column indicates the end of the month. The previous business day column stores whether to move the deadline forward to the previous business day if the calculated deadline falls on a holiday or national holiday. A black circle indicates that the deadline must be moved forward, a blank space indicates that it is not necessary and that the deadline can be moved forward to the next business day. In the example of Figure 10, for task ID = 100010001, task name = registering the representative's official seal and obtaining a seal certificate, the base date = founding date, before or after = -, deadline = 30, previous business day = black circle. This indicates that the task of registering the representative's official seal and obtaining a seal certificate should be completed 30 days before the founding date, and if the deadline falls on a holiday or national holiday, it should be moved forward to the previous business day.

[0032] The description column stores the description of the task. The description column further indicates a summary column and a detail column. The summary column stores a summary of the description. The detail column stores the details of the description. The must column indicates whether or not the task must be performed. A black circle indicates that it is required. A space indicates that it does not have to be performed depending on the user's circumstances. The industry ID column stores an ID that specifies the industry to which the task applies. Even if it is the same task, if the content differs depending on the industry, or if the task is only required in that industry, the industry ID column indicates the target industry. The industry ID column further includes a large column, a medium column, and a small column. The large column stores IDs that indicate large categories. The medium column stores IDs that indicate medium categories. The small column stores IDs that indicate small categories. When using the Japanese Industry Classification as the classification, the large column = M, the medium column = 75, and the small column = 764 respectively indicate accommodation, food service, restaurants, and sushi restaurants.

[0033] 12 and 13 are explanatory diagrams showing examples of the task execution DB. The task execution DB 137 stores specific procedures for executing a task. The task execution DB 137 includes a task ID column, a notification destination column, a necessary item column, a procedure 1 column, a procedure 2 column, a procedure 3 column, a procedure 4 column, a procedure 5 column, a supplementary column, and a template column. The task ID column stores a task ID. The notification destination column stores a destination to which a document is to be notified. The necessary item column stores items required for executing a task. The procedure 1 column to the procedure 5 column store execution procedures. If the number of steps does not fit within five, the contents of each step may be increased, but it is preferable to divide each step into two tasks with five or less steps. The supplementary column stores supplementary explanations about the task execution. If a template (document template) for the document to be created is prepared, the information on the template is stored in the template column. The template column further stores a name column and a number column. The name column stores the name of the template. The number column stores the number of the template.

[0034] FIG. 14 is an explanatory diagram showing an example of a product DB. When executing a task, product DB 138 stores information on products recommended for purchase or services recommended for use. Product DB 138 includes a task ID column, a number column, a category column, a name column, a logo column, and a URL column. The task ID column stores the task ID of the corresponding task. The number column stores a sequence number. When multiple products are recommended, they are displayed according to the sequence number. The category column stores the category of the product. The name column stores the name of the product. The logo column stores a logo image of the product as binary data. The logo image may be stored as a file in auxiliary storage unit 13, and the image file name may be stored in the logo column. The URL column stores URLs (Uniform Resource Locators) such as a homepage introducing the product or a homepage of the product provider.

[0035] FIG. 15 is an explanatory diagram showing an example of an in-progress DB. The in-progress DB 139 stores the status of each task that constitutes an ongoing event. The in-progress DB 139 includes a user ID column, an event ID column, a task ID column, a deadline column, a status column, and an expert ID column. The user ID column stores the user ID of the user who will perform the task. The event ID column stores the event ID of the event corresponding to the task. The task ID column stores the task ID. The deadline column stores the deadline for executing the task. The status column stores the status of the task. The status may be not started, in progress, completed, etc. The expert ID column stores the expert ID of the expert when the user purchases a ticket through or after being introduced by an expert in order to use the task management system 100 to manage the progress of the event.

[0036] Next, the information processing performed by the task management system 100 will be described. An end user who is going to use the task management system 100 for the first time needs to register as a user. The user registration process is a general process, so the description will be omitted. The user registration process adds records to the user DB 131 and the user attribute DB 132.

[0037] FIG. 16 is a flowchart showing an example of a procedure for ticket purchase processing. The user operates the user terminal 2 to select ticket purchase. The control unit 21 of the user terminal 2 transmits a request to the management server 1 (step S1). The control unit 11 of the management server 1 receives the request (step S2). The control unit 11 transmits a ticket purchase screen to the user terminal 2 (step S3). The control unit 21 of the user terminal 2 receives the ticket purchase screen and displays it on the display unit 26 (step S4). The user selects a ticket to be purchased. The control unit 21 accepts the selection (step S5). The control unit 21 transmits the selection to the management server 1 (step S6). The control unit 11 of the management server 1 receives the selection (step S7). The control unit 11 cooperates with the user terminal 2 and the payment service to perform a payment process for the ticket price (step S8). The control unit 11 determines whether or not the payment has been successful (step S9). When the control unit 11 determines that the payment is successful (YES in step S9), it creates a task list for the event corresponding to the purchased ticket (step S10). The control unit 11 searches the event DB 135 using the ticket ID of the purchased ticket as a search key, and acquires the corresponding event and the tasks that constitute the event. The control unit 11 stores the task list in the in-progress DB 139 and the information of the purchased ticket in the contract DB 134 (step S11). The control unit 11 creates a home screen and transmits it to the user terminal 2 (step S12). The control unit 21 of the user terminal 2 receives the home screen, displays it on the display unit 26 (step S13), and ends the process. When the control unit 11 determines that the payment is unsuccessful (NO in step S9), it transmits an error screen to the user terminal 2 (step S14). The control unit 21 of the user terminal 2 receives the error screen, and displays it on the display unit 26 (step S15). The control unit 21 ends the ticket purchase process.

[0038] FIG. 17 is a flowchart showing an example of the procedure of the task details display process. The user selects one of the tasks displayed on the home screen by the input unit 25. The control unit 21 of the user terminal 2 transmits the task ID of the selected task to the management server 1 (step S31). The control unit 11 of the management server 1 receives the task ID (step S32). The control unit 11 searches the task basic DB 136, the task execution DB 137, and the in-progress DB 139 using the task ID as a search key, and acquires data related to the task (step S33). The control unit 11 creates a task details screen with the acquired data embedded therein, and transmits it to the user terminal 2 (step S34). The control unit 21 of the user terminal 2 receives the task details screen, and displays it on the display unit 26 (step S35). The control unit 21 ends the process.

[0039] FIG. 18 is a flowchart showing an example of a procedure for task completion processing. The user inputs completion of a task through the input unit 25 on the home screen or task details screen. The control unit 21 of the user terminal 2 transmits the task ID of the task for which completion has been input and the screen ID of the screen on which the completion has been input to the management server 1 (step S41). The control unit 11 of the management server 1 receives the task ID and the screen ID (step S42). There may be a case where a plurality of task IDs are transmitted and received. The control unit 11 searches the in-progress DB 139 using the task ID as a search key, and updates the value of the status column of the hit record to completion (step S43). The control unit 11 creates a screen with the updated status, and transmits it to the user terminal 2 (step S44). At this time, the control unit 11 determines the screen to be created based on the received screen ID. The control unit 21 of the user terminal 2 receives the screen, and displays it on the display unit 26 (step S45). The control unit 21 ends the process.

[0040] Next, an example of a screen displayed on the user terminal 2 will be described. FIG. 19 is an explanatory diagram showing an example of a ticket purchase screen. The ticket purchase screen d01 includes an industry selection area d011, a required ticket area d012, a selected ticket area d013, an amount display area d014, and a payment button d015. The industry selection area d011 is a field for selecting the user's industry. The required ticket area d012 displays tickets that the user must purchase in order to use the task management system 100. Since the purchase is required, the check box displays a check in the selected state, and the user cannot uncheck it. The selected ticket area d013 displays tickets that the user can purchase at will. By checking the check box, the ticket can be made a purchase target. The amount display area d014 displays the amount to be paid by the user. As shown in FIG. 19, not only the total amount but also the amount for each ticket may be displayed. In addition, if a discount is applied, the discount amount may be displayed. As described above, since the task management system 100 is assumed to be a subscription service, the amount displayed in FIG. 19 is a monthly fee. When the payment button d015 is selected, the payment process begins.

[0041] FIG. 20 is an explanatory diagram showing an example of a home screen. The home screen d02 includes a task list d021 and a calendar d022. The task list d021 displays tasks that constitute an event. Each task is displayed in a different manner depending on the state. Four display modes are shown here. The task d0211 is an incomplete task that has been completed for more than two weeks since the deadline. The characters indicating the task name are bold and underlined. The task d0212 is an incomplete task that has been completed for less than two weeks since the deadline. The characters indicating the task name are bold. The task d0213 is an incomplete task whose completion deadline is in the future. The characters indicating the task name are in the normal manner. The task d0214 is a completed task that has already been completed. The characters indicating the task name are struck through and marked as completed. The calendar d022 displays each task on its due date. As with the task list d021, the tasks are displayed in a different manner depending on the state.

[0042] FIG. 21 is an explanatory diagram showing an example of a task details screen. The task details screen d03 includes a name display d031, a notification destination display d032, an event display d033, a download button d034, a summary column d035, a details column d036, a progress display column d037, a progress display bar d038, a necessary item column d039, a procedure column d03A, a supplement column d03B, a recommended service column d03C, a memo column d03D, a back button d03E, a completion button d03F, and an update button d03G. The name display d031 displays the name of the task. The notification destination display d032 displays the document to be notified. If there is no notification destination, it is blank or not displayed. The event display d033 displays the event corresponding to the task. When the download button d034 is selected, the format of the document to be created can be downloaded. The summary column d035 displays a summary explanation of the task. The details column d036 displays a detailed explanation of the task. The progress display field d037 displays the progress of the event. Here, it shows that two of the six tasks have been completed. The progress display bar d038 shows the progress of the event with a progress bar. The required items field d039 displays the items required to complete the task. The procedure field d03A displays the procedure for performing the task. The supplementary field d03B displays supplementary explanations. The recommended services field d03C displays services that can be used to perform the task. The memo field d03D is a field where the user can enter memos. Selecting the back button d03E returns to the previous screen. Selecting the complete button d03F stores the completion of the task. Selecting the update button d03G stores the content entered in the memo field d03D.

[0043] The present embodiment has the following effects. A user can receive support for the execution of multiple tasks from the task management system 100 by simply paying a ticket fee for the business (event) for which support is desired. The task management system 100 stores the event (business) and multiple tasks that constitute the event. Therefore, the task management system 100 can support the execution of the event without identifying the tasks that constitute the business and implementing the system. The task management system 100 stores the standard number of days from a reference date for each task. The task management system 100 displays a list of multiple tasks to be performed to complete an event. Even if a user does not have detailed knowledge about the event, the user can complete the event by completing each task. In addition, the standard completion date of each task is displayed on a calendar so that the user can understand the execution order and deadline of the tasks before executing the tasks. When the event is a business related to business management, the use of the task management system 100 is meaningful.

[0044] (Customization feature) The customization function is a function provided to a system administrator or a user who is familiar with events. As an example of the customization function, adding an event, adding a task, and editing / deleting a task will be described below. FIG. 22 is a flowchart showing an example of the procedure of an event addition process. For a user who is permitted to use the customization function, an operation menu for adding / editing an event or a task is provided. The user selects adding an event from the operation menu. The control unit 21 of the user terminal 2 transmits a request to add an event to the management server 1 (step S51). The control unit 11 of the management server 1 receives the request (step S52). The control unit 11 transmits a setting screen to the user terminal 2 (step S53). The control unit 21 of the user terminal 2 receives the setting screen and displays it on the display unit 26 (step S54). The user inputs information of the event to be added into the setting screen. The control unit 21 accepts the input (step S55). The user performs the next operation such as a registration instruction. The control unit 21 accepts the operation (step S56). The control unit 21 judges whether the received operation is registration or not (step S57). When the control unit 21 judges that the received operation is registration (YES in step S57), it transmits information of the event to be added input by the user to the management server 1 (step S58). The control unit 11 of the management server 1 receives the information of the event to be added (step S59). The control unit 11 stores the received content in the event DB 135 (step S60). The control unit 11 transmits a completion screen to the user terminal 2 (step S61). The control unit 21 of the user terminal 2 receives the completion screen and displays it on the display unit 26 (step S62). The control unit 21 ends the process. When the control unit 21 judges that the received operation is not registration (NO in step S57), it displays the home screen (step S63) and ends the process.

[0045] FIG. 23 is a flowchart showing an example of a procedure of a task addition process. A user selects adding a task from an operation menu. The control unit 21 of the user terminal 2 transmits a request to add a task to the management server 1 (step S71). The control unit 11 of the management server 1 receives the request (step S72). The control unit 11 transmits a list screen of events to the user terminal 2 (step S73). Events included in the list screen are events added by the user or events that the user is permitted to edit. The control unit 21 of the user terminal 2 receives the list screen and displays it on the display unit 26 (step S74). The user selects an event to which a task is to be added from the list screen. The control unit 21 transmits the event ID of the event selected by the user to the management server 1 (step S75). The control unit 11 of the management server 1 receives the event ID (step S76). The control unit 11 transmits a setting screen to the user terminal 2 (step S77). A setting screen may be prepared for each event classification, and the control unit 11 transmits a setting screen according to the selected event classification. The control unit 21 of the user terminal 2 receives the setting screen and displays it on the display unit 26 (step S78). The user inputs task information on the setting screen. The control unit 21 accepts the input (step S79). The user performs the next operation, such as a registration instruction. The control unit 21 accepts the operation (step S80). The control unit 21 judges whether the accepted operation is registration or not (step S81). If the control unit 21 judges that the accepted operation is registration (YES in step S81), it transmits information on the task to be added input by the user to the management server 1 (step S82). The control unit 11 of the management server 1 receives the information on the task to be added (step S83). The control unit 11 stores the received contents in the task basic DB 136 and the task execution DB 137, and also stores information on the task added to the event DB 135 (step S84). The control unit 11 transmits a completion screen to the user terminal 2 (step S85). The control unit 21 of the user terminal 2 receives the completion screen and displays it on the display unit 26 (step S86). The control unit 21 ends the process. If the control unit 21 determines that the accepted operation is not registration (NO in step S81), it displays the home screen (step S87) and ends the process.

[0046] FIG. 24 is a flowchart showing an example of a procedure for editing a task. A user selects editing or deleting a task from an operation menu. The control unit 21 of the user terminal 2 transmits a request to edit or delete a task to the management server 1 (step S101). The control unit 11 of the management server 1 receives the request (step S102). The control unit 11 transmits a list screen of events to the user terminal 2 (step S103). Events included in the list screen are events added by the user or events that the user is permitted to edit. The control unit 21 of the user terminal 2 receives the list screen and displays it on the display unit 26 (step S104). The user selects an event to which a task is to be added from the list screen. The control unit 21 transmits the event ID of the event selected by the user to the management server 1 (step S105). The control unit 11 of the management server 1 receives the event ID (step S106). The control unit 11 creates a list screen of tasks that constitute the specified event and transmits it to the user terminal 2 (step S107). The control unit 21 of the user terminal 2 receives the list screen and displays it on the display unit 26 (step S108). The user selects a task to be edited on the list screen. The control unit 21 accepts the selection (step S109). The control unit 21 transmits the task ID of the task selected by the user to the management server 1 (step S110). The control unit 11 of the management server 1 receives the task ID (step S111). The control unit 11 creates an operation screen and transmits it to the user terminal 2 (step S112). The control unit 21 of the user terminal 2 receives the operation screen and displays it on the display unit 26 (step S113). When updating a task, the user updates the contents of the task on the operation screen and selects a registration button or the like. When deleting a task, the user selects a delete button on the operation screen. The control unit 21 transmits a command corresponding to the selected button to the management server 1 (step S114). The control unit 11 of the management server 1 receives the command (step S115). The control unit 11 determines whether the received command is an update command (step S116). If the control unit 11 determines that the received command is an update command (YES in step S116), the control unit 11 stores information on the updated task received from the user terminal 2 in the task basic DB 136 and the task execution DB 137 (step S117).When the control unit 11 determines that the received command is not an update command (NO in step S116), it deletes the task (step S118). The control unit 11 deletes the task from the task basic DB 136 and the task execution DB 137, and also deletes the record of the task from the event DB 135. The control unit 11 sends a completion screen to the user terminal 2 (step S119). The control unit 21 of the user terminal 2 receives the completion screen and displays it on the display unit 26 (step S120). The control unit 21 ends the process.

[0047] FIG. 25 is an explanatory diagram showing an example of an event setting screen. The event setting screen d04 is a setting screen for adding an event. The event setting screen d04 includes an occurrence date field d041, a main item menu d042, a medium item menu d043, a small item menu d044, a memo field d045, a registration button d046, and a back button d047. The occurrence date field d041 is a field for inputting the date on which the event occurred or the date on which it is scheduled to occur. If the date is not fixed, no input is required. The main item menu d042 is a pull-down menu for setting the main category of the event. The medium item menu d043 is a pull-down menu for setting the medium category of the event. The small item menu d044 is a pull-down menu for setting the small category of the event. The memo field d045 is a field for inputting an explanation of the event or supplementary information. When the registration button d046 is selected, the setting contents are sent to the management server 1. When the back button d047 is selected, the setting contents are discarded and the screen returns to the home screen.

[0048] 26 and 27 are explanatory diagrams showing examples of task setting screens. The task setting screen d05 is a setting screen (business editing screen) for adding a task. The task setting screen d05 includes a task name field d051, a must box d052, a deadline field d053, a submission destination field d054, a description field d055, a required item field d056, a procedure field d057, a supplementary field d058, an upload field d059, a registration button d05A, and a cancel button d05B. The task name field d051 is a field for inputting the name of the task. The must box d052 is checked when the task must be executed. The deadline field d053 is a field for setting the completion deadline of the task. When the completion deadline is determined based on the event occurrence date or the scheduled event occurrence date, the user sets whether the deadline is before or after the standard, and inputs the number of days from the standard date. When the task is performed monthly, the date is set on the calendar. When it is the last day, the radio button associated with the last day is selected. The submission destination field d054 is a field for inputting the submission destination for tasks that require the submission of documents. The explanation field d055 is a field for inputting an explanation of the task. The explanation field d055 has a field for inputting a summary and a field for inputting a detailed explanation. The necessary items field d056 is a field for inputting items required to perform the task. The procedure field d057 is a field for inputting an explanation of the order in which the tasks will be performed. The supplementary field d058 is a field for inputting supplementary explanations about the task. The upload field d059 is a field for setting the file to be uploaded when uploading forms for documents to be created, etc. When the registration button d05A is selected, the set contents are sent to the management server 1. When the cancel button d05B is selected, the set contents are ignored and the screen returns to the home screen.

[0049] The task editing screen for updating and deleting existing tasks is almost the same as the task setting screen d05, so a description will be omitted. The task editing screen displays the contents of the selected task in a layout similar to that of the task setting screen d05. The user edits the parts where they wish to make changes. When the Update button displayed in place of the Register button d05A is selected, the updated contents are sent to the management server 1. The task editing screen also displays a Delete button, which is not present on the task setting screen d05, and when the Delete button is selected, the displayed task is deleted.

[0050] The customization function makes it possible to add events and tasks, and edit and delete tasks. When events and tasks added by a user, and edited and deleted tasks are stored in the event DB 135, basic task DB 136, and task execution DB 137 common to all users, it is desirable to attach the user ID of the target user to each record. This is to prevent events and tasks unique to a user from affecting the use of other users. Alternatively, a database dedicated to the user may be set up, and events and tasks added by the user may be stored in that database.

[0051] (API integration) API (Application Programming Interface) linkage will be described. When a task is repeated periodically, such as a monthly task, and the content of the task can be performed by a cloud service 4 intended for business support, it is efficient to instruct the task management system 100 to execute the task and receive a notification of completion of the execution. The cloud service 4 is, for example, a communication tool or a SaaS (Software as a Service) that provides services related to accounting, labor, SFA (Sales Force Automation), and CRM (Customer Relationship Management).

[0052] FIG. 28 is a flowchart showing an example of a procedure of a task execution process. The user selects a task to be executed on the home screen displayed on the display unit 26 of the user terminal 2. The control unit 21 of the user terminal 2 accepts the selection (step S141). The control unit 21 transmits the task ID of the selected task to the management server 1 (step S142). The control unit 11 of the management server 1 receives the task ID (step S143). The control unit 11 creates a task details screen and transmits it to the user terminal 2 (step S144). The control unit 21 of the user terminal 2 receives and displays the task details screen (step S145). On the task details screen, the user selects a link for executing a task by the business support system. The control unit 21 of the user terminal 2 transmits an execution request to the management server 1 (step S146). The control unit 11 of the management server 1 receives the execution request (step S147). The control unit 11 transmits an execution request for the corresponding task to the cloud service 4 (step S148). The execution request is a request by a Web API. The cloud service 4 receives the request (step S149). The cloud service 4 executes processing in accordance with the request (step S150). The business support system transmits the completion to the management server 1 as a response to the request (step S151). The control unit 11 of the management server 1 receives the completion, and stores the completion of the task in the in-progress DB 139 (step S152). The control unit 11 transmits a completion screen to the user terminal 2 (step S153). The control unit 21 of the user terminal 2 receives the completion screen (step S154). The control unit 21 displays the completion screen on the display unit 26 (step S155), and ends the process.

[0053] FIG. 29 is an explanatory diagram showing another example of the task details screen. The task details screen d06 (task display screen) includes a task name field d061, a summary field d062, a details field d063, a hyperlink d064, a memo field d065, a completion button d066, an update button d067, and a back button d068. The task name field d061 displays the task name. The summary field d062 displays a summary explanation of the task. The details field d063 displays a detailed explanation of the task, an execution procedure, and the like. The hyperlink d064 is a hyperlink for executing the task. When the hyperlink d064 is selected, a request for payroll calculation and creation of a payroll ledger is sent to the cloud-based payroll calculation system. When the cloud-based payroll calculation system performs payroll calculation and creates a payroll ledger, this task is completed, and a completion screen is displayed. The hyperlink d064 is displayed when the user has concluded a service contract with an appropriate cloud service 4 corresponding to the task and has completed the link setting with the task management system 100. The memo field d065 is a field for the user to enter memos. When the completion button d066 is selected, completion of the task is sent to the management server 1. When the update button d067 is selected, the updated contents are sent to the management server 1. When the back button d068 is selected, the user returns to the previously displayed screen.

[0054] The API linking function enables a user to execute a task using the cloud service 4 via the task management system 100. When a task is completed by the cloud service 4, this is reflected in the task management system 100, making it possible to omit the completion operation.

[0055] (Embodiment 2) This embodiment relates to a form in which an expert who provides business support, such as a professional or consultant, has a client use task management system 100, thereby entrusting part of the support business to the system. Specifically, the expert provides a ticket for task management system 100 to the client, thereby causing the client to use task management system 100. The expert refers to the progress of tasks for the client using task management system 100, and provides advice, etc., as necessary.

[0056] FIG. 30 is an explanatory diagram showing an example of a contract ticket DB. The contract ticket DB 13A stores information on tickets that experts allow customers to use. The contract ticket DB 13A includes user ID and ticket ID columns. The user ID column stores the user ID assigned to the expert. The ticket ID column stores the ticket ID of the ticket (usage ticket) that the expert allows the customer to use. The fee per ticket may be stored in the contract ticket DB 13A. It is assumed that the ticket fee is paid by the expert. The expert may collect the ticket fee from the customer, or may collect it by including it in the consulting fee, etc. A volume discount may also be applied to the ticket fee.

[0057] FIG. 31 is a flowchart showing an example of the procedure of the ticket selection process. The ticket selection process is a process performed when a customer who is encouraged by an expert to use the task management system 100 starts using the task management system 100. It is assumed that the customer has completed user registration before performing the ticket selection process. The customer corresponds to the user in the first embodiment, and is hereinafter referred to as the user. The user operates the user terminal 2 to input the expert ID and make a display request for tickets recommended by the expert. The control unit 21 of the user terminal 2 transmits a ticket display request to the management server 1 (step S171). At this time, the user may be made to input an introduction code transmitted from the expert, and the request may be transmitted to the management server 1. The introduction code is issued in advance by the task management system 100. The expert code and the introduction code are used to prevent unauthorized access. The control unit 11 of the management server 1 receives the request (step S172). The control unit 11 creates a ticket selection screen (acquisition screen) and transmits it to the user terminal 2 (step S173). When creating the ticket selection screen, the control unit 11 searches the contract ticket DB 13A using the received expert ID as a search key, and acquires the ticket ID of the ticket recommended by the expert. The acquired ticket ID is used as a search key to search the ticket DB 133, and acquires ticket information. The control unit 11 generates a ticket selection screen in which the acquired ticket information is embedded. The control unit 21 of the user terminal 2 receives the selection screen, and displays it on the display unit 26 (step S174). The user refers to the selection screen, and selects and inputs the ticket to be used. Note that tickets that the expert forces to be used may be in a selected state, and an unselection operation may not be possible. The control unit 21 accepts the selection (step S175). The control unit 21 transmits the selection result to the management server 1 (step S176). The control unit 21 receives the selection result (step S177). The control unit 21 creates a notification to the expert, and transmits it to the expert terminal 3 (step S178). The control unit 31 of the expert terminal 3 receives the notification, and displays it on the display unit 36 ​​(step S179). The expert refers to the notification, checks the ticket selected by the user (customer), and inputs the result of the decision as to whether or not to approve the use. The control unit 31 transmits the result to the management server 1 (step S180). The control unit 11 of the management server 1 receives the result (step S181).The control unit 11 judges whether the result is approval or not (step S182). When the control unit 11 judges that the result is approval (YES in step S182), it creates a task list corresponding to the selected ticket (step S183). This process is the same as step S10 in FIG. 16. The control unit 11 stores the task list in the in-progress DB 139 and the information of the selected ticket in the contract DB 134 (step S184). The control unit 11 creates a home screen and transmits it to the user terminal 2 (step S185). The control unit 21 of the user terminal 2 receives the home screen and displays it on the display unit 26 (step S186). When the control unit 11 judges that the result is not approval (NO in step S182), it creates a notification screen to the effect that approval was not granted and transmits it to the user terminal 2 (step S187). The control unit 21 of the user terminal 2 receives the notification screen and displays it on the display unit 26 (step S188). The control unit 21 ends the ticket selection process. If approval by an expert is not required for the selection of tickets, step S183 may be executed after step S177.

[0058] FIG. 32 is a flowchart showing an example of the procedure of the user list display process. The user list display process is a process used by an expert. The expert operates the expert terminal 3 and selects user list display from the menu. The control unit 31 transmits a display request to the management server 1 (step S201). The control unit 11 of the management server 1 receives the request (step S202). The control unit 11 creates a user list and transmits it to the expert terminal 3 (step S203). The control unit 11 uses the expert ID as a search key to search the contract DB 134 and acquires the user ID of the user who is the expert's customer. The control unit 11 uses the acquired user ID as a search key to search the user DB 131 and acquires user information. The control unit 11 creates a user list from the acquired user information. The control unit 31 of the expert terminal 3 receives the user list and displays it on the display unit 36 ​​(step S204). The control unit 31 ends the process.

[0059] FIG. 33 is a flowchart showing an example of the procedure of the user management process. The user management process is executed when an expert performs an operation on the user list. The expert performs an operation on the user list. The control unit 31 of the expert terminal 3 accepts the operation (step S211). The control unit 31 judges whether the accepted operation is "open" or not (step S212). The "open" operation is an operation for displaying a list of tasks of the user. When the control unit 31 judges that the accepted operation is "open" (YES in step S212), it displays a list of tasks of the selected user (step S213). The control unit 31 returns the process to step S211. When the control unit 31 judges that the accepted operation is not "open" (NO in step S212), it judges whether the operation is "close" or not (step S214). The "close" operation is the opposite of "open". The "open" operation is an operation for hiding the task list of the user displayed. When the control unit 31 determines that the accepted operation is "close" (YES in step S214), it hides the task list of the selected user (step S215). The control unit 31 returns the process to step S211. When the control unit 31 determines that the accepted operation is not "close" (NO in step S214), it determines whether it is "send email" (step S216). "Send email" is an operation for sending an email from an expert to a user. When the control unit 31 determines that the accepted operation is "send email" (YES in step S216), it displays an email creation screen in a pop-up window (step S217). The expert creates an email on the email creation screen and instructs sending. The created email is sent to the specified user via the management server 1 and the email server. The control unit 31 returns the process to step S211. When the control unit 31 determines that the accepted operation is not "send email" (NO in step S216), it determines whether it is "completed" (step S218). "Complete" is an operation that changes the status of the displayed task to complete. When the control unit 31 determines that the accepted operation is "Complete" (YES in step S218), it transmits a command to complete the task to the management server 1 (step S219). The control unit 31 returns the process to step S211.When the control unit 31 determines that the accepted operation is not "complete" (NO in step S218), the process ends.

[0060] FIG. 34 is an explanatory diagram showing an example of a user list screen. The user list screen d07 is a screen presented to the expert. The user list screen d07 includes a list table d071 and an add button d072. The list table d071 is a list of users who are clients of the expert. The list table d071 includes an ID column, a company name / trade name column, a person in charge column, a task completion status column, a mark column without a column name d0711, a check box column d0712, and a delete button d0713. The ID column displays the user's ID. The ID may be a sequential number. The company name / trade name column displays the user's company name or trade name, etc. The person in charge column displays the name of the person who will be the user's contact point. The task completion status column displays the total number of tasks assigned to the user and the number of tasks that have been completed among them. Each user in the list d071 is displayed in an accordion, and by operating the mark in the mark column d0711, in this case the upside-down caret, the accordion opens and the list of tasks assigned to the user changes from hidden to visible. After operating the checkbox column d0712 to check a box, operating the Delete button d0713 will delete the selected user from the list d071. Selecting the Add button d072 will take you to the operation of adding a user to be displayed in the list d071.

[0061] FIG. 35 is an explanatory diagram showing another example of the user list screen. The user list screen d07 shown in FIG. 35 is an example of a screen showing a state in which the accordion for one user is open on the user list screen d07 shown in FIG. 34. In FIG. 35, the components displayed in FIG. 34 are given the same reference numerals, and the description is omitted. On the user list screen d07, when the upside-down caret is operated, the accordion opens and a list of tasks assigned to the user is displayed. The task list d073 includes a task name column, a notification destination column, a deadline column, a Memo column, a remind column, and a completion column. The task name column displays the task name. The notification destination column displays the destination of the document to be submitted. The deadline column displays the deadline for completing the task. The Memo column displays the contents of the Memo column. When the remind column is selected, a screen for sending an email to the user opens. When the completion column is selected, the status of the task is updated to completion. When the caret d074 is operated, the accordion closes.

[0062] FIG. 36 is an explanatory diagram showing an example of the email sending screen. The email sending screen d08 is a screen that is displayed when a column for reminding is selected in the task list d073 displayed on the user list screen d07. The email sending screen d08 includes a send button d081 and a back button d082. When the send button d081 is selected, a reminder email is sent to the user. When the back button d082 is selected, the email is not sent and the email sending screen d08 is closed. The email sending screen d08 may be provided with a field for inputting a message from the expert to the user.

[0063] In addition to the effects of the first embodiment, the present embodiment provides the following effects. When a client of an expert uses the task management system 100, the client can autonomously proceed with the execution of a task. The expert can provide the client with services that cannot be supported by the task management system 100, which improves the efficiency of the work.

[0064] In the task management system 100, the events handled are described as business related to business management, but are not limited to this. The task management system 100 can be used for events in various fields. The task management system 100 can be used to manage various life events. For example, an event such as marriage includes multiple tasks such as a wedding ceremony, moving, and a honeymoon. Each of the wedding ceremony, moving, and honeymoon is also an event and includes multiple tasks. In this way, for events with a nested structure in which each task should be treated as an event, management by the task management system 100 is particularly useful for users. The task management system 100 can also be used for dieting, taking exams, acquiring financial literacy, and the like.

[0065] The involvement of experts is also meaningful in various events. For example, a marriage advisor can be involved as an expert in a wedding, and a moving advisor can be involved as an expert in a move. In particular, for events that are difficult to complete on your own, such as dieting, it is meaningful to have a trainer involved as an expert.

[0066] Similarly, for events that are not expected to occur many times in life, such as starting a company, it is difficult to execute smoothly because many users are executing the event for the first time. However, by using the task management system 100 to support the execution of the tasks that make up the event, the end user can execute the event smoothly.

[0067] (Modification) In this modified example, another example of the home screen and a chat function will be described. FIG. 37 is an explanatory diagram showing another example of the home screen. The home screen d09 is a dashboard showing the progress of each task of the business. The home screen d09 includes a user task progress display field d091, a person in charge task progress display field d092, a project task progress display field d093, and the like. The user task progress display field d091 is a display field that displays the progress of the task of the user who is logged in to this system. The person in charge task progress display field d092 is a display field that displays the progress of the task of the user's subordinate (person in charge). The project task progress display field d093 is a display field that displays the progress of the task group that has been made into a project. In addition to this, the home screen d09 displays a display field that displays the progress of the task group for each customer, a calendar showing the implementation deadline of each task, and the like (not shown in FIG. 37). The user terminal 2 presents the progress of tasks to the user by displaying a pie chart in each display field representing the number of tasks completed for each event (for example, the number of tasks completed is displayed as "75 / 100," and the percentage is displayed as "75%" in the pie chart).

[0068] The user terminal 2 accepts an input of task completion on the home screen d09 shown in Fig. 37 or the task details screen d03 (see Fig. 21), etc. This updates the progress status of each task, and the results are reflected on the home screen d09.

[0069] FIG. 38 is an explanatory diagram showing an example of a chat screen. In this modified example, a chat function is implemented that allows a user to chat with other users (including people outside the company). The chat screen d10 includes a chat display field d101 and a chat input field d102. The chat display field d101 is a display field that displays a message (text, etc.) entered by the user. The chat input field d102 is an input field that accepts message input. A user can use this chat function to exchange messages with other users, whether inside or outside the company.

[0070] In this modified example, the chat function may have the following functions. Specifically, the user terminal 2 may accept editing of chat contents, display an icon for displaying the editing history, and display all of the editing history in response to an operation on the icon. The user terminal 2 may accept deletion of a chat, display an icon for displaying the deleted chat, and display the deleted chat contents in response to an operation on the icon. The user terminal 2 may display an approval button (not shown) on the chat screen d10, and when all of the chat sender and recipients press the approval button, the chat contents may be prohibited from being edited or deleted. The user terminal 2 may also have a function of linking with an external chat service (application). The user terminal 2 may transmit the chat contents to the user's superior before sending the chat, and reflect the chat contents on the chat screen d10 only when approval is obtained from the superior.

[0071] (Embodiment 3) This embodiment relates to a form in which a task name is extracted from a response sentence generated by a large-scale language model (for example, GPT (Generative Pre-trained Transformer)), and a task with the extracted task name is newly registered.

[0072] 39 is a flowchart showing an example of a procedure for a task registration process. The control unit 11 of the management server 1 displays and outputs a pop-up screen for a user to interact with the large-scale language model on the home screen (step S301). The control unit 11 accepts input of a prompt from the user terminal 2 (step S302). The control unit 11 generates a response sentence by inputting the prompt to the large-scale language model, and outputs the response sentence on the pop-up screen (step S303).

[0073] FIG. 40 is an explanatory diagram showing an example of a pop-up screen. The user terminal 2 displays a pop-up screen d11 on the home screen d09. The pop-up screen d11 includes a prompt input field d111, a response sentence display field d112, and a task creation button d113. The prompt input field d111 is an input field for the user to input an arbitrary prompt (text, etc.). The response sentence display field d112 is a display field for displaying a response sentence generated by the large-scale language model based on the prompt. The task creation button d113 is a button for extracting a task name from the response sentence and setting it on the event setting screen (see FIG. 41).

[0074] Returning to Fig. 39, the explanation will be continued. The control unit 11 of the management server 1 judges whether or not to generate a task in response to an operation on the task generation button d113 (step S304). If it is judged that a task is not to be generated (S304: NO), the control unit 11 ends the series of processes. If it is judged that a task is to be generated (S304: YES), the control unit 11 extracts one or more task names from the response sentence (step S305).

[0075] The control unit 11 extracts text parts that match a predetermined rule from the response sentence as task names. Specifically, the control unit 11 extracts text parts that are numbered, written in bold, and in a larger font than other text as task names. In accordance with the example of FIG. 40, the control unit 11 extracts "market research and analysis," "developing a business idea," "designing a business model," and the like as task names.

[0076] The control unit 11 displays an event setting screen in which the extracted task name is set (step S306). The control unit 11 accepts an editing operation for the task displayed on the event setting screen (step S307). The control unit 11 stores (registers) the task set in response to the user's operation (step S308), and ends the series of processes.

[0077] 41 is an explanatory diagram showing an example of an event setting screen. The event setting screen d12 is a screen (business editing screen) for setting addition, editing, or deletion of a task. The event setting screen d12 according to this embodiment includes a main item menu d121, a medium item menu d122, a small item menu d123, a task name field d124, a deadline field d125, an add task button d126, and a register button d127. The main item menu d121, the medium item menu d122, and the small item menu d123 are input fields for selecting a main item, a medium item, and a small item of a new event to be registered, using pull-down menus, respectively.

[0078] The task name column d124 is a column for inputting a task name associated with an event. In this embodiment, the user terminal 2 sets the task name extracted from the response sentence generated by the large-scale language model in the task name column d124 by default. The user modifies the task name as necessary.

[0079] The deadline field d125 is a field for setting a deadline for completing a task. The add task button d126 is an input button for adding other tasks. By operating the add task button d126, the user can also add tasks other than the tasks automatically generated from the large-scale language model. The register button d127 is a button for storing (registering) the setting contents in the management server 1.

[0080] As described above, according to the third embodiment, a large-scale language model is used to automatically generate task names, thereby making it possible to favorably assist in setting tasks.

[0081] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims. In addition, the claims are written in a format in which a claim cites two or more other claims (multiple claim format), but this is not limited to this format. The claims may be written in a format in which multiple claims cite at least one other claim (multi-multi claim format). [Explanation of symbols]

[0082] 100: Task management system 1: Management server 11: Control section 12: Main memory 13: Auxiliary storage section 131: User DB 132: User attribute DB 133: Ticket DB 134: Contract DB 135: Event DB 136: Task basic DB 137: Task execution DB 138: Product DB 139: Work in progress DB 13A: Contract ticket DB 14: Communications Department 15: Reading section 1P: Control program 1a: Portable storage medium 1b: Semiconductor memory 2: User terminal 21: Control section 22: Main memory 23: Auxiliary storage section 24: Communications Department 25: Input section 26:Display section 2P: Control program 3: Expert terminal 31: Control section 32: Main memory 33:Auxiliary storage section 34: Communications Department 35: Input section 36:Display section 4: Cloud services B: Bus N: Network

Claims

1. Output the tasks required for running multiple businesses and the fees for managing the tasks for each task, Accept the selection of work, After the fee for the accepted business is settled, a list of tasks for the business and a calendar in which each task is described are displayed and output. An information processing program that causes a computer to perform processing.

2. Accept the selection of industry, The task list and the calendar are displayed based on the tasks associated with the business type and the job. The information processing program according to claim 1 .

3. Obtain a task ID that identifies the task; Obtaining an execution procedure or a hyperlink to a document template associated with the obtained task ID; A task display screen including the acquired execution procedure or the hyperlink to the document template is displayed.

3. The information processing program according to claim 1 or 2.

4. displaying and outputting a task editing screen for setting addition, editing, or deletion of the task corresponding to the task; Obtaining settings for adding, editing, or deleting the task; Add, edit, or delete the task based on the obtained settings.

3. The information processing program according to claim 1 or 2.

5. the task display screen includes the hyperlink to a service that performs the task; When a response is obtained from the service resulting from selection of the hyperlink, completion of the task is stored. The information processing program according to claim 3.

6. Get the administrator ID. Acquire the business associated with the acquired administrator ID; Displaying and outputting a screen for obtaining a usage ticket corresponding to the business; Acquire information about the acquired usage ticket, The task list related to the business corresponding to the acquired usage ticket and the calendar are displayed and output.

3. The information processing program according to claim 1 or 2.

7. Get the administrator ID. displaying a list of end users associated with the acquired administrator ID; Obtain a user ID of the end user selected in the list; A task list of the tasks associated with the acquired user ID is displayed.

3. The information processing program according to claim 1 or 2.

8. Each task in the task list is associated with a hyperlink for reminding the user. The information processing program according to claim 7.

9. Accepts prompt input from the user, inputting the prompt into a language model to obtain a response sentence to the prompt from the language model; Extracting a task name from the response sentence; Add a task with the extracted task name to the task editing screen where the above-mentioned tasks are added, edited, or deleted.

3. The information processing program according to claim 1 or 2.

10. Output the tasks required for running multiple businesses and the fees for managing the tasks for each task, Accept the selection of work, After the fee for the accepted business is settled, a list of tasks for the business and a calendar in which each task is described are displayed and output. An information processing device having a control unit.

11. Output the tasks required for running multiple businesses and the fees for managing the tasks for each task, Accept the selection of work, After the fee for the accepted business is settled, a list of tasks for the business and a calendar in which each task is described are displayed and output. An information processing method in which processing is performed by a computer.

12. Output the tasks required for running multiple businesses and the fees for managing the tasks for each task, Accept the selection of work, After the fee for the accepted business is settled, a dashboard showing the progress of each task of the business is displayed and output. Accept input of the progress of the task An information processing program that causes a computer to perform processing.

Images