Piping data management system, piping data management method, and program

Abstract

To provide a technology capable of more easily managing data of a piping system.SOLUTION: A piping data management system records type information (cheese, elbow, or the like), position information (X, Y, Z, or the like) and hierarchy information ("At1", "CAB", or the like) of each joint in a piping system 2 in a data table and manages data of the piping system 2. For example, the hierarchy information is symbolized by using two symbol sets ("At"="A"+"t"), and is information that represents a hierarchical level with the number of symbol sets.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to a piping data management system and related techniques. [Background technology]

[0002] Currently, piping diagrams of piping systems are generally drawn using CAD systems. In other words, data on piping systems is often managed using CAD systems. In CAD system data (CAD data), piping systems are mainly represented by line diagrams. Summary of the Invention [Problem to be solved by the invention]

[0003] Meanwhile, at construction sites, etc., the route of pipes in a piping system may be changed. For example, when an unexpected obstacle is present at a construction site, the route of the pipes (piping route) may be changed at the discretion of the site to avoid the obstacle.

[0004] However, it is not always easy to operate a CAD system on-site. Therefore, the CAD data may not be updated after the route is changed, and the piping status after the route change may not be reflected in the CAD data. In such cases, the piping status (piping route status) may be unknown during subsequent maintenance or when a failure occurs.

[0005] These problems arise from the fact that data management of piping systems using CAD systems is not necessarily easy.

[0006] Therefore, an object of the present invention is to provide a technique that enables easier management of data on a piping system. [Means for solving the problem]

[0007] In order to solve the above problems, the piping data management system of the present invention is characterized by having a control means for recording piping data having type information, position information, and hierarchical information of each fitting in a piping system in a data table and managing the data of the piping system.

[0008] The hierarchical information may be information that is symbolized using a single or multiple symbol sets, and the number of the symbol sets represents a hierarchical level.

[0009] The hierarchical information may be symbolized using a single or multiple symbol sets comprising characters, and the order of characters in each symbol set may represent the order of branch joints within the same hierarchy.

[0010] The hierarchical information of a non-branched joint may be symbolized by adding an auxiliary symbol consisting of a different type of symbol from the characters used in the symbol set to the hierarchical information of the branched joint immediately preceding the non-branched joint, and the ranking of the auxiliary symbol may be information that expresses the ranking from the immediately preceding branched joint.

[0011] The hierarchical information may be information that is symbolized using a single or multiple symbol sets comprising numbers, and the order of numbers in each symbol set represents the order of joints within the same hierarchy.

[0012] The piping data management system may further include an acquisition means for acquiring the type information and the position information of each of the joints, and connection information indicating a connection relationship of each of the joints, and the control means may generate the hierarchical information based on the connection information and the type information of each of the joints, and record the hierarchical information, the type information, and the position information in the data table.

[0013] The control means may determine whether each of the joints is a branch joint and whether a joint immediately preceding each of the joints belongs to the same hierarchical level as each of the joints based on the type information and the connection information, and generate the hierarchical information for each of the joints in accordance with a determination result.

[0014] The acquisition means may acquire the positional information of each of the joints in the piping data based on the position of each of the joints in the CAD data of the piping system, and may acquire the connection information of each of the joints based on the positional relationship of each of the joints in the CAD data.

[0015] When one of a plurality of fittings included in the piping system is specified, the control means may identify a piping route in the piping system based on the hierarchical information, the piping route including a fitting lower in rank within the hierarchy to which the specified fitting belongs, and a fitting lower in rank than the specified fitting.

[0016] When the location of a fault in the piping system is known, the control means may, based on the hierarchical information, identify a piping route that includes a joint on a lower level within the hierarchy to which the fault location belongs and a joint on a lower level than the fault location as a route within the affected range.

[0017] When normal terminal appliances and abnormal terminal appliances in the piping system are specified, the control means may estimate a normal route for the normal terminal appliance based on the hierarchical information, and may also estimate an abnormal route for the abnormal terminal appliance based on the normal route.

[0018] In order to solve the above problems, the piping data management method of the present invention is characterized by comprising the steps of: a) recording piping data comprising type information, position information, and hierarchical information of each fitting in a piping system in a data table.

[0019] The hierarchical information may be information that is symbolized using a single or multiple symbol sets, and the number of the symbol sets represents a hierarchical level.

[0020] The hierarchical information may be symbolized using a single or multiple symbol sets comprising characters, and the order of characters in each symbol set may represent the order of branch joints within the same hierarchy.

[0021] The hierarchical information of a non-branched joint may be symbolized by adding an auxiliary symbol consisting of a different type of symbol from the characters used in the symbol set to the hierarchical information of the branched joint immediately preceding the non-branched joint, and the ranking of the auxiliary symbol may be information that expresses the ranking from the immediately preceding branched joint.

[0022] The hierarchical information may be information that is symbolized using a single or multiple symbol sets comprising numbers, and the order of numbers in each symbol set represents the order of joints within the same hierarchy.

[0023] The piping data management method may further include a step of b) acquiring the type information and the position information of each of the fittings, and connection information indicating a connection relationship of each of the fittings, and the step a) may include a step of a-1) generating the hierarchical information based on the connection information and the type information of each of the fittings, and a-2) recording the hierarchical information, the type information, and the position information in the data table.

[0024] In step a-1), it may be determined based on the type information and the connection information whether each of the joints is a branch joint and whether an immediately preceding joint of each of the joints belongs to the same hierarchical level as each of the joints, and the hierarchical information of each of the joints may be generated according to a determination result.

[0025] The step b) may include: b-1) acquiring position information of each of the joints in the piping data based on the position of each of the joints in the CAD data of the piping system; and b-2) acquiring the connection information of each of the joints based on the positional relationship of each of the joints in the CAD data.

[0026] The piping data management method may include a step of c) when one of a plurality of fittings included in the piping system is specified, identifying in the piping system a piping route including a fitting lower in rank within the hierarchy to which the specified fitting belongs, and a fitting lower in rank than the specified fitting, based on the hierarchical information.

[0027] The piping data management method may include a step of: d) when the location of a fault in the piping system is known, identifying, based on the hierarchical information, a piping route that includes a joint on a lower level in the hierarchy to which the fault location belongs and a joint on a lower level than the fault location, as a route within an affected range.

[0028] The piping data management method may include the steps of e) accepting designation of normal terminal devices and abnormal terminal devices in the piping system, and f) estimating a normal route for the normal terminal devices based on the hierarchical information, and estimating an abnormal route for the abnormal terminal device also based on the normal route.

[0029] In order to solve the above problems, the piping data management method of the present invention is characterized by comprising the steps of: a) acquiring piping data having type information, position information, and hierarchical information of each fitting in a piping system; and b) converting the piping data into data for a CAD system, and drawing each of the fittings and the routes connecting the fittings in the CAD system.

[0030] In order to solve the above problems, the present invention provides a program for causing a computer to execute any one of the above piping data management methods. Effect of the Invention

[0031] According to the present invention, data on a piping system can be managed more easily. [Brief description of the drawings]

[0032] [Figure 1] FIG. 1 is a conceptual diagram showing a piping data management system. [Diagram 2] FIG. 2 is a block diagram showing a functional configuration of a management device. [Diagram 3] 2 is a block diagram showing a functional configuration of a management server. [Figure 4] FIG. 1 shows a typical joint. [Diagram 5] FIG. 13 is a diagram showing an example of a piping layout diagram drawn based on piping data. [Figure 6] FIG. 13 is a diagram showing a piping layout diagram in which joint information is expressed using another expression method. [Figure 7] FIG. 7 is an enlarged view of a portion of FIG. 6. [Figure 8] FIG. 4 is a diagram showing data of a first hierarchical level among piping data. [Figure 9] FIG. 11 is a diagram showing data of a second layer of piping data. [Figure 10] FIG. 13 is a diagram showing data of a third layer of piping data. [Figure 11] FIG. 13 is a diagram showing data of a fourth layer of the piping data. [Figure 12] FIG. 13 is a diagram showing a piping layout diagram at the time of inputting some information. [Figure 13] FIG. 13 is a diagram showing a dialogue for inputting joint information. [Figure 14] FIG. 13 is a diagram showing a sub-dialog for inputting joint type information and pipe diameter information. [Figure 15] FIG. 13 is a diagram showing a dialog in which the contents of an input in a sub-dialog are reflected. [Figure 16] FIG. 4 is a piping layout diagram drawn based on input joint information. [Figure 17] This is a piping layout diagram with the joints of the first level drawn. [Figure 18] 13 is a diagram showing a situation in which information on a lower level joint is input into a dialog. FIG. [Figure 19] FIG. 11 is a piping layout diagram drawn based on the joint information of the lower hierarchy. [Figure 20] FIG. 13 is a diagram showing how a piping layout is updated in response to a change in the positions of some joints. [Figure 21] FIG. 13 is a diagram showing a state in which a new joint is added and a piping route is changed. [Figure 22] This is a piping layout diagram in which affected paths due to obstacles, etc. are drawn. [Figure 23] FIG. 11 is a piping layout diagram in which abnormal paths and the like related to the estimation results are depicted. [Figure 24] FIG. 13 is a diagram showing hierarchical information etc. according to a modified example. [Diagram 25] FIG. 13 is a diagram showing hierarchical information etc. according to another modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0034] <1. System Overview> 1 is a conceptual diagram showing a piping data management system 1. The piping data management system 1 is a system that manages data related to a piping system 2. In the following, a water supply piping system is mainly exemplified as the piping system 2.

[0035] The piping system 2 is configured to include pipes 3 and joints (also referred to as pipe joints) 5. There are various types of joints 5, such as a direction-changing joint (elbow, etc.) that changes the direction of the flow of a fluid (here, water), a branch joint (tee, etc.) that branches the flow, and an extension joint (socket, etc.) that joins pipes to extend their length (see FIG. 4).

[0036] A piping system 2 (also simply referred to as piping) is constructed by repeatedly connecting a plurality of pipes 3 with joints 5, etc.

[0037] 1, the piping data management system 1 includes a management device (terminal device) 10 and a management server 30. The management device 10 and the management server 30 are capable of communicating with each other via a network such as the Internet.

[0038] 2. Management Device 10 and Management Server 30 2 is a block diagram showing a functional configuration of the management device 10. The management device 10 is configured as, for example, a tablet terminal, etc. The management device 10 is preferably a computer device suitable for portability.

[0039] As shown in FIG. 2, the management device 10 includes a controller 11 (also referred to as a control unit), a memory unit (storage unit) 12, a communication unit 14, and an operation unit 15.

[0040] The controller 11 is a control device that is built into the management device 10 and controls the operation of the management device 10 .

[0041] The controller 11 is configured as a computer system including one or more hardware processors (e.g., a CPU (Central Processing Unit)). The controller 11 realizes various processes by executing a predetermined software program (hereinafter also simply referred to as a program) stored in a storage unit 12 (a non-volatile storage unit such as a ROM and / or a hard disk) in the CPU or the like. The program (specifically, a group of program modules) (also referred to as a "program product") may be recorded in a portable recording medium such as a USB memory, read from the recording medium, and installed in the management device 10. Alternatively, the program may be downloaded via a communication network or the like and installed in the management device 10. In the management device 10, a program (application program) for managing piping data 200 (data related to the piping system 2) or the like is installed as the program.

[0042] The controller 11 uses the program to execute processes such as storing the piping data 200, input / output processing of the piping data 200, changing the piping data 200, drawing a piping layout diagram of the piping system 2, and data conversion processing between the piping data 200 and CAD data.

[0043] The storage unit 12 is configured with a storage device such as a hard disk drive (HDD) and / or a solid state drive (SSD), etc. The storage unit 12 stores the piping data 200 and the like.

[0044] The communication unit 14 is capable of performing network communication via a network. In this network communication, various protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) are used. By using the network communication, the management device 10 can transmit and receive various data (photographed image data, etc.) to and from a desired destination (for example, the management server 30, etc.) via wire or wirelessly.

[0045] The operation unit 15 includes an operation input unit 15a that receives operation input to the management device 10, and a display unit 15b (for example, a display (liquid crystal display, etc.)) that displays and outputs various information. Here, a touch panel 15c (see FIG. 1) that functions as part of the operation input unit 15a and as part of the display unit 15b is provided. Alternatively, a mouse, a keyboard, etc. may be used as the operation input unit 15a.

[0046] 3 is a block diagram showing the functional configuration of the management server 30. The management server 30 is a device that transmits and receives data to and from the management device 10 and the like. The management server 30 also functions as a CAD device (CAD system) and the like. The management server 30 is also expressed as a cooperating device that cooperates with the management device 10.

[0047] As shown in FIG. 3, the management server 30 includes a controller 31 (also referred to as a control unit), a memory unit (storage unit) 32, a communication unit 34, and an operation unit 35.

[0048] The controller 31 is a control device that is built into the management server 30 and controls the operation of the management server 30 .

[0049] The controller 31 has the same hardware configuration as the controller 11 described above. The controller 31 executes a predetermined program stored in a storage unit (a non-volatile storage unit such as a ROM and / or a hard disk) 32 in a CPU or the like, thereby realizing various processes. The program may be recorded in a portable recording medium such as a USB memory, read from the recording medium, and installed in the management server 30. Alternatively, the program may be downloaded via a communication network or the like and installed in the management server 30. In the management server 30, a program for linking with the management device 10, a program for CAD (also referred to as CAD software), and the like are also installed as the programs.

[0050] The controller 31 uses the program to execute various processes related to CAD and various cooperative processes with the management device 10, etc.

[0051] The storage unit 32 is configured with a storage device such as a hard disk drive (HDD) and / or a solid state drive (SSD), etc. The storage unit 32 stores CAD data related to the piping system 2, etc.

[0052] The communication unit 34 is capable of performing network communication via a network. In this network communication, various protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) are used. By using the network communication, the management server 30 can transmit and receive various data (photographed image data, etc.) to and from a desired destination (for example, the management device 10, etc.) via wire or wirelessly.

[0053] The operation unit 35 includes an operation input unit 35a that receives operation input to the management server 30, and a display unit 35b that displays and outputs various information. A mouse and a keyboard are used as the operation input unit 35a, and a display (such as a liquid crystal display) is used as the display unit 35b. A touch panel that functions as both a part of the operation input unit 35a and a part of the display unit 35b may also be provided.

[0054] <3. Piping system> As described above, the piping system 2 is configured to include the pipes 3 and the joints 5. Fig. 4 is a diagram showing typical joints (specifically, elbows, sockets, and tee joints).

[0055] The top row of Figure 4 shows an elbow (direction-changing joint), the middle row of Figure 4 shows a socket (extension joint), and the bottom row of Figure 4 shows a tee (branch joint).

[0056] An elbow is a direction-changing joint (direction-changing joint) that changes (converts) the direction of travel of a fluid flowing from the upstream side to the downstream side by a predetermined angle (such as 90 degrees).

[0057] A socket is an extension joint that connects pipes to extend their length. Some sockets (also called reducers or different-diameter sockets) have the function of reducing (increasing) the size (diameter) of the pipe (changing the diameter before and after the joint) in addition to the function of connecting pipes to extend their length. The different-diameter sockets are both extension joints and pipe diameter changing joints. For example, in the socket (different-diameter socket) in the middle of Figure 4, the diameter of the pipe on the left side of the joint is different from the diameter of the pipe on the right side in the flow path (path) that flows from left to right through the joint (different-diameter socket) (more specifically, the diameter of the pipe on the right side is smaller than the diameter of the pipe on the left side). Here, the different-diameter sockets (reducers) that have the latter function (diameter changing function) are collectively referred to as "sockets".

[0058] A tee is a branch joint that branches a part (branch) of a fluid flowing from the upstream side to the downstream side in a different direction (for example, at a 90-degree angle to the direction of the main flow). There are also tee's (also called tees) with different diameters in which the diameter of the pipe changes before and after the branch (specifically, tee's in which the pipe diameter (pipe diameter after branching) of the branched route (sub-route) is different from the pipe diameter of the main route (pipe diameter before branching)). For example, in the different diameter tee at the bottom of Figure 4, the pipe diameter of the route (main route) that flows from left to right across the joint (tee) is different from the pipe diameter of the route (sub-route (branched route)) that branches from left to bottom across the joint. Specifically, the diameter of the lower pipe in the branched route is smaller than the diameter of the pipe on the left (and right). Here, both same-diameter tee's and different-diameter tee's (different-diameter tees) are collectively referred to as "tee's".

[0059] <4. Piping Data 200> <Outline of Piping Data 200> In this embodiment, the piping data 200 (data related to the piping system 2) (see Figs. 8 to 11, etc.) is mainly composed of various information (type information, pipe diameter information, position information, hierarchical information, etc.) of the joints constituting the piping system 2. The piping data 200 expresses the type information, pipe diameter information, position information, and hierarchical information of each joint of the piping system 2 in a table format. The piping data 200 expresses a piping route (piping layout) of the piping system 2 based on information of a plurality of joints constituting the piping system 2. However, the piping data 200 is composed as data separate from the CAD data 400 which expresses the piping route of the piping system 2 in a line diagram.

[0060] The joint type information is information that indicates which type of joint it is from a plurality of types such as "L: elbow", "T: tee", and "S: socket".

[0061] The pipe diameter information of a fitting is information about the diameter (size) of a pipe (a pipe to be connected) to be connected with the fitting. For example, the pipe diameter information is information indicating which of the sizes determined by JIS standards or the like, and more specifically, may be expressed as an A designation (nominal diameter of A series) indicating the pipe diameter. In addition, for fittings (such as different diameter tee, different diameter socket, and different diameter elbow) in which the pipe diameters differ between the upstream side (main path side) and the downstream side (particularly the sub-path side) of the fitting, both pipe diameters (main size and sub-size) are managed as pipe diameter information.

[0062] The position information of a joint is information that indicates the position of the representative point of the joint (such as the point where the center lines of the pipes to be connected at an elbow or tee (pipes before and after a direction change, or pipes before and after a branch) intersect). The position information is indicated, for example, by coordinate values ​​(X, Y, Z) with a predetermined reference position (such as a reference position in a building or site) as the origin. However, without being limited to this, for example, the position information may be indicated by the relative movement distance (also referred to as the increment or displacement amount) (ΔX, ΔY, ΔZ) from the previous (or next) joint among the joints that are connected in sequence (by pipes).

[0063] The hierarchical information of a fitting is information indicating which of a plurality of hierarchical paths (flow paths) (also referred to as a flow hierarchy) the fitting exists in (the path (hierarchical path) to which the fitting belongs). In other words, the hierarchical information of a fitting is information indicating the hierarchical level to which the fitting belongs (the rank within the piping system 2). The hierarchical information of a fitting is also referred to as mainstream / division information (main / tributary information) indicating which of the hierarchical flows (main / division) the fitting belongs to. The hierarchical information is information that makes it possible to distinguish a fitting on a path before branching by a branch fitting (such as a tee) from a fitting on a path after branching by the branch fitting as fittings belonging to paths of different hierarchies (upper hierarchical path and lower hierarchical path).

[0064] Here, the hierarchical information is represented as a symbol. Specifically, the hierarchical information is represented as a hierarchical symbol. For example, in FIG. 5, "A", "A1", "Bt1", "BA", "BA1", "CAA", "CAAt1", etc. are shown as the hierarchical information (hierarchical symbol) of each joint.

[0065] Fig. 5 shows an example of a piping layout diagram (piping route diagram) of the piping system 2 drawn based on the piping data 200. In the piping layout diagram of Fig. 5, hierarchical information of each joint is shown. Note that in Fig. 5 (and Fig. 6, etc.), the thickness of the pipes in the piping system 2 (relative to the length of the pipes) is shown emphasized (deformed).

[0066] The hierarchical information (hierarchical symbols) will be described below with reference to FIG.

[0067] In the main route (represented by the thickest pipe in FIG. 5), the first branch joint (tee) located to the right (+X side) (also downstream) of the start point SP is given hierarchical information "A". This "A" is also an identification symbol that uniquely identifies the branch joint (branch point). The branch joint (representative point) is also expressed as branch point "A".

[0068] The second joint (elbow (non-branch joint)) located further to the right is given the hierarchical information "A1". Furthermore, the next joint (third joint) located further down (-Y side) (downstream) on the main route is given the hierarchical information "A2". After that, each joint on the downstream side is given the hierarchical information "B", "B1", "C", "C1", ... in order.

[0069] Here, in the main path (also referred to as the top-level hierarchical path or first-level path), each time a branch joint (cheese) appears, the next-ranked letter (alphabet) (specifically, a capital letter) in the alphabetical order (e.g., "A", "B", "C", ...) is assigned as hierarchical information (hierarchical symbol). For example, the first cheese is assigned "A", the second cheese is assigned "B", and the third cheese is assigned "C". In this way, "A", "B", "C", ... are also identification symbols that uniquely identify each branch joint (branch point).

[0070] Furthermore, for non-branch joints (joints that are not branch joints) in the first level route, numbers (Arabic numerals) are added as hierarchical information. Specifically, each time a non-branch joint (elbow, socket, etc.) appears, the next number (e.g., "1" or "2") is added to the right of the hierarchical information of the immediately preceding branch joint (e.g., "A"), and information (e.g., "A1" or "A2") is added as hierarchical information for each non-branch joint. Similarly, "B1" is assigned to the non-branch joint between "B" and "C," and "C1," "C2," etc. are assigned to the non-branch joint between "C" and "D." In this way, "A1," "A2," "B1," "C1," ... are also identification symbols that uniquely identify each non-branch joint.

[0071] In this way, for joints in the first level route (first level joints), hierarchical information expressed by a single alphabetical character (including an expression in which a number is added to the right of a single alphabetical character) is assigned.

[0072] In addition, for joints (second-level joints) in a route (second-level route) branched from each branch joint at the first level, a second alphabet is added to the right of the first alphabet. In other words, a joint having hierarchical information (including "At", "Bt", "BA", etc.) expressed by (a combination of) two alphabets means that it is a joint in a second-level route. Here, as the second alphabet, "t" (more specifically, lowercase t) representing a distributary or tributary is first added. After that, each time a branch joint appears, the next uppercase alphabet ("A", "B", "C", ...) in alphabetical order is added as the second alphabet in sequence instead of "t". In other words, uppercase alphabets (starting with "A") are added to branch joints in a branch, and "t" is added to non-branch joints that exist up to the first branch joint in the branch.

[0073] Also, for non-branch joints (elbows) in the second level path, information in which a number of the next order is added to the right of the alphabet representing the branch joint immediately before it is given as the hierarchical information of each non-branch joint. For example, for a non-branch joint immediately after a branch joint "BA", information in which a number of the next order (for example, "1" or "2") is added to the right of the alphabet "BA" representing the branch joint immediately before it (such as "BA1" or "BA2") is given as the hierarchical information of each non-branch joint. Similarly, for a non-branch joint immediately after the 0th branch joint "At0" (=A) (described later) in the second level path, information in which a number of the next order (for example, "1" or "2") is added to the right of the alphabet "At" representing the branch joint immediately before it (such as "At1" or "At2") is given as the hierarchical information of each non-branch joint.

[0074] In addition, for joints (third-level joints) in paths (third-level paths) branching from each branch joint at the second level, a third alphabet is added to the right of the second alphabet. In other words, a joint having hierarchical information expressed by three alphabets means that it is a joint in a third-level path. Here, the third alphabet is first given as "t" (specifically, lowercase t), and then, for each branch joint, the next alphabetical letter (uppercase alphabet) is added in order in place of "t" and so on. In addition, for non-branch joints in a third-level path, information (such as "CAt1") in which the next-order number (such as "1") is added to the right of the alphabet (such as "CAt") representing the branch joint immediately before is added as the hierarchical information of each non-branch joint.

[0075] The same applies to the joints (fourth level joints) in the paths (fourth level paths) branching off from each branch joint in the third level, and to the joints in further lower paths, etc.

[0076] In addition, a branch (sub-route) that branches off from a branch point "A" (at a lower level) is also expressed as a "branch At." In other words, "At" is used as a symbol to identify (represent) a branch point, and also as a symbol to identify (represent) the branch (itself). The same is true for other symbols such as "Bt," "BAt," and "Ct."

[0077] As described above, alphabets are assigned to branch joints in the same hierarchy (same hierarchy flow), and the number of letters of the alphabet increases as the hierarchy increases (as the rank becomes lower). In other words, a hierarchical symbol consisting of i consecutive unit symbol sets (also simply referred to as symbol sets) with one alphabet character as a unit is assigned to a "branch joint" at the i-th level. For example, a hierarchical symbol (such as "B", "C") represented by a single (only one) symbol set (composed of one alphabet character units) is assigned to a branch joint at the first level. A hierarchical symbol (such as "At", "CA") consisting of two consecutive symbol sets (one alphabet character units) is assigned to a branch joint at the second level. Similarly, a hierarchical symbol (such as "CAt", "CAB") consisting of three consecutive symbol sets (one alphabet character units) is assigned to a branch joint at the third level.

[0078] In this way, the number of symbol sets represents (specifies) the hierarchical level. For example, the number of symbol sets "B" is 1, and the symbol set "B" represents the first level (first hierarchy). Similarly, the number of symbol sets "At" is 2, and the symbol set "At" represents the second level (second hierarchy). Furthermore, the number of symbol sets "CAB" is 3, and the symbol set "CAB" represents the third level (third hierarchy).

[0079] Also, each alphabet in the hierarchy symbol (the alphabet of the i-th symbol set) represents the order (the order of branching points from the starting point of the i-th level route) of the branching point (branching joint) in the i-th level route (flow). Here, the alphabet "t" represents "0th".

[0080] For example, of the two symbol sets "BA," the first symbol set "B" indicates that it is the second (B) branch point in the first level route (main stream). The second symbol set "A" indicates that it is the first (A) branch point in the second level route branching off from branch point "A." Therefore, the hierarchical symbol "BA" indicates that it is the first branch point in the second level route branching off from branch point B in the first level route.

[0081] In addition, of the two symbol sets, "At", the first symbol set "A" indicates the first (A) branch point in the first level route (main stream). The second symbol set "t" indicates the 0th (t) branch point (branch joint) in the second level route branched from the branch point "A". In other words, the hierarchical symbol "At" indicates a joint (branch joint or non-branch joint) that exists before (upstream of) the first (1st) branch joint (such as a cheese) in the second level route. The hierarchical symbol "At0" indicates the 0th joint in the second level route branched from the branch point "A" in the first level route (the joint immediately before the 1st joint (such as At1) in the second level route). The 0th joint in the second level route is also the starting point of the second level route, and corresponds to the branch joint (branch point) A that exists in the immediately upper hierarchical route (first level route). Therefore, the symbol "At0" is the starting point of the second level path and also means the branching joint (branching point) "A" (in the first level path). Also, the starting point (0th joint) of the second level path "At0" is simply expressed as "At".

[0082] Similarly, the first symbol set "C" of "CAB" consisting of three symbol sets indicates that it is the third (C) branch point in the first level route (main stream). The second symbol set "A" of the hierarchy symbol "CAB" indicates that it is the first (A) branch point in the second level route branching from the branch point C. The last (third) "B" of the hierarchy symbol "CAB" indicates that it is the second (B) branch point in the third level route branching from the branch point CA. Therefore, the joint "CAB" indicates that it is the second branch joint in the third level route branching from the first (A) branch point CA in a specific second level route. The specific second level route is a route branching from the third (C) branch point C in the first level route (main stream).

[0083] In this way, the rank of the characters in each symbol set (specifically, alphabetical rank, etc.) represents the rank within the same hierarchy (specifically, the rank of the branch joints).

[0084] Furthermore, for a "non-branch joint" at the i-th level, a hierarchical symbol is assigned in which an auxiliary symbol (a symbol that supports a symbol set and is a different type of symbol from the characters used in the symbol set) is added to the hierarchical symbol (alphabetical part) of the "branch joint" immediately preceding the non-branch joint. Note that the "immediately preceding" joint of a joint refers to the joint that is higher in the hierarchy to which the joint belongs.

[0085] More specifically, for the non-branching joint, a hierarchical symbol (e.g., "At", "BA") is assigned in which an auxiliary symbol (here, a number) is added to a hierarchical symbol of i consecutive symbol sets (e.g., "At2", "BA1") The number in the auxiliary symbol represents the rank (order) of the non-branching point (non-branching joint) in the i-th level route (flow) (more specifically, the rank from the previous branching point in the i-th level route).

[0086] For example, "BA1" (two symbol set "BA" + auxiliary symbol "1") indicates that the first non-branch point (location of a non-branch joint) in the second level route is located from the previous branch point BA in the second level route. Similarly, "At2" (two symbol set "At" + auxiliary symbol "2") indicates that the second non-branch point (location of a non-branch joint) in the second level route is located from the previous branch point At0 (= "At" = "A") in the second level route (flow).

[0087] For non-branch joints (non-branch points) up to the first branch joint (branch point) in the ith level route, "t" is assigned as the i-th symbol set in the hierarchy symbol. Here, the symbol "t" can be assigned not only to joints in the substream but also to joints in the main stream. For example, in FIG. 5, if a non-branch joint (elbow, etc.) exists between the start point SP of the main stream and the first branch joint "A", each hierarchy symbol "t1", "t2", ... is assigned. In this case, "t" means that it is a non-branch joint that exists from the start point SP of the main stream to the first branch point ("A"), and the number following "t" ("1", "2", etc.) indicates the order (sequence) from the start point SP. The start point SP may also be written as "t0".

[0088] By expressing the hierarchical information in a symbolic form as described above, both machines (computers) and humans can easily understand the hierarchical information (specifically, the hierarchy (hierarchical level) of the joints and the order within the same hierarchy). This makes it possible to obtain the advantage that the hierarchical structure of the piping system 2 can be easily understood.

[0089] In addition, the hierarchy symbol attached to a certain joint makes it possible to easily distinguish whether the joint is a branch joint or a non-branch joint. Specifically, a joint whose hierarchy symbol ends with an alphabet is a branch joint, and a joint whose hierarchy symbol ends with a number is a non-branch joint.

[0090] A branch (sub-route) branched off from a branch point "A" is also expressed as a "branch At." In other words, "At" is used as a symbol to identify (represent) a branch point (joint) and also as a symbol to uniquely identify (represent) a branch.

[0091] <Example of realization of piping data 200> 8 to 11 are diagrams showing an example of piping data 200 (database). In the piping data 200 of FIGS. 8 to 11, information on each joint is recorded as one data record. Moreover, data records showing information on each joint are arranged (vertically in FIG. 8, etc.) according to the connection order of each joint. Here, in FIGS. 8 to 11, the joint information is shown as separate data tables for each hierarchical level (in separate diagrams), and the joint information within the same hierarchical level is shown as separate data tables for each branch. However, this is not limited to this, and the joint information may be configured as a continuous data table (a data table including multiple data records belonging to multiple levels).

[0092] Fig. 8 is a diagram showing various information of multiple joints belonging to the first hierarchical level ("hierarchical level 1 (first level)"). The data table in Fig. 8 (also referred to as first hierarchical level data 210) includes information of joints in the mainstream.

[0093] Fig. 9 is a diagram showing various information of multiple joints belonging to the second hierarchy ("Hierarchy Level 2 (Second Level)"). The data in Fig. 9 (also referred to as second hierarchy data 220) includes information on the joints in each of the second hierarchy branch flows At, Bt, and Ct (see data tables 220a, 220b, and 220c).

[0094] Fig. 10 is a diagram showing various information of multiple joints belonging to the third hierarchy ("hierarchical level 3"). The data in Fig. 10 (also referred to as third hierarchy data 230) includes information on the joints in each of the third hierarchy branch BAt, CAt, and CBt (see data tables 230a, 230b, and 230c).

[0095] Fig. 11 is a diagram showing various information of multiple joints belonging to the fourth hierarchy ("hierarchical level 4"). The data in Fig. 11 (also referred to as fourth hierarchy data 240) includes information on the joints in each of the fourth hierarchy divisions CAAt and CABt (see data tables 240a and 240b).

[0096] The top row of each data table lists information about the starting point of each flow (main stream or each branch stream), and the second row and below lists information (data records) about the fittings (from the first one onwards) belonging to each flow, arranged in order from upstream to downstream.

[0097] Each data record has multiple data fields, including the type of joint, pipe diameter (main, secondary), hierarchical information (hierarchical symbol), incremental position (ΔX, ΔY, ΔZ), and coordinate position (X, Y, Z).

[0098] The "type" of the fitting is information that indicates the type of fitting, such as "T" (tee), "L" (elbow), "S" (socket), etc. Also, "SP" indicates the start point (start end), and "V" indicates the valve (water faucet, etc.) connected at the end of the flow path.

[0099] The direction change angle of an "L" elbow is basically 90 degrees. Here, for elbows with a 90 degree direction change angle, the angle is not indicated. On the other hand, elbows with other direction change angles are indicated with a name that includes the angle, such as "L: elbow (45 degrees)". The same applies to the branching angle of a "T" tee.

[0100] Here, information such as the type of elements other than fittings (for example, a starting end (starting point), a terminal device (valve, etc.)) is also stored in the "Type" column ("Type" field). However, this is not limited to this, and information on elements other than fittings may be stored in an item column (data field) provided separately from the "(fitting) type".

[0101] The "pipe diameter" of a fitting is information that indicates the diameter (size) of the pipe (connection target pipe) to be connected with the fitting. Here, in order to accommodate fittings with different diameters, two items, "main (size)" and "secondary (size)", are provided as pipe diameter information (pipe diameter size).

[0102] The "hierarchical information" of a joint is information that indicates, in a hierarchical manner, the route to which the joint belongs. Here, the hierarchical information is expressed by a hierarchical symbol (see FIG. 5, etc.).

[0103] Furthermore, items for two types of position information (increment amount and coordinate value) are provided as position information for joints. "Increment amount" is information indicating the increment amount (increment position) from the previous joint (or starting point), and is specifically composed of increment amounts (increment values) ΔX, ΔY, and ΔZ in each of the three directions, X, Y, and Z. "Coordinate value" is indicated by coordinate values ​​X, Y, and Z with a predetermined reference position (such as a reference position in a building) as the origin. Note that, although items related to two types of position information (increment amount and coordinate value) are provided here, the present invention is not limited to this, and only one of the two types of position information may be provided.

[0104] The type and diameter of a joint are information that indicates the basic configuration (physical configuration) of a joint, and are also expressed as "joint basic information", etc. Meanwhile, the hierarchical information and position information of a joint are auxiliary information of a joint, and are also expressed as "joint auxiliary information", etc.

[0105] 8 to 11, information on multiple joints in the same layer is stored as vertically consecutive data records in accordance with the connection order of the multiple joints. Therefore, information on a previous joint to a certain joint in the same layer is obtained by referring to the data record immediately above (immediately before) the certain joint. For example, information on the previous joint to joint A2 in the first layer is obtained (as the data record of previous joint A1) by referring to the data record immediately above (immediately before) the certain joint A2 (the third row from the top) (see FIG. 8).

[0106] Moreover, information on the routes (lower hierarchical routes) branching (diverging) from each branch joint in each hierarchy is acquired by identifying routes starting from each branch joint from the level information of the lower hierarchy. For example, information on a lower hierarchical route (route of the hierarchy (child hierarchy) one level lower) branching (diverging) from a branch joint C in the first hierarchy is acquired by identifying a route starting from the branch joint C (Ct0) from the level information of the lower hierarchy (second hierarchy) (see FIG. 9). Similarly, information on a lower hierarchical route branching from a branch joint CB in the second hierarchy is acquired by identifying a route starting from the branch joint CB (CBt0) from the level information of the lower hierarchy (third hierarchy) (see FIG. 10).

[0107] In the above, the piping data 200 as shown in Fig. 8 to Fig. 11 is exemplified, but is not limited thereto. For example, in the data table constituting the above-mentioned piping data 200, other field information may be further provided for each data record. Examples of the other field information include "hierarchical level" ("hierarchical level 1", "hierarchical level 2", etc.), "adjacent joint information" (hierarchical information of the immediately preceding joint), "presence or absence of a lower hierarchy table (sub-table)", etc.

[0108] <Example of joint information expression> In addition, the type information and pipe diameter information of each joint may be combined with each other and expressed as follows.

[0109] For example, the information on fitting 501 (see FIG. 5) (fitting "A") is expressed as "50×20T." Here, the "T" in "50×20T" indicates that "fitting type = Tee," and "50×20" indicates that "pipe diameter in main direction = 50 (nominal diameter)" and "pipe diameter in secondary direction (branch direction) = 20 (nominal diameter)."

[0110] Furthermore, the type information and pipe diameter information of each joint may be combined with hierarchical information of the joint and expressed as follows:

[0111] For example, the information of joint 501 (see FIG. 5) is expressed as "50×20T:A" (see FIG. 6). Here, the "A" next to "50×20T" indicates the hierarchical information of joint 501 (that it is the first branch joint in the first level route). Note that ":" is a delimiter that separates "50×20T" and "A" while connecting (associating) them. However, the delimiter is not limited to this, and may be a symbol other than ":" (such as " / " or "-").

[0112] In Figures 6 and 7, information on each joint is shown using such an expression method. Note that Figure 7 is an enlarged view of a part (a part surrounded by a dashed line) of Figure 6. For convenience of illustration, the part in Figure 6 is shown in the same expression as in Figure 5.

[0113] Moreover, the information of each joint may be expressed as follows, further combined with the position information. For example, the information of the joint 501 is expressed as "50×20T:A:(X0+ΔX1,Y0,Z0)". "(X0+ΔX1,Y0,Z0)" is a value (for example, (0,6000,0)) indicating the coordinate value (X,Y,Z) with a predetermined reference position as the origin. The position indicated by the coordinate value is also a position moved by +ΔX1 in the X direction with respect to the coordinate value (X0,Y0,Z0) of the start point SP. Note that the position information of the joint 501 may be indicated by the relative moving distance (increment) (ΔX,ΔY,ΔZ) from the previous joint, as described above. The information of the joint 501 may be expressed, for example, as "50×20T:A:ΔX=+2000". "ΔX=2000" indicates that the position is moved +2000 (mm: millimeters) in the X direction from the coordinate value of the previous joint.

[0114] Also, information on pipes connected by joints is generated from information on the joints. For example, the actual length of the pipe connecting joints "A (=At0)" and "At1" is calculated by subtracting a predetermined length (e.g., several tens of mm) determined for each joint from the distance between the positions of joints At0 and At1 (e.g., the increment ΔY in the Y direction). Also, the thickness of the pipe is calculated based on the pipe diameter information (secondary size) of joint At0 (=AB) or the pipe diameter information (primary size) of joint At1.

[0115] <5. Generation process of piping data 200 (user input, etc.)> Next, a process for generating piping data 200 in the piping data management system 1 (a process for generating data according to user input) will be described. It is assumed here that the coordinate value of the start point SP and the coordinate values ​​of each of a plurality of terminal devices (valves V1 to V8) have already been registered in the piping data 200. FIG. 12 is a diagram showing a state in which a piping layout diagram (piping route diagram) is generated based on such registered information, and the piping layout diagram is first displayed in the display area 300 of the display unit 15b (15c). In FIG. 12, only the start point SP and the terminal points V1 to V8 are arranged at positions according to their respective coordinate values.

[0116] The operator displays a pop-up menu by long tapping (or clicking the right button of the mouse (also simply referred to as right clicking)) on the start point SP (shown here as a circle) displayed on the display unit 15b (display area 300). The pop-up menu includes options such as "Add the next joint information of the same level," "Add the joint information of a lower level," "Change the joint information," and "Delete the joint information." When "Add the next joint information of the same level" is selected from the pop-up menu, the dialog (screen) 320 in FIG. 13 is displayed.

[0117] The dialog 320 has an input field 321 for "information of the joint to be input," an input field 322 for "hierarchy (flow level)," an input field 323 for "adjacent joint information (hierarchical information of the previous joint)," and a button 325. The input fields 322 and 323 already display information that has been automatically determined based on the previous joint of the added joint (here, the start point SP). The input field 321 is still blank (no input has been made). The button 325 is a button for calling up a sub-dialog 330 (see FIG. 14) for inputting joint information (described later).

[0118] The dialog 320 also has radio buttons 326, 327 for selecting the position information input method (increment input method / coordinate value input method). The dialog 320 also has increment fields 326X, 326Y, 326Z for inputting increment amounts in the X, Y, and Z directions, and coordinate value fields 327X, 327Y, 327Z for inputting coordinate values ​​in the X, Y, and Z directions.

[0119] In addition, the dialog 320 has an OK button 328 and a Cancel button 329 .

[0120] When button 325 is pressed in the display state of FIG. 13, sub-dialog 330 (FIG. 14) is displayed.

[0121] The sub-dialog 330 has an input field 331 for "joint type," an input field 332 for "pipe diameter size (main size)," an input field 333 for "pipe diameter size (secondary size)," an OK button 338, and a cancel button 339. The input field 331 is configured as a list box.

[0122] The operator selects a desired option from a plurality of options (including "T: Tee", "L: Elbow", "S: Socket", etc.) in input field 331 (list box). FIG. 14 shows the state in which "T: Tee" is selected. The operator also inputs the main pipe diameter size (e.g., "50") in input field 332, and the secondary pipe diameter size (e.g., "20") in input field 333. Note that the pipe diameter (main size) (e.g., "50") of the immediately preceding joint may be automatically pre-displayed in input field 332.

[0123] After that, when the OK button 338 is pressed, the input contents in the sub-dialog 330 are reflected in the input field 321 of the dialog 320 (see FIG. 15). At this time, in response to the input of the type information of the joint, the hierarchical information of the joint (here, the hierarchical symbol "A") is automatically calculated based on the type information and the hierarchical information of the immediately preceding joint (here, the start point SP). In detail, the hierarchical information of the joint (hierarchical symbol "A") is calculated based on the fact that the joint is in the same hierarchical level (first hierarchical level) as the start point SP and is the first branch joint (branch point). Then, as shown in FIG. 15, "50×25T:A" is displayed in the input field 321. As described above, "50×25T:A" indicates that the type of the joint is a tee (T), the pipe diameter (nominal diameter) in the main direction is "50", the pipe diameter (nominal diameter) in the secondary direction is "20", and the hierarchical symbol of the joint is "A".

[0124] Here, information equivalent to "50×25T:A" is input using the sub-dialog 330, but the present invention is not limited to this, and the character string "50×25T:A" may be directly input into the input field 321 of the dialog 320. In this case, the joint type ("T: Tee") and pipe diameter information ("Main=50", "Secondary=25") may be automatically obtained by the management device 10 based on the input character string "50×25T:A".

[0125] Furthermore, the operator inputs the position information of the joint. For example, the operator presses the radio button 326 to select the increment input method, and inputs "2000" (ΔX=+2000 (mm)) in the increment field 326X. The management device 10 updates (calculates) the coordinate values ​​(X, Y, Z) in response to the input of the increment amount (ΔX, ΔY, ΔZ), and (automatically) updates the display contents of the coordinate value fields 327X, 327Y, and 327Z. For example, the coordinate values ​​(X, Y, Z) are changed from (-2000, 6000, 0) to (0, 6000, 0), and the display contents of the coordinate value field 327X change from "-2000" (FIG. 13) to "0" (FIG. 15). The operator may also press the radio button 327 to select the coordinate value input method, and input appropriate contents into each of the coordinate value fields 327X, 327Y, and 327Z. In this case, the increment amounts (ΔX, ΔY, ΔZ) are updated (calculated) in response to the input of coordinate values ​​(X, Y, Z), and the display contents of the increment fields 326X, 326Y, 326Z are automatically updated.

[0126] When the input is completed, the operator presses the OK button 328. In response to pressing the OK button 328, the input information is confirmed (the contents of the piping data 200 are updated). Specifically, in the piping data 200, information on the first fitting ("A") at the first hierarchical level is registered (updated) (see the data record in the second row from the top in FIG. 8). Also, in the data at the second hierarchical level (second hierarchical data) 210 (see FIG. 9) of the piping data 200, a data table 220a relating to the branch At branching from the fitting "A" is created. Then, in the top row of the data table 220a, information (data record) of the fitting "A" is registered as information on the 0th fitting (start point of the branch At) of the branch At. Note that when the cancel button 329 is pressed, the information entered using the dialogue 320 is canceled, and the piping data 200 is not updated.

[0127] Furthermore, in the display area 300 (also referred to as the screen 300), a state in which a tee (T) is placed at a position +2000 in the X direction from the start point SP is drawn (in response to pressing of the OK button 328) (see FIG. 16). More specifically, a state in which the start point SP and the tee are connected by a pipe with a pipe diameter of "50" (main size) is drawn. Also, "A" is displayed (near the tee) as the hierarchical information of the tee. Here, the tee is drawn in a state in which it is temporarily placed in a predetermined direction (for example, a direction branching upward (+Y direction)). The direction of the tee is appropriately corrected according to a later input (input of the second hierarchical level (joint information at the branch At)). For example, if the position of the next joint At1 is below (-Y side) of the branch joint A, the direction of the tee is corrected (changed) to a direction branching downward (-Y direction). As shown in FIG. 6 and other figures, "50×25T:A" (which includes not only "A" but also "50×25T") may be displayed as information about the cheese (near the cheese).

[0128] Similarly, when information on a plurality of joints (A1, A2, B, B1, C, C1) at the first hierarchical level is input in sequence, data 210 (see FIG. 8) at the first hierarchical level of the piping data 200 is registered accordingly. Also, on the screen 300, the piping route (the piping route at the first hierarchical level) passing through the plurality of joints from the start point SP is updated and drawn in sequence (see FIG. 17).

[0129] Next, the input process of information on joints at lower hierarchical levels will be described.

[0130] For example, the joint At1 (see FIG. 5) of the lower hierarchical level path (second level path) branching off from the branch joint "A" to the +Y side is input as follows.

[0131] Specifically, in the display state of Fig. 17, the operator displays a pop-up menu by long tapping (or right-clicking) on ​​the branch point "A" (shown here as a circle) displayed on the display unit 15b (display area 300). When "Additionally input lower level joint information" is selected from the pop-up menu, the dialogue 320 of Fig. 18 is displayed.

[0132] Information that has been automatically generated based on the immediately preceding joint "A" of the added joint is already displayed in input fields 322, 323 of the dialog 320. Specifically, since the newly created joint (additional joint) is one hierarchical level lower than the immediately preceding joint "A" (first hierarchical level), "second hierarchical level" is specified as the hierarchy level of the added joint, and "second hierarchical level" is displayed in input field 322. In addition, the joint "A" is specified as information on the immediately preceding joint of the newly created joint (additional joint), and "A" is displayed in input field 323.

[0133] When the button 325 is pressed in the display state of FIG. 18, the sub-dialog 330 (see FIG. 14) is displayed. However, the pipe diameter (main size) (for example, "20") of the fitting to be input is (automatically) displayed in the input field 332 of the sub-dialog 330. Specifically, the process related to the sub-dialog 330 is an input process related to a fitting in the hierarchy (second hierarchy) one level lower than the fitting "A". Based on this, the sub-size (for example, "20") of the pipe diameter of the original fitting (fitting in the hierarchy immediately above the fitting to be input) "A" is specified as the pipe diameter (main size) of the fitting to be input. Then, the specified pipe diameter (main size) is displayed in the input field 332. Note that the same size (for example, "20") as the input field 332 is displayed in the input field 333 as the initial state (or as a blank field), and may be changed as necessary.

[0134] When "L: Elbow" is selected from among multiple options in the input field 331 (list box) in the sub-dialog 330 and the OK button 338 is pressed, the input contents in the sub-dialog 330 are reflected in the input field 321 of the dialog 320 accordingly. Specifically, based on the type information of the added joint "L: Elbow" (non-branch joint) and the hierarchical information of the immediately preceding joint ("A"), the hierarchical information of the added joint (here, the hierarchical symbol "At1") and the branch flow to which the added joint belongs ("At") are automatically obtained. In detail, based on the fact that the added joint is a joint in the hierarchical level (second hierarchical level) one level lower than the joint "A" and is the first non-branched joint (branch point), the hierarchical information of the added joint (hierarchical symbol "At1") and the branch flow to which the added joint belongs ("At") are obtained. Then, as shown in FIG. 18, "20L:At1" is displayed in the input field 321. "20L:At1" indicates that the type of fitting is an elbow (L), the pipe diameter (nominal diameter) is "20", and the fitting hierarchy symbol is "At1".

[0135] Furthermore, the operator inputs position information of the joint. For example, the operator inputs "3000" (ΔY = +3000 (mm)) in the increment field 326Y. In response to the input of the increment amount (ΔX, ΔY, ΔZ), the coordinate values ​​(X, Y, Z) are changed from (0, 6000, 0) to (0, 9000, 0), and the coordinate value fields 327X, 327Y, and 327Z are automatically updated.

[0136] Upon completing the input, the operator presses the OK button 328. In response to pressing the OK button 328, the input information is confirmed (the contents of the piping data 200 are updated). Specifically, in the data table 220a relating to the branch At in the second hierarchical data 220 (see the top row in FIG. 9), information on the first fitting At1 in the second hierarchical level one level lower than the fitting "A" is registered (updated) (see the data record in the second row from the top).

[0137] Furthermore, on the screen 300, an elbow (L) is depicted at a position +3000 in the Y direction from the branch point "A" (see FIG. 19). More specifically, a state in which the branch point "A" and the elbow are connected by a pipe with a pipe diameter of "20" is depicted. Also, "At1" is displayed (near the elbow) as the hierarchical information of the elbow. Here, the elbow is provisionally placed facing right (in a direction that changes the flow direction to the +X direction). However, the direction of the elbow is appropriately corrected according to subsequent input (input of information on the next joint in the branch At). Note that, as shown in FIG. 6 etc., "20L:At1" (which includes not only "At1" but also "20L") etc. may be displayed (near the elbow) as information on the elbow.

[0138] Thereafter, when information on the remaining joints (At2, At3) at the second hierarchical level related to the branch At is input in sequence according to the connection order, (all) information on the branch At is registered accordingly in the second hierarchical data 220 (see FIG. 9) of the piping data 200. Also, on the screen 300, the piping route of the second hierarchical level starting from the branch point "A" (the piping route of the branch At) is updated and drawn in sequence.

[0139] When inputting information about the joint At3 (more specifically, the valve V1) at the end of the branch flow At, a "valve" is selected as the type of joint in the sub-dialog 330 (although a valve is not strictly speaking a joint, for convenience, it will be treated as a type of "joint" here). When a coordinate value (or an increment value) is input as position information in the dialog 320, the valve V1 having the same coordinate value as the input coordinate value (the input coordinate value itself, or the coordinate value calculated in response to the input of the increment value) is automatically identified (based on the information about the valve V1 that has been set in advance). If there is no valve that can be connected by the joint At2, a warning is displayed (after pressing the OK button 328, etc.), and the user is prompted to change the input information, etc.

[0140] Similarly, when information on multiple joints (Bt1, Bt2, BA, BA1, BA2) at the second hierarchical level related to the branch Bt is input in order of connection, information on the branch Bt is registered (all) in the second hierarchical data 220 (see FIG. 9). Also, on the screen 300, the piping route of the second hierarchical level (piping route of the branch Bt) starting from the branch point B is updated and drawn in sequence. The same applies to other branches Ct, etc.

[0141] Furthermore, similar input processing is performed for the third and fourth hierarchical levels. As a result, the piping data 200 shown in Figures 8 to 11 is completed, and a piping layout diagram (piping route diagram) such as Figure 5 or Figure 6 is drawn.

[0142] As described above, the management device 10 acquires type information of each joint (target joint) and connection information indicating the connection relationship of each joint (information of the joint immediately preceding each joint (information including the connection order between adjacent joints) and the hierarchical relationship between adjacent joints, etc.) through input from the operator.

[0143] For example, when inputting information on a joint to be added (a joint of interest), an operation such as tapping (long tapping) on ​​the joint immediately preceding the joint of interest (the joint immediately preceding the joint of interest) corresponds to a process of inputting (specifying) which joint the joint immediately preceding the joint of interest is (information on the joint immediately preceding the joint of interest). In addition, whether or not the joint immediately preceding the joint of interest belongs to the same hierarchy as the joint of interest (in other words, the hierarchical relationship between adjacent joints) is determined according to the option selected in the pop-up menu. Specifically, when "Add and input the next joint information of the same level" is selected, it is determined that the joint of interest and the joint immediately preceding the joint of interest belong to the same hierarchy. On the other hand, when "Add and input lower level joint information" is selected, it is determined that the joint of interest and the joint immediately preceding the joint of interest do not belong to the same hierarchy (the joint of interest belongs to a hierarchy one level lower than the joint immediately preceding the joint of interest). Furthermore, whether or not the one joint to be processed (the joint of interest) is a branch joint is determined based on the information entered in the input field 331 (or 321). For example, if "tee" or the like is entered as the type information of the joint of interest, it is determined that the joint of interest is a branch joint. On the other hand, if "elbow" (direction-changing joint), "socket" (extension joint), or the like is entered as the type information of the joint of interest, it is determined that the joint of interest is not a branch joint (is a non-branch joint).

[0144] Then, the management device 10 automatically generates "hierarchical information" for each joint (joint of interest) based on type information (whether it is a branch joint or not) and connection information for each joint (which joint is the previous joint, whether it belongs to the same hierarchical level as the previous joint, etc.).

[0145] In detail, the management device 10 judges whether a joint to be processed (a joint of interest) is a branch joint based on the input (acquired) type information, and judges whether a joint immediately before the joint of interest belongs to the same hierarchical level as the joint of interest based on the input (acquired) connection information. The management device 10 automatically generates hierarchical information of the joint of interest according to the judgment result.

[0146] If the joint of interest belongs to the same hierarchy as the joint immediately preceding the joint of interest, the number of symbol sets is maintained. If the joint of interest is a branching joint, no supplementary symbol is added and the alphabetical order of the last symbol set is incremented (+1). On the other hand, if the joint of interest is a non-branching joint, a supplementary symbol is added and the numerical order of the supplementary symbol is incremented (+1).

[0147] If the joint of interest belongs to a hierarchy one level lower than the joint immediately preceding the joint of interest, the number of symbol sets is increased by one, and the alphabet (last alphabet) of the added symbol set is set to the initial state "t". If the joint of interest is a branching joint, no auxiliary symbol is added. On the other hand, if the joint of interest is a non-branching joint, an auxiliary symbol is added, and the number of the auxiliary symbol is set to the initial state "1".

[0148] In other words, for a branch joint (branch point), a hierarchical symbol is generated by incrementing the last alphabet of the hierarchical symbol of the branch point immediately preceding the branch point (or by adding one alphabet to the initial state (t)). On the other hand, for a non-branch joint (non-branch point), a hierarchical symbol is generated by adding a number indicating the rank from the hierarchical symbol of the branch point immediately preceding the non-branch point.

[0149] In particular, it is preferable that the hierarchical information (hierarchical symbol) is automatically generated based on the connection information and type information of each joint as described above. In this way, the hierarchical information (hierarchical symbol) is generated while reducing the effort of the operator.

[0150] In the above embodiment, each joint and a path (pipe) connected to each joint are drawn based on the piping data 200. Therefore, it is possible to visually grasp (in a illustrated state) the piping route (piping layout) of the piping system 2 without requiring CAD data.

[0151] <6. Partial route change processing using piping data 200> Moreover, it is possible to easily manage the piping route by using the above-mentioned piping data 200. In particular, when the piping route is partially changed (during design change, etc.), the above-mentioned piping data 200 is extremely useful.

[0152] <Change in joint position> For example, when changing the positions of the joints At1 and At2 (see the left side of Fig. 20), the following processing may be performed. Fig. 20 is a diagram showing how the piping layout is updated in response to a change in the position of one joint (At1). The left side of Fig. 20 shows the situation before the change, and the right side of Fig. 20 shows the situation after the change.

[0153] Specifically, in the data table 220a relating to the diversion At in the second hierarchical data 220 (see FIG. 9), a process is performed to change the value in the ΔY column of the data record in the second row from the top from the pre-change value ("3000") to the post-change value (for example, "4000").

[0154] In detail, in the display state of FIG. 5 (or FIG. 6, etc.), the operator displays a pop-up menu by, for example, long tapping on the joint At1 displayed on the display unit 15b (15c). When "Change joint information" is selected from the pop-up menu, a dialogue 320 similar to that of FIG. 18 (see FIG. 18, etc.) is displayed. Here, information on the joint At1 (before the change) is displayed in the dialogue 320. In the dialogue 320, the operator performs an operation to change the content of the increment column 326Y from the value before the change ("3000") to the value after the change (for example, "4000").

[0155] In response to this operation, the management device 10 (controller 11) changes the value in the Y column of the data record in the second row from the top of the data table 220a from the value before the change ("3000") to the value after the change (for example, "4000"). Furthermore, the management device 10 updates the coordinate values ​​of the joints after the joint At1. Specifically, the coordinate value of the joint At1 is updated ((0,9000,0)→(0,10000,0)), and the coordinate value of the joint At2 is updated ((1000,9000,0)→(1000,10000,0)). Furthermore, the management device 10 updates the value in the ΔY column of the valve V1 next to the joint At2 (ΔY:2000→1000). Here, it is assumed that "fixed (unchangeable)" is set in advance as the attribute information of the position information (coordinate value) of the valve V1. When such settings are made, the coordinate value of the valve V1 is not changed, and the distance information (increment information) between the valve V1 and the immediately preceding joint At2 is adjusted.

[0156] Furthermore, the screen 300 is updated. Specifically, the display positions of the joints At1 and At2 in the screen 300 are changed (see the right side of FIG. 20). Specifically, the joints At1 and At2 (elbow (L)) are placed at a position ΔY=+4000 from the joint "A", and the pipe connecting the joints At1 and At2 is drawn in a state in which it has been appropriately moved in the Y direction (upward in the figure) by the difference amount (+1000) before and after the change. In addition, the length of the pipe connecting the joint "A" and the joint At1 is appropriately adjusted and changed (to extend by "1000"), and the length of the pipe connecting the joint At2 and the valve V1 (At3) is also appropriately changed (to shorten by "1000").

[0157] According to such a process, the piping layout can be easily changed by a very simple operation by the operator. In detail, for example, by "only changing the increment ΔY" of the joint At1, it is possible to generate a piping layout (and a diagram representing the piping layout) (see the right side of FIG. 20) in which the length of the pipe from the joint A to the joint At1, etc. are changed. In addition, it is also possible to automatically change the position of the joint At2 together with the joint At1.

[0158] Note that, when implementing the above-mentioned change processing in a CAD system, relatively cumbersome operations are required. Specifically, operations such as moving the fittings At1 and At2 and the pipe (the pipe connecting the fittings At1 and At2) (1000 in the +Y direction) on the CAD drawing and changing the length of the pipe (the pipe up to the fitting At1 and the pipe from the fitting At2) are required. Compared to such operations (operations on the CAD), the above-mentioned change operations (change operations related to the piping data 200) are much easier operations ("only change operations of the increment amount ΔY").

[0159] <Adding (inserting) a new joint> It is also possible to add (insert) a new joint. In Fig. 21, a situation is assumed in which the piping route is changed to avoid an obstacle, more specifically, a situation in which the position of the joint At2 (see Fig. 21) is changed and joints At3 and At4 are added (inserted between the joint At2 and the valve V1). In this case, the following processing may be performed. Note that the left side of Fig. 21 shows the situation before the piping route is changed, and the right side of Fig. 21 shows the situation after the piping route is changed. Also, the center of Fig. 21 shows the situation during the change (at a certain point in time).

[0160] First, the position of the joint At2 is changed in the same manner as described above. For example, a change from "ΔX=+4000" to "ΔX=+2000" is made. At this time, the direction from the joint At1 to the joint At2 and the direction from the (changed) joint At2 to the valve V1 are not perpendicular, so if the joint At2 is an elbow (90 degrees), the joint At1 and the valve V1 cannot be connected. Therefore, the pipeline connecting the joint At2 and the valve V1 is not displayed, and instead a warning message (a thick dotted line in FIG. 21) is displayed (see the center column of FIG. 21).

[0161] Next, a process of adding a joint (new At3) next to the joint At2 is performed. Specifically, the operator displays a pop-up menu by long-tapping the joint At2 displayed on the display unit 15b (15c), for example. When "Add next joint information of the same level" is selected from the pop-up menu, a dialogue 320 is displayed. Thereafter, in the same manner as above, information on the new joint At3 (elbow) and the like are input, and data on the new joint At3 is added. In detail, the data record of the new joint At3 is inserted between the data record of the joint At2 and the data record of the original joint At3 in the data table 220b. Also, the display contents on the screen 300 are updated, and the joint At3 and the like are also displayed. However, the pipeline connecting the joint At3 and the valve V1 is not displayed, and instead, a warning message is displayed.

[0162] Furthermore, a process of adding a new joint (At4) next to the joint At3 is performed in a similar manner. As a result, data of the new joint At4 is added. The display content on the screen 300 is also updated, and the new joint At4, etc. are also displayed. At this time, on the condition that the new joint At4 is placed in an appropriate position, the warning display is erased, and the pipeline connecting the new joint At4 and the valve V1 is also displayed (see the right column in FIG. 21).

[0163] <Delete existing fitting> Similarly, it is also possible to delete existing joints. For example, a process may be performed in which the piping route is changed from the right side to the left side of Fig. 21 (in the opposite direction to the above), more specifically, a process may be performed in which the joints At3 and At4 are deleted (due to the removal of obstacles, etc.) and the position of the joint At2 (see Fig. 21) is changed.

[0164] For example, first, a process of deleting fitting At4 is performed. Specifically, the operator displays a pop-up menu by, for example, long-tapping on fitting At4 displayed on display unit 15b (15c). When "Delete fitting information" is selected from the pop-up menu, the data record of fitting At4 is deleted. Also, the display content on screen 300 is updated, and (the image of) fitting At4 is deleted from screen 300. However, the pipeline connecting fitting At3 and valve V1 is not displayed, and instead a warning message is displayed.

[0165] Next, a process for deleting the fitting At3 is performed in a similar manner. In response to an operation by the operator (such as a selection operation of "Delete fitting information"), the data record of the fitting At3 is deleted. Furthermore, the display content on the screen 300 is updated, and (the image of) the fitting At3 is deleted from the screen 300. However, the pipeline connecting the fitting At2 and the valve V1 is not displayed, and instead a warning message is displayed.

[0166] Finally, a process for changing the position of the joint At2 is performed. In response to the operation of the operator, the data record of the joint At2 is updated. Also, the display content on the screen 300 is updated. At this time, on the condition that the joint At2 is placed in an appropriate position, the warning display is erased, and the pipeline connecting the joint At2 and the valve V1 is also displayed (see the left column of FIG. 21).

[0167] In the above embodiment, when a joint is added, the hierarchical symbol may be changed as needed. For example, when a new joint is added between joints "B" and "C", the new joint may be given the symbol "C" and the original joint "C" may be reassigned the symbol "D". The original joints "D" and onward may also be assigned symbols that are shifted in the same manner. However, this is not limited to this. For example, the existing joints may not be reassigned the hierarchical symbol, and the new joint may be assigned an unassigned alphabet (the alphabet next to the alphabet (e.g. "F") assigned to the last joint (e.g. "E")).

[0168] The same applies when a joint is deleted. A process of reassigning hierarchical symbols to joints other than the deleted joint may be performed, or conversely, a process of reassigning hierarchical symbols may not be performed.

[0169] <7. Extraction of partial paths based on piping data 200> As described above, the hierarchical information is information that can distinguish, in particular, a joint on a route before the branching of a branch joint from a joint on a route after the branching as joints that belong to routes of different hierarchical levels (upper hierarchical route and lower hierarchical route). According to such hierarchical information, it is possible to easily extract only a route of a predetermined hierarchical level (a route downstream of a predetermined branch joint) (partial route information) from (all routes of) the piping system 2.

[0170] Specifically, the management device 10 can partially extract (identify in the piping system 2) a piping route including a joint on the lower-ranking side (lower order side) in the hierarchy to which a specific joint belongs, and a joint on the lower-ranking side than the specific joint, from the piping system 2 based on the hierarchical information. An example of the specific joint is one joint (designated joint) designated by an operator (administrator, etc.) from among multiple joints included in the piping system 2.

[0171] For example, by utilizing the hierarchical information described above, when a fault occurs in the piping system 2 and the location of the fault is known, it is possible to easily identify the scope of the fault (the route within the scope of the fault) (see FIG. 22).

[0172] In FIG. 22, a situation is assumed in which a fault (such as a water leak) occurs between the joint CAt1 and the joint CAA. The joint CAt1, which is relatively higher than the two, is designated as a reference joint (designated joint). Then, a piping route including joints (CAA, CAB, CAB1) lower in rank than the joint CAt1 (reference joint) in the same hierarchical level as the joint CAt1 and joints (CAAt1-CAAt4, CABt1, CABt2) lower in rank than the joint CAt1 is specified as a route within the affected range. Note that a joint lower in rank than the joint CAt1 in the same hierarchical level as the joint CAt1 is also referred to as a lower-ranked joint in the hierarchical level to which the fault location belongs (or a lower-ranked joint in the same hierarchical level).

[0173] Specifically, the piping data management system 1 first acquires the location of a fault in the piping system 2 through an input from an operator or the like.

[0174] Next, the piping data management system 1 identifies a route within the affected range based on the piping data 200 (particularly the hierarchical information) and the like. In detail, first, it is determined that "the reference joint CAt1 exists in the branch CAt of the third level route" by searching for "CAt1" in the piping data 200 or the like (or based on the hierarchical symbol CAt). Then, based on a data table related to the branch CAt in the third hierarchical data 230, the same level joints (CAA, CAB, CAB1) after the first joint CAt1 of the branch CAt are identified as joints on the lower priority side in the same hierarchical level. In addition, among the joints on the lower priority side in the same hierarchical level, branch joints (CAA, CAB) are identified, and joints belonging to the branch (CAAt, CABt) starting from the branch joint are identified. The joints (CAAt1 to CAAt4, CABt1, CABt2) belonging to the branch (CAAt, CABt) are identified as joints on the lower hierarchical level than the fault position. Specifically, these joints are identified based on a data table 240a relating to the branch CAAt and a data table 240b relating to the branch CABt in the fourth hierarchical data 240 (FIG. 11). If there is a joint on a lower hierarchical level than the joints belonging to these branch flows (CAAt, CABt), the joint on the lower hierarchical level is also identified as a joint on a lower hierarchical level than the fault position.

[0175] Then, the piping route including the joints (CAA, CAB) on the lower-ranking side in the hierarchy to which the fault location belongs and the joints (CAAt1 to CAAt4, CABt1, CABt2) on the lower-ranking side than the fault location are identified as routes within the affected range (routes within the affected range).

[0176] Furthermore, the piping data management system 1 draws (highlights in detail) the route within the affected range on the screen 300 (see FIG. 22). In FIG. 22, the route within the affected range (particularly the pipes) is highlighted by applying diagonal hatching. Note that the highlighting is not limited to the hatched display, and may be other display such as a display with a specific color (display that allows the route within the affected range to be distinguished from other routes (routes other than the route within the affected range)). Furthermore, the "highlighting" of the route within the affected range may be a display that allows the route to be identified. All elements (including joints) within the route within the affected range may be highlighted, or elements (mainly pipes) excluding joints (such as tees and elbows) may be highlighted as shown in FIG. 22.

[0177] According to this embodiment, the range of influence of the failure (path within the range of influence) can be easily specified. In addition, the path within the range of influence is highlighted within the piping route of the piping system 2, so that the range of influence in the entire piping system 2 can be easily grasped.

[0178] <8. Estimation of abnormal paths based on piping data 200> Furthermore, by using the hierarchical information as described above, it is possible to estimate an abnormal route (a route including a location where an abnormality has occurred) for an abnormal terminal instrument (an instrument in which an abnormality has been confirmed). Specifically, when a normal terminal instrument (such as a normal valve) and an abnormal terminal instrument (such as an abnormal valve) in the piping system 2 are specified, it is possible to estimate a normal route for a normal terminal instrument (an instrument confirmed to be normal) and an abnormal route for the abnormal terminal instrument based on the hierarchical information of the piping data 200.

[0179] 23 shows a situation in which, among the terminal instruments (valves) V1 to V8, the valves V5 and V7 are abnormal terminal instruments, the valve V6 is a normal terminal instrument, and the other valves V1 to V4 and V8 are unknown status instruments (instruments whose normality is unknown). More specifically, for example, it is known that the valves V5 and V7 do not dispense water (an abnormality has occurred) and the valve V6 normally supplies water. In this case, the path from the joint CAA via the joint CAB to the valve V5 and the path from the joint CAB via the joint CABt1 to the valve V7 are estimated as abnormal paths (more specifically, paths that may have an abnormality).

[0180] Specifically, the piping data management system 1 first acquires designation information of normal terminal instruments (normal valves, etc.) and abnormal terminal instruments in the piping system 2. For example, the designation information is acquired (accepted) by input by an operator (designation input of an abnormal instrument, etc., using an instrument status input screen). More specifically, the valves V5 and V7 are designated as abnormal instruments, and the valve V6 is designated as a normal instrument.

[0181] Next, the piping data management system 1 estimates a normal route for a normal terminal device based on the hierarchical information of the piping data 200, and estimates an abnormal route for an abnormal terminal device (from a route other than the normal route).

[0182] Specifically, first, a normal route is estimated based on information of a normal terminal device. Since the valve V6 is a normal device, the route from the start point SP to the valve V6 is estimated to be the normal route. More specifically, based on the piping data 200, the route from the valve V6 to the higher-order side (higher-order side) in the same hierarchy and to the higher hierarchy side is identified as the normal route.

[0183] In detail, first, the route from the valve V6 to the branch point CAA is determined to be a normal route based on the data table 240a (data table including the valve V6) related to the branch CAAt in the fourth hierarchical data 240 (see FIG. 11). In detail, in the data table 240a, the route returning from CAAt4 (=V6) at the bottom to CAAt0 (=CAA) at the top via CAAt3-CAAt1 is determined to be normal.

[0184] Next, based on the data table 230b (upstream data table including the branch point CAA) for the branch CAt in the third hierarchical data 230 (see FIG. 10), among the third level routes (branch CAt) which are parent hierarchical routes (one higher hierarchical route) of the branch CAAt, the route from the branch point CAA to the joint CA on the upstream side is also determined to be a normal route. In detail, in the data table 230b, the route from CAA in the third row from the bottom via CAt1 and returning to CAt0 (=CA) in the top row is determined to be normal.

[0185] Furthermore, based on the data table 220c (upstream data table including branch point CA) for the branch Ct in the second hierarchical data 220 (see Figure 9), the second level route (branch Ct), which is the parent hierarchical route of the branch CAt, is also determined to be a normal route, from branch point CA to joint C upstream of it.

[0186] Finally, based on the first hierarchical data 210 (see FIG. 8) (data table of the upstream (main) stream including branch point C), it is determined that the first level route (main) which is the parent hierarchical route of the branch Ct, that is, the route from branch point C to the upstream starting point SP, is also a normal route.

[0187] In this way, the route (see FIG. 5, etc.) from the valve V6 via the branch points CAA, CA, C to (return from) the start point SP is determined to be a normal route. At this time, each of the branch points CAA, CA, C is determined to be a normal point (also simply referred to as a "normal point") at least up to the branch point (up to the upstream route of the branch point), and the determination result is recorded. For example, a flag column indicating whether or not the point is normal may be further provided in each data record of the piping data 200. Then, data "1" (on = normal) is assigned to the flag column of the branch point (specifically, the data record) determined to be a normal point, and data "0" (off) is assigned to the flag column of the other branch points.

[0188] In addition, if there are other normal terminal devices, the route from the other normal terminal devices to the starting point SP is identified as the normal route in a similar manner based on the information of the other normal terminal devices and the piping data 200.

[0189] Next, an abnormal path is estimated based on the information of the abnormal terminal device as well.

[0190] First, an abnormal path estimation process for the valve V5 is executed.

[0191] Since the valve V5 is an abnormal terminal device, it is estimated that an abnormality has occurred on one of the paths returning from the valve V5 to the upstream side (the higher-ranking side and / or the higher hierarchy side). However, it is estimated that no abnormality has occurred on the normal paths among the paths upstream of the abnormal terminal device. In other words, the above-mentioned normal path is excluded (from the abnormal path) and the abnormal path is estimated. The abnormal path estimation process is performed using the piping data 200. Specifically, a "normal point" (mentioned above) is searched for while returning upstream from the abnormal terminal device, and the path from the normal point reached (by the search) to the abnormal terminal device (this time heading in the opposite direction to the downstream side) is estimated as the abnormal path.

[0192] In detail, first, based on the data table 230b related to the branch CAt of the third hierarchical data 230 (see FIG. 10), it is determined that the branch point immediately before the valve V5 (one higher in the order of priority) is the branch point CAB. It is determined that the branch point CAB is not determined to be a normal point (based on the flag field (=off) of the branch point CAB), and the process goes back further upstream from the branch point CAB. Specifically, based on the same data table 230b, it is determined that the branch point immediately before the branch point CAB is the branch point CAA. In the above-mentioned normal route determination process, it is determined that the branch point CAA is a normal point (the route returning from the branch point CAA to the higher side is a normal route). Based on this, the route from the branch point CAA to the valve V5 via the branch point CAB is estimated to be an abnormal route.

[0193] Next, an abnormal path estimation process for the valve V7 is executed.

[0194] Similarly, based on the fact that the valve V7 is an abnormal terminal device, normal paths are excluded from paths returning from the valve V7 to the upstream side, and an abnormal path is estimated. Specifically, a "normal point" (described above) is searched for while returning from the valve V7 to the upstream side, and a path from the normal point reached to the abnormal terminal device is estimated as an abnormal path. In detail, a search process for a normal point is performed based on the data tables 240b and 230b, and a path from the valve V7 to the normal point CAA via the branch point CAB is searched for. Based on the search result, a path from the branch point CAA (normal point) via the branch point CAB (and the non-branch joint CABt1) to the valve V7 is estimated as an abnormal path.

[0195] Thereafter, on screen 300, the path (particularly the pipe) from branch point CAA via branch point CAB to valve V5 and the path (particularly the pipe) from branch point CAA via branch point CAB to valve V7 are drawn (highlighted (e.g., hatched)) as abnormal paths (see FIG. 23). Although not shown in FIG. 23, normal paths may also be highlighted in other types of manners. Note that the highlighting of the abnormal paths (and normal paths) may be done in various manners similar to the highlighting of the paths within the affected range (described above).

[0196] According to such processing, it is possible to determine a normal route for a normal terminal device based on the hierarchical information of the piping data 200, and to accurately estimate an abnormal route for an abnormal terminal device based on information on the normal route (information on normal points). In addition, since the abnormal route etc. related to the determination result is drawn on the piping layout diagram, the operator can easily grasp the abnormal route etc.

[0197] <9. Effects of the embodiment> As described above, the piping data management system 1 manages the data of the piping system 2 by recording in a data table the piping data 200 including type information (such as "T" or "L"), pipe diameter information, position information, and hierarchical information of each joint (pipe joint) in the piping system 2. This makes it possible to manage the piping route of the piping system 2 relatively easily.

[0198] In conventional CAD systems, operations to change CAD data require operations such as drawing a line on the screen. However, in environments such as construction sites, it is not easy to execute operations to change CAD data (operations to change a line). Due to such circumstances, changes to piping routes may not be reflected in the CAD data.

[0199] On the other hand, in the above embodiment, the piping system 2 is managed by the piping data 200 expressed in a relatively simple data table (in short, in a table format). Therefore, it is possible to manage the piping route of the piping system 2 relatively easily. For example, when changing the piping route, it is not necessary to operate a CAD system on-site (redraw a drawing by operating CAD software). Since the change operation on the piping data 200 can be performed relatively easily, the change operation of the piping data 200 can be easily performed even at a construction site. For example, even when the piping route is changed on-site, the change operation of the piping data 200 can be easily performed on-site. Therefore, the change of the piping route is easily reflected appropriately in the piping data 200. In turn, the data of the piping system 2 is easily managed appropriately.

[0200] Moreover, according to the piping data management system 1 in this embodiment, it is possible to manage the data (piping data) of the piping system 2 with a data table having a simple configuration. Therefore, it is possible to manage the data of the piping system relatively easily (easier than the conventional CAD system). For example, the piping data 200 has a small size compared to the CAD data, and is therefore easy to handle. Also, a device (computer) for running software that changes the CAD data requires relatively high CPU performance and drawing performance. In contrast, a device for running an application program that changes the piping data 200 does not require such high CPU performance (a device having lower hardware performance than the CAD system is sufficient). For example, the program (the application program that changes the piping data 200) can be smoothly operated even on a smartphone or a tablet terminal.

[0201] Furthermore, compared to the case where the piping routes of the piping system 2 are grasped based only on a line-drawn piping layout diagram (CAD drawing or the like), it is possible to more easily manage the piping routes of the piping system.

[0202] In particular, in the past, a manager (human) understood the hierarchical structure of a piping system by looking at a drawing drawn by CAD (CAD drawing), etc. Specifically, the manager (human) had to construct the hierarchical structure of the piping system 2 in his or her mind while looking at a piping layout drawing and sequentially tracing the joints (and pipes).

[0203] In contrast, according to the above embodiment, the piping data 200 includes hierarchical information (hierarchical symbol) of each joint of the piping system 2. In other words, the piping data 200 is digitized including the hierarchical structure of the piping route of the piping system 2. The hierarchical information (hierarchical symbol) makes it possible to easily grasp the hierarchical structure of the piping system 2. Therefore, by using the piping data 200, a manager or the like can easily grasp the hierarchical structure of the piping system 2 and manage the piping system 2.

[0204] In particular, by using the above-mentioned piping data 200, partial changes to a piping route (changing the position of a joint, adding and / or deleting a joint, etc.) can be easily realized. If a piping route is drawn only by a CAD system, operations at the time of changing the route are cumbersome. On the other hand, by using the above-mentioned piping data 200, a piping route can be changed relatively easily. Such changes to a piping route can be easily made during construction and / or design of a new building, etc. Also, they can be easily made when renewing a piping route or during maintenance, etc.

[0205] In addition, the hierarchical information of each joint is coded, which makes it possible to easily grasp the hierarchical structure of each joint.

[0206] In particular, the hierarchical information of each joint expresses the hierarchical level by the number of symbol sets (symbol sets represented by a single alphabet in the above embodiment) (simply put, the number of alphabets), which makes it possible to easily grasp the hierarchical level of each joint.

[0207] Moreover, each symbol set indicates a branch point in the flow of each layer. In particular, the order of the alphabet in each symbol set expresses the order of branch joints in the same layer (ith layer). For example, the first (i=1) character "C" in the two-character alphabet (symbol set) "CA" means the third branch point in the first layer (i=1). The second (i=2) character "A" following the character "C" means the first branch point in the lower layer (second layer (i=2)) branched from the branch point C. Therefore, it is possible to easily grasp the route to a certain joint (which branch point is passed through to reach the certain joint).

[0208] Furthermore, a hierarchical symbol consisting of only alphabets is given to a branch joint, and a hierarchical symbol with a number (auxiliary symbol) added to the end is given to a non-branch joint. Therefore, it is possible to easily distinguish between a branch joint and a non-branch joint.

[0209] <10. Modifications, etc.> Although the embodiment of the present invention has been described above, the present invention is not limited to the above-described contents.

[0210] <Display device for piping layout diagram based on piping data 200> For example, in the above embodiments, a configuration has been described in which a piping layout diagram is drawn (displayed) in the management device 10 based on the piping data 200, but this is not limited to this, and a piping layout diagram may be drawn (displayed) in the management server 30 based on the piping data 200.

[0211] <Conversion of piping data 200 to CAD data, etc.> In the above embodiment and the like, the piping layout diagram is displayed (directly) based on the piping data 200, but the present invention is not limited to this. For example, the piping data 200 may be converted into CAD data, and a piping layout diagram (CAD drawing) may be drawn based on the converted CAD data. In other words, the piping data 200 may be converted into data (CAD data) that can be read by a CAD system and is used to draw each joint and a route connecting the joints in the CAD system. Then, a piping layout diagram (CAD drawing) based on the (converted) CAD data may be drawn (displayed) in the CAD system.

[0212] For example, the management device 10 may convert the piping data 200 into CAD data. In particular, the controller 11 may function as a data conversion unit that executes data conversion between the piping data 200 and the CAD data. Here, it is assumed that each joint included in the piping data 200 is registered as a part image (grouped (unitized) as a collection of line drawings) by type in the management device 10.

[0213] Specifically, the management device 10 generates CAD data for drawing the following line diagrams and the like based on the piping data 200. First, the management device 10 acquires type information of a certain joint (a joint of interest) based on the piping data 200, and identifies a part image of the joint corresponding to the type information (for example, a part image of an "elbow"). Then, in the generated CAD data (CAD drawing), the part image (a collection of line diagrams) of the joint is arranged at a position according to the position information of the joint. The orientation of the joint (the orientation of the part image) may be determined (adjusted) according to the extension direction of the pipe connected to the joint. Also, based on the position information of the joint and the pipe diameter information of the joint, a line segment (two line segments spaced apart according to the pipe diameter of the joint, etc.) representing the pipe connected to the joint is arranged at an appropriate position. In the same manner, a plurality of joints and the like (a plurality of joints and a plurality of pipes belonging to a plurality of hierarchical levels) included in the piping data 200 are drawn (toward the lower order side for each hierarchical level). The CAD data for drawing such line diagrams and the like is generated by converting the piping data 200.

[0214] In this manner, after the management device 10 executes the generation process of CAD data based on the piping data 200 (the conversion process to CAD data), the converted CAD data is transmitted from the management device 10 to the management server 30 via the communication network. In response to this, the management server 30 receives (acquires) the CAD data based on the piping data 200.

[0215] Thereafter, the management server 30 visualizes and displays a drawing based on the CAD data (CAD drawing). In detail, the management server 30 draws each joint, a route connecting each joint, and the like using a CAD system.

[0216] According to the above-described processing, the piping system 2 can be easily managed at the site or the like using the piping data 200, and if necessary, a CAD drawing converted from the piping data 200 can be displayed in a CAD system.

[0217] The conversion process to CAD data may be executed by the management device 10 (controller 11, etc.) as described above, but is not limited thereto, and may be executed by, for example, the management server 30 (controller 31, etc.). In other words, the controller 31 may function as a data conversion unit that executes data conversion process between the piping data 200 and the CAD data. Specifically, the original piping data 200 is transmitted from the management device 10 to the management server 30 via a communication network, and the management server 30 acquires the piping data 200. Thereafter, the management server 30 may execute a generation process (conversion process to CAD data) of CAD data (data for a CAD system) based on the piping data 200.

[0218] <Generation process of piping data 200 (generation process using a CAD system)> In the above embodiment, the piping data 200 is generated in response to an operation input by an operator, but is not limited to this. For example, the piping data 200 may be generated based on a CAD drawing (CAD data) depicting the piping system 2.

[0219] Here, it is assumed that software (data conversion software) that generates piping data 200 from CAD data is installed as add-in software (function extension software) of the CAD software in the management server 30. When position information of each joint is already input and exists in the CAD data, the position information of each joint in the CAD data is used. Data that does not exist in the CAD data (for example, joint type information and connection information, etc.) is additionally input by the operator using the function extension software.

[0220] In detail, in the function extension software, the connection information of each joint can be obtained by performing an operation such as tracing each flow (main flow or each branch flow) from the starting point to the end point of the flow.

[0221] Specifically, first, the operator selects "main stream information input" from the menu. After that, with the CAD drawing of the piping system 2 displayed on the operation screen of the CAD system, the operator clicks with the mouse on the reference points of each joint included in the main stream route (start point, one or more joints (specifically, reference points of the joints), and end point (terminal end)) in sequence according to the fluid passing order on the route. This allows information on multiple points belonging to the main stream (start point, via point (reference point of the joint), end point (valve, etc.)). More specifically, the function extension software acquires information on which points (joints, etc.) belong to the main stream, information on the order of the multiple points belonging to the main stream, and position information of each joint. Furthermore, the operator inputs type information and pipe diameter information of the joint as detailed information of each point. The management server 30 automatically generates hierarchical information of each joint in the main stream route based on this information (information on the start point, via point, and end point of the main stream route, and type information of each point (joint) in the main stream route, etc.).

[0222] Next, the operator selects "Diversion information input" from the menu, and then performs the same operation as above. Specifically, the operator clicks on the reference points of each joint included in one diversion path (start point (branch joint), one or more joints (specifically, reference points of the joints), and end point (terminal end)) in sequence according to the order in which the fluid passes on the path. This allows information on multiple points (start point, intermediate point (reference point of the joint), end point (valve, etc.)) belonging to the one diversion path to be acquired. More specifically, the function extension software acquires information on which points (joints, etc.) belong to the one diversion path, information on the order of the multiple points belonging to the one diversion path, and position information of each joint. Furthermore, the operator inputs information on the type of joint and pipe diameter information as detailed information on each point. The management server 30 automatically generates hierarchical information for each joint in the one branch route based on this information (information on the start point, intermediate points, and end point of the one branch route, as well as information on the type of each point (joint) within the one branch route).

[0223] For the other branch paths, the operation by the operator and the processing by the management server 30 are similarly carried out.

[0224] In this manner, the type information, pipe diameter information, position information, and hierarchical information of each joint in the main stream and all the branches are acquired by the management server 30 (its function extension software). Then, the management server 30 generates the piping data 200 based on the acquired information.

[0225] In this manner, the piping data 200 may be generated based on the CAD drawing (CAD data) depicting the piping system 2. The generated piping data 200 may be used in the management device 10 and the management server 30.

[0226] The pipe diameter information of the joint (pipe diameter information of the piping data 200) may be acquired based on CAD data instead of being input by an operator. Specifically, the pipe diameter information of the piping data 200 may be obtained based on the width (pipe diameter) of the pipe drawn in the CAD data (CAD drawing).

[0227] Furthermore, when inputting the type information of the joint, only the branch joint among a plurality of branch joints may be designated as a "branch joint (tee)" (joints that are not designated may be determined to be non-branch joints).

[0228] Alternatively, in the case where the CAD data already has type information of the joint, the type information included in the CAD data may be acquired as the type information of the piping data 200 as it is.

[0229] In addition, the positional relationship of each joint in the CAD data may be automatically read, and the hierarchical structure may be automatically generated. For example, the piping data 200 may be generated by using the position information, type information, and pipe diameter information of each joint included in the CAD data, and automatically acquiring (generating) the connection information of each joint (the mutual positional relationship between a plurality of joints) as follows.

[0230] In detail, it is determined that there exists a route that passes through non-branch joints (elbow, socket) in sequence in the direction in which the pipe extends or bends until a branch joint (tee) appears from the start point of the flow at the same hierarchical level (start point of the main flow or branch (first, start point SP of the main flow)). In other words, until a branch joint appears, a route is basically formed that sequentially connects joints (non-branch joints), and a data table (piping data 200) representing that route is generated. As for the hierarchical information, hierarchical symbols within the same hierarchical route may be generated (assigned) in the same manner as described above.

[0231] When a route branches at a branch joint, a route (flow) in a direction going further straight from the branch joint (towards the next joint along a direction connecting the branch joint and its immediately preceding joint) is automatically determined to be a route in the same hierarchy (a flow at the same level as the level to which the immediately preceding joint belongs). Then, the next joint (of the branch joint) in the same hierarchy route is determined to be a joint of the next order in the same hierarchy. On the other hand, a route (flow) in a non-straight direction (for example, an orthogonal direction perpendicular to the direction connecting the branch joint and its immediately preceding joint) branching from the branch joint is automatically determined to be a lower hierarchy route (a flow at a level one level lower than the level to which the immediately preceding joint belongs). Then, the next joint (of the branch joint) in the lower hierarchy route is determined to be a joint of the next order in the lower hierarchy. In this way, based on the positional relationship of each joint in the CAD data, connection information of each joint in the piping data 200 is acquired.

[0232] Furthermore, based on such a determination result (connection information of each joint), hierarchical information of each joint is generated. For example, hierarchical information (hierarchical symbols) similar to the above may be assigned. In detail, different numbers of symbol sets (alphabet letters) may be assigned to joints in different hierarchical levels, and alphabets (and numbers) (within one symbol set) indicating the order, etc., within the same hierarchical level may be assigned to joints in the same hierarchical level.

[0233] According to the above-described process, the piping data 200 is generated based on a CAD drawing (CAD data) depicting the piping system 2. According to this, in cases where the CAD data already exists, it is not necessary to generate the piping data 200 from scratch, and it is possible to easily generate the piping data 200 by utilizing the existing CAD data. As a result, it is possible to facilitate management using the piping data 200.

[0234] <Hierarchy symbol> In the above embodiment, etc., "t" is given as a symbol representing the 0th branch point in the branch, etc., but this is not limited to this. For example, "A" may be given as a symbol representing the 0th branch point in the branch (see FIG. 24). In detail, "At" in the above embodiment may be changed to "AA", "Bt" may be changed to "BA", and "BA" may be changed to "BB". Also, another symbol (e.g., "#") may be used instead of "t" as a symbol representing the branch. For example, the branch At may be expressed as the branch "A#". Incidentally, "A" may also be given as a symbol representing the 0th branch point in the main stream.

[0235] In the above embodiment, a symbol set with one alphabetical character as a unit (such as "B", "CB", "At", "CAB", etc.) is used, but the present invention is not limited to this. For example, a symbol set with two alphabetical characters, specifically a combination of an uppercase letter and a lowercase letter (such as "Ba", "Cf", "Az", etc.), may be used. Specifically, after 26 characters, Aa, Ba, Ca to Za, are sequentially assigned, Ab, Bb, Cb to Zb, Ac to Zc, ..., As to Zs, At to Zt, Au to Zu, ..., Az to Zz may be sequentially assigned. The rank number of the first character (uppercase alphabet) represents the zeroth power of 26 in base 26, and the rank number of the second character (lowercase alphabet) (to be precise, the alphabetical character rank number - 1) represents the first power of 26 in base 26. In this case, another symbol (for example, "#") may be used instead of "t" as the symbol representing the branch.

[0236] For example, "Cf7", "CfAcBa8", etc. may be assigned as the hierarchy symbols of the joints.

[0237] "Cf7" is composed of one symbol set ("Cf") and an auxiliary symbol "7". "Cf" indicates the 133rd (=26*5+3) branch joint (branch point) in the first level path, and "Cf7" indicates that it is the seventh non-branch joint from the branch joint Cf in the first level path.

[0238] Similarly, "CfAcBa8" is composed of three symbol sets ("Cf" + "Ac" + "Ba") and the auxiliary symbol "8" combined. "CfAc" indicates the 53rd (=26*2+1) (Ac) branch joint (branch point) in the "second level route" (Cf#) branched from the 133rd branch point Cf in the first level route. "CfAcBa" indicates the second (Ba) branch joint (branch point) in the "third level route" (CfAc#) branched from the branch joint CfAc. "CfAcBa8" indicates that it is the 8th non-branch joint from the branch joint CfAcBa in the third level route (CfAca#). In this case, the number of symbol sets also represents the hierarchical level, and the order in each symbol set (the order of the combination of two alphabets) represents the order in the same hierarchy.

[0239] A symbol set based on a single alphabetic character can accommodate up to 26 branching points, whereas a symbol set based on two alphabetic characters can accommodate many more branching points (for example, 676 = 26 x 26).

[0240] Furthermore, a symbol set having a unit of a predetermined number of three or more alphabetical letters may be used.

[0241] Also, in the case where a symbol set is used with a combination of uppercase and lowercase letters (such as "Ba", "Cf", and "Az") as a unit, first, uppercase letters (A to Z) may be sequentially added, and then combinations of uppercase and lowercase letters (Aa to Za, Ab to Zb, ..., Zz) may be sequentially added. In other words, the symbol set may be such that the first through twenty-sixth characters are represented by one alphabetical character, and the twenty-seventh and subsequent characters are represented by two alphabetical characters (Aa to Za, Ab to Zb, ..., Zz). Furthermore, the symbol set may be such that the third and subsequent characters are sequentially added ("A" to "Z", "Aa" to "Zz", "Aaa to Zzz").

[0242] In the above embodiment, an "alphabet" is added to the end of the hierarchy symbol for a branch joint (branch point), and a "number" is added to the end of the hierarchy symbol for a non-branch joint (non-branch point), but the present invention is not limited to this. For example, the hierarchy symbol may be a symbol in which a number indicating the order (sequence) from the upstream is added to a joint (whether it is a branch joint or a non-branch joint) in the same hierarchy. This makes it easy to understand the order in the same hierarchy. In addition, for a branch joint, an "alphabet" that indicates that it is a branch joint and distinguishes branch joints in the same hierarchy from each other may be added immediately after the number. In other words, the symbol set may be composed of numbers (only numbers) or a combination of numbers and alphabets.

[0243] For example, as shown in FIG. 25, the joints in the first level path may be assigned hierarchical symbols such as "1A", "2", "3", "4B", "5", "6C", .... The alphabet at the end indicates that it is a branch point (branch joint) (and the order of branch joints in the same hierarchy). Similarly, the joints in the second level path may be assigned hierarchical symbols such as "1A1", "1A2", "1A3", ..., "4B1", "4B2", "4B3A", ..., "6C1", "6C2", "6C3A", .... The joints in the third level path may be assigned hierarchical symbols such as "4B3A1", "4B3A2", ..., "6C3A1", "6C3A2A", .... In this case, the number of numbers represents the number of symbol sets (and thus the hierarchical level). For example, "4B1" (number of digits = 2) represents the second level, and "6C5B1" (number of digits = 3) represents the third level.

[0244] In this way, the hierarchical information may be encoded using a single or multiple symbol sets comprising numbers (and letters). In this case, the number of the symbol sets (symbol sets comprising at least one of numbers and letters) represents the hierarchical level. Furthermore, the order within each symbol set represents the order within the same hierarchy. More specifically, the order of the numbers within each symbol set (e.g., 1, 2, 3, ...) represents the order of the joints within the same hierarchy, and the order of the alphabets (letter order) within each symbol set represents the order of the branch joints within the same hierarchy.

[0245] With this representation, especially when there are many joints in the same route, the order (sequence) of each joint in the same route can be easily understood by the "number." For example, the hierarchy symbol "156G" can be easily understood to mean the 156th joint in the main stream (and the 7th branch joint in the main stream).

[0246] It is possible to express hierarchical information only with alphabets obtained by removing numbers (except for the last digit) from the hierarchical symbol (see FIG. 25) in the modified example. For example, "CAA" obtained by removing numbers from "6C3A2A" represents the first branch point ("A") of a specific third level route (CA#). The specific third level route CA# is a route branched at point A in a second level route (C) which branches at point C in a first level route. Also, "CAA3" obtained by removing numbers other than the last digit from "6C3A2A3" means the third joint of a fourth level route (CAA#) branched from the first branch point ("A" (=CAA)) in a specific third level route (CA#). In this case, the total value of the number of alphabets and the number of numbers (the number of symbol sets consisting of either alphabets or numbers) represents the number of symbol sets (and thus the hierarchical level). For example, "CAA" (the sum value=3) represents the third level, and "CAA3" (the sum value=4) represents the fourth level.

[0247] Also, in the above embodiment (see FIG. 5, etc.), the symbol sets are mainly expressed by alphabets (letters) and the auxiliary symbols are expressed by numbers, but this is not limited to this. For example, conversely, the symbol sets may be mainly expressed by numbers and the auxiliary symbols may be expressed by alphabets (letters). When multiple symbol sets are consecutive (as a combination of numbers), a separator (such as " / " or "-") may be provided between the multiple symbol sets (multiple numbers). For example, "CBt1" (FIG. 5) in the above embodiment may be expressed as "3-2-0A".

[0248] In addition, in the above embodiments, the characters in the symbol set are not limited to alphabets, but may be Greek letters, Hiragana, Katakana, etc. Furthermore, the numbers in the symbol set are not limited to Arabic numerals, but may be Roman numerals, Chinese numerals, etc.

[0249] <Other> In the above embodiment, information on the joint "immediately before" each joint is acquired as the connection order between adjacent joints, but this is not limited to this. For example, information on the joint "immediately after" each joint may be acquired as (information on) the connection order between adjacent joints.

[0250] In the above embodiment, the pipe diameter information is also recorded in the piping data 200. By using the pipe diameter information in the piping data 200, it is possible to appropriately manage the diameter of the pipe to be used for piping. For example, based on the position information and pipe diameter information of each joint in the piping data 200, it is possible to appropriately calculate the length and pipe diameter of the pipe connecting each joint to the joint at the connection destination, and it is also possible to appropriately draw the pipe diameter in the piping layout diagram. However, it is not limited to this, and in cases where management of the pipe diameter is not required (for example, when only the position of the piping route is required to be known), the piping data 200 does not need to have the pipe diameter information.

[0251] Furthermore, in cases where pipe diameter information is not required, information on pipe diameter changing joints that are not branch joints (for example, reduced diameter sockets (and reduced diameter elbows)) is not necessarily required.

[0252] In the above embodiment, the piping system 2 has been mainly described as a water supply piping system, but is not limited thereto. For example, the piping system 2 may be a drainage piping system, an air conditioning piping system, a gas piping system, or the like. The fluid flowing through the piping may be a liquid other than water (oil, etc.), or may be a gas such as gas.

[0253] In the above embodiment, the main stream gradually branches into the tributaries (from the upper layer to the lower layer) in the water supply piping system, but the present invention is not limited to this. For example, the main stream may gradually merge into the tributaries (from the lower layer to the upper layer) in the drainage piping system. In this case, the direction of the fluid flow is reversed, but the same idea as above may be applied to the hierarchical information.

[0254] In the above embodiment, the piping data management system 1 includes the management device 10 and the management server 30, but is not limited thereto. For example, the management device 10 may include the above-mentioned various functions of the management server 30, and the piping data management system 1 may be configured by only the management device 10. [Explanation of symbols]

[0255] 1 Piping Data Management System 2 Piping System 3 Pipes 5,501 fittings 10 Management device 30 Management Server 200 Piping Data 320 Dialogue 330 Subdialog SP starting point V1~V8 valves

Claims

1. A control means for managing data of the piping system by recording piping data including type information, position information, and hierarchical information of each joint in the piping system in a data table; A piping data management system comprising:

2. In the piping data management system according to claim 1, A piping data management system characterized in that the hierarchical information is symbolized using a single or multiple symbol sets, and the number of the symbol sets represents the hierarchical level.

3. In the piping data management system according to claim 2, A piping data management system characterized in that the hierarchical information is symbolized using a single or multiple symbol sets composed of characters, and the order of characters in each symbol set represents the order of branch fittings within the same hierarchy.

4. In the piping data management system according to claim 3, A piping data management system characterized in that the hierarchical information of a non-branched fitting is symbolized by adding an auxiliary symbol composed of a different type of symbol from the characters used in the symbol set to the hierarchical information of the branch fitting immediately preceding the non-branched fitting, and the information represents the order from the immediately preceding branch fitting by the order of the auxiliary symbols.

5. In the piping data management system according to claim 2, A piping data management system characterized in that the hierarchical information is symbolized using a single or multiple symbol sets composed of numbers, and the ranking of the numbers in each symbol set represents the ranking of fittings within the same hierarchy.

6. In the piping data management system according to claim 1, an acquisition means for acquiring the type information and the position information of each of the joints, and connection information indicating a connection relationship of each of the joints; Further equipped with a piping data management system characterized in that the control means generates the hierarchical information based on the connection information and the type information of each of the fittings, and records the hierarchical information, the type information, and the position information in the data table.

7. 7. The piping data management system according to claim 6, A piping data management system characterized in that the control means determines whether each of the fittings is a branch fitting and whether the fitting immediately preceding each of the fittings belongs to the same hierarchy as each of the fittings based on the type information and the connection information, and generates the hierarchical information of each of the fittings in accordance with the determination result.

8. 7. The piping data management system according to claim 6, A piping data management system characterized in that the acquisition means acquires the position information of each of the joints in the piping data based on the position of each of the joints in the CAD data of the piping system, and acquires the connection information of each of the joints based on the positional relationship of each of the joints in the CAD data.

9. In the piping data management system according to claim 1, A piping data management system characterized in that, when one of a plurality of fittings included in the piping system is specified, the control means identifies a piping route in the piping system based on the hierarchical information, the piping route including a fitting lower in rank within the hierarchy to which the specified fitting belongs, and a fitting lower in rank than the specified fitting.

10. In the piping data management system according to claim 1, A piping data management system characterized in that, when the location of a fault in the piping system is known, the control means identifies, based on the hierarchical information, a piping route that includes a joint on a lower level in the hierarchy to which the fault location belongs and a joint on a lower level than the fault location, as a route within the affected range.

11. In the piping data management system according to claim 1, A piping data management system characterized in that, when normal terminal instruments and abnormal terminal instruments in the piping system are specified, the control means estimates a normal route for the normal terminal instrument based on the hierarchical information, and also estimates an abnormal route for the abnormal terminal instrument based on the normal route.

12. a) recording piping data including type information, position information, and hierarchical information of each joint in the piping system in a data table; A piping data management method comprising:

13. The piping data management method according to claim 12, A piping data management method, characterized in that the hierarchical information is symbolized using a single or multiple symbol sets, and the number of the symbol sets represents the hierarchical level.

14. The piping data management method according to claim 13, A piping data management method characterized in that the hierarchical information is symbolized using a single or multiple symbol sets composed of characters, and the order of characters in each symbol set represents the order of branch fittings within the same hierarchy.

15. The piping data management method according to claim 14, A piping data management method characterized in that the hierarchical information of a non-branched fitting is symbolized by adding an auxiliary symbol composed of a different type of symbol from the characters used in the symbol set to the hierarchical information of the branch fitting immediately preceding the non-branched fitting, and the information represents the order from the immediately preceding branch fitting by the order of the auxiliary symbols.

16. The piping data management method according to claim 12, A piping data management method characterized in that the hierarchical information is symbolized using a single or multiple symbol sets composed of numbers, and the ranking of fittings within the same hierarchy is expressed by the ranking of numbers in each symbol set.

17. The piping data management method according to claim 12, b) acquiring the type information and the position information of each of the joints, and connection information indicating a connection relationship of each of the joints; Further equipped with The step a) comprises: a-1) generating the hierarchical information based on the connection information and the type information of each of the joints; a-2) recording the hierarchical information, the type information, and the position information in the data table; A piping data management method comprising:

18. The piping data management method according to claim 17, In the step a-1), it is determined based on the type information and the connection information whether each of the joints is a branch joint and whether a joint immediately preceding each of the joints belongs to the same hierarchical level as each of the joints, and the hierarchical information of each of the joints is generated according to a result of the determination.

19. The piping data management method according to claim 17, The step b) comprises: b-1) acquiring the position information of each of the joints in the piping data based on the position of each of the joints in the CAD data of the piping system; b-2) acquiring the connection information of each of the joints based on a positional relationship of each of the joints in the CAD data; A piping data management method comprising:

20. The piping data management method according to claim 12, c) when one of a plurality of fittings included in the piping system is designated, a piping route including a fitting lower in rank within a hierarchy to which the designated fitting belongs, and a fitting lower in rank than the designated fitting, is identified in the piping system based on the hierarchical information; The piping data management method further comprising:

21. The piping data management method according to claim 12, d) when the location of the fault in the piping system is known, a step of identifying a piping route including a joint on a lower level in the hierarchy to which the fault location belongs and a joint on a lower level than the fault location as a route within an affected range based on the hierarchical information; The piping data management method further comprising:

22. The piping data management method according to claim 12, e) accepting designations of normal and abnormal terminal devices in the piping system; f) estimating a normal route for the normal terminal device based on the hierarchical information, and estimating an abnormal route for the abnormal terminal device based on the normal route; The piping data management method further comprising:

23. a) acquiring piping data including type information, position information, and hierarchical information of each joint in a piping system; b) converting the piping data into data for a CAD system, and drawing each of the joints and a path connecting the joints in the CAD system; A piping data management method comprising:

24. A program for causing a computer to execute the piping data management method according to any one of claims 12 to 23.

Images