JP7591366B2 - Management system and management program - Google Patents

Description

The present invention relates to a management system and a management program.

Technology for managing construction materials used at construction sites has been known in the past (see, for example, Patent Document 1).

JP 2007-323497 A

However, in the technology of Patent Document 1, the identification information indicated on the barcode attached to each piece of equipment was read, and the equipment was managed individually based on that identification information. Therefore, for example, even if multiple pieces of equipment were delivered to a construction site together, it was necessary to read and manage the barcodes individually, which could be time-consuming.

The present invention has been made in consideration of the above-mentioned facts, and aims to provide a management system and management program that makes it possible to easily manage multiple objects.

In order to solve the above-mentioned problems and achieve the object, the management system described in claim 1 is a management system for managing a plurality of objects, and includes a storage means in which group identification information for identifying a group including the plurality of objects is stored, a reception means for receiving object identification information for identifying at least one of the plurality of objects, and a management means for performing a management process for managing the plurality of objects included in the group to which at least one object identified by the object identification information received by the reception means belongs, based on the group identification information stored in the storage means, wherein when a user selects a first mode for collectively processing acceptance information indicating that the plurality of objects included in the group to which the at least one object identified by the object identification information received by the reception means belongs have been accepted by the construction site side , the management means performs a first storage process for collectively storing the acceptance information as the management process, and when the user selects a second mode for individually processing the acceptance information , the management means does not perform the first storage process, but performs a second storage process for individually storing the acceptance information as the management process.

The management system of claim 2 is the management system of claim 1 , wherein the storage means stores attribute information that identifies attributes of each of the plurality of objects, and the management means performs the management process of displaying attributes of the plurality of objects based on the attribute information stored in the storage means.

The management system described in claim 3 is the management system described in claim 1 or 2, in which the multiple objects are multiple components to be assembled at the construction site, and the groups are defined based on the state of the multiple components after assembly.

The management system of claim 4 is a management system of any one of claims 1 to 3 , in which each of the multiple objects is assigned a two-dimensional code indicating the object identification information that identifies each of the multiple objects, the management system further comprising a reading means for reading the two-dimensional code, and the reception means for receiving the object identification information indicated in the two-dimensional code read by the reading means.

The management system of claim 5 is the management system of claim 4, in which the multiple objects are processed at a designated processing facility other than the construction site and then transported to the construction site, the reading means reads the two-dimensional codes attached to the multiple objects transported to the construction site, and the management means performs the management process of storing the acceptance information in the storage means.

The management program described in claim 6 is a management program for managing a plurality of objects, and causes a computer to function as a reception means for receiving object identification information that identifies at least one of the plurality of objects, and a management means that performs a management process for managing the plurality of objects included in the group to which at least one object identified by the object identification information received by the reception means belongs, based on the group identification information stored in a storage means in which group identification information for identifying a group including the plurality of objects is stored, and when a user selects a first mode for collectively processing acceptance information indicating that the plurality of objects included in the group to which the at least one object identified by the object identification information received by the reception means belongs has been accepted by the construction site side, the management means performs a first storage process for collectively storing the acceptance information as the management process, and when the user selects a second mode for individually processing the acceptance information , the first storage process is not performed, and a second storage process for individually storing the acceptance information is performed as the management process .

According to the management system of claim 1 and the management program of claim 6 , by performing management processing for managing multiple objects included in a group to which at least one object identified by object identification information belongs, it is possible to manage multiple objects together, for example, thereby making it possible to easily manage multiple objects.

According to the management system of the second aspect, by performing a process of displaying the attributes of a plurality of objects, it becomes possible, for example, to allow the user to recognize the attributes of a plurality of objects.

According to the management system of claim 3 , the groups are defined based on the state of a plurality of components after assembly, thereby making it possible, for example, to smoothly carry out the process of assembling a plurality of components.

According to the management system described in claim 4 , by accepting the object identification information indicated in the read two-dimensional code, it is possible to eliminate the need for a user to input the object identification information using a keyboard, etc., thereby making it possible to easily manage multiple objects.

According to the management system described in claim 5 , for example , it is possible to centrally manage the receipt of multiple objects processed at a processing facility at a construction site, making it possible to easily manage multiple objects.

FIG. 1 is a diagram illustrating a situation in which a management system according to an embodiment of the present invention is applied; FIG. 2 is a block diagram showing a functional concept of the management system. FIG. 11 is a diagram illustrating an example of three-dimensional building-related information. 1 is a display example of a three-dimensional model. FIG. 13 is a diagram illustrating an example of piping acceptance related information. FIG. FIG. 13 is a diagram illustrating an example of a piping label. FIG. 13 is a diagram showing piping with piping labels attached. 13 is a flowchart of a group acceptance information storage process. 13 is a display example of a group acceptance screen. 13 is a display example of a details screen. 13 is a flowchart of an individual acceptance information storage process. 13 is an example of an individual acceptance screen.

The following describes in detail an embodiment of a management system and a management program according to the present invention with reference to the attached drawings. First, [I] the basic concept of the embodiment is explained, then [II] the specific content of the embodiment is explained, and finally, [III] modified examples of the embodiment are explained. However, the present invention is not limited to the embodiment.

[I] Basic Concept of the Embodiment First, the 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 a plurality of objects, and includes, for example, a storage unit, a receiving unit, and a management unit, and optionally includes a reading unit.

"Multiple objects" refers to objects that are managed by the management system, and is a concept that includes, for example, multiple components assembled at a construction site, as well as objects that are processed at a designated processing facility other than the construction site and then transported (i.e., delivered) to the construction site. "Multiple objects" is a concept that includes, for example, building materials (i.e., components) or any other objects, and examples include pipes, columns, beams, reinforcing bars, and steel frames used in construction.

"Storage means" refers to a means in which group-identifying information is stored, and is a concept that includes, for example, a means in which other information is optionally further stored, and as one example, a concept that includes a means in which attribute information, etc. is further stored. "Attribute information" refers to information that identifies the attributes of each of multiple objects.

"Group identification information" is information for identifying a group that includes multiple objects; that is, information for identifying a group to which multiple objects belong (a group of any unit, such as a bundle, a group, a box, etc.). Here, "group" is a concept that includes, for example, a group to which a single type of object belongs, and a group to which multiple types of objects belong. Note that the number of objects that belong to this group is arbitrary, and for example, it may be interpreted as a group containing only one object, or multiple objects. In addition, the criteria for defining this group are arbitrary, but for example, the group may be defined based on the state after assembly of multiple components.

"Receiving means" refers to a means for receiving object identification information that identifies at least one of a plurality of objects, and is a concept that includes, for example, a means for receiving object identification information indicated in a two-dimensional code read by a reading means.

A "two-dimensional code" is a code that can indicate any information, specifically a two-dimensional barcode, a concept that includes, for example, QR Code (registered trademark). Note that in this embodiment, an example will be described in which a two-dimensional code indicating object-specific information that identifies each of a number of objects is affixed to each of the multiple objects.

The "management means" is a means for performing a management process for managing multiple objects included in a group to which at least one object identified by the object identification information received by the reception means belongs, based on the group identification information stored in the storage means. The "management means" is a concept that includes, for example, a means for performing a process for storing information about multiple objects collectively as a management process, a means for performing a process for displaying attributes of multiple objects based on attribute information stored in the storage means, and a means for performing a process for storing acceptance information in the storage means indicating that multiple objects included in a group to which at least one object identified by the object identification information received by the reception means belongs have been accepted by the construction site.

"Reading means" refers to a means for reading a two-dimensional code, and is a concept that includes, for example, a means for reading two-dimensional codes attached to multiple objects transported to a construction site.

In the embodiment described below, the case where the "multiple objects" are pipes used as building materials at a construction site will be described.

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

(composition)
First, a management system according to the present embodiment will be described. Fig. 1 is a diagram illustrating an example of a situation in which the management system according to the present embodiment is applied, and Fig. 2 is a block diagram illustrating the functional concept of the management system.

In this embodiment, an example will be described in which the pipe 900 is processed (more specifically, a relatively long pipe is cut, etc.) at the pipe processing center in FIG. 1, the processed pipe 900 is shipped from the pipe processing center to a construction site, and the pipe 900 is received at the construction site.

A "piping processing center" is, for example, a processing facility that processes pipes 900 to be used as building materials at construction sites. A "construction site" is, for example, a site where a building to be constructed is constructed, for example, a site where a building is constructed using at least pipes 900 processed at a piping processing center as building materials.

The management system 100 in FIG. 2 is, for example, a system for managing the receipt of the piping 900 in FIG. 1 at the construction site, and includes, as an example, a terminal device 1 and a server device 2. Note that, for convenience of explanation, only one terminal device 1 is shown in FIG. 2, but the number of terminal devices 1 is arbitrary, and multiple terminal devices 1 may be present.

(Configuration - Terminal Device)
The terminal device 1 is a mobile terminal, for example a smartphone or tablet terminal carried by a user who is a worker at the construction site of Figure 1, and as an example, as shown in Figure 2, it is equipped with a communication unit 11, a touchpad 12, a display 13, a camera 14, a recording unit 15, and a control unit 16.

(Configuration - Terminal Device - Communication Unit)
2 is a communication unit that communicates with other devices (such as the server device 2). The specific configuration of the communication unit 11 is arbitrary, but it can be configured to include, for example, a known wireless communication circuit.

(Configuration - Terminal Device - Touch Pad)
2 is an operation means for receiving various operation inputs from a user by being pressed by the user's finger, etc. The specific configuration of this touchpad 12 is arbitrary, but for example, a known one equipped with an operation position detection means using a resistive film method, a capacitive method, or the like can be used.

(Configuration - Terminal Equipment - Display)
The display 13 in Fig. 2 is an image display means for displaying various images under the control of the control unit 16. The specific configuration of the display 13 is arbitrary, and for example, a known flat panel display such as a liquid crystal display or an organic EL display can be used. The touch pad 12 and the display 13 may be integrally formed as a touch panel.

(Configuration - Terminal Device - Camera)
The camera 14 in Fig. 2 is an imaging unit that captures an image and obtains an image. The specific configuration of the camera 14 is arbitrary, and is configured using, for example, a known imaging element such as a CMOS image sensor or a CCD image sensor, and known optical components such as a fisheye lens or a prism.

(Configuration - Terminal Device - Recording Unit)
2 is a recording means for recording programs and various data necessary for the operation of the terminal device 1, and is configured using, for example, a flash memory (not shown) as an external recording device. However, instead of or together with the flash memory, any other recording medium including a magnetic recording medium such as a hard disk or a magnetic disk, or an optical recording medium such as a DVD or a Blu-ray disk can be used (the same applies to the recording units of other devices).

(Configuration - Terminal Device - Control Unit)
2 is a control means for controlling the terminal device 1, and is specifically a computer including a CPU, various programs interpreted and executed on the CPU (including basic control programs such as an OS, and application programs that are started on the OS and realize specific functions), and an internal memory such as a RAM for storing the programs and various data. In particular, the program according to the embodiment is installed in the terminal device 1 via an arbitrary recording medium or a network, thereby substantially configuring each part of the control unit 16 (the same applies to the control units of other devices).

The control unit 16, for example, conceptually includes a reading unit 161. The reading unit 161 is a reading means for reading a two-dimensional code. The processing of each part of the control unit 16 will be described later.

(Configuration - Server Device)
The server device 2 is configured, for example, as a server computer installed at any location such as a data center or a so-called cloud computer realized by multiple computers, and is equipped, for example, with a communication unit 21, a recording unit 22, and a control unit 23.

(Configuration - Server Device - Communication Unit)
2 is a communication means for communicating with other devices (such as the terminal device 1 or a terminal (not shown) of a person in charge at the piping processing center described later). The specific configuration of the communication unit 21 is arbitrary, but it can be configured in the same way as the communication unit 11 of the terminal device 1, for example.

(Configuration - Server Device - Recording Unit)
2 is a storage unit that stores programs and various data necessary for the operation of the server device 2. The recording unit 22 also includes, for example, a three-dimensional building-related information database 221 (hereinafter, the database is referred to as a "DB") and a piping reception-related information DB 222.

(Configuration - Server device - Recording unit - 3D building related information DB)
The three-dimensional building-related information DB 221 in FIG. 2 is a drawing information storage means for storing three-dimensional building-related information. FIG. 3 is a diagram illustrating three-dimensional building-related information, and FIG. 4 is a display example of a three-dimensional model. "Three-dimensional building-related information" is information about a three-dimensional model showing the entire building to be constructed, and is a concept including information to which so-called BIM (Building Information Modeling) technology is applied, for example. As shown in FIG. 3, the "three-dimensional building-related information" is information in which, for example, information corresponding to the item "component ID", information corresponding to the item "model information", information corresponding to the item "type information", and information corresponding to the item "position direction information" are mutually associated.

The information corresponding to the item "Component ID" is component identification information (hereinafter, "identification information" is also referred to as "ID") that uniquely identifies the component piping 900, and is information corresponding to a so-called global ID (GUID) (such as "ID0001" in FIG. 3). The information corresponding to the item "Model Information" is model information that identifies a three-dimensional model of each component. This model information is arbitrary, but for example, as illustrated in FIG. 4, which shows a three-dimensional model of a part of a building as viewed from above, it is information that identifies piping models Gm001 to Gm004 that indicate the piping of the building to be constructed, designed by the designer, and beam model Gm0005 that indicates the beam, and the like. In FIG. 3, examples include "M0001" that identifies piping model Gm001 in FIG. 4, "M0002" that identifies piping model Gm002, "M0003" that identifies piping model Gm003, and "M0004" that identifies piping model Gm004.

The information corresponding to the item "Type Information" is type information that identifies the type (kind) of the component indicated by the three-dimensional model identified by the model information (e.g., "Pipe" in FIG. 3, which identifies it as pipe). The information corresponding to the item "Position/Direction Information" is position/direction information that identifies the position and direction of the three-dimensional model of each component identified by the model information in the three-dimensional model of the entire building. This position/direction information is arbitrary, but it may be, for example, to identify the position and direction based on a three-dimensional coordinate system based on the X-axis, Y-axis, and Z-axis with a specified position of the three-dimensional model representing the entire building as the origin, and in FIG. 3, it is written as "Dp0001" for convenience.

And, for example, in the top row of the three-dimensional building-related information in FIG. 3 (i.e., the information of the combination of "ID0001", "M0001", "Piping", and "Dp0001"), it is shown that the type of the three-dimensional model of the piping 900 (piping model Gm001 in FIG. 4) specified by the "model information" = "M0001" identified by the "component ID" = "ID0001" is "piping", and that the position and direction of the piping model Gm001 in FIG. 4 in the three-dimensional model showing the entire building is "Dp0001".

The specific method for storing such three-dimensional building-related information is arbitrary, but for example, a designer may generate each piece of information using a three-dimensional CAD application (not shown) and then input the generated information to the server device 2 using any method (for example, a method of sending information to the server device 2 and inputting it, or a method of inputting it using a recording medium such as a memory stick), and the control unit 23 may store it based on the input information. The three-dimensional building-related information may also be stored using any method other than the method described here.

(Configuration - Server device - Recording section - Pipe receiving related information DB)
The piping acceptance related information DB 222 in Fig. 2 is a drawing information storage means for storing piping acceptance related information. Fig. 5 is a diagram showing an example of the piping acceptance related information, and Fig. 6 is a diagram showing an example of a production drawing.

A "production drawing" is a drawing that is referred to when processing the pipe 900 at the pipe processing center in FIG. 1. For example, a worker at the pipe processing center refers to a production drawing that is printed out on paper or displayed on an arbitrary display device, processes the pipe 900 as shown in the production drawing, and then ships the pipe 900. An example of work related to the pipe 900 at the pipe processing center will be described later. As shown in FIG. 6, a "production drawing" has, for example, a system name display column 31, a drawing display column 32, and an information display column 33.

The system name display field 31 is a field that displays the name of a system of multiple pipes. In FIG. 6, for example, "K-1" is shown as the name of the system. A "system" is a group of pipes 900. This group of "systems" may be determined arbitrarily, but in this embodiment, the group is determined based on the state after assembly of multiple pipes 900. For example, when constructing a building to be constructed at a construction site, a group to which multiple pipes 900 that are interconnected belong will be described. Note that this "system" may be determined, for example, taking into consideration the construction procedure of the pipes 900 at the construction site, or other factors.

The drawing display field 32 is a field that displays the assembled state of multiple pipes 900 belonging to the system whose name is displayed in the system name display field 31. In FIG. 3, for example, the assembled state of three pipes 900 indicated by arrows with processing numbers "1" to "3" is displayed. Note that the "processing number" is, for example, information for identifying the pipes 900 to be processed.

The information display field 33 is a field that displays detailed information about multiple pipes 900 belonging to the system whose name is displayed in the system name display field 31. In FIG. 3, for example, the name and size of each pipe 900 corresponding to each processing number viewed with an arrow in the drawing display field 32 are displayed. In detail, the information at the top of the information display field 33 (i.e., "1 Ditch drain pipe XX mm") indicates that the name of the pipe 900 viewed with an arrow in the "processing number" = "1" in the drawing display field 32 among the pipes 900 belonging to the "K-1" system is "ditch drain pipe" and that the size of the pipe 900 is "XX mm" (note that "XX" is a description for convenience and is actually a numerical value). Note that the specific method of generating and using such a production drawing will be described later.

Returning to FIG. 2, the "piping acceptance related information" stored in the piping acceptance related information DB 222 is information that includes information related to the acceptance at the construction site of the piping 900 that was processed and shipped at the piping processing center in FIG. 1. As shown in FIG. 5, the "piping acceptance related information" is information that, for example, correlates information corresponding to the item "component ID," information corresponding to the item "name information," information corresponding to the item "item material information," information corresponding to the item "size information," information corresponding to the item "system information," information corresponding to the item "processing number information," information corresponding to the item "acceptance status information," information corresponding to the item "acceptance date and time information," and information corresponding to the item "acceptance staff information."

The information corresponding to the item "component ID" is the same as the information of the same name in FIG. 3 (such as "ID0001" in FIG. 5). This component ID is information that uniquely identifies the component, piping 900. Therefore, in this embodiment, when it is considered that the piping 900 is processed based on a three-dimensional model as described below, the component ID can be interpreted as uniquely identifying each processed piping 900 (i.e., identifying each piping 900). In other words, the "component ID" may be interpreted as corresponding to "object identification information".

The information corresponding to the item "name information" is name information indicating the name of the processed pipe 900 (e.g., "ditch drain pipe" in FIG. 5). The information corresponding to the item "item material information" is attribute information specifying the attributes of the processed pipe 900, specifically, item material information indicating the characteristics of the item or material (e.g., "fireproof two-layer pipe" in FIG. 5). The information corresponding to the item "size information" is attribute information specifying the attributes of the processed pipe 900, specifically, size information indicating the size (e.g., length "xx mm" in FIG. 5, which is a description for convenience). The information corresponding to the item "system information" is the above-mentioned group identification information, and is system information indicating the system to which the processed pipe 900 belongs (e.g., "K-1" which is the system name in FIG. 5). The information corresponding to the item "processing number information" is processing number information indicating the processing number assigned to the processed pipe 900 in the production drawing (FIG. 6).

The information corresponding to the item "Acceptance status information" is acceptance status information indicating the acceptance status at the construction site of the pipe 900 that has been processed and shipped from the pipe processing center (Figure 1). Any information can be used as this acceptance status information, but for example, we will explain the case where "Accepted" indicating that it has been accepted and "Not yet accepted" indicating that it has not yet been accepted are used. Note that "Acceptance" here may be interpreted as equivalent to "acceptance information". Also, "accepting the pipe 900 at the construction site" may be interpreted as a concept corresponding to, for example, the person in charge of acceptance work at the construction site checking the pipe 900 that has been shipped from the pipe processing center, transported to the construction site, and delivered to the construction site.

The information corresponding to the item "Acceptance date and time information" is acceptance date and time information that specifies the date and time when the processed piping 900 was accepted at the construction site (e.g., "07051100" in FIG. 5, which indicates 11:00 on July 5th). The information corresponding to the item "Acceptance staff information" is acceptance staff information that indicates the acceptance staff who accepted the processed piping 900 at the construction site (e.g., "AA AA" which is the staff's name in FIG. 5). Note that "AA AA" is written for convenience.

And the information at the top of the piping acceptance-related information in Figure 5 (i.e., "ID0001", "ditch drainage pipe", "fireproof two-layer pipe", "xxmm", "K-1", "1", "acceptance", "07051100", and "AA In the information for the combination of "07051100" and "07051100", for example, the name of the pipe 900 identified by "Component ID" = "ID0001" is indicated as "ditch drain pipe", the item or material of the pipe 900 is indicated as "fireproof double-layer pipe", the size of the pipe 900 is indicated as "xx mm", the system to which the pipe 900 belongs is indicated as "K-1", the processing number of the pipe 900 is indicated as "1", and (by "Acceptance status information" = "Accepted") it is indicated that the pipe 900 has been accepted by the construction site, the date and time when the pipe 900 was accepted is indicated as "07051100, 11:00 am" and the person who accepted the pipe 900 is indicated as "AA AA".

The specific method of storing such piping acceptance related information is arbitrary, but for example, the component ID, name information, item material information, size information, system information, and processing number information are basically stored by performing work on the piping 900 at the piping processing center described below, and the acceptance status information, acceptance date and time information, and acceptance person information are basically stored by executing the group acceptance information storage process or the individual acceptance information storage process described below. The component ID, name information, item material information, size information, system information, and processing number information in the piping acceptance related information in FIG. 5 can also be interpreted as information indicating the piping 900 to be accepted at the construction site, and this information is referred to as "acceptance candidate piping information." The "acceptance candidate piping information" may be stored by any method other than the above-mentioned method.

(Configuration - Server Device - Control Unit)
2 is a control means for controlling the server device 2, and functionally includes, for example, a reception unit 231 and a management unit 232. The reception unit 231 is a reception means for receiving a member ID that identifies at least one of the multiple processed pipes 900. The management unit 232 is a management means for performing management processing for managing multiple pipes 900 included in a system that is a group to which at least one pipe 900 identified by the member ID received by the reception unit 231 belongs, based on system information stored in the pipe reception related information DB 222. Processing performed by each unit of the control unit 23 will be described later.

(Piping work at the piping processing center)
Next, a description will be given of the work related to piping carried out at the piping processing center side of Fig. 1. Fig. 7 is a diagram showing an example of a piping label, and Fig. 8 is a diagram showing the piping with the piping label attached.

===Pipe Label===
A "piping label" 4 is a label that is affixed to a piping 900 that has been processed (cut) according to the production drawing in FIG. 6, and more specifically, is a label that displays information indicating the processed piping 900, and as shown in FIG. 7, for example, each piping label 4 includes a two-dimensional barcode 401 and an information display field 402.

The two-dimensional barcode 401 is the above-mentioned two-dimensional code, for example, a QR code (registered trademark). The information indicated by the two-dimensional barcode 401 is arbitrary, but for example, the access destination information and the above-mentioned component ID (i.e., the component ID that uniquely identifies the processed piping 900 to which the piping label 4 is attached) can be read from the two-dimensional barcode 401. The "access destination information" is, for example, information indicating the server device 2 that is accessed and communicated by the device that reads the information of the two-dimensional barcode 401 (specifically, the terminal device 1 in FIG. 2). Any information can be used as this access destination information, and for example, information corresponding to a URL (Uniform Resource Locator) or any other arbitrary information may be used. In the two-dimensional barcodes 401 of the three pipe labels 4 in FIG. 7, information for accessing the server device 2 is shown as common access information, and the two-dimensional barcode 401 of the pipe label 41 shows "component ID" = "ID0001", the two-dimensional barcode 401 of the pipe label 42 shows "component ID" = "ID0002", and the two-dimensional barcode 401 of the pipe label 43 shows "component ID" = "ID0003". The "component ID" = "ID0001" to "ID0003" here correspond to the information described in FIG. 3 and FIG. 5.

The information display field 402 is a field in which information indicating the processed pipe 900 to which the pipe label 4 is affixed is displayed. The fields displayed in this information display field 402 are arbitrary, but for example, a case in which information similar to the information displayed in the system name display field 31 and information display field 33 of the production drawing in FIG. 6 is displayed will be described as an example. As another example, for example, the name of the contractor who processed the pipe 900 may be displayed, or some of the information (for example, information similar to the information displayed in the system name display field 31) may be omitted.

===Piping work carried out at the piping processing center===
The piping-related work performed at the piping processing center includes, for example, piping determination work, production drawing creation work, piping label creation work, piping processing work, piping shipping work, and shipping report work. Note that each of these works is basically performed by a person in charge at the piping processing center.

=Piping decision work=
The "piping determination work" is, for example, a work of determining a specific configuration of the piping 900 to be processed. For example, a three-dimensional model showing a building to be constructed, designed by a designer, is stored on the server device 2 side as the three-dimensional building-related information of FIG. 3, and the three-dimensional building-related information is used to determine the specific configuration. First, a person in charge at the piping processing center performs a predetermined operation on his/her terminal (computer) to obtain the three-dimensional building-related information of FIG. 3 from the server device 2, and displays the three-dimensional model of FIG. 4 corresponding to the obtained three-dimensional building-related information on the terminal. Next, the person in charge performs a predetermined operation on the terminal to select a plurality of piping models from the three-dimensional model of FIG. 4 displayed on the terminal, group them into a system, determine and input system information of the system (i.e., the name of the system), and also determine and input name information, item material information, size information, and processing number information of each piping 900 belonging to the grouped system.

Here, for example, a person in charge at the piping processing center performs a predetermined operation on his/her own terminal to obtain the three-dimensional building-related information of Fig. 3 from the server device 2, display the three-dimensional model of Fig. 4 corresponding to the obtained three-dimensional building-related information on the terminal, select piping models Gm001-Gm003 of Fig. 4 and group them into systems, and determine and input the "system information" of the system = "K-1". Next, he/she clicks to select the piping model Gm001 of Fig. 4 grouped into "K-1", and determines and inputs the "name information" = "ditch drain pipe", "item material information" = "fireproof two-layer pipe", "size information" = "xx mm", and "processing number information" = "1" for the piping 900 indicated by the piping model Gm001 selected by clicking. Also, click and select the piping model Gm002 in FIG. 4 grouped under "K-1," and similarly determine and input the "ditch drain pipe," "fireproof two-layer pipe," "00 mm," and "2" for the piping 900 represented by the piping model Gm002. Also, click and select the piping model Gm003 in FIG. 4 grouped under "K-1," and similarly determine and input the "ditch drain pipe," "fireproof two-layer pipe," "00 mm," and "3" for the piping 900 represented by the piping model Gm003.

=Creating production drawings=
The "work of generating a production drawing" is, for example, a work of generating a production drawing. For example, when a person in charge at the piping processing center performs a predetermined operation for generating a production drawing on his/her own terminal, the terminal generates and outputs a production drawing based on the information selected or input in the above-mentioned "piping determination work". Specifically, the terminal generates and outputs a production drawing in which the "system information" input in the "piping determination work" is displayed in the system name display field 31 of FIG. 6, the plan view of the piping model selected and grouped in the system indicated by the input "system information" and the information corresponding to the above-mentioned input "processing number information" are displayed in the drawing display field 32, and the above-mentioned input "processing number information", "name information", and "size information" are displayed in the information display field 33.

For example, when a person in charge at the piping processing center performs a predetermined operation to generate a production drawing on his/her own terminal, the terminal generates a production drawing in which the "system information" = "K-1" input in the "piping determination work" is displayed in the system name display field 31 of FIG. 6, and the plan view of the piping models Gm001 to Gm003 (FIG. 4) selected and grouped into the system indicated by the input "system information" = "K-1" and the information corresponding to the input "processing number information" = "1" to "3" are displayed in the drawing display field 32, and the input "processing number information" = "1", "name information" = "ditch drain pipe", and "size information" = "xx mm", etc. are displayed in the information display field 33. The generated production drawing is then printed out on paper, or displayed on a display and output.

The specific method for displaying the plan views of the piping models Gm001 to Gm003 in the drawing display area 32 can be arbitrary, but for example, they may be displayed based on the model information and position and direction information in the three-dimensional building-related information in Figure 3 obtained in the "piping determination work".

=Pipe label generation work=
The "piping label generation work" is, for example, a work of generating a piping label 4. For example, when a person in charge at the piping processing center performs a predetermined operation on his/her own terminal to generate a piping label 4, the terminal generates and outputs the piping label 4 based on the information selected or input in the above-mentioned "piping determination work". Specifically, the terminal refers to the three-dimensional building-related information acquired from the server device 2 in the "piping determination work", specifies a member ID that identifies one pipe 900 selected in the "piping determination work" and grouped into a system, and generates and outputs a piping label 4 including a two-dimensional barcode 401 indicating the specified member ID and access destination information for accessing the server device 2, and displaying in the information display field 402 the "system information", "processing number information", "name information", and "size information" input in the "piping determination work". Then, the terminal performs the above-mentioned process for each piping model selected in the "piping determination work" and grouped into a system.

Here, for example, when a person in charge at the piping processing center performs a predetermined operation on his/her own terminal to generate a piping label 4, the terminal refers to the three-dimensional building-related information acquired from the server device 2 in the "piping determination work", and identifies, for example, the piping 91 corresponding to the "piping model Gm001" (Figure 4) as one piping 900 selected in the "piping determination work" and grouped into the system "K-1", and obtains "member ID" = "ID0001" (i.e., "M0001" that identifies the piping model Gm001 in the three-dimensional building-related information in Figure 3). 7, which includes a two-dimensional barcode 401 indicating the identified "component ID" = "ID0001" and access destination information for accessing the server device 2, and in which the "system information" = "K-1", "processing number information" = "1", "name information" = "ditch drain pipe", and "size information" = "xx mm" input in the "piping determination work" are displayed in the information display field 402, and the generated piping label 41 is printed and output as an attachable sticker. Then, similar processing is performed for the piping 92, 93 information corresponding to, for example, "piping model Gm002" and "piping model Gm003" as the piping 900 selected in the "piping determination work" and grouped into the system "K-1", to generate the piping labels 42, 43 in FIG. 7, and the generated piping labels 42, 43 are printed and output as attachable stickers.

=Pipe processing work=
The "piping processing work" is, for example, a work of processing the pipes 900. For example, a person in charge at the piping processing center refers to the production drawing generated in the "production drawing generation work" and processes the relatively long sized pipes 900 by cutting them to lengths corresponding to the sizes of the respective pipes 900 shown in the production drawing. Note that since this "piping processing work" is performed based on the production drawing, the pipes 900 are processed in system units, which are groups.

Here, for example, a person in charge at the piping processing center refers to the production drawing of FIG. 6 generated in the "production drawing generation work" and cuts the relatively long piping 900 to the length corresponding to the size shown in the production drawing, thereby processing it into three pipes 900 according to the production drawing, resulting in pipes 91 to 93 in FIG. 8.

=Pipe shipping work=
The "piping shipping work" is, for example, work to ship the pipes 900 processed in the "piping processing work." For example, a person in charge at the pipe processing center attaches the pipe labels 4 generated in the "piping label generation work" (the pipe labels 4 corresponding to each processed pipe 900) to each piece of pipe 900 processed in the "piping processing work," and then ships the pipes 900 processed in the "piping processing work" together (as an example, as a bundle of pipes 900 grouped by system unit).

Here, for example, a person in charge at the piping processing center attaches piping labels 41-43 generated in the "piping label generation work" to the piping 91-93 in Figure 8 that was processed in the "piping processing work", and then bundles the piping 91-93 processed in the "piping processing work" (as an example, a bundle of piping 91-93 grouped by system unit) and ships them out.

=Shipping report work=
The "shipment report work" is, for example, a work of reporting the shipped pipes 900 to the server device 2. For example, when a person in charge at the pipe processing center performs a predetermined process for making a shipment report on his/her own terminal, the terminal identifies one component ID (i.e., the component ID shown in the two-dimensional barcode 401 of the pipe label 4) in the same manner as described in the "piping label generation work", and transmits the identified component ID, the name information, item material information, size information, system information, and processing number information input in the "piping determination work" to the server device 2 in association with each other. Then, the terminal performs the above-mentioned process for each pipe 900 selected in the "piping determination work" and grouped into a system (i.e., all pipes 900 shipped in the "piping shipping work"). Meanwhile, the control unit 23 of the server device 2 receives each piece of information transmitted from the terminal, and stores the "reception candidate pipe information" in the pipe reception related information in FIG. 5 based on each piece of information received. In this case, "not yet" is stored as the initial value of the acceptance status information associated with the stored "acceptance candidate piping information" in the piping acceptance related information in FIG.

For example, when a person in charge at the piping processing center performs a predetermined process to submit a shipping report to his/her own terminal, the terminal identifies, for example, "ID0001" as one component ID (i.e., the component ID shown in the two-dimensional barcode 401 of the piping label 4) in the same manner as described in the "piping label generation work", and then transmits to the server device 2 the identified "component ID" = "ID0001", "name information" = "ditch drain pipe", "item material information" = "fireproof two-layer pipe", "size information" = "xx mm", "system information" = "K-1", and "processing number information" = "1" that were input in the "piping determination work" in a mutually associated manner. Then, the terminal performs the same process for "component ID" = "ID0002" and "ID0003".

Meanwhile, the control unit 23 of the server device 2 receives each piece of information sent from the terminal, and stores the "candidate piping information for acceptance" in the first to third rows of the piping acceptance related information in Figure 5 (i.e., component ID, name information, item material information, size information, system information, and processing number information) based on each piece of received information. Note that in this case, although "accepted" is shown as an example of the acceptance status information associated with these in Figure 5, "not yet" will be stored at this point. Furthermore, no information will be stored at this point for the acceptance date and time information and acceptance staff information associated with these.

In this way, as shown in FIG. 8, information corresponding to the information displayed on the pipe label 41 affixed to the processed and shipped pipes 91-93 is stored as "candidate pipe information for acceptance" in the pipe acceptance related information in FIG. 5.

=Variations=
The content of the "piping-related work at the piping processing center" described here may be changed as desired. For example, at least one of the pieces of information input by the person in charge at the piping processing center in the "piping decision work" (i.e., name information, item material information, size information, system information, or processing number information) may be determined, input, and stored by the designer.

(process)
Next, a description will be given of processes executed by the management system 100 according to the present embodiment. Specifically, a group acceptance information storage process and an individual acceptance information storage process will be described.

(Processing - Group Receipt Information Storage Processing)
First, the group acceptance information storage process will be described. The "group acceptance information storage process" is, in outline, a process performed by the server device 2, and is a process for storing the acceptance information in a lump by system unit. FIG. 9 is a flowchart of the group acceptance information storage process (in the following description of each process, steps are abbreviated as "S"). The timing of executing this group acceptance information storage process is arbitrary, but for example, when a user on the construction site side in FIG. 1 inputs name information indicating his/her name via the touch pad 12 and performs a predetermined operation to select a lump input mode for inputting the acceptance information in a lump by system unit, the terminal device 1 transmits the input name information and lump input mode information (information indicating that input is performed in the lump input mode) to the server device 2, and the server device 2 is started when it receives the name information and lump input mode information, and the group acceptance information storage process is started. The following description will begin with the start of the group acceptance information storage process.

Here, we will explain an example in which the pipes 91 to 93 shown in Figure 8 are delivered together to the construction site in Figure 1, and the user at the construction site, "AA AA," receives these pipes 91 to 93.

===SA1===
In SA1 of Fig. 9, the reception unit 231 of the server device 2 acquires a member ID. Specifically, although this is optional, for example, when a user at the construction site performs a predetermined operation via the touch pad 12, the terminal device 1 captures an image of the two-dimensional barcode 401 of the piping label 4 attached to the piping 900 of Fig. 8 delivered to the construction site with the camera 14, and the reading unit of the terminal device 1 reads the access destination information and the above-mentioned member ID indicated in the captured two-dimensional barcode 401, and transmits the above-mentioned read member ID to the server device 2 indicated by the read access destination information. Meanwhile, the reception unit 231 of the server device 2 receives the member ID transmitted from the terminal device 1 (i.e., accepts the member ID) and acquires it.

Here, for example, a user at the construction site performs a predetermined operation via the touchpad 12, causing the terminal device 1 to capture an image of the two-dimensional barcode 401 on the piping label 41 affixed to the piping 91 in FIG. 8 that has been delivered to the construction site with the camera 14, and the reading unit of the terminal device 1 reads the access destination information indicated in the captured two-dimensional barcode 401 and the aforementioned "component ID" = "ID0001", and transmits the aforementioned read "component ID" = "ID0001" to the server device 2 indicated by the read access destination information. Meanwhile, the reception unit 231 of the server device 2 receives and acquires the "component ID" = "ID0001" transmitted from the terminal device 1.

===SA2===
At SA2 in FIG. 9, the management unit 232 of the server device 2 displays a group acceptance screen, and then optionally displays a details screen.

= Group Acceptance Screen =
Fig. 10 is a display example of a group acceptance screen. The "group acceptance screen" is a screen for collectively storing acceptance information by system unit, and includes, for example, a system name display field 51 and an information display field 52 as shown in Fig. 10. The "system name display field" 51 is a field for displaying the name of the system for which acceptance information is to be stored, and specifically, a field for displaying the name of the system to which the piping 900 that is to be accepted at the construction site (i.e., for example, delivery confirmation is performed) belongs. The "information display field" 52 is a field for displaying information indicating the piping 900 that belongs to the system displayed in the system name display field 51.

=Details screen=
Fig. 11 is a display example of a details screen. The "details screen" is a screen on which detailed information on the pipes 900 is displayed, and includes an information display field 61, as shown in Fig. 11, for example. The "information display field" 61 is a field on which detailed information on one pipe 900 is displayed.

= Processing =
<Required processing in SA2>
The specific process of SA2 is arbitrary, but for example, by referring to the piping acceptance related information in Fig. 5, first, system information associated with the same component ID as the component ID acquired in SA1 is acquired, then a component ID associated with the same system information as the acquired system information is identified, name information and size information associated with the identified component ID is acquired, next, the acquired system information is displayed in the system name display field 51 in Fig. 10, and screen information for displaying a group acceptance screen in which the acquired name information and size information are displayed in the information display field 52 in Fig. 10 is generated, and the generated screen information is transmitted to the terminal device 1. Meanwhile, the terminal device 1 receives the screen information, and displays the group acceptance screen on the display 13 based on the received screen information.

Here, for example, by referring to the piping acceptance-related information in FIG. 5, first, the "system information" = "K-1" associated with the same system information as the "component ID" = "ID0001" acquired in SA1 is acquired, then the "component IDs" = "ID0001", "ID0002", and "ID0003" associated with the same system information as the acquired "system information" = "K-1" are identified, and "trench drain pipe" and "〇〇 mm" are acquired (for all component IDs) as the name information and size information associated with the identified "component IDs" = "ID0001", "ID0002", and "ID0003". Next, the aforementioned acquired "system information" = "K-1" is displayed in the system name display column 51 in FIG. 10, and the aforementioned acquired name information and size information) "trench drain pipe" and "〇〇 mm" are displayed in the information display column 52. Screen information for displaying the group acceptance screen of FIG. 10 is generated and transmitted to the terminal device 1. Meanwhile, the terminal device 1 receives the screen information and displays the group acceptance screen of FIG. 10 on the display 13 based on the received screen information.

<Optional processing in SA2>
When a user on the construction site side performs an operation of long pressing information displayed in the information display field 52 as a predetermined operation for displaying a detailed screen via the touch pad 12 on the group acceptance screen, the terminal device 1 transmits the component ID of the piping 900 corresponding to the long pressed information to the server device 2. On the other hand, when the management unit 232 of the server device 2 receives the component ID, it refers to the piping acceptance related information in Fig. 5, acquires the name information, item material information, size information, system information, and processing number information associated with the same component ID as the component ID, generates screen information for displaying a detailed screen in which each acquired information and the above-mentioned component ID are displayed in the information display field 61 in Fig. 11, and transmits the generated screen information to the terminal device 1. On the other hand, the terminal device 1 receives the screen information, and displays the detailed screen on the display 13 based on the received screen information.

Here, for example, when a user at the construction site performs an operation of long pressing "Gutter drain pipe XX mm" at the top displayed in the information display field 52 on the group acceptance screen of FIG. 10 via the touch pad 12, the terminal device 1 transmits the "component ID" = "ID0001" of the pipe 91 corresponding to the long pressed "Gutter drain pipe XX mm" to the server device 2. Meanwhile, the management unit 232 of the server device 2 receives the "component ID" = "ID0001", refers to the pipe acceptance related information of FIG. 5, acquires "Gutter drain pipe", "Fireproof double layer pipe", "XX mm", "K-1", and "1" associated with the same component ID as the "component ID" = "ID0001", generates screen information for displaying the detailed screen of FIG. 11 in which the acquired information and "component ID" = "ID0001" are displayed in the information display field 61, and transmits the generated screen information to the terminal device 1. Meanwhile, the terminal device 1 receives the screen information and displays the details screen of FIG. 11 on the display 13 based on the received screen information.

After that, when the user at the construction site taps the confirmation button 62 on the details screen of FIG. 11, the terminal device 1 and the server device 2 perform appropriate communication or processing, and the group acceptance screen of FIG. 10 that was previously displayed on the display 13 is displayed again.

===SA3===
In SA3 in Fig. 9, the management unit 232 of the server device 2 judges whether or not to store the acceptance information. Specifically, this is arbitrary, but for example, the judgment is made based on whether the user on the construction site side tapped the back button 53 or the acceptance button 54 in Fig. 10 via the touch pad 12 on the group acceptance screen. Then, when the back button 53 is tapped, the terminal device 1 transmits a back button signal (a signal indicating that the back button 53 has been tapped) to the server device 2, and when the management unit 232 of the server device 2 receives the back button signal, it judges that the back button 53 has been tapped, and judges not to store the acceptance information (NO in SA3), and ends the process. In addition, when the acceptance button 54 is tapped, the terminal device 1 transmits an acceptance button signal (a signal indicating that the acceptance button 54 has been tapped) to the server device 2, and when the management unit 232 of the server device 2 receives the acceptance button signal, it determines that the acceptance button 54 has been tapped and determines that the acceptance information should be stored (YES in SA3), and proceeds to SA4.

For example, when a user at the construction site checks the information about the three pipes 900 displayed in the information display section 52 of the group acceptance screen in FIG. 10 and the pipes 900 (pipes 91-93) transported and delivered to the construction site in FIG. 8, and then taps the accept button 54 in FIG. 10, the terminal device 1 sends an accept button signal to the server device 2, and the management unit 232 of the server device 2 receives the accept button signal, determines that the accept button 54 has been tapped, and then determines to store the acceptance information (YES in SA3).

===SA4===
In SA4 of Fig. 9, the management unit 232 of the server device 2 stores the acceptance information, etc. Although the specific details are arbitrary, for example, first, the name information received when the group acceptance information storage process is started is acquired, and current date and time information indicating the current date and time is specified by an arbitrary method (a method of referring to the time measurement result of a timing means such as a timer of the server device 2). Next, referring to the piping acceptance related information of Fig. 5, system information associated with the same component ID as the component ID acquired in SA1 is identified, a component ID associated with the same system information as the identified system information is identified, and "acceptance", the identified current date and time information, and the acquired name information are commonly stored as the acceptance status information, acceptance date and time information, and acceptance person information associated with the identified component ID.

Here, for example, it is assumed that when the group acceptance information storage process is started, "AA AA", a user on the construction site, enters "name information" indicating his/her own name = "AA AA". In this case, first, the "name information" = "AA AA" received when the group acceptance information storage process is started is obtained, and then any method is used to identify "current date and time information" = "07051100", indicating the current date and time, "July 5th, 11:00". Next, by referring to the piping acceptance-related information in FIG. 5, the "system information" = "K-1" associated with the same system information as the "component ID" = "ID0001" acquired in SA1 is identified, and the "component ID" = "ID0001", "ID0002", and "ID0003" associated with the same system information as the identified "system information" = "K-1" are identified, and "acceptance", the identified "current date and time information" = "07051100", and the acquired "name information" = "AA AA" are commonly stored as the acceptance status information, acceptance date and time information, and acceptance staff information associated with the identified "component ID" = "ID0001", "ID0002", and "ID0003", as shown in the first to third rows of FIG. 5.

In this way, for example, the acceptance information for the "K-1" system can be stored all at once by tapping the acceptance button 54 in FIG. 10 once. This completes the group acceptance information storage process.

(Processing - Individual Receipt Information Storage Processing)
Next, the individual acceptance information storage process will be described. The "individual acceptance information storage process" is, in brief, a process performed by the server device 2, and is a process for individually storing the acceptance information for each pipe 900. FIG. 12 is a flowchart of the individual acceptance information storage process. The timing for executing this individual acceptance information storage process is arbitrary, but for example, when a user on the construction site side in FIG. 1 inputs name information indicating his/her name via the touch pad 12 and then performs a predetermined operation to select an individual input mode for individually inputting the acceptance information, the terminal device 1 transmits the input name information and individual input mode information (information indicating that input is performed in the individual input mode) to the server device 2, and the server device 2 starts up when it receives the name information and the individual input mode information. The individual acceptance information storage process will be described from the point where it starts up.

As an example, similar to the group acceptance information storage process, the case will be explained here where the pipes 91 to 93 shown in FIG. 8 are delivered together to the construction site in FIG. 1, and the user at the construction site, "AA AA", accepts pipe 91 of these pipes 91 to 93.

===SB1===
At SB1 in Fig. 12, the reception unit 231 of the server device 2 acquires a component ID. Although the specific details are arbitrary, for example, the component ID is acquired by performing a process similar to SA1 in Fig. 9. Here, for example, "component ID"="ID0001" is acquired.

===SB2===
At SB2 in FIG. 9, the management unit 232 of the server device 2 displays an individual acceptance screen.

=Individual Receipt Screen=
Fig. 13 is a display example of an individual receiving screen. The "individual receiving screen" is a screen for individually storing receiving information for each pipe 900, and includes an information display field 71, as shown in Fig. 13, for example. The "information display field" 71 is a field in which detailed information about one pipe 900 is displayed.

= Processing =
The specific process of SB2 is arbitrary, but for example, by referring to the piping acceptance-related information in Fig. 5, first, the name information, item material information, size information, system information, and processing number information associated with the same component ID as the component ID acquired in SB1 are acquired, and screen information is generated for displaying an individual acceptance screen in which the acquired information and the component ID acquired in the above-mentioned SB1 are displayed in the information display field 71 in Fig. 13 (note that the component ID is displayed in the GUID field in Fig. 13), and the generated screen information is transmitted to the terminal device 1. Meanwhile, the terminal device 1 receives the screen information, and displays the individual acceptance screen on the display 13 based on the received screen information.

For example, here, by referring to the piping acceptance-related information in FIG. 5, the system first acquires "ditch drain pipe," "fireproof double-layer pipe," "xx mm," "K-1," and "1" that are associated with the same component ID as the "component ID" = "ID0001" acquired in SB1, and generates screen information for displaying an individual acceptance screen in which the acquired information and the "component ID" = "ID0001" acquired in SB1 described above are displayed in the information display column 71 in FIG. 13 (note that for the "component ID" "ID0001," a screen is displayed in the GUID column in FIG. 13), and transmits this screen information to the terminal device 1. Meanwhile, the terminal device 1 receives the screen information, and displays the individual acceptance screen of FIG. 13 on the display 13 based on the received screen information.

===SB3===
In SB3 of FIG. 12, the management unit 232 of the server device 2 judges whether to store the acceptance information. Specifically, although it is optional, for example, the same process as SA3 of FIG. 9 is performed, that is, the judgment is made based on whether the user on the construction site side tapped the back button 72 or the acceptance button 73 of FIG. 13 via the touch pad 12 on the individual acceptance screen. Then, when the back button 72 is tapped, the terminal device 1 transmits a back button signal to the server device 2, and when the management unit 232 of the server device 2 receives the back button signal, it determines that the back button 72 has been tapped and determines that the acceptance information is not to be stored (NO in SB3), and ends the processing. Also, when the acceptance button 73 is tapped, the terminal device 1 transmits an acceptance button signal to the server device 2, and when the management unit 232 of the server device 2 receives the acceptance signal, it determines that the acceptance button 73 has been tapped and determines that the acceptance button information is to be stored (YES in SB3), and proceeds to SB4.

Here, for example, if a user at the construction site checks the information displayed in the information display field 71 of the individual acceptance screen in FIG. 13 and the delivered piping 91 in FIG. 8, and then taps the Accept button 73 in FIG. 13, the terminal device 1 sends an Accept button signal to the server device 2, and when the management unit 232 of the server device 2 receives the Accept button signal, it determines that the Accept button 73 has been tapped and decides to store the acceptance information (YES in SB3).

===SB4===
In SB4 of Fig. 12, the management unit 232 of the server device 2 stores the acceptance information, etc. Although the specific details are arbitrary, for example, it is the same as the case of SA4 of Fig. 9, and first, the name information received when the individual acceptance information storage process is started is acquired, and the current date and time information is specified by an arbitrary method. Next, by referring to the piping acceptance related information of Fig. 5, "acceptance", the specified current date and time information, and the acquired name information are stored as the acceptance status information, acceptance date and time information, and acceptance person information associated with the same component ID as the component ID acquired in SB1.

Here, for example, first, the "name information" = "AA AA" received when the individual acceptance information storage process was started is obtained, and the "current date and time information" = "07051100" is identified by any method. Next, by referring to the piping acceptance related information in Figure 5, "Acceptance", the previously identified "current date and time information" = "07051100", and the previously acquired "name information" = "AA AA" are stored as the acceptance status information, acceptance date and time information, and acceptance staff information associated with the same component ID as the "component ID" = "ID0001" acquired in SB1, as shown in the first row of Figure 5.

In this way, for example, it is possible to store the receiving information, etc., individually in the pipe 91. This completes the individual receiving information storage process.

(Effects of this embodiment)
According to this embodiment, by performing a management process for managing a plurality of pipes 900 included in a system, which is a group to which at least one object, that is, a pipe 900, which is identified (i.e., specified) by a component ID, which is object identification information, belongs, it is possible to manage the plurality of pipes 900 collectively, for example, thereby making it possible to easily manage the plurality of pipes 900.

In addition, by performing a process to store information about multiple pipes 900 in one place, for example, multiple pipes 900 can be managed together, making it possible to easily manage multiple pipes 900.

In addition, by performing a process to display the attributes of multiple pipes 900 (see, for example, information display fields 52, 61 in Figures 10 and 11), it becomes possible to allow the user to recognize the attributes of multiple pipes 900, for example.

In addition, since the groups are defined based on the state of the multiple pipes 900 after assembly, it is possible to, for example, smoothly carry out the process of assembling the multiple pipes 900.

In addition, by accepting the component ID, which is the object identification information shown in the read two-dimensional barcode 401, it is possible to eliminate the need for the user to input the component ID using a keyboard, etc., thereby making it possible to easily manage multiple pipes 900.

In addition, by performing a process to store acceptance information indicating that multiple pipes 900 included in a system that is a group to which at least one pipe 900 identified by a component ID, which is object identification information, belongs have been accepted by the construction site, it is possible to collectively manage the acceptance by the construction site of multiple pipes 900 that have been processed in a processing facility, for example, thereby making it possible to easily manage multiple objects.

[III] Modifications to the embodiment The embodiment of the present invention has been described above, but the specific configuration 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. Such modifications will be described below.

(About the problem to be solved and the effects of the invention)
First, the problems that the invention aims to solve and the effects of the invention are not limited to those described above, and may vary depending on the implementation environment of the invention and the details of the configuration, and may solve only some of the problems described above or achieve only some of the effects described above.

(Regarding decentralization and integration)
Furthermore, each of the electrical components described above is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution or integration of each part is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc. For example, at least some of the elements of the terminal device 1 may be arranged in the server device 2, and at least some of the elements of the server device 2 may be arranged in the terminal device 1.

(shape, number, structure, time series)
The components illustrated in the embodiments and drawings may be modified and improved as desired within the scope of the technical concept of the present invention with respect to the shape, numerical values, or structure or chronological relationships of multiple components.

(A terminal that reads two-dimensional barcodes)
In the above embodiment, the construction site side has been described in terms of the case where the two-dimensional barcode 401 is read using the terminal device 1, which is a smartphone or a tablet terminal, but the present invention is not limited to this. For example, the two-dimensional barcode 401 may be read using a so-called AR lens (for example, a goggle-type wearable device). In this case, when the two-dimensional barcode 401 is read using a smartphone or a tablet terminal, the processing described in the embodiment is performed. On the other hand, when the two-dimensional barcode 401 is read using an AR lens, the three-dimensional model shown in FIG. 4 may be displayed on the display of the AR lens by referring to the three-dimensional building viewpoint information in FIG. 3 and using each piece of information associated with the component ID indicated by the read two-dimensional barcode 401, and the assembly method of the piping 900 may be guided. In this case, the AR lens side may be configured to perform spatial recognition of the three-dimensional real space using a known AR technology, and the piping model may be displayed based on the spatial recognition result.

(Additional Note)
The management system of Appendix 1 is a management system for managing a plurality of objects, and comprises a storage means in which group identification information for identifying a group including the plurality of objects is stored, a reception means for receiving object identification information for identifying at least one of the plurality of objects, and a management means for performing management processing for managing the plurality of objects included in a group to which at least one object identified by the object identification information received by the reception means belongs, based on the group identification information stored in the storage means.

The management system of Supplementary Note 2 is the management system described in Supplementary Note 1, in which the management means performs the management process of storing information about the multiple objects in a lump.

The management system of Appendix 3 is the management system described in Appendix 1 or 2, in which the storage means stores attribute information that identifies the attributes of each of the multiple objects, and the management means performs the management process of displaying the attributes of the multiple objects based on the attribute information stored in the storage means.

The management system of appendix 4 is the management system described in any one of appendixes 1 to 3, in which the multiple objects are multiple components assembled at a construction site, and the groups are defined based on the state of the multiple components after assembly.

The management system of Appendix 5 is the management system described in any one of Appendixes 1 to 4, in which each of the plurality of objects is provided with a two-dimensional code indicating the object identification information that identifies each of the plurality of objects, and the management system further includes a reading means for reading the two-dimensional code, and the receiving means receives the object identification information indicated in the two-dimensional code read by the reading means.

The management system of Appendix 6 is the management system described in Appendix 5, in which the multiple objects are transported to the construction site after being processed at a specified processing facility other than the construction site, the reading means reads the two-dimensional codes attached to the multiple objects transported to the construction site, and the management means performs the management process of storing in the storage means acceptance information indicating that the multiple objects included in a group to which at least one object identified by the object identification information received by the receiving means belongs have been accepted by the construction site.

The management program of Appendix 7 is a management program for managing a plurality of objects, and causes a computer to function as: a reception means for receiving object identification information for identifying at least one object among the plurality of objects; and a management means for performing a management process for managing the plurality of objects included in a group to which at least one object identified by the object identification information received by the reception means belongs, based on the group identification information stored in a storage means in which group identification information for identifying a group including the plurality of objects is stored.

(Effect of supplementary notes)
According to the management system described in Appendix 1 and the management program described in Appendix 7, by performing management processing for managing multiple objects included in a group to which at least one object identified by object identification information belongs, it is possible to easily manage multiple objects, for example, by managing multiple objects collectively.

According to the management system described in Appendix 2, by performing a process for storing information about multiple objects in a lump, for example, multiple objects can be managed together, making it possible to easily manage multiple objects.

According to the management system described in Appendix 3, by performing a process to display the attributes of multiple objects, it becomes possible, for example, to allow the user to recognize the attributes of multiple objects.

According to the management system described in Appendix 4, groups are defined based on the state of multiple components after assembly, which makes it possible, for example, to smoothly carry out the process of assembling multiple components.

According to the management system described in Appendix 5, by accepting the object identification information indicated in the read two-dimensional code, it is possible to, for example, eliminate the need for a user to input the object identification information using a keyboard or the like, thereby making it possible to easily manage multiple objects.

According to the management system described in Appendix 6, by performing a process of storing acceptance information indicating that multiple objects included in a group to which at least one object identified by the object identification information belongs have been accepted by the construction site, it is possible to collectively manage the acceptance by the construction site of multiple objects processed in a processing facility, for example, thereby making it possible to easily manage multiple objects.

REFERENCE SIGNS LIST 1 Terminal device 2 Server device 4 Pipe label 11 Communication unit 12 Touch pad 13 Display 14 Camera 15 Recording unit 16 Control unit 21 Communication unit 22 Recording unit 23 Control unit 31 System name display field 32 Drawing display field 33 Information display field 41 Pipe label 42 Pipe label 43 Pipe label 51 System name display field 52 Information display field 53 Back button 54 Accept button 61 Information display field 62 Confirmation button 71 Information display field 72 Back button 73 Accept button 91 Pipe 92 Pipe 93 Pipe 100 Management system 161 Reading unit 221 Three-dimensional building-related information DB
222 Pipe receiving related information DB
231 Reception unit 232 Management unit 401 Two-dimensional barcode 402 Information display field 900 Piping Gm001 Piping model Gm002 Piping model Gm003 Piping model Gm004 Piping model Gm005 Beam model

Claims (6)

A management system for managing a plurality of objects,
a storage means for storing group identification information for identifying a group including the plurality of objects;
a receiving means for receiving object identification information that identifies at least one object among the plurality of objects;
a management means for performing a management process for managing the plurality of objects included in a group to which at least one object identified by the object identification information received by the receiving means belongs, based on the group identification information stored in the storage means,
The management means includes:
When a user selects a first mode for processing, in a batch, acceptance information indicating that the plurality of objects included in a group to which at least one object identified by the object identification information received by the receiving means belongs have been accepted by the construction site side , a first storage process for storing the acceptance information in a batch is performed as the management process;
When the user selects a second mode for processing the received information individually, the first storage process is not performed, and a second storage process for storing the received information individually is performed as the management process.
Management system. the storage means stores attribute information that identifies attributes of each of the plurality of objects;
the management means performs a process of displaying attributes of the plurality of objects based on the attribute information stored in the storage means as the management process.
The management system according to claim 1 . the plurality of objects are a plurality of members to be assembled at the construction site,
The groups are determined based on the state after assembly of the plurality of components.
The management system according to claim 1 or 2. A two-dimensional code indicating the object identification information that identifies each of the plurality of objects is attached to each of the plurality of objects;
The management system includes:
A reading means for reading the two-dimensional code is further provided,
The receiving means receives the object identification information indicated in the two-dimensional code read by the reading means.
The management system according to any one of claims 1 to 3. The plurality of objects are processed in a predetermined processing facility other than the construction site and then transported to the construction site;
The reading means reads the two-dimensional codes attached to the plurality of objects transported to the construction site,
The management means performs a process of storing the acceptance information in the storage means as the management process.
The management system according to claim 4. A management program for managing a plurality of objects,
Computer,
a receiving means for receiving object identification information that identifies at least one object among the plurality of objects;
a management means for performing a management process for managing the plurality of objects included in a group to which at least one object identified by the object identification information received by the receiving means belongs, based on group identification information stored in a storage means in which the group identification information for identifying a group including the plurality of objects is stored,
The management means includes:
When a user selects a first mode for processing, in a batch, acceptance information indicating that the plurality of objects included in a group to which at least one object identified by the object identification information received by the receiving means belongs have been accepted by the construction site side , a first storage process for storing the acceptance information in a batch is performed as the management process;
When the user selects a second mode for processing the received information individually, the first storage process is not performed, and a second storage process for storing the received information individually is performed as the management process.
Management program.

Images