WORK ADMINISTRATION FACILITY, WORK ADMINISTRATION PROCEDURES AND WORK ADMINISTRATION PROGRAM

Abstract

A progress acceptance unit (214) accepts delay information specifying a delay task, which is a task that may experience a delay. An impact identification unit (23) references assignment relationship information specifying resources assigned to a variety of tasks to identify a task that shares the same resource as a resource assigned to the delay task. This task is identified by the delay information accepted by the progress acceptance unit (214) as being affected by a delay in the delay task. A notification unit (24) notifies a person responsible for the affected task identified by the impact identification unit (23).

Description

Technical field

[0001] The present disclosure relates to a technology for supporting the planning and management of tasks. State of the art

[0002] In medical facilities such as hospitals, treatment plans are created for patients individually based on their illnesses. A treatment plan is a list of daily tasks for each patient. However, for the actual execution of these tasks, it is necessary to allocate time, a staff member, materials, and a location for each task.

[0003] Patent document 1 describes how, for each patient, a list of required work elements and a list of resources required to perform those work elements are created. Patent document 1 then describes the allocation of resources to each work element for each patient based on these two lists. Reference list patent literature

[0004] Patent Literature 1: JP 2016-099766 A Summary of the invention: Technical problem

[0005] It is possible that there are numerous individuals responsible for allocating resources to tasks. In this case, with the technology described in patent literature 1, each responsible individual cannot know how other responsible individuals allocate resources to tasks or the progress status of tasks assigned to other responsible individuals. Therefore, if a delay occurs in a task for which another person is responsible, each responsible individual cannot know what effect this will have on their own task.

[0006] The purpose of this disclosure is to identify the effects of any delay in performing a task. Solution to the problem

[0007] A labor administration institution as described in this disclosure comprises a progress acceptance unit for receiving delay information specifying a delay task, where the delay task is a task or activity in which a delay may occur; and An impact identification unit for referencing assignment relationship information that specifies resources each assigned to a variety of tasks in order to identify a task that has the same resource assigned to it as a resource assigned to the delay task, which is indicated by the delay information accepted by the progress assumption unit as an affected task that may be affected by a delay in the delay task. Advantageous effects of the invention

[0008] In the present disclosure, a task or activity is identified to which the same resource is assigned as a resource assigned to a delaying task. In this way, it is possible to identify a task that could be affected by a delay of the delaying task. Brief description of the drawings Fig. Figure 1 is a configuration diagram of a work management system 100 according to embodiment 1; Fig. Figure 2 is a configuration diagram of the work management facility 10 according to embodiment 1; Fig. Figure 3 is a flowchart of a data collection process according to embodiment 1; Fig. Figure 4 is a figure that describes resource information 31 according to embodiment 1; Fig. Figure 5 is a figure that describes task information 32 according to embodiment 1; Fig. Figure 6 is a figure that describes assignment information 33 according to embodiment 1; Fig. Figure 7 is a figure that describes assignment relationship information 34 according to embodiment 1; Fig. Figure 8 is a figure that describes dependency relationship information 35 according to embodiment 1; Fig. Figure 9 is a flowchart of a process for identifying affected tasks according to embodiment 1; and Fig. 10 is a configuration diagram of the work management facility 10 according to variant 1. Description of embodiments Embodiment 1.*** Description of configuration ***

[0009] With reference to Fig. 1 describes a configuration of a work management system 100 according to embodiment 1.

[0010] The work management system 100 comprises a work management facility 10 and one or more user terminals 50. The work management facility 10 and each of the one or more user terminals 50 are connected via a network 60.

[0011] The work management unit 10 is a computer, such as a server, that identifies another task that may be affected by a task experiencing a delay. The user terminal 50 is a computer, such as a PC, used by a person responsible for managing tasks. PC is an abbreviation for personal computer. The network 60 is a communication device used to connect the work management unit 10 and the user terminal 50, either wired or wirelessly, and to transmit information. The network 60 consists of communication lines and a communication device.

[0012] With reference to Fig. 2 describes a configuration of the work management facility 10 according to embodiment 1.

[0013] The work management unit 10 comprises hardware consisting of a processor 11, a working memory 12, a storage unit 13 and a communication interface 14. The processor 11 is connected to other hardware components via signal lines and controls these other hardware components.

[0014] Processor 11 is an integrated circuit (IC) that performs the processing. IC stands for Integrated Circuit. Specific examples of processor 11 are a CPU, a DSP, and a GPU. CPU stands for Central Processing Unit. DSP stands for Digital Signal Processor. GPU stands for Graphics Processing Unit.

[0015] Random Access Memory (RAM) is a storage device used to temporarily store data. Specific examples of RAM are SRAM and DRAM. SRAM stands for Static Random Access Memory. DRAM stands for Dynamic Random Access Memory.

[0016] Memory 13 is a storage device used to store data. A specific example of memory 13 is an HDD. HDD stands for Hard Disk Drive. Alternatively, memory 13 can also be a portable recording medium, such as an SD memory card (registered trademark), CompactFlash (registered trademark), NAND flash memory, a flexible disk, an optical disc, a compact disc, a Blu-ray disc (registered trademark), or a DVD. SD stands for Secure Digital. DVD stands for Digital Versatile Disc.

[0017] The communication interface 14 is an interface for establishing communication with other devices and for transmitting and receiving data. Specific examples of communication interface 14 are an Ethernet port (registered trademark), a USB port, and an HDMI port (registered trademark). USB is an abbreviation for Universal Serial Bus. HDMI is an abbreviation for High-Definition Multimedia Interface.

[0018] The work management unit 10 is connected via the communication interface 14 to an input device 141 and a display device 142. A specific example of an input device 141 is a keyboard and a mouse. A specific example of a display device 142 is an LCD. LCD is an abbreviation for Liquid Crystal Display.

[0019] The work management facility 10 comprises, as functional components, an acceptance unit 21, a relationship extraction unit 22, an impact identification unit 23, and a notification unit 24. The acceptance unit 21 comprises a resource acceptance unit 211, a task acceptance unit 212, an assignment acceptance unit 213, and a progress acceptance unit 214. The relationship extraction unit 22 comprises a resource relationship extraction unit 221 and a dependency relationship extraction unit 222. The functions of the functional components of the work management facility 10 are implemented by software.

[0020] Memory 13 stores programs that implement the functions of the functional components of the work management unit 10. These programs are read into main memory 12 by processor 11 and executed by processor 11. This is how the functions of the functional components of the work management unit 10 are implemented.

[0021] In Fig. Figure 2 shows only one processor 11. However, there can also be multiple processors 11, and these multiple processors 11 can work together to execute the programs that implement the functions. *** Description of a business ***

[0022] With reference to the Fig. Sections 3 to 9 describe the operation of the employment administration facility 10 according to embodiment 1.

[0023] A process for operating the work management facility 10 according to embodiment 1 corresponds to a work management procedure according to embodiment 1. A program that implements the operation of the work management facility 10 according to embodiment 1 corresponds to a work management program according to embodiment 1.

[0024] The operation of the employment administration facility 10 includes a data collection process and a process for identifying affected tasks.

[0025] In Fig. Section 3 describes the data collection process according to embodiment 1. (Step S11: Resource Acceptance Process)

[0026] Resource acceptance unit 211 accepts the input of resource information 31.

[0027] The resource acceptance unit 211 accepts, in particular, the resource information 31 entered by one of the user terminal devices 50. Alternatively, the resource acceptance unit 211 can accept the resource information 31 entered by operating the input device 141. The resource acceptance unit 211 writes the accepted resource information 31 to the memory 13.

[0028] As in Fig. As shown in Figure 4, the resource information 31 is information about resources. This resource information includes details such as a resource name, type, period, and assignment availability. The resource name identifies a resource. The type classifies the resource. The period is the timeframe during which assignment to a task is permitted. Assignment availability indicates whether assignment to a task is possible. Assignment availability is typically defined for a specific time period. (Step S12: Task Acceptance Process)

[0029] The task acceptance unit 212 accepts the input of task information 32.

[0030] The task acceptance unit 212 accepts, in particular, the task information 32 entered by one of the user terminal devices 50. Alternatively, the task acceptance unit 212 can accept the task information 32 entered by operating the input device 141. The task acceptance unit 212 writes the accepted task information 32 to the memory 13.

[0031] As in Fig. As shown in Figure 5, the task information 32 is information about tasks. The task information 32 includes details such as a task name, an execution period, a dependency target, and an execution status. The task name is information used to identify a task. The execution period is the timeframe in which the task is scheduled to run. The dependency target is another task that must be completed before the task can run. The execution status is the current status of the task's execution. (Step S13: Assignment Acceptance Process)

[0032] The allocation acceptance unit 213 accepts allocation information 33 about the allocation of resources to tasks.

[0033] The assignment acceptance unit 213 accepts, in particular, the assignment information 33 entered by one of the user terminals 50. Alternatively, the assignment acceptance unit 213 can accept the assignment information 33 entered by operating the input device 141. At this point, the assignment acceptance unit 213 can display the resource information 31 and the task information 32 on the display device 142. The assignment acceptance unit 213 writes the accepted assignment information 33 to memory 13. In this way, for example, each of a multitude of tasks is assigned a responsible person. The assignment information 33 is entered for each of the tasks by the person responsible for that task.

[0034] As in Fig. As shown in Figure 6, the assignment information 33 is information that specifies the resources assigned to the tasks individually. The assignment information 33 includes information such as a task name, a resource name, and an assignment period. The assignment period specifies the period during which the resource identified by the resource name is assigned to the task identified by the task name. (Step S14: Resource Relationship Extraction Process)

[0035] Resource Relationship Extraction Unit 221 extracts an assignment relationship between a task and a resource assigned to the task. Resource Relationship Extraction Unit 221 then generates assignment relationship information 34, which specifies the assignment relationship. Resource Relationship Extraction Unit 221 writes the assignment relationship information 34 to memory 13.

[0036] Specifically, the resource relationship extraction unit 221 refers to the assignment information 33 assumed in step S13 to extract each resource assigned to each task. As a result, the assignment relationship information 34 is generated, specifying the resource name of each assigned resource for each task name, as shown in Fig. 7 shown. (Step S15: Dependency Relationship Extraction Process)

[0037] The dependency relationship extraction unit 222 extracts dependency relationships between tasks. It then generates dependency relationship information 35, which specifies the dependency relationships. The dependency relationship extraction unit 222 writes this information to memory 13. A dependency relationship indicates that there is a task Y that must be completed before a task X can be executed. Task X is referred to as the dependency origin task, and task Y is referred to as the dependency target task.

[0038] Specifically, the dependency relationship extraction unit 222 refers to the dependency target task in the task information 32 assumed in step S12 to extract a dependency relationship. The dependency relationship extraction unit 222 extracts a task specified by the task name in the task information 32 as the dependency source task and extracts a task specified by the dependency target as the dependency target task. As a result, the dependency relationship information 35 is generated, specifying the dependency source task and the dependency target task, as shown in Fig. 8 shown.

[0039] A dependency relationship does not have to be one-to-one. For a dependency origin task, there can be a multitude of dependency target tasks. For a dependency target task, there can be a multitude of dependency origin tasks.

[0040] In step S13, the allocation acceptance unit 213 can update the allocation availability in the resource information 31 for the resource specified by the resource name to "Allocation not available" for the allocation period. This prevents the same resource from being assigned to a large number of tasks in overlapping periods.

[0041] Alternatively, if the same resource is assigned to a large number of tasks in overlapping periods in step S13, notification unit 24 can notify the user terminals 50 used by the people responsible for those tasks. This can help resolve a resource conflict. If the same resource is assigned to a large number of tasks in closely spaced periods, even if the periods do not overlap, notification unit 24 can notify the user terminals 50 used by the people responsible for those tasks. This allows for the early detection of a resource conflict if a delay occurs in the execution of a particular task.

[0042] The work management unit 10 can enable the resource information 31, task information 32, assignment information 33, assignment relationship information 34, and dependency relationship information 35 to be referenced from the user terminal device 50. Alternatively, the work management unit 10 can display the resource information 31, task information 32, assignment information 33, assignment relationship information 34, and dependency relationship information 35 on the display device 142 upon request.

[0043] In Fig. Section 9 describes the process for identifying affected tasks according to embodiment 1. (Step S21: Progress Assumption Process)

[0044] The progress acceptance unit 214 accepts input of progress information for a task. Here, the progress acceptance unit 214 accepts delay information as progress information, indicating a delay task, i.e., a task where a delay may occur.

[0045] The progress acceptance unit 214 accepts, in particular, the delay information entered by one of the user terminals 50. Alternatively, the progress acceptance unit 214 can accept the delay information entered by operating the input device 141. The delay information is entered, for example, by the person responsible for the delay task. (Step S22: Process of identifying the dependent task)

[0046] The impact identification unit 23 identifies a dependency origin task whose dependency target task is the delay task, which is specified as the affected task by the delay information assumed in step S21, and which may be affected by a delay of the delay task.

[0047] Specifically, the impact identification unit 23 identifies a data record in which the delay task is set as the dependency target task in the dependency relationship information 35. The impact identification unit 23 identifies the dependency origin task in the identified data record as the affected task. (Step S23: First process of determining existence)

[0048] The impact identification unit 23 identifies in step S22 whether an affected task has been identified.

[0049] If an affected task is identified, the impact identification unit 23 forwards processing to step S24. If no affected task is identified, the impact identification unit 23 skips step S24 and forwards processing to step S25. (Step S24: First notification process)

[0050] Notification Unit 24 notifies the person responsible for the affected task identified in step S22.

[0051] Specifically, the notification unit 24 sends a message containing the task name of the affected task to the user terminal 50, which is used by the person responsible for the affected task. The notification unit 24 can display the task name of the affected task, etc., on the display device 142. At this time, the notification unit 24 can also provide information about the delayed task. This information includes details such as the execution period, allocated resources, and the execution status of the delayed task. The execution status refers to the progress rate, the condition of a delay, or the likelihood of a delay occurring, etc. (Step S25: Resource Identification Process)

[0052] The impact identification unit 23 identifies a resource that is associated with the delay task specified by the delay information assumed in step S21.

[0053] Specifically, the impact identification unit 23 uses the assignment relationship information 34 to identify a data record in which the task name of the delay task is specified. The impact identification unit 23 identifies the resource name of the resource set in the extracted data record. (Step S26: Identification process of the same assignment task)

[0054] Impact identification unit 23 identifies a task that is assigned the same resource as the resource identified in step S25.

[0055] Specifically, the impact identification unit 23 identifies records where the resource name identified in step S25 is specified from the assignment relationship information 34. The impact identification unit 23 identifies, among the identified records, a task name for each record that is not the record of the delay task. (Step S27: Execution period identification process)

[0056] The impact identification unit 23 identifies, among the tasks identified in step S26, a task that is identified as starting within a reference time period after the execution of the delay task has ended, as an affected task that may be affected by a delay of the delay task.

[0057] Specifically, the impact identification unit 23 uses task information 32 to identify the data record in which the name of the delay task is specified. Impact identification unit 23 identifies the end date and time of the execution period specified in the extracted data record. Impact identification unit 23 identifies the data record with the task name identified in step S26 using task information 32. Impact identification unit 23 identifies the start date and time of the execution period specified in the identified data record. Impact identification unit 23 determines whether the identified start date and time are within the reference time period after the identified end date and time.If the start date and start time are within the reference time period after the identified end time, the impact identification unit 23 identifies the task specified by the task name as the affected task. (Step S28: Second existence determination process)

[0058] The impact identification unit 23 determines in step S27 whether an affected task has been identified.

[0059] If an affected task is identified, the impact identification unit 23 forwards processing to step S29. If no affected task is identified, the impact identification unit 23 skips step S29 and terminates processing. (Step S29: Second notification process)

[0060] Notification Unit 24 notifies the person responsible for the affected task identified in step S27.

[0061] Specifically, the notification unit 24 sends a message containing the task name of the affected task to the user terminal 50, which is assigned to the person responsible for the affected task. The notification unit 24 can display the task name of the affected task, etc., on the display device 142. At this time, the notification unit 24 can also provide information about the delay task, as described in step S24.

[0062] Notification Unit 24 can change the content of the notification between step S24 and step S29. For example, in step S24, Notification Unit 24 notifies that a delay may occur with the dependency origin task. In step S29, Notification Unit 24 notifies that a delay may occur with a task that has a resource conflict. *** Effects of embodiment 1 ***

[0063] As described above, the work management device 10, according to embodiment 1, identifies a task assigned the same resource as a resource assigned to a delay task as an affected task. In this way, it is possible to identify a task that might be affected by a delay of the delay task due to a resource conflict.

[0064] If a delay in the delay task due to a resource conflict could have an impact, possible countermeasures include changing the allocated resource and changing the task's execution period. This can prevent a delay in the affected task caused by a delay in the delay task.

[0065] The work management device 10 according to embodiment 1 identifies as an affected task a task that begins within a reference time period after the completion of a delay task. In this way, it is possible to identify only one task that is likely to be affected among the tasks to which the same resource is assigned.

[0066] The work management device 10 according to embodiment 1 identifies as an affected task a task that depends on a delay task. In this way, it is possible to identify a task that, due to a dependency between the tasks, may be affected by a delay of the delay task.

[0067] If a delay in the delay task could have an impact due to dependencies between the tasks, possible countermeasures include changing the execution period of the task. This can prevent a delay in the affected task from also being caused by delaying the delay task.

[0068] The work management device 10 according to embodiment 1 prevents the same resource from being assigned to a large number of tasks in the same period. This avoids a waiting state due to a resource conflict.

[0069] The work management device 10 according to embodiment 1 allows the resource information 31, the task information 32, the assignment information 33, the assignment relationship information 34, and the dependency relationship information 35 to be referenced from the user terminal device 50 or the like. When multiple managers manage tasks, this allows each manager to know individual plans for the tasks and resources assigned to each task.

[0070] The work management device 10 according to embodiment 1 is suitable for a use case in which one or more project managers perform process management in a situation where resources such as personnel, computers, and locations are needed to perform a variety of tasks. In particular, the work management device 10 according to embodiment 1 is suitable for a use case in which a large number of project managers perform process management. A project manager is a person responsible for managing the progress of a project.

[0071] In a testing process during system development, it is common practice for multiple people responsible for testing to manage each test element separately, along with the personnel and computer resources required to execute each test element. The work management facility 10, as described in embodiment 1, is used for the testing process in system development.

[0072] In a situation where multiple individuals responsible for testing share resources to continue testing, a task managed by another responsible individual may be at risk of delay. In this case, Work Management Unit 10 will notify the notified responsible individual that a task managed by them may be affected by the delay. This allows the responsible individual to identify the impact on their task before it occurs. Furthermore, if Work Management Unit 10 is also configured to notify about information concerning the task at risk of delay, this will enable the responsible individual to assess the extent of the impact. *** Other configurations ***<Variante 1>

[0073] In embodiment 1, the functional components are implemented by software. In variant 1, however, the functional components can also be implemented by hardware. The differences between variant 1 and embodiment 1 are described below.

[0074] Based on Fig. Section 10 describes a configuration of the work management facility 10 according to variant 1.

[0075] If the functional components are implemented by hardware, the work management device 10 contains an electronic circuit 15 instead of the processor 11, the main memory 12 and the storage 13. The electronic circuit 15 is a dedicated electronic circuit that implements the functions of the functional components, the main memory 12 and the storage 13.

[0076] The electronic circuit 15 can be a single integrated circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0077] The functional components can be implemented by one electronic circuit 15, or the functional components can be distributed across a multitude of electronic circuits 15 and implemented by them. <Variante 2>

[0078] In variant 2, some of the functional components can be implemented by hardware and the rest of the functional components by software.

[0079] Each of the processor 11, the main memory 12, the storage 13, and the electronic circuit 15 is referred to as a processing circuit. This means that the functions of the functional components are implemented by the processing circuit.

[0080] “Unit” in the above description can be interpreted as “circuit”, “step”, “sequence”, “process” or “processing circuit”.

[0081] The embodiment and variants of the present disclosure have been explained above. Two or more of these embodiments and variants can be implemented in combination. Alternatively, one, two, or more of them can be partially implemented. The present disclosure is not limited to the embodiment and variants mentioned above, and various modifications can be made as required. Reference symbol list

[0082] 100: Work management system, 10: Work management unit, 11: Processor, 12: RAM, 13: Memory, 14: Communication interface, 141: Input unit, 142: Display unit, 21: Acceptance unit, 22: Relationship extraction unit, 23: Impact identification unit, 24: Notification unit, 211: Resource acceptance unit, 212: Task acceptance unit, 213: Assignment acceptance unit, 214: Progress acceptance unit, 221: Resource relationship extraction unit, 222: Dependency relationship extraction unit, 31: Resource information, 32: Task information, 33: Assignment information, 34: Assignment relationship information, 35: Dependency relationship information, 50: User terminal, 60: Network. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2016-099766 A

[0004]

Claims

[1] Employment administration facility, comprising: a progress acceptance unit for accepting delay information indicating a delay task, wherein the delay task is a task in which a delay may occur; and an impact identification unit for referring to assignment relationship information indicating resources respectively assigned to a plurality of tasks to identify a task to which a same resource is assigned as a resource assigned to the delay task indicated by the delay information assumed by the progress assumption unit as an affected task that may be affected by a delay in the delay task. [2] The work management device according to claim 1, wherein the impact identification unit identifies, as the affected task, a task scheduled to start within a reference time period after completion of execution of the delay task, among the tasks to which the same resource as the resource assigned to the delay task is assigned. [3] The work management device according to claim 1 or 2, wherein the impact identification unit refers to dependency relationship information indicating a dependency relationship between tasks to identify a task dependent on the delayed task as the affected task. [4] The work management device according to claim 3, wherein the dependency relationship indicates that the completion of a dependency target task is a request for the execution of a dependency source task. [5] The work management device according to any one of claims 1 to 4, further comprising a notification unit for notifying a person in charge of the affected task identified by the impact identification unit. [6] Employment administration procedures, including: Accepting, by a computer, delay information indicating a delay task, wherein the delay task is a task in which a delay may occur; and Referring to allocation relationship information indicating resources each allocated to a plurality of tasks to identify, by a computer, a task allocated a same resource as a resource allocated to the delay task indicated by the delay information as an affected task that may be affected by a delay in the delay task. [7] Work management program that causes a computer to function as a work management device to perform: a progress acceptance process of accepting delay information indicating a delay task, wherein the delay task is a task in which a delay may occur; and an impact identification process of referring to assignment relationship information indicating resources each assigned to a plurality of tasks to identify a task to which a same resource is assigned as a resource assigned to the delay task indicated by the delay information assumed by the progress assumption process as an affected task that may be affected by a delay in the delay task.

Images