Data structure, data processing system, data processing program, and data processing method

Abstract

To provide a data structure to be efficiently processed in managing construction of a construction property.SOLUTION: This invention relates to a database, a data processing system for processing data on the database, a data processing program, and a data processing method. A data structure is a graph structure, and includes multiple element nodes representing elements to be used in constructing a construction property, multiple process nodes representing processes in constructing the construction property, multiple work nodes representing works included in one or more processes, and multiple attribute nodes representing attributes related to the element nodes and the process nodes. Each of the process nodes has a relationship with one or more work nodes. Each of the process nodes has a relationship with one or more attribute nodes. Each of the element nodes has a relationship with one or more attribute nodes.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a data structure, a data processing system, a data processing program, and a data processing method, and can be applied to a system that manages (hereinafter referred to as "construction management") the construction (architecture) of, for example, buildings, structures, information systems, etc. (hereinafter referred to as "construction properties"). [Background technology]

[0002] 2. Description of the Related Art Conventionally, a system described in Patent Document 1 exists as a technology for managing the construction of buildings such as factories and buildings.

[0003] In the system described in Patent Document 1, the position, shape, working status, etc. of each component are stored and managed as attribute information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-21190 Summary of the Invention [Problem to be solved by the invention]

[0005] By the way, the number of components that make up a single building typically amounts to tens of thousands, so when trying to set up a construction management system to manage multiple construction properties, the database of the system that manages these construction properties becomes even larger.

[0006] Furthermore, since the construction of construction properties involves design and on-site work in real time and with a large number of people, the construction management system database requires a high response time.

[0007] Furthermore, because there are a wide variety of "component attributes" and "construction processes" that make up a construction project, the database of a construction management system must be able to narrow down and aggregate data from multiple perspectives (conditions) according to these attributes and processes. Normally, when narrowing down or aggregating data in a large database, creating intermediate tables or indexes enables high-speed processing. In other words, with conventional construction management systems, when narrowing down or aggregating data from multiple perspectives is attempted, the database structure tends to become complex, resulting in poor processing efficiency.

[0008] As described above, the databases that make up conventional construction management systems require expensive hardware resources to process large amounts of data with complex structures at high speed.

[0009] Therefore, there is a demand for a data structure, a data processing system, a data processing program, and a data processing method that enable more efficient processing when managing the construction of a construction property. [Means for solving the problem]

[0010] A first data processing system of the present invention comprises a database holding means for holding a graph-structured database and a data processing means for processing data from the database, wherein the database is set with a plurality of element nodes indicating elements used when constructing a construction object consisting of a plurality of elements, a plurality of process nodes indicating processes for constructing the construction object, a plurality of task nodes indicating tasks included in one or more of the processes, and a plurality of attribute nodes indicating attributes related to the element nodes and the process nodes, wherein an edge indicating a relationship between each of the process nodes and the task nodes is set, and each of the process nodes is set with an edge indicating a relationship between each of the process nodes and the attribute nodes, and wherein the data processing means, when receiving input from a client terminal indicating that a task of interest for a target element has been completed, sets an edge indicating task completion between the element node corresponding to the target element and the task node corresponding to the target task.

[0011] A second data processing program of the present invention causes a computer to function as database storage means for storing a graph-structured database and as data processing means for processing data in the database, wherein the database is set with a plurality of element nodes indicating elements used when constructing a construction object consisting of a plurality of elements, a plurality of process nodes indicating processes for constructing the construction object, a plurality of task nodes indicating tasks included in one or more of the processes, and a plurality of attribute nodes indicating attributes related to the element nodes and the process nodes, wherein an edge indicating a relationship between each of the process nodes and the task nodes is set, and an edge indicating a relationship between each of the process nodes and the attribute nodes is set, and wherein the data processing means, when receiving input from a client terminal indicating that a task of interest for a target element has been completed, sets an edge indicating task completion between the element node corresponding to the target element and the task node corresponding to the target task.

[0012] A third data processing method of the present invention is a data processing method performed by a data processing device, the data processing device having a database holding means and a data processing means, the database holding means holding a database with a graph structure, the data processing means processing data of the database, the database being set with a plurality of element nodes indicating elements used when constructing a construction object consisting of a plurality of elements, a plurality of process nodes indicating processes when constructing the construction object, a plurality of task nodes indicating tasks included in one or more of the processes, and a plurality of attribute nodes indicating attributes of the element nodes and the process nodes, each of the process nodes having an edge indicating a relationship with the task node, each of the process nodes having an edge indicating a relationship with the attribute node, and the data processing means, when receiving input from a client terminal indicating that a task of interest for an element of interest has been completed, sets an edge indicating task completion between the element node corresponding to the element of interest and the task node corresponding to the task of interest. [Effects of the Invention]

[0014] According to the present invention, it is possible to provide a data structure, a data processing system, a data processing program, and a data processing method that enable more efficient processing when managing the construction of a construction property. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a block diagram showing the overall configuration of a data processing system according to an embodiment; [Figure 2]FIG. 2 is a block diagram illustrating an example of a hardware configuration of a server according to an embodiment. [Figure 3] 2 illustrates an example of the configuration of a construction management DB according to the embodiment. [Figure 4] FIG. 10 is a diagram showing the relationship between process work groups and attribute groups in a construction management DB according to the embodiment. [Figure 5] FIG. 10 is a diagram (part 1) showing the relationship between component nodes of an element group (component subgroup) and nodes of other groups in a construction management DB according to the embodiment. [Figure 6] FIG. 10 is a diagram (part 2) showing the relationship between the component nodes of an element group (component subgroup) and the nodes of other groups in the construction management DB according to the embodiment. [Figure 7] FIG. 10 is a diagram (part 1) showing data transitions (transitions of relationships) accompanying the progress of work on a certain component node in a construction management DB according to the embodiment. [Figure 8] FIG. 10 is a diagram (part 2) showing data transitions (transitions in relationships) accompanying progress of work on a component node in the construction management DB according to the embodiment. [Figure 9] FIG. 10 is a diagram (part 3) showing data transitions (transitions in relationships) accompanying the progress of work on a certain component node in the construction management DB according to the embodiment. [Figure 10] FIG. 10 is a diagram (part 4) showing data transitions (transitions of relationships) accompanying the progress of work on a certain component node in the construction management DB according to the embodiment. [Figure 11] 10 is a flowchart showing the operation of initially constructing an implementation management DB in the data processing system according to the embodiment. [Figure 12] FIG. 10 is a diagram showing an example of the configuration of process work group definition data that constitutes a construction management DB according to the embodiment. [Figure 13] 10 is a diagram showing an example of the configuration of import data used to configure a construction management DB according to the embodiment. FIG. [Figure 14] 10 is a diagram showing an example of the configuration of attribute definition data used in the configuration of a construction management DB according to the embodiment. FIG. [Figure 15] FIG. 10 is a diagram showing an example of the configuration of a construction management screen presented on a client terminal in the data processing system according to the embodiment. [Figure 16] 10A and 10B are diagrams showing an example (part 1) of the transition of a construction management screen presented on a client terminal in the data processing system according to the embodiment. [Figure 17] FIG. 10 is a diagram showing an example (part 2) of transition of a construction management screen presented on a client terminal in the data processing system according to the embodiment. [Figure 18] FIG. 10 is a diagram showing an example (part 3) of the transition of the construction management screen presented on the client terminal in the data processing system according to the embodiment. [Figure 19] FIG. 10 is a diagram showing an example (part 4) of the transition of the construction management screen presented on the client terminal in the data processing system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] The first invention is characterized in that a data structure consisting of a graph-structured database has (1) a plurality of element nodes indicating elements used when constructing a construction object, (2) a plurality of process nodes indicating processes when constructing a construction object, (3) a plurality of work nodes indicating work included in one or more of the processes, and (4) a plurality of attribute nodes indicating attributes related to the element nodes and the process nodes, (5) each of the process nodes has a relationship established with one or more of the work nodes, (6) each of the process nodes has a relationship established with one or more of the attribute nodes, and (7) each of the element nodes has a relationship established with one or more of the attribute nodes.

[0017] The second aspect of the present invention is a data processing system comprising a data processing means for processing data in a database comprising the data structure of the first aspect of the present invention.

[0018] A third data processing program of the present invention is a data processing program that causes a computer to function as data processing means for processing data in a database having the data structure of the first invention.

[0019] The fourth invention is a data processing method performed by a data processing system, characterized in that (1) the data processing system comprises a data processing means, and (2) the data processing means processes each node and data of each node that constitutes the data structure of the first invention.

[0020] (A) Main embodiment Hereinafter, an embodiment of a data structure, a data processing system, a data processing program, and a data processing method according to the present invention will be described in detail with reference to the drawings.

[0021] (A-1) Configuration of the embodiment FIG. 1 is a block diagram showing the overall configuration of a data processing system 1 according to this embodiment.

[0022] The data processing system 1 is a system for managing the construction of a building object X.

[0023] In this embodiment, the building X is a building, and the building is described as being composed of a large number of components. In this embodiment, the process of constructing the building X involves multiple steps, and each step includes multiple tasks. Each task uses one or more components.

[0024] Also, in this embodiment, for the sake of simplicity, the data processing system 1 is described as performing construction management of one construction object X, but the data processing system 1 may also be configured to perform construction management of multiple construction objects simultaneously.

[0025] Next, the overall configuration of the data processing system 1 will be described with reference to FIG.

[0026] In this embodiment, the data processing system 1 has a server 10 and a plurality of client terminals connected to the server 10 via a network NW. In this embodiment, for ease of explanation, the data processing system 1 is described as having three client terminals 21, 22, and 23, but the number and types of client terminals included in the data processing system 1 are not limited.

[0027] The server 10 and the client terminal provide a service of an application (hereinafter referred to as "data processing application" or "data processing AP") that processes information related to the construction management of the construction property X (for example, information processing such as input reception and reading of information related to the construction management of property X and database editing) to a user (for example, a user of a client terminal). A user of the data processing AP corresponds to, for example, a field worker, a field supervisor, a designer, a component manager, etc. in the construction (construction) of the construction property X.

[0028] Next, an example of the internal functional configuration of the server 10 will be described with reference to FIG.

[0029] The server 10 has graph DB middleware 11, a back-end AP 12 (back-end application), Web service middleware 13, and a construction management DB 15. In addition, a front-end AP 14 (front-end application) is installed on the Web service middleware 13.

[0030] In the server 10, information relating to the construction management of the construction object X is recorded in a construction management DB 15, which is a database with a graph structure (hereinafter referred to as a "graph DB"). The construction management DB 15 employs a data structure according to the present invention.

[0031] The graph DB middleware 11 is middleware (platform) that processes data of the implementation management DB 15, which is a graph DB. As the graph DB middleware 11, various middleware (platforms) compatible with graph DBs, such as Neo4J and JanusGraph, can be applied. Note that in this embodiment, the graph DB middleware 11 will be described as being applied to Neo4J.

[0032] Furthermore, the web service middleware 13 can be various web service middleware such as Apache and Nginx.

[0033] On the server 10, the data processing AP is realized by the cooperative operation of the back-end AP 12 and the front-end AP 14 installed on the Web service middleware 13. In the server 10, the front-end AP 14 is mainly responsible for the interface function with client terminals (Web-based interface) among the server functions of the data processing AP, while the back-end AP 12 is responsible for other functions (for example, data processing functions for the implementation management DB 15). The back-end AP 12 processes data for the implementation management DB 15 via the graph DB middleware 11.

[0034] In this embodiment, the server function of the data processing AP is realized by two elements: the back-end AP 12 and the front-end AP 14. However, the specific program configuration (e.g., the number of program elements) that realizes the server function of the data processing AP is not limited, and various configurations can be applied. Hereinafter, the programs that realize the server function of the data processing AP are collectively referred to as "data processing server applications" or "data processing server APs," and the programs that realize the client function are referred to as "data processing client applications" or "data processing client APs." In this embodiment, the data processing server AP can be said to be realized by programs / software including the back-end AP 12 and the front-end AP 14. In addition, in this embodiment, the data processing client AP can be said to be realized by APs 211 and 221 installed (downloaded) on the client terminal side, or an application (Web application) executed on the Web browser 231.

[0035] The detailed structure of the implementation management DB 15 will be described later.

[0036] Next, an example of the configuration of each client terminal will be described.

[0037] The client terminals connected to the server 10 may be various types of terminals such as smartphones, tablets, and PCs. In this embodiment, the client terminals connected to the server 10 are assumed to be a client terminal 21 configured as a smartphone, a client terminal 22 configured as a tablet, and a client terminal 23 configured as a PC.

[0038] The client terminal 21, which is a smartphone, has a touch panel display 212 as a user interface (input / output) device. The client terminal 22, which is a tablet PC, has a touch panel display 222 as a user interface (input / output) device. Applications 211 and 221 that perform the client function of the data processing AP (client function for connecting to the front-end AP 14) are installed on the client terminals 21 and 22, respectively.

[0039] The client terminal 23, which is configured as a PC, has a display 232 and an input device 233 as user interface (input / output) devices. The input device 233 can be, for example, a combination of devices such as a keyboard and a pointing device (e.g., a mouse or touchpad). A web browser 231 is installed on the client terminal 23. In the client terminal 23, the web browser 231 accesses the server 10 (front-end AP 14), whereby a web application (a program that performs the client function of the data processing AP) is downloaded and executed on the web browser 231. Note that in this embodiment, the client terminal 23, which is configured as a PC, uses the web browser 231 to realize the client function of the data processing AP, but it may also be configured as a separate application, as with other client terminals.

[0040] Next, an example of the hardware configuration of the server 10 will be described.

[0041] FIG. 2 is a block diagram showing an example of the hardware configuration of the server 10. As shown in FIG.

[0042] FIG. 2 shows an example of a hardware configuration when the server 10 is configured using software (computer).

[0043] 2 has, as a hardware component, a computer 1000 on which a program (including a data processing program (a program corresponding to the data processing server AP) of the embodiment) is installed. The computer 1000 may be a computer dedicated to the data processing server AP as the data processing program, or may be configured to be shared with programs of other functions.

[0044] The computer 1000 shown in FIG. 2 includes a processor 1001, a primary storage unit 1002, and a secondary storage unit 1003. The primary storage unit 1002 is a storage unit that functions as a working memory for the processor 1001, and may be, for example, a high-speed memory such as a dynamic random access memory (DRAM). The secondary storage unit 1003 is a storage unit that records various data such as an operating system (OS) and program data (including data for a data processing program (data processing server AP) according to an embodiment), and may be, for example, a non-volatile memory such as a flash (registered trademark) memory, HDD, or SSD. In the computer 1000 according to this embodiment, when the processor 1001 starts up, the OS and programs (including the data processing program according to an embodiment) recorded in the secondary storage unit 1003 are loaded and executed on the primary storage unit 1002.

[0045] Note that the specific configuration of the computer 1000 is not limited to the configuration in Fig. 2, and various configurations can be applied. For example, if the primary storage unit 1002 is a non-volatile memory (e.g., a flash memory), the secondary storage unit 1003 may be excluded.

[0046] In addition, in the client terminals 21 and 22, the applications 211 and 221 are realized (executed) on a computer having a configuration similar to that of the computer 1000 shown in Fig. 2. Furthermore, in the client terminal 23, the web browser 231 and the application executed by the web browser 231 are realized (executed) on a computer having a configuration similar to that of the computer 1000 shown in Fig. 2.

[0047] Next, the internal structure of the implementation management DB 15 will be described.

[0048] As described above, the construction management DB 15 is a graph DB (a database with a graph structure).

[0049] In addition, some of the data in the construction management DB 15 will be described as data expanded based on data modeled using a BIM (Building Information Modeling) design tool such as Autodesk's Revit (registered trademark). In other words, the construction management DB 15 will be described as having a structure that allows for projection (expandability) of part of the data (hereinafter referred to as "modeling data") modeled using a BIM design tool for a construction property. Note that the design tool supported by the construction management DB 15 is not limited to Revit, and may also be modeling data from other BIM design tools such as ARCHICAD or GLOOBE, or CAD data such as AutoCAD. Figure 1 illustrates modeling data MD for construction property X.

[0050] In this embodiment, the term "components / elements" refers to objects registered in the modeling data MD as components / elements that constitute the construction object X. The components / elements that constitute the construction object X may also include components / elements (for example, construction scaffolding, cranes, etc.) that are used during the construction of the construction object X.

[0051] A graph DB has a network-type structure consisting of circular entities called nodes (vertices) and arrow-shaped entities called relationships (edges) that indicate the relationships between nodes.

[0052] FIG. 3 shows an example of the configuration of the implementation management DB 15 in this embodiment.

[0053] As shown in FIG. 3, the construction management DB 15 of this embodiment is also configured with circular nodes and relationships indicated by arrows.

[0054] First, the nodes that make up the construction management DB 15 will be described.

[0055] As shown in Fig. 3, the nodes that make up the construction management DB 15 are divided into multiple groups. As shown in Fig. 3, the nodes that make up the construction management DB 15 are broadly divided into multiple groups including process operation groups, element groups, and attribute groups.

[0056] The process operation group node is further divided into a plurality of subgroups. Specifically, the process operation group node is divided into a plurality of subgroups including an operation subgroup and a process subgroup.

[0057] Each attribute group is further divided into a plurality of subgroups. In the example of Fig. 3, the attribute groups include a layer subgroup, a component name subgroup, a material subgroup, a room subgroup, and a floor subgroup.

[0058] The number of nodes that make up each group / subgroup is not limited, but the example in Figure 3 only illustrates a portion of the nodes that make up the construction property X. Also, in the example in Figure 3, each node shown is given a symbol.

[0059] In the construction management DB15 shown in Figure 3, the process subgroup includes two nodes A1 and A2, the work subgroup includes four nodes B1 to B4, the component group includes ten nodes C1 to C10, the layer subgroup includes nodes D1 to D5, the component name subgroup includes nodes E1 to E7, the material subgroup includes nodes F1 to F4, the room subgroup includes nodes G1 to G3, and the floor subgroup includes nodes H1 and H2.

[0060] In this embodiment, it is assumed that an ID for identifying each component is assigned as the name of each component node.

[0061] In FIG. 3, for the sake of simplicity, the relationships between groups are not shown.

[0062] Here, an overview of the correspondence between the group / subgroup of each node and the modeling data MD will be described.

[0063] For each node, the upper string indicates the node's label, and the lower string indicates the node's name. Each node is labeled according to the group / subgroup to which it belongs. Nodes in groups without subgroups are labeled according to the group to which they belong, and nodes in subgroups are labeled according to the subgroup. Here, the process subgroup, operation subgroup, component subgroup, layer subgroup, component name subgroup, material subgroup, room subgroup, and floor subgroup are labeled "process," "operation," "component," "layer," "component name," "material," "room," and "floor," respectively. Below, each node is sometimes referred to in the format "label + node + symbol." For example, since the label of node C1 is "component," node C1 may also be referred to as "component node C1." Below, the nodes of each group / subgroup are sometimes referred to collectively in the format "group name / subgroup name + node." For example, the nodes of the component subgroup are collectively referred to as "component nodes."

[0064] As described above, in this embodiment, each member node has a one-to-one relationship with the object of each member that constitutes the construction X in the modeling data MD.

[0065] In this embodiment, each of the subgroups (layer, component name, material, room, floor, etc.) that make up the attribute group is considered to be a data item registered or associated in the modeling data MD with each component object that makes up the construction property X. In other words, in the modeling data MD, data for items corresponding to the items layer, component name, material, room, floor, etc. are registered or associated with each component object. Note that the names of the attributes in the construction management DB 15 (the names of the subgroups that make up the attribute group) do not need to be exactly the same as the names of the items in the modeling data MD (the names of the items that correspond to component objects). For example, when converting (importing) the modeling data MD to the construction management DB 15, an item defined as "floor number" may be changed to "floor" to create a floor subgroup (a node whose label is "floor").

[0066] Furthermore, in this embodiment, the processes and tasks corresponding to the process work group will be described as not being related to the items included in the modeling data MD. Therefore, in this embodiment, the nodes (process nodes and task nodes) belonging to the process work group will be described as being set by the user (the editor of the construction management DB 15).

[0067] As described above, in this embodiment, the group / subgroup of each node is associated with the modeling data MD.

[0068] In the drawings of this embodiment, if a type is not explicitly shown on a relationship arrow, it is assumed that a type called "DEFINE" is set, which defines the relationship between nodes. Also, in the drawings of this embodiment, it is assumed that the type and property contents may be explicitly added to the relationship arrow. In the drawings of this embodiment, types and properties (one or more pairs of keys and values) are illustrated in the format "type name:{first key:first value, second key:second value, ...}". For example, if "TASK:{sort:1}" is added to a relationship arrow, it indicates that the type is "TASK" and the value of the key called "sort" in the property is set to "1".

[0069] Figure 3 only illustrates the relationship between the process subgroups and the operation subgroups.

[0070] In Fig. 3, the names of process nodes A1 and A2 are "duct work" and "piping work," respectively. Also, in Fig. 3, the names of work nodes B1 to B4 are "delivery instructions," "carry-in," "installation," and "insulation," respectively.

[0071] Process node A1 (duct work) is connected to work nodes B1, B2, and B4 through TASK-type relationships. Here, TASK-type relationships describe the work included in a process and their order. In a TASK-type relationship, a SORT key indicating the work order is set as a property, with the numerical value of the order corresponding to the connected work node set as its value. In Figure 3, the SORT key for the relationship between A1 and B1 is set to "1," the SORT key for the relationship between A1 and B2 is set to "2," and the SORT key for the relationship between A1 and B4 is set to "3."

[0072] Therefore, in this case, "duct work" (process node A1) includes the tasks "delivery instructions," "delivery," and "insulation" (work nodes B1, B2, B4), and the order is (1) "delivery instructions," (2) "delivery," and (3) "insulation." Similarly, in Figure 3, "piping work" (process node A2) includes the tasks "delivery instructions," "delivery," and "installation" (work nodes B1, B2, B3), and the order is (1) "delivery instructions," (2) "delivery," and (3) "installation."

[0073] Next, the relationship between the process operation group and the attribute group will be explained with reference to FIG.

[0074] In this embodiment, it is assumed that a DEFINE type relationship is set with an associated attribute node for each process node.

[0075] In this embodiment, it is assumed that a DEFINE type relationship is set with each process node and its associated layer node. Note that in this embodiment, for ease of explanation, the layer nodes are shown as the only attribute group nodes connected to the process nodes (connected by DEFINE type relationships), but they may also be connected to other subgroup nodes of the attribute group.

[0076] In this embodiment, the names of the layer nodes D1 to D5 are "exhaust," "air conditioning equipment," "transport equipment," "hot and cold water," and "cooling water," respectively.

[0077] Here, layers correspond to the layers set in the modeling data MD in the BIM design tool. Therefore, the following explanation will be given assuming that the modeling data MD contains at least five layers: "Exhaust," "Air Conditioning Equipment," "Conveying Equipment," "Hot and Chilled Water," and "Cooling Water."

[0078] Furthermore, in the BIM design tool, the objects (i.e., components) displayed change for each layer. In other words, in the BIM design tool, one or more layers are associated with each object representing a component / element. As will be described later, in the construction management DB 15, each component node is connected to the layer node of the corresponding layer through a DEFINE-type relationship based on the data in the modeling data MD. In other words, in the construction management DB 15, the corresponding layer is described for each component.

[0079] In this embodiment, process node A1 (duct work) is connected to layer nodes D1 to D3 ("exhaust," "air conditioning equipment," and "transport equipment") through DEFINE type relationships, as shown in Fig. 4. Also, in this embodiment, process node A2 (piping work) is connected to layer nodes D2 to D5 ("air conditioning equipment," "transport equipment," "hot and cold water," and "cooling water") through DEFINE type relationships, as shown in Fig. 4.

[0080] In this way, in the construction management DB 15, each process node is associated with the corresponding layer node through a DEFINE-type relationship. In other words, Figure 4 shows that "duct work" is associated with the layers of "exhaust," "air conditioning equipment," and "conveyance equipment." Also, Figure 4 shows that "piping work" is associated with the layers of "air conditioning equipment," "conveyance equipment," "hot and cold water," and "cooling water."

[0081] Next, the relationship between the member nodes of the element group (member subgroup) and the nodes of other groups will be described with reference to FIGS.

[0082] 5 and 6 are diagrams showing the relationship between the member nodes of an element group (member subgroup) and the nodes of other groups.

[0083] In FIG. 5, for ease of explanation, only the member node C1 of the member subgroup is extracted and illustrated.

[0084] As shown in Figure 5, component node C1 is connected to layer node D1 (exhaust), component name node E1 (exhaust duct 475φ), material node F1 (galvanized steel plate), room node G2 (machine room), and floor node H1 (1FL) through DEFINE type relationships.

[0085] In this case, the component corresponding to component node C1 is displayed on the "Exhaust" layer, with the component name "Exhaust duct 475φ" and the material "Galvanized steel sheet," and it is located in the "Machine room" on 1FL (first floor). As mentioned above, the items in each subgroup of the attribute group are data for the items registered or associated with the object of the component in the modeling data MD.

[0086] As described above, each member node is associated with one or more attribute nodes through a DEFINE-type relationship. In this embodiment, each member node is associated with multiple attribute nodes, including at least a layer node.

[0087] A process node is connected to one or more attribute nodes (nodes of any of its subgroups) and one or more work nodes through DEFINE-type relationships. In other words, in the construction management DB 15, each component node is related to one or more work nodes via attribute nodes and process nodes.

[0088] For example, as shown in Figure 5, component node C1 is associated with layer node D1 (exhaust). Process node A1 (duct work) is associated with layer node D1 (air conditioning equipment) and operation nodes B1, B2, and B4.

[0089] Therefore, component node C1 is associated with work nodes B1, B2, and B4 ("Delivery instruction," "Delivery," and "Insulation") via layer node D1 (exhaust) and process node A1 (duct work).

[0090] This shows that material node C1 contains the tasks "Delivery instructions," "Carry-in," and "Keep warm" that correspond to work nodes B1, B2, and B4. Each work node has a Sort key value set as a sequence number, so for material node C1, this shows that the work will be performed in the following order: (1) "Delivery instructions," (2) "Carry-in," and (3) "Keep warm."

[0091] In the construction management DB 15, each component node may be associated with multiple process nodes.

[0092] FIG. 6 extracts only the member node C5 from the member subgroup and illustrates the relationship between the member node C5 and other nodes.

[0093] As shown in FIG. 6, component node C5 is associated with layer node D2 (air conditioning equipment). Furthermore, process node A1 (duct work) is associated with layer node D1 (air conditioning equipment) and operation nodes B1, B2, and B4 ("Delivery instructions," "Delivery," and "Insulation"). Furthermore, process node A2 (piping work) is associated with layer node D2 (air conditioning equipment) and operation nodes B1, B2, and B3 ("Delivery instructions," "Delivery," and "Installation"). In other words, layer node D2 (air conditioning equipment) is associated with two process nodes A1 and A2 (duct work, piping work).

[0094] Therefore, component node C5 is associated with work nodes B1 to B4 ("Delivery instructions," "Carry-in," "Installation," and "Insulation") via layer node D2 (air conditioning equipment) and process nodes A1 and A2 (duct work, piping work). This indicates that component node C5 includes the work nodes B1 to B4, which correspond to "Delivery instructions," "Carry-in," "Installation," and "Insulation," as tasks.

[0095] In this case, since the Sort keys for both work node B3 (installation) and work node B4 (keep warm) are 3, the data processing system 1 may determine the order of work nodes B3 and B4 (installation, keep warm) based on some criteria. For example, the data processing system 1 may determine a priority for each work node in advance and set a value corresponding to the priority in the property. For example, a value (numeric value) may be set for each work node using a key named Priority, which indicates the order priority, and if there are work nodes with the same Sort value, one of the work nodes may be given priority depending on the Priority value.

[0096] Here, the following description will be given assuming that the data processing system 1 is set so that when the sorts of the work nodes B3 and B4 (installation, insulation) are the same, the work node B3 (installation) is given priority.

[0097] In this case, in Figure 6, for component node C5, based on the Sort value, etc., it is shown that work will be performed in the following order: (1) "Delivery instruction", (2) "Delivery", (3) Insulation, (4) "Insulation".

[0098] Next, the representation format for managing (construction management) the progress of work on each component (component node) in the construction management DB 15 will be described.

[0099] 7 to 9 are diagrams showing data transitions (transitions of relationships) that occur with the progress of work on the component node C1.

[0100] In the construction management DB 15, each component node is associated with a task node corresponding to a completed task through a DONE-type relationship. In this embodiment, the DONE-type relationship has a property set with a key called date, which indicates the timing of task completion (the date on which the task was completed), and its value.

[0101] As described above, the component node C1 includes the tasks "Delivery instruction," "Carry-in," and "Insulation" corresponding to the task nodes B1, B2, and B4. In Figure 6, the component node C1 is shown in its initial state (a state in which the component node C1 has only been generated based on the data in the modeling data MD), and no tasks related to the component node C1 have been completed yet.

[0102] That is, in Figure 7, from the state in Figure 6, a DONE type relationship is registered between component node C1 and task node B1 (delivery instruction) corresponding to the first task (task for which Sort: 1 is set) along with the completion date ("date: 2021 / 6 / 1" indicating the completion date). In other words, the state in Figure 7 indicates that the task for the first task node B1 (delivery instruction) for component node C1 was completed on "2021 / 6 / 1".

[0103] Also, in Figure 7, from the state of Figure 6, a DONE type relationship is registered between component node C1 and task node B2 (delivery) corresponding to the second task (task for which Sort:2 is set) along with the completion date ("date:2021 / 6 / 2" indicating the completion date). In other words, the state of Figure 8 indicates that the task for the second task node B2 (delivery) for component node C1 was completed on "2021 / 6 / 2".

[0104] Furthermore, in Figure 8, from the state in Figure 7, a DONE type relationship has been registered between component node C1 and task node B3 (heat retention), which corresponds to the third task (task for which Sort: 3 is set), along with the completion date ("date: 2021 / 6 / 3" indicating the completion date). In other words, the state in the figure shows that the task for the third task node B3 (heat retention) for component node C1 was completed on "2021 / 6 / 3".

[0105] As described above, Figures 7 to 9 respectively show the completed state of the first task (delivery instruction for work node B1), the completed state of the second task (delivery for work node B2), and the completed state of the third task (insulation for work node B3) for component node C1.

[0106] In the state shown in Figure 9, DONE type relationships are set between component node C1 and work nodes B1, B2, and B4 related to component node C1, indicating that all work related to component node C1 has been completed.

[0107] FIG. 10 is a diagram showing data transitions (transitions of relationships) that occur with the progress of work on the component node C5.

[0108] In the state of Figure 10, compared to the initial state of Figure 6, all relationships between component node C5 and work nodes B1 to B4 related to component node C5 are of the DONE type, which indicates that all work related to component node C5 has been completed.

[0109] As described above, the construction management DB 15 expresses the progress of work corresponding to each component node.

[0110] In this embodiment, the data processing server AP (back-end AP 12, front-end AP 14) edits the construction management DB 15 via the graph DB middleware 11 based on a request (i.e., a user operation) from a data processing client application (client terminal). That is, in this embodiment, the data processing server AP sets a DONE-type relationship between a component node and an operation node in the construction management DB 15 (associates the component node with the operation node).

[0111] An example of an operation screen (GUI) for the data processing AP to receive work progress information for each component (receive completed work information) from the user will be described later.

[0112] Next, an overview of data (each node and relationship) processing in the implementation management DB 15 by the data processing server AP (server 10) will be described.

[0113] As described above, various graph DB platforms can be applied to the graph DB middleware 11, but in this embodiment, neo4j is applied.

[0114] All graph DB platforms support a QL (Query Language; hereafter referred to as "graph DBQL") for defining data processing, and in the case of Neo4j, it supports a graph DBQL called CypherQL (hereafter referred to as "CQL").

[0115] In this embodiment as well, the backend AP 12 (data processing server AP) uses this CQL to instruct data processing (data processing for the construction management DB 15) for the graph DB middleware 11. By using the graph DBQL, the backend AP 12 (data processing server AP) can process data using nodes and relationships as elements.

[0116] (A-2) Operation of the embodiment Next, the operation of the data processing system 1 of this embodiment having the above configuration (data processing method of the embodiment) will be described.

[0117] FIG. 11 is a flowchart showing an example of processing in which the data processing system 1 uses data imported from the modeling data MD of the construction property X to initially construct a construction management DB 15 having a graph structure as shown in FIGS.

[0118] Here, the explanation will be given assuming that in the initial state, not even a single node has been set in the implementation management DB 15.

[0119] Here, an example will be described in which the data processing server AP performs the initial construction process for the construction management DB 15 in accordance with the flowchart of FIG.

[0120] First, the data processing server AP sets process nodes and work nodes in the construction management DB15 based on data describing the definition of the process nodes and work nodes that make up the process work group (hereinafter referred to as "process work group definition data") (S101).

[0121] There are no limitations on the means by which the data processing server AP stores the process work group definition data, but for example, the process work group definition data itself may be read from a client terminal used by a user (e.g., a designer or manager of construction property X), or an operation screen (GUI) may be provided to the data processing client application to accept input of data equivalent to the process work group definition data.

[0122] In this embodiment, the process work group definition data includes a list of processes, a list of tasks, a list of tasks included in each process, and the order of each task in each process (Sort number).

[0123] FIG. 12 is a diagram showing an example of the configuration of process operation group definition data.

[0124] Fig. 12(a) is a diagram showing a list of processes in a table format. The table shown in Fig. 12(a) shows that the processes include "duct work" and "piping work".

[0125] Fig. 12(b) is a diagram showing a list of tasks in table format. The table shown in Fig. 12(b) shows that the tasks include "delivery," "carry-in," "installation," and "heat retention."

[0126] FIG. 12(c) is a diagram showing, in table format, a list of tasks corresponding to each process and the order of each task (sort number) in each process. In the table shown in FIG. 12(c), the tasks included in each process are described along with the task order (sort number). Specifically, in the table shown in FIG. 12(c), the duct work process has delivery instruction as the first task, delivery as the second task, and insulation as the third task. In addition, in the table shown in FIG. 12(c), the piping work process has delivery instruction as the first task, delivery as the second task, and installation as the third task.

[0127] In step 101, the data processing server AP first sets process nodes A1 and A2 in the construction management DB 15 based on the table in Figure 12(a). Next, the data processing server AP sets work nodes B1 to B4 in the construction management DB 15 based on the table in Figure 12(b). Next, the data processing server AP sets TASK-type relationships between the process nodes and work nodes, along with Sort numbers, in the construction management DB 15 based on the table in Figure 12(c). As a result, the construction work group configuration in the construction management DB 15 will be as shown in Figure 3.

[0128] Next, the data processing server AP holds data (hereinafter referred to as "import data") of a list of components that make up the construction project X based on the modeling data MD (S102).

[0129] FIG. 13 is a diagram showing an example of the configuration of import data.

[0130] The import data shown in Figure 13 is a table in which information about one component is described in one line. The import data shown in Figure 13 describes data for each component, including the component name, floor, room, layer, and material name.

[0131] FIG. 13 shows that data including at least 10 components (components with component IDs 1 to 10) is registered in the import data.

[0132] There are no limitations on the means by which the data processing server AP stores the import data, but for example, the import data (e.g., data in CSV format) itself may be read from a client terminal used by a user (e.g., a designer or manager of construction property X), or the import data may be generated based on the modeling data MD.

[0133] As described above, data for items corresponding to at least each subgroup of an attribute group is set for each component object constituting the modeling data MD, so it is possible to generate import data such as that shown in Fig. 13 based on the modeling data MD. The data processing server AP may reflect all of the parameters (properties) set for each component object in the modeling data MD in the import data, or may reflect only a portion of the items (items required for the attribute group in the construction management DB 15) in the import data. The data processing server AP may also be configured to set up a list in advance of the items (list of subgroups) required for the attribute group in the construction management DB 15.

[0134] Next, the data processing server AP sets the element group nodes (component nodes) in the construction management DB 15 based on the import data (S103).

[0135] When the data processing server AP sets component nodes in the construction management DB 15 based on the import data of Fig. 13, the contents of the element groups in the construction management DB 15 will be as shown in Fig. 3. Fig. 3 shows component nodes including component nodes C1 to C10 described in the import data of Fig. 13.

[0136] Next, the data processing server AP sets the attribute group nodes (nodes for each subgroup) in the implementation management DB 15 based on the import data (S104).

[0137] The data processing server AP performs processing to add a node for each subgroup of the attribute group by referring to each item related to the attribute in the import data (in FIG. 13, the data in each column after the component ID).

[0138] For example, when the data processing server AP acquires import data such as that shown in Figure 13, it first performs a process to add a component name node (a component name subgroup node) to the attribute group based on the "component name" column that follows the component ID.

[0139] For example, the data processing server AP may read the column of component names starting from the first row and add them as component name nodes. In this case, if a component name node has already been added for the same component name in the read row, the data processing server AP performs processing to skip that row (processing to not generate a component name node with the same component name).

[0140] Therefore, in this case, the data processing server AP reads "Exhaust duct 475φ" in the first row of the component name column from the import data in Figure 13 and adds component name node E1, reads "Exhaust duct 600 x 450" in the second row and adds component name node E2, skips the third and fourth rows, reads "VRV A series" in the fifth row and adds component name node E3, and performs this process for all rows in the component name column.As a result, component name nodes E1, E2, E3, etc. are added to the construction management DB 15, as shown in Figure 3.

[0141] The data processing server AP then similarly generates floor nodes from the floor column of the imported data in Fig. 13, room nodes from the room column, layer nodes from the layer column, material names from the material name nodes, and so on for all columns after the component name. As a result, nodes for each subgroup of the attribute group (component name subgroup, floor subgroup, room subgroup, layer subgroup, material name subgroup, ...) are added to the construction management DB 15, as shown in Fig. 3.

[0142] Next, the data processing server AP sets the relationship between the process node and the attribute node based on data (hereinafter referred to as "attribute definition data") that defines the association between the attribute group and the process subgroup (content of the relationship) (S105).

[0143] FIG. 14 is a diagram showing an example of the structure of attribute definition data.

[0144] As described above, in this embodiment, it is assumed that the process node is associated (a relationship is set) only with the layer node among the attribute nodes.

[0145] The attribute definition table shown in FIG. 14 defines the layers associated with each process.

[0146] In the attribute definition data shown in Figure 14, layer items are set in each row, and process items are set in each column. In the attribute definition data shown in Figure 14, either a value of "1" indicating that a DEFINE type relationship is to be set, or a value of "0" indicating that no relationship is to be set, is entered in each row of each process column.

[0147] For example, in the attribute definition data shown in Figure 14, in the column for duct work, a value of 1 is set in the rows for "exhaust," "air conditioning equipment," and "conveyance equipment," and a value of 0 is set in the other rows. Therefore, in this case, the data processing server AP will set a DEFINE-type relationship between the process node A1 (duct work) and the layer nodes D1, D2, and D3 (exhaust, air conditioning equipment, conveyance equipment). Similarly, in the attribute definition data shown in Figure 14, a value of 1 is set in the rows for "air conditioning equipment," "conveyance equipment," and "chilled / hot water" in the column for piping work, so a DEFINE-type relationship will be set between the process node A2 (piping work) and the layer nodes D2, D3, and D4 (exhaust, air conditioning equipment, chilled / hot water).

[0148] As described above, in this embodiment, the data processing server AP identifies the attribute nodes associated with each process node based on the attribute definition data shown in Fig. 14, and performs processing to set the relationships between each process node and the associated attribute nodes. As a result, in the construction management DB 15, the relationships between process subgroups and attribute groups will be as shown in Fig. 4.

[0149] The content of the attribute definition data is not limited to a specific table format as long as the attributes (layers) related to each process are defined.

[0150] Next, a configuration example of an operation screen (hereinafter referred to as a "construction management screen") that can manage the work progress of each component (each component that constitutes construction object X) managed by construction management DB 15 will be described.

[0151] FIG. 15 is a diagram showing an example of the configuration of the construction management screen.

[0152] In Figure 15, there are arranged field F100 for accepting settings to narrow down the components to be displayed on the construction management screen (hereinafter referred to as ``display narrowing settings''), field F200 for accepting settings for the display units on the construction management screen (hereinafter referred to as ``display unit settings''), and field 300 for performing display output processing and input reception processing (hereinafter referred to as ``construction management processing'') of work progress in display units according to the display unit settings for components within the relevant range of the display narrowing settings.

[0153] In the display refinement setting field F100, an object B101 for receiving input of a process name (hereinafter also referred to as a "process name input object") and an object B102 for receiving input of an attribute name (hereinafter also referred to as an "attribute name input object") are arranged. Note that in the display refinement setting field F100, multiple objects B102 can be arranged, and an object B103 for receiving addition of an object B102 (hereinafter referred to as an "attribute addition object") is also arranged. Each object B102 has a sub-object B102a for receiving input of a sub-group name within the attribute group, and a sub-object B103b for receiving an attribute name (an attribute name within the sub-group set by the sub-object B102a).

[0154] In the object B101, it is assumed that the process name can be input and accepted by menu selection (for example, selection from a pull-down menu, etc.).

[0155] Sub-object B102a constituting object B102 allows for menu selection (e.g., selection from a pull-down menu) of a sub-group name (the name of one of the sub-groups of the attribute group), and sub-object B102b allows for menu selection (e.g., selection from a pull-down menu) of an attribute name (the attribute name within the sub-group selected by sub-object B102a).

[0156] In the display refinement setting field F100, multiple objects B102 can be displayed. Then, in the display refinement setting field F100, when an object B103 is operated (for example, touched on a touch panel or clicked with a mouse), an object B102 is additionally displayed in the display refinement setting field F100.

[0157] The filtering condition set in the display filter setting field F100 is an AND condition between the process name entered in the object B101 and all the attribute names entered in the object B102. For example, if the process name "Duct Work" is entered in the object B101 and "Layer / Exhaust" is entered in one object B102 in the display filter setting field F100, the filtering condition will be "Process Name: Duct Work" AND "Layer / Exhaust." Also, if the process name "Duct Work" is entered in the object B101 and "Layer: Exhaust" and "Floor: 2FL" are entered in two objects B102 in the display filter setting field F100, the filtering condition will be "Process Name: Duct Work" AND "Layer: Exhaust" AND "Floor: 2FL."

[0158] In the display unit setting field F200, there are arranged a plurality of radio button objects B201 (B201-1 to B201-3) for receiving a selection of setting the display unit as a set value, an object B203 for receiving input of an arbitrary display unit, a radio button B202 for receiving a selection of setting the display unit to the set value (arbitrary display unit) input to the object B203, and an object B204 for receiving addition of the radio button object B201. In the example of Fig. 15, the radio button objects B201-1 to B201-3 are set with the display units "per component", "per floor" (floor unit of floor subgroup), and "per room (floor-room unit)" (room unit of room subgroup), respectively.

[0159] Object B203 can accept input of a subgroup name (either a subgroup name of a process operation group or a subgroup name of an attribute group) by menu selection (for example, selection from a pull-down menu, etc.).

[0160] In the display unit setting field F200, when the object B204 is operated (for example, touched on a touch panel or clicked with a mouse), a radio button object B201 is added whose setting value is the content input to the object B203.

[0161] Next, an example of the operation of the construction management screen configured as above will be described with reference to FIGS.

[0162] 16 to 18 are diagrams showing examples of transitions of the construction management screen.

[0163] On the construction management screen, the progress of work is displayed in the construction management processing field F300 for components that correspond to the filter settings set in the display filter setting field F100, in the display unit set in the display unit setting field F200.

[0164] For example, in the example of Figure 15, only "Process name: Duct work" is set as the display filter setting in the display filter setting field F100, and "Component unit" is set as the display unit setting in the display unit setting field F200 (the radio button for object B201-1 is selected).

[0165] Therefore, in the construction management processing field F300, work progress information (progress status of each work) for each component (each component with component ID 1 to 6) corresponding to "Process name: Duct work" is displayed (displayed in display items) in matrix format (table format).

[0166] In Figure 15, the display unit is "per component," so one line displays the work progress information for one component. In this example embodiment, when the display unit is "per component," the construction management processing field F300 displays the component ID and component name for each component, as shown in Figure 15.

[0167] In addition, in the construction management processing field F300 (work progress information) of this embodiment, a status (hereinafter referred to as "work status") is set in a cell corresponding to each task (in the example of FIG. 15, each of the delivery instructions, delivery, and insulation tasks related to duct work) of each task unit (in the example of FIG. 15, each of the components) In this embodiment, the work status of each component unit is displayed as either a blank (NULL) indicating that the task has not been performed, or "performed" indicating that the task has been performed.

[0168] In the construction management process field F300, when a cell displaying one of the work statuses is selected (for example, by touching a touch panel or clicking a mouse), input to change that work status may be accepted. For example, when a cell displaying one of the work statuses is selected in the construction management process field F300, a menu selection (for example, selection from a pull-down menu) may be made possible.

[0169] When the work status of any cell is changed in the implementation management process field F300, the server 10 updates (switches the display of) the contents of the implementation management DB 15 in accordance with the change.

[0170] For example, in the state of FIG. 15, the delivery instruction and delivery work have been completed for the component with component ID: 1, but the insulation work has not yet been completed. In other words, in the state of FIG. 15, the relationship state for component node C1 alone is the state of FIG. 8. Then, from the state of FIG. 15, cell C301 corresponding to the insulation work for component ID: 1 is selected and changed to a completed state, resulting in the state shown in FIG. 16. Then, the data processing server AP (server 10) controls the construction management DB 15 to connect component node C1 to the work node B3 corresponding to the insulation work through a DONE-type relationship and set the date to the current date (the date on which cell C301 was updated to completed). Then, the relationship state for component node C1 becomes the state shown in FIG. 9.

[0171] Next, examples of other setting patterns for the implementation management screen (display refinement setting field F100 and display unit setting field F200) will be described with reference to FIGS.

[0172] First, an example (part 2) of a setting pattern for the construction management screen will be described with reference to FIG.

[0173] In the example of Figure 17, only "Process name: Duct work" is set as the display filter setting in the display filter setting field F100, and "Room (floor-room unit)" is set as the display unit setting in the display unit setting field F200 (the radio button for object B201-3 is selected).

[0174] Therefore, in Figure 17, the construction management processing field F300 displays (displays in display items) work progress information (progress status of each work) for each component (each component with component ID 1 to 6) corresponding to "Process Name: Duct Work" by room.

[0175] In Fig. 17, the display unit is "room (floor-room unit)", so one line displays the work progress information for one "room". In this embodiment, when the display unit is "room (floor-room unit)", as shown in Fig. 17, the construction management processing field F300 displays the room name and floor name (the floor name of the floor on which the room is located) for each room.

[0176] In addition, in the construction management processing field F300 (work progress information) of this embodiment, a work status is set in a cell corresponding to each task (in the example of FIG. 17, each of the delivery instructions, delivery, and insulation tasks related to duct work) of each task unit (in the example of FIG. 17, each of the rooms) In this embodiment, the work status for each component unit is displayed as either a blank (NULL) indicating that the task has not been completed for all components of the room, "in progress" indicating that the task has been completed for only some of the components of the room, or "completed" indicating that the task has been completed for all components of the room.

[0177] In this embodiment, in the construction management processing field F300 (work progress information), a value indicating the percentage of all components that have been completed (hereinafter referred to as the "progress rate") may be added to cells where the work status for multiple components is "in progress." For example, if five of ten components in a certain room have been completed, the cell corresponding to that room may be displayed with the notation "in progress (50%)" and the progress rate (50%).

[0178] Next, an example (part 3) of a setting pattern for the construction management screen will be described with reference to FIG.

[0179] In the example of Figure 18, only "Process name: Duct work" is set as the display filter setting in the display filter setting field F100, and "Layer" is set as the display unit setting in the display unit setting field F200 (the radio button for object B202 is selected and "Layer" is entered in object B203).

[0180] Therefore, in Figure 18, the construction management processing field F300 displays work progress information (progress status of each work) for each component (each component with component ID 1 to 6) corresponding to the "Process Name: Duct Work" on a layer-by-layer basis.

[0181] In Fig. 18, the display unit is "layer," so one line displays the work progress information for one "layer." In this embodiment, when the display unit is "layer," the layer name is displayed (displayed in the display item) for each layer in the construction management process field F300, as shown in Fig. 18.

[0182] In addition, in the construction management processing field F300 (work progress information) of this embodiment, a work status is set in a cell corresponding to each task (in the example of FIG. 18, each layer) of each task unit (each layer in the example of FIG. 18, the delivery instructions, delivery, and insulation tasks related to duct work). In this embodiment, the work status for each layer is displayed as either a blank (NULL) indicating that the work has not been completed for all components of the layer, "In Progress" indicating that the work has been completed for only some of the components of the layer, or "Completed" indicating that the work has been completed for all components of the layer. Note that the progress rate may also be added to the work status for each layer, as described above.

[0183] Next, an example (part 4) of a setting pattern for the construction management screen will be described with reference to FIG.

[0184] In the example of Figure 19, only "Process name: Piping work" is set as the display filter setting in the display filter setting field F100, and "Component unit" is set as the display unit setting in the display unit setting field F200 (the radio button for object B201-1 is selected).

[0185] Therefore, in Figure 19, the construction management processing field F300 displays (displays in display items) work progress information (progress status of each work) for each component (each component with component ID 5 to 10) corresponding to "Process Name: Piping Work" on a component-by-component basis.

[0186] (A-3) Effects of the embodiment According to this embodiment, the following effects can be achieved.

[0187] (A-3-1) In the data processing system 1 of this embodiment, it is possible to realize a construction management screen that allows display switching more efficiently (faster and with fewer resources) than systems that use conventional relational databases (hereinafter referred to as "RDBs").

[0188] In a traditional RDB, tables are linked to each other. The advantage of an RDB is that data processing is consistent, and it demonstrates great performance when executing routine processing even with huge amounts of data.

[0189] In this embodiment, the backend AP 12 (data processing server AP) uses graph DBQL to search for nodes with an indirect relationship (association) by tracing relationships (networks) and making multiple hops from any node. If a similar process were to be performed using an RDB and SQL, a JOIN statement (a statement for linking multiple elements (tables, etc.)) would need to be executed a number of times corresponding to the number of hops. As mentioned above, the number of components that make up a single building typically amounts to tens of thousands. Therefore, if the construction management DB 15 were to be constructed using an RDB, it would be massive, with records relating to tens of thousands of components registered in multiple intermediate tables. If the server 10 were to execute multiple JOIN statements on such a large-scale RDB, the hardware resources required for the server 10 (e.g., CPU, memory (primary storage), hard disk (secondary storage)) would be enormous. However, in this embodiment, since a graph DB structure is applied to the implementation management DB 15, the backend AP 12 (data processing server AP) only needs to extract and process the nodes to be processed (for example, nodes directly or indirectly connected to the node of interest via a relationship), which requires significantly fewer hardware resources than when an RDB is used. In particular, when the server 10 is hosted on the cloud, the running costs related to hardware resources are high, so the effect of reducing hardware resources in this way is significant.

[0190] For example, if each component node has a structure as shown in Figure 5 above and you want to search for a component node (a component located on 1FL) that belongs to floor node H1 (floor: 1FL), the backend AP12 (data processing server AP) can perform the search by simply using graph DBQL to obtain the component node (a node whose label is a component) that is connected to floor node H1 (floor: 1FL) by a relationship (Define type).

[0191] However, if you were to perform the same processing in an RDB, you would need to use a JOIN to combine the first table that manages each component with the second table that manages its attributes, and then execute a process to extract records that are 1F by referencing the floor column of all records. While it is not possible to simply compare the data processing volume of a graph DB with that of an RDB, if building property X is 10 stories tall (1F to 10F) and the number of components on each floor is uniform, then the number of records accessed in the RDB for the above-mentioned extraction process for one floor would be 10 times the number of nodes accessed in the graph DB. The larger the scale of building property X (e.g., the number of floors), the more significant the difference in processing volume between building it with a graph DB and building it with an RDB.

[0192] In other words, if the construction management database 15 is constructed using an RDB, extracting components by attributes as described above requires access to all records of the components. However, if the database is constructed using a graph database, only the nodes targeted for extraction need to be accessed. In other words, in the data processing system 1 of this embodiment, constructing the construction management database 15 using a graph database enables component extraction with a processing volume equal to the number of nodes targeted for processing, regardless of the total number of components. Project managers (e.g., site supervisors and managers) who manage the construction of the construction project X (particularly the construction management) are required to support faster display switching and input for construction management screen processing (e.g., information output and input) while supporting multiple display units, such as attribute group subgroups and process subgroups. Particularly at the construction site where the construction project X is being constructed, there is a demand for greater efficiency in construction management operations, and the speed of display switching significantly affects the efficiency of construction management operations.

[0193] (A-3-2) If an RDB were used to manage each attribute of each component, a table like the one shown in Figure 13 could be constructed. However, because not all attribute items (subgroups) are required for all components, capacity may be reserved for cells that are not actually used (for example, the material name for component ID: 5 in Figure 13). In other words, if an RDB were used to manage each attribute of each component, the data length (record length) of each component (each record) would be a fixed length adjusted to the maximum. However, in the construction management DB 15, which has a graph DB structure, for example, as shown in Figure 5, relationships are set for each component node only with nodes in related subgroups of the attribute group. This allows the amount of data required for each component to be kept to the minimum required variable length compared to an RDB.

[0194] (A-3-3) A graph DB is essentially a platform for computer modeling things that originally have a network-like structure in the real world, such as social network services, neural networks that make up artificial intelligence, and network equipment in IT infrastructure. On the other hand, things that have no network-like structure in the real world, such as construction property X, cannot be modeled on a graph DB. However, the inventors of the present application have discovered that by adopting the structures shown in Figures 3 to 11, construction management (e.g., progress) of construction property X can be adapted, and the above-mentioned unique effects ("A-3-1", "A-3-2", etc.) can be achieved.

[0195] In the construction management DB 15, subgroups are set up for attribute groups, and attribute nodes are arranged for each attribute value within each subgroup. By adopting this structure, the construction management DB 15 adapts each component (component node) of the construction property X, which is not originally a network structure, to the network model of the graph DB.

[0196] Furthermore, in the initial state (e.g., the state in FIG. 5 ), the construction management DB 15 has a data structure in which a relationship is established between each component node and an attribute node (layer node in the above example), a relationship is established between the attribute node (layer node in the above example) and a process node, and a relationship is established between the process node and an operation node. In other words, in the initial state, no direct relationship is established between each component node and an operation node, but an indirect association (relationship) is established between the operation node and each component node and the operation node for the operation related to that component node. The data processing server AP (server 10) then manages the operation status (unperformed or performed) for each component node depending on whether or not there is a direct relationship (DONE-type relationship) with the associated operation node. By forming this structure between each component node and an operation node in the construction management DB 15, construction management (progress management) for each component node is possible even with a graph DB structure.

[0197] (B) Other embodiments The present invention is not limited to the above-described embodiments, and may include modified embodiments such as those exemplified below.

[0198] (B-1) In the above embodiment, the construction object that is the object of construction management in the data processing system 1 (construction management DB 15) is described as a building, but the construction object is not limited to a building. For example, in the data processing system 1 (construction management DB 15), an object that has multiple parts as elements (e.g., an automobile, an airplane, etc.) may be applied as the object of construction management. Furthermore, in the data processing system 1 (construction management DB 15), the object of construction management is not limited to a tangible object, but may also be a computer program (software) that has multiple programs (modules) as elements.

[0199] (B-2) When the data processing server AP (server 10) narrows down nodes using multiple items, such as in processing related to the display narrowing settings on the construction management screen, it can perform more efficient narrowing down processing by prioritizing the items with fewer related nodes (items with fewer nodes with relationships set up).

[0200] For example, assume that "Layer: Exhaust" and "Floor: 2FL" have been entered for two objects B102 in the display filter settings on the construction management screen. Here, the number of component nodes connected to layer node D1 (Layer: Exhaust) is set to J1, and the number of component nodes connected by relationship to floor node H2 (Floor: 2FL) is set to J2, with J1 > J2. In this case, if the data processing server AP (server 10) first extracts the component nodes connected to floor node H2 (Floor: 2FL), and then further extracts the component nodes connected to layer node D1 (Layer: Exhaust) from the extracted component nodes, the number of component nodes to be accessed will be fewer than if the order were reversed. [Explanation of symbols]

[0201] 1...data processing system, 10...server, 11...graph DB middleware, 12...back-end application, 13...web service middleware, 14...front-end application, 15...construction management DB, 21...client terminal, 211...application, 212...touch panel display, 22...client terminal, 221...application, 222...touch panel display, 23...client terminal, 231...web browser, 232...display, 233...input device

Claims

1. A database holding means for holding a graph structured database; a data processing system including a data processing means for processing data in the database, The database includes: A plurality of element nodes indicating elements used when constructing a structure consisting of a plurality of elements; A plurality of process nodes indicating processes for constructing the construction object; a plurality of operation nodes indicating operations included in one or more of the processes; a plurality of attribute nodes indicating attributes related to the element node and the process node are set; An edge indicating a relationship between each of the process nodes and the operation nodes is set, An edge indicating a relationship between each of the process nodes and the attribute node is set, An edge indicating a relationship between each of the element nodes and the attribute node is set, When receiving an input from a client terminal indicating that a task of interest for an element of interest has been completed, the data processing means sets an edge indicating task completion between the element node corresponding to the element of interest and the task node corresponding to the task of interest. A data processing system comprising:

2. Each of the element nodes is indirectly connected to any of the process nodes by the edge via any of the attribute nodes, The data processing means recognizes the element node indirectly connected to the process node as a target in the process of the process node.

2. The data processing system of claim 1.

3. A data processing system as described in Claim 2, characterized in that a work order edge having a work order value indicating the order of work is set between the process node and the work node, and each of the work order edges set from the process node has a different work order value set.

4. A computer, a database holding means for holding a graph structured database; functioning as a data processing means for processing data in the database; The database includes: A plurality of element nodes indicating elements used when constructing a structure consisting of a plurality of elements; A plurality of process nodes indicating processes for constructing the construction object; a plurality of operation nodes indicating operations included in one or more of the processes; a plurality of attribute nodes indicating attributes related to the element node and the process node are set; An edge indicating a relationship between each of the process nodes and the operation nodes is set, An edge indicating a relationship between each of the process nodes and the attribute node is set, An edge indicating a relationship between each of the element nodes and the attribute node is set, When receiving an input from a client terminal indicating that a task of interest for an element of interest has been completed, the data processing means sets an edge indicating task completion between the element node corresponding to the element of interest and the task node corresponding to the task of interest. A data processing program characterized by:

5. A data processing method performed by a data processing device, the data processing device comprises a database holding means and a data processing means, the database holding means holds a graph-structured database; the data processing means processes the data in the database; The database includes: A plurality of element nodes indicating elements used when constructing a structure consisting of a plurality of elements; A plurality of process nodes indicating processes for constructing the construction object; a plurality of operation nodes indicating operations included in one or more of the processes; a plurality of attribute nodes indicating attributes related to the element node and the process node are set; An edge indicating a relationship between each of the process nodes and the operation nodes is set, An edge indicating a relationship between each of the process nodes and the attribute node is set, An edge indicating a relationship between each of the element nodes and the attribute node is set, When receiving an input from a client terminal indicating that a task of interest for an element of interest has been completed, the data processing means sets an edge indicating task completion between the element node corresponding to the element of interest and the task node corresponding to the task of interest. A data processing method comprising:

Images