WO2016031318A1

WO2016031318A1 - Product specification design device and product specification design method

Info

Publication number: WO2016031318A1
Application number: PCT/JP2015/064400
Authority: WO
Inventors: 仲田　輝男; 芳賀　憲行; 貴元松井
Original assignee: 株式会社日立製作所
Priority date: 2014-08-29
Filing date: 2015-05-20
Publication date: 2016-03-03
Also published as: JP2017207791A

Abstract

　The present invention designs product specifications conforming to client demands. A product specification design device for determining product specifications by setting, from past designs, design rules in response to inputted specifications requested by a client, said rules fulfilling these requested specifications, wherein the product specification design device is characterized in being provided with a memory unit in which the requested specifications and the design rules for the requested specifications are stored categorized as client information or setting information, and, when the product specifications are set in response to the inputted specifications requested by the client, the product specifications are to be determined by inputting a category that becomes an extraction criterion and using only past designs belonging to the category.

Description

Product specification design apparatus and product specification design method

The present invention relates to a product specification design apparatus.

In order-made products such as plants and infrastructure equipment that design products after receiving customer requirements, product specification design devices that automatically determine product specifications are often used to improve design efficiency. This product specification design device requires a design rule for determining product specifications. As a background art of this design rule generation, there is JP 2010-128699 A (Patent Document 1). The design specification design apparatus of this publication outputs a device with a high matching rate of required specification items.

JP 2010-128699 A

However, customers who require special specification values different from other customers for some required specification items (for example, the safety of the outer case material of products that handle corrosive gas is guaranteed by the standards. Even if there is a material, a customer who has a policy that emphasizes safety may desire a material that is stronger than the standard material). Since many of the customer's required specification items are standard specification values, standard design rules are adopted, resulting in standard product specifications ignoring customer policies.

In addition, not only the circumstances of the customer, the situation regarding the installation, for example, environmental measures at the installation area (wind, snow, flying sand measures, such as salt damage measures) and the presence or absence of the need for, EPC (E ngineering P rocurement C onstruction) contractors Appropriate product specifications vary depending on the construction capabilities of the supplier.

The object of the present invention is to design product specifications according to the project.

In order to solve the above-described problems, the present invention provides a customer specification (for example, customer-specific specification information) or installation information (for example, installation) for the required specifications stored in the design performance DB and the product specifications for the required specifications. Categorize by region and EPC contractor, and use these categories as extraction conditions.

According to the present invention, it is possible to design a product specification according to the project.

It is the figure which showed the structure of the product specification design apparatus. It is the figure which showed the processing flow of the product specification design apparatus. It is the figure which showed the flow of the rule production | generation process according to category. It is the figure which showed the flow of the rule adoption determination process according to category. It is the figure which showed the rule edit screen classified by category. It is the figure which showed the edit screen of category priority. It is the figure which showed design performance data. It is the figure which showed the total result of the design performance. It is a figure showing rule adoption standard data. It is the figure which showed the rule data classified by category. It is the figure which showed category priority data. It is the figure which showed matter category data. It is the figure which showed required specification data. It is the figure which showed product specification data.

Examples of the present invention will be described below, but the present invention is not limited to the following examples.

[Basic configuration]
FIG. 1 shows the configuration of the product specification design apparatus.

The product specification design apparatus according to the present embodiment includes a calculation unit 101, an input / output unit 102, and a storage unit 103.

The calculation unit 101 includes a category-specific rule generation unit 104 and a category-specific rule adoption determination unit 105. Details will be described later.

The input / output unit 102 has a function of performing input / output through an input / output device.

The storage unit 103 includes category-specific rule data 108, category classification priority data 109, rule adoption reference value data 110, design performance data 111, item category data 112, requirement specification data 113, and product specification data 114.

The category-specific rules 108, the category classification priority 109, the rule adoption reference value 110, and the case category 112 are input or edited through the input / output unit 102 and stored in the storage unit 103.

The required specification data 113 is received from the case management system, and the design performance data 111 is received from the design data management system via a network (not shown), and stored in the storage unit 103.
[Basic processing flow]
FIG. 2 shows a processing flow. The category-specific rule generation unit 104 reads the rule adoption reference value 110, the design performance data 111, and the category classification priority data 109 from the storage unit 103, and generates the category-specific rule 108 based on them. The category-specific rule generation unit 104 stores the generated category-specific rule 108 in the storage unit 103.

The category-specific rule adoption determination unit 105 is based on the category classification priority data 109, the item category data 112, the required specification data 113, and the category-specific rules 108 created by the category-specific rule generation unit 104 from the storage unit 103. Then, product specification data 114 is generated and stored in the storage unit 105.
[Detailed flow of category-specific rule generation unit 104]
The processing contents of the category-specific rule generation unit 104 will be described with reference to the processing flowchart of FIG.

First, the flow 301 selects a category category set in the category category priority data 109 from the design result data 111, and extracts data of a category target in the category category.

7 shows design result data 111 and FIG. 11 shows category division priority data 109. In the category classification priority data 109 shown in FIG. 11, customers, EPCs, regions, and standards are registered as category classifications. The category category priority data 106 can be edited on the category category priority editing screen 106 shown in FIG. The category division priority editing screen 106 includes a menu 611 on the left side and a screen 612 showing the priority for each category generated from the category division priority data 109 on the right side. From the top, the menu includes priority order storage, new category registration, and category deletion. The user can select this menu, and can add, delete, and modify rule data, category data, and category classification priority data by category. When a change occurs, each data in the storage unit 103 is updated. Will be.

The case where “Customer” is selected as the category classification for the first rule generation will be described.

Refer to the design performance data 111 shown in FIG. The design record data 111 stores installation information related to installation of equipment and customer information for specifying the customer's original specifications. In the present embodiment, as the installation information, the EPC business name is stored in the category classification “EPC”, and the installation area is stored in the category classification “region”. In the present embodiment, items of “customer name”, “required specification / specification gas type”, and “required specification / pipe material” are set as customer information. When the customer of the target product for product design is “Company A”, data of case Nos. 1, 2, 3, and 4 in which the category classification “customer name” is data of “Company A” are extracted.

Next, the flow 302 is performed. First, a combination of the required specification value and product specification value of the extracted design performance data is obtained. Here, when the extracted category classification is “customer” and the category target “customer name” is “Company A”, when “use gas type” is “CO2”, “pipe material” is “Stainless” ”, 2 data,“ CH4 ”is used, 1 data is“ Stainless ”and 1 data is“ Brass ”. . Therefore, there are three types of combinations of required specifications and product specifications. Then, the adoption rate and the number of data are tabulated for these three types of combinations. The tabulation results are shown in FIG. The adoption rate means the ratio of the corresponding product specifications to the same required specifications. In the example of FIG. 8, for the “use gas type CO2” that is the required specification, the product material “pipe material” is only Stainless, so the rate of adoption of the pipe material “Stainless” relative to the specification gas type CO2 is 100%. On the other hand, for the gas type CH4, the pipe materials are Stainless and Brass, so the adoption rate is 50% for both Stainless and Brass. At the same time, the number of data is also counted.

Next, the processing flow 303 will be described. The rule adoption reference value data 110 stores a reference as to which rule is adopted. FIG. 9 shows rule adoption reference value data 110. In this embodiment, the “adoption rate reference value” and the “data number reference value” are used as references. For each combination of “Required specification” and “Product specification”, the calculated adoption rate and the number of data are compared, and the combination is that the adoption rate is greater than the adoption rate reference value and the number of data is greater than the data number reference value. Is adopted as a design rule. As shown in FIG. 9, in this embodiment, the rule is that the adoption rate is 75% or more and the number of data is 2 or more. Therefore, according to the total result of FIG. ", The rule that the pipe material is" Stainless "is adopted. When a plurality of combinations satisfying the adoption standard value are extracted, the combination having the highest adoption rate is adopted as the design rule.

Finally, it is determined whether or not calculation has been performed for all category divisions and category targets in the flow 304. If there is a category division or category target for which calculation has not been performed, the flow returns to the flow 301 to perform calculation.

Note that the calculated category-specific rules 108 can be confirmed and edited on the category-specific rule edit screen 107.

In the category-specific rule editing screen shown in FIG. 5, there is a navigation 501 for tracing a design rule to be confirmed from the product configuration. When a design rule to be referred to is selected using this, the design rule display unit 503 displays category categories and category targets. Separately, combinations of required specifications and product specifications are displayed, and it is possible to confirm which combination was adopted based on the rule adoption reference value 110 set by the rule adoption reference value setting unit 502. If the combination adopted in the rule adoption standard value is not adopted in the design rule, or conversely, if the rule adoption standard value is not met, but there is a combination to be adopted as the design rule, edit whether to adopt it here It can be carried out.
[Detailed Flow of Category-Based Rule Adoption Determination Unit 105]
A detailed flow of the category-specific rule adoption determination unit 105 will be described with reference to the processing flowchart shown in FIG.

First, in the flow 401, the category classification with the priority “1” is selected from the category classification priority 109. In this embodiment, as shown in FIG. 11, “customer” is selected.

Next, in the flow 402, the corresponding category classification rule is extracted from the category-specific rule data 108. FIG. 10 shows the category-specific rule data 108 of this embodiment. In this embodiment, there are a rule for determining “pipe material” and a rule for determining “presence / absence of a heat retaining mechanism”. Since there is a rule relating to “Company A” in the rule for determining “pipe material”, the rule is extracted. On the other hand, in the rule for determining “presence / absence of heat insulation mechanism”, there is no category classification rule of customer, so nothing is extracted.

Next, in the flow 403, the extracted category classification rules are checked against the item category data 112 to determine the applicability of the rules. The item category data 112 of the present embodiment is shown in FIG. In this example, the category target for the category classification "customer" is "Company A", the category target for the category classification "EPC" is "Company J", and the category target for the category classification "Region" is "Middle East" Since there is a category object “Company A” of the category “Customer”, it is determined that the rule relating to “Company A” for determining the extracted “pipe material” is applicable. Further, when there is a rule determined to be applicable, the required specification value 113 of the rule determined to be applicable is checked against the required specification data 113 to determine whether or not the product specification value is adopted. FIG. 13 shows the required specification data 113 of this embodiment. In this example, the category classification “Used gas type” is “CO2” and matches the “Used gas type CO2” which is the required specification of the rule for determining the “Pipe material” of the extracted “Company A”. Adopting this rule, the product specification and “pipe material” is determined as “Stainless”.

Then, whether or not the rule application determination has been calculated for all the category sections is determined in flow 404. If all the category sections have not been calculated, the next priority category section is selected and the flow proceeds to step 405. Then, the next priority order of the category category targeted at that time and the set category category are selected, and the flow returns to the corresponding flow 402 to perform calculation.

As shown in FIG. 11, “EPC” is set as the priority order “2” in this embodiment. As shown in FIG. 10, the only rule for determining “presence / absence of heat retaining mechanism” stored as the category classification “EPC” in the category-specific rule data 108 of this embodiment is “M company”. However, as shown in FIG. 12, in the case category data 112 of this embodiment, “EPC” is “Company J”, so this rule is not applied.

Furthermore, as shown in FIG. 11, “region” is set as the priority “3” of this embodiment. As shown in FIG. 10, the rule stored as the category classification “region” in the category-specific rule data 108 of this embodiment is only the rule relating to “Europe” that determines the pipe material. However, as shown in FIG. 12, in the case category data 112 of this embodiment, “Region” is “Middle East”, so this rule is not applied.

Here, as a rule for determining the “pipe material”, a rule for “Middle East” is set, and the “use gas type” is “CO2” and the “pipe material” is “Brass”. If there is a match, the item category data 112 and the required specification data 113 are matched, but since the product specification has already been determined for the pipe material in the category “customer” of the priority “1”, the priority Low rules do not apply.

Eventually, the standard category category rule is applied to the rule for determining the presence or absence of the heat retention mechanism, and in this embodiment, the site temperature of the required specification is 20 degrees, so the product specification without the heat retention mechanism is determined. Is done. The determined product specification data 114 is shown in FIG. The product specifications thus determined can be linked to various design support systems to calculate an estimated amount and create a drawing.

The processing by the category-specific rule adoption determining unit 105 is executed when the product specification is determined after the required specification data 113 is updated after receiving the required specification from the customer. The processing at may be executed in advance.

101: calculation unit,
102: Input / output unit 103: Storage unit,
104: a category-specific rule generator,
105: A category-specific rule adoption determination unit,
106: Category classification priority setting screen,
107: Rule editing screen by category,
108: Rule data by category,
109: Category division priority data,
110: Rule adoption standard value data,
111: Design result data,
112: Item category data
113: Requirement specification data,
114: Product specification data

Claims

A product specification design device that determines a product specification by determining a design rule that satisfies the required specification from the design results for the input specification of the customer.
A storage unit in which required specifications and design rules for the required specifications are categorized and stored by customer information or installation information,
When determining a product specification with respect to the input requirement specification of the customer, a category is input as an extraction condition, and the product specification is determined using only design results belonging to the category. Specification design equipment.
In claim 1,
When there are a plurality of the categories, the product specification design apparatus is characterized in that priorities among the categories are determined in advance.
In claim 1,
The category is expressed by a numerical value serving as a threshold,
The product specification design apparatus, wherein the product specification design apparatus is classified into a category by comparison with the threshold value when stored in the storage unit.
In claim 1,
An apparatus for designing product specifications, wherein an adoption rate and the number of data are used as criteria for determining product specifications by determining design rules that satisfy the required specifications from design results.
A product specification design method for determining a product specification by determining a design rule that satisfies the required specification from the design results with respect to an input requirement specification of a customer,
Requirement specifications and design rules for the required specifications are categorized by customer information or installation information into a database,
When determining a product specification for the input requirement specification of the customer, a category as an extraction condition is also input, and the product specification is determined using only design results belonging to the category. Specification design method.
In claim 5,
A product specification design method characterized in that, when there are a plurality of the categories, priorities among the categories are determined in advance.
In claim 5,
The category is expressed by a numerical value serving as a threshold,
A product specification design method characterized by classifying a category by comparison with the threshold value.
In claim 5.
A product specification design method characterized by using an adoption rate and the number of data as determination criteria when determining a product specification by determining a design rule that satisfies the required specification from design results.