Case schedule management system, case schedule management method and case schedule management program

Abstract

To provide a case schedule management system, a method, and a program that enable a user who implements a case to create a case schedule that suits the user himself / herself.SOLUTION: A case schedule management system comprises a storage unit and a case management unit. The storage unit stores user condition information and case information including case delivery date and milestone information. The user condition information is a condition that limits the schedule when a user implements a case, and includes the user's working hours, and the milestone information includes milestone progress information regarding the order of progress of the milestones included in the case and the man-hours required for each milestone. One user in charge is assigned to each case. The case management unit generates a case schedule that is a schedule for the implementation of each case by an individual user, including the implementation schedule for each milestone contained in the case, based on the case information and the user condition information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an item schedule management system, an item schedule management method, and an item schedule management program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, a large number of systems for creating schedules for cases or projects have been disclosed as systems for creating and managing schedules when implementing cases or projects.

[0003] Patent Document 1 discloses a system for creating a work schedule based on the work capabilities of workers, etc., using a trained model. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-35516 Summary of the Invention [Problem to be solved by the invention]

[0005] The invention described in Patent Document 1 is a system for creating and managing a schedule for the entire project, such as a manufacturing process involving a large number of people, but it was not able to create and manage schedules suitable for each individual user.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a novel technique for enabling a user who is to carry out an event to create a schedule for the event that is suited to the user himself / herself. [Means for solving the problem]

[0007] In order to solve the above problems, the present invention provides a case schedule management system for managing a schedule of a user's case, comprising: The system includes a storage unit and a case management unit, The storage unit stores user condition information and case information including delivery date and milestone information of the case, The user condition information is a condition that restricts a schedule when a user executes an item, and includes a user's working time. The milestone information is information about milestones included in a project, and includes milestone progress information about the order of progress of the milestones included in the project and the required man-hours for each milestone; Each case is assigned to a single user, The case management unit generates a case schedule, which is a schedule for the execution of a case for an individual user, including an execution plan for each milestone included in the case, based on the case information and the user condition information.

[0008] With this configuration, it is possible to use the acquired user condition information to generate a project schedule that is appropriate for the user and is personal to the user, as opposed to a project such as a schedule of operations that assigns multiple workers to a single project.

[0009] In a preferred embodiment of the present invention, the case schedule is a schedule including implementation plans for each milestone optimized in the case management section based on constraint conditions including conditions set based on the user condition information and / or the case information.

[0010] With this configuration, it is possible to generate an optimal case schedule using optimization.

[0011] In a preferred embodiment of the present invention, the case schedule management system further includes a reception unit, The user condition information includes a user's simultaneous work capacity for the case; When the reception unit acquires case information regarding a new case, When a project schedule for an existing project for which a schedule has already been generated is the same as part or all of the period for implementing the project of a new project, the project management unit generates an adjusted schedule, which is an adjusted project schedule, based on project information including project information for the new project and project information for the existing project stored in the memory unit.

[0012] With this configuration, even when there are multiple item schedules, it is possible to generate an item schedule that takes into account the other item schedules.

[0013] In a preferred embodiment of the present invention, the case schedule management system further includes a display processing unit and a reception unit. displaying a case information input screen for receiving input of the case information including the milestone information; the case information input screen is a screen for receiving the case information including the milestone information related to a plurality of milestones included in the case, and is a screen for receiving an input of milestone progress information related to an order of progress of the milestones included in the case, The reception unit acquires the case information input via the case information input screen.

[0014] With this configuration, milestone information for generating a case schedule can be easily received.

[0015] In a preferred embodiment of the present invention, the case schedule management system further comprises: a display processing unit that displays a case schedule display screen based on the case information and the case schedule, The case schedule display screen is a screen for displaying a case schedule, and shows milestones, including implementation plans for each milestone included in a case, in the order of progress of the case.

[0016] With this configuration, the schedule for each milestone included in the generated case schedule can be easily provided to the user.

[0017] In a preferred embodiment of the present invention, the storage unit stores a generative model that is a trained model trained using the user condition information and the case information as input data and the case schedule as output data, The case information stored in the storage unit further includes a case type, The case management unit uses the generation model to generate the case schedule based on the case information.

[0018] With this configuration, a project schedule can be easily generated using a trained model. Effect of the Invention

[0019] The present invention can provide a novel technique for enabling a user to create a schedule of an item that suits the user. [Brief description of the drawings]

[0020] [Figure 1] Block diagram showing the overall system configuration [Diagram 2] System hardware configuration diagram [Diagram 3] Data configuration example [Figure 4] Example of case information input screen [Diagram 5] Example of the case schedule display screen [Figure 6] Example of the case schedule display screen [Figure 7] Example of the case schedule display screen [Figure 8] Processing Flowchart [Figure 9] FIG. 1 is a block diagram showing the overall configuration of a system according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] The present invention will be described in more detail below with reference to the accompanying drawings. Although the drawings show a preferred embodiment, the present invention can be implemented in different forms and is not limited to the embodiment described in this specification. In this embodiment, the configuration and operation of a schedule management device will be described, but similar effects can be achieved by a method executed by the device, a computer program, etc. The computer program may be provided as a non-transitory computer-readable recording medium.

[0022] In the embodiments described below, the project schedule management system 0 generates and manages project schedules for individuals (users) who work on projects, such as freelancers, but it may also generate and manage project schedules for each person who belongs to an organization and works on projects as a group of multiple people, or for the entire team when working on a project as a team.

[0023] Moreover, a project schedule is a plan for the implementation of a project, such as a website production or logo design, by a user, and includes the start date and end date of the project. Moreover, in this embodiment, the project schedule includes the start date and end date of implementation for each milestone included in the project, as the implementation plan for each milestone included in the project. In this embodiment, the project schedule generated by the project schedule management system 0 is a personal schedule of a user, to which one person in charge, such as a user, is assigned. A milestone indicates a goal to be implemented that is included in the project, such as a task included in the project.

[0024] The project schedule management system is configured by a computer device. The computer device has an arithmetic unit such as a CPU (Central Processing Unit) and a storage device. The computer device can function as a project schedule management device by executing a project schedule management program stored in the storage device with the arithmetic unit. The project schedule management method is realized by processing of the computer device including the project schedule management device.

[0025] <1.1. System configuration> Fig. 1 is a block diagram showing the configuration of a system according to an embodiment. As shown in Fig. 1, an item schedule management system 0 includes an item schedule management device 1 and a user terminal 2, and is configured to be capable of communicating with each other via a network NW. In this embodiment, the network NW is an IP (Internet Protocol) network, but there is no restriction on the type of communication protocol, and there is no restriction on the type and scale of the network.

[0026] The project schedule management device 1 is a server device for managing project schedules. The user terminal 2 is a terminal device operated by a user who manages the schedule of his / her own project, and in this embodiment, is a computer terminal such as a PC, tablet, or smartphone owned by the user.

[0027] In addition, in this embodiment, the user terminal 2 is configured to be able to communicate with the project schedule management device 1 via the network NW, but if the user terminal 2 stores data necessary for generating and managing the project schedule, it does not have to be configured to be able to communicate.

[0028] <1.2. Hardware configuration> Fig. 2 is a hardware configuration diagram. As shown in Fig. 2(a), the project schedule management device 1 has a processing unit 101, a storage unit 102, and a communication unit 103, and is used to cause each unit and each process to function. Also, as shown in Fig. 2(b), the user terminal 2 has a processing unit 201, a storage unit 202, a communication unit 203, an input unit 204, and an output unit 205, and is used to cause each unit and each process to function.

[0029] One or more information processing devices such as a general-purpose server or a personal computer can be used as the project schedule management device 1. The project schedule management device 1 has a functional configuration described below, but a part of the functional configuration of the project schedule management device 1 may be disposed in another device configured to be able to communicate with the project schedule management device 1 and the user terminal 2. The user terminal 2 can be a computer device such as a PC, a smartphone, or a tablet terminal.

[0030] An arbitrary computer device such as a PC or a smartphone functions as the user terminal 2 of the present invention by the processing unit 201 performing various processes using various data such as a browser application for accessing a dedicated web page stored in the storage unit 202 of the user terminal 2. In addition, the processing unit 201 may perform processes using a dedicated application stored in the storage unit 202 of the user terminal 2 to function as the user terminal 2.

[0031] The processing unit 101 and the processing unit 201 have a processor such as a CPU (Central Processing Unit) capable of executing an instruction set, and execute an OS (Operating System) as well as a case schedule management program (in the case of the case schedule management device 1) or a case schedule management device utilization program (in the case of the case of the user terminal 2).

[0032] The storage unit 102 and the storage unit 202 each have a volatile memory such as a RAM (Random Access Memory) capable of storing an instruction set, and a non-volatile recording medium such as a HDD (Hard Disk Drive) or SSD (Solid State Drive) capable of recording an OS, etc. The storage unit 102 of the matter schedule management device 1 stores a matter schedule management program, etc. The storage unit 202 of the user terminal 2 stores a program for using the matter schedule management device, such as a dedicated application or a browser application, etc.

[0033] The storage unit 102 stores various information received by the reception unit. In this embodiment, the storage unit 102 stores various information necessary for generating a project schedule including project information including milestone information and user condition information, a generation model that is a trained model used for generating a project schedule, and the like.

[0034] The communication unit 103 and the communication unit 203 have an interface for connecting to a network, and execute communication control with the network to communicate with other information processing devices and the user terminal 2.

[0035] The input unit 204 has an operation input device capable of input processing, such as a touch panel or a keyboard. The output unit 205 has a display device capable of display processing, such as a display. The input unit 204 may also have an audio input device, such as a microphone. The output unit 205 may also have an audio output device, such as a speaker.

[0036] <1.3. Functional configuration> 1, the matter schedule management device 1 includes a reception unit 11, a matter management unit 12, and a display processing unit 13. This is information processing by software (a program stored in a storage unit or the like temporarily or non-temporarily) specifically realized by hardware (a processing unit or the like).

[0037] <1.3.1. Configuration of Reception Unit 11> The reception unit 11 performs a process of receiving information necessary for generating a project schedule, such as project information and user condition information. In this embodiment, the reception unit 11 performs a process of receiving various information necessary for generating a project schedule, including project information and user condition information input by a user at the user terminal 2.

[0038] In addition, the reception unit 11 may further receive information regarding the progress of the user's case, such as information on the user's ongoing milestones and milestones that have already been completed, and use the received information for generating a case schedule or modifying a case schedule that has already been generated.

[0039] Furthermore, the reception unit 11 may perform a process of converting the received data into a format that is easy to use in the case schedule management system 0 as a preprocessing step.

[0040] 3 shows an example of the structure of data acquired by the receiving unit 11. The data structure shown in the figure is an example, and the data structure is not limited to this form.

[0041] In this embodiment, the reception unit 11 acquires data necessary for generating a project schedule, such as user condition information and project information, by receiving information input by a user from the user terminal 2 communicably connected via a network. In addition, when the user terminal 2 has all the functional configuration of the project schedule management device 1 and all the data necessary for generating a project schedule is stored in the storage unit 202 of the user terminal 2, the project schedule management device 1 and the user terminal 2 do not need to have a configuration for executing the processing in the reception unit 11. In addition, in this embodiment, various information including the project information and user condition information received by the reception unit 11 is stored in the storage unit 102.

[0042] 3(a) shows an example of user condition information received by the receiving unit 11 and stored in the storage unit 102. The user condition information is information related to the execution of a user's case, such as the user's working status, that is used for generating a schedule. In this embodiment, the user condition information includes a user ID and a user name, the user's working hours per day and the number of working days per week, and the number of milestones that the user can execute simultaneously as the simultaneous work capacity.

[0043] In addition, the user condition information may be any information regarding the user's project execution that can be used to generate a project schedule, such as the user's working conditions and the user's project execution capabilities, and may include, for example, the user's job type, the number of days or time taken to execute projects by the user in the past, the time required for each milestone, the amount of leeway to be left in the schedule, and other user requests regarding the project schedule.

[0044] In this embodiment, the reception unit 11 acquires and stores the user condition information input when the user registers as a member, but may acquire the user condition information input in the user terminal 2 every time a case is registered.

[0045] FIG. 3(b) shows an example of case information received by the reception unit 11. The case information shown in FIG. 3(b) is information about a case implemented by a user, and includes a case ID, a case name, a deadline, and a case type. The case information may be any information about a case. The case name is the name of the case, and is a name registered by the user. The deadline is information about the deadline for implementing the case, and in this embodiment, includes the start date and completion date of the case, but may be only the completion date of the case. The case type is information about the type of case, such as web site production, web site design, and image design. The case type may be different depending on the user's occupation. For example, if the user's occupation is designer, a case type related to design or the like may be selected, and if the user's occupation is web engineer, a case type such as web site production may be selected.

[0046] FIG. 3(c) shows milestone information included in the case information received by the receiving unit 11. The milestone information is information about milestones, and is information about each milestone included in the case. In this embodiment, the milestone information includes a milestone ID and a milestone name (type), and, as milestone progress information, the order of progress of the milestone and the required man-hours for the milestone. The required man-hours is the work time required for each milestone, and in this embodiment, is the time required from the start to the completion of the milestone, calculated based on the ratio of the allocated time when the total time of the case input by the user is set to 100. The required man-hours may also be the average time required to carry out the milestones registered for each milestone type, the time previously taken by the user to complete the milestone, etc.

[0047] Furthermore, the milestone information may be any information relating to each milestone included in the case. In this embodiment, the milestone progress information relating to the order of progress of the milestones is the order of progress of the milestones in the case, but may also be information relating to the interdependencies between milestones, such as the relationship between milestones in which work cannot be started until work at a specific milestone has been completed. In this embodiment, when multiple cases are registered, the reception unit 11 receives the priority of the cases input at the user terminal 2. The priority is the priority of each case among the multiple cases, including a designation of the case to be implemented with the highest priority when implementing the multiple cases.

[0048] Furthermore, the receiving unit 11 may receive, as the case history, a history of actual case implementation, such as the time spent by a user who implemented the case based on the case schedule on implementing each milestone.

[0049] <1.3.2. Configuration of the Case Management Department 12> The case management unit 12 generates and adjusts the case schedule based on information such as user condition information and case information. In this embodiment, the case management unit 12 generates and adjusts the case schedule by using an optimization technique, but may generate the case schedule using a trained model (generative model) that has been trained based on case information related to the user's past cases. In this embodiment, when a new case is registered, the case schedule is generated based on the case information of the new case and user condition information, but may generate the case schedule using case information of other cases including existing cases. In this embodiment, the case management unit 12 determines the order of milestones in the case schedule based on milestone progress information. In addition, the case management unit 12 may perform a process of acquiring data necessary for generating the case schedule, such as already stored user condition information and case information, from the storage unit 102, the storage unit 202, etc., in order to generate the case schedule.

[0050] In this specification, "optimization" refers to finding an optimal solution to an optimization problem. In this embodiment, the case management unit 12 performs optimization using conditions for generating a case schedule based on user condition information and case information, etc., as constraint conditions in the optimization problem, and determines the start date and end date of the planned implementation of each milestone as the case schedule, which is an optimal schedule. In this embodiment, the case management unit 12 generates a case schedule including a start date and end date of the milestone that minimizes the number of days that the end date of the case schedule exceeds the completion date of the case input as the delivery date, for each milestone, under constraint conditions set based on the user condition information and the case information. In addition, the case management unit 12 may perform optimization in a manner that maximizes or minimizes the difference between the average time required for implementation of each milestone based on the implementation history of the case and the time from the start date to the end date of the milestone, or other functions.

[0051] In this embodiment, the start date and end date of each milestone included in the case are determined based on the constraint conditions shown in the following formulas from Number 1 to Number 4. In this embodiment, the case management unit 12 generates a case schedule including milestones in an order based on milestone progress information, with the start date and end date of the milestone satisfying the constraint conditions shown in the following formulas. Number 1 is a constraint condition that restricts the start date of each milestone. The case management unit 12 sets the start date of the milestone included in the case to a date after the start date of the case based on Number 1. Furthermore, Numbers 2, 3, and 4 are expressions related to the constraint conditions that restrict the end date of the milestone. The case management unit 12 sets the end date of the milestone before the date obtained by adding the allowable overtime days to the completion date of the case set by the user based on Number 2. Furthermore, the case management unit 12 sets the start date and end date of each milestone based on Number 3 so that the start date and end date of each milestone are not shorter than the number of days required to complete the case based on the required man-hours and daily operating hours of the milestone. Furthermore, the project management unit 12 sets the allowable number of excess days not to be exceeded when the milestone completion date exceeds the project completion date based on the formula 4. In this embodiment, when the end date of the last milestone in sequence is after the completion date of the project acquired as the delivery date, the project management unit 12 performs optimization to minimize the number of excess days and determines the project schedule including the start and end dates of the milestones.

[0052] The allowable excess days is the number of excess days that a user allows for in a project schedule. In this embodiment, the allowable excess days is the number of days set by the user, but it may be the number of days that is uniformly determined for all users, the number of days that is determined based on the type of project, or the number of days that is set based on the user's past project implementation schedule.

number

number

number

number

[0053] In addition, the case schedule may not satisfy some of the conditions set based on the user condition information and the case information, such as the case implementation time in one week exceeding the number of working days per week set by the user. In addition, there is no limit to the combination of the case information and user condition information used to set the constraint conditions, and the constraint conditions may be set using some or all of the acquired case information and user condition information.

[0054] In this embodiment, the case management unit 12 outputs, as the case schedule, the time required from the start to the end of each milestone and the end date of the case. In this embodiment, the case management unit 12 outputs a date earlier than the completion date of the case acquired as the due date of the case. However, for example, when multiple cases are progressing simultaneously, in order to secure time for work, a date later than the completion date of the case acquired as the due date may be output as the end date of the milestone. In addition, when the end date of the case output as the case schedule is a date later than the completion date input by the user as the due date of the case and acquired as the due date, the case management unit 12 may correct the case schedule so that the end date is in time for the completion date input by the user and acquired as the due date, such as by reducing the time (number of days) required for each milestone as the planned implementation time for each milestone. In this embodiment, the planned implementation time of the milestone is the number of days from the start date to the end date of the milestone output as the case schedule, but may be the work time required for each milestone. In addition, the case management unit 12 may generate a case schedule in which multiple milestones included in a specific case are progressed simultaneously.

[0055] The case management unit 12 generates a case schedule including a planned implementation time for each milestone included in the case based on the acquired information. In this embodiment, the case management unit 12 generates a case schedule for each milestone day as a planned implementation time for work, etc. for each milestone included in the case, but it may generate a case schedule including a schedule for each hour, not for each day, such as the time to perform work, etc. for each milestone.

[0056] In addition, the case management unit 12 adjusts the case schedules when a part or all of the implementation periods of a plurality of cases are the same and the implementation periods overlap, such as when there is a case schedule for an existing case and the implementation period (the period from the start to the completion of the case acquired as the delivery date) of a case schedule for a newly registered new case overlaps with the case schedule for an existing case. In this embodiment, the case management unit 12 adjusts the case schedules by generating or regenerating the case schedule based on the case information of the plurality of cases and the user condition information, but the adjustment may be performed by other methods. In addition, the case management unit 12 generates a case schedule that prioritizes a case with a high priority based on the priority of the acquired cases. In this embodiment, the case management unit 12 generates an adjusted case schedule such that the number of overtime days of the case schedule for a case with a high priority is less than the number of overtime days of the case schedule for a case with a low priority, but for example, a case schedule in which a case with a high priority is completed earlier may be generated as an adjusted schedule.

[0057] In this embodiment, when case information of a new case is received, if the implementation period of the new case overlaps with the implementation period of the case schedule of an existing case that has already been registered, that is, if part or all of the implementation periods are the same, the case management unit 12 generates a case schedule that does not exceed the user's simultaneous work capacity. For example, if the user's simultaneous work capacity is two milestones that can be progressed simultaneously, the case management unit 12 generates a case schedule that does not exceed two milestones that are progressed simultaneously, based on the constraints on the simultaneous work capacity.

[0058] In this embodiment, the case management unit 12 performs optimization based on the case information of multiple cases and user condition information, and adjusts the case schedule by changing the planned implementation time of each milestone, but the adjustment may be performed by changing the start date or end date of the case, or by increasing the user's daily working hours or the number of working days per week. Also, in this embodiment, the case management unit 12 performs optimization based on the acquired case information of a new case, case information of an existing case, and user condition information, and generates an adjusted schedule, which is an adjusted case schedule including the planned implementation time for each milestone, for both the new case and the existing case, but may adjust the case schedule of only one of the existing case or the new case, and generate an adjusted schedule for the existing case or the new case.

[0059] The display processing unit 13 performs display processing of necessary screens including input screens such as a necessary case information input screen and a case schedule display screen that displays the generated case schedule. In this embodiment, the display processing unit 13 performs display processing of input screens such as a case information input screen and a user condition information input screen for receiving input of user condition information and case information based on the acquired information.

[0060] The user condition information input screen is an input screen for inputting user condition information. In this embodiment, the user condition information input screen is displayed when a user of the system performs user registration, and accepts input of user condition information including the user's occupation, the user's working hours per day, and the user's working days per week. The user condition information input screen may also accept, as user condition information, information regarding the user's wish regarding a case schedule, the number of cases that can be executed simultaneously, and other information regarding the user's own ability to execute cases.

[0061] The following will use the drawings to show examples of screens to be displayed by the display processing unit 13. The case information input screen displayed by the display processing unit 13 is a screen for inputting case information including milestone information.

[0062] An example of the case information input screen is shown below with reference to Fig. 4. The case information input screen W1 shown in Fig. 4 includes a case information reception section W11 for receiving case information, a milestone reception section W12 for receiving milestone information, and a man-hour reception section W13 for registering required man-hours.

[0063] The case information receiving unit W11 receives input of case name, case due date, and case type as case information. The case information receiving unit W11 receives input of case type, due date, and case information corresponding to the input field for case type. In this embodiment, the input field for the due date of the case information receiving unit W11 is an input field in which a calendar is displayed by pressing the calendar icon displayed on the right side, and the start date and end date of the case are specified as the due date by selecting a specific date on the displayed calendar. In addition, the input field for case type of the case information receiving unit W11 displays multiple case types and receives the selection of the case type by the user, but the case name, etc. input by the user may be received as the case type.

[0064] The milestone receiving unit W12 further receives the milestone name as the milestone information included in the case information and the progress order of the milestone in the case as the milestone progress information.

[0065] In the milestone reception section W12 shown in Figure 4, the milestone names entered as milestone candidates can be dragged and dropped into the milestone display field and rearranged in the order of milestone progress, thereby inputting the milestone names (types) and milestone progress order (milestone progress information) of the milestones included in the project.

[0066] The man-hour reception unit W13 receives the required man-hours for each milestone registered in the milestone reception unit W12. In this embodiment, the man-hour reception unit W13 receives, as man-hour information, the proportion to be allocated to each milestone when the delivery date is assumed to be about one month. The man-hour reception unit W13 displays the milestones registered in the milestone reception unit W12 in the order of progress in which they were registered, and receives the proportion of time to be allocated to each milestone. The method of inputting the man-hours may be selected using the man-hour reception unit W13. For example, an input method of the required man-hours may be selected in which the time to be spent on each milestone is input, and the input of the time required for each milestone may be received.

[0067] Furthermore, in this embodiment, the man-hour receiving unit W13 receives the proportion of the required man-hours for each milestone, which is set as the proportion of time to be spent on each milestone when the delivery date is assumed to be one month, and receives input of the proportion of time to be allocated to each milestone by the user by sliding the circle displayed below the milestone name left and right when the project period is set to 100, and registers the required man-hours for each milestone. The circle display for each milestone is moved left and right by the user's operation, and the proportion of time to be spent on the milestone, which is displayed in a rounded rectangle displayed above the circle display, is changed, allowing the user to intuitively grasp the change in the required man-hours that has been changed.

[0068] In this embodiment, when the man-hours receiving unit W13 registers the ratios of 10% for hearing and 5% for proposal, the required man-hours for hearing are registered as 24 hours and the required man-hours for proposal are registered as 12 hours. The required man-hours based on the ratio are the required time for each milestone calculated based on the number of days expected for implementation based on the ratio selected by the user (for example, 3 days for 10%) when the entire project period is 30 days, and the user's operating hours.

[0069] In addition, if a user wishes to make corrections to the case schedule generated by the case management unit 12, the case schedule management system 0 may accept information regarding corrections to the case schedule via a screen having a screen layout similar to the case information input screen W1.

[0070] Hereinafter, examples of the project schedule display screen will be described with reference to Figs. 5 to 7. In this embodiment, the project schedule display screen W2 shown in the drawings is a screen display for displaying the generated project schedule, and is a screen display that simultaneously displays the schedules of multiple projects.

[0071] The case schedule display screen W2 includes an ongoing project list W21, a milestone list W22, and a Gantt chart display section W23. The ongoing project list W21 is a section that displays ongoing cases, and the case schedule of the case selected on the case schedule display screen W2 can be switched between displayed and hidden by pressing the square display to the left of the case name. The milestone list W22 is a section that displays the implementation schedule of each case, such as the start date and end date of each milestone included in the case schedule. As shown in the figure, the milestone list W22 displays the case name for each case, the milestone name (type) of the milestone included in the case, and the start date of each milestone. In this embodiment, the case schedule is displayed from the top based on the priority of the case, but the cases may be displayed from the top in order of the earliest start date. Furthermore, if the generated case schedule or the implementation status of the case schedule will not meet the delivery date, such as when the start date or end date of each milestone is delayed, the milestone list W22 may display a warning indicating that the case schedule is delayed by displaying the number of days that the delivery date is delayed. The Gantt chart display section W23 is a section that displays a Gantt chart based on the case schedule, and in this embodiment, is a section that displays the scheduled implementation time for each milestone included in the case as a Gantt chart.

[0072] A Gantt chart is a type of bar graph with the milestone names of the milestones to be worked on as the vertical axis and time as the horizontal axis. In this embodiment, the Gantt chart display unit W23 processes and displays a Gantt chart based on the project schedules of multiple projects including new projects and existing projects. In this embodiment, the Gantt chart is displayed in order of project priority from top to bottom, but it may be displayed in any order, such as in order of project registration, earliest delivery date, or the deadline of the currently ongoing milestone. In addition, the Gantt chart may be displayed by accepting settings related to the display of the Gantt chart from the user terminal 2.

[0073] Moreover, the case schedule display screen W2 may further include an adjustment schedule display section W24 that displays the adjusted schedule, which is the case schedule after adjustment, as shown in Fig. 7. The adjustment schedule display section W24 is a section that displays the adjusted adjustment schedule, and in this embodiment, displays a comparison with the case schedule before adjustment to show the user the details of the adjustment.

[0074] Furthermore, in this embodiment, the case schedule display screen W2 displays each case in the same chromatic color scheme, thereby improving visibility.

[0075] <1.4. Processing flow> The process flow will be described below with reference to the drawings. The process flow shown in Fig. 8 is an example in this embodiment, and the processes may be executed in an order different from that shown in the drawing.

[0076] When a request to display a case information input screen is transmitted from the user terminal 2, the display processing unit 13 of the case schedule management device 1 that has received the request performs display processing of the case information input screen (S101). The user terminal 2 displays the case information input screen (S201) and accepts input of case information via the displayed case information input screen (S202). The reception unit 11 accepts the case information and user condition information input at the user terminal 2 (S102). The reception unit 11 may acquire user condition information already acquired at the time of user registration from the storage unit 102 in order to generate the case schedule. When the implementation period of the case based on the start date and completion date input as the delivery date for the existing case does not overlap, the case management unit 12 generates the case schedule based on the acquired user condition information and case information (S103). The case management unit 12 may acquire user condition information already acquired at the time of user registration from the storage unit 102 in order to generate the case schedule, and use the acquired user condition information in generating the case schedule.

[0077] When the case information is acquired, if the implementation period overlaps with the case schedule of an existing case that has already been registered and for which a case schedule has been generated, the case management unit 12 acquires the case information of the existing case from the memory unit 102 (S104), and generates an adjusted schedule, which is an adjusted case schedule, based on the acquired case information of the existing case, the case information of the new case, and the user condition information.

[0078] The display processing unit 13 performs display processing of the generated matter schedule including the adjusted schedule (S106). Also, the user terminal 2 displays the matter schedule display screen (S203).

[0079] <2.1. Second embodiment> An example of the implementation when generating a project schedule using a trained model (generative model) is shown below. In the second embodiment, a user can input the deadline and project type (website production, logo design, etc.) of the project as project information to generate a schedule suitable for the user based on past project data.

[0080] 9 shows a system configuration of a matter schedule management system 0 in embodiment 2. The matter schedule management system 0 includes a matter schedule management device 1 and a user terminal 2. In embodiment 2, the matter schedule management device 1 includes a reception unit 11, a matter management unit 12, a display processing unit 13, and further includes a learning unit 14.

[0081] In the second embodiment, the case management unit 12 generates and adjusts the case schedule by using a trained generation model that has been trained using case information and user condition information of the user's past cases as input data and a case schedule as output data. The case management unit 12 generates a case schedule from the case information and input data acquired by the reception unit 11 by using the generation model. In the second embodiment, the case management unit 12 generates the case schedule by using case information including the case type and milestone information, and user condition information. Also, in the second embodiment, the case management unit 12 generates the case schedule by using the milestone name (type), milestone progress information, and required man-hours as milestone information, but the case schedule may be generated by using the average time required to complete a milestone acquired from the case history, which is the history of past case implementation, as the required man-hours.

[0082] Furthermore, the project schedule management system 0 receives, from the user terminal 2, correction information on parts of the project schedule generated by the project management unit 12 that the user wishes to correct, and makes the corrections to ultimately create a project schedule that is suited to the user. In this embodiment, the generation model is a model that has been corrected by the user and has been trained using the project schedule that ultimately reflects the user's opinions.

[0083] In embodiment 2, the generative model is a model that has been trained using a deep learning technique, but any technique may be used as long as the model has been trained using a machine learning technique.

[0084] The learning unit 14 learns a generation model using the user condition information and the case information accepted by the accepting unit 11 as input data and the case schedule as output data. The model generated by the learning is stored in the storage unit 102 and is used for generating the case schedule.

[0085] In the second embodiment, the learning unit 14 learns the generative model using case information including the required man-hours and case type, user condition information regarding the user's case implementation, and milestone information including milestone progress information and milestone type as input data, and the case schedule as output data. In the present embodiment, the learning unit 14 uses the time (number of days) taken from the start to completion of milestone implementation based on the user's case history as the required man-hours for learning the generative model. A model for each user that has been learned using only the case information entered by the user as input data and the case schedule as output data may be used as the generative model. The generative model may also be a model that has been learned for each case type.

[0086] In this embodiment, the learning unit 14 learns a generation model capable of generating a project schedule suitable for a user by learning using project schedules that reflect the user's actual project implementation status and project schedule planning tendencies, such as a project schedule that was generated by optimization but did not match the user's preferences and was modified based on information input by the user, or a project schedule based on the time that the user actually took to implement past projects and actual results. [Explanation of symbols]

[0087] 0 Project Schedule Management System 1. Project Schedule Management Device 2. User terminal 11 Reception 12 Project Management Department 13 Display processing section 14 Learning Department

Claims

1. A case schedule management system for managing a schedule of a user's case, The system includes a storage unit and a case management unit, The storage unit stores user condition information and case information including delivery date and milestone information of the case, The user condition information is a condition that restricts a schedule when a user executes an item, and includes a user's working time. The milestone information is information about milestones included in a project, and includes milestone progress information about the order of progress of the milestones included in the project and the required man-hours for each milestone; Each case is assigned to a single user, the case management unit generates a case schedule, which is a schedule for the execution of a case by an individual user, including an execution plan for each milestone included in the case, based on the case information and the user condition information; Project schedule management system.

2. The case schedule is a schedule including an implementation plan for each milestone optimized in the case management unit based on constraint conditions including conditions set based on the user condition information and / or the case information. The case schedule management system according to claim 1 .

3. The case schedule management system further includes a reception unit, The user condition information includes a user's simultaneous work capacity for the case; When the reception unit acquires case information regarding a new case, When a part or all of a period for implementing the case of the new case is the same as a case schedule for an existing case for which a schedule has already been generated, the case management unit generates an adjusted schedule, which is an adjusted case schedule, based on case information including case information of the new case and case information of the existing case stored in the storage unit. The case schedule management system according to claim 1 .

4. The case schedule management system further includes a display processing unit and a reception unit, displaying a case information input screen for receiving input of the case information including the milestone information; the case information input screen is a screen for receiving the case information including the milestone information related to a plurality of milestones included in the case, and is a screen for receiving an input of milestone progress information related to an order of progress of the milestones included in the case, the reception unit acquires the case information input via the case information input screen; The case schedule management system according to claim 2 .

5. The project schedule management system also: a display processing unit that displays a case schedule display screen based on the case information and the case schedule, The case schedule display screen is a screen for displaying a schedule of a case, and is a screen for displaying milestones, including implementation plans for each milestone included in the case, in the order of progress of the case. The case schedule management system according to claim 2 .

6. the storage unit stores a generative model that is a trained model trained using the user condition information and the case information as input data and the case schedule as output data; The case information stored in the storage unit further includes a case type, the case management unit uses the generation model to generate the case schedule based on the case information; The case schedule management system according to claim 1 .

7. 1. A computer-implemented case schedule management method for managing a schedule of a user's cases, comprising: The method includes a storage step and a case management step, The storage step includes storing user condition information and case information including delivery date and milestone information of the case in a storage unit; The user condition information is a condition that restricts a schedule when a user executes an item, and includes a user's working time. The milestone information is information about milestones included in a project, and includes milestone progress information about the order of progress of the milestones included in the project and the required man-hours for each milestone; Each case is assigned to a single user, The case management step generates a case schedule, which is a schedule for the execution of a case by an individual user, including an execution schedule for each milestone included in the case, based on the case information and the user condition information. How to manage project schedules.

8. A case schedule management program for managing a user's case schedule, A computer is caused to function as a storage unit and a case management unit, The storage unit stores user condition information and case information including delivery date and milestone information of the case, The user condition information is a condition that restricts a schedule when a user executes an item, and includes a user's working time. The milestone information is information about milestones included in a project, and includes milestone progress information about the order of progress of the milestones included in the project and the required man-hours for each milestone; Each case is assigned to a single user, the case management unit generates a case schedule, which is a schedule for the execution of a case by an individual user, including an execution plan for each milestone included in the case, based on the case information and the user condition information; Project schedule management program.

Images