Design support system, design support method and program

Abstract

To provide a design support system, a design support method and a program that allow a person in charge to recognize information of a system which a customer is considering designing.SOLUTION: A design support system according to an embodiment has an input unit, a specification unit, a recording unit, and a transmitting unit. The input unit accepts input of specification values of a plurality of items of a requirement specification relating to a product from a customer. The specification unit specifies a module constituting the product based on the specification values of the requirement specification. The recording unit records a design plan that associates the specification values of the requirement specification with the module in a database. The transmitting unit transmits information of the design plan recorded in the database to a designer.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] An embodiment of the present invention relates to a design support system, a design support method, and a program. [Background technology]

[0002] When designing large-scale systems such as electrical equipment, the system designer formulates the product design specifications based on the customer's required specifications. In the design process, development is underway using a configurator that identifies modules that meet the design specifications from those specifications. The configurator generates documents (quotations, module tables, etc.) based on the identified modules. The designer formulates the design specifications by hearing the required specifications in meetings with the customer, and enters the design specifications into the configurator. The configurator creates design-related documents by performing calculations based on the input design specifications.

[0003] By knowing in advance the information about the system that the customer is considering designing, the designer can consider design specifications that capture the needs of the customer. Therefore, it is preferable for the designer in charge to be made aware of the information about the system that the customer is considering designing at an early stage. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-207791 A Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a design support system, a design support method, and a program that enable a designer in charge to recognize information about a system that a client is considering designing. [Means for solving the problem]

[0006] A design support system according to an embodiment has an input unit, an identification unit, a recording unit, and a transmission unit. The input unit accepts input of specification values ​​of multiple items of required specifications for a product from a customer. The identification unit identifies modules that constitute the product based on the specification values ​​of the required specifications. The recording unit records a design plan in a database that associates the specification values ​​of the required specifications with the modules. The transmission unit transmits information about the design plan recorded in the database to a designer. [Brief description of the drawings]

[0007] [Figure 1] 1 is a schematic diagram showing the configuration of a design support system according to a first embodiment. [Diagram 2] FIG. 1 is a first diagram showing an example of a screen according to the first embodiment; [Diagram 3] FIG. 2 is a second diagram showing an example of a screen according to the first embodiment. [Figure 4] FIG. 3 is a third diagram showing an example of a screen according to the first embodiment. [Diagram 5] FIG. 4 is a fourth diagram showing an example of a screen according to the first embodiment. [Figure 6] FIG. 5 is a fifth diagram showing an example of a screen according to the first embodiment. [Figure 7] FIG. 6 is a sixth diagram showing an example of a screen according to the first embodiment. [Figure 8] FIG. 7 is a seventh diagram showing an example of a screen according to the first embodiment. [Figure 9] FIG. 8 is an eighth diagram showing an example of a screen according to the first embodiment. [Figure 10] FIG. 9 is a ninth diagram showing an example of a screen according to the first embodiment. [Figure 11] FIG. 10 is a tenth diagram showing an example of a screen according to the first embodiment. [Figure 12] FIG. 11 is an eleventh diagram showing an example of a screen according to the first embodiment. [Figure 13] FIG. 12 is a twelfth diagram showing an example screen according to the first embodiment. [Figure 14] FIG. 13 is a thirteenth figure showing an example screen according to the first embodiment. [Figure 15] FIG. 14 is a 14th diagram showing an example of a screen according to the first embodiment. [Figure 16] FIG. 15 is a 15th diagram showing an example of a screen according to the first embodiment. [Figure 17] FIG. 16 is a 16th diagram showing an example of a screen according to the first embodiment. [Figure 18] FIG. 17 is a 17th diagram showing an example of a screen according to the first embodiment. [Figure 19] FIG. 18 is an 18th diagram showing an example screen according to the first embodiment. [Figure 20] FIG. 19 is a 19th diagram showing an example of a screen according to the first embodiment. [Figure 21] FIG. 4 is a view showing an example of a plan list file according to the first embodiment. [Figure 22] FIG. 4 is a view showing an example of a query list file according to the first embodiment. [Figure 23] FIG. 20 is a twentieth diagram showing an example screen according to the first embodiment. [Figure 24] FIG. 4 is a diagram showing an example of a quote file according to the first embodiment. [Diagram 25] FIG. 1 is a schematic software configuration diagram of a design support system according to a first embodiment. [Figure 26] FIG. 4 is a view showing an example of a plan table according to the first embodiment. [Figure 27] FIG. 4 is a diagram showing an example of a user table according to the first embodiment. [Figure 28] FIG. 4 is a diagram showing an example of an inquiry table according to the first embodiment. [Figure 29] FIG. 4 is a diagram showing an example of an initial value table according to the first embodiment. [Diagram 30] FIG. 4 is a diagram showing an example of a prohibition rule table according to the first embodiment. [Diagram 31] 5 is a flowchart showing a process of creating a new case in the design support system according to the first embodiment. [Diagram 32] 5 is a flowchart showing a process of editing detailed items in the design support system according to the first embodiment. [Diagram 33] FIG. 11 is a view showing an example of a screen according to the second embodiment. [Diagram 34] FIG. 13 is a schematic software configuration diagram of a design support system according to another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a design support system, a design support method, and a program according to an embodiment will be described with reference to the drawings.

[0009] (First embodiment) FIG. 1 is a schematic diagram showing the configuration of a design support system 1 according to the first embodiment. The design support system 1 supports the design of power supply equipment, which is a product. The power supply equipment is composed of a combination of multiple devices such as extra-high voltage switch gear, extra-high voltage transformer, high voltage switch gear, high voltage transformer, emergency generator, and uninterruptible power supply system. The power supply equipment is composed of multiple modules including the above-mentioned devices and has various characteristics. A module is a combination of the device itself and multiple parts that make up the device, and is a constituent unit of the power supply equipment. The specific specifications of the power supply equipment are mutually related. The specifications are the functions, performance, shape, part configuration, standards, etc. that the power supply equipment has. As an example, if a certain module is used in the power supply equipment, another module cannot be used due to restrictions caused by the size, output, or function of the module. As another example, if a certain module is used in the power supply equipment, the use of another module that has an adverse effect when combined with the module is restricted. When designing the power supply equipment, it is necessary to take into account the correlation of such specifications, and each module is selected and specified so as to meet the specifications required for the power supply equipment. The design support system 1 includes a detailed design device 10 and a design support device 30. The detailed design device 10 accepts input of specification values ​​of the design specifications of the power supply facility, and specifies modules constituting the power supply facility so as to satisfy the input specification values. Since the number of items of the design specifications required by the detailed design device 10 is huge (for example, more than 1000 items), it is difficult for a customer who is not familiar with design to formulate the design specifications. Hereinafter, the items of the design specifications required by the detailed design device 10 are referred to as design items. Furthermore, the detailed design device 10 generates documents related to the design based on the specified modules. Examples of documents generated by the detailed design device 10 include a module usage table, specification description, single-line connection diagram, layout single-connection diagram, outline drawing, side view, and NET quotation.

[0010] The design support device 30 supports the customer in determining the specification values ​​of the design specifications, and inputs the determined specification values ​​of the design specifications to the detailed design device 10. Since the number of required specification items to be input to the design support device 30 is smaller than that of the detailed design device 10 (for example, 100 items or less), even a customer who is unfamiliar with design can roughly design a power supply facility. The detailed design device 10 and the design support device 30 are connected to a communication network N such as the Internet, and each receives access from a terminal T via the communication network N.

[0011] A designer who designs power supply equipment accesses the detailed design device 10 via a terminal T. The designer is a person whose occupation is to provide power supply equipment design services to customers. The designer may be, for example, an employee of an infrastructure business or a service provider. The designer may also be an infrastructure business or a service provider. In this case, the designer's account and email address may be a representative account and email address handled by multiple employees belonging to the infrastructure business or the service provider. Hereinafter, the terminal T operated by the designer is referred to as a designer terminal T1. A customer who requests the design of power supply equipment accesses the design support device 30 via the terminal T. Hereinafter, the terminal operated by the customer is referred to as a customer terminal T2. Hereinafter, the customer and the designer are collectively referred to as users.

[0012] Here, a description will be given of the services provided by the design support device 30. FIGS. The customer accesses the design support device 30 using a customer terminal T2. The design support device 30 displays a login screen as shown in Fig. 2 on the customer terminal T2. The login screen prompts the customer to enter a user ID and password. The customer enters the user ID and password and presses the sign-in button.

[0013] When the customer logs in, the design support device 30 causes the customer terminal T2 to display a home screen as shown in Fig. 3. On the home screen, a new plan creation button V11, a my page button V12, and a library button V13 are displayed. The new plan creation button V11 is a button for transitioning to a creation screen for creating a new plan for power supply equipment. The My Page button V12 is a button for transitioning to a My Page screen that displays plans belonging to the logged-in customer. The Library button V13 is a button for transitioning to a library screen for viewing plans created by the logged-in customer, other customers in the same group as the logged-in customer, and designers. The customer presses the desired button among the buttons displayed on the home screen.

[0014] When the new plan creation button V11 is pressed, the design support device 30 causes the customer terminal T2 to display a new plan creation screen as shown in Fig. 4. On the new plan creation screen, the customer is prompted to input the management number, name, purpose, and installation area of ​​the plan. The customer inputs the management number, name, purpose, and installation area, and presses the start creation button.

[0015] Hereinafter, the design support device 30 accepts input of specification values ​​of about 10-14 basic items from among multiple items related to the required specifications of the power supply equipment from the customer. The basic items are required specification items that are essential for the outline design of the electrical equipment. As shown in Figs. 5 to 7, the input screen for the basic items displays an input form V1 for the basic items, a hint V2, a progress bar V3, and a Next button V4. The specification values ​​of the basic items are set to initial values. The hint V2 displays information to be considered in determining the specification values ​​of the basic items, reasons why some options are not selectable, and the like. The progress bar V3 indicates the progress of input of the specification values ​​of the basic items. When the Next button V4 is pressed, the specification values ​​of the selected basic items are confirmed and the screen moves to the screen of the next basic item to be input.

[0016] First, the design support device 30 displays an electric power company selection screen as shown in Fig. 5 on the customer terminal T2. The electric power company is one of the basic items of the required specifications. There are multiple electric power companies, but in the example shown in Fig. 5, only one company can be selected as the electric power company. This is because the available electric power companies are narrowed down by the installation area entered on the new plan creation screen in Fig. 4. The customer selects an electric power company and presses the Next button V4.

[0017] Next, the design support device 30 displays a selection screen for the receiving voltage as shown in FIG. 6 on the customer terminal T2. The receiving voltage is one of the basic items of the required specifications. Four options for the receiving voltage are set: 77 kV, 66 kV, 33 kV, and 22 kV. In the example shown in FIG. 6, 77 kV and 33 kV cannot be selected. This is because the receiving voltages available for the electric power company selected on the electric power company selection screen in FIG. 5 have been narrowed down. In addition, the design support device 30 sets 66 kV, which is a recommended option, as an initial value in advance. Even when the customer is unfamiliar with design and cannot determine which receiving voltage to select, or when the receiving voltage cannot be determined in the early stages of design, the customer can easily select an appropriate option. The customer selects the receiving power and presses the next button V4.

[0018] Next, the design support device 30 displays a selection screen for the main transformer capacity as shown in FIG. 7 on the customer terminal T2. The main transformer capacity is one of the basic items of the required specifications. As shown in FIG. 7, the main transformer capacity may be set by operating a slide bar or by directly inputting a numerical value. In the example of FIG. 7, the design support device 30 sets level 6 as a default value as a recommended option in advance. In addition, the selection screen for the main transformer capacity is provided with a function for calculating the main transformer capacity from the total floor area. When the customer presses the "Calculate from total floor area" button, the design support device 30 displays an input screen for the total floor area as shown in FIG. 8 on the customer terminal T2. In the input screen for the total floor area, the total floor area can be input for each use. In addition, initial values ​​such as the usage amount per unit area are input for each use. This allows the customer to calculate the main transformer capacity by inputting the total floor area for each use. The calculation result is displayed on the selection screen for the main transformer capacity shown in FIG. 7. Therefore, the customer can input the specification value of the main transformer capacity while referring to the calculation result of the main transformer capacity. After inputting the specification value of the main transformer capacity, the customer presses the next button V4.

[0019] After specification values ​​for several basic items have been input, design support device 30 causes customer terminal T2 to display a selection screen for the high-voltage unit configuration as shown in FIG. 9. The configuration of the high-voltage unit is one of the basic items of the required specifications. As shown in FIG. 9, the selection screen for the high-voltage unit configuration has multiple configuration types shown in the figure set as options. Design support device 30 sets initial values ​​for the high-voltage unit configuration based on the specification values ​​of the required specifications that have been input up to that point. The customer selects the configuration of the high-voltage unit and presses the Next button V4.

[0020] When specification values ​​have been input for all basic items of the required specifications, the design support device 30 causes the customer terminal T2 to display a confirmation screen for the specification values ​​of the basic items as shown in Fig. 10. The customer confirms the specification values ​​of the basic items that have been set up to that point, and presses a button to transition to the next screen. The design support device 30 generates design specifications for the power supply facility based on the specification values ​​of the basic items input by the customer, and causes the detailed design device 10 to identify the combination of modules that make up the power supply facility.

[0021] Next, the design support device 30 displays on the customer terminal T2, as shown in FIG. 11, a selection screen for a plan of the power supply facility that satisfies the input required specifications. The configuration diagram of the power supply facility displayed on the plan selection screen is generated by the detailed design device 10 based on the design specifications input from the design support device 30. In the example shown in FIG. 11, one plan (reliability-oriented type) is selected as an initial value. This is specified by the purpose input on the new plan creation screen in FIG. 4. The customer selects one of the presented plans and presses the next button V4. Note that in another embodiment, the detailed design device 10 may generate only one plan based on the input design specifications without receiving a plan selection by the customer.

[0022] Next, as shown in FIG. 12, the design support device 30 displays a power supply equipment presentation screen on the customer terminal T2. The power supply equipment presentation screen displays the configuration of the power supply equipment that satisfies the input required specifications and the estimated cost of the power supply equipment. The power supply equipment presentation screen also includes an input form V1 for detailed items of the required specifications. The detailed items are required specifications for more detailed settings in the design of electrical equipment. The customer can re-specify the configuration of the power supply equipment so as to satisfy the specifications related to the detailed items by rewriting the specification values ​​of the detailed items in the input form V1 and pressing the update button V5. The design support device 30 re-specifies the design specifications of the power supply equipment based on the specification values ​​of the basic items and detailed items input by the customer, and causes the detailed design device 10 to specify a combination of modules that constitute the power supply equipment. The power supply equipment presentation screen also includes a check box V21 that can specify whether or not to allow other customers belonging to the same group to view the plan. The customer can allow other customers belonging to the same group to view the plan by checking the check box V21, and can refuse viewing by other customers by checking the check box V21. In another embodiment, the details display panel V7 of the My Page screen shown in FIG. 14 may be provided with a check box V21 that allows the user to specify whether or not to permit other customers belonging to the same group to view the page. Moreover, the customer confirms the information about the designed power supply equipment by pressing the save button V6 on the power supply equipment presentation screen.

[0023] When the save button V6 is pressed, the design support device 30 displays a result output screen showing the information of the saved plan on the customer terminal T2, as shown in FIG. 13. The result output screen displays the management number, installation area, rough estimate, and system diagram of the plan. The rough estimate shows the breakdown of the component units and the total amount. The result output screen also has a download button for downloading documents such as a specification description, a single-line connection diagram, spec information, an outline drawing, and a description of the maintenance space. When the download button is pressed, the design support device 30 generates corresponding information and transmits the generated information to the customer terminal T2. The result output screen has a My Page button V12, a home button V14, an edit button V15, and an inquiry button V16. The My Page button V12 is a button for transitioning to a My Page screen that displays plans belonging to the logged-in customer. The Home button V14 is a button for transitioning to the home screen shown in Fig. 3. The Edit button V15 is a button for editing the specifications of the plan. The Inquiry button V16 is a button for inquiring of information about the plan to the designer. When the home button V14 is pressed, the design support device 30 displays the home screen shown in FIG.

[0024] On the other hand, when the My Page button V12 shown in FIG. 13 or FIG. 3 is pressed, the design support device 30 displays the My Page screen shown in FIG. 14. The My Page screen includes a list of plans belonging to the logged-in customer. The My Page screen is an example of a presentation screen (second presentation screen) that shows design plans associated with the user ID of the logged-in customer. The list is a two-dimensional table in which plans are arranged on the vertical axis and the values ​​of items of each plan are arranged on the horizontal axis. The items shown in the list are name, status, management number, plan ID, creation date, last update date, standard price, and installation area. The item names are displayed at the top of the list, and by pressing the desired item name, the plans can be rearranged in ascending or descending order of that item.

[0025] When a plan displayed in the list is selected, the design support device 30 displays a detail display panel V7 on the My Page screen. The detail display panel V7 includes the name of the selected plan, the management number, the installation area, a configuration diagram, an edit button V15, an inquiry button V16, a result output button V17, and a copy button V18. The edit button V15 is a button for editing the specifications of the plan. The inquiry button V16 is a button for inquiring of information about the plan from the designer. The result output button V17 is a button for transitioning to the result output screen shown in FIG. 13. Note that if the status of the plan is a draft, the result output button V17 cannot be selected. The copy button V18 is a button for copying the plan.

[0026] The My Page screen is provided with a search form V19 for narrowing down the plans to be displayed. The search form V19 has a condition input form and a search button. The condition input form is collapsed, and pressing the button expands the input form as shown in FIG. 15. Conditions include any keyword, purpose, values ​​of basic items, values ​​of detailed items, etc. When the customer enters the conditions and presses the search button, the design support device 30 searches for plans that meet the conditions and displays them in a list.

[0027] The My Page screen has a comparison button V20 for comparing multiple plans. The list has check boxes for selecting multiple plans, and when the comparison button V20 is pressed while the check boxes for multiple plans are checked, the design support device 30 displays a comparison screen for comparing values ​​such as the standard price, installation area, number of feeders, external dimensions, mass, and heat value of the selected plans.

[0028] When the inquiry button V16 shown in FIG. 13 or 14 is pressed, the design support device 30 displays an inquiry screen shown in FIG. 16. The inquiry screen includes information on the target plan, an inquiry form, a discard button, and a send button. The inquiry form includes a drop-down list for selecting an inquiry category, a text box for entering the inquiry content, and an upload button for attachments. The customer can send an inquiry about the selected plan to the designer by entering the inquiry content in the inquiry form and pressing the send button. The entered inquiry content can be discarded by pressing the discard button. The inquiry category also includes design request items for requesting detailed design to the designer and meeting requests for requesting a meeting, and also functions as a request processing unit for the designer.

[0029] When the library button V13 shown in FIG. 3 is pressed, the design support device 30 displays a library screen shown in FIG. 17. The library screen includes a list of plans. The list includes plans (created plans) created by customers (including the logged-in customer) belonging to the same group as the logged-in customer, standard plans created by designers using the design support system 1, and drawing plans (non-standard plans) created by designers without using the design support system 1. The created plans and standard plans are created using the design support system 1, so specification values ​​related to the required specifications are associated with them. On the other hand, the drawing plans are design plans created without the design support system 1 and outside the range of the specifications of the design support system 1, so specification values ​​related to the required specifications are not associated with them. In other words, the drawing plans are design plans related to specification values ​​that cannot be input to the design support system 1. The library screen is an example of a presentation screen (first presentation screen) that displays multiple design plans, including a design plan whose user ID and owned information of the logged-in customer do not match.

[0030] The list is a two-dimensional table with plans arranged on the vertical axis and the item values ​​of each plan arranged on the horizontal axis. The items shown in the list are name, category, last update date, standard price, and installation area. The category indicates whether it is a created plan, a standard plan, or a drawing plan. The item names are displayed at the top of the list, and by clicking the desired item name, the plans can be sorted in ascending or descending order of that item.

[0031] When a plan displayed in the list is selected, the design support device 30 displays a detail display panel V7 on the library screen. The detail display panel V7 includes the name of the selected plan, the management number, the installation area, the configuration diagram, the inquiry button V16, the result output button V17, and the copy button V18. The detail display panel V7 on the library screen does not include the edit button V15. This is because the plan displayed on the library screen may have been created by someone else, and this is to prevent editing by anyone other than the user to which the plan belongs. Note that if the selected plan is a drawing plan, the copy button V18 is not displayed on the detail display panel V7. This is because the drawing plan does not have specification values ​​related to the required specifications, so it cannot be customized by the customer and there is no reason to copy it.

[0032] The library screen is provided with a search form V19 for narrowing down the plans to be displayed and a comparison button V20 for comparing multiple plans. The search form V19 includes a condition input form and a search button. The condition input form is collapsed, and pressing it expands the input form as in the example shown in FIG. 15. Conditions include any keyword, purpose, basic item values, detailed item values, and the like. When a customer enters conditions and presses the search button, the design support device 30 searches for plans that meet the conditions and displays them in a list. When the comparison button V20 is pressed, the design support device 30 displays a comparison screen that compares values ​​such as the standard price, installation area, number of feeders, external dimensions, mass, and heat value of the selected plan.

[0033] When the result output button V17 is pressed on the library screen, the design support device 30 displays the result output screen shown in Fig. 13 on the customer terminal T2. The result output screen related to the created plan or standard plan does not include the edit button V15. Furthermore, the result output screen related to the drawing plan does not include the plan management number and the edit button V15, nor does it include the standard price, installation area, number of feeders, input item data, a download button for the specification statement, or a download button for the maintenance space description.

[0034] In this way, the design support system can present the customer with a My Page screen that allows the customer to view and edit plans that the customer created in the past, and a library screen that allows the customer to refer to plans created by others.

[0035] A designer can also access the design support device 30. The designer accesses the design support device 30 using a designer terminal T1. When the attribute of the logged-in user is a designer, the design support device 30 causes the designer terminal T1 to display a home screen for the designer as shown in Fig. 18. The home screen for the designer displays a new plan creation button V11, a my page button V12, a library button V13, and a customer management button V22. The customer management button V22 is a button for transitioning to a customer management screen for displaying data of customers who use the design support device 30.

[0036] When the customer management button V22 is pressed, the design support device 30 displays a customer management screen as shown in FIG. 19 on the designer terminal T1. The customer management screen displays a customer list V23 and a download button V24. The customer list V23 is a list in which, for each customer, the customer's user ID, the group to which the customer belongs, user information such as the customer's name and email address, the registration date of the user ID, the last login date, the number of logins, the number of plans, and the number of inquiries are associated. Here, the user's login, the creation of a plan, an inquiry, and the like are examples of user actions with respect to the design support system 1. When the download button V24 is pressed, the design support device 30 generates a customer list file representing the customer list V23, and transmits the generated customer list file to the designer terminal T1. In other words, it can be said that the design support device 30 includes a transmission unit that transmits customer information recorded in the database to the designer. The customer list file may be, for example, CSV data. Based on the displayed customer list V23 and the downloaded customer list file, the designer can perform analysis such as estimating the progress of the project related to each customer's plan. For example, the detailed design device 10, the design support device 30, or an externally provided analysis device may generate analysis data for each group that compiles the frequency of use of the design support device 30 by customers belonging to the group based on the customer list file. Also, for example, the detailed design device 10, the design support device 30, or an externally provided analysis device may compile user actions such as the number of logins by users within the last month and the number of plans created by users for each group, and generate analysis data that shows the tendency of each group. In particular, the detailed design device 10, the design support device 30, or an externally provided analysis device may generate analysis data that shows the number of design plans for each region related to the same group. By referring to such analysis data, the designer can recognize the degree of busyness of each customer's region, and can provide support such as advice and assistance to the customer. The analysis result of the group may be presented to the customer belonging to the group by pressing an analysis result icon provided on the screen of the library for the customer. Downloading of the customer list file is permitted for the designer but not for the customer.

[0037] Furthermore, when the designer presses the library button V13 shown in FIG. 18, the design support device 30 displays the designer's library screen shown in FIG. 20. The designer's library screen includes a list of plans. The plans displayed in the list are those plans that satisfy the conditions entered in the search form V19, among all plans that are not created by the creating user. The search form V19 on the designer's library screen includes a check box for specifying whether or not deleted plans are to be included in the search results. By turning on the check box, deleted plans that satisfy the conditions can also be included in the list. Furthermore, the designer's library screen is provided with a plan download button V25 and an inquiry download button V26.

[0038] When the plan download button V25 shown in Fig. 20 is pressed, the design support device 30 generates a plan list file that represents data related to all plans displayed in the list, and transmits the generated plan list file to the designer terminal T1. In other words, it can be said that the design support device 30 has a transmission unit that transmits information on the design plan recorded in the database to the designer. The plan list file may be, for example, CSV data. The designer is permitted to download the plan list file, but the customer is not permitted to download it.

[0039] FIG. 21 is a diagram showing an example of a plan list file according to the first embodiment. The plan list file is data in which, for each plan, a plan ID, user information (user ID, email address, group, name, etc.) of the customer who created the plan, creation date, last update date, deletion date, category, publication state, name, use, basic items, the number of downloads of various documents (specification description, single-line connection diagram, spec information, outline drawing), and the detailed plan ID of the detailed plan corresponding to the plan are associated. Here, creation, update, deletion, document download, inquiry, etc. of a plan are examples of user actions on a design plan. A detailed plan is a plan expressed by more detailed design items that is generated by the detailed design device 10 based on a plan generated by the design support device 30. A detailed plan ID is an ID for identifying a detailed plan stored in the database 14 of the detailed design device 10 as the first place. The design support device 30 may narrow down the period for counting the number of downloads of various documents. For example, the design support device 30 may record the number of downloads in the most recent month or in a period specified by the designer in the plan list file. The designer can check the frequency of use of the design plan from, for example, the number of downloads and logins of various documents. The designer can analyze each plan based on the plan list file. For example, the designer can estimate the plan that is being considered from the number of downloads of various documents included in the plan list file. In addition, since a detailed plan ID is associated with the plan list file, the designer can use the detailed design device 10 to edit a detailed plan based on the plan. In addition, the detailed design device 10, the design support device 30, or an external analysis device may have a function of performing analysis based on the information in the plan list file. For example, the detailed design device 10, the design support device 30, or an external analysis device may generate analysis data that represents a ranking by tallying up the number of multiple basic items by purpose for the most recent year. The detailed design device 10, the design support device 30, or an external analysis device may generate analysis data that represents a ranking of design plans, customer names, or groups with a large number of actions such as the number of downloads.The design support device 30 presents the generated analysis data to the designer.

[0040] When the inquiry download button V26 in Fig. 20 is pressed, the design support device 30 generates an inquiry list file representing inquiries related to all plans displayed in the list, and transmits the generated inquiry list file to the designer terminal T1. The inquiry list file may be, for example, CSV data. Downloading of the inquiry list file is permitted for the designer, but not for the customer.

[0041] FIG. 22 is a diagram showing an example of an inquiry list file according to the first embodiment. The inquiry list file is a file in which an inquiry ID, a plan ID, user information of the customer who made the inquiry (user ID, email address, group, name, etc.), an inquiry date, a plan category, a name, a purpose, an inquiry category, an inquiry content, and an attachment are associated with each inquiry. A designer can consider improvements to the functions of a service based on the inquiry list file. In addition, the detailed design device 10, the design support device 30, or an external analysis device may have a function of performing an analysis based on information in the inquiry list file. For example, the detailed design device 10, the design support device 30, or an external analysis device may generate analysis data that tally up the number of inquiry categories by purpose for the most recent year. The design support device 30 displays the analysis data, allowing the designer to understand the problems customers have for each purpose.

[0042] When the result output button V17 is pressed on the designer library screen, the design support device 30 causes the designer terminal T1 to display a result output screen, as shown in FIG. 23. The designer result output screen displays the management number, installation area, rough estimate, and system diagram of the plan. The rough estimate represents the total cost of the entire system. The result output screen includes a quote download button V27. When the download button V27 is pressed, the detailed design device 10 generates an estimate file representing the estimate and transmits it to the designer terminal T1.

[0043] Fig. 24 is a diagram showing an example of an estimate file according to the first embodiment. The estimate file includes the cost for each module constituting the system for each component unit, and the total cost. The rough estimate that the customer can check on the result output screen shown in Fig. 13 is the subtotal and grand total for each component unit. In other words, the designer can check the breakdown of the subtotal for each component unit presented to the customer.

[0044] The configuration of a design support system that provides the above-mentioned functions will be described below. FIG. 25 is a schematic software configuration diagram of the design support system according to the first embodiment. The detailed design device 10 includes a design-oriented UI 11, an application interface unit 12, a calculation unit 13, and a database 14.

[0045] The design UI 11 provides a user interface for the designer to operate the detailed design device 10. That is, the design UI 11 outputs an input screen for inputting the specification values ​​of the design specifications to the designer terminal T1 that has accessed the detailed design device 10. In the input screen, items that should be input and items that do not need to be input are switched according to the inputted specification values ​​of the design specifications. For example, the design UI 11 may not display items that do not need to be input, or may disable items that do not need to be input. This allows the designer to easily recognize items that should be input. The application interface unit 12 receives input of specification values ​​of the design specifications from the design support device 30 .

[0046] The calculation unit 13 judges whether or not it is necessary to input other items of the design specifications based on the inputted specification values ​​of the design specifications and the predetermined prohibition rules. Information on whether or not it is necessary to input determined by the calculation unit 13 is output by the design-oriented UI 11. The judgment of whether or not it is necessary to input based on the prohibition rules may be performed by the calculation unit 13 through asynchronous communication, or the judgment of whether or not it is necessary to input based on the prohibition rules may be performed by the designer terminal T1 through a script incorporated in the display data. A method of setting the prohibition rules will be described later. The prohibition rules may be stored in the database 14 or may be specified in a program. The calculation unit 13 calculates the specification values ​​of a huge number of design items based on the specification values ​​of the input design specifications. The calculation unit 13 identifies a combination of modules that can configure a power supply facility while satisfying the design specifications based on the specification values ​​of the design items, and generates various documents such as an estimate and a module table based on the combination of modules. In other words, the calculation unit 13 is an example of an identification unit that identifies modules that configure the power supply facility based on the specification values ​​of the design specifications. For example, the database 14 records, for each module, the model number and type (devices such as switchgears and transformers, and parts that configure the devices, etc.)) and the specification values ​​of various specification items (voltage, frequency, bus voltage, withstand voltage, etc.) in association with each other, and the calculation unit 13 identifies modules that configure the power supply facility by extracting modules that satisfy the specification values ​​of the design specifications from among the multiple modules recorded in the database 14.

[0047] For each detailed plan, the database 14 stores in association with each other a detailed plan ID that identifies the detailed plan, the specification values ​​of the input design specifications, the specification values ​​of the design items calculated by the calculation unit 13, and the power supply equipment composed of a combination of modules identified by the calculation unit 13.

[0048] The number of design items in the detailed design device 10 is enormous, and a certain level of knowledge and experience is required, so it is difficult for a customer who is unfamiliar with design to directly access the detailed design device 10 using the customer terminal T2 to design power supply equipment. On the other hand, a designer can make fine adjustments to the design of the power supply equipment by directly accessing the detailed design device 10 using the designer terminal T1. The designer can generate a standard plan by performing design using the design support device 30. The designer may also adjust the design plan generated by the customer using the detailed design device 10.

[0049] The design support device 30 includes a support UI 31, a calculation unit 32, an application interface unit 33, and a database .

[0050] The support UI 31 provides a user interface for the customer to operate the design support device 30. That is, the support UI 31 outputs a new plan creation screen, a My Page screen, a library screen, and the like to the customer terminal T2 that has accessed the design support device 30.

[0051] The new plan creation screen accepts input of specification values ​​of the requirement specifications. The requirement specifications have fewer items than the design specifications. For example, the number of items in the requirement specifications may be less than 100. The items in the requirement specifications include basic items and detailed items. The basic items are requirement specification items that are essential in the outline design of electrical equipment. The detailed items are requirement specification items for making more detailed settings in the design of electrical equipment. The number of basic items is fewer than the number of detailed items. The number of basic items may be, for example, about 10-14 items, and the number of detailed items may be, for example, about 40-60 items. The support UI 31 presents the customer with an input screen for basic items and accepts input of specification values ​​of the basic items from the customer. As shown in Figs. 4 to 11, the input screen for basic items accepts input of specification values ​​for one item per page, and transitions to a page related to the next item when input is accepted. After input of the basic items is completed, the support UI 31 presents a schematic configuration of the electrical equipment calculated based on the input specification values ​​of the basic items, as shown in Fig. 12. The schematic configuration of the electrical equipment is identified by the detailed design device 10 based on design specifications estimated from the specification values ​​of the basic items. Thereafter, the support UI 31 accepts input of specification values ​​of detailed items from the customer as necessary. That is, the support UI 31 is an example of an input unit that accepts input of values ​​of a plurality of required specifications related to a product from a customer.

[0052] When the customer inputs specification values ​​for at least the basic items of the required specifications, the calculation unit 32 can set specification values ​​for all items by estimating the specification values ​​of the detailed items from the specification values ​​of the basic items. The calculation unit 32 estimates specification values ​​of items (other items) of the required specifications that have not been input based on the specification values ​​of the input required specifications. For example, the calculation unit 32 estimates specification values ​​of detailed items based on the specification values ​​of basic items. The calculation unit 32 is an example of an identification unit that identifies modules that constitute a product based on the specification values ​​of the required specifications. The calculation unit 32 is also an example of a recording unit that records a design plan that associates the specification values ​​of the required specifications with modules in a database. The calculation unit 32 performs a login process for the customer based on the information input by the customer.

[0053] The application interface unit 33 determines the specification values ​​of the design items based on the specification values ​​of the required specifications input via the support UI 31 and the specification values ​​of the required specifications estimated by the calculation unit 32. As described above, the detailed design device 10 is a device that determines a combination of modules that satisfies the design specifications from the specification values ​​of more than 1,000 design items. The application interface unit 33 transmits the determined specification values ​​of the required specifications to the detailed design device 10. The application interface unit 33 receives deliverables (such as a combination of modules that satisfies the design specifications and a document generated based on the combination of modules) generated based on the specification values ​​of the design specifications from the detailed design device 10.

[0054] The database 34 stores a plan table that stores plans, a user table that stores information about customers, a query table that stores queries from customers, and a matching table.

[0055] FIG. 26 is a diagram illustrating an example of a plan table according to the first embodiment. The plan table stores, for each plan, a plan ID that identifies the plan, a user ID that identifies the user as ownership information of the plan, the customer management number of the plan, the status of the plan, whether or not it can be viewed by other users, the name of the plan, the creation date, the last update date, the deletion date, the use of the power supply equipment, the specification value of the required specifications input via the support UI 31, the module combination, the number of downloads of various documents (specification description, single-line connection diagram, spec information, outline drawing), and the detailed plan ID in association with each other. The status of the plan may indicate the progress of input of basic items of the required specifications. For example, the status of the plan may be, for example, input of basic items is in progress, input of basic items is completed, input of detailed items is completed, etc. When input of basic items is in progress, the status of the plan may be represented by the number of the last screen on which input is completed among the input screens for basic items. The deletion date of the plan table indicates the date on which the plan was deleted. When the plan has not been deleted, the value of the deletion date may be a NULL value. The plan table may store specification values ​​of the required specifications related to the estimated items that have not been input, specification values ​​of the design specifications, and specification values ​​of the design specifications calculated by the detailed design device 10. On the other hand, these specification values ​​may not be stored in the plan table because they can be recalculated from the specification values ​​of the input required specifications. The plan list file shown in FIG. 21 is generated by combining the information in the plan table shown in FIG. 26 and the information in the user table shown in FIG.

[0056] The plans stored in the plan table include standard plans that are generated by a designer and can be referenced by all users. For example, a value indicating whether the standard plan can be referenced by all users is recorded as a value indicating whether the standard plan can be viewed by other users. For example, the value of whether the standard plan can be viewed by other users may be 0 to indicate that the standard plan cannot be viewed by other users, 1 to indicate that the standard plan can be viewed by other users in the same group, and 2 to indicate that the standard plan can be referenced by all users. It is preferable that standard plans are prepared for all options for the use of the power supply equipment.

[0057] The plan stored in the plan table includes drawing plans that can be referenced by all users. The specification values ​​of the requirement specifications related to the drawing plans include values ​​that are not included in the options used in the design support system 1 for at least some items. In other words, the specification values ​​of the multiple items associated with the drawing plans include values ​​that are not included in the options that can be accepted when the design support device 30 creates a plan. In addition, the specification values ​​of the requirement specifications related to the drawing plans may have multiple values ​​in order to make the drawing plans more likely to be included in the search results. For example, when it is not desired to make a certain drawing plan dependent on the installation area, all selectable values ​​may be set as the specification values ​​of the installation area of ​​the drawing plan, or a wild card may be set. It is preferable that drawing plans are prepared for all options for the use of the power supply equipment. In the design support device 30, the options for the specification values ​​of the search form V19 in My Page or the library include standard options that can be selected when creating a plan, as well as specification values ​​that are not included in the options when creating a plan and are set only to the drawing plans. This makes it possible to search for drawing plans with special specifications by searching in My Page or the library. Note that the specification values ​​of the requirement specifications do not have to be associated with the drawing plans.

[0058] FIG. 27 is a diagram illustrating an example of a user table according to the first embodiment. In the user table, for each user, a user ID, a group ID that identifies a group to which the user belongs, user information such as the user's name and address, information used for login such as a password, user attributes, the registration date of the user ID, the last login date, and the number of logins are stored in association with each other. Examples of the group to which a user belongs include the company to which the user belongs and the department to which the user belongs. The user attributes indicate whether the user is a customer or a designer. The values ​​in the user table may be recorded by the designer, for example, when the customer signs a contract to use the design support system 1. This makes it possible to prevent a customer from intentionally setting a group ID of another group and viewing or copying unauthorized data. The customer list shown in Figure 19 is a combination of information extracted from the user table shown in Figure 27 whose attribute is customer, and the count of inquiries associated with that user ID in the inquiry table shown in Figure 28.

[0059] FIG. 28 is a diagram illustrating an example of a query table according to the first embodiment. The inquiry table stores an inquiry ID for identifying an inquiry, the user ID of the customer making the inquiry, the plan ID of the plan that is the subject of the inquiry, the inquiry category, the inquiry content, and an attachment, all of which are associated with each other. The inquiry list file shown in FIG. 22 is generated by combining the information in the inquiry table shown in FIG. 28, the information in the user table shown in FIG. 27, and the information in the plan table shown in FIG.

[0060] The matching table is a table showing the relationship between the plan created by the customer and the designer in charge of the design. The matching table stores the group ID of the customer, the use and installation area related to the plan, and the user ID of the designer in association with each other. Note that the use and installation area are optional items. In other words, the matching table is a table for identifying the user ID of the designer in charge from the group ID, use, and installation area related to the plan. A designer related to a row in which either the use or the design area is not a NULL value is a specialist contact person for the use or the design area in a certain group, and a designer related to a row in which both the use and the design area are NULL values ​​is a general contact person in a certain group. The matching table stores at least the user ID of the specialist contact person for all group IDs.

[0061] Here, the specification value of the requirement specification will be described. The detailed design device 10 and the design support device 30 specify the specification value of the requirement specification based on the initial value table (FIG. 29) and the prohibition rule table (FIG. 30) of each item of the requirement specification. The initial value table is a table that stores the initial values ​​of the requirement specification. The initial values ​​are determined without depending on the specification values ​​of other requirement specifications. The prohibition rule table is a table that stores the relationship between the specification value of the requirement specification, which is the objective variable, and the specification values ​​of other requirement specifications, which are explanatory variables. The specification value of the requirement specification related to the prohibition rule is determined by the specification values ​​of the other requirement specifications.

[0062] FIG. 29 is a diagram showing an example of an initial value table according to the first embodiment. As shown in FIG. 29, the initial value table associates item names with initial values ​​of the items. In the example of the initial value table shown in FIG. 29, for each option of one item, 1 is associated with the initial value, and 0 is associated with the non-initial value. The detailed design device 10 or the design support device 30 estimates the specification value of an item that has not been input based on the initial value table. In the example shown in FIG. 29, the specification items are presented as options, but input of numerical values ​​or character strings may be accepted. In this case, numerical values ​​or character strings may simply be associated with the item names as initial values.

[0063] Fig. 30 is a diagram showing an example of a prohibition rule table according to the first embodiment. As shown in Fig. 30, the prohibition rule table associates one or more item names related to explanatory variables with conditions for their specification values, and item names related to objective variables with estimated values ​​for their specification values. For example, when the selection of the receiving voltage shown in Fig. 6 is explained using the prohibition rules shown in Fig. 30, the explanatory variable is the power company and the objective variable is the receiving voltage. In the prohibition rule table, for each option of the power company, it is determined whether each option of the receiving voltage is selectable or not, and whether it is set as an initial value or not. The condition for the specification value of the explanatory variable takes one of the following values: selected (indicated by "●" in FIG. 30) and not selected (indicated by a blank space in FIG. 30). The estimated value for the specification value of the objective variable takes one of the following values: not included in the options (indicated by "×" in FIG. 30), included in the options but not selected as the initial value (indicated by "○" in FIG. 30), and included in the options and selected as the initial value (indicated by "◎" in FIG. 30). In other words, the prohibition rule table associates a condition for the specification value of an item related to the explanatory variable (a combination of specification values ​​when there are two or more explanatory variables), whether or not an item related to the objective variable is included in the options when that condition is satisfied, and an estimated value indicating the initial value of that item.

[0064] For example, in Example 1 shown in FIG. 30, for a combination of option A1 of item A and option B1 of item B, which are explanatory variables, "◎" is associated with option C1 of item C, which is the objective variable, and "○" is associated with the other options C2-C4. This indicates that when option A1 of item A and option B1 of item B are selected, options C1-C4 of item C are made selectable, and the specification value of item C is estimated to be C1. For example, in the case where item A is the receiving voltage, item B is the main transformer capacity, and item C is the configuration of the high voltage unit, when the specification value of the receiving voltage is A1 and the specification value of the main transformer capacity is B1 on the selection screen for the configuration of the high voltage unit shown in FIG. 9, options C1-C4 are displayed as selectable options as the configuration of the high voltage unit, and option C1 is set as the initial value.

[0065] Also, for example, in Example 2 shown in FIG. 30, for a combination of option A2 of item A and option B1 of item B, which are explanatory variables, “x” is associated with option C1 of item C, which is an objective variable, “o” is associated with options C2 and C3, and “◎” is associated with option C4. This indicates that when option A2 of item A and option B1 of item B are selected, options C2-C4 of item C are made selectable, and the specification value of item C is estimated to be C4. In this case, option C1 does not need to be displayed as an option. For example, in the case where item A is the receiving voltage, item B is the main transformer capacity, and item C is the configuration of the high-voltage unit, when the specification value of the receiving voltage is A2 and the specification value of the main transformer capacity is B1 on the selection screen of the configuration of the high-voltage unit shown in FIG. 9, options C2-C4 are displayed as selectable options as the configuration of the high-voltage unit, and option C4 is set as the initial value. Option C1 does not need to be displayed on the selection screen, or may be displayed grayed out.

[0066] Also, for example, in Example 3 shown in FIG. 30, for a combination of option A2 of item A and option B3 of item B, which are explanatory variables, "x" is associated with options C1-C3 of item C, which is the objective variable, and "◎" is associated with option C4. This indicates that when option A2 of item A and option B3 of item B are selected, the specification value of item C is determined to be C4. At this time, item C may be made non-inputtable. For example, in a case where item A is the receiving voltage, item B is the main transformer capacity, and item C is the configuration of the high-voltage unit, if the specification value of the receiving voltage is A2 and the specification value of the main transformer capacity is B3 on the selection screen for the configuration of the high-voltage unit shown in FIG. 9, the configuration of the high-voltage unit is determined to be option C4. In this case, the selection screen for the configuration of the high-voltage unit shown in FIG. 9 may be skipped, or a screen in which only option C4 can be selected may be displayed.

[0067] Also, for example, in Example 4 shown in FIG. 30, for the combination of option A3 of item A, which is an explanatory variable, and option B1 of item B, an "X" is associated with all of options C1-C4 of item C, which is an objective variable. This indicates that when option A3 of item A and option B1 of item B are selected, no value is selected for item C. In this case, item C does not need to be displayed.

[0068] The prohibition rule table stores at least rules that use basic items of the requirement specifications as explanatory variables and detailed items as objective variables, and rules that use the requirement specifications as explanatory variables and the design specifications as objective variables. The rules that use basic items as explanatory variables and detailed items as objective variables are used to estimate detailed items such as those shown in Fig. 12 from the specification values ​​of the basic items set in Fig. 5 to Fig. 9. The rules that use the requirement specifications as explanatory variables and the design specifications as objective variables are used by the design support device 30 to specify the design specifications from the specification values ​​of the requirement specifications so that the detailed design device 10 specifies a combination of modules. The prohibition rule table may further store rules that use basic items of the requirement specifications as explanatory variables and other basic items as objective variables, rules that use detailed items of the requirement specifications as explanatory variables and other detailed items as objective variables, rules that use combinations of basic items and detailed items of the requirement specifications as explanatory variables and other detailed items as objective variables, rules that use design specifications as explanatory variables and other items of the design specifications as objective variables, rules that use combinations of requirement specifications and design specifications as explanatory variables and other items of the design specifications as objective variables, etc. These rules are used when a customer inputs specification values ​​of detailed items of the requirement specifications, when a designer edits specification values ​​of the design specifications, etc.

[0069] The initial values ​​set in the initial value table and the prohibition rule table may be statistically determined based on the specification values ​​of the required specifications of electrical equipment previously designed. In this case, the initial value table and the prohibition rule table may be set for each customer. In other words, the initial value table and the prohibition rule table may be determined based on the specification values ​​of electrical equipment previously designed for that customer.

[0070] Next, the operation of the design support system 1 according to the first embodiment will be described. A user accesses the design support device 30 using a terminal T. The support UI 31 of the design support device 30 displays a login screen shown in FIG. 2. The user inputs a user ID and a password via the terminal T. The calculation unit 32 compares the input user ID and password with information recorded in a user table of the database 34 and performs a login process. If there is no user ID, the calculation unit 32 records information of the user in the user table of the database 34 based on an input from the user. The user ID and password may be input by the user or may be automatically generated.

[0071] When the user logs in, the support UI 31 generates a home screen shown in Fig. 3 and presents it to the user. At this time, the calculation unit 32 updates the last login date and the number of logins of the user stored in the user table of the database 34. The home screen includes a create new plan button V11, a my page button V12, and a library button V13. If the attribute of the logged-in user is a designer, the home screen further includes a customer management button V22 as shown in Fig. 18. When the create new plan button V11 is pressed, the design support device 30 accepts input of information for a new plan.

[0072] Fig. 31 is a flowchart showing a process for creating a new plan in the design support system 1 according to the first embodiment. Fig. 32 is a flowchart showing a process for editing detailed items in the design support system 1 according to the first embodiment.

[0073] When creation of a new plan is selected from the home screen, the support UI 31 displays an input screen for receiving input of the management number, name, and purpose of the plan from the user as shown in FIG. 4, and receives the input (step S0). Examples of the purpose include an office building, a commercial building, and the like. In this case, the input screen may include an input form for basic items. For example, the input screen shown in FIG. 4 includes an input form for the installation area, which is one of the basic items. The calculation unit 32 creates a plan ID for the plan, and records the plan ID in the plan table of the database 34 in association with the user ID, management number, creation date, last update date, name, and purpose. The calculation unit 32 also records the status of the plan as "draft" in the database 34.

[0074] Next, the design support device 30 accepts input of basic items of the required specifications. For example, an input screen for the basic items as shown in FIG. 5 to FIG. 9 is prepared for each item, and the design support device 30 displays a plurality of input screens in accordance with the display order. For example, the design support device 30 outputs an input screen for basic item B (for example, a selection screen for the receiving voltage shown in FIG. 6) after the specification value of the basic item A is input in an input screen for basic item A (for example, a selection screen for the power receiving voltage shown in FIG. 5). Note that, when a prohibition rule that specifies the relationship between two basic items is set, the display order of the input screen for the item related to the objective variable is set after the input screen for the item related to the explanatory variable. For example, since a prohibition rule that sets the power company as the explanatory variable and the receiving voltage as the objective variable is set in the prohibition rule table, the selection screen for the receiving voltage is displayed after the selection screen for the power company.

[0075] The calculation unit 32 specifies the basic items for which the input screen should be displayed according to a predetermined display order (step S1). That is, the calculation unit 32 specifies the basic item that is the earliest in the display order and is not yet set as the basic item for which the input screen should be displayed. The calculation unit 32 judges whether or not there is a prohibition rule with the specified basic item as the objective variable (step S2). If there is no prohibition rule with the specified basic item as the objective variable (step S2: NO), the calculation unit 32 determines the initial value of the basic item according to the initial value table (step S3). That is, if the basic item specified in step S1 cannot be obtained from the specification values ​​of other basic items that have been input, the calculation unit 32 determines the initial value of the basic item specified in step S1 as the value of the initial value table. For example, if the power receiving method, which is one of the basic items, is not limited by other basic items that have been input, such as the power company, whether it is single-line power receiving or dual-line power receiving, the calculation unit 32 sets the power receiving method (e.g., dual-line power receiving) specified in the initial value table as the initial value.

[0076] On the other hand, if there is a prohibition rule that uses the identified basic item as the objective variable (step S2: YES), the calculation unit 32 determines selectable options and initial values ​​(estimated values) of the basic item from the values ​​of the explanatory variables based on the prohibition rule (step S4). For example, since the power company limits the selectable options for the receiving voltage, which is one of the basic items, the calculation unit 32 sets selectable options and initial values ​​according to the prohibition rules defined in the prohibition rule table. The calculation unit 32 determines whether or not there is a selectable option (step S5).

[0077] If there is no prohibition rule (step S2: NO), or if there is a selectable option after applying the prohibition rule (step S5: YES), the support UI 31 transmits the input screen for the basic items identified in step S1 (e.g., FIG. 5 to FIG. 9) to the customer terminal T2 (step S6).

[0078] When the support UI 31 accepts input of specification values ​​of basic items from the customer terminal T2 (step S7), the calculation unit 32 updates the plan table in the database 34 based on the specification values ​​entered in association with the plan ID of the plan. When the support UI 31 receives input of specification values ​​of basic items from the customer terminal T2 (step S7), or when the input screen of the basic items is skipped because there are no selectable options in step S5 (step S5: NO), the calculation unit 32 judges whether there is a basic item for which an input screen should be displayed next (step S8). When there is a basic item for which an input screen should be displayed next (step S8: YES), the process returns to step S1, and the process for the next basic item is performed. The customer may interrupt the plan creation process in the middle of inputting the specification values ​​of the basic items.

[0079] On the other hand, if there are no basic items to be displayed next (step S8: NO), that is, if input to all basic items has been completed, the calculation unit 32 updates the plan table in the database 34 based on the input values ​​of the basic items (step S9). Next, the calculation unit 32 calculates the estimated values ​​of the detailed items from the input specification values ​​of the basic items based on the prohibition rules (step S10). At this time, the calculation unit 32 generates three combinations of the estimated values ​​of the detailed items. Specifically, the calculation unit 32 generates a combination that balances reliability and cost (balanced type), a combination that emphasizes reliability (reliability-oriented type), and a combination that emphasizes cost (cost-oriented type). Furthermore, the calculation unit 32 calculates the estimated values ​​of the design specifications from the input values ​​of the basic items and the estimated values ​​of the detailed items based on the prohibition rules (step S11). That is, the calculation unit 32 calculates the estimated values ​​of the design specifications for each of the three combinations of the estimated values ​​of the detailed items. That is, the calculation unit 32 identifies multiple configurations with different performance of the electrical equipment based on the input values ​​of the required specifications that have been input and the estimated values ​​of the required specifications that have not been input. The application interface unit 33 transmits design instructions including the purpose of the power supply facility and the calculated estimated values ​​of the three sets of design specifications to the detailed design device 10 (step S12).

[0080] When the application interface unit 12 of the detailed design device 10 receives a design instruction from the design support device 30 (step S13), the calculation unit 13 automatically generates values ​​of design items required by the detailed design device 10 based on the design specifications included in the received design instructions. The number of design items required by the detailed design device 10 exceeds 1000 items, for example. The calculation unit 13 identifies a combination of modules that satisfies the design specifications based on the generated design item values ​​(step S14). This is equivalent to the calculation unit 13 identifying modules based on the input values ​​of the already inputted required specifications and the estimated values ​​of the not yet inputted required specifications when the specification values ​​are input for some required specifications. At this time, the calculation unit 13 generates a configuration diagram of the power supply facility based on the identified combination of modules and calculates the standard price and installation area. That is, the calculation unit 13 identifies a combination of modules for each of the three sets of design specifications and calculates the configuration diagram, standard price, and installation area for the combination. The calculation unit 13 also determines whether there is any inconsistency in the specification values ​​of the design specifications based on the prohibition rules. Furthermore, when there is an item for which there are options for module combinations that can satisfy the design specifications, the calculation unit 13 determines the option based on the application included in the design instructions. For example, when there are multiple module combinations that satisfy the design specifications, the calculation unit 13 selects a highly reliable module combination when the application is a hospital, etc., and selects a low-cost module combination when the application is a commercial facility, etc. In other words, the calculation unit 13 determines the modules based on the specification values ​​of the required specifications and the application. The application interface unit 12 transmits the calculation result to the design support device 30 (step S15).

[0081] When the application interface unit 33 of the design support device 30 receives the three sets of calculation results from the detailed design device 10 (step S16), the support UI 31 generates an input screen (FIG. 11) that presents the received calculation results while allowing the customer to select one of the three plans, balanced, reliability-oriented, and cost-oriented, and outputs the screen to the customer terminal T2. At this time, the configuration diagram, standard price, and installation area included in the calculation results are displayed in association with each plan. The calculation unit 32 determines the initial values ​​of the plan based on the purpose input in step S0. That is, the calculation unit 32 specifies estimated values ​​for items of the required specifications that have not been input based on the purpose.

[0082] When the support UI 31 accepts the selection of a plan from the customer terminal T2 (step S17), it transmits an input screen (FIG. 12) for the detailed items of the required specifications related to the selected plan to the customer terminal T2 (step S18). The estimated values ​​of the design specifications identified in step S10 are set as initial values ​​on the input screen for the detailed items. Also, items for which all options are unselectable may be displayed in a disabled state (e.g., grayed out). Items for which all options are unselectable may not be displayed. The support UI 31 accepts input for either changing the specification values ​​of the detailed items or saving the plan (step S19).

[0083] When the specification value of a detailed item is changed (step 19: change), that is, when the specification value of the input form V1 of the detailed item shown in Fig. 12 is changed and the update button V5 is pressed, the calculation unit 32 calculates the selectability and estimated value of the options of other detailed items from the input specification value of the detailed item based on the prohibition rules (step S20). Next, the calculation unit 32 determines whether there are other detailed items whose input values ​​have subsequently become unselectable due to the change in the specification value of the detailed item (step S21).

[0084] If there are other detailed items whose input values ​​have subsequently become unselectable due to the change in the specification value of the detailed item (step S21: YES), the design support device 30 returns the process to step S18 and continues displaying the input screen. At this time, the support UI 31 may display a warning on the input screen indicating that there are items that have subsequently become unselectable.

[0085] On the other hand, if there are no other detailed items whose input values ​​have subsequently become unselectable (step S21: NO), the calculation unit 32 calculates the estimated value of the design specification from the input values ​​of the basic items and detailed items and the estimated values ​​of the other detailed items based on the prohibition rules (step S22).Then, the application interface unit 33 transmits a design instruction including the estimated value of the design specification to the detailed design device 10 (step S23).

[0086] When the application interface unit 12 of the detailed design device 10 receives a design instruction including the design specification from the design support device 30 (step S24), the calculation unit 13 identifies a combination of modules that satisfies the design specification based on the received design specification (step S25). The application interface unit 12 transmits the calculation result to the design support device 30 (step S26).

[0087] When the application interface unit 33 of the design support device 30 receives the calculation result from the detailed design device 10 (step S27), the design support device 30 returns the process to step S18 and updates the input screen for the detailed items of the requirement specifications. In other words, when a new input value is input to at least one of the multiple requirement specifications, the calculation unit 32 updates the estimated value of the requirement specifications that have not been input. Note that the screen update in steps S20-S27 may be performed by asynchronous communication through execution of a script embedded in the display data.

[0088] When saving of the plan is selected in step S19 (step 19: save), that is, when the save button V6 in FIG. 12 is pressed, the calculation unit 32 rewrites the status of the plan to "Complete", updates the last update date, and updates the plan table in the database 34 to indicate whether or not the plan can be viewed by other customers, as indicated by the check box V21 (step S29). The calculation unit 32 also calculates a combination of modules that satisfies the design specifications from the input values ​​of the basic items and detailed items and the estimated values ​​of other detailed items based on the prohibition rules (step S30). Then, the application interface unit 33 transmits a save instruction including the plan ID and the estimated values ​​of the design specifications to the detailed design device 10 (step S31).

[0089] When the application interface unit 12 of the detailed design device 10 receives a save instruction (step S31), the calculation unit 13 automatically generates values ​​of design items requested by the detailed design device 10 based on the design specifications included in the received save instruction. The calculation unit 13 identifies a combination of modules based on the generated values ​​of the design items (step S32). Then, the calculation unit 13 generates a new detailed plan ID, and records the plan ID included in the received save instruction, the values ​​of the design items, and the identified combination of modules in association with each other in the database 14 (step S33). The detailed design device 10 transmits the generated detailed plan ID to the design support device 30, and the design support device 30 updates the detailed plan ID of the plan in the plan table.

[0090] As a result, by inputting at least the basic items of the required specifications, the customer can easily obtain a rough estimate of the configuration diagram, standard price, and installation area of ​​the power supply equipment, since the design support device 30 estimates the specification values ​​of the detailed items and a combination of modules that satisfy the design specifications based on these. Furthermore, by inputting the detailed items of the required specifications, the customer can consider the configuration diagram, standard price, and installation area in more detail. In this case, too, since the design support device 30 estimates the specification values ​​of other items by inputting some of the specification values ​​of the detailed items, the specification values ​​of the design specifications can be updated without inputting all of the detailed items.

[0091] When the creation of the plan is completed, the support UI 31 transmits a result output screen (FIG. 13) related to the created plan to the customer terminal T2 (step S34).

[0092] The result output screen is provided with download buttons for the specification, single-line connection diagram, external dimensions, mass, heat value, transformer entry dimensions, and maintenance space description. However, the data for the specification, single-line connection diagram, external dimensions, mass, heat value, transformer entry dimensions, and maintenance space description may not be generated at the time when the result output screen is displayed. These data are generated by the detailed design device 10, and may take time to generate. Furthermore, the customer does not necessarily need these data at the time when the result output screen is displayed. In another embodiment, the data for the specification, single-line connection diagram, external dimensions, mass, heat value, transformer entry dimensions, and maintenance space description may be generated by a device other than the detailed design device 10 and the design support device 30. Therefore, when the download button is pressed, the design support device 30 transmits a data creation request to the detailed design device 10 via the application interface unit 33. When the detailed design device 10 completes the creation of the data, the calculation unit 32 of the design support device 30 receives the data from the detailed design device 10 via the application interface unit 33 and transmits the data to the customer terminal T2. In other words, the calculation unit 32 is an example of a document presentation unit that generates a document showing the configuration of a product related to the design plan and presents it to the customer. At this time, the calculation unit 32 increments the number of downloads of the document associated with the plan ID of the plan in the plan table.

[0093] When the customer presses the edit button V15 on the result output screen, the calculation unit 32 moves the process to step S18 in FIG. 32, generates an input screen for detailed items in the support UI 31, and transmits it to the customer terminal T2.

[0094] When the My Page button V12 is pressed on the home screen shown in FIG. 3, the design support device 30 displays the My Page screen in the following procedure.

[0095] First, the calculation unit 32 reads out plan information associated with the user ID of the logged-in customer from the database 34. The support UI 31 generates a My Page screen including a list of the read plans as shown in Fig. 14, and transmits it to the customer terminal T2. In the initial display state of the My Page screen, since none of the plans included in the list are selected, information on any of the plans does not need to be displayed on the detail display panel V7.

[0096] When a customer inputs search conditions into the input form of the search form V19 and presses the search button, the calculation unit 32 reads out information on plans that are associated with the user ID of the logged-in customer from the database 34 and that satisfy the conditions input into the search form V19. The support UI 31 updates the list on the My Page screen based on the read out information.

[0097] When the customer selects any plan included in the list, the support UI 31 identifies the plan ID of the selected plan. The support UI 31 identifies the plan associated with the identified plan ID from the information of the customer's plans already read by the calculation unit 32, and displays the plan ID on the detail display panel V7. The support UI 31 enables the edit button V15 and the duplicate button V18 of the detail display panel V7. That is, the support UI 31 allows the logged-in customer to update a plan associated with ownership information matching the user ID of the customer, among multiple design plans stored in the database 34. Furthermore, when the status related to the identified plan ID is "Complete", the support UI 31 enables the inquiry button V16 and the result output button V17 of the details display panel V7.

[0098] When the edit button V15 is pressed by the customer, the calculation unit 32 judges whether the status of the selected plan is "draft". If the status is "draft", the calculation unit 32 judges whether there is any basic item in the request specification that has not been input. If there is any basic item that has not been input, the calculation unit 32 moves the process to step S1 in FIG. 31, and the support UI 31 generates an input screen for the basic items and transmits it to the customer terminal T2. If there is no basic item that has not been input, the calculation unit 32 moves the process to step S18 in FIG. 32, and the support UI 31 generates an input screen for the detailed items and transmits it to the customer terminal T2. On the other hand, if the status of the selected plan is not "draft", the support UI 31 generates a result output screen shown in FIG. 13 and transmits it to the customer terminal T2. In other words, the support UI 31 determines the input screen for the specification value based on the progress of the plan. When the customer presses the inquiry button V16, the assistance UI 31 generates an inquiry screen (FIG. 16) based on the information of the selected plan, and transmits it to the customer terminal T2. When the customer presses the result output button V17, the assistance UI 31 generates a result output screen based on the information of the selected plan and transmits it to the customer terminal T2. When the customer presses the copy button V18, the calculation unit 32 copies the data of the selected plan recorded in the database 34. The calculation unit 32 creates a new plan ID for the copied data and updates it.

[0099] When the library button V13 is pressed on the home screen shown in FIG. 3, the design support device 30 displays the library screen in the following procedure.

[0100] First, the calculation unit 32 reads out plan information associated with the user ID of the logged-in customer from the database 34. The calculation unit 32 also reads out plan information associated with the group ID of the group to which the logged-in customer belongs and for which the value of whether or not the plan can be viewed by other customers indicates "permitted" from the database 34. The calculation unit 32 also reads out standard plan and drawing plan information from the database 34. The support UI 31 generates a library screen including a list of the read plans as shown in FIG. 17 and transmits it to the customer terminal T2. In other words, the support UI 31 allows the presentation of multiple plans (plans, standard plans, and drawing plans generated by other customers in the same group) recorded in the database 34 to the logged-in customer, regardless of whether the user ID of the logged-in customer matches the ownership information. In the initial display state of the library screen, since none of the plans included in the list are selected, information about any of the plans does not need to be displayed in the details display panel V7.

[0101] When a customer inputs search conditions into the input form of the search form V19 and presses the search button, the calculation unit 32 reads out from the database 34 information on plans that are associated with the user ID of the logged-in customer and satisfy the conditions input into the search form V19, plans that are associated with the group ID of the group to which the logged-in customer belongs and for which the value of whether or not viewing is permitted by other customers and satisfy the conditions input into the search form V19, and standard plans and drawing plans that satisfy the conditions input into the search form V19. The support UI 31 updates the list on the library screen based on the read information.

[0102] When a plan included in the list is selected by the customer, the support UI 31 identifies the plan ID of the selected plan. From the information of the customer's plans already read by the calculation unit 32, the support UI 31 identifies the plan associated with the identified plan ID, and displays it on the detail display panel V7. The support UI 31 activates the inquiry button V16 and the result output button V17 on the detail display panel V7. Furthermore, if the identified plan is not a drawing plan, the support UI 31 activates the copy button V18.

[0103] When the customer presses the inquiry button V16, the assistance UI 31 generates an inquiry screen (FIG. 16) based on the information of the selected plan and sends it to the customer terminal T2. The inquiry category and inquiry content are entered on the inquiry screen, and an attachment is uploaded optionally. When the send button is pressed, the calculation unit 32 generates a new inquiry ID, and records the customer's user ID, the plan ID of the selected plan, the inquiry category, the inquiry content, and the attachment in the inquiry table in association with the inquiry ID. In other words, the calculation unit 32 is an example of an inquiry unit that accepts input of an inquiry about a design plan from a customer. The calculation unit 32 reads the group ID associated with the user ID related to the inquiry from the user table of the database 34, and reads the use and installation area associated with the plan ID related to the inquiry from the plan table of the database 34. The calculation unit 32 reads the user ID of the designer in charge from the matching table of the database 34 based on the read group ID, use, and installation area. The calculation unit 32 reads the email address associated with the read user ID from the user table of the database 34, and sends an email to the email address to notify the occurrence of a new inquiry. In other words, the calculation unit 32 is an example of a sending unit that sends information on the design plan recorded in the database 34 to the designer. Note that a representative account of the infrastructure business operator may be set as the person in charge, and emails arriving at the representative email address may be manually assigned to the actual person in charge. The calculation unit 32 sends information on the design plan when it receives an inquiry about the design plan. This allows the designer in charge to know that a new inquiry has occurred. At this time, the calculation unit 32 may notify the responsible designer of the inquiring customer's usage history of the design support device 30 (such as the date of registration of the user ID, the last login date, and the number of logins) and aggregated data of plans created in the past by the customer.

[0104] The calculation unit 32 may notify the responsible designer at a timing other than the occurrence of an inquiry. For example, the calculation unit 32 may notify the responsible designer that the number of times the same plan has been viewed by the customer exceeds a predetermined threshold (for example, 10 times). For example, the calculation unit 32 may notify the responsible designer that a document related to the plan has been downloaded when the customer downloads a document such as a usage specification, a single-line connection diagram, or an outline drawing. The fact that a document has been downloaded means that the plan is likely to be considered based on the document. For example, the calculation unit 32 may notify the responsible designer of information on the plan when the customer has not updated the plan for a predetermined period (for example, three months). This allows the designer to check the progress of the plan with the customer.

[0105] When the customer presses the result output button V17, the assistance UI 31 generates a result output screen based on the information of the selected plan and transmits it to the customer terminal T2. When the customer presses the copy button V18, the calculation unit 32 copies the data of the selected plan recorded in the database 34. The calculation unit 32 creates and updates the plan ID of the copied data. The calculation unit 32 also updates the ownership information of the copied data with the user ID of the logged-in customer.

[0106] When the customer management button V22 is pressed on the designer home screen shown in FIG. 18, the design support device 30 displays the customer management screen in the following procedure. First, the calculation unit 32 reads out the user ID, email address, group, name, registration date, last login date, and number of logins related to a user whose attribute is a customer from the user table. The calculation unit 32 calculates the number of tuples associated with each of the read user IDs in the plan table, and calculates the number of plans. A tuple is a set of data that represents a row of a table. The calculation unit 32 calculates the number of tuples associated with each of the read user IDs in the inquiry table, and calculates the number of inquiries. The support UI 31 generates a customer management screen including a customer list V23 associated with user IDs, email addresses, groups, names, registration dates, last login dates, number of logins, number of plans, and number of inquiries, and transmits it to the designer terminal T1. When the designer presses the download button V24, the calculation unit 32 generates a customer list file indicating the user ID, email address, group, name, registration date, last login date, number of logins, number of plans, and number of inquiries, and transmits it to the designer terminal T1. In other words, the calculation unit 32 is an example of a transmission unit that transmits customer information recorded in the database 34 to the designer.

[0107] When the library button V13 is pressed on the designer home screen shown in FIG. 18, the design support device 30 displays the library screen in the following procedure.

[0108] First, the calculation unit 32 reads out information on all plans from the database 34. The support UI 31 generates a library screen including a list of the read plans as shown in Fig. 20, and transmits it to the designer terminal T1. In the initial display state of the library screen, since none of the plans included in the list are selected, information on any of the plans does not need to be displayed on the detail display panel V7.

[0109] When the designer inputs search conditions into the input form of the search form V19 and presses the search button, the calculation unit 32 reads out information about plans that satisfy the conditions input into the search form V19 from the plan table of the database 34. At this time, if the check box shown in Fig. 20 is off, the calculation unit 32 reads out information about plans that satisfy the conditions and have a NULL value for the deletion date. If the check box shown in Fig. 20 is on, the calculation unit 32 reads out information about plans that satisfy the conditions regardless of the value of the deletion date. The support UI 31 updates the list on the library screen based on the read information.

[0110] When the designer presses the plan download button V25, the design support device 30 generates a plan list file in the following procedure. The calculation unit 32 reads out information on plans that satisfy the conditions entered in the search form V19 from the plan table. For each read plan, the calculation unit reads out user information associated with the user ID from the user table. As a result, the calculation unit 32 can generate a plan list file that associates, for each plan, the plan ID, the user information of the customer who created the plan, the creation date, the last update date, the deletion date, the category, the publication state, the name, the purpose, the basic items, the number of downloads of various documents, and the detailed plan ID of the detailed plan corresponding to the plan, as shown in FIG. 21. Then, the calculation unit 32 transmits the generated plan list file to the designer terminal T1. In other words, the calculation unit 32 is an example of a transmission unit that transmits information on the design plan recorded in the database 34 to the designer.

[0111] Since the plan list file records the number of times each document has been downloaded, the design plan from which the document has been downloaded can be regarded as reliable data. Therefore, the designer can generate a database for comparing the plan list file with design plans previously requested, and analyze the data. The analysis may be performed manually by the designer, or may be performed by the detailed design device 10, the design support device 30, or an external analysis device. The designer may also classify the design plans from the plan list file by attributes and perform an analysis for each attribute. Examples of attributes include use, location, and user. If the preference trends of each user can be extracted by such analysis, the design support device 30 may be configured to present recommended design plans from the analysis results when the user selects the use.

[0112] When the designer presses the inquiry download button V26, the design support device 30 generates an inquiry list file in the following procedure. The calculation unit 32 reads out information on plans that satisfy the conditions entered in the search form V19 from the plan table. The calculation unit reads out inquiry information associated with the plan ID of the read plan from the user table. As a result, the calculation unit 32 can generate an inquiry list file that associates, for each inquiry, the inquiry ID, plan ID, user information of the customer who made the inquiry, inquiry date, plan category, name, purpose, inquiry category, inquiry content, and attachments, as shown in FIG.

[0113] Second embodiment In a company, the person in charge of electrical equipment may be changed due to transfer or the like. In such a case, the plan that was considered for the electrical equipment by the previous person in charge may not be carried over and may go to waste. In response to this, the design support device 30 according to the second embodiment presents plans that are highly likely to be related as reference information when creating a plan, thereby preventing the plan considered in the past from going to waste.

[0114] The calculation unit 32 according to the second embodiment creates a new plan in the procedure (steps S1 to S34) shown in Fig. 31 and Fig. 32, similarly to the first embodiment. Next, the calculation unit 32 calculates the degree of agreement between the new plan and the specification values ​​of the detailed items of the design specifications for each of the multiple plans stored in the plan table. The degree of agreement may be the ratio of items with the same specification values, or may be the similarity of the specification values. The calculation unit 32 extracts a plan that satisfies all of the following first to fifth conditions from among the multiple plans stored in the plan table. The first condition is that the degree of agreement of the specification value with the new plan is equal to or greater than a reference value (e.g., 80%). The reference value of the degree of agreement may be different between basic items and detailed items. For example, the reference value of the degree of agreement of the detailed items (e.g., 60%) may be lower than the reference value of the degree of agreement of the basic items (e.g., 80%). The second condition is that the plan was created by a customer who belongs to the same group as the creator of the new plan. The third condition is that the plan is permitted to be viewed by other users. The fourth condition is that the purpose is the same as that of the new plan. The fifth condition is that the plan was created before the new plan. The calculation unit 32 is an example of a determination unit that determines the degree of agreement and similarity with other stored design plans, and the conditions are not limited thereto.

[0115] As shown in FIG. 33, the support UI 31 displays a pop-up window presenting the extracted plan on the result output screen. The pop-up window may display the plan ID, group, name of the customer who created the extracted plan, creation date, name and purpose, a display button, and a close button. That is, the support UI 31 is an example of an associated plan presenting unit that determines whether or not another design plan similar to a certain design plan is stored in the database 34, and presents the other design plan in association with the certain design plan. When the display button of the pop-up window is pressed, the support UI 31 transitions the screen to a result output screen presenting the extracted plan. On the other hand, when the close button of the pop-up window is pressed, the support UI 31 closes the pop-up window and displays a result output screen presenting a new plan. This allows customers to review the plans created by their predecessors.

[0116] In the second embodiment, a plan that is highly likely to be related is presented when the customer creates a new plan, but this is not limited to the above. For example, in another embodiment, the calculation unit 32 may present a plan that is highly likely to be related to the designer when notifying the designer of information on the plan created by the customer. In this case, the support UI 31 extracts plans that satisfy the above first condition, fourth condition, and fifth condition from the multiple plans stored in the plan table. That is, the highly relevant plan that the support UI 31 presents to the designer may be created by a customer belonging to a different group from the creator of the new plan, or may not be permitted to be viewed by other users. The design support device 30 issues a notification to the designer, for example, when a new inquiry about a plan is received, when a certain period (e.g., three months) has passed since the customer logged out, when a new plan that is highly similar to an existing plan (e.g., 90% or more) is created by a customer belonging to a different group, etc. For example, when a design company orders electrical equipment construction of a building designed by the design company to a subcontractor, new plans with high similarity are created by customers belonging to different groups. Therefore, the design support device 30 according to the second embodiment can make the designer aware that the player has changed from the design company to the subcontractor, that is, that the design phase has moved from the basic design stage to the detailed design stage. In particular, in electrical equipment construction, the customer's person in charge may change depending on the design phase, and the infrastructure company's engineer in charge may change. Therefore, it is difficult to manage and link design information, and new designs may be made for the same project. The design support device 30 according to the second embodiment makes it possible to appropriately link with existing plans even when the player changes depending on the design phase.

[0117] In addition, in the design support system 1 according to another embodiment, the functions of the detailed design device 10 and the design support device 30 may be realized in one device as shown in FIG. 34. FIG. 34 is a schematic software configuration diagram of the design support system according to another embodiment. The design support system 1 includes a design-oriented UI 11, a support UI 31, a calculation unit 23, and a database 24. The calculation unit 23 has the function of the calculation unit 13 according to the first embodiment and the function of the calculation unit 32. The database 24 stores the data stored in the database 14 according to the first embodiment and the data stored in the database 34. According to the configuration shown in FIG. 25, the design support system 1 can accept the input of the required specifications by the customer and the input of the detailed design by the designer without communication via the application interface unit. In the design support system 1 according to another embodiment, the detailed design device 10 and the design support device 30 may not cooperate with each other, and each may have its own logic for determining a combination of modules from the specification values ​​of the design specifications.

[0118] According to at least one of the embodiments described above, the design support system 1 has the following features. The design support system 1 has an input unit (support UI 31), an identification unit (calculation unit 32), a recording unit (calculation unit 32), and a transmission unit (calculation unit 32). The input unit accepts input of specification values ​​of multiple items of required specifications related to a product from a customer. The identification unit identifies modules that constitute the product based on the specification values ​​of the required specifications. The recording unit records a design plan that associates the specification values ​​of the required specifications with the modules in a database (database 34). The transmission unit transmits information of the design plan recorded in the database to the designer. In this way, the design support system 1 can allow the designer in charge to recognize information about the system that the client is considering designing.

[0119] The detailed design device 10 includes a processor, a memory, an auxiliary storage device, etc., each connected by a bus, and functions as a device including a design-oriented UI 11, an application interface unit 12, and a calculation unit 13 by executing a program. The design support device 30 includes a processor, a memory, an auxiliary storage device, etc., each connected by a bus, and functions as a device including a support UI 31, an application interface unit 33, and a calculation unit 32 by executing a program. Examples of the processor include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor. The program may be recorded on a computer-readable recording medium. The computer-readable recording medium is, for example, a storage device such as a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. The program may be transmitted via a telecommunication line. All or part of the functions of the detailed design device 10 or the design support device 30 may be realized using a custom LSI (Large Scale Integrated Circuit) such as an ASIC (Application Specific Integrated Circuit) or a PLD (Programmable Logic Device). Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). Such integrated circuits are also included in the example of a processor.

[0120] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention. [Explanation of symbols]

[0121] REFERENCE SIGNS LIST 1...design support system 10...detailed design device 11...user interface section 12...application interface section 13...calculation section 14...database 30...design support device 31...user interface section 32...calculation section 33...application interface section 34...database N...communication network T...terminal T1...designer terminal T2...customer terminal

Claims

1. An input unit that receives input of specification values ​​of a plurality of items of required specifications related to the product from a customer; an identification unit that identifies modules that configure the product based on specification values ​​of the required specifications; a recording unit that records a design plan in which the specification values ​​of the required specifications and the modules are associated with each other in a database; a transmitting unit that transmits the information of the design plan recorded in the database to a designer; A design support system equipped with:

2. The transmission unit transmits the information of the client to the designer in addition to the information of the design plan. The design support system according to claim 1 .

3. The design plan information includes a history of the customer's actions on the design plan. The design support system according to claim 1 .

4. The customer information includes a history of the customer's actions on the design support system. The design support system according to claim 2 .

5. an inquiry unit that accepts an input of an inquiry regarding the design plan from the customer; The transmission unit, upon receipt of the inquiry, transmits information on the design plan related to the inquiry to the designer. The design support system according to any one of claims 1 to 4.

6. a document presentation unit that generates a document showing a configuration of a product related to the design plan and presents the document to the customer; The transmitting unit transmits information on the design plan related to the document to the designer when the document is presented to the client. The design support system according to any one of claims 1 to 4.

7. Transmitting an analysis result based on the information of the design plan to the designer. The design support system according to claim 1 .

8. Transmitting an analysis result based on the customer's information to the designer The design support system according to claim 2 .

9. an associated plan presenting unit that determines whether or not another design plan similar to the design plan is stored in the database, and presents the other design plan in association with the design plan; The design support system according to claim 1 , further comprising:

10. A step of receiving input of specification values ​​of a plurality of items of required specifications related to the product from a customer; identifying modules that configure the product based on specification values ​​of the required specifications; a step of recording a design plan in which the specification values ​​of the required specifications and the modules are associated with each other in a database; transmitting the information of the design plan recorded in the database to a designer; A design support method comprising:

11. On the computer, A step of receiving input of specification values ​​of a plurality of items of required specifications related to the product from a customer; identifying modules that configure the product based on specification values ​​of the required specifications; a step of recording a design plan in which the specification values ​​of the required specifications and the modules are associated with each other in a database; transmitting the information of the design plan recorded in the database to a designer; A program for executing the above.

Images