Component information management system, management device, and management program

Abstract

To provide a member information management system, management device, and management program capable of improving convenience upon setting standards.SOLUTION: A member information management system comprises a basic database 111 in which a plurality of standards are set as items for the attributes of building members and a plurality of attributes are associated. The basic database 111 records, as the relation of the standards between the attributes, grades in which the degree of recommendation of availability of setting as a member is divided into a plurality of stages. It is possible to set a related member database 112 which associates a plurality of attributes having, as items, a plurality of standards of related members set in relation to the installation of members serving as foundations recorded in the basic database 111. The related member database 112 is prohibited from setting a grade at a recommendation degree higher than a grade set for a base member. It is also possible to set, in a sub member database 113, information on sub-members used for the configuration of the members recorded in the basic database 111.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a component information management system, a management device, and a management program for managing information related to construction components. [Background technology]

[0002] The applicant of the present application has disclosed a design support system for managing components for which standards are set for various attributes, as described in Patent Document 1. In order to utilize such a system, for example, when commercializing a new architectural component such as a sash, setting standards for various attributes such as length and width, wind pressure resistance, etc. is considered. [Prior art documents] [Patent documents]

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

[0004] When using a system for managing components such as that disclosed in Patent Document 1, it becomes necessary to set various standards for the components.

[0005] The present invention has been made in view of the above circumstances, and has as its main object to provide a component information management system that supports the setting of information relating to components.

[0006] Another object of the present invention is to provide a management device for use in the member information management system according to the present invention.

[0007] A further object of the present invention is to provide a management program for realizing the management device according to the present invention. [Means for solving the problem]

[0008] In order to solve the above problems, the component information management system disclosed in the present application is provided with a basic database in which multiple standards are listed as items for the attributes of building components and the multiple attributes are associated with each other, and the basic database is characterized in that it records, as the standard relationship between each attribute, a class that classifies into multiple stages the degree of recommendation for whether or not a component can be set.

[0009] In addition, in the component information management system, the component is a sash, the attributes include the vertical length standard and the horizontal length standard of the sash, and the classes include "already set," "can be set," and "cannot be set."

[0010] In the member information management system, the attributes further include an interior color and an exterior color of a sash.

[0011] The component information management system further comprises a related component database in which multiple attributes having multiple standards of related components as items that are set in relation to the installation of underlying components recorded in the basic database are associated with each other, and a management device for managing the basic database and the related component database, wherein the related component database has, for related components, related attributes of items similar to those of the underlying components and independent attributes different from those of the underlying components set as attributes, and the management device comprises a means for accepting settings of standard relationships between the related attributes in the related component database, and a means for prohibiting the setting if the accepted setting is of a higher recommendation level than the level set for the underlying components.

[0012] In the component information management system, the base component is a sash, and the related component is a picture frame.

[0013] The component information management system further comprises a child component database in which multiple child attributes each having a multiple specifications of a child component used in the configuration of a parent component recorded in the basic database are associated with each other, and a management device for managing the basic database and the child component database, wherein the child component database is capable of setting child attributes of the same items as those of a parent component as attributes for the child components, and the management device comprises a means for accepting the settings of child components used in the configuration of a parent component recorded in the basic database by specifying the attributes, and a means for setting, for the child attributes among the accepted attributes, a rank similar to that of the attributes of the parent component.

[0014] In the component information management system, the parent component is a sash.

[0015] Furthermore, the management device disclosed in the present application is a management device that manages a database that records information about building components, and is equipped with a means for accessing a basic database in which a plurality of standards are set as items for the attributes of building components and the plurality of attributes are associated with each other, and the basic database records a plurality of levels of recommendation for whether or not to set the components as components as the standard relationship between each attribute, and is equipped with a means for accessing a related component database in which a plurality of attributes having a plurality of standards as items of related components to be set in relation to the installation of foundation components recorded in the basic database are associated with each other, and the related component database is set for related components with related attributes of the same items as the foundation components and independent attributes different from the foundation components as attributes, and is further characterized in that it is equipped with a means for accepting settings of standard relationships between the related attributes in the related component database, and a means for prohibiting setting if the accepted setting is of a higher recommendation level than the level set for the foundation components.

[0016] Furthermore, the management device disclosed in the present application is a management device that manages a database that records information regarding building components, and is equipped with a means for accessing a basic database in which multiple standards are items for the attributes of building components and multiple attributes are associated with each other, and the basic database records a class that classifies the degree of recommendation for whether or not to set the component as a component into multiple stages as the standard relationship between each attribute, and is equipped with a means for accessing a child component database in which multiple child attributes having multiple standards as items for child components used in the configuration of parent components recorded in the basic database are associated with each other, and the child component database is capable of setting child attributes with the same items as those of the parent components and independent attributes different from those of the parent components as attributes for child components, and is further characterized in that it is equipped with a means for accepting settings for child components used in the configuration of parent components recorded in the basic database by specifying attributes, and a means for setting the same class as the attributes of the parent components for the child attributes among the accepted attributes.

[0017] Furthermore, the management program disclosed in the present application is a management program executable on a computer having a means for accessing a basic database in which attributes of building components are classified into items of multiple standards and associated with the multiple attributes, and a means for accessing a related component database in which attributes having items of multiple standards of related components to be set in relation to the installation of foundation components recorded in the basic database are associated with each other, wherein the basic database records classes in which the recommendation level for whether or not to set the related components as components is classified into multiple stages as the standard relationship between each attribute, and the related component database sets, for the related components, related attributes of items similar to those of the foundation components and independent attributes different from those of the foundation components as attributes, and the computer is caused to execute a step of accepting a setting of the standard relationship between the related attributes in the related component database, and a step of prohibiting the setting if the accepted setting is of a higher recommendation level than the class set for the foundation components.

[0018] Furthermore, the management program disclosed in the present application is a management program executable on a computer having a means for accessing a basic database in which attributes of architectural components are classified into a plurality of standards and associated with the plurality of attributes, and a means for accessing a child component database in which child attributes having a plurality of standards as items of child components used in the construction of parent components recorded in the basic database are associated with the plurality of attributes, the basic database records a class that classifies into a plurality of stages the degree of recommendation for whether or not to set the component as a standard relationship between each attribute, and the child component database allows child attributes of the same items as those of the parent components and independent attributes different from those of the parent components to be set as attributes for the child components, and is characterized in that the computer is caused to execute a step of accepting the settings of child components used in the construction of parent components recorded in the basic database by specifying the attributes, and a step of setting the same class as the attributes of the parent components for the child attributes among the accepted attributes. Effect of the Invention

[0019] The present invention records in a basic database that associates multiple attributes, each of which has multiple standards for building materials, a multiple-level classification of the recommended degree of suitability for setting the material as a standard relationship between each attribute. This provides excellent effects, such as improving the convenience of setting standards. [Brief description of the drawings]

[0020] [Figure 1] FIG. 1 is an explanatory diagram showing an example of an overview of a member information management system disclosed in the present application. [Diagram 2] 1 is a block diagram conceptually illustrating an example of the configuration of a management device and a terminal device described in the present application. [Diagram 3] 1 is an explanatory diagram conceptually illustrating an example of a basic database accessible by a management device used in a member information management system disclosed in the present application; [Figure 4]1 is an explanatory diagram conceptually illustrating an example of a basic database accessible by a management device used in a member information management system disclosed in the present application; [Diagram 5] 1 is an explanatory diagram conceptually illustrating an example of a related component database accessible by a management device used in the component information management system disclosed in the present application; [Figure 6] 1 is an explanatory diagram conceptually illustrating an example of a related component database accessible by a management device used in the component information management system disclosed in the present application; [Figure 7] 1 is an explanatory diagram conceptually illustrating an example of a relationship between a basic database and a child component database accessible by a management device used in the component information relating system disclosed in the present application. [Figure 8] 11 is a flowchart illustrating an example of a related member information setting process of the management device disclosed in the present application. [Figure 9] 13 is a flowchart illustrating an example of a child component database setting process of the management device disclosed in the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following embodiments of the present invention will be described in detail. Note that the following embodiments are merely examples of the present invention and are not intended to limit the technical scope of the present invention.

[0022] <Application Examples> The component information management system disclosed in the present application is used, for example, for tasks such as setting standards for newly manufactured building components.

[0023] <System configuration example> FIG. 1 is an explanatory diagram showing an example of the outline of the component information management system disclosed in the present application. The component information management system disclosed in the present application is a system including a management device 1 using a computer such as a server computer. The management device 1 can access various databases such as a basic database 111, a related component database 112, and a child component database 113, and is used to manage data related to building components recorded in the various databases. The management device 1 is connected to a communication network NW such as the Internet, a wide area network (WAN), a local area network (LAN), or other dedicated communication network. A terminal device 2 using a computer such as a notebook computer or a desktop computer is connected to the communication network NW, and the terminal device 2 can access the management device 1 via the communication network NW. An operator uses the terminal device 2 to perform tasks such as setting standards for building components to be newly commercialized.

[0024] <Hardware configuration of various devices> Next, the configuration of each device used in the member information management system will be described. Fig. 2 is a block diagram conceptually showing an example of the configuration of the management device 1 and the terminal device 2 described in the present application.

[0025] The management device 1 used in the member information management system includes various components such as a control unit 10, a recording unit 11, and a communication unit 12. In this embodiment, an embodiment in which the management device 1 is configured using one computer will be described, but the management device 1 may be configured by linking a plurality of computers.

[0026] The control unit 10 includes various circuits such as an information processing circuit, a clock circuit, and a register circuit, and is a processor such as a CPU (Central Processing Unit) that executes processes for controlling the entire device.

[0027] The recording unit 11 is a recording device configured using a non-volatile memory such as a hard disk, an SSD (Solid State Drive), a RAID (Redundant Arrays of Inexpensive Disks), a flash memory, and various volatile memories such as RAM (Random Access Memory). The recording unit 11 records programs such as a basic program (OS: Operating System) and an application program (application program) that runs on the basic program. As one of the application programs, the recording unit 11 records a management program 110 for realizing the management device 1. A computer such as a server computer executes the management program 110 recorded in the recording unit 11 under the control of the control unit 10, thereby functioning as the management device 1 disclosed in the present application. Furthermore, a part of the recording area of ​​the recording unit 11 is used as various databases such as a basic database 111, a related component database 112, and a child component database 113.

[0028] The communication unit 12 is a communication device such as a communication adapter and a control circuit that is connected to the communication network NW and communicates with other devices via the communication network NW.

[0029] The various databases recorded in the recording unit 11 will be described below. The basic database 111 is a database in which a plurality of attributes, each of which has a plurality of standards for building materials as items, are associated with one another. The basic database 111 records a plurality of classes of recommended levels for the suitability of setting a material as a standard relationship between each attribute.

[0030] FIG. 3 is an explanatory diagram conceptually illustrating an example of a basic database 111 accessible by the management device 1 used in the component information management system disclosed in the present application. FIG. 3 illustrates an example of the basic database 111 that records information about sashes as building components. The basic database 111 illustrated in FIG. 3 records information such as attributes related to sashes as building components and standards set for the attributes in a two-dimensional table format. In the basic database 111 illustrated in FIG. 3, attributes such as the horizontal length of the sash are set in the row direction (horizontal direction), and attributes such as the vertical length of the sash are set in the column direction (vertical direction). The attributes related to the horizontal direction of the sash include items such as standards indicating the horizontal length of the sash, such as "1N", "1.25N", "1.5N", and "2N", and standards related to the installation location, such as "standard", "left inside corner", "right inside corner", and "both inside corners". The attributes related to the vertical direction of the sash include items such as a standard indicating the vertical length of the sash indicated by symbols such as "C", "T", "D", and "PS", and a standard of the vertical direction of the sash indicated by a predetermined code string (indicated by numbers in the figure). In the basic database 111 illustrated in FIG. 3, the relationship between the standards of each attribute is recorded as a three-level classification of the recommended degree of setting, namely, "◎", "○", no mark, or "×". The recommended degree indicated by "◎" indicates that the standard has already been set and is the highest recommended degree. The recommended degree indicated by "○" indicates that the standard can be set and is the second highest recommended degree after "◎". The recommended degree indicated by no mark indicates that the product is a custom-made product and is the second highest recommended degree after "○". The recommended degree indicated by "×" indicates that the standard cannot be set and is the lowest recommended degree.

[0031] FIG. 4 is an explanatory diagram conceptually showing an example of a basic database 111 accessible by the management device 1 used in the component information management system disclosed in the present application. FIG. 4 shows an example of another basic database 111, and the basic database 111 illustrated in FIG. 4 records information on color as an attribute related to a sash, which is a building component, in a two-dimensional table format. In the basic database 111 illustrated in FIG. 4, attributes related to the exterior color of the sash, such as "soft black," "mild stain," and "silky white," are set in the row direction. In addition, in the basic database 111, attributes related to the interior color, such as "white," "clear," "gray," and "deep," are set in the column direction. Note that the "virtual color" is dummy data used when setting standards. The basic database 111 illustrated in FIG. 4 also shows the same recommendation level as the basic database 111 illustrated in FIG. 3.

[0032] As the basic database 111 accessible by the management device 1, in addition to those shown in Figs. 3 and 4, it is possible to set a basic database 111 that records information on various attributes such as the degree of wind pressure resistance, whether or not argon gas is contained, etc. In addition, in these basic databases 111, information such as a symbol indicating the degree of wind pressure resistance and a symbol indicating whether or not argon gas is contained is set, rather than the recommended degree indicated by "◎", "○", no mark, or "×". In addition, the basic database 111 is not limited to the two-dimensional table format exemplified in Figs. 3 and 4, but can also be set in a one-dimensional or three-dimensional or more table format. In addition, for example, the two-dimensional table format basic database 111 exemplified in Fig. 3 can also be set as two basic databases 111, one in which information on standards related to the horizontal direction only is recorded, and one in which information on attributes of standards related to the vertical direction only is recorded. For example, when a building material is developed as a new product, one or more basic databases 111 are set for various attributes of the material, and the standards (grades) related to the material are managed.

[0033] The related component database 112 is a database that associates a plurality of attributes having, as items, a plurality of standards of related components that are set in relation to the installation of the foundation components recorded in the basic database 111. In the related component database 112, for the related components, related attributes of items similar to those of the foundation components and independent attributes different from those of the foundation components are set as attributes.

[0034] FIG. 5 is an explanatory diagram conceptually illustrating an example of the related component database 112 accessible by the management device 1 used in the component information management system disclosed in the present application. FIG. 5 illustrates an example of the related component database 112 that records information on frames as related components for sashes that are basic components. FIG. 5 illustrates information on related attributes that are items similar to sashes recorded in the basic database 111 of the related component database 112 in a two-dimensional table format. The related component database 112 illustrated in FIG. 5 illustrates related attributes that are items similar to sashes. In the related component database 112 illustrated in FIG. 5, a plurality of standards related to the horizontal direction are set as items in the row direction, and a plurality of standards related to the vertical direction of the sash are set as items in the column direction. Note that the recommendation level for the related attributes in the related component database 112 cannot be set to a higher recommendation level than the level set for the basic component. For example, for an item for which "◎" is set in the basic database 111, "◎", "○", no mark, or "×" can be set in the related component database 112. Furthermore, for items that have been marked with "○" in the basic database 111, it is possible to mark them with "○", no mark, or "×" in the related parts database 112, but it is not possible to mark them with the highly recommended "◎".

[0035] Fig. 6 is an explanatory diagram conceptually showing an example of the related component database 112 accessible by the management device 1 used in the component information management system disclosed in the present application. Fig. 6 shows an example of the related component database 112 that records information on frames as related components for a base sash. Fig. 6 shows information on independent attributes that are items different from sashes recorded in the basic database 111 in the related component database 112. In the related component database 112 shown in Fig. 6, independent attributes such as "room / sliding (two panels)", "room / sliding consideration", "aluminum-resin composite sash / non-fireproof / normal", and "highly insulated aluminum-resin composite sash / non-fireproof / vacuum" are set, and a recommendation level for each independent attribute is set.

[0036] The child component database 113 is a database in which multiple child attributes having, as items, multiple specifications of child components used in the configuration of parent components recorded in the basic database 111 are associated with each other. The child component database 113 is capable of setting, as attributes, child attributes of the same items as those of the parent components for the child components.

[0037] FIG. 7 is an explanatory diagram conceptually illustrating an example of the relationship between the basic database 111 and the child component database 113 accessible by the management device 1 used in the component information related system disclosed in the present application. As shown in FIG. 7, when information on a sash is set as a parent component in the basic database 111, information on components such as "frame + shoji + glass," "screen door," and "frame L cover" used in the configuration of the sash is set in the child component database 113. It is also possible to set hierarchically, such as setting "frame + shoji + glass" as the basic database 111 and setting the child component database 113 for "frame." FIG. 7 shows the relationship between attributes set as standards in the basic database 111 and child attributes inherited by child components. In the parent components set in the basic database 111, attributes indicating the classification and specifications as a sash are set as items in addition to attributes such as length and color described using FIG. 3 to FIG. 5. For each of these items, whether or not it can be used as a child attribute set in the child components is set. In the figure, items marked with an "O" are items that are set as child attributes of child components, and items marked with an "X" are items that are not set for child components. For example, a "frame + shoji + glass" set as a child component inherits settings for attributes such as house style, sash type, ..., exterior color, and interior color. Also, for example, a "screen door" set as a child component inherits settings for attributes such as house style and sash type, but does not inherit settings for attributes such as fireproofing specifications. Also, items set as child attributes are set to the same rank as the attributes of the parent component.

[0038] As described above, the management device 1 can access various databases such as the basic database 111, the related component database 112, and the child component database 113. In addition, the various databases such as the basic database 111, the related component database 112, and the child component database 113 are not set only once, but a plurality of databases are set for each component. In addition, these databases can be set hierarchically in a plurality of databases, and can be deployed in various configurations. In this embodiment, the management device 1 sets various databases in the recording unit 11 and accesses them from the control unit 10, but can be deployed in various configurations. For example, it is also possible to use a computer such as a database server outside the management device 1 as a recording device, set various databases in the recording device, and access them appropriately from the management device 1 to perform processing such as recording and reading information.

[0039] Returning to FIG. 2, the terminal device 2 used in the member information management system includes various components such as a control unit 20, a recording unit 21, an input unit 22, a display unit 23, and a communication unit 24.

[0040] The control unit 20 is a processor such as a CPU that controls the entire device.

[0041] The recording unit 21 is a recording device configured using a non-volatile memory and a volatile memory, and stores programs such as a basic program and an application program.

[0042] The input unit 22 is an input device such as a keyboard, a mouse, a touch panel, etc. that accepts operations by a user. The display unit 23 is an output device such as a liquid crystal display that displays images.

[0043] The communication unit 24 is a communication device such as a communication adapter for wired communication or an antenna for wireless communication and its control circuit.

[0044] <Device software processing> Next, the processing of various devices used in the component information management system will be described. Fig. 8 is a flowchart showing an example of related component information setting processing of the management device 1 disclosed in the present application. The related component information setting processing is processing for recording the settings of related components in the related component database 112.

[0045] An operator who operates the terminal device 2 operates the terminal device 2 to perform a setting operation of the related parts. The terminal device 2, which has accepted the operation of the operator, accesses the management device 1 and sets the related parts based on the accepted input content. Here, an example will be described in which, as the setting of the related parts, a part such as a sash set in the basic database 111 is designated as a basic part, and the attributes and recommendation level of the related parts related to the basic parts are input to set up the related parts database 112 in which information related to the related parts is recorded.

[0046] The control unit 10 included in the management device 1 executes the management program 110 recorded in the recording unit 11 to perform related component information setting processing. The control unit 10 of the management device 1 that has received access from the terminal device 2 receives a designation of a basic database 111 from the terminal device 2 (S101), and receives designation of attributes that are set in the designated basic database 111 and are also to be set in the related component database 112 as designation of related attributes (S102). Furthermore, the control unit 10 receives setting of independent attributes that are different from the attributes set in the basic database 111 (S103).

[0047] The control unit 10 takes over the related attributes specified in step S102 from among the attributes set in the basic database 111 specified in step S101, and sets the related component database 112 in which the independent attributes set in step S102 are set (S104). In the attribute items that have been taken over as related attributes, similar information, for example, information such as a recommendation level class such as "◎", "◯", no mark, or "×", is set.

[0048] The operator operates the terminal device 2 to specify an attribute item set in the related component database 112 and input settings for the specified item.

[0049] The control unit 10 of the management device 1 accepts the designation of an item and the input of settings for the designated item from the terminal device 2 (S105). The control unit 10 determines whether the designated item is an item for a related attribute (S106).

[0050] In step S106, when it is determined that the item is about a related attribute (S106: YES), the control unit 10 determines whether or not the input setting is higher than the rank set for the underlying component (S107). In step S107, for example, for an item for which "○" is set for the underlying component recorded in the basic database 111, it is determined whether "◎", which indicates a recommendation level rank higher than "○", has been input. If "○", no mark, or "×" has been input, it is determined that the rank is not higher than (is equal to or lower than) the rank set for the underlying component.

[0051] In step S107, if it is determined that the inputted setting is higher than the rank set for the underlying component (S107: YES), the control unit 10 prohibits the setting with the inputted content (S108), returns to step S105, and repeats the subsequent processes. In step S108, the control unit 10 transmits information such as the reason for prohibiting the setting, together with the prohibition of the setting, from the communication unit 12 to the terminal device 2. In the terminal device 2, the information transmitted from the management device 1 is received by the communication unit 24, and is displayed on the display unit 23 to inform the operator.

[0052] In step S107, when it is determined that the input setting is equal to or lower than the class set for the base member (S107: NO), the control unit 10 sets the input content for that item (S109). In step S109, the recommended level of the standard for that item is set with the content input by the operator.

[0053] In step S106, when it is determined that the item is an independent attribute (S106: NO), the control unit 10 sets the content input for the item (S110). In step S110, the recommended level of the standard for the item is set based on the content input by the operator.

[0054] In the above manner, the management device 1 executes the related component information setting process. Setting the related component database 112 in the related component information setting process provides excellent effects such as improved convenience and prevention of errors, as compared with the case where attributes and classes are set manually one by one.

[0055] 9 is a flowchart showing an example of the child component database 113 setting process of the management device 1 disclosed in the present application. The child component database 113 setting process is a process for setting the child component database 113.

[0056] An operator who operates the terminal device 2 operates the terminal device 2 to set up the child component database 113. The terminal device 2, which has accepted the operator's operation, accesses the management device 1 and sets up the child components based on the accepted input. Here, an example will be described in which a component such as a sash set up in the basic database 111 is designated as a parent component, and the attributes and recommendation level of the child component used in the configuration of the parent component are input to set up the child component database 113 in which information related to the child components is recorded.

[0057] The control unit 10 included in the management device 1 executes the management program 110 recorded in the recording unit 11 to perform a child component database 113 setting process. The control unit 10 of the management device 1 that has received access from the terminal device 2 receives a designation of the basic database 111 from the terminal device 2 (S201), and accepts settings of child components used in the configuration of the parent component recorded in the designated basic database 111 (S202). In step S202, for example, for a parent sash, settings of child components such as "frame + shoji + glass," "screen door," and "frame L cover" used in the configuration of the sash are accepted.

[0058] Furthermore, the control unit 10 of the management device 1 accepts designation of attributes to be set for the child components from the terminal device 2 (S203). In step 203, designation of attributes to be set for the child components is accepted from among the attributes set for the parent components.

[0059] The control unit 10 of the management device 1 sets the child component database 113 indicating the standard of the child component to which the same rank of recommendation level as that of the parent component is set in the item indicating the specified attribute (S204).

[0060] In the above manner, the management device 1 executes the child component database setting process. Setting the child component database 113 in the child component database setting process provides excellent effects such as improved convenience and prevention of errors, compared to the case where attributes and classes are set manually one by one.

[0061] As described above in detail, the component information management system disclosed in the present application has excellent effects such as being able to improve the convenience when setting component standards.

[0062] The present invention is not limited to the above-described embodiment, and can be implemented in various other forms. Therefore, the embodiment is merely illustrative in all respects and should not be interpreted as being limited. The scope of the present invention is indicated by the claims, and is not restricted in any way by the text of the specification. Furthermore, all modifications and changes within the equivalent scope of the claims are within the scope of the present invention.

[0063] For example, in the above embodiment, an operator operates the terminal device 2 to cause the management device 1 to manage various databases, but the present invention is not limited to this and can be expanded into various forms, such as a form in which an operator operates the management device 1. [Explanation of symbols]

[0064] 1 Management device 10 Control section 11 Recording section 110 Management Program 111 Basic Database 112 Related parts database 113 Sub-component database 12 Communications Department 2 Terminal Device 20 Control section 21 Recording Section 22 Input section 23 Display section 24 Communications Department NW Communication network

Claims

1. An information management system for managing information regarding building components, A basic database that lists multiple standards for the attributes of building materials and associates multiple attributes with each other; a related component database in which a plurality of attributes each having a plurality of standards of related components set in relation to the installation of the foundation components recorded in the basic database are associated with each other; a management device for managing the basic database and the related component database; Equipped with The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, In the related component database, related attributes of items similar to those of the base component and independent attributes different from those of the base component are set as attributes for the related component, The management device includes: A means for receiving settings of the relationship of standards between the related attributes in the related component database; If the accepted setting is a recommendation level higher than the level set for the underlying component, a means of prohibiting the setting is provided. Equipped A component information management system comprising:

2. A component information management system according to claim 1, The base member is a sash, The related member is a picture frame. A component information management system comprising:

3. An information management system for managing information relating to building components, comprising: A basic database that lists multiple standards for the attributes of building materials and associates multiple attributes with each other; a child component database in which a plurality of child attributes each having a plurality of specifications of a child component used in the configuration of a parent component recorded in the basic database are associated with each other; a management device for managing the basic database and the child member database; Equipped with The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, The child component database can set, as an attribute, a child attribute of an item similar to that of a parent component for the child component; The management device includes: a means for receiving, by designating an attribute, a setting of a child component to be used in the configuration of a parent component recorded in the basic database; For the child attributes among the accepted attributes, a means for setting a rank similar to that of the parent component attribute is provided. A component information management system comprising:

4. A component information management system according to claim 3, The parent member is a sash. A component information management system comprising:

5. A component information management system according to claim 1 or claim 3, the member is a sash, The attributes include a vertical length standard and a horizontal length standard of the sash, The classes include set, configurable, and non-configurable. A component information management system comprising:

6. A component information management system according to claim 5, The attributes further include interior and exterior colors of the sash. A component information management system comprising:

7. A management device for managing a database that records information about building components, A means for accessing a basic database in which a plurality of standards are set as items for attributes of building materials and a plurality of attributes are associated with each other is provided; The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, a means for accessing a related component database in which attributes having a plurality of standards of related components set in relation to the installation of the foundation components recorded in the basic database are associated with each other; In the related component database, related attributes of items similar to those of the base component and independent attributes different from those of the base component are set as attributes for the related component, Furthermore, A means for receiving settings of the relationship of standards between the related attributes in the related component database; If the accepted setting is a recommendation level higher than the level set for the underlying component, a means of prohibiting the setting is provided. A management device comprising:

8. A management device for managing a database that records information about building components, A means for accessing a basic database in which a plurality of standards are set as items for attributes of building materials and a plurality of attributes are associated with each other is provided; The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, a means for accessing a child component database in which a plurality of child attributes having a plurality of specifications of child components used in the configuration of a parent component recorded in the basic database are associated; The child component database can set, as attributes for a child component, a child attribute of an item similar to that of a parent component and an independent attribute different from that of the parent component; Furthermore, a means for receiving, by designating an attribute, a setting of a child component to be used in the configuration of a parent component recorded in the basic database; For the child attributes among the accepted attributes, a means for setting a rank similar to that of the parent component attribute is provided. A management device comprising:

9. A management program executable by a computer, comprising: a means for accessing a basic database in which attributes of building components are classified into a plurality of standards and the plurality of attributes are associated with each other; and a means for accessing a related component database in which attributes having a plurality of standards as items of related components set in relation to the installation of foundation components recorded in the basic database are associated with each other; The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, In the related component database, related attributes of items similar to those of the base component and independent attributes different from those of the base component are set as attributes for the related component, On the computer, receiving a setting of a standard relationship between the related attributes in the related component database; prohibiting the setting if the accepted setting is a higher recommended level than the level set for the underlying member; A management program for causing the user to execute the above steps.

10. A management program executable by a computer, comprising: a means for accessing a basic database in which a plurality of standards are items for attributes of building components and the attributes are associated with each other; and a means for accessing a child component database in which a plurality of child attributes, each child attribute having a plurality of standards as items for child components used in the construction of a parent component recorded in the basic database, are associated with each other; The basic database records a plurality of levels of recommendation for the suitability of a component as a relationship between the specifications of each attribute, The child component database can set, as attributes for a child component, a child attribute of an item similar to that of a parent component and an independent attribute different from that of the parent component; On the computer, receiving a setting of a child component to be used in the configuration of a parent component recorded in the basic database by specifying an attribute; A step of setting a rank for a child attribute of the received attributes in the same way as the attribute of the parent component. A management program for causing the user to execute the above steps.

Images