Management system, information processing apparatus, and program

Abstract

To provide a management system that improves the maintainability of a configurator.SOLUTION: A management system manages a configurator that selects candidate combinations of elements that configure a product. The management system comprises: a storage unit for storing configuration information that defines data related to the elements, data related to connections between the elements, and data related to constraints on the connections; and a control unit for selecting candidates for the combination based on a request received from a user and rules related to the combination of the elements generated from the configuration information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] An embodiment of the present disclosure relates to a management system, an information processing device, and a program. [Background technology]

[0002] A tool called a configurator is provided to determine product specifications based on customer requirements. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-15381 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present disclosure is to provide a management system that improves the maintainability of a configurator. [Means for solving the problem]

[0005] A management system according to an embodiment manages a configurator that selects candidate combinations of elements that constitute a product. The management system includes a storage unit that stores configuration information that defines data on the elements, data on connections between the elements, and data on constraints on the connections, and a control unit that selects the candidate combinations based on a request received from a user and rules for combining the elements that are generated from the configuration information. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram showing the functional configuration of a management system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of element data included in the configuration information. [Figure 3] FIG. 3 is a diagram illustrating an example of connection data included in the configuration information. [Figure 4] FIG. 4 is a diagram illustrating an example of constraint data included in the configuration information. [Figure 5] FIG. 5 is a flowchart showing the flow of the combination rule registration process in the management system. [Figure 6] FIG. 6 is a flow diagram showing the flow of a process for updating a combination rule in the management system. [Figure 7] FIG. 7 is a flowchart showing the flow of a process for selecting combination candidates in the management system. [Figure 8] FIG. 8 is a diagram showing an outline of a process for selecting combination candidates in the management system. [Figure 9] FIG. 9 is a diagram illustrating a hardware configuration of an information processing device included in the management system. [Figure 10] FIG. 10 is a block diagram showing the functional configuration of a management system according to the second embodiment. [Figure 11] FIG. 11 is a diagram showing an outline of the estimation in the second embodiment. [Figure 12] FIG. 12 is a flowchart showing the flow of the estimate calculation process in the second embodiment. [Figure 13A] FIG. 13A is a diagram illustrating an example of the estimate estimation information. [Figure 13B] FIG. 13B is a diagram showing another example of the estimate estimation information. [Figure 14] FIG. 14 is a flow diagram illustrating the flow of the process for generating estimate information. DETAILED DESCRIPTION OF THE INVENTION

[0007] <1. Embodiment> Each embodiment of the present disclosure will be described below with reference to the drawings. In this specification and each drawing, elements similar to those already described are designated by the same reference numerals, and detailed description will not be repeated. In this disclosure, a user refers to a person who determines product specifications and / or calculates an estimated cost based on those specifications using the configurator function provided by the management system 100. An administrator refers to a person who manages the management system 100. The user and the administrator may be different people or may be the same person.

[0008] (1.1. Functional Configuration of Management System 100) The functional configuration of a management system 100 according to an embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the management system 100 includes a terminal device 10 and a management device 20.

[0009] The terminal device 10 is an information processing device that includes input means and output means and can be operated by a user or an administrator. The terminal device 10 may be a general-purpose or dedicated personal computer, a smart device, or the like. Smart devices include tablet terminals, smartphones, smart glasses, smart watches, and the like. The hardware configuration of an information processing device that functions as the terminal device 10 will be described later.

[0010] The management device 20 is, for example, an information processing device that functions as a server. The management device 20 includes a control unit 30 and a storage unit 40. The control unit 30 serves as a processor and controls the processing of the management device 20. The control unit 30 includes a configurator module 31, a configuration information management module 32, and an estimate calculation module 33.

[0011] The configurator module 31 functions as a configurator that selects candidate combinations of multiple elements that constitute a product. Here, a product refers to any item that can be manufactured and traded commercially, and includes, for example, industrial products such as automobiles and home appliances, as well as factory equipment such as power plants and petrochemical plants. The configurator module 31 accepts a request from a user and presents to the user candidate combinations of multiple elements (specifically, multiple parts of a product) that satisfy the request.

[0012] The configuration information management module 32 has a function of managing the configuration information 41 stored in the storage unit 40. The configuration information 41 specifies data on the elements of a target product (hereinafter referred to as the target product), data on the connections between the elements, and data on constraints on the connections. The configuration information management module 32 adds, updates, deletes, etc. the configuration information 41 based on the operation of the terminal device 10 by the administrator.

[0013] The estimate calculation module 33 calculates an estimate for a product including the combination of parts selected by the configurator module 31. As an example, the estimate calculation module 33 adds up the estimated prices of the parts included in the combination selected by the configurator module 31 to estimate the entire product.

[0014] The storage unit 40 stores programs and data necessary for processing by the control unit 30, data obtained by processing by the control unit 30, etc. As an example, the storage unit 40 stores configuration information 41 and combination rules 42. As described above, the configuration information 41 includes data on the elements of the target product, data on the connections between the elements, and data on constraints on the connections. The combination rules 42 are rules on the combination of the elements of the target product, and are generated from the configuration information 41 by the configuration information management module 32.

[0015] (1.2.Configuration Information 41) The configuration information 41 will be described with reference to FIGS. 2 to 4. In this embodiment, the configuration information 41 is defined by a modeling language. A modeling language is a language designed based on common specifications and standards, and is used to model (i.e., abstract and visualize) systems, processes, data, etc. Examples include, but are not limited to, SysML (Systems Modeling Language) and UML (Unified Modeling Language). The specifications may be such that an administrator can select the most appropriate modeling language depending on the configuration of the target product, etc.

[0016] 2 is a diagram showing an example of element data 41A included in configuration information 41. The element data 41A is data related to elements included in the target product. As shown in FIG. 2, the element data 41A includes a plurality of element boxes 50. Each element box 50 corresponds to a component as an element included in the target product, or a module made up of a plurality of components.

[0017] The element box 50 includes a part name 50a and an accessory part 50b. The part name 50a is the name of the part as the element. The accessory part 50b is the name of the part that the element includes. As an example, the element data 41A shown in FIG. 2 has a tree structure, and the topmost element box 50 corresponds to the part "motor." The part "motor" includes, as accessory parts, a part "case module," a part "shaft," a part "fan module," a part "stator-rotor module," a part "terminal box," a part "bearing module," and a part "power supply."

[0018] The element box 50 further includes data on parameters associated with the element. A parameter refers to a variable or index for expressing the characteristics of a part as an element. Part characteristics include, but are not limited to, dimensions, performance, function, shape, and material (or quality of material). As an example, in the bottom row of element data 41A shown in FIG. 2, the element boxes 50 corresponding to the part "fan-side bearing" and the part "load-side bearing" each have a parameter box 51 corresponding to the parameter "bearing inner diameter." From this, it can be seen that the part "fan-side bearing" and the part "load-side bearing" each have a parameter called "bearing inner diameter." Note that there may be multiple fan bearing candidates, and each fan bearing may have a different bearing inner diameter parameter. Similarly, there may be multiple other parts with parameters, and the parameters they have may be different.

[0019] 3 is a diagram showing an example of connection data 41B included in configuration information 41. The connection data 41B is data regarding the connections between elements included in the target product. As shown in FIG. 3, the connection data 41B includes a plurality of element boxes 50 and connection lines 61 that connect the element boxes 50. The element boxes 50 connected by the connection lines 61 have a predetermined connection as parts of the product.

[0020] In the connection data 41B, an element box 50 may contain one or more other element boxes 50. For example, FIG. 3 shows that the part "bearing module" has a part "fan-side bracket," a part "fan-side bearing," a part "load-side bracket," and a part "load-side bearing." In this way, the connection data 41B visualizes the connections and inclusion relationships between the elements (i.e., parts) of the target product more clearly than the element data 41A.

[0021] A constraint box 60 can also be added to the connection line 61. The constraint box 60 corresponds to a constraint condition regarding the constraint on the connection between the element boxes 50. In the example shown in FIG. 3, a constraint box 60 is added to the part "fan side bearing" and the part "shaft", and to the part "load side bearing" and the part "shaft".

[0022] FIG. 4 is a diagram showing an example of constraint data 41C included in the configuration information 41. The constraint data 41C includes one or more constraint boxes 60. As shown in FIG. 4, the constraint box 60 includes a constraint name 60a and a condition content 60b. The constraint name 60a is the name of the constraint. The condition content 60b is the content of the condition. The condition content 60b includes a condition related to a parameter of the element to be linked.

[0023] In the example shown in Fig. 4, the condition "ConstraintBlock3" specifies as a constraint that the parameter "shaft diameter" and the parameter "bearing inner diameter" are equal. In other words, the constraint that the parameter "shaft diameter" and the parameter "bearing inner diameter" are equal is imposed on the connections between the part "fan-side bearing" and the part "shaft" and between the part "load-side bearing" and the part "shaft" in Fig. 3.

[0024] (1.3. Processing flow) The flow of processing in the management system 100 will be described with reference to Figures 5 to 8. Figure 5 is a flow diagram showing the flow of processing for registering a combination rule in the management system.

[0025] In step S110, the configuration information management module 32 registers data relating to the parts of the target product in the element data 41A of the configuration information 41 based on the operation of the terminal device 10 by the administrator.

[0026] In step S120, the configuration information management module 32 registers data relating to the connections between the components of the target product in the connection data 41B of the configuration information 41 based on the operation of the terminal device 10 by the administrator.

[0027] In step S130, the configuration information management module 32 registers data on constraints on connections between components in the constraint data 41C of the configuration information 41 based on the administrator's operation of the terminal device 10. Furthermore, the configuration information management module 32 assigns the constraint data 41C to the connections between elements in the connection data 41B.

[0028] In step S140, the configuration information management module 32 generates combination rules 42 regarding combinations of parts in the target product based on the element data 41A, connection data 41B, and constraint data 41C of the configuration information 41. As an example, the configuration information management module 32 may select combinations of parts that can satisfy the constraint data 41C from a group of parts made up of one or more parts by referring to the element data 41A and connection data 41B, and set the combination rules 42.

[0029] In step S150, the configuration information management module 32 determines whether the generated combination rule is appropriate. This determination may be performed automatically using a predetermined check tool or the like, or may be performed manually by an administrator checking the generated combination rule. If the combination rule is appropriate (YES in S150), step S160 is executed. On the other hand, if the combination rule is not appropriate (NO in S150), the combination rule update process shown in FIG. 6 is performed.

[0030] In step S160, the configuration information management module 32 registers the generated combination rule 42 in the storage unit 40. As a result, the combination rule 42 for the combination of parts of the target product is stored in the storage unit 40.

[0031] FIG. 6 is a flow diagram showing the flow of a process for updating a combination rule in the management system.

[0032] In step S210, the configuration information management module 32 updates the configuration information 41 based on the administrator's operation of the terminal device 10. The administrator updates at least one of the element data 41A, the connection data 41B, and the constraint data 41C included in the configuration information 41 as necessary.

[0033] In step S220, the configuration information management module 32 updates the combination rules 42 relating to the combination of parts in the target product based on the element data 41A, connection data 41B, and constraint data 41C of the updated configuration information 41.

[0034] In step S230, the configuration information management module 32 determines whether the updated combination rule is appropriate. If the combination rule is appropriate (YES in S230), step S240 is executed. On the other hand, if the combination rule is not appropriate (NO in S230), step S210 is executed again.

[0035] In step S240, the configuration information management module 32 registers the updated combination rule 42 in the storage unit 40. As a result, the updated combination rule 42 is stored in the storage unit 40.

[0036] FIG. 7 is a flowchart showing the flow of the process of selecting combination candidates in the management system 100. As shown in FIG.

[0037] In step S310, the configurator module 31 receives a request for a target product from a user based on the user's operation of the terminal device 10. The request includes requirements that are conditions related to parameters of parts included in the product. In other words, the requirements included in the user's request are, for example, conditions related to variables or indicators related to the dimensions, performance, function, shape, or material (or quality) of parts included in the product.

[0038] In step S320, the configurator module 31 selects candidate combinations that satisfy the requirement conditions included in the request received from the user by referring to the combination rules 42 in the storage unit 40. As shown in Fig. 8, the configurator module 31 selects candidate combinations of parts that satisfy the requirement conditions based on the requirement conditions included in the request received from the user and parameters associated with the parts included in the target product.

[0039] In step S330, the configurator module 31 presents candidates for the selected combination of parts. Specifically, the configurator module 31 transmits data on one or more candidates for the selected combination of parts to the terminal device 10 and displays the data on the display of the terminal device 10.

[0040] In step S340, the configurator module 31 accepts the selection of candidates based on the user's operation of the terminal device 10. The user can select one or more combinations of parts.

[0041] In step S350, estimate calculation module 33 calculates an estimate for the combination of parts selected in step S340. As an example, estimate calculation module 33 calculates an estimate for the combination of selected parts by adding up the estimates for each selected part. Note that data regarding the estimate for each part may be included in element data 41A of configuration information 41, or may be stored in another database or the like within storage unit 40.

[0042] In step S360, the estimate calculation module 33 presents the calculated estimated price. Specifically, the configurator module 31 transmits the estimated price for the selected candidate combination of parts to the terminal device 10 and displays it on the display of the terminal device 10.

[0043] (1.4. Hardware configuration of information processing device) 9, a hardware configuration of an information processing device used in the terminal device 10 and the management device 20 will be described. The terminal device 10 and the management device 20 as information processing devices are realized, for example, by a computer 90 shown in FIG. 9. The computer 90 includes a CPU 91, a ROM 92, a RAM 93, a storage 94, an input interface 95, an output interface 96, and a communication interface 97.

[0044] The CPU 91 functions as a processor that executes processing. Specifically, the CPU 91 uses the RAM 93 as a work memory and executes a program stored in at least one of the ROM 92 and the storage 94. During program execution, the CPU 91 controls each component via a system bus 98 and executes various processes. As an example, the CPU 91 functions as a control unit 30.

[0045] The ROM 92 stores a program that controls the operation of the computer 90. The ROM 92 stores a program necessary for causing the computer 90 to perform each of the above-described processes. The RAM 93 functions as a storage area in which the programs stored in the ROM 92 are expanded.

[0046] The storage 94 stores data necessary for executing the program and data obtained by executing the program. The storage 94 includes one or more selected from a hard disk drive (HDD) and a solid state drive (SSD). As an example, the storage 94 functions as the memory unit 40.

[0047] The input interface (I / F) 95 can connect the computer 90 to an input device 95a. The input interface 95 is, for example, a serial bus interface such as USB. The CPU 91 can read various data from the input device 95a via the input interface 95.

[0048] The output interface (I / F) 96 can connect the computer 90 and an output device 96a. The output interface 96 is, for example, a video output interface such as a Digital Visual Interface (DVI) or a High-Definition Multimedia Interface (HDMI (registered trademark)). The CPU 91 can transmit data to the output device 96a via the output interface 96 and cause the output device 96a to output the data.

[0049] The input device 95a includes one or more selected from a mouse, a keyboard, a microphone (voice input), and a touchpad. The output device 96a includes one or more selected from a display, a projector, a printer, and a speaker. A device having the functions of both the input device 95a and the output device 96a, such as a touch panel, may also be used.

[0050] The communication interface (I / F) 97 can connect the computer 90 to an external server 97a located outside the computer 90. The communication interface 97 is, for example, a network card such as a LAN card. The CPU 91 can read various data from the external server 97a via the communication interface 97.

[0051] Each process executed by the terminal device 10 or the management device 20 may be realized by one computer 90 or by a plurality of computers 90 working together.

[0052] The various data processing operations described above may be recorded as a computer-executable program on a magnetic disk (such as a flexible disk or hard disk), an optical disk (such as a CD-ROM, CD-R, CD-RW, DVD-ROM, DVD±R, or DVD±RW), a semiconductor memory, or other non-transitory computer-readable storage medium.

[0053] For example, information recorded on a recording medium can be read by a computer (or an embedded system). The recording medium may have any recording format (storage format). For example, the computer reads a program from the recording medium and causes a processor to execute instructions written in the program based on the program. The computer may acquire (or read) the program via a network.

[0054] (1.5.Summary) As described above, the management system 100 according to this embodiment includes a storage unit 40 that stores configuration information 41 that defines data on the elements of the target product, data on the connections between the elements, and data on constraints on the connections, and a control unit 30 that selects combination candidates based on a request received from a user and rules for combining the elements generated from the configuration information. This configuration makes it possible to visualize the causal relationships of combination rules in the combination of parts by the configurator, thereby improving the maintainability of the configurator.

[0055] The configuration information 41 stored in the storage unit 40 may also be defined using a modeling language. This allows a complex system, including the elements of the target product, the connections between the elements, and the constraints on those connections, to be abstracted and visualized, making it easier to understand the structure and interrelationships of the entire system.

[0056] Furthermore, the data on the elements includes parameters associated with the elements, and the data on the constraints includes constraint conditions, which are conditions on the parameters. In this way, it is possible to accurately grasp the constraints on the parameters of the elements of the target product.

[0057] The request also includes requirement conditions, which are conditions related to the parameters, and the control unit selects candidate combinations based on the requirement conditions included in the request received from the user and the parameters associated with the elements. In this way, it is possible to select a combination of elements of the target product that satisfies the user's request based on quantitative conditions, and to accurately select a feasible combination.

[0058] 2. Second Embodiment 10 to 14, a management system 200 according to a second embodiment of the present disclosure will be described, focusing on differences from the first embodiment. As shown in Fig. 10, the management system 200 has estimate estimation information 43 in a storage unit 40. When calculating an estimate for a selected combination, an estimate calculation module 33 of a control unit 30 in the management system 200 estimates an estimate for a lower element in the combination based on information about the higher element if the information about the lower element is undetermined.

[0059] 11, the unit U1 included in the target product S1 has a main part MP1, and the main part MP1 includes any one of accessory parts MP_IP1, MP_IP2, and MP_IP3. If it is not yet determined which accessory parts the main part MP1 will include, the estimate calculation module 33, when calculating the estimated price of the main part MP1, references the estimate estimation information 43 to estimate the estimated prices of the undetermined accessory parts.

[0060] Referring to Fig. 12, the flow of processing by the estimate calculation module 33 in the management system 200 will be described. In step S351, the estimate calculation module 33 determines whether the accessory parts provided for the main parts included in the combination of parts in the product to be estimated have been determined. If the accessory parts have been determined (YES in step S351), step S352 is executed. On the other hand, if the accessory parts have not been determined (NO in step S351), step S353 is executed.

[0061] In step S352, the estimate calculation module 33 calculates the estimated prices of the accessory parts provided for the main parts included in the combination.

[0062] In step S353, the estimate calculation module 33 estimates the estimated cost of the undetermined accessory parts by referring to the estimate estimation information 43. As shown in Fig. 13A, the estimate estimation information 43 may be, for example, data on the correlation between predetermined parameters related to the main parts (hereinafter referred to as main part parameters) and the cost of the accessory parts.

[0063] The main component parameter is a parameter related to the main component, and can be appropriately set as a parameter correlated with the cost of the accessory component that the main component is equipped with. For example, if the main component is a housing cover and the accessory component is a set screw for the housing cover, the main component parameter may be a parameter correlated with the cost of the number of set screws for the housing cover that are the accessory component, such as the size of the housing cover. Alternatively, the main component parameter may be a parameter correlated with the labor cost of installing the set screws for the housing cover that are the accessory component, such as the weight of the housing cover.

[0064] 13B, the estimate information 43 may be data on the correlation between predetermined parameters (hereinafter referred to as unit parameters) related to a unit including a main part and the cost of an accessory part. In this way, if there is a unit parameter that has a correlation with the cost of an accessory part, the cost of the accessory part may be estimated based on the unit parameter.

[0065] In step S354, the estimate calculation module 33 calculates the estimated price of the main part based on the estimated price of the accessory part calculated in the preceding process (S352 or S353). This makes it possible to calculate the estimated price of the main part even if the accessory part has not been decided.

[0066] 14, the flow of the process for generating the estimate information 43 will be described. In step S410, the estimate calculation module 33 tally up the actual estimates for the accessory parts. Specifically, for multiple accessory parts included in the target main part, the actual estimates for each accessory part and the total estimated price of the main part are tallied up.

[0067] In step S420, the estimate calculation module 33 investigates the cost impact of multiple accessory parts included in the main part. Specifically, among multiple accessory parts included in the main part, the accessory part that has the greatest cost impact on the main part is identified.

[0068] In step S430, the estimate calculation module 33 selects main part parameters. Specifically, based on the tabulation results in step S410, the estimate calculation module 33 selects main part parameters that are correlated with the cost of the accessory parts.

[0069] In step S440, the estimate calculation module 33 determines a calculation formula for the estimate of the accessory parts, giving priority to the accessory parts with a large cost impact. As an example, the calculation formula is obtained as a function with the main part parameters selected in step S430 as variables.

[0070] In step S450, the estimate calculation module 33 calculates the estimated price of the main part. Specifically, the estimate calculation module 33 estimates the estimated price of the accessory part based on the main part parameters of the target main part, using the calculation formula determined in step S440.

[0071] In step S460, the estimate calculation module 33 determines whether the estimated amount estimated in step S450 is valid. If the estimated amount is valid (YES in step S460), step S470 is executed. On the other hand, if the estimated amount is not valid (NO in step S460), step S430 is executed again.

[0072] In step S470, the estimate calculation module 33 registers the calculation formula for the estimate price of the accessory determined in step S440 as estimate estimation information 43 in the storage unit 40.

[0073] <3. Other embodiments> Although the management system 100 according to the present embodiment has been described above, the application of the technical concept of the present disclosure is not limited to the above embodiment. For example, in the above embodiment, the configuration information 41 is defined in a modeling language, but the present disclosure is not limited to this example. That is, data related to product elements, data related to connections between elements, and data related to constraints on the connections may be defined using a method other than a modeling language.

[0074] In the above embodiment, the management device 20 includes the storage unit 40 that stores the configuration information 41 and the combination rules 42, but the present invention is not limited to this example. That is, at least one of the configuration information 41 and the combination rules 42 may be stored in another storage medium, and the control unit 30 may perform the above-described processing by referring to the storage medium. The same applies to the estimate / estimate information 43.

[0075] The disclosure may include the following features. (Appendix 1) A management system for a configurator that selects candidate combinations of elements that configure a product, a storage unit that stores configuration information that defines data related to the elements, data related to connections between the elements, and data related to constraints on the connections; A management system comprising: a control unit that selects candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information. (Appendix 2) the data relating to the element includes a parameter associated with the element; 2. The management system of claim 1, wherein the data regarding the constraints includes constraint conditions that are conditions regarding the parameters. (Appendix 3) the request includes a requirement condition that is a condition regarding the parameter; 3. The management system according to claim 2, wherein the control unit selects the candidate combinations based on the request conditions included in the request received from the user and parameters associated with the elements. (Appendix 4) The control unit calculates an estimate for the selected combination, and if the lower-level elements in the combination are undecided, estimates an estimate for the lower-level elements based on information about the higher-level elements. (Appendix 5) An information processing device that manages a configurator that selects candidate combinations of elements that configure a product, a storage unit that stores configuration information that defines data related to the elements, data related to connections between the elements, and data related to constraints on the connections; an information processing device comprising: a control unit that selects candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information; (Appendix 6) A program that causes an information processing device having a storage unit and a control unit to manage a configurator that selects candidate combinations of elements that configure a product, storing configuration information in the storage unit that defines data on the elements, data on connections between the elements, and data on constraints on the connections; a program that causes the control unit to select candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information;

[0076] Although several embodiments of the present disclosure have been illustrated above, these embodiments are presented by way of example only and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, etc. can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as set forth in the claims. Furthermore, the above-described embodiments can be implemented in combination with each other. [Explanation of symbols]

[0077] 10: terminal device, 20: management device, 30: control unit, 31: configurator module, 32: configuration information management module, 33: estimate calculation module, 40: memory unit, 41: configuration information, 42: combination rules, 43: estimate estimation information, 50: element box, 51: parameter box, 60: constraint box, 61: association line, 90: computer, 91: CPU, 92: ROM, 93: RAM, 94: storage, 95: input interface, 95a: input device, 96: output interface, 96a: output device, 97: communication interface, 97a: external server, 98: system bus, 100: management system, 200: management system

Claims

1. A management system for a configurator that selects candidate combinations of elements that configure a product, a storage unit that stores configuration information that defines data related to the elements, data related to connections between the elements, and data related to constraints on the connections; A management system comprising: a control unit that selects candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information.

2. the data relating to the element includes a parameter associated with the element; The management system according to claim 1 , wherein the data regarding the constraints includes constraints that are conditions regarding the parameters.

3. the request includes a requirement condition that is a condition regarding the parameter; The management system according to claim 2 , wherein the control unit selects the combination candidates based on the request conditions included in the request received from the user and parameters associated with the elements.

4. 2. The management system according to claim 1, wherein the control unit calculates an estimate for the selected combination, and when a lower-level element in the combination is undecided, estimates an estimate for the lower-level element based on information about the higher-level element.

5. An information processing device that manages a configurator that selects candidate combinations of elements that configure a product, a storage unit that stores configuration information that defines data related to the elements, data related to connections between the elements, and data related to constraints on the connections; an information processing device comprising: a control unit that selects candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information;

6. A program for causing an information processing device having a storage unit and a control unit to manage a configurator that selects candidate combinations of elements that configure a product, storing configuration information in the storage unit that defines data on the elements, data on connections between the elements, and data on constraints on the connections; a program that causes the control unit to select candidates for the combination based on a request received from a user and rules regarding the combination of the elements generated from the configuration information;

Images