Management system and management program

Abstract

To provide a management system and a management program capable of managing setups.SOLUTION: A server device 2 for managing processes being steps in a case of dividing construction into the plurality of steps or setups belonging to work performed at the processes comprises: aggregation means which aggregates second setup related information DB 225 in which setup state information indicating a setup state is stored, and the setup state indicated by the setup state information stored in the second setup related information DB 225, on the basis of a prescribed reference; and display means which displays setup display information indicating the setup state aggregated by the aggregation means. The aggregation means performs processing which aggregates the setup state on the basis of a type of a setup object being an object of the setup, processing which aggregates the setup state on the basis of the work to which the setup belongs, or processing which aggregates the setup state on the basis of the process to which the setup belongs.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a management system and a management program. [Background technology]

[0002] Conventionally, techniques for managing the progress of a project have been known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-095917 A Summary of the Invention [Problem to be solved by the invention]

[0004] Meanwhile, there has been a demand for a technique for managing the setup, which is the preparation for carrying out a target task.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to provide a management system and a management program that are capable of managing setup. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objective, the management system described in claim 1 is a management system for managing setups belonging to a process which is a stage when a construction project is divided into multiple stages, or work performed in the process, and comprises a storage means for storing setup status information indicating the status of the setups, an aggregation means for aggregating the setup status indicated by the setup status information stored in the storage means based on a predetermined criterion, and a display means for displaying setup display information indicating the setup status aggregated in the aggregation means.

[0007] The management system of claim 2 is the management system of claim 1, wherein the aggregation means performs a process of aggregating the status of the setup based on a type of setup object that is the subject of the setup, a process of aggregating the status of the setup based on the operation to which the setup belongs, or a process of aggregating the status of the setup based on the process to which the setup belongs.

[0008] The management system according to a third aspect of the present invention is the management system according to the second aspect, wherein the type of the setup target is a predetermined type that is determined in advance for the construction work.

[0009] The management system according to a fourth aspect of the present invention is the management system according to the third aspect, wherein the type of the setup object includes one or more types of labor, materials, construction machines, space, and information related to the construction work.

[0010] The management system according to claim 5 is the management system according to claim 1, further comprising an output means for outputting a candidate setup schedule that is a candidate for setting the setup for the work, based on a type of the setup target.

[0011] The management system of claim 6 is the management system of claim 1, wherein the aggregation means aggregates the status of the setup by type of the setup object based on the type of the setup object that is the subject of the setup, and the display means displays information indicating the status of the setup aggregated by the aggregation means as the setup display information.

[0012] The management system of claim 7 is the management system of claim 1, wherein the aggregation means performs a first aggregation process of aggregating the status of the setup by type of setup object based on the type of setup object that is the subject of the setup, and a second aggregation process of further aggregating the status of the setup aggregated in the first aggregation process by task unit or process unit to which the setup belongs based on the work or process to which the setup belongs, and the display means displays information indicating the status of the setup aggregated in the first aggregation process and information indicating the status of the setup aggregated in the second aggregation process as the setup display information.

[0013] The management system of claim 8 is the management system of claim 1, wherein the aggregation means performs a third aggregation process of aggregating a state of the setup at the task unit to which the setup belongs based on the work to which the setup belongs, and a fourth aggregation process of further aggregating the state of the setup aggregated in the third aggregation process at the process unit to which the work belongs based on the process to which the work belongs, and the display means displays information indicating the state of the setup aggregated in the third aggregation process and information indicating the state of the setup aggregated in the fourth aggregation process as the setup display information.

[0014] The management program described in claim 9 is a management program for managing setups belonging to a process that is a stage when a construction project is divided into a plurality of stages, or work to be performed in the process, and causes a computer to function as a storage means for storing setup status information indicating the status of the setup, an aggregation means for aggregating the setup status indicated by the setup status information stored in the storage means based on a predetermined criterion, and a display means for displaying setup display information indicating the setup status aggregated in the aggregation means. Effect of the Invention

[0015] According to the management system described in claim 1 and the management program described in claim 9, by displaying setup display information indicating the aggregated setup status, it becomes possible to manage setup, for example, using the setup display information.

[0016] According to the management system described in claim 2, by aggregating the setup status based on the type of setup object, the work, or the process, for example, the setup status can be effectively aggregated, thereby making it possible to appropriately manage the setup.

[0017] According to the management system described in claim 3, the type of the setup object is a predetermined type that is determined in advance for the construction work, so that, for example, an appropriate type can be used, thereby making it possible to appropriately manage the setup.

[0018] According to the management system described in claim 4, the types of setup objects include types related to one or more of labor, materials, construction machinery, space, or information related to the construction, so that appropriate types can be used in accordance with the actual conditions of the construction, making it possible to appropriately manage the setup.

[0019] According to the management system of claim 5, by outputting candidate setup schedules based on the type of setup target, it is possible to improve convenience regarding setup schedules, for example.

[0020] According to the management system described in claim 6, by aggregating the setup status by type of setup object, for example, the setup status can be effectively aggregated, making it possible to appropriately manage the setup.

[0021] According to the management system described in claim 7, the setup status can be aggregated by type of setup object and further aggregated by task or process, for example, so that setup can be appropriately aggregated at multiple stages, thereby making it possible to appropriately manage the setup.

[0022] According to the management system described in claim 8, the setup status can be aggregated by task and then further aggregated by process, for example, so that the setup status can be appropriately aggregated at multiple stages, thereby making it possible to appropriately manage the setup. [Brief description of the drawings]

[0023] [Figure 1] 1 is a block diagram showing a functional concept of an information processing system according to an embodiment of the present invention; [Diagram 2] FIG. 11 is a diagram illustrating example person in charge information. [Diagram 3] FIG. 11 is a diagram illustrating an example of process-related information. [Figure 4] FIG. 11 is a diagram illustrating an example of work-related information. [Diagram 5] FIG. 11 is a diagram illustrating an example of first setup related information. [Figure 6] FIG. [Figure 7] FIG. [Figure 8] FIG. 1 is an explanatory diagram of a classification of setups. [Figure 9] FIG. 1 is an explanatory diagram of a classification of setups. [Figure 10] FIG. 11 is a diagram illustrating an example of second setup related information. [Figure 11] FIG. 11 is a diagram illustrating an example of a setup state (setup state information). [Figure 12] FIG. 11 is an explanatory diagram of an aggregation process. [Figure 13] FIG. 11 is an explanatory diagram of an aggregation process. [Figure 14] FIG. 11 is an explanatory diagram of an aggregation process. [Figure 15] 13 is a display example of a calendar screen. [Figure 16] FIG. 13 is an explanatory diagram of a calendar screen. [Figure 17] 11A and 11B are diagrams illustrating example setup states displayed by index information on each screen. [Figure 18] 13 is a display example of a list screen. [Figure 19] FIG. 11 is an explanatory diagram of index information. [Figure 20]13 is a display example of a first tree screen. [Figure 21] 13 is a display example of a second tree screen. [Figure 22] 13 is a display example of the third tree screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of a management system and a management program according to the present invention will be described in detail with reference to the accompanying drawings.

[0025] [I] Basic Concept of the Embodiment First, a basic concept of the embodiment will be described. The embodiment relates to a management system and a management program. The management system according to the present invention is a system for managing setups belonging to processes or tasks.

[0026] A "process" is a concept that indicates a stage when construction work is divided into multiple stages. A "task" is a concept that indicates the work that is the subject of setup, and includes, for example, construction work or any other type of work. A "setup" is a concept that indicates the preparation for carrying out a task.

[0027] The definitions of these processes, tasks, and setups are not limited to those shown here, and other definitions commonly used in society may be applied. Note that in this embodiment, for example, a case will be described in which one or more tasks belong to a process, and performing one or more tasks belonging to a process corresponds to performing the process.

[0028] "Managing the setup" is a concept that includes displaying various information related to the setup.

[0029] In the embodiment described below, a case will be described in which the "management system" is applied to the construction field, and the "work" is work related to construction work.

[0030] [II] Specific Contents of the Embodiments Next, the specific contents of the embodiment will be described.

[0031] (composition) First, FIG. 1 is a block diagram showing a functional concept of an information processing system according to the present embodiment.

[0032] (Configuration - Information Processing System) 1 includes, for example, a terminal device 1 and a server device 2, and these devices are capable of communicating with each other. Note that the information processing system 100 includes a plurality of terminal devices carried by various users, but in this embodiment, the information processing system 100 will be described by illustrating one terminal device 1 in FIG. 1 as a representative example.

[0033] (Configuration - Information Processing System - Terminal Device) 1 is a device carried by a user, such as a smartphone or a tablet terminal, and includes, for example, a communication unit 11, a touch pad 12, a display 13, a recording unit 14, and a control unit 15. Note that the terminal device 1 is not limited to this, and for example, a personal computer may be used as the terminal device 1.

[0034] The communication unit 11 is a communication means for communicating with an external device (for example, the server device 2). The touch pad 12 is an operation means for receiving various operation inputs from a user. The display 13 is an image display means for displaying various information or images, and for example, the touch pad 12 and the display 13 are integrally formed as a touch panel. The recording unit 14 is a recording means for recording programs and various data. The control unit 15 is a control means for controlling the terminal device 1, and is configured using, for example, internal memories such as a CPU, a RAM, and a ROM (the same applies to the control units of other devices).

[0035] (Configuration - Information Processing System - Server Device) The server device 2 in FIG. 1 is a management system, and includes, for example, a communication unit 21, a recording unit 22, and a control unit 23.

[0036] (Configuration - Information processing system - Server device - Communication unit) The communication unit 21 in FIG. 1 is a communication unit that communicates with an external device (for example, the terminal device 1).

[0037] (Configuration - Information processing system - Server device - Recording unit) 1 is a recording means for recording programs and various data necessary for the operation of the server device 2. The recording unit 22 includes, for example, a person in charge information database 221 (hereinafter, database is referred to as "DB"), a process related information DB222, a work related information DB223, a first setup related information DB224, and a second setup related information DB225.

[0038] In this embodiment, for the sake of convenience, information regarding setup is stored separately in two DBs, the first setup related information DB 224 and the second setup related information DB 225. However, these DBs may be integrated or distributed among three or more DBs.

[0039] (Configuration - Information processing system - Server device - Recording unit - Personnel information DB) The person in charge information DB 221 in FIG. 1 is a person in charge information storage unit that stores person in charge information.

[0040] Fig. 2 is a diagram showing an example of person in charge information. Note that in Fig. 2, specific illustrations of some information are omitted for convenience of explanation, and are shown as "...". "Person in charge information" is information about a user such as a person in charge of arrangements, etc., and for example, information of each item shown in Fig. 2 is mutually associated.

[0041] The person in charge ID in FIG. 2 is person in charge identification information (hereinafter, identification information will also be referred to as "ID") that uniquely identifies the person in charge (e.g., "ID0001" in FIG. 2). The person in charge identification information in FIG. 2 is information that identifies the person in charge (e.g., "AA AA" in FIG. 2, which indicates the name of the person in charge, and "Company A" which indicates the name of the company to which the person in charge belongs). Note that "AA AA," "Company A," etc. in FIG. 2 are written for the sake of convenience of explanation and indicate names.

[0042] The information shown in the top row of such person in charge information in Figure 2, for example, indicates that the name of the person in charge identified by "ID0001" is "AA AA" and that the company to which "AA AA" belongs is "Company A."

[0043] It should be noted that this person in charge information is stored by, for example, an administrator inputting information to the server device 2 (the same applies to process-related information, work-related information, and first setup-related information, which will be described later).

[0044] (Configuration - Information processing system - Server device - Recording unit - Process related information DB) The process related information DB 222 in FIG. 1 is a process related information storage means for storing the process related information.

[0045] 3 is a diagram showing an example of process-related information. "Process-related information" is information related to a process, and for example, information on each item shown in FIG. 3 is related to each other.

[0046] The process ID in FIG. 3 is information that uniquely identifies a process (e.g., "ID1001" in FIG. 3). The process name information in FIG. 2 is information that indicates the name of the process (e.g., "1FA Work Area Reinforcement" in FIG. 3). The period information in FIG. 3 is information that indicates the period to which the process is assigned (e.g., "August 9, 2021 - August 11, 2021" in FIG. 3, indicating that the process is assigned from August 9, 2021 to August 11, 2021). The person in charge ID in FIG. 3 is information that identifies a user who is in charge of the process (as an example, the person responsible for the process) (in FIG. 3, one of the information of the person in charge ID in FIG. 2 is used, e.g., "ID0001").

[0047] For example, the top row of such process-related information in Figure 3 indicates that the name of the process identified by "ID1001" is "1F1 Work Section Reinforcement," that the period allocated to the process (i.e., the period during which the process is scheduled to be carried out) is from August 9, 2021 to August 11, 2021, and that the person responsible for the process is the user identified by "ID0001."

[0048] (Configuration - Information processing system - Server device - Recording unit - Work-related information DB) The work-related information DB 223 in FIG. 1 is a work-related information storage means for storing work-related information.

[0049] 4 is a diagram illustrating an example of work-related information. The "work-related information" is information related to work, and for example, the information items shown in FIG. 4 are associated with each other.

[0050] The work ID in FIG. 4 is a work ID that uniquely identifies the work (e.g., "ID2001" in FIG. 4). The related process ID in FIG. 4 is a related process ID that identifies the process to which the work belongs (e.g., "ID1001" in FIG. 4, any of the process IDs in FIG. 3 are used). The work name information in FIG. 4 is information that indicates the name of the work (e.g., "material delivery and lifting" in FIG. 4). The period information in FIG. 4 is information that indicates the period assigned to the work (e.g., "August 9, 2021" in FIG. 4). The person in charge ID in FIG. 4 is information that identifies the user who is in charge of the work (as an example, the person responsible for the work) (e.g., "ID0002" in FIG. 4, any of the person in charge IDs in FIG. 2 are used).

[0051] For example, the information at the top of the work-related information in Fig. 4 indicates that the name of the work identified by "ID2001" is "material delivery and lifting," and that the work (i.e., "material delivery and lifting") belongs to the process (i.e., "reinforcement for 1FA work area") identified by "ID1001. It also indicates that the period assigned to the work (i.e., the period during which the work is scheduled to be performed) is August 9, 2021, and that the person responsible for the work is the user identified by "ID0002."

[0052] Furthermore, looking at the related process IDs in Figure 4, the example in Figure 4 shows that the tasks of "Material transportation and lifting", "1FA work area slab reinforcement", and "Removal of unused materials" belong to the process identified by "ID1001" (i.e., the "1FA work area reinforcement" process).

[0053] (Configuration - Information processing system - Server device - Recording unit - First setup related information DB) The first setup related information DB 224 in FIG. 1 is a first setup related information storage means for storing the first setup related information.

[0054] Fig. 5 is a diagram illustrating the first setup-related information, and Figs. 6 and 7 are explanatory diagrams of setup. Fig. 6 is a conceptual diagram for explaining setup, and Fig. 7 is a diagram illustrating the setup defined in this embodiment. Also, the numbers of "tasks" and "setups" and "object types" illustrated in Figs. 6 and 7 are examples, and the contents and numbers can be arbitrary depending on the situation.

[0055] === Setup (Process side setup, Work side setup) === As mentioned above, "setup" is a concept that indicates preparation for carrying out work, and in this embodiment, it will be described as indicating a concept that includes process-side setup (see the right side of Figure 6) and work-side setup (see the left side of Figure 6).

[0056] "Process-side setup" refers to setup that belongs to a process, and specifically, it is a concept that indicates common preparations for performing all tasks that belong to a process. In other words, "process-side setup" is a concept that indicates, for example, common preparations for performing all tasks that belong to a process. Here, for example, if three tasks belong to a specific process, "process-side setup" is a concept that indicates common preparations for performing each of the three tasks.

[0057] "Work-side setup" refers to setup belonging to a work, other than process-side setup, and specifically, it is a concept that indicates individual preparations for performing only a portion of the work belonging to a process. In other words, "work-side setup" is a concept that indicates, for example, individual preparations for performing only a portion of the work belonging to a process. Here, for example, if three tasks belong to a specific process, "work-side setup" is a concept that indicates preparations for performing only one task, or two tasks.

[0058] In this embodiment, each setup will be described as corresponding to only one of process-side setup and operation-side setup.

[0059] ===Arrangements (Classification)=== Figures 8 and 9 are explanatory diagrams of the classification of setups. Each setup can be classified based on "action type" (Figure 8), which is a type based on the action to perform the setup, or "object type" (Figure 9), which is a type based on the object for which the setup is performed.

[0060] ==Action Type== The "action type" is a concept that indicates the type (classification) of the arrangement based on the action taken to make the arrangement for construction work, and includes, for example, the types of arrangement, such as arrangement, processing, adjustment, approval, and agreement, as shown in the "action type" column in Figure 8.

[0061] "Arrangements" is a type of arrangement that corresponds to actions related to making preparations for various matters related to the construction work. "Processing" is a type of arrangement that corresponds to actions related to processing various matters related to the construction work. "Coordination" is a type of arrangement that corresponds to actions related to coordinating various matters related to the construction work. "Approval" is a type of arrangement that corresponds to actions related to approving various matters related to the construction work. "Agreement" is a type of arrangement that corresponds to actions related to coming to an agreement on various matters related to the construction work.

[0062] As the setups belonging to each type, those exemplified in the "Example of Setup" column in FIG. 8 are assumed, but the setups are not limited to these descriptions.

[0063] ==Target Type== "Object type" is a concept that indicates the type (classification) of the setup based on the type of object for which setup is performed for construction work (i.e., the setup object that is the subject of the setup). Note that the type of setup object can be any type (predetermined type) that is predefined for construction work, but here, we will explain the case where labor, materials, information, construction machinery, and space are used, for example. In other words, we will explain the case where "object type" is a concept that includes the types of labor, materials, information, construction machinery, and space, for example, as shown in the "object type" column in Figure 9.

[0064] "Labor" is a concept that indicates a type of setup that targets labor related to construction (for example, labor, or people performing labor such as workers). "Materials" is a concept that indicates a type of setup that targets various materials, parts, or objects (other than construction machinery) including materials related to construction. "Information" is a concept that indicates a type of setup that targets various information related to construction (for example, drawing information such as structural drawings, other information, etc.). "Construction machinery" is a concept that indicates a type of setup that targets machinery used in construction. "Space" is a concept that indicates a type of setup that targets space related to construction.

[0065] In other words, "labor," "materials," "information," "construction machinery," and "space" can also be interpreted as concepts indicating the types of setup in which the types of setup objects are labor, materials, information, construction machinery, and space.

[0066] As the setups belonging to each type, those exemplified in the "Example of Setup" column in FIG. 9 are assumed, but the setups are not limited to these descriptions.

[0067] ===Description of this embodiment=== The system can be configured to focus on one or both of these behavior types and target types for processing, but in the following explanation, we will mainly use an example of processing that focuses on the target type, as shown in Figure 6.

[0068] As shown in Fig. 7, the process of "1FA work area reinforcement" includes the work of "material delivery and lifting", the work of "1FA work area slab reinforcement", and the work of "unused material removal", and the process side setup is set to "request labor from partner companies", and the work side setup is set to "allocation of workers". The example in Fig. 7 corresponds to the information exemplified in the process related information in Fig. 3, the work related information in Fig. 4, and the first setup related information in Fig. 5.

[0069] In particular, the "Labor request to partner companies" in Figure 7 shows the common preparation for carrying out the three tasks ("Material delivery and lifting", "Slab reinforcement for 1FA work area", and "Removal of unused materials") that belong to the "Reinforcement for 1FA work area" process, and is therefore set as a process-side setup.

[0070] In addition, the example of Fig. 7 shows that each process-side setup, for example, "request for labor from partner company," "response to labor request," and "confirmation of labor request," is performed in the order shown by the arrows in Fig. 7, and the target type of each process-side setup is "labor." Also, it shows that each work-side setup, for example, "reservation of lifting machine" and "adjustment of lifting machine" is performed in the order shown by the arrows in Fig. 7, and the target type of each work-side setup is "construction machine."

[0071] ===First step related information=== The "first setup related information" stored in the first setup related information DB 224 in FIG. 1 is setup related information, that is, information related to setup, in which, for example, information on each item shown in FIG. 5 is mutually associated.

[0072] ===Schedule ID=== The setup ID in FIG. 5 is a setup ID that uniquely identifies the setup (eg, "ID3001" in FIG. 5).

[0073] ===Related Process ID=== The related process ID in Fig. 5 is a related process ID that identifies the process to which the setup (specifically, the process-side setup within the process-side setup or the work-side setup) belongs (in Fig. 5, information on one of the process IDs in Fig. 3 is used, such as "ID1001"). For the work-side setup, "x" is recorded as the related process ID.

[0074] That is, by referring to the related process ID in FIG. 5, it is possible to determine whether the corresponding setup is a process-side setup or an operation-side setup (the same applies to the related task ID in FIG. 5).

[0075] ===Related Work ID=== The related work ID in Fig. 5 is a related work ID that identifies the work to which the setup (more specifically, the work-side setup within the process-side setup or the work-side setup) belongs (in Fig. 5, one of the work IDs in Fig. 4 is used, such as "ID2001"). Note that for process-side setup, "x" is recorded as the related work ID.

[0076] ===Plan name information, target type information, action type information=== The setup name information in FIG. 5 is information indicating the name of the setup (e.g., "Labor request to partner company" in FIG. 5). The object type information in FIG. 5 is information indicating the object type into which the setup is classified (e.g., "Labor" shown in the "Object type" column of FIG. 9 in FIG. 5). The action type information in FIG. 5 is information indicating the action type into which the setup is classified (e.g., "Arrangement" shown in the "Action type" column of FIG. 8 in FIG. 5).

[0077] ===Order specific information=== The order specification information in Fig. 5 is information indicating the execution order of each setup. The specific contents of the order specification information in Fig. 5 are arbitrary, but for example, information is exemplified in which the execution order is specified using the setup IDs immediately before and after each setup. In Fig. 5, an example is "Previous: x, Next: ID3002", which indicates that there is no immediately preceding setup and the immediately following setup is the setup identified by "ID3002".

[0078] In this embodiment, an example is given of a case in which order specification information is stored and the order in which each setup is to be performed can be specified, but the technology of the present invention is applicable even if the order in which each setup is to be performed cannot be specified.

[0079] ===Contact ID=== The person in charge ID in Figure 5 is information that identifies a user who is a person in charge of the setup (as an example, a person responsible for the setup) (in Figure 5, one of the information of the person in charge ID in Figure 2 is used, such as "ID0001").

[0080] ===Example=== 5, for example, the top row of the first setup-related information indicates that the setup identified by "ID3001" is a process-side setup belonging to the process identified by "ID1001." It also indicates that the name of the setup is "Labor request to partner company," and that the target type and action type of the setup are "Labor" and "Arrangement." It also indicates that there is no setup immediately before the setup in terms of the execution order, and that the setup immediately after is the setup identified by "ID3002," and that the person in charge of the setup is the person identified by "ID0001."

[0081] 5 indicates that the setup identified by "ID3051" is an operation-side setup belonging to the operation identified by "ID2001." The first setup-related information in FIG. 5 stores information related to each setup, etc., as shown in FIG. 7.

[0082] (Configuration - Information processing system - Server device - Recording unit - Second setup related information DB) The second setup related information DB 225 in FIG. 1 is a second setup related information storage means for storing the second setup related information.

[0083] 10 is a diagram illustrating an example of the second setup related information. The "second setup related information" is setup related information, which is information related to setup, and for example, information on each item shown in FIG. 10 is related to each other.

[0084] === Setup ID, Setup name information === The setup ID and setup name information in FIG. 10 are the same as the information of the same names in FIG.

[0085] === Setup status information === 10 is information showing a setup state, which is a setup state. In the following description, for example, "normal", "caution", "urgent", and "other" are used as the setup state information.

[0086] Fig. 11 is a diagram illustrating an example of a setup state (setup state information). Note that Fig. 11 illustrates setup states classified into each action type. In this embodiment, the setup state will be described using the example of Fig. 11, but is not limited to this.

[0087] In FIG. 11, "Arranged" shown in the column corresponding to "Setup Status" = "Normal" and "Action Type" = "Arrangement" illustrates an example in which, for a setup classified as an action type of "Arrangement", the state in which arrangements have already been completed (i.e., in the example of FIG. 8, the state in which "request for labor from partner company" has already been completed) corresponds to "Normal". The same is true for the other columns, so their explanation will be omitted. Note that "gray", "green", etc. in the "Display Color" column are examples of colors used when displaying the status of the corresponding setup, and will be described later.

[0088] "Setup status" is a concept that indicates the state or condition of the setup. The setup status information is arbitrary, but in this embodiment, for example, a case where "normal", "caution", "urgent", and "other" are used will be described. That is, a case where "normal", "caution", "urgent", and "other" are used as the setup status information in FIG. 10 will be described.

[0089] "Normal" indicates a state in which there is no problem with the progress of the setup and no need to take any measures regarding the setup. "Normal" indicates, for example, a state in which the setup has already been completed, as illustrated in the column corresponding to "Setup Status" = "Normal" in Fig. 11. Note that Fig. 11 also illustrates other specific states, but as they are as illustrated, detailed description will be omitted.

[0090] "Caution" indicates a state where there is currently no problem with the progress of the setup, but if things continue as they are, it may become necessary to take some kind of measure regarding the setup. "Caution" indicates a state where, for example, the current date has not passed the arrangement deadline, but has passed (exceeded) the recommended arrangement date (a day before the arrangement deadline, and if arrangements are made on this date, there is a margin of error, etc.) as shown in the column corresponding to "Setup Status" = "Caution" in Figure 11.

[0091] "Urgent" indicates a state where there is a problem with the progress of the arrangement, and some kind of measure needs to be taken regarding the arrangement. "Urgent" indicates a state where, for example, the current day has passed (exceeded) the deadline for arrangement, as shown in the column corresponding to "Arrangement Status" = "Urgent" in Figure 11.

[0092] "Other" refers to a status other than "Normal," "Caution," and "Urgent." As shown in the column corresponding to "Arrangement Status" = "Other" in Fig. 11, "Other" refers to a status in which, for example, the current day is before the recommended arrangement date and has not yet passed.

[0093] It should be noted that "Normal", "Caution", "Urgent", and "Other" can be interpreted as indicating a state related to the attention level, which is the relative degree to which the user managing the progress of the setup should pay attention. For example, among the four states, "Urgent" may be interpreted as indicating a state corresponding to the highest attention level, "Caution" as indicating a state corresponding to the second highest attention level, "Normal" as indicating a state corresponding to the third highest attention level, and "Other" as indicating a state corresponding to the lowest attention level. From the viewpoint of smoothly progressing the setup, it is important to display, for example, a state with a higher attention level more conspicuously so that measures related to the setup can be taken promptly and appropriately. The display of the states will be described later.

[0094] ===Variations=== Although the case where "normal", "caution", "urgent", and "other" are used as the "state of setup" has been described here, for example, "other" may be omitted and the remaining three states may be used. In this case, all states other than "caution" and "urgent" may be configured to be treated as "normal".

[0095] In addition, the system may be configured to use any two of the four states described above as the "setup state," or other states may be added to use five or more states.

[0096] In addition, the state of each setup may be determined on a target type (FIG. 9) basis regardless of the action type, or may be determined on a setup basis regardless of the type.

[0097] ===Example of setup status information=== For example, the top row of the second setup-related information in Figure 10 indicates that the name of the setup identified by "ID3001" is "Labor request to cooperating company" and that the setup status of the "Labor request to cooperating company" is "Normal."

[0098] ===Storage method=== For example, the setup ID and setup name information of this second setup-related information are stored as the same information as the information of the same name in Figure 5, and the setup status information is stored by executing the setup status information storage process described below.

[0099] (Configuration - Information processing system - Server device - Control unit) The control unit 23 in FIG. 1 is a control unit that controls the server device 2, and conceptually functions as, for example, an aggregating unit and a display unit.

[0100] ===Aggregation methods=== The "aggregation means" is a means for aggregating the setup states indicated by the setup state information stored in the storage means based on a predetermined criterion.

[0101] The "aggregation means" aggregates the setup status based on the type of setup object that is the target of the setup, aggregates the setup status based on the work to which the setup belongs, or aggregates the setup status based on the process to which the setup belongs. The "aggregation means" aggregates the setup status by type of setup object, for example, based on the type of setup object that is the target of the setup.

[0102] The "aggregation means" performs, for example, a first aggregation process that aggregates the status of setups by type of setup object based on the type of setup object that is the subject of the setup, and a second aggregation process that further aggregates the status of setups aggregated in the first aggregation process by task unit or process unit to which the setup belongs based on the task or process to which the setup belongs.

[0103] The "aggregation means" performs, for example, a third aggregation process that aggregates the state of a setup by task unit to which the setup belongs based on the work to which the setup belongs, and a fourth aggregation process that further aggregates the state of the setup aggregated in the third aggregation process by process unit to which the work belongs based on the process to which the work belongs.

[0104] ===Display means=== The "display means" is a means for displaying setup display information that shows the setup status aggregated in the aggregation means.

[0105] The "display means" displays, for example, information indicating the setup status aggregated in the aggregation means as setup display information. The "display means" displays, for example, information indicating the setup status aggregated in the first aggregation process and information indicating the setup status aggregated in the second aggregation process as setup display information. The "display means" displays, for example, information indicating the setup status aggregated in the third aggregation process and information indicating the setup status aggregated in the fourth aggregation process as setup display information.

[0106] The processing performed by the control unit 23 will be described later.

[0107] (process) Next, the setup status information storage process, aggregation process, calendar screen display process, list screen display process, first tree screen display process, second tree screen display process, and third tree screen display process executed by the information processing system 100 according to this embodiment will be described.

[0108] (Processing - Setup status information storage processing) First, the setup status information storage process will be described. The setup status information storage process is generally executed by the server device 2, and is, for example, a process for storing the setup status information in the second setup-related information in FIG.

[0109] ===Assumptions=== It is assumed that the recording unit 22 of the server device 2 stores judgment criteria information indicating judgment criteria for determining the setup status ("Other", "Normal", "Caution", and "Urgent" in FIG. 11) for each setup shown in the first setup-related information in FIG. 5.

[0110] Here, for example, for "request for labor from partner company" in FIG. 5, the action type is "arrangement", so for example, information for judging according to the criteria shown in the "action type"="arrangement" column in FIG. 11 (for example, specific dates for the recommended arrangement date and the deadline for arrangement, and information indicating that if the current day is before the recommended arrangement date, it is judged as "other", and if arrangements have been made, it is judged as "normal", as shown in FIG. 11) is stored as the judgment criteria information. Also, for "adjustment of heavy equipment" in FIG. 5, the action type is "adjustment", so for example, information for judging according to the criteria shown in the "action type"="adjustment" column in FIG. 11 is stored as the judgment criteria information. Note that judgment criteria information is similarly stored for all other arrangements.

[0111] In addition, when a person in charge of each setup has performed the setup, information regarding the performed setup (also referred to as "input information for determining the setup status") (for example, information indicating that a labor request to a cooperating company has been completed, and various information used to determine the setup status) is configured to be transmitted from the person in charge's device (for example, a computer used by the person in charge, or a server device of the system used by the person in charge, etc.) to the server device 2.

[0112] ===Processing=== Regarding the process, the control unit 23 of the server device 2 repeatedly executes the process of determining the setup state of each setup indicated by the first setup-related information in Fig. 5 at a predetermined time interval (e.g., every 5 to 10 seconds, etc.) based on the determination criteria information recorded in the recording unit 22 and the setup state determination input information received by itself, thereby repeatedly determining the setup state of each setup. Then, for each setup, information indicating the setup state determined most recently is stored as the setup state information in Fig. 10.

[0113] ===Variations=== In the above, a case has been described in which the control unit 23 of the server device 2 determines and stores the setup state, but this is not limiting, and for example, a person in charge of setup may determine the state of the setup he or she is in charge of using any method and input information indicating the determined setup state to the server device 2, and the server device 2 may store the information indicating the input setup state as the setup state information in Fig. 10. This concludes the explanation of the setup state information storage process.

[0114] (Processing - Aggregation Processing) Next, the aggregation process will be described. Figs. 12 to 14 are explanatory diagrams of the aggregation process. Note that Fig. 12 illustrates various setup states and the definitions of the setup states. In Figs. 13 and 14, various setup states are illustrated in Figs. 6 and 7. Note that in Figs. 13 and 14, the previously explained "normal", "caution", and "urgent" are illustrated as "〇 normal", "△ caution", and "× urgent". Also, in Figs. 13 and 14, the "other" setup state is not included, but in reality, it can be "other".

[0115] The aggregation process is, in general, a process that is repeatedly executed by the server device 2 at predetermined time intervals (e.g., at intervals of 5 to 10 seconds), and is a process that aggregates, for example, the setup states indicated by the setup state information in the second setup-related information in FIG. 10 based on predetermined criteria.

[0116] ===Predetermined criteria=== The "predetermined criteria" refers to criteria that are determined in advance, and is a concept that includes, for example, criteria that indicate aggregation based on the type of setup object, criteria that indicate aggregation based on work, and criteria that indicate aggregation based on process.

[0117] ===SUMMARY=== "Aggregation" is a concept that indicates gathering and consolidating, for example, a concept that indicates determining a representative setup state by gathering and consolidating one or more setup states. In other words, "aggregation" is a concept that indicates determining a representative setup state in a set of setup states that includes one or more setup states.

[0118] ===Aggregation Techniques=== When a set of setup states (hereinafter simply referred to as a "set") contains multiple types of setup states, the aggregation method for determining which type of setup state to group them into is arbitrary, but in this embodiment, the setup state that has the higher level of attention described above among the setup states included in the set will be described as being defined as the representative setup state.

[0119] That is, for example, with respect to the four types of setup status, "normal," "caution," "urgent," and "other," as described above, the levels of attention are, from highest to lowest, "urgent," "caution," "normal," and "other."

[0120] For example, if "urgent" is included in a set that contains multiple types of setup states, the control unit 23 of the server device 2 will aggregate the set together as "urgent" regardless of the types of other setup states in the set, and determine "urgent" as the representative setup state.

[0121] For example, if a set containing multiple types of setup states does not include "urgent" but does include "caution," the control unit 23 of the server device 2 will aggregate the set to "caution" regardless of the types of other setup states in the set, and will determine "caution" as the representative setup state.

[0122] For example, if a set containing multiple types of setup status does not include "urgent" or "caution" but does include "normal," the control unit 23 of the server device 2 will aggregate the set to "normal" regardless of the types of other setup statuses in the set, and determine "normal" as the representative setup status.

[0123] For example, if a set contains only one type of setup state, the control unit 23 of the server device 2 will aggregate the set into that one type of setup state and determine that one type of setup state as the representative setup state.

[0124] Specifically, for example, in cases where the set of setup states includes only one type of setup state, "Urgent," only one type of setup state, only one type of setup state, only one type of setup state, only one type of setup state, or only one type of setup state, "Other," the control unit 23 of the server device 2 will aggregate the setup states into "Urgent," "Caution," "Normal," and "Other," and define these setup states as representative setup states.

[0125] === Preparation status === Here, details of the setup states used in this embodiment will be described with reference to Fig. 12 to Fig. 14. The explanation will be divided into the setup states shown in the "Setup state" column of Fig. 12. Note that "Number" = "1" in Fig. 13 and Fig. 14, descriptions of individual setup states on the work side, etc. correspond to the information shown in the "Number" column and the "Setup state" column of Fig. 12.

[0126] =Individual setup status on the work side= The individual work-side setup states with "number"="1" in Figs. 12 and 13 are concepts showing the individual setup states of each work-side setup.

[0127] = Resource-based aggregate setup status on the work side = The work-side resource-unit aggregated setup state indicated by "Number" = "2" in Figures 12 and 13 is a concept that indicates the work-side individual setup state aggregated by target type unit (i.e., resource unit) for work-side setups associated with common processes and tasks.

[0128] <Example> In this case, the "work side setup associated with common processes and tasks" refers to, for example, in the example of Figure 7, the setup associated with "material delivery and lifting," which is one task belonging to the "1FA work area reinforcement" process, such as "assignment of workers," "reservation of lifting machine," and "adjustment of lifting machine."

[0129] In addition, "individual work-side setup states aggregated by target type (i.e., resource unit) for work-side setups associated with common processes and tasks" refers to, for example, in the example of Figure 7, an aggregate of individual work-side setup states of "reservation of lifting machine" and "adjustment of lifting machine" for which the target type is "construction machinery."

[0130] = Full integration setup status on the work side = The work-side total aggregated setup state of "Number" = "3" in Figures 12 and 13 is a concept that indicates the work-side resource-unit aggregated setup state aggregated by task unit for work-side setups associated with a common process, and is also a concept that indicates the work-side individual setup states aggregated by task unit for work-side setups associated with a common process.

[0131] <Example> In addition, the "work side setup associated with the common process" here refers to, for example, in the example of Figure 7, the setup associated with "material delivery and lifting," "1FA work area slab reinforcement," and "unused material removal," which are all tasks belonging to the process of "1FA work area reinforcement," such as "worker allocation," "reservation of lifting machine," and "lifting machine adjustment." Note that examples of the setup associated with "1FA work area slab reinforcement" and "unused material removal" are omitted for the sake of convenience.

[0132] In addition, "the work-side resource-unit aggregated setup state aggregated by task unit for the work-side setup associated with a common process" refers to, for example, in the example of Figure 7, an aggregate of the work-side resource-unit aggregated setup states of "labor," "construction machinery," and "space" for the task of "material transportation and lifting."

[0133] =Individual setup status on process side= The individual process-side setup state numbered "4" in FIG. 12 and FIG. 13 is a concept showing the individual setup state of each process-side setup.

[0134] = Resource unit aggregate setup status on the process side = The process-side resource-unit aggregated setup state indicated by "Number" = "5" in Figures 12 and 13 is a concept that indicates the process-side individual setup states and work-side individual setup states aggregated by target type unit (i.e., resource unit) for the process-side setup and work-side setup associated with a common process.

[0135] <Example> In this case, "process-side setups and work-side setups associated with a common process" refers to, for example, in the example of Figure 7, process-side setups associated with the "1FA work area reinforcement" process, such as "request for labor from partner companies," and setups associated with all the work belonging to the "1FA work area reinforcement" process, such as "material delivery and lifting," "1FA work area slab reinforcement," and "unwanted material removal," such as "assignment of workers," "reservation of lifting machine," and "adjustment of lifting machine."

[0136] In addition, "individual process-side setup states and individual work-side setup states aggregated by target type (i.e., resource unit) for process-side setups and work-side setups associated with a common process" refers to, for example, in the example of Figure 7, an aggregation of individual process-side setup states such as "request for labor from cooperating company" where the target type is "labor", and individual work-side setup states such as "assignment of workers" where the target type is "labor".

[0137] = Process side full integration setup status = The total process-side aggregated setup state of "Number" = "6" in Figures 12 and 13 is a concept that indicates the process-side resource-unit aggregated setup state aggregated by process unit, and also a concept that indicates the process-side individual setup state and the work-side individual setup state aggregated by process unit.

[0138] <Example> In addition, the "process-side resource unit aggregated setup state aggregated by process unit" here refers to, for example, in the example of Figure 7, an aggregate of process-side resource unit aggregated setup states such as "labor," "construction machinery," and "space" associated with the "1FA work area reinforcement" process.

[0139] In addition, "individual process-side setup states and individual work-side setup states aggregated by process unit" refers to the aggregation of individual process-side setup states such as "request for labor from partner companies," which is a process-side setup associated with the "1FA work area reinforcement" process, and individual work-side setup states such as "allocation of workers," "reservation of lifting machine," and "adjustment of lifting machine," which are setups associated with all the work belonging to the "1FA work area reinforcement" process, such as "material delivery and lifting," "1FA work area slab reinforcement," and "unwanted material removal."

[0140] ===Processing=== For the aggregation process, the control unit 23 of the server device 2 performs the following first and second steps.

[0141] ==First Step== In the first step, each process and the work belonging to each process are identified based on the process related information in Figure 3 and the work related information in Figure 4 (particularly, the related process ID), and further, based on the first setup related information in Figure 5 (particularly, the related process ID, related work ID, and target type information), the process side setup belonging to each process and the target type of the process side setup, the work side setup belonging to each work and the target type of the work side setup are identified.

[0142] Here, for example, the information in FIGS. 3 to 5 is referenced to identify the processes, operations, process-side setups, and the like shown in FIG.

[0143] ==Second Step== In the second step, based on the processing result of the first step and the second setup-related information in Fig. 10 (particularly, setup state information), various setup states of "numbers" = "1" to "6" in Fig. 12 are identified for each setup indicated by the first setup-related information in Fig. 5. In detail, the following processing is performed.

[0144] = Processing for individual setup status on the work side = For the work side individual setup state of "Number" = "1" in Figures 12 and 14, for example, based on the second setup related information (particularly, the setup state information) in Figure 10, the setup state of the work side setup identified in the first step is identified as the work side individual setup state.

[0145] Here, for example, based on the "setup status information" = "urgent" etc. associated with the "worker allocation" in Figure 10, the individual setup status on the work side of the "worker allocation" is identified as "urgent" etc., as shown in Figure 14.

[0146] = Processing for resource-based aggregate setup status on the work side = For the work-side resource-unit aggregated setup state of "Number" = "2" in Figures 12 and 14, for example, a set is generated that includes work-side individual setup states related to work-side setup (the processing result of the above-mentioned "Processing related to individual work-side setup states") that have the same process, work, and target type identified in the first step, and the work-side individual setup states included in the generated set are aggregated to determine and identify the work-side resource-unit aggregated setup state.

[0147] In addition, "work-side setup with common processes, tasks, and target types" may be interpreted as a concept indicating that the tasks to which the work-side setup is associated are common, the processes to which the tasks belong are common, and the target types of the work-side setups are common.

[0148] In addition, the method for aggregating the setup status will be the same as that described above in "===Aggregation Method===" (the same applies to the process of aggregating the setup status in other processes described later).

[0149] Here, for example, as shown in FIG. 14, a set of "labor" including "urgent" for "worker allocation" is generated, and "urgent" is defined and specified as the work-side resource unit aggregated setup state of "labor". Also, as shown in FIG. 14, for example, a set of "construction machinery" including "normal" for "lifting machinery reservation" and "normal" for "lifting machinery adjustment" is generated, and "normal" is defined and specified as the work-side resource unit aggregated setup state of "construction machinery". Also, as shown in FIG. 14, for example, a set of "space" including "normal" for "work area reservation" and "normal" for "adjustment with other processes" is generated, and "normal" is defined and specified as the work-side resource unit aggregated setup state of "space".

[0150] = Processing for all aggregated setup status on the work side = For the work-side total aggregated setup state of "Number" = "3" in Figures 12 and 14, for example, a set is generated that includes work-side resource-unit aggregated setup states for work-side setup (the processing result of the above-mentioned "Processing related to work-side resource-unit aggregated setup states") that have the common processes and tasks identified in the first step, and the work-side total aggregated setup state is determined and identified by aggregating the work-side resource-unit aggregated setup states included in the generated set.

[0151] In addition, "work-side setup in which processes and tasks are common" may be interpreted as a concept indicating that the tasks to which the work-side setup is associated are common, and that the processes to which the tasks belong are common.

[0152] Here, for example, as shown in Fig. 14, a set of "material delivery / lifting weight" including "urgent", "normal", and "normal", which are the work-side resource-unit aggregated setup states of "labor", "construction machinery", and "space", is generated, and "urgent" is determined and specified as the work-side total aggregated setup state of "material delivery / lifting weight". Also, as shown in Fig. 14, for example, "normal" and "normal" are determined and specified as the work-side total aggregated setup states of "1FA work area slab reinforcement" and "unused material removal".

[0153] <Variations> As a variation of the processing here, a set may be generated that includes individual work-side setup states related to the work-side setup that share the processes and tasks identified in the first step (the processing result of the above-mentioned "processing related to individual work-side setup states"), and the individual work-side setup states included in the generated set may be aggregated to determine and identify a total aggregated work-side setup state.

[0154] = Processing for individual setup status on the process side = Regarding the individual process side setup state of "Number" = "4" in Figures 12 and 14, for example, based on the second setup related information (particularly, the setup state information) in Figure 10, the setup state of the process side setup identified in the first step is identified as the individual process side setup state.

[0155] Here, for example, based on the "setup status information" = "normal" etc. associated with the "labor request to cooperating company" in Figure 10, the individual setup status on the process side of the "labor request to cooperating company" is identified as "normal" etc. as shown in Figure 14.

[0156] =Processing for resource-based aggregate setup status on the process side= For the process-side resource-unit aggregated setup state of "Number" = "5" in Figures 12 and 14, for example, a set is generated that includes work-side individual setup states related to work-side setup (the processing result of the above-mentioned "Processing related to individual work-side setup states") and process-side individual setup states related to process-side setup (the processing result of the above-mentioned "Processing related to individual work-side setup states") that have the same process and target type identified in the first step, and the work-side individual setup states and process-side individual setup states included in the generated set are aggregated to determine and identify the process-side resource-unit aggregated setup state.

[0157] In addition, "work-side setup with a common process and target type" may be interpreted as a concept indicating that the processes to which the work-side setup is associated belong to are common, and that the target types of the work-side setup are common. "Process-side setup with a common process and target type" may be interpreted as a concept indicating that the processes to which the process-side setup is associated are common, and that the target types of the process-side setup are common.

[0158] Here, for example, as shown in FIG. 14, a set of "labor" is generated that includes "urgent" for "allocation of worker," "normal" for "labor request to partner company," "normal" for "response to labor request," and "normal" for "confirmation of labor request," and "urgent" is defined and specified as the process-side resource unit aggregation setup status for "labor."

[0159] In reality, when the work-side setup belonging to the tasks in Figure 14, "1FA work area slab reinforcement" and "removal of unused materials", includes a target type of "labor", the aforementioned set of "labor" will additionally include the work-side individual setup status related to this work-side setup. However, since "urgent" for "worker allocation" is included as described above, no matter what type of additional work-side individual setup status is included, "urgent" will be defined and specified as the process-side resource unit aggregated setup status for "labor".

[0160] The process-side resource unit aggregated setup states of "construction machinery" and "space" are also specified in a similar manner, but are not shown in FIG. 14 for the sake of convenience.

[0161] = Processing related to the total aggregate setup status on the process side = Regarding the total process-side aggregated setup state of "Number" = "6" in Figures 12 and 14, for example, a set is generated that includes process-side resource-unit aggregated setup states related to setup (the processing result of the above-mentioned "Processing related to resource-unit aggregated setup states on the process side") that have the processes identified in the first step in common, and the total process-side aggregated setup state is determined and identified by aggregating the process-side resource-unit aggregated setup states included in the generated set.

[0162] In addition, "setup with a common process" may be interpreted as a concept indicating that the work to which the work-side setup is associated belongs to a common process, or that the process to which the process-side setup is associated is a common process.

[0163] Here, for example, as shown in Fig. 14, a set of "1FA work area reinforcement" including "urgent" which is a task-side resource unit aggregated setup state of "labor" etc. is generated, and "urgent" is determined and specified as the process-side total aggregated setup state of "1FA work area reinforcement". In addition, although not shown in Fig. 14, the process-side total aggregated setup state of "xx reinforcement" (see "Process name information" in Fig. 3) is determined and specified in the same way.

[0164] <Variations> As a variation of the processing here, a set may be generated that includes individual work-side setup states related to work-side setup (the processing result of the above-mentioned "Processing related to individual work-side setup states") and individual process-side setup states related to process-side setup (the processing result of the above-mentioned "Processing related to individual process-side setup states") that share the process identified in the first step, and the setup states included in the generated set may be aggregated to determine and identify an overall aggregated process-side setup state.

[0165] As another variation of the processing here, a set may be generated that includes a work-side total aggregated setup state for work-side setups that share the process identified in the first step, and a process-side individual setup state for process-side setups that share the process identified in the first step, and the setup states included in the generated set may be aggregated to determine and identify the process-side total aggregated setup state.

[0166] In this manner, the various setup states shown in Fig. 14 are specified. Although not shown in Figs. 3 to 5, for example, when the state is as shown in Fig. 13, the various setup states exemplified in Fig. 13 are determined and specified by carrying out the same process as described above.

[0167] ===Interpretation of terms=== The processes relating to the work-side resource-unit aggregated setup state and the process-side resource-unit aggregated setup state of “Numbers” = “2” and “5” in Figures 12 and 14 define and specify the setup state aggregated on a target type basis, and therefore may be interpreted as corresponding to the “first aggregation process.”

[0168] In addition, the processes relating to the total aggregated setup state on the work side and the total aggregated setup state on the process side of "Numbers" = "3" and "6" in Figures 12 and 14 define and specify the setup state aggregated on a task basis or a process basis, so they may be interpreted as corresponding to the "second aggregation process."

[0169] In addition, the process relating to the total aggregated setup state on the work side indicated by “number” = “3” in Figures 12 and 14 defines and identifies the aggregated setup state on a task basis, and therefore may be interpreted as corresponding to the “third aggregation process.”

[0170] 12 and 14, the process related to the total aggregated setup state on the process side, "number" = "6", determines and specifies the setup state aggregated by process unit, and can also be interpreted as determining and specifying the setup state that further aggregates the total aggregated setup state on the work side, so it may be interpreted as corresponding to the "fourth aggregation process". This concludes the explanation of the aggregation process.

[0171] (Processing - Calendar screen display processing) Next, the calendar screen display process will be described. The calendar screen display process is generally a process executed by the server device 2, for example, a process for displaying a calendar screen. The timing of execution of this calendar screen display process is arbitrary, but for example, when the administrator performs a predetermined operation via the terminal device 1, the process starts, and the description will be given from the point where this process is started (the same applies to the list screen display process).

[0172] Here, the process will be explained after explaining the calendar screen.

[0173] ===Calendar screen=== Fig. 15 is a display example of a calendar screen, and Fig. 16 is an explanatory diagram of the calendar screen. Fig. 16(a) is an enlarged diagram of a part of the calendar screen of Fig. 15, and Fig. 16(b) is an explanatory diagram of process side index information.

[0174] The calendar screen in FIG. 15 is a screen that displays a process related image G11 and a task related image G12 on a schedule screen that allows users to specify dates belonging to a month.

[0175] == Process related images == The process-related image G11 in Figures 15 and 16 is an image that displays information about a process, and is displayed, for example, in a rectangular shape for each process in a column for the date corresponding to the schedule to which the process is assigned, and is an image that includes text information indicating information about the process (in Figure 16(a), "1FA work area reinforcement" indicating the name of the process) and process side indicator information G111 in Figure 16(a).

[0176] Fig. 17 is a diagram showing an example of the setup state displayed by the index information of each screen. The "Displayed Setup State" column in Fig. 17 shows the setup state displayed by the index information of each corresponding screen, with "(6)" etc. corresponding to the numerical value in the "Number" column in Fig. 12. For example, "Number" = "1" in Fig. 17 shows that the process side index information G11 (Fig. 16) on the calendar screen displays the process side total aggregated setup state of "Number" = "6" in Fig. 12. The contents shown from "Number" = "2" onwards in Fig. 17 are as shown.

[0177] The process side index information G111 in Fig. 16(a) is information that displays the setup status of the setup related to the process corresponding to the process-related image G11, and is information that displays the process side total aggregated setup status, for example, as shown in "number"="1" in Fig. 17. As the process side index information G111, for example, as shown in Fig. 16(b), any one of the first display image G111A, the second display image G111B, the third display image G111C, or the fourth display image G111D is displayed.

[0178] The first display image G111A is an image indicating that the setup status is "normal", for example, an image displayed in green. The second display image G111B is an image indicating that the setup status is "caution", for example, an image displayed in yellow. The third display image G111C is an image indicating that the setup status is "urgent", for example, an image displayed in red. The fourth display image G111D is an image indicating that the setup status is "other", for example, an image displayed in gray.

[0179] With regard to the process-related image G11 in FIG. 16(a), the third display image G111D in FIG. 16(b) is displayed as the process side indicator information G111, so that it is shown that the process side total aggregate setup status for the “1FA work area reinforcement” process is “urgent”.

[0180] ==Work related images== The work-related image G12 in Figures 15 and 16 is an image that displays information about a task, and is, for example, displayed in a rectangular shape for each day's work in the column for each date corresponding to the period for which the task is assigned, and is an image that includes text information showing information about the task (in Figure 16(a), "8:00-17:00" indicating the work time period for the day, "Company B" indicating the company to which the person in charge of the task belongs, and "Material delivery / lifting" indicating the name of the task) and the work side indicator information G121 in Figure 16(a).

[0181] The work-side indicator information G121 in Fig. 16(a) is information that displays the setup status of the setup related to the work corresponding to the work-related image G12, and is information that displays the work-side total aggregated setup status, for example, as shown in "number"="2" in Fig. 17. As the work-side indicator information G121, for example, like the process-side indicator information G111, any one of the display images exemplified in Fig. 16(b) is displayed.

[0182] For the work-related image G12 displayed in the “9th” column in FIG. 16(a), the third display image G111D in FIG. 16(b) is displayed as the work side indicator information G121, indicating that the work side total aggregate setup status for the setup related to the work of “material delivery and lifting” is “urgent”.

[0183] ===Processing=== Regarding the process, the control unit 23 of the server device 2 performs the following first and second steps. Note that the following description will be given on the assumption that the setup state in Fig. 14 is specified as a result of the aggregation process (the same applies to other processes).

[0184] ==First Step== In the first step, screen information for displaying a calendar screen is generated based on the information recorded in the recording unit 22 in Fig. 1 and the latest processing result of the aggregation process described above. Note that the latest processing result of the aggregation process used here includes, for example, a result at an intermediate stage of the process and a final result of the process (the same applies to each of the following processes).

[0185] Here, for example, with regard to the process-related image G11 in FIG. 16(a), screen information is generated so that the “Process name information” in FIG. 3 = “1FA work area reinforcement” is displayed, and the “Period information” in FIG. 3 = “August 9, 2021 - August 11, 2021” is displayed in a rectangular shape spanning, and the “Process side indicator information G111 displaying the third display image G111D (FIG. 16(b)) showing the “Process side total aggregated setup status” = “Urgent” (FIG. 14) for the “1FA work area reinforcement” process, which is the most recent processing result of the aggregation process, is displayed.

[0186] Furthermore, for example, with regard to the work-related image G12 displayed in the "9th" column in FIG. 16(a), screen information is generated so that the predetermined working time period for one day, "8:00-17:00", is displayed, and "Company B" (the company name to which the person in charge of "ID0002" in FIG. 2 belongs) corresponding to the "Person in Charge ID" = "ID0002" in FIG. 4 is displayed, and "Work Name Information" = "Material Delivery and Lifting" in FIG. 4 is displayed, and work side indicator information G121 displaying the third display image G111D (FIG. 16(b)) showing the "Work side total consolidation setup status" = "Urgent" (FIG. 14) for the work of "Material Delivery and Lifting", which is the most recent processing result of the consolidation process, is displayed.

[0187] Moreover, for example, screen information is generated in the same manner for the work-related image G12 displayed in the "10th" and "11th" columns in FIG.

[0188] ==Second Step== In the second step, the screen information generated in the first step is sent to the terminal device 1, thereby displaying the calendar screen of Fig. 15 on the display 13 of the terminal device 1. In this case, the user can grasp the setup status by visually checking the calendar screen of Fig. 15. This concludes the explanation of the calendar screen display process.

[0189] (Processing - List screen display processing) Next, the list screen display process will be described. The list screen display process is generally a process executed by the server device 2, and is, for example, a process for displaying a list screen.

[0190] Here, the list screen will be explained first, and then the process contents will be explained.

[0191] ===List screen=== FIG. 18 is a display example of the list screen, and FIG. 19 is an explanatory diagram of index information.

[0192] The list screen in Figure 18 is a screen that displays information about processes and the work belonging to those processes in a list, and has each column shown in Figure 18 (a "Status" column, a "Process / Work" column, etc.).

[0193] 18 is a column for displaying index information indicating the setup status of a setup related to a process or an operation. Note that the index information will be described later.

[0194] The "Process / Work" column in FIG. 18 is a column in which the name of the process or work is displayed. In this column, for example, each name is displayed together with "(Work)" which indicates that it is a process, or "(Work)" which indicates that it is work. Note that for "(Work)" and "(Work)", figures or pictograms that evoke the image of the process or work may be used (the same applies to "(Work)" and "(Work)" on other screens). In addition, from the viewpoint of improving visibility, the list screen is displayed in a manner that allows the process and the work belonging to the process to be grasped, and is configured so that, for example, the name of the work belonging to the process is displayed below the name of the process.

[0195] The "person in charge" column in FIG. 18 is a column in which information identifying the person in charge of the process or work (name and company to which the person belongs) is displayed.

[0196] The "Schedule" field in Fig. 18 is a field that displays information indicating the period to which a process or task is assigned. For tasks, the date is displayed, and the list screen is configured so that one day's worth of information is displayed per line.

[0197] The "Labor", "Materials", "Information", "Construction Machinery" and "Space" columns in Fig. 18 are columns that display index information showing the setup status of the setup related to the process or work based on the target types "Labor", "Materials", "Information", "Construction Machinery" and "Space". The index information will be described later.

[0198] ==Indicator information in the "Status" column== The indicator information displayed in the "Status" column in Fig. 18 is information indicating the setup status of the setup related to the process or task displayed in the "Process / Work" column. For example, as shown in "Number" = "3" in Fig. 17, when information related to a process is displayed in the "Process / Work" column, information indicating the total aggregated setup status on the process side is used as the setup status of the setup related to the process, and when information related to a task is displayed in the "Process / Work" column, information indicating the total aggregated setup status on the task side is used as the setup status of the setup related to the task.

[0199] Any index information may be used here, but for example, the case where index information 9 shown in Fig. 19(a) is used will be described. The index information 9 in Fig. 19(a) is information that displays a setup state, and has, for example, a first display field 91, a second display field 92, and a third display field 93.

[0200] Each display column of the indicator information 9 is configured to indicate the setup status by either all being off or any one being lit. For example, the first display column 91 is a column that is lit green or off, the second display column 92 is a column that is lit yellow or off, and the third display column 93 is a column that is lit red or off.

[0201] It should be noted that the first display column 91 being lit in green may be interpreted as a concept indicating that the first display column 91 is displayed in green to make it stand out, and the first display column 91 being turned off may be interpreted as a concept indicating that the first display column 91 is not stood out by being the same color as the background color (e.g., gray). The same applies to the other display columns. In each drawing, the lit display columns are shown hatched, and the display columns not shown hatched are not lit (i.e., turned off).

[0202] For example, as shown in FIG. 19(b), when the first display column 91 is lit in green, it indicates that the setup status is "normal." For example, as shown in FIG. 19(c), when the second display column 92 is lit in yellow, it indicates that the setup status is "caution." For example, as shown in FIG. 19(d), when the third display column 93 is lit in red, it indicates that the setup status is "urgent." For example, as shown in FIG. 19(e), when the first display column 91 to the third display column 93 are all turned off, it indicates that the setup status is "other."

[0203] ==Indicator information for the "Labor" to "Space" columns== The indicator information displayed in the "Labor" to "Space" columns in Fig. 18 is information indicating the setup status of the setup related to the process or task displayed in the "Process / Work" column. For example, as shown in "Number" = "4" in Fig. 17, when information related to a process is displayed in the "Process / Work" column, information indicating the resource-unit aggregated setup status on the process side is used as the setup status of the setup related to the process as the indicator information displayed in the "Labor" to "Space" columns, and when information related to a task is displayed in the "Process / Work" column, information indicating the resource-unit aggregated setup status on the task side is used as the setup status of the setup related to the task.

[0204] In detail, the "Labor", "Materials", "Information", "Construction Machinery" and "Space" columns in Fig. 18 each display index information that displays the process-side resource-unit aggregated setup state or the work-side resource-unit aggregated setup state for each of "Labor", "Materials", "Information", "Construction Machinery" and "Space". Note that any index information may be used here, but for example, a case will be described in which index information 9 shown in Fig. 19(a) is used, similar to the index information in the "Status" column.

[0205] ===Processing=== Regarding the processing, the control unit 23 of the server device 2 performs the following first and second steps.

[0206] ==First Step== In the first step, generally speaking, screen information for displaying a list screen is generated based on the information recorded in the recording unit 22 in FIG. 1 and the most recent processing result of the above-mentioned aggregation processing.

[0207] = Overall = Overall, by focusing on the related process ID in the work-related information in Figure 4, the process and the work belonging to that process are identified, and screen information is generated so that information about the work belonging to that process is displayed below the information about the process on the list screen (below the drawing in Figure 18).

[0208] <Example> Here, for example, in the work-related information of FIG. 4, the related process ID of a task such as "material delivery and lifting" is "ID1001," so the task such as "material delivery and lifting" is identified as a task belonging to the process of "1FA work area reinforcement" shown in the process-related information of FIG. 3, and screen information is generated so that information on the task such as "material delivery and lifting" is displayed below information on the process of "1FA work area reinforcement," as shown in FIG. 18.

[0209] = "Process / Work" column, "Person in charge" column, "Schedule" column= Regarding the "Process / Work", "Person in Charge" and "Schedule" columns in Figure 18, when displaying information about a process, screen information is generated so that information corresponding to the process name information in Figure 3, the name of the person in charge identified by the person in charge ID and the name of the company to which the person belongs, and information corresponding to the period information are displayed.

[0210] In addition, when displaying information about work in each of these columns, screen information is generated so that information corresponding to the work name information in Figure 4, the name of the person in charge identified by the person in charge ID and the name of the company to which the person belongs, and information corresponding to the period information are displayed.

[0211] <Example> Here, for example, for the "Process / Work", "Person in Charge", and "Schedule" columns at the top of Figure 18, screen information is generated so that information corresponding to "Process Name Information" = "1FA Work Section Reinforcement" in Figure 3, the name and company name of the person in charge identified by "Person in Charge ID" = "ID0001" (see person in charge information in Figure 2), and information corresponding to "Period Information" = "August 9, 2021 - August 11, 2021" is displayed.

[0212] Furthermore, for example, for the "Process / Work", "Person in Charge", and "Schedule" columns in the second row of Figure 18, screen information is generated so that information corresponding to "Work Name Information" = "Material Delivery / Lifting" in Figure 4, the name and company name of the person in charge identified by "Person in Charge ID" = "ID0002" (see person in charge information in Figure 2), and information corresponding to "Period Information" = "August 9, 2021" are displayed.

[0213] ="Status" column= In the "Status" column of FIG. 18, when displaying information about a process, the screen information is generated so that the total aggregated setup status on the process side indicated by the most recent processing result of the aggregation process is obtained for the process whose name is displayed in the corresponding "Process / Work" column, and index information 9 corresponding to the obtained total aggregated setup status on the process side is displayed.

[0214] In addition, when displaying information about work in this column, the screen information is generated so that the total work-side aggregated setup state indicated by the most recent processing result of the aggregation process is obtained for the work whose name is displayed in the corresponding "Process / Work" column, and index information 9 corresponding to the obtained total work-side aggregated setup state is displayed.

[0215] <Example> Here, for example, for the "Status" column at the top of Fig. 18, the "Total consolidated setup status on the process side" = "Urgent" (Fig. 14) indicated by the most recent processing result of the consolidation process is obtained for the "1FA work area reinforcement" process, and screen information is generated so that indicator information 9 (Fig. 19(d)) corresponding to "Urgent" is displayed.

[0216] Furthermore, for example, with regard to the "Status" column in the second row of Fig. 18, for the task of "material delivery and lifting", the "total consolidation setup status on the work side" indicated by the most recent processing result of the consolidation process = "urgent" (Fig. 14) is obtained, and screen information is generated so that indicator information 9 (Fig. 19(d)) corresponding to "urgent" is displayed.

[0217] = "Labor" column = In the "Labor" column of Figure 18, when displaying information about a process, the screen information is generated so that the process-side resource unit aggregate setup state of "Labor" indicated by the most recent processing result of the aggregation process is obtained for the process whose name is displayed in the corresponding "Process / Work" column, and index information 9 corresponding to the obtained process-side resource unit aggregate setup state is displayed.

[0218] In addition, when displaying information about work in this column, the screen information is generated so that the work-side resource unit aggregate setup status of "labor" indicated by the most recent processing result of the aggregation process is obtained for the work whose name is displayed in the corresponding "Process / Work" column, and index information 9 corresponding to the obtained work-side resource unit aggregate setup status is displayed.

[0219] <Example> Here, for example, for the "Labor" column at the top of Figure 18, the "Process side resource unit aggregation setup status" = "Urgent" (Figure 14) indicated by the most recent processing result of the aggregation process is obtained for the "1FA work area reinforcement" process, and screen information is generated so that indicator information 9 (Figure 19(d)) corresponding to "Urgent" is displayed.

[0220] Furthermore, for example, for the "Labor" column in the second row of Figure 18, for the task of "Material delivery and lifting", the "Work side resource unit aggregation setup status" = "Urgent" (Figure 14) indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that indicator information 9 (Figure 19(d)) corresponding to "Urgent" is displayed.

[0221] = "Material" column ~ "Space" column = The processing of the "Material" column to the "Space" column in Fig. 18 is similar to that of the "Labor" column, so detailed explanation will be omitted. Note that it is possible that there is no corresponding setup for the "Labor" column to the "Space" column, and the setup state cannot be specified. In this case, screen information may be generated so that each column is hidden, "none" is displayed, or indicator information 9 (Fig. 19(e)) corresponding to "Other" is displayed.

[0222] ==Second Step== In the second step, the screen information generated in the first step is sent to the terminal device 1, thereby displaying the list screen of Fig. 18 on the display 13 of the terminal device 1. In this case, the user can grasp the setup status by visually checking the list screen of Fig. 18. This concludes the explanation of the list screen display process.

[0223] (Processing - First Tree Screen Display Processing) Next, the first tree screen display process will be described. The first tree screen display process is, roughly speaking, a process executed by the server device 2, and is, for example, a process for displaying the first tree screen. The timing of execution of this first tree screen display process is arbitrary, but for example, when the administrator performs a predetermined operation (operation for selecting a process to be displayed and starting the process) via the terminal device 1, the process is assumed to start, and the process will be described from the point where it is started. Here, for example, when the user selects "1FA work area reinforcement" on the list screen of FIG. 18 and performs an operation for starting the process, information indicating that the "1FA work area reinforcement" has been selected by the user is input to the server device 2, and the process is started.

[0224] Here, the first tree screen will be explained first, and then the processing contents will be explained.

[0225] ===First Tree Screen=== FIG. 20 is an example of the first tree screen.

[0226] The first tree screen in Fig. 20 is a screen that displays information about a specific process using tree-structured information, and displays a process related image G21, a process type related image G22, and process setup related images G23 to G25. In this first tree screen, for example, each image is displayed in a display mode that shows the relationship between each element shown in Fig. 14 (the same applies to the second and third tree screens described later).

[0227] Since the process setup related images G23 to G25 have the same configuration, the process setup related image G23 will be representatively described below.

[0228] == Process related images == The process-related image G21 in Figure 20 is an image that displays information about the process, and is an image that includes, for example, text information indicating information about the process (in Figure 20, "2021 / 8 / 9 to 2021 / 8 / 11" indicating the assigned period, and "1FA work area reinforcement" indicating the name of the process) and process side indicator information G211.

[0229] The process side indicator information G211 is information that displays the setup status of the setup related to the process corresponding to the process related image G21, and is information that displays the entire aggregated setup status on the process side, for example, as shown in "number"="5" in Fig. 17. As the process side indicator information G211, for example, information having the same structure as the indicator information 9 in Fig. 19 (that is, a structure in which each setup status is shown by turning on or off each display field) is used.

[0230] == Process type related images == The process type related image G22 in Figure 20 is an image that displays information about the target type of the setup related to the process, and is an image that includes, for example, text information indicating the target type (in Figure 20, "Labor") and process type side indicator information G221.

[0231] The process type side index information G221 is information that displays the setup state of the setup related to the process corresponding to the process related image G21 that is associated with the process type related image G22, and is information that displays the process side resource unit aggregated setup state, for example, as shown in "number"="6" in Fig. 17. As the process type side index information G221, for example, information having the same configuration as the index information 9 in Fig. 19 is used.

[0232] == Process setup related images == The process setup related image G23 in Figure 20 is an image that displays information related to the process side setup, and is an image that includes, for example, text information indicating information related to the process side setup (in Figure 20, "Labor request to cooperating company" indicating the name of the setup, and "AA AA" indicating the person in charge of the work) and process setup side indicator information G231.

[0233] The process setup side index information G231 is information that displays the setup state of the process side setup corresponding to the process setup related image G23, and is information that displays the individual setup state of the process side, for example, as shown in "number"="7" in Fig. 17. As the process setup side index information G231, for example, information having the same configuration as the index information 9 in Fig. 19 is used.

[0234] ===Processing=== Regarding the process, the control unit 23 of the server device 2 performs the following first and second steps for the process indicated by the information input when the process is started (for example, the process of "1FA work area reinforcement" selected by the user).

[0235] ==First Step== In the first step, generally speaking, screen information for displaying the first tree screen is generated based on the information recorded in the recording unit 22 in FIG. 1 and the most recent processing result of the aggregation processing described above.

[0236] = Overall = Overall, the process to be processed (for example, the "1FA Work Area Reinforcement Arrangement" process selected by the user) is identified by referring to the process-related information in Figure 3, and the setup associated with the process to be processed (for example, the "1FA Work Area Reinforcement Arrangement" process selected by the user) and the target type of the setup are identified by focusing on the related process ID in the first setup-related information in Figure 5, and screen information is generated so that the images corresponding to these identification results are displayed in a mutually associated tree structure.

[0237] =Process related images= With regard to the process-related image G21 in FIG. 20, in the process-related information in FIG. 3, the process name information and period information corresponding to the process to be processed are identified, and further, for the process to be processed, the total process-side aggregated setup state indicated by the most recent processing result of the aggregation process is acquired, and screen information is generated so that the information corresponding to the identified process name information and period information and the process-side index information G211 corresponding to the acquired total process-side aggregated setup state are displayed.

[0238] <Example> Here, for example, in the process-related information in Figure 3, "1FA Work Area Reinforcement" and "August 9, 2021 - August 11, 2021" corresponding to the process to be processed are identified, and for the "1FA Work Area Reinforcement" process to be processed, the "Process side total aggregated setup status" = "Urgent" (Figure 14) indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that the process-related image G21 in Figure 20 is displayed.

[0239] = Process type related images = With regard to the process type related image G22 in FIG. 20, in the first setup related information in FIG. 5, target type information of the setup (process side setup and work side setup associated with the work belonging to the process) associated with the process to be processed is identified, and for the process to be processed, the process side resource unit aggregate setup state indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that information corresponding to the identified target type information and process type side indicator information G221 corresponding to the obtained process side resource unit aggregate setup state are displayed.

[0240] <Example> Here, for example, in the first setup related information in FIG. 5, "labor" is specified as the setup target type information associated with the "1FA work area reinforcement" process that is the target of processing, and for the "1FA work area reinforcement" process that is the target of processing, the "process side resource unit aggregate setup status" for "labor" indicated by the most recent processing result of the aggregation process = "urgent" (FIG. 14) is obtained, and screen information is generated so that the process type related image G22 in FIG. 20 is displayed.

[0241] =Process setup related images= Regarding the process setup related image G23 in Fig. 20, the process side setup associated with the process to be processed is specified in the first setup related information in Fig. 5, the setup name information, the target type information, and the person in charge ID corresponding to the specified process side setup are specified, and in the person in charge information in Fig. 2, the name of the person in charge corresponding to the specified person ID is specified, and regarding the specified process side setup, the process side individual setup state indicated by the most recent processing result of the aggregation process is obtained, and the screen information is generated so that the information corresponding to the specified setup name information and the person in charge name, and the process setup side indicator information G231 corresponding to the obtained process side individual setup state, etc. are displayed. Note that, regarding the process setup related image G23, the screen information is generated so that the image is displayed in association with the process type related image G22 corresponding to the target type indicated by the specified target type information.

[0242] <Example> Here, for example, a specific example of the process setup related image G23 will be described. In the first setup related information in Fig. 5, the process side setup associated with the process of "1FA work area reinforcement" that is the target of processing is specified, and "Labor request confirmation" and "ID0001" are specified as the setup name information and person in charge ID corresponding to the specified process side setup, and "AA AA" and the like are specified as the name of the person in charge corresponding to the specified person ID in the person in charge information in Fig. 2, and "Process side individual setup status" = "Caution" and the like indicated by the most recent processing result of the aggregation process is obtained with respect to "Labor request confirmation" and the like, and then screen information is generated so that the process setup related image G23 in Fig. 20 is displayed. Note that the same processing is also performed for the process setup related images G24 to G25.

[0243] ==Second Step== In the second step, the screen information generated in the first step is transmitted to the terminal device 1, thereby displaying the first tree screen of Fig. 20 on the display 13 of the terminal device 1. In this case, the user can grasp the setup status by visually checking the first tree screen of Fig. 20. This concludes the explanation of the first tree screen display process.

[0244] (Processing - Second Tree Screen Display Processing) Next, the second tree screen display process will be described. The second tree screen display process is, roughly speaking, a process executed by the server device 2, and is, for example, a process for displaying the second tree screen. The timing of execution of this second tree screen display process is arbitrary, but for example, when the administrator performs a predetermined operation via the terminal device 1 (such as tapping the "work setup display button" not shown on the first tree screen in FIG. 20), the process will be described from the point where it is started. Here, for example, when the user performs an operation of tapping the "work setup display button" on the first tree screen related to the "1FA work area reinforcement" in FIG. 20, information indicating that the "1FA work area reinforcement" has been selected by the user is input to the server device 2, and the process is started.

[0245] Here, the second tree screen will be explained first, and then the processing contents will be explained.

[0246] ===Second Tree Screen=== FIG. 21 is an example of the second tree screen.

[0247] The second tree screen in Fig. 21 is a screen that displays information about a specific process using tree-structured information, and is a screen that displays additional information to the first tree screen. The second tree screen is a screen that displays a process-related image G21, a process type-related image G22, process setup-related images G23-G25, and a task-related image G31. Note that, among the images on the second tree screen, all images except for the task-related image G31 are the same as those on the first tree screen, so only the task-related image G31 will be described in detail.

[0248] ==Work related images== The work-related image G31 in Figure 21 is an image that displays information about the work, and is an image that includes, for example, text information indicating information about the work (in Figure 21, "2021 / 8 / 9" indicating the date corresponding to the assigned period, and "Material delivery and lifting" indicating the name of the work) and work side indicator information G311.

[0249] The work-side index information G311 is information that displays the setup status of the setup related to the work corresponding to the work-related image G31, and is information that displays the work-side total aggregated setup status, for example, as shown in "number"="11" in Fig. 17. As the process-side index information G311, for example, information having the same configuration as the index information 9 in Fig. 19 is used.

[0250] ===Other Images=== As mentioned above, the process-related image G21, process type-related image G22, and process setup-related images G23 to G25 in Figure 21 are the same as the information of the same name displayed in the first tree screen in Figure 20, and as shown by "Number" = "8" to "10" in Figure 17, each indicator information indicating the total aggregated setup state on the process side, the resource-unit aggregated setup state on the process side, and the individual setup state on the process side is displayed.

[0251] ===Processing=== Regarding the process, the control unit 23 of the server device 2 performs the following first and second steps for the process indicated by the information input when the process is started (for example, the process of "1FA work area reinforcement" selected by the user).

[0252] ==First Step== In the first step, generally speaking, screen information for displaying the second tree screen is generated based on the information recorded in the recording unit 22 in FIG. 1 and the most recent processing result of the aggregation processing described above.

[0253] = Overall = Overall, similar to the first tree screen display processing, the process related information in FIG. 3 is referenced to identify the process to be processed (for example, the "1FA Work Area Reinforcement" process selected by the user), and the related process ID in the first setup related information in FIG. 5 is focused on to identify the setup associated with the process to be processed (for example, the "1FA Work Area Reinforcement" process selected by the user) and the target type of the setup.

[0254] Next, by referring to the work-related information in Figure 4, the system identifies the work that belongs to the process that is the target of processing (for example, work such as "material delivery and lifting" that is associated with the related process ID "ID1001"), and also, by focusing on the related work ID in the first setup-related information in Figure 5, it identifies the setup that is associated with the identified work (i.e., work such as "material delivery and lifting" that belongs to the process that is the target of processing) and the target type of that setup.

[0255] Next, screen information is generated so that the images corresponding to the aforementioned specified results are displayed in a tree structure in which they are mutually associated.

[0256] = Process related images, process type related images, process setup related images = Regarding the process related image G21, process type related image G22, and process setup related images G23 to G25 in Figure 21, screen information is generated so that each image in Figure 21 is displayed in the same manner as described in the first tree screen display process.

[0257] =Work related images= With regard to the work-related image G31 in FIG. 21, in the work-related information in FIG. 4, work belonging to the process that is the target of processing is identified, and work name information and period information corresponding to the identified work are identified. Also, for the identified work, the total work-side aggregated setup state indicated by the most recent processing result of the aggregation process is obtained. Also, in the first setup-related information in FIG. 5, the work-side setup associated with the identified work is identified, and target type information corresponding to the identified work-side setup is identified.

[0258] Next, the screen information is generated so that the information corresponding to the above-mentioned specified work name information and period information, and the work side indicator information G311 corresponding to the acquired work side total aggregated setup state are displayed. Note that the screen information is generated so that the work related image G31 is displayed in association with the process type related image G22 corresponding to the object type indicated by the above-mentioned specified object type information.

[0259] <Example> Here, for example, in the work-related information in Figure 4, the work etc. of "material delivery and lifting" belonging to the process of "1FA work area reinforcement" that is the target of processing is identified, and "material delivery and lifting" and "August 9, 2021" etc. corresponding to the identified work are identified. In addition, for the identified work etc. of "material delivery and lifting", the "work side total aggregated setup status" = "urgent" etc. (Figure 14) indicated by the most recent processing result of the aggregation process is obtained. In addition, in the first setup-related information in Figure 5, "worker allocation" and "lifting machine reservation", which are work side setups associated with the aforementioned identified "material delivery and lifting" etc., are identified, and "labor", etc., which is the target type information corresponding to the identified work side setup, is identified.

[0260] Next, image information is generated so that the work-related image G31 in FIG. 21 is displayed in association with the process type-related image G22 corresponding to the specified "labor" described above.

[0261] ==Second Step== In the second step, the screen information generated in the first step is transmitted to the terminal device 1, thereby displaying the second tree screen of Fig. 21 on the display 13 of the terminal device 1. In this case, the user can grasp the setup status by visually checking the first tree screen of Fig. 21. This concludes the explanation of the second tree screen display process.

[0262] (Processing - 3rd Tree Screen Display Processing) Next, the third tree screen display process will be described. The third tree screen display process is, roughly speaking, a process executed by the server device 2, for example, a process for displaying the third tree screen. The timing of execution of this third tree screen display process is arbitrary, but for example, when the administrator performs a predetermined operation via the terminal device 1 (such as pressing and holding the work-related image G31 on the second tree screen), the process is assumed to start, and the description will begin from the point where this process is started.

[0263] Here, for example, a case will be described in which, when a user selects the work of "material delivery and lifting" belonging to the process of "1FA work area reinforcement" by long pressing the work-related image G31 in Figure 21, information indicating that the work of "material delivery and lifting" belonging to the process of "1FA work area reinforcement" has been selected by the user is input to the server device 2, and processing is then started.

[0264] Here, the third tree screen will be explained first, and then the processing contents will be explained.

[0265] ===Third Tree Screen=== FIG. 22 is an example of the display of the third tree screen.

[0266] The third tree screen in FIG. 22 is a screen that displays information related to a specific task using tree-structured information, and is a screen that displays a task related image G41, task type related images G42 to G44, and task setup related images G45 to G49.

[0267] In addition, since the task type related images G42 to G44 have the same configuration, the following description will be limited to the task type related image G42. In addition, since the task setup related images G45 to G49 have the same configuration, the following description will be limited to the task setup related image G45.

[0268] ==Work related images== The work-related image G41 in Figure 22 is an image that displays information about the work, and is an image that includes, for example, text information indicating information about the work (in Figure 22, "August 9, 2021" indicating the date corresponding to the assigned period, and "Material delivery and lifting" indicating the name of the work) and work side indicator information G411.

[0269] The work-side index information G411 is information that displays the setup status of the setup related to the work corresponding to the work-related image G41, and is information that displays the work-side total aggregated setup status, for example, as shown in "number"="12" in Fig. 17. As the work-side index information G411, for example, information having the same configuration as the index information 9 in Fig. 19 is used.

[0270] ==Work type related images== The work type related image G42 in Figure 22 is an image that displays information about the target type of work-related setup, and is an image that includes, for example, text information indicating the target type (in Figure 22, "Labor") and work type side indicator information G421.

[0271] The task type side index information G421 is information that displays the setup state of the setup related to the task corresponding to the task related image G41 that is associated with the task type related image G42, and is information that displays the task side resource unit aggregated setup state, for example, as shown in "number"="13" in Fig. 17. As the task type side index information G421, for example, information having the same configuration as the index information 9 in Fig. 19 is used.

[0272] ==Work setup related images== The work setup related image G45 in Figure 22 is an image that displays information related to the work side setup, and is an image that includes, for example, text information indicating information related to the work side setup (in Figure 22, ``Worker assignment'' indicating the name of the setup, and ``BB BB'' indicating the person in charge of the work, etc.) and work setup side indicator information G451.

[0273] The work setup side indicator information G451 is information that displays the setup state of the work side setup corresponding to the work setup related image G45, and is information that displays the work side individual setup state, for example, as shown in "number"="14" in Fig. 17. As the work setup side indicator information G451, for example, information having the same configuration as the indicator information 9 in Fig. 19 is used.

[0274] ===Processing=== Regarding the processing, the control unit 23 of the server device 2 performs the following first and second steps with respect to the work belonging to the process indicated by the information input when the processing is started (for example, the work of "material delivery and lifting" belonging to the process of "1FA work area reinforcement" selected by the user).

[0275] ==First Step== In the first step, generally speaking, screen information for displaying the third tree screen is generated based on the information recorded in the recording unit 22 in FIG. 1 and the most recent processing result of the above-mentioned aggregation processing.

[0276] = Overall = Overall, the system refers to the work-related information in Figure 4 to identify the work to be processed (for example, the work of "material delivery and lifting" selected by the user), and also focuses on the related work ID in the first setup-related information in Figure 5 to identify the setup associated with the work to be processed (for example, the work of "material delivery and lifting" selected by the user) and the target type of that setup, and generates screen information so that each image corresponding to these identification results is displayed in a tree structure in which they are mutually associated.

[0277] =Work related images= With regard to the work-related image G41 in FIG. 22, in the work-related information in FIG. 4, the work name information and period information corresponding to the work to be processed are identified, and further, for the work to be processed, the work-side total aggregated setup state indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that the information corresponding to the identified work name information and period information and the work-side indicator information G411 corresponding to the obtained work-side total aggregated setup state are displayed.

[0278] <Example> Here, for example, in the work-related information in Figure 4, "Material delivery and lifting" and "August 9, 2021" corresponding to the work to be processed are identified, and for the "Material delivery and lifting" work to be processed, the "Work side total aggregation setup status" = "Urgent" (Figure 14) indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that the work-related image G41 in Figure 22 is displayed.

[0279] =Work type related images= With regard to the work type related image G42 in FIG. 22, in the first setup related information in FIG. 5, target type information of the setup (work side setup) associated with the work to be processed is identified, and with regard to the work to be processed, the work side resource unit aggregate setup state indicated by the most recent processing result of the aggregation process is obtained, and screen information is generated so that information corresponding to the identified target type information and work type side indicator information G421 corresponding to the obtained work side resource unit aggregate setup state are displayed.

[0280] <Example> Here, for example, in the first setup related information in Fig. 5, "labor" is specified as the setup target type information associated with the task of "material delivery and lifting" that is the target of processing, and for the task of "material delivery and lifting" that is the target of processing, the "task side resource unit aggregate setup status" of "labor" indicated by the most recent processing result of the aggregation process = "urgent" (Fig. 14) is obtained, and then screen information is generated so that the task type related image G42 in Fig. 22 is displayed. Note that the same process is also performed for the task type related images G43 to G44.

[0281] =Work setup related images= Regarding the work setup related image G45 in Fig. 22, the work side setup associated with the work to be processed is specified in the first setup related information in Fig. 5, the setup name information, target type information, and person in charge ID corresponding to the specified work side setup are specified, and in the person in charge information in Fig. 2, the name of the person in charge corresponding to the specified person ID is specified, and regarding the specified work side setup, the work side individual setup state indicated by the most recent processing result of the aggregation process is obtained, and the screen information is generated so that the information corresponding to the specified setup name information and the person in charge name, and the work setup side indicator information G451 corresponding to the obtained work side individual setup state are displayed. Note that, regarding the work setup related image G45, the screen information is generated so that it is displayed in association with the work type related image G42 corresponding to the target type indicated by the specified target type information.

[0282] <Example> Here, for example, in the first setup-related information in Fig. 5, the work-side setup associated with the work of "material delivery and lifting" to be processed is specified, "worker allocation" and "ID0002" are specified as the setup name information and person in charge ID corresponding to the specified process-side setup, "BB BB" and the like are specified as the name of the person in charge corresponding to the specified person in charge ID in the person in charge information in Fig. 2, and regarding "worker allocation", etc., the "work-side individual setup status" = "urgent" and the like indicated by the most recent processing result of the aggregation process is obtained, and then screen information is generated so that the work setup-related image G45 in Fig. 22 is displayed. Note that the same processing is also performed for the work setup-related images G46 to G49.

[0283] ==Second Step== In the second step, the screen information generated in the first step is transmitted to the terminal device 1, thereby displaying the third tree screen of Fig. 22 on the display 13 of the terminal device 1. In this case, the user can grasp the setup status by visually checking the third tree screen of Fig. 22. This concludes the explanation of the third tree screen display process.

[0284] (Understanding the setup status, etc.) By visually checking each screen displayed by each process described above, it is possible to easily grasp the hierarchical structure of each element shown in FIG. 14 and each setup status, making it possible to accurately grasp the setup status.

[0285] (Effects of this embodiment) According to this embodiment, by displaying setup display information indicating setup based on setup-related information, it becomes possible to manage setup using the setup display information, for example.

[0286] [III] Modifications to the embodiment Although the embodiments of the present invention have been described above, the specific configurations and means of the present invention can be modified and improved as desired within the scope of the technical ideas of each invention described in the claims.

[0287] (About the type) In the above embodiment, the case where five types are applied as the behavior type (FIG. 8) and the target type (FIG. 9) has been described, but this is not limiting. For example, the number of types may be increased or decreased to apply two or three types, or six or more types. Also, only one of the behavior type or the target type may be applied. Also, the type may be configured to be set according to the construction work to which the information processing system 100 is applied (the content, timing, or other matters of the construction work).

[0288] (About aggregation) In the above embodiment, a case has been described in which the setup status is aggregated based on the target type. However, this is not limited to this, and it may be configured to aggregate based on, for example, a combination of an action type and a target type, or it may be configured to aggregate based on the action type.

[0289] (About setup status) Regarding the process-side resource-unit aggregated setup state of "number" = "5" in Figures 12 and 13 in the above embodiment, we will explain the case where it is a concept indicating an aggregated individual setup state on the process side and an individual setup state on the work side. However, as a variation, for example, it may be configured to perform each processing by indicating an aggregated individual setup state on the process side.

[0290] In this case, the process side total aggregated setup state of "Number" = "6" in Figures 12 and 13 may be configured to perform each process by showing an aggregate of the process side resource unit aggregated setup states, or it may be configured to perform each process by showing an aggregate of the work side total aggregated setup state and the process side resource unit aggregated setup state.

[0291] (About the arrangements) The definitions of process-side setup and work-side setup described in the above embodiment may be changed as desired. For example, for each setup, some setups designated by the user based on their own criteria may correspond to "process-side setup" and other setups may correspond to "work-side setup", and each process may be performed based on this.

[0292] The concept of process-side setup described in the above embodiment may be omitted. In other words, each process may be performed assuming that all setups correspond to "operation-side setup."

[0293] (Indicator information) The setup state indicated by each piece of indicator information shown in the "Indicator Information" column in Fig. 17 of the above embodiment may be changed as desired. Also, each piece of indicator information shown in the "Indicator Information" column in Fig. 17 may be interpreted as corresponding to "setup display information".

[0294] (About the output section) An output unit may be provided. The "output unit" is an output means for outputting a candidate setup schedule to be set as a construction setup schedule based on the type of setup target. The specific implementation method is arbitrary, but for example, an "output unit" may be provided as a part of the function of the control unit 23 of the server device 2 in FIG. 1, and the "output unit" may be configured to perform the following processes.

[0295] For example, it is assumed that type setting candidate related information is stored in the recording unit 22 of the server device 2. The "type setting candidate related information" is information indicating candidates for setups that are set based on the type of setup, and is, for example, information in which target type information (see FIG. 5) and candidate information indicating setting candidate setups that are candidates for the setups that are set are mutually associated. In the "type setting candidate related information", for example, combinations of "labor" and "setup A1" and "setup A2", combinations of "labor" and "setup A3" and "setup A4", combinations of "labor" and "setup A5" and "setup A6", etc. are stored, and it is assumed that multiple sets of similar combinations of information are stored for "material", "information", "construction equipment", and "space".

[0296] Then, for example, when setting each setup in FIG. 6 and FIG. 7 (i.e., when storing the first setup-related information in FIG. 5), the user inputs target type information of the setup that is expected to be set to the server device 2 via his / her own computer (tablet terminal, personal computer, etc.). Meanwhile, the "output unit" of the control unit 23 of the server device 2 acquires the input target type information, refers to the type setting candidate related information (not shown) in the recording unit 22, identifies candidate information corresponding to the acquired target type information, transmits the identified candidate information to the user's computer, and displays and outputs the candidate information on the display of the computer. Then, the user decides the setup to be set with reference to the candidate information displayed on the display, and inputs information related to the setup to the server device 2, whereby at least a part of the first setup-related information is stored.

[0297] As a specific example of the processing of the "output unit", when target type information indicating "labor" is input by a user to the server device 2, the type setting candidate related information (not shown) in the recording unit 22 is referenced to identify a combination of "setup A1" and "setup A2", a combination of "setup A3" and "setup A4", and a combination of "setup A5" and "setup A6" as candidate information corresponding to the target type information indicating "labor", and information indicating these identified combinations is displayed and output. Then, the user determines the setup to be set, for example, the combination of "setup A3" and "setup A4", and inputs information regarding the setup to the server device 2, whereby information regarding "setup A3" and "setup A4" is stored as at least a part of the first setup related information.

[0298] The content of the information stored as "category setting candidate related information" is arbitrary; for example, as described above, multiple combinations of arrangements related to target type information (e.g., "labor") may be stored, or one or more individual arrangements related to target type information may be stored.

[0299] Also, instead of the above-mentioned target type information, behavior type information (FIG. 5) may be applied, or both the target type information and the behavior type information may be applied, or other type information may be applied.

[0300] Further, although the case of display output has been described here, it may be configured to output audio, or to output on paper using a printer or the like. [Explanation of symbols]

[0301] 1 Terminal equipment 2. Server equipment 9 Indicator information 11 Communications Department 12 Touchpad 13. Display 14 Recording section 15 Control section 21 Communications Department 22 Recording Section 23 Control Unit 91 1st display column 92 Second display column 93 3rd display column 100 Information Processing Systems 221 Personnel Information DB 222 Process-related information DB 223 Work-related information DB 224 First Step Related Information DB 225 2nd Preparation Related Information DB G11 Process related images G12 Work related images G21 Process related images G22 Process type related images G23 Process setup related images G24 Process setup related images G25 Process Setup Related Images G31 Work related images G41 Work related images G42 Work type related images G43 Work Type Related Images G44 Work type related images G45 Work setup related images G46 Work setup related images G47 Work setup related images G48 Work setup related images G49 Work setup related images G111 Process-side index information G111A 1st display image G111B 2nd display image G111C 3rd display image G111D 4th display image G121 Work side indicator information G211 Process-side index information G221 Process type side indicator information G231 Process setup side index information G311 Work side index information G411 Work side index information G421 Work type side indicator information G451 operation stage setting side index information

Claims

1. A management system for managing a process that is a stage when a construction project is divided into multiple stages or a setup belonging to work performed in the process, A storage means for storing setup status information indicating the setup status; an aggregating means for aggregating the setup states indicated by the setup state information stored in the storage means based on a predetermined criterion; a display means for displaying setup display information indicating the setup status aggregated by the aggregation means; A management system comprising:

2. The aggregation means includes: a process of aggregating the status of the setup based on the type of the setup object that is the target of the setup; A process of aggregating the status of the setup based on the work to which the setup belongs; or a process of aggregating the status of the setup based on the process to which the setup belongs; The management system according to claim 1 .

3. The type of the setup object is a predetermined type that is predetermined for the construction work, The management system according to claim 2.

4. The type of the setup object includes one or more types of labor, materials, construction machinery, space, or information related to the construction work; The management system according to claim 3.

5. An output means for outputting a candidate setup to be set as the setup of the construction work based on the type of the setup target, The management system according to claim 1 .

6. the consolidation means consolidates the status of the setup for each type of the setup object based on the type of the setup object that is the target of the setup, the display means displays information indicating the state of the setup aggregated by the aggregation means as the setup display information. The management system according to claim 1 .

7. The aggregation means includes: a first consolidation process for consolidating the setup states by type of the setup object based on the type of the setup object that is the target of the setup; a second consolidation process for further consolidating the states of the setups consolidated in the first consolidation process for the task unit or the process unit to which the setups belong, based on the work or the process to which the setups belong; the display means displays, as the setup display information, information indicating the setup state summarized in the first summarizing process and information indicating the setup state summarized in the second summarizing process. The management system according to claim 1 .

8. The aggregation means includes: a third consolidation process for consolidating a state of the setup for each task to which the setup belongs based on the work to which the setup belongs; a fourth consolidation process for further consolidating the setup states consolidated in the third consolidation process for each process to which the work belongs, based on the process to which the work belongs; the display means displays, as the setup display information, information indicating the setup state summarized in the third summarizing process and information indicating the setup state summarized in the fourth summarizing process. The management system according to claim 1 .

9. A management program for managing a process that is a stage when a construction project is divided into multiple stages or a setup belonging to work performed in the process, Computer, A storage means for storing setup status information indicating the setup status; an aggregating means for aggregating the setup states indicated by the setup state information stored in the storage means based on a predetermined criterion; a display means for displaying setup display information indicating the setup status aggregated by the aggregation means; A management program that acts as a

Images