DE102011117679A1 - System for automated design and manufacture of Heating, Ventilating and Air Conditioning (HVAC) control panels, selects control panel enclosures dynamically as function of rules, components, and equipment to be controlled - Google Patents

Abstract

The system (100) has a computer storage medium comprising data relating to control panel enclosures and a set of rules for designing a control panel, and one or more computer processors (111) configured to: receive a selection of two or more components for placement in the enclosures; retrieve information about two or more components from a database; and generate one or more layouts. The enclosures are dynamically selected as a function of one or more of the set of rules, the two or more components, an equipment to be controlled by the control panel and an application of the equipment. The one or more layouts include placement of the two or more components within at least one of the control panel enclosures as a function of the set of rules for designing a control panel. Independent claims are also included for the following: (1) a method for automated design and manufacture of HVAC control panels; and (2) a computer readable medium comprising instructions that when executed by a processor executes the method for automated design and manufacture of HVAC control panels.

Description

Copyright notice and permission

Part of this patent document contains material subject to copyright. The copyright owner has no objection to the facsimile reproduction of the patent document or patent disclosure by any person as it appears in the Patent and Trademark Office patent files or patents, but reserves all copyright whatsoever. The following note applies to this document: Copyright ^© 2007, Design Ready Controls, Inc.

Technical area

Various embodiments of the present invention relate to the automatic design and manufacture of equipment panels, such as panels for heating, ventilation and air conditioning (HVAC) equipment. Some embodiments also relate to control panels and other subassemblies, such as wire harnesses, for the design and manufacture of pumps, large compressors, conveyors, packaging and ventilation equipment.

background

Devices, such as HVAC equipment, are manufactured by Original Equipment Manufacturers (OEMs), who have a large number of customers with different requirements. In order to meet these requirements efficiently, OEMs are developing customer-specific product lines or product families for specific market segments. Customers then select from various lists of parameters, configurations, and options in the product family to order partially customized equipment just as automakers customize their automobiles by choosing from available options.

For example, a customer may select for HVAC devices under parameters such as cooling power and power supply voltages, and configurations such as the number and size of the supply air and exhaust fans. By selecting specific parameters, configurations and options, the customer ultimately chooses a single product of thousands or even millions of unique options.

Once the HVAC customer has finalized their selection by placing an order, an HVAC OEM will normally execute the order using an ETO (Engineer To Order) process. In particular, this process involves passing on the job to a team of technicians who study the selection and customize a generic electrical or mechanical model to include the customer's choice. This adaptation work requires u. a. often a redesign of the electrical panel of the HVAC unit.

One problem that has been recognized by the present inventors, however, is that the conventional redesign of the panel is particularly time consuming and expensive because the panel acts as the brain of the HVAC device and contains hundreds of interconnected components. This extra time and effort puts significant pressure on OEMs to narrow down the range of options they offer to customers in a market where many customers actually want more options and lower prices.

In addition, because of this timing and price pressure, many OEMs have tried to shorten the usual design and manufacturing process by skipping steps such as fully documenting their dashboard models with accurate inventory drawings. However, the absence of these drawings creates another problem because it makes the maintenance and troubleshooting of HVAC equipment after installation difficult.

Accordingly, the inventors of the present invention have recognized the need for better ways of designing and manufacturing OEM devices in general and HVAC panels in particular.

Summary

To meet these and / or other requirements, inventors of the present invention invented, among other things, systems, methods, and software that facilitate the specification, design, manufacture, and documentation of panels for partially or even completely customized OEM devices, such as panels or panels Simplify wiring harnesses for HVAC devices and reduce the time required for them. An exemplary computerized system includes a product configuration module, a technical design module, and a manufacturing module.

In operation, the product configuration module receives user input about product family parameters via a special configuration interface and outputs a product family data structure, such as a coded string analogous to human DNA, to the engineering design module. The engineering design module, which incorporates engineering design rules, automatically processes the coded string and outputs true engineering inventory drawings, component lists, cabling lists, and even assembly instructions for robot manufacturing equipment. The manufacturing module receives the output from the engineering design module, creates and orders parts using a merchandise management system, and communicates the assembly instructions to the robot manufacturing facility.

The exemplary system significantly reduces the product specification and design time required for a custom panel, and enables OEMs to efficiently offer more options and shorter turnaround times to their customers, thus gaining a significant competitive advantage.

Brief description of the drawings

1 Figure 12 is a block diagram of an exemplary panel design and manufacturing system 100 that corresponds to one or more embodiments of the present invention.

2 FIG. 10 is a flowchart of an example method of operating system. FIG 100 that corresponds to one or more embodiments of the invention.

3 is a facsimile of an exemplary graphical user interface 300 that corresponds to one or more embodiments of the present invention.

5A and 5B are combination flowchart and block diagrams, taken together an exemplary architecture 500 which corresponds to one or more embodiments of the present invention.

6 is a facsimile of an exemplary graphical user interface 600 that corresponds to one or more embodiments of the present invention.

7 is a facsimile of an exemplary graphical user interface 700 that corresponds to one or more embodiments of the present invention.

8th is a facsimile of an exemplary graphical user interface 800 that corresponds to one or more embodiments of the present invention.

9 is a facsimile of an exemplary graphical user interface (and database structure) 900 that corresponds to one or more embodiments of the present invention.

10 FIG. 10 is a block diagram of an exemplary embodiment of a dynamic panel generator. FIG.

12 is an exemplary embodiment of a switchboard layout.

13 is an example illustrating the relative location in a switchboard layout.

14 is an example that illustrates the relationship between relative location and orientation.

15A and 15B FIG. 10 is an exemplary embodiment of a process (method) for dynamically creating a switchboard layout.

18 is an example of a switchboard layout with overlapping components.

19 is an example of a switchboard layout with overlapping components.

20 Figure 10 is a block diagram of an exemplary embodiment of a computer system on which an embodiment may be practiced.

Detailed description of exemplary embodiments

This description, which includes the figures and claims, describes one or more specific embodiments of an invention. These embodiments, which are not given to limit the invention but to explain it by way of example, are shown and described in sufficient detail to enable those skilled in the art to implement or put into practice the invention. Therefore, the description, where appropriate, without obscuring the invention, may omit certain information known to those skilled in the art.

overview

The exemplary system and method embody a unique method for the design and manufacture of switchboards for custom OEM (Original Equipment Manufacturer) products, particularly HVAC equipment. Traditionally, OEMs develop and provide families of products that address specific market segments. For example, OEMs that produce HVAC equipment typically provide a family or series of products. Within a product family, OEM customers can choose from a relatively large number of options. Within each product family, there are generally millions of permutations or potentially unique option combinations possible. Because of this variability in product configuration, each ordered OEM product is considered, at least in part, as unique or custom in terms of content or design terms.

• 1) Erkennung einer Marktchance.
• 2) Definition von Spezifikationen für eine Produktfamilie, die die Chance ergreift.
• 3) Detail- und Entwurfskonzeption für die Produktfamilie.
• 4) Bereitstellung einer Optionsliste, aus der Kunden auswählen können.
• 5) Fertigstellung des Entwurfs und Layouts bei Empfang der einzelnen Bestellungen (ETO/Engineer-to-Order-Prozess).
• 6) Fertigung, Prüfung und Auslieferung des Produkts gemäß Kundenspezifikationen.

To bring a highly variable product family to the market, an OEM typically works as follows:

• 1) Recognition of a market opportunity.
• 2) Defining specifications for a product family that takes the opportunity.
• 3) Detailed and design concept for the product family.
• 4) Provide an option list from which customers can select.
• 5) Completion of the design and layout upon receipt of the individual orders (ETO / engineer-to-order process).
• 6) Manufacturing, testing and delivery of the product according to customer specifications.

The development of the control subsystem or product family dashboard follows the same process, especially steps 2-6.

The exemplary switchboard design and manufacturing system optimizes the advance development of switchboards for such OEM product families (steps 2, 3, and 4), automates the ETO process (step 5), and provides the necessary manufacturing information and reports for the justifications. In-time mass production of customized switchboards for OEM products (step 6).

Exemplary design and manufacturing system for switchboards

1 shows an exemplary design and manufacturing support system for switchboards 100 , system 100 includes a computer workstation 110 , a merchandise management system 120 and a manufacturing complex 130 (NC machines, cabling machines, robotor, etc.). In the exemplary embodiment, access device takes 110 the form of a PC, laptop, PDA, cellular phone, or other device that can support the functions described herein. In particular, Workstation included 110 a processor module 111 , a store 112 , a display 113 , a keyboard 114 and a graphical pointing or selection device 115 ,

processor module 111 includes one or more processors, processing circuits, or controllers. In the exemplary embodiment, processor module takes 111 any practical or desirable form. Coupled with processor module 111 is memory 112 ,

memory module 112 , which assumes the exemplary form of one or more electronic, magnetic or optical data storage devices, stores Automated Panel Expert (APE) design and manufacturing module 116 (APE b / w).

module 116 comprising machine-readable and / or executable instruction sets and related data includes a generic product specification module 1161 , a product definition data structure 1162 (DNA), a technical specification module 1163 , a production support module 1164 and associated graphical user interfaces 1165 (GUI).

The general product (panel) specification (or configuration) module 1161 includes instruction sets and data for manufacturing one or parts of a graphical user interface (GUI) 1165 which accepts user input associated with attributes of an HVAC system, and defines and gives a general product specification data structure (DNA) 1162 based on selected attributes or imported attributes or requirements. In the exemplary embodiment, the generic product specification data structure takes the form of a coded text string that is validated based on rules for compatibility of the options. DNA 1162 becomes the technical specification module 1163 output.

The technical specification module 1163 decodes DNA 1162 in different fields or segments. These segments are used to automatically select components and define mechanical and electrical schematics for a product, such as an HVAC panel, using design rules and macros for computer-aided design tools.

production module 1164 , which receives the mechanical and electrical diagrams, includes instruction sets and data not only for the definition of one or more parts of the GUI 1165 for example, ECAD interfaces, but also for the definition of cabling lists, mechanical layouts, ERP order management, etc.

In addition to workstation 110 includes system 100 ERP system 120 and manufacturing complex 130 , both an interface to manufacturing module 1164 to facilitate just-in-time mass production of HVAC panels and associated wiring harnesses.

Exemplary operating procedure

2 shows a flowchart of an exemplary method 200 for the operation of a system 100 in 1 , flow chart 200 includes blocks 210 - 240 arranged and described in series.

The reference numerals in 2 describe:

LIST OF REFERENCE NUMBERS

210

General product data specification received

220

Define device data structure

230

Create engineering design data structures and documents

240

Production based on the design data structures.

However, other embodiments execute two or more blocks in parallel using multiple processors or processor-like devices or a single processor organized as two or more virtual machines or sub-processors. Other embodiments also change the process order or provide different functional partitions or blocks to obtain analogous results. Still further embodiments implement the blocks as two or more interconnected hardware modules with interconnected control and data signals communicated between and over the modules. Therefore, the exemplary process flow (procedure) applies to software, hardware, and firmware implementations.

The example method begins at block 210 which involves the receipt of inputs defining a set of product options. In the exemplary embodiment, this includes displaying a product definition or configuration interface part of the GUI 1165 , which lists a variety of product selection options. 3 shows an exemplary configuration interface 300 ,

Configuration interface 300 includes a product line listing region 310 , a feature listing region 320 , and a corresponding feature definition region 330 , The product line listing region lists one or more selectable product lines. Feature list Region 320 lists a set of features or attributes, such as the voltage / phase / frequency attributes 321 that with the active or selected product line in region 310 are connected. Feature definition region 330 includes one Set of feature definition regions, for example pull-down menu 331 that match the voltage / phase / frequency attributes 321 correspond. Pull-down menu 331 lists selectable options. The execution is at block 220 continued.

block 220 Contains the definition of a device data structure based on the selected product options. In the exemplary embodiment, this includes the definition of a DNA data structure in the form of a coded text string based on the selection made using the configuration interface part of the GUI 1165 or interface 300 took place.

Table 1.1 is an exemplary patch DNA data structure that corresponds to one or more embodiments of the present invention. Table 1.1: 400 410 420 430 DATA FIELD NO. CORRESPONDING PRODUCT OPTION DATA FIELD LENGTH 1 ₁ MODEL NUMBER ₁ 9 ₁ 2 ₁ VOLTAGE PHASE FREQUENCY ₁ 3 ₁ 3 ₁ TRENNER ₁ 1 ₁ 4 ₁ SUPPLY FAN ₁ 1 ₁ 5 ₁ SUPPLY FAN CONTROL ₁ 1 ₁ 6 ₁ SUPPLY FAN PS ₁ 4 ₁ 7 ₂ SUPPLY FAN FLA NO. ₂ 4 ₂ 8 ₁ EXHAUST AIR FAN QUANTITY: 0, 1, 2 ₁ 1 ₁ 9 ₁ EXHAUST VALVE CONTROL ₁ 1 ₁ 10 ₁ EXHAUST VALVE PS ₁ 4 ₁ 11 ₂ EXHAUST VALVE FLA NO. ₂ 4 ₂ 12 ₁ CONDENSATION TYPE ₁ 2 ₁ 13 ₂ CONDENSATE FAN NO. ₂ 1 ₂ 14 ₂ CONDENSATION FAN PS NO. ₂ 4 ₂ 15 ₂ CONDENSATE FAN FLA NO. ₂ 4 ₂ 16 ₂ COMPRESSOR 1 MGE. NO. ₂ 1 ₂ 17 ₂ COMPRESSOR 1 TONN. NO. ₂ 4 ₂ 18 ₂ COMPRESSOR 1 FLA NO. ₂ 4 ₂ 19 ₂ COMPRESSOR 1B MGE. NO. ₂ 1 ₂ 20 ₂ COMPRESSOR 1B TONNES NO. ₂ 4 ₂ 21 ₂ COMPRESSOR 1B FLA NO. ₂ 4 ₂ 22 ₂ COMPRESSOR 2 MGE. NO. ₂ 1 ₂ 23 ₂ COMPRESSOR 2 TONNES NO. ₂ 4 ₂ 24 ₂ COMPRESSOR 2 FLA NO. ₂ 4 ₂ 25 ₂ COMPRESSOR 2B MGE. NO. ₂ 1 ₂ 26 ₂ COMPRESSOR 2B TONNES NO. ₂ 4 ₂ 27 ₂ COMPRESSOR 2B FLA NO. ₂ 4 ₂ 28 ₁ AIR FLAPS ₁ 2 ₁ 29 ₁ GAS HEAT ₁ 2 ₁ 30 ₁ GAS HEAT CONTROL ₁ 2 ₁ 31 ₁ ELECTRICALLY HARDENED SPOOL ₁ 2 ₁ 32 ₂ GAS HEATING OVEN MGE. NO. ₂ 1 ₂ 33 ₁ ELECTRIC HEAT ₁ 2 ₁ 34 ₂ ELECTRIC HEAT kW NO. ₂ 4 ₂ 35 ₂ HEAT RECOVERY ₂ 2 ₂ 36 ₂ ENTHALPY WHEEL PHASE ₂ 1 ₂ 37 ₂ ENTHALPY WHEEL PS NO. ₂ 4 ₂ 38 ₂ ENTHALPY WHEEL FLA NO. ₂ 4 ₂ 39 ₁ COMPRESSOR CRANKCASE HEATER ₁ 1 ₁ 40 ₁ GFCI OUTPUT ₁ 1 ₁ 41 ₁ PRINT CONTROL ₁ 1 ₁ 42 ₁ LOW AMBIENT CONTROL ₁ 1 ₁ 43 ₁ HEATING BELT ₁ 1 ₁ 44 ₁ HOUSING CONTROL ₁ 1 ₁ 45 ₁ UV-LIGHT ₁ 1 ₁

Table 1.2 is an exemplary table for translating options to coded strings that corresponds to one or more embodiments of the present invention. Table 1.2: 452 454 456 OPTIONS CODE STRING FOLLOW CODE Model number ₁ 9 _{1 1} Model 1 MDL110D05 Model 2 MDL110D08 Model 3 MDL110D10 Model 4 MDL210D10 Model 5 MDL210D13 Model 6 MDL210D16 Model 7 MDL210D18 Model 8 MDL210D20 Model 9 MDL210D25 Model 10 MDL310D20 Model 11 MDL310D25 Model 12 MDL310D30 Model 13 MDL310D35 MDL310D40 VOLTAGE PHASE FREQUENCY ₁ 3 _{1 1} 200 (208) V - 3PH - 60 Hz 203 230 (240) V - 3PH - 60 Hz 233 460 (480) V - 3PH - 60 Hz 463 TRENNER ₁ 1 _{1 1} NONE (POWERBLOCK) N TRENNER WITHOUT D FUSE F TRENNER WITH FUSE C FAN VOLUME ₁ 1 _{1 1} ONE 1 TWO 2 SUPPLY FAN CONTROL ₁ 1 _{1 1} VFD V MOTOR STARTER S SUPPLY FAN PS ₁ 4 _{1 1} 1 / 3HP 00.3 1 / 2HP 00.5 3 / 4HP 00.8 1HP 01.0 1.5HP 01.5 2HP 02.0 3HP 03.0 5HP 05.0 7.5HP 07.5 SUPPLY FAN FLA NO. ₂ 4 ₂ 2: 6 ₂ EXHAUST FAN QUANTITY ₁ 1 _{1 1} NONE 0 ONE 1 TWO 2 EXHAUST VALVE CONTROL ₁ 1 _{1 1} NONE N VFD V MOTOR STARTER S EXHAUST VALVE PS ₁ 4 _{1 1} NONE 00.0 1 / 3HP 00.3 1 / 2HP 00.5 3 / 4HP 00.8 1HP 01.0 1.5HP 01.5 2HP 02.0 3HP 03.0 5HP 05.0 7.5HP 07.5 EXHAUST VALVE FLA NO. ₂ 4 ₂ 2:10 ₂ CONDENSATION TYPE ₁ 2 ₁ NONE N / A LUFTGEKÜHLT AC REMOTE CONDENSING RC WATER COOLED WC COOLED WATER CW SHARED SYSTEM SS HOT WATER HW CONDENSATE FAN NO. ₂ 1 ₂ 1:12 ₂ NONE 0 ONE 1 TWO 2 THREE 3 CONDENSATION FAN PS NO. ₂ 4 ₂ 1:13 ₂ CONDENSATE FAN FLA NO. ₂ 4 ₂ 2:14 ₂ COMPRESSOR 1 MGE. NO. ₂ 1 ₂ 1:12 ₂ COMPRESSOR 1 TONN. NO. ₂ 4 ₂ 1:16 ₂ COMPRESSOR 1 FLA NO. ₂ 4 ₂ 2:17 ₂ COMPRESSOR 1B MGE. NO. ₂ 1 ₂ 1:12 ₂ COMPRESSOR 1B TONNES NO. ₂ 4 ₂ 1:19 ₂ COMPRESSOR 1B FLA NO. ₂ 4 ₂ 2:20 ₂ COMPRESSOR 2 MGE. NO. ₂ 1 ₂ 1:12 ₂ COMPRESSOR 2 TONNES NO. ₂ 4 ₂ 1:22 ₂ COMPRESSOR 2 FLA NO. ₂ 4 ₂ 2:23 ₂ COMPRESSOR 2B MGE. NO. ₂ 1 ₂ 1:12 ₂ COMPRESSOR 2B TONNES NO. ₂ 4 ₂ 1:25 ₂ COMPRESSOR 2B FLA NO. ₂ 4 ₂ 1:26 ₂ AIR FLAPS ₁ 2 ₁ NONE N / A OUTDOOR AIR OA RETURN AIR RA EXTERNAL AND REVERSE AIR OR GAS HEAT ₁ 2 ₁ NONE N / A YES GH GAS HEAT CONTROL ₁ 2 ₁ NO CONTROL NC 2 STATES TS MODULATION MD ELECTRICALLY HARDENED SPOOL ₁ 2 ₁ NONE N / A SCR CONTROL SC GAS HEATING OVEN MGE. NO. ₂ 1 ₂ 1:29 ₂ ELECTRIC HEAT ₁ 2 ₁ NONE N / A YES EW ELECTRIC HEAT kW NO. ₂ 1 ₂ 1:33 ₂ HEAT RECOVERY ₁ 2 NONE N / A ENTHALPIE WHEEL NO SENSOR EH ENTHALPY WHEEL WITH ROTATION SENSOR HE FLAT PLATE HEAT EXCHANGER WITH BYPASS AIR INTAKE FB FLAT PLATE HEAT EXCHANGER WITH MODULATION BYPASS AIR INTAKE FM ENTHALPIE-RADPHASE 1 SINGLE PHASE S PHASE T ENTHALPY WHEEL PS NO. ₂ 4 35:36 ₂ ENTHALPY WHEEL FLA NO. ₂ 4 2:37 ₂ COMPRESSOR CRANKCASE HEATER ₁ 1 NONE N CRANKCASE HEATER H GFCI OUTPUT ₁ 1 NONE N DRC OUTPUT O DRC TRANSFORMER IN SEPARATED P CASING HEAT PRESSURE CONTROL ₁ 1 NONE N YES H LOW AMBIENT CONTROL ₁ 1 NONE N YES H HEATING BELT ₁ 1 NONE N HEATING BELT IN SWITCHBOARD H HOUSING COOLING ₁ 1 NONE N COOLERS IN SWITCHBOARDS C UV-LIGHT ₁ 1 NONE N YES L

Table 1.1 shows a tabular representation of an exemplary DNA data structure 400 , which includes 45 data fields, each associated with a particular, user selected or otherwise defined OEM product option, for example an OEM HVAC system. In the exemplary string implementation, each data field is associated with a position in the string and has a predetermined number of characters representative of some aspects of an OEM HVAC system that affect its panel (and harness). For example, data field # 1 is 9 characters long and defines the model number of the HVAC system; Data field # 2 is 3 characters long and defines some aspect of voltage / phase / frequency of the HVAC system with the selected model number; Data field # 3 defines some aspects of the HVAC separator and has the length of one character. In the exemplary embodiment, the data field number also indicates its cardinal position in a concatenated text string.

In the definition of the DNA data structure based on the options selected, the exemplary embodiment uses a translation data structure or table. Table 1.2 shows an example translation data structure 450 stored in the memory of the exemplary system. Translation data structure 450 includes options 452 , Code strings 454 and lookup codes 456 , In the exemplary system, one or more user selects for the configuration menu are calculated based on other selected parameters or selected from a lookup table using a lookup encoding scheme that handles either a predetermined value or a formula for determining a value. (In the exemplary embodiment, DNA coding table is used 450 Also used to define the content and order of menus and menu listings in the configuration interface. Therefore, the position of the model number options within the spreadsheet also changes their position within interface 300 .) An exemplary panel DNA data structure is as follows:

The exemplary method also includes validating the DNA data structure using validation rules, with special assurance that the selected options presented in the DNA data structure are compatible based on the option rules. Some embodiments perform the validation during the general product specification based on the particular selection and, if a particular selection is not compatible with an earlier selection, alert the user or alternatively narrow the available feature space as the user moves through the configuration interface.

2 shows that after defining a device data structure based on the selected product options, execution at block 230 will continue.

block 230 includes the automatic generation of engineering design data structures and documentation based on the defined (and validated) device data structure (which is representative of the general product specification). In the exemplary embodiment, this generally includes the definition of a parts list based on the DNA data structures, the generation of electrical and mechanical diagrams based on ECAD macros for the parts, and associated macro attributes logically connected to parts and one or more parts of the DNA fragments. Data structure, for example model number or product line.

block 240 involves the automatic fabrication of a device, in this case a control panel, based on the technical design data structures. In the exemplary embodiment, fabrication involves defining cabling lists, mechanical layouts, etc., and communicating the appropriate instruction sets to one or more automated or robotic manufacturing equipment, such as a cabling machine, laser cutter, or milling machine, to complete the desired panel. In addition, an automatic check is performed.

Furthermore, structural and operational details are described below in connection with an example software architecture.

Exemplary software architecture

5A and 5B show an architecture block and a flow chart of an example implementation 500 of software 116 in 1 , These two figures show three sets of hatched coded components, with the left-hatched component generally module 1161 corresponds to the vertically-hatched component module 1163 corresponds and the right-hatched component module 1164 equivalent. The flow through the diagram is generally from left to right.

GENERAL PRODUCT SPECIFICATION

In operation, the example method starts with the presentation of a "draft ready" list of the most common technical options (EDB PROGRAM OPTIONS 202 ) in an OEM industry, such as HVAC, pump, large compressor, conveyor, packaging or air conditioning etc. For example, an HVAC OEM can select options for a range of supply air fans based on power. ( 3 or Tables 1.1 and 1.2 shows the respective graphical user interface 300 respectively. 400 for the selection of options.)

By selecting from this list of options and restricting the available choices within each option, the OEM can use the example system to quickly define and generate the general technical specifications for a product family (Step 2 at a Glance). In the exemplary embodiment, the OEM may further develop the technical product family specifications by adding to this list any additional options that may be unique to its offering.

As the system helps to reduce the time and cost of pre-product development (step 3) and ETO (step 5), OEMs can often reduce the number and variety of product family options (EDB PROGRAMM OPTIONS 2021 ) in an economic way. Once a set of options is defined, the system defines a DNA code string or data structure 208 (analogous to DNA 1162 in 1 ), which records the customer-specific order from the customers of the OEM.

In particular, in the exemplary embodiment, an APE reads CONFIG DLL module 503 the original technical specifications from an OPTIONS DATABASE 502 and automatically defines a panel DNA data structure 508 for the product family.

To capture an order, the example system configures the OEM-preselected EDB PROGRAM OPTIONS in a dynamic GUI interface list, for example GUI 300 in 3 , This GUI is used for the manual configuration of purchase orders (step 4) by selecting the switchboard options (ORDER CONFIGURATION, MANUAL CONFIGURED ORDER). The in the GUI 300 The selection listed is from an EDB program options database 5051 filled. 6 shows that the EDB program options database can take the form of an Excel spreadsheet, however, some embodiments use a SQL database format.

The EDB Program Moption Database contains the list of options or parameters used to define the translation table in Table 1.2, which translates the selected device options described above into the DNA code string for a control panel. Some of these options are made dynamically via the configuration interface in 3 displayed when someone configures a control panel. These are the options highlighted in Tables 1.1 and 1.2 with footnote "1". Those highlighted with footnote "2" are calculated spontaneously or by using lookup tables included in other Microsoft Excel spreadsheet files. In many cases, the user does not have to be prompted. For example, the exemplary embodiment calculates an amperage when prompted for voltage and power input. In this case, the DNA strand shows power, voltage, and amperage, even though we've only asked the user to input power and voltage. All parameters are used to fill in the fields in the DNA strands. EDB files are fully customizable to each customer's panel requirements.

The exemplary system provides a unique link between how a customer sees requirements and how these requirements translate into a set of technical specifications in the form of a SWITCHBOARD DNA CODESTRING. For example, a customer may see a request as a request for an HVAC system for a 25,000 square foot bearing, and the exemplary system eventually translates this into a technical requirement for a 4 unit HVAC system with a specified power, each unit having 5 supply air fans PS has.

The example system presents customer options in a menu using customer-friendly language and then uses the RDB OPTION RULES 5022 in OPTION DATABASE 502 to translate the customer requirements into technical requirements or assign them to them. For example, the system may ask a customer for the size of the warehouse for which they need air conditioning and, in response, select a suitable quantity and product recommendation based on the model number. Based on the model number, the exemplary system provides further rules for selecting more detailed technical criteria such as supply air fan performance, etc. This automatic translation of customer requirements into technical specifications allows the OEM to quickly identify customer requirements and promptly make customer-specific technical specifications including quotations and parts lists (BOM ).

In the exemplary embodiment, APE may be CONFIG DLL 504 which is used to associate customer requests and orders in panel DNA codestring 508 to be embedded, or invoked directly by the customer's internal order entry software, such as the CUSTOMIZED PROUDKT DNA 509 represents. The APE GUI interface can be hosted on a web server to make a WEB CONFIGURED ORDER 510 which allows OEM customers to order products from anywhere via a WLAN or LAN.

To detect compatibility issues between the selected options and to allow for correction, APE reads RULES.DLL 510 the list of selected options in the SWITCHBOARD DNA CODESTRING 508 and dynamically checks for errors and option incompatibilities using design rules in the RDB OPTION RULE database 5022 to validate each potential order. DNA VALIDITATSPRÜFUNGS interface 511 is together with the ORDER CONFIGURATION interface 506 used to guide OEM sales people and their potential customers through the order configuration process. (In some embodiments, the APE RULES.DLL can also be used in conjunction with an OEM's internal order entry software tool and can be called directly from it.)

In particular, the RDB OPTION RULE database includes 5022 a series of Boolean if / then operations that refer to fields in the SWITCHBOARD DNA CODESTRING. For example, if a field equals 30 (which could be for a model number 30 pump controller), then field 2 may not be X, Y or Z (which could represent certain types of separators). Each rule violation refers to an error message that is dynamically presented to the user as a DNA ERROR REPORT 512 from the DNA VALIDITY INSPECTION interface 512 off can be displayed. For example: "Error: You can not have an X, Y, or Z separator in a Model 30 product." 7 shows an exemplary DNA bug report GUI 700 ( 300 ) with an error message region 710 ,

If APE RULES.DLL 510 determines that all rules in the RDB OPTION RULE database 5022 are met for a specific order by the BILLBOARD DNA CODESTRING 508 it validates the DNA codestring and releases the order, now in VALID DNA format, for use with the ETO automatic editing tools. 8th shows an exemplary valid DNA GUI 800 which is issued in response to a validity confirmation.

9 shows an exemplary spreadsheet version 900 the RDB Rule Rules database 5022 , The rules are set up as complex sets of IF-THEN statements of the form IF (DNA code (=, <,>, etc.) a calculated value) THEN (select size, part, macro, wire, etc.). (Rules of this form can also be created and managed using ready-made applications such as Rules Stream expert system software.)

• Spalte A: • Jede einzelne Regel sollte mit einem nummerischen Wert beginnen. • Jede Regel sollte mit „EOR” und einer Regelnummer enden. • „ENDOFRULES” sollte am Ende aller Regeln angegeben werden
• Spalte B: • Diese Spalte enthält: Codenummer = Option • Erlaubte Operatoren sind • <> (nicht gleich) • >= • <= • > • <
• Spalte C: • Diese Spalte enthält Bedingungen im folgenden Format: Codenumber <> Option • Erlaubte Operatoren sind • <> (nicht gleich) • >= • <= • > • <
• Spalte D: • Diese Spalte enthält logische Operatoren, die zwei Reihen bedienen. • Erlaubte Operatoren sind • UND • ODER • XOR
• Spalte E: • Diese Spalte enthält Fehlercodes. • Regelnummer und Fehlercodes sollten in dieselbe Reihe platziert werden.

Explanations to 9 :

• Column A: • Each rule should begin with a numeric value. • Each rule should end with "EOR" and a rule number. • "ENDOFRULES" should be given at the end of all rules
• Column B: • This column contains: Code number = Option • Allowed operators are • <> (not equal) •> = • <= •> • <
• Column C: • This column contains conditions in the following format: Codenumber <> option • Allowed operators are • <> (not equal) •> = • <= •> • <
• Column D: • This column contains logical operators that serve two rows. • Allowed operators are • AND • OR • XOR
• Column E: • This column contains error codes. • Rule number and error codes should be placed in the same row.

NOTE: The logical operator between OPTIONS and CONDITIONS is always AND.

These are rules that run against a DNA code string. In some cases, the rules describe DNA code compatibility and what options may and may not work with others. In this case, they are used in DNA error checking routines that validate a desired configuration or DNA code string. In other cases, these rules are used to select and size components contained in a panel. For example, if the DNA code for PS = 30, then a motor starter of a particular size will be selected by a particular supplier. If we use the RDB format for such a selection, we sometimes refer to the file as a DWEEEB database.

DETAILED TECHNICAL DESIGN SPECIFICATION

• A) Eine Reihe allgemeiner, und doch detaillierter elektrischer Schaltbilder, die die Optionen und grundlegenden Steuerungsfunktionen abdecken, die für die OEM-Produktfamilie erforderlich sind.
• B) Eine vollständige Liste aller Komponenten und Teile, die potenziell benötigt werden, um die Schalttafeln für eine ganze OEM-Produktfamilie auszuführen.
• C) Ein detailliertes Schema für das physikalische Layout der Teile von Schritt B für die Familie der Schalttafeln.

The pre-conception of controls for an OEM product family usually involves the creation of:

• A) A series of general, yet detailed electrical schematics covering the options and basic control features required for the OEM product family.
• B) A complete list of all components and parts that are potentially needed to run the panels for an entire OEM family of products.
• C) A detailed physical layout diagram of the parts of step B for the family of control panels.

The example process and software tools are intended to help optimize the detailed pre-design process (steps A, B and C) and automate the ETO process. The example system automates the process such that the detailed design information from step A, B, and C (MACROOBJECT DB, APET ENGINE TRACK DB, and MACROS) together with ETO engineering or decision making know-how (DWEEEB database with electrical engineering and estimated brain database) in the system. The system includes ready-to-use 3D solid modeling applications (SOLID WORKS 3D LAYOUT) for interference testing and the development of a layout scheme. (Step C).

The detailed design process (steps A, B, C) will therefore be optimized into a standardized process of selecting appropriate generic macros and rules and improving them with additional data that may be needed to execute the design of the controls for a product family. (Note: ECAD macros are small schematic or layout drawings that can be selected and placed in complete schematic and layout drawings and linked to them.) After completing the detail design information and the ETO rules, the example system fully automates the ETO process and produces inventory screens , Inventory layouts, BOMs and a variety of manufacturing reports for each individual panel at the touch of a button (PICTURES, LAYOUTS, BOM, LABELS, CABLE LABELS, MANUFACTURING REPORTS).

AUTOMATED MANUFACTURING

Generally speaking, the exemplary system captures the know-how and criteria used by ETO engineers and processes orders (VALID DNA) with this information. Rather than an engineer presenting schematized diagrams to a technical draftsman, the example system uses the APE GUI ECA INTERFACE, APE (APE PROMISE DLL, APE EPLAN DLL), to create an ECAD instruction set (PROMISE INSTRUCTION SET, EPLAN INSTRUCTION SET), which can be executed via the API (Application Programming Interface) of standard finished ECAD design packages (APE PROMISE API, APE EPLAN API). The APIs can be used to create inventory panels and layouts at the touch of a button or by a single command or call from another application. The schematics and layouts are then efficiently checked for errors and completeness using standard utilities included in ECAD (ECA ENVIRONMENT) packages.

The exemplary system includes a unique filled-in stem database (APE-TECHNOLOGY TEAM) which is associated with a unique set of macro information or MACROOBJECT DATABASE and a catalog of ECAD macros (MACROS, MACROS / PLACEHOLDER).

Electrical CAD systems, such as PromisE, EPLAN, or AutoCAD electric, use the concept of macros or part drawings, which can be accessed quickly to create larger or more complete schematics. In addition to the graphical representation, each software vendor allows the assignment of data or attributes to macros. This information may include items such as component part numbers, cable number, cable cross-section, cable color, harness names, schematic page, and X, Y location coordinates, device IDs, connection point labels, cable terminations, stripping lengths, cable lengths, and so on.

Traditional macros contain this type of product family attribute information. Therefore, traditional macro catalogs usually need to be rebuilt for each different product family or for each schematic or layout design. However, the inventors of the present invention have recognized the inefficiency of this approach and invented a unique MACROBODY DATABASE that captures, maintains, and manages ECAD macro attribute information. This allows the creation of genuinely generic macro catalogs (with generic placeholders for the attribute information) for all finished ECAD packages. These generic macros can be used repeatedly across multiple OEMs and product families, as well as schematic and layout configurations. Once generic macros are placed, macros can be assigned specific information for the product family from the MACROOBJECT DATABASE.

This unique method offers many benefits and benefits. The need to redraw and manage macros used for specific product families is reduced. The manufacturer of an original design can share generic macros across product families and customers, reducing up-front development costs. ECAD attributive data is managed independently by specific ECAD software applications, providing the ability to switch from one ECAD software vendor to another during an APE installation. And managing the attribute data in a sophisticated database utility, such as the Microsoft SQL Utility, makes it much easier to maintain, update, and revise the data. And those who maintain this attribute data can do so directly without accessing ECAD software applications or even knowing how they are accessed, which in turn reduces the design time, resources, and know-how needed to implement initial installations of the APE system or future design changes in a product family.

There is a set of rules (DWEEEB DATABASE) associated with each part in the root library and with each macro describing which parts and which macros can be selected for a given GULTIGEN DNA codestring. The rules include a series of Boolean if / then operations that, if satisfied, reference a part (PARTIAL SELECT) to be included in the BOM, or a macro (MACRO SELECTION) that is included in the inventory SWITCH PICTURES or LAYOUTS shall be.

When the APE PROMISE DLL or APE EPLAN DLL processes the individual rules (DWEEEB DATABASE) against an order (VALID DNA), instruction sets for selecting and placing macros and assigning parts (PROMISE INSTRUCTION SET, EPLAN INSTRUCTION SET) and ECAD attributes as inputs for ECAD systems (PROMISE APPLICATION, EPLAN APPLICATION). The ECAD APIs (APE PROMISE API, APE EPLAN API) automatically execute the instruction sets and generate inventory drawings, BOMs, and manufacturing reports (SCHILLBILDER, LAYOUTS, BOM, LABELS, CABLE LABELS, MANUFACTURING REPORTS) without the need for manual intervention (ECAD). INTERFACE). The results are verified in the ECAD ENVIRONMENT and then sent electronically to the appropriate manufacturing group (ECAD INTERFACE).

Inventory production reports (SCHEDULE, LAYOUTS, BOM, MARKINGS, CABLE LABELS, MANUFACTURING REPORTS) are archived using the APE DB SYNC DLL and DB SYNC interface for future aftermarket and support access (PORT MARKET WEB INTERFACE, SPARE PARTS ORDERING) (LIBRARY OF PUBLISHED JOBS).

The treatment of macros is a notable aspect of the exemplary system. Unlike conventional ECAD systems that aggregate macros and macro attributes, the illustrative embodiment effectively separates them and stores product line-specific macro attributes in a separate database that can be called from the ECAD APIs. The ECAD system includes the drawing macros for relevant components along with their traditional macro attributes. However, in the exemplary embodiment, when ECAD APIs call a particular macro from an ECAD program, they also call a set of product line-specific macro attributes from the macro attribute database (DWEEEB in 5A ) up or down. The conventional macro attributes are ignored or overridden by the ECAD API in accordance with the product line specific macro attributes. Therefore, in the exemplary embodiment, ECAD macros may be paired with multiple sets of product-specific macro attributes that effectively redefine the macro as needed to facilitate the production of schematics and inventory drawings not only for multiple product lines of a particular OEM, but also across product lines of multiple OEMs ,

The overall benefits of this system include ETO cycle times measured in minutes versus days or even weeks, less human intervention and fewer design errors, complete manufacturing and aftermarket support specifications in the form of inventory drawings, BOMB, and manufacturing reports (PICTURES, LAYOUTS, BOM, LABELS, CABLE LABELS , MANUFACTURING REPORTS) and a system that is constantly improved by the iterative process of quality control.

EXTENSIONS

Price Tool Extensions

Price information can be optionally added to the parts master list (ERP-PART-INFO-DB). Along with PARTIAL SELECTION rules, the example system uses a QUOTING DLL and an OFFSET / PREISTOOL GUI interface to calculate and display pricing information (SWITCHBOARD BOM, BOM PANEL OFFER) when the sales organization configures an order (VALID DNA). This ability to generate instant quotes at the time of configuring a custom panel order is another competitive advantage.

Harness and cable processing extensions

If one imagines switchboards as the brain and the OEM product as the body, the harness connecting the brain to the body can be considered the nervous system. For every potential panel in an OEM family, there is a unique set of harnesses required to connect a panel to the OEM product.

The example system includes a wire harness parts and pricing rule database (HDB CABLE TREE, HDB COMPONENT PRICE), which is processed with the APE HRNS DLL (CABLE TREE GUI) to process both quotes (CABLE TREE OFFER) and production reports (CABLE TREE GUIDE). PRODUCTION HALL REPORT, CABLE TREE LABELING REPORT) for the external wiring harnesses. Harness shop floor reports may include instruction kits for use with automatic wire processing machines.

While most of the harness information can be captured in a draft-ready format, the lengths of the harnesses depend on the size, shape, and electrical routing within of the ordered OEM device. Through the exemplary system, OEMs can choose to include this additional harness information (CUSTOM EXTERNAL CABLE TREE INPUT FILE) together with the panel configuration (VALID DNA + CABLE TREE).

In addition to the harness data, a set of panel cable information (WDB-CABLES) can be created for the product family. This set of data / rules is used by the APE WIRE MACHINE DLL to compile a cable production report (CABLE PRODUCTION HALL REPORT) and a set of instructions for an automatic cable processing machine. The exemplary embodiment supports Schleneger brand cable machines (SCHLENEGER INTERFACE, SCHLENEGER INSTRUCTION SET), but the system architecture also allows for the addition of others, for example Konax. The use of automatic wire processing machines dramatically reduces the time required to cut, strip, label, and terminate cables.

Database synchronization

The example system manages and synchronizes the databases used during the specification, the detailed design, the ETO process, and the manufacturing process (step 2-6) and future aftermarket activities. With the SUB-DATE ENVIRONMENT ENVIRONMENT and the DB SYNC GUI interface, APE builds industry-ready libraries of design-ready data, manages historical production data, and synchronizes information with order-to-delivery applications for internal, vendor, and customer orders.

The exemplary system also helps to differentiate and manage both commercial and technical data for parts. On the commercial side, the system recognizes a central enterprise resource planning (ERP) system as a source of up-to-date parts, pricing and scheduling information (M1 APPLICATION).

While the ERP system specializes in commercial information, there is still a need to manage the technical data such as part specifications, mounting holes, connection point specifications, etc. In many cases, ECAD software applications have proprietary database utilities for managing this type of part data. Similar to the MACROOBJECT DATABASE, the exemplary system uses a more generic APE TECHNICAL PARTS DB that can manage generic parts data across multiple product families, customers, suppliers, and ECAD software applications, while seamlessly synchronizing with an ERP system.

The example system uses this information (ERP PARTICLE INFOs) to populate and update the drafting master libraries (MACROOBJECT DB, TECHNICAL PARTS DB, and DWEEEB DATABASE PARTS SELECTION). Through the DB SYNC interface, the APE DB SYNC DLL extracts information from the ERP system (APE M1 API), combines this information with the APE TECH DB, and makes all necessary data about the ECAD ENVIRONMENT, OFFER TOOLS, MANUFACTURING REPORT generation such as BOMs and aftermarket selection utilities such as the PORT MARKET WEB INTERFACE are available and accessible.

When orders enter the ETO engineering process, orders are managed in parallel from vendor and order-to-delivery perspective. The electronic communication from the exemplary system generates component purchase orders (POs) and automatically sends them to suppliers, manages inventory (ELECTRONIC XML SUPPLIER BOMS, COLLECTION LISTS), and coordinates schedules (MANUFACTURING SCHEDULE, MANUFACTURING REPORTS) between the manufacturing department and the manufacturing department OEM customers.

When jobs are executed through the automated ETO process included in the system, manufacturing reports (PICTURES, LAYOUTS, BOM, MARKINGS, CABLE LISTS, MANUFACTURING REPORTS) and project data (ECAD PROJECTS) are stored in a LIBRARY OF THE WORKED JOBS. This library can in turn be accessed for later reference via the DB SYNC interface. An additional web portal (PORT MARKET WEB INTERFACE) for this historical project data is available for aftermarket support and the creation of SPARE PAR POs.

Last check and PLC logic

The exemplary system also supports the last programming and test operations of the panel before it goes to the OEM customer. Once the panel is mounted, the APE PLC LOAD AND TEST interface uses the APE MFG PLC DLL to download the correct controller instructions (PLC LICENSE INSTRUCTION SET) for the panel PLC (Programmable Logic Controller) and then to test the panel make sure it is working properly (SWITCH PANEL INSPECTION). Thus, audit logs or statements are dynamically loaded to suit the particularities of a particular panel being tested.

Full customization

The exemplary system enables "truly custom" design and fabrication by providing a manual interface for the ECAD applications. In particular, the system may be used to define a partially customized product using the configuration interface to define a product DNA structure and to develop a detailed engineering design, including ECAD schematics. The ECAD circuit diagram can then be changed manually to include options that are not available in the configuration interface. Once the schematic is fully customized with these options, they and associated BOMs, etc. can be generated as with any product that has been fully defined in the configuration interface. This customization process also applies to the mechanical layout and cabinet dimensioning and design, except that 2D or 3D modeling software can be used to manually or automatically create layouts and cabinet designs after the electrical schematic and BOMs have been established. The system can process this engineering design using its manufacturing and ERP automation, as with partially customized designs.

Dynamic generator

An embodiment may be referred to as a "dynamic schematic layout". This embodiment is an extension of the Automated Panel Expert (APE) system disclosed above.

As noted above, one embodiment of the APE system takes a unique set of panel options and creates a functional inventory diagram, a layout drawing, bill of materials (BOM), and unique dashboard manufacturing reports. This is done by preconfiguring the APE expert system with all necessary rules to first select the necessary components and housing from a predefined list of components and a predefined list of enclosures and then configuring the resulting BOM of the parts into a functional inventory and an inventory drawing (Layout), reached.

With the APE system as disclosed above, a prior art analysis of the predetermined list of standard enclosures is used to pre-define a set of rules that assigns fixed locations for each selectable component from the master list for each of the previously selected enclosures.

When the APE system is running, a BOM for a specific panel from the component tree is selected based on the options selected. A separate set of enclosure selection rules is then used to select a suitable enclosure from the predefined enclosure list. The APE system then selects the appropriate predetermined fixed location (derived from the pre-analysis described in the previous sections) for combining each part in the BOM with the selected housing. This location information is then used to automatically produce a stock layout drawing of the unique control panel.

In one embodiment, dynamic layout generation technology goes one step further in the concept of creating inventory layouts. The new dynamic panel layout technology extends an embodiment of an APE system described above by a uniquely designed rule base for generating dynamic package layouts. Dynamic enclosure layouts refer to layouts in which the selected components are efficiently placed in a series of dynamically selected or available enclosures or available spaces. With dynamic layout generation technology, you no longer have to pre-select packages, and you no longer need pre-technology analysis to populate an expert system with specific location data to create an inventory layout.

APE systems were initially developed to automate the manual design required to produce unique high volume Original Equipment Manufacturers (OEM) panels that produce highly variable machines. In this environment, the overall design of the OEM's machine may result in limited space for the placement of a panel. For these highly customized machines, it is not possible to pre-select suitable housings because the resulting space available for the housing and the location at which it is placed are previously unknown. To automate in these cases the manual process of arranging the components in a housing of individual shape and limited space, a new technology and method is desirable.

One embodiment of dynamic panel layout technology differs from the method used in a typical APE expert system as described above. A typical APE system requires pre-technology analysis and manual input of specific detailed information for each combination of potential components and potential enclosures that can potentially be used in a panel.

The dynamic panel layout technology interface relies not on a large number of predetermined peculiarities but on general rules (profile) previously performed manually by the engineers while performing the pre-technology analysis described above. These rules are now used with the new dynamic switchboard layout expert system architecture and can be executed dynamically by an APE system, fully automating custom switchboard layouts.

This method has several advantages. The time required to configure the layout part of an APE expert system is reduced, and the APE system now has the ability to select the most suitable enclosure from a dynamically changing list of differently sized enclosures, or it can design layouts for a truly customized one create available space.

Dynamic panel layout technology uses profiles. A profile is a registered set of general rules that were previously used during the pre-draft process. Advance rules are those normally used by more experienced panel designers in the course of their daily work. For example, the engineer may generally want to place separator components in the center and top of the dash panel. In general, the engineer can route the power cables out of the bottom of the housing, and generally he can place a set of terminal strips on a horizontal strip of DIN rails somewhere in the middle. A complete set of these general rules used in an entire dashboard program for an OEM is called a profile. A complete sentence refers to all the rules necessary to group and place all potential components in a closed space.

During the conventional pre-development process, the engineer, through the use of a conventional finished Computer Aided Design (CAD) application, would apply these general rules over and over again to specify predefined specific data required for each potential component-to-potential package combination.

In one embodiment of dynamic panel layout technology, an engineer uses a unique method in the form of a software tool to capture the general rules rather than having to manually re-implement them over and over again. A complete description of this unique method and software tool is described below. One embodiment of the dynamic panel layout technology is shown in FIG 10 illustrated.

Once a profile is defined, one embodiment of the dynamic generator system may exploit the profile by successively selecting components from the BOM and applying the general rules in the profile and placing the part in the layout. An example of a BOM is illustrated in Tables 2.1 and 2.2. Table 2.1: device tag PRODUCTION PART NUMBER CBL1 C45-72 CR3 RPM41F7 CR3 RPZF4 CR3 8WH9150-0CA00 CR5 RPM41F7 CR5 RPZF4 CR7 RPM41F7 CR7 RPZF4 CR7 8WH9150-0CA00 CR8 RPM41F7 CR8 RPZF4 CR9 RPM41F7 CR9 RPZF4 CR10 RPM41F7 CR10 RPZF4 DOB1 XB4BD33 DOB1 DRC 006844 DPT1 2641010WD11TIC DPT1 DRC 001260 DS1 GS1GU3 DS1 GS1AE21 DS1 GS1AH430 DS1 DRC 001261 DS1 D03000201 DS1 LPJ-45-SP DS1 349927664 DS3 GS1EU3 DS3 GS1AD020 DS3 DRC 001261 DS3 LPJ-30 SP DS3 349927661 DS3 D03000201 DS4 GS1EU3 DS4 GS1AD020 DS4 DRC 001261 DS4 LPJ-30 SP DS4 349927661 DS4 D03000201 F1A FNQ-R-4 F1B FNQ-R-4 F1C FNQ-7 FAN1 OA172SAP-11-1TBXC FAN1 RHA4000G Table 2.2: device tag PRODUCTION PART NUMBER FAN1 G172-10HA FAN1 RH40000LG FAN1 193422601 FAN1 193422501 FAN1 349937605 FAN1 349937603 FB50 6M30A1SQ FB50 CC630 FB50-FU50C FNQ-20 FU50 CCP 2-30CC FU50 FNQ-R-12 FU50 DRC 010492 FU50 193403801 GLG1 2 / 0TP GLG1 DRC 001433 GLG1 DRC 001264 GLG2 2 / 0TP GLG2 DRC 001433 GLG2 DRC 001264 GLG3 2 / 0TP GLG3 DRC 001433 GLG3 DRC 001264 GRD1 PK4GTA GRD1 349939009 LR1 KDRC3H LR1 DRC 001277 LR1 DRC 001276 LR1 DRC 001258 LR2 KDRC3H LR2 DRC 001277 LR2 DRC 001276 LR2 DRC 001258 LT1 ZB4BV043 LT1 ZB4BVG4 LT1 DRC 006844 LT2 ZB4BV043 LT2 ZB4BVG4 LT2 DRC 006844 LT3 ZB4BV043 LT3 ZB4BVG4 LT3 DRC 006844 LT4 ZB4BV063 LT4 ZB4BVG6

Information for each component, such as size, shape, assembly information, macro drawing, connection point location, etc., is stored in a parts database. This is general information about the component itself, which is in no way specific to the panel or housing in which it is housed. Once these data are in the library, they can be used in a number of panels or dynamic generator systems. In one or more embodiments, the library includes general component information in the sense that it only needs to be entered into the library once, and that information can then be used repeatedly for multiple panels that use multiple dynamic multi-program generator systems for multiple OEMs can be.

As soon as the dynamic generator system places all components from the BOM in a selected housing, the system checks for overlaps. If one or more overlaps are found, the system may go to subsequent, perhaps larger, enclosures from a list until a housing is found that can accommodate a layout of all components in the BOM under the profile's guidelines. For those instances where the dynamic panel layout technology is used for a single custom space, the system will show where overlapping occurs or produce the layout if all the components from the BOM can be accommodated in the specified space.

In general, the dynamic panel layout generator assembles all of the location and part data needed to create a layout. The compiled layout data can be configured and displayed in a variety of styles and formats.

The layout itself first appears in a dynamic layout application. 12 illustrates a sample layout 1200 ,

The compiled layout data can also be used to automate the creation of CAD layout drawings or solid models or eCAD. This is accomplished by post-processing the compiled layout data and applying it via the Application Programming Interfaces (APIs) offered by finished CAD standard applications. For example, AutoCAD, Solid Works and ePLAN CAD applications can be used, but many more are possible.

The compiled layout data also contains all the information needed to modify enclosures with all the necessary mounting holes, display openings, etc. This information is collected in instruction sets or input files for NC milling machines that are used to automate the milling and drilling of these modifications.

Although one embodiment of the dynamic panel layout has been developed as an extension of one or more embodiments of the APE system for use in the OEM panel industry, it has wider applications. Dynamic panel layout technology can be used as a standalone panel design application. In such applications, the operator is typically a control engineer who creates custom dashboard designs. The engineer can efficiently manipulate his own personal general rule profile to quickly create panel layouts by simply adding components to a BOM and executing the application with the desired enclosures.

As described above, an embodiment of the APE layout technology has been developed for specific situations in which conventional package sizes may be pre-selected for the panel requirements of an OEM. In these situations, all assembly information for each possible component that can be placed in each of the previously selected enclosures was captured in a pre-technology analysis. This data was then often used to pre-plate sheet metal mounting plates that contained all the necessary mounting holes for all potential components. (The Swiss Cheese Method) Even though only a small subset of potential components has ever been mounted on a single plate, and so on yet only a small subset of the mounting holes have ever been used, it is still often more cost effective to pre-punch these standardized mounting plates.

The dynamic panel layout tool can be configured to not only take a single panel BOM as input, but to place the entire component history of the components and, often by appropriately overlapping them, place them to generate the NC input. which is required for the information files for the Swiss-Cheese months. This significantly reduces the advance technology analysis time necessary to determine all mounting locations while ensuring that the potential components do not interfere with each other.

In one embodiment, the dynamic layout generator is used to dynamically generate switchboard layouts. The generator uses the following information to create layouts - a Bill of Materials (BOM) dashboard, a list of possible enclosures, at least one layout profile, and data in a parts database for each component in the BOM.

10 illustrates a detailed flowchart of a process 1000 to create a layout.

The reference numerals in 10 describe:

LIST OF REFERENCE NUMBERS

1005

parts list

1010

Parts database

1015

layout profile

1020

setting profile

1030

Create panel component objects

1025

Create dashboard option objects

1035

Start layout generation

1040

Housing to test?

1045

Place next group in housing

1070

No valid layouts found

1050

All groups placed?

1060

Overlap found?

1065

Return switchboard layout

1055

Add cable routes and wiring harness

Before the layout can be created, a certain preprocessing must be done. For each component in the bill of material ( 1005 ), data from the parts master database ( 1010 ). It is assumed that a component should not be placed in the layout if no data is found in the part master database. The generator can be configured to issue a warning if a component is not found. Then the layout profile ( 1015 ) and the program settings ( 1020 ) (Settings Profile) in an "Options" object 1025 read. The "options" object 1025 contains all the information needed to place the components in the enclosure. It also contains a list of enclosures that can be used.

Once all preprocessing is complete, the actual layout production begins. Starting with the first case, that in the settings profile 1020 is listed, the program starts creating layouts ( 1030 . 1035 ). Each group becomes independent according to the options in the layout profile 1015 constructed. When all groups are created and placed in the enclosure ( 1040 . 1045 . 1050 ), cable routes are added to connect all groups that are wired together ( 1055 ). If no valid layouts are found ( 1070 ), the process ends. Finally, a method is called that is based on overlapping components ( 1060 ) checks. If no overlap is found, a valid layout has been created ( 1065 ). If a component overlap is found, the program moves to the next housing and creates another layout ( 1040 ). It is possible to create a layout for each enclosure and still not find a valid layout. In this case, the layout profile ( 1015 ) or a new layout profile ( 1015 ) must be created.

In one embodiment, the generator may illustrate a valid layout by "trying" a chassis, that is, the dynamic layout generator creates a layout in the selected chassis. The generator shows the result regardless of its validity (ie also in case of an overlap). This feature allows you to export layouts that are not valid for manual customization.

A user of the generator can set up a list of enclosures for a particular project and / or customer. A list of enclosures includes information such as a case name, a part number, a panel depth, a door height and width, and a back height and width.

After creating the list of enclosures, one or more layout profiles are added for each enclosure. In one embodiment, layout profiles are created using a Layout Builder tool, described in more detail below. When adding layout profiles to a chassis, the builder can prompt a user to choose any profile variant that the user wants to use. The user can select as many profile variants as he likes. The user can also rearrange the profile variants by dragging and dropping them. In one embodiment, the order of the profile variants determines the order in which the variants are applied to the main options. The user can also add conditions that must be met for a layout profile to be used.

A user can choose from a variety of warnings / errors that the system should display. A user may choose to be notified when there is a component overlap in a dashboard or layout. For example, the component overlap may be displayed in red on the switchboard layout. A user may choose to see an indication of an overlap among groups within the dashboard. For example, the group overlap may be displayed in red, as in the case of component overlap. However, the group overlap is normally acceptable in a switchboard layout, so a user may wish to disable this feature and enable it only for troubleshooting or other specific purposes. A user can configure the generator to allow overlap on the panel door since there is usually enough room on the door to manually move overlapping components (as opposed to fitting components to the back, which is usually more difficult than components to adapt to the door). A user can configure the generator so that component padding goes beyond the panel. It should be noted, however, that the component itself must not be too close to the edges of a panel when component padding goes beyond the panel. The generator system can be configured to record alerts in a log file. An enhanced version of the log file can be configured to display much of the verbose information in the log file. The generator may also be configured to display a warning when a component is placed in the layout with respect to components that are not present in the profile. The generator can also be configured to display a warning if a component listed in the BOM is not found in the layout profile. This feature is useful for preventing a user from accidentally skipping components in the layout. The generator can be configured to ignore one or more components for each setting profile. Any part that the user wants it not to appear in the layout should be put on this list. The generator can be configured to display every single layout that is created while searching for the optimal chassis. This feature is useful for troubleshooting layout profiles because it allows the user to see how much a case is too small.

The generator can transfer data directly to a server to immediately create a three-dimensional model of the panel. Using this feature typically requires specifying a directory to place the files in after creating the three-dimensional model, the IP address of the server, and a port of the server.

Sometimes, a user may want to use only certain layout profiles if certain conditions are met. This can be achieved by using a profile conditions function. The profile conditions can be used in two ways. First, layout profiles are selected if certain criteria are met. Then a variant is added to all layout profiles if certain criteria are met.

To use profile conditions to select layout profiles, a user chooses an enclosure and a profile, and then selects the conditions for that layout profile. In one embodiment, the generator may be configured to display all profile conditions under a drop-down menu. To then add a profile condition to this layout profile, a user selects one of the profile conditions from the drop-down menu. A user indicates whether this condition is true or false got to. Finally, a user indicates that he wants to add the profile condition, and the generation adds it.

A user can also use profile conditions to add variants to the layout profiles. These rules can be referred to as so-called conditional variants. There are three fields that a user must identify before the user can add a Conditional Variant: variant name, profile condition, and Boolean value.

To create a layout profile, a user can use a tool called a Layout Builder. The Layout Builder allows a user to add options and preferences for each component that might be on the BOM. To use the Layout Builder tool efficiently, a user must know how to set up the component options.

There are some important organizational divisions in a layout profile. The three main divisions are: dashboard options, group options, and component options. Before explaining all fields in the options, here are some important terms that need to be explained.

A "group" is a set of components whose placement depends on the location of other panel components in the same group. In other words, all components that lie next to each other should be in the same group.

In the options there are left, right, upper and lower padding. Padding refers to the empty space required on a particular page of a component, group, or back. This space is required for cabling and cooling requirements.

A cable path is a path at the back reserved for cables. The easiest way to imagine a cable path is to use an invisible part of the wiring harness. The cable routes are automatically added by the software and can be customized for each group. The Layout Builder tool includes the following options.

• • Neue Layoutoptionen: Neues Layoutprofil erstellen
• • Layoutoptionen laden: Gespeichertes Layoutprofil öffnen
• • Speichern: Aktuelle Layoutprofil auf Datenträger speichern
• • Speichern unter ...: Aktuelles Layoutprofil als neues Profil speichern
• • Schließen: Layout Builder schließen. Falls Änderungen vorgenommen wurden, wird ein Benutzer aufgefordert, das Layoutprofil zu speichern.

file

• • New Layout Options: Create New Layout Profile
• • Load layout options: open saved layout profile
• • Save: Save current layout profile to disk
• • Save as ...: Save current layout profile as a new profile
• • Close: Close Layout Builder. If changes have been made, a user is prompted to save the layout profile.

Tools

• • Load Cable Report: Select a cable report to read. This completes the section Cable Route Information of Group Options.
• • Check For Profile Errors: Performs a series of checks on the current layout profile, looking for potential logic errors or missing component references.
• • Add variant: Adds a new variant to the profile. Variants are detailed below.

Help

• • View option documentation: View the software documentation. This is the documentation for the actual code. It is probably not useful to the end user.
• • Show Help on Override: The Layout Builder displays pop-up messages when a user hovers over a field or group of fields.

The dashboard options are the smallest and simplest set of options in the layout profile. The most useful feature is the Add Group function. The switchboard options further include a name of the layout profile. This field is only a reminder of which type of layout this set of options should be used for. The options further include the empty space (pad left) required at the left edge of the back. All pad options are useful when the outer edge of the back panel needs to be empty. The empty space (pad right) required at the right edge of the back. Of the empty space (pad top), which is required at the top of the back. The empty space (pad below), which is required at the bottom of the back.

Group options fall into three categories: general, lines, and cable routes. These three categories contain all the options and preferences for a single group. There can be any number of groups in a layout profile.

In the general category, components can be added by entering a device ID into a group. For group options, the name of the group should describe the set of parts it contains. The place should describe where the group is placed. A group may be on the back, on the door, or on any side of the enclosure. After placement, an offset can be added to a group. In addition, when this group is placed relative to another group, the offset is added after placement of the group.

There are two aspects to the relative location of a group. First, there is the x-location of a group in relation to the width of the back (or door). The alignment determines where the insertion point is in the group. Second, there is the y-location of this group in terms of the height of the back (or door). The alignment determines where the insertion point is in the group. Here are some examples that show how the relative location works. casing Panel Width Panel Height X location X-alignment Y location Y alignment Description of the placement 1 30 60 50 Left 0 Above On top in the middle 2 30 60 100 Right 100 Below Bottom right corner 3 30 60 50 center 50 center Exact middle 13 illustrates the placement of packages 1, 2 and 3 based on the above table. The point 1310 is the insertion point of the group. The location of this insertion point depends solely on the orientation options. The relative location determines the distance between the edges of the panel and the insertion point, and the software can rearrange groups to eliminate overlapping of the components.

When designing a layout profile, it often happens that the location of one group depends on the location of another group. The Relative Group options allow relative placement of groups. To set the Relative Groups options, a user specifies a relative group, selects the group that has just been added to a list box, and populates the Relative Groups radio buttons. Starting with the relative group at the top of the list, the dynamic layout generator attempts to place that group relative to the relative group. If this fails, he simply moves on to the next group in the list.

If he has gone through all relative groups and that group is still not placed, the group is placed in accordance with their relative location.

A user can specify on which side of the relative group a particular group is placed. A user can specify the distance to be added between the group next to the usual padding. A user can specify the percentage distance of the total height / width of the relative group in which a particular group is placed.

A user can specify which dimensions of a particular group will be used during group placement. This allows a user to place only the X or Y coordinate of one group in relation to another group. The relative placement of a group can center a group in the dashboard. A user can place a group in relation to two groups. Example of relative group options: casing page Zus. space Relative place alignment X Y 1 Above 0 0 Left Yes Yes 2 Below 0 50 center Yes Yes 3 Right 0 50 Below Yes Yes 4 Left 4 0 Above Yes Yes 5 Above 0 0 Left Yes No An easy way to see the relationship between relative location and orientation is to look at the points 1410 in 14 , The place of the points 1410 on the rectangles 1420 is completely determined by the field alignment. Then the rectangles 1420 and the points 1410 shifted by <relative location>% in the relative group.

One embodiment includes line options that allow a user to automatically create lines of components within control panels. This can save time if a user has a large number of possible device IDs and the user does not want to take the time to enter options for all.

The functions associated with a line option include setting the minimum and maximum lengths of the lines, adding up to three lines, placing components in a line on the DIN rail, adding an additional DIN rail to each line, the placing a line horizontally or vertically, placing a part of a harness between each line, and choosing which components to place on which line in which order. In one embodiment, a user interface includes a "types in group" field. This field is automatically populated for the user with all the different component types that are in this group. To indicate which components are on which line, a user simply pulls the desired "type" into one of the "line fields". The "types" can be rearranged by dragging and dropping as soon as they are in the "line fields".

There are also a number of other fields associated with the line options. A user can set a minimum and maximum line length and a user can set a minimum and maximum number of lines. Although a user may adjust the length and number of lines, the user may also configure the system to ignore the parameters for the length of the lines and the number of lines. If these parameters are ignored, the generator creates a line that is as long as possible before it overlaps another group or leaves the back. The line options can be used per user interface page. The generator can be configured to add a harness between each line. This option meets padding requirements for all components on the lines. As noted, a user may configure a layout such that a line runs either horizontally across a back or door or vertically over a back or door. The generator can also be configured so that all components are on a line on a DIN rail. In addition, the user can specify additional centimeters for the DIN rail added at the end of each line. The user can configure the system so that all lines have a DIN rail of the same length. This is useful if a user wants to make sure this group is a rectangle.

A cable path option allows a user to select which sides of the respective group should contain cable paths - no cable path, cable path, and cable path with wiring harness. A user can set the "nominal space" between the group and the cable path.

The cableway option user interface may include an information section that shows which groups this group is connected to, as well as information about the cables that are connected to components in that group. This information can be reported in a cable report. A cable report can be dynamically used to determine the padding of the individual components based on the cable bending radii.

A parts options UI page has all options for placing a single component in a group. When a group is created, the "placement priority" of each component is based on its position in a tree view on the left side of this window. Both groups and parts can be rearranged by dragging and dropping in the order in which they are to be placed on the back / door.

There are a variety of part options. The name is the device ID of a component. In a UI, a user can use a placeholder format to include multiple device IDs. The type is the type of a component. This must match the type specified in the parts master database. This field allows you to place multiple components in a chassis that have the same device ID. (eg VFD and VFD keyboard, both with device ID "VFD1"). A user may also specify an angle by which a component can or should be rotated when placed within the layout or housing. A user can specify that a component is placed on a line using the line options in the group options of that group. A user can place one component on the padding of another component. This feature is useful for small parts with a lower profile. (eg ground connections and grounding chains). A user can also configure the generator to ignore component overlap. Some components can be mounted directly on sheet metal or a DIN rail. The generator can be configured to mount all the components that can be mounted on a DIN rail, and so that if a user wants to ensure that a component is not mounted on a DIN rail, it will not is mounted so.

A user can specify an absolute X and Y coordinate of a component in a group. It should be noted that this is not an absolute x / y coordinate for the entire back / door. A user can specify padding on each side of a component. A standard padding is stored in the parts master database. However, a user can override the default padding values.

A user can align door components over the back. In particular, sometimes a component on the door must be aligned over a component on the back. This is the case for a disconnector and its switch, for example. To accomplish this, a data table stores a dot (x / y) on a component that may need this option. If two components need to be aligned, the component is placed normally on the back. Also, when the options for the door-mounted component are selected, a user specifies the device ID of the component mounted on the back panel. If the user has selected the "Align via component" option, the software retrieves the points that need to be aligned and places the door mounted component accordingly.

Wildcard device IDs are a powerful feature when adding a component that can have many different device IDs. Certain components, such as MMPs, often have many different possible device IDs (eg, MMP1 through MMP40). Instead of adding 40 parts to a group, a user can cover all 40 MMPs with a single placeholder.

Problems can quickly arise when trying to place components with wildcard device IDs in relation to each other. To fix this problem, another wildcard with a slightly different syntax can be used to refer to relative parts.

After a user has created a preference profile and a layout profile, the user can begin creating layouts. First, a user should check if at least one layout profile is associated with each enclosure in the settings profile. If not, no layout is created.

A user selects a BOM and a layout is created based on the settings profile, the layout profile, and the BOM.

A user may receive the "Profile missing device ID" warning if the parts list contains device IDs that are not in the layout profile. At this point, a user may either stop running the dynamic layout generator and save the list of missing device IDs in a file, or continue running the dynamic layout generator and ignore this warning. It is recommended that a user add the missing device IDs to the layout profile or, if the user does not need them, add them to the user's ignore list. If this error does not appear, it means that a layout should have been created. A user can look in the log, to make sure a valid layout was found successfully. If the layout creation was successful, the user is presented with a diagram of the layout.

A user might want to see what the layout would look like in a particular enclosure. One embodiment includes a "test chassis" feature that allows a user to do so. The drop-down box in the Test Enclosure section automatically populates with any enclosures a user typed in the preference profile. First, a user selects a BOM for testing, initiates "Test Case", and the layout is displayed regardless of whether it is valid or not. If the user has selected a housing that is too small, the user sees overlapping components. A user can test cases that almost fit. This is a good way to see how the layout profile needs to be adjusted. As previously mentioned, illustrated 12 an example of a display of a layout.

A user can move the layout with a computer mouse and zoom in / out. To move the image, the user holds down the middle mouse button (or scroll wheel) and moves the mouse. To enlarge / reduce the image, the user uses the scoll wheel. Scrolling up and zooming down scrolls down.

A toolbox allows a user to turn different layers on and off in the layout image. The layer settings are automatically saved in the settings profile. These levels include physical parts, parts padding, physical groups, group padding, part labels, DIN rails, overlap, and cable paths.

When a user has created a layout and the user is satisfied with what it looks like, the user can export the layout in a variety of formats. For example, the user can export the generated layout to a DXF file. Additionally, ShortestDistance exports and SolidWorks exports are usually done using the Dynamic Layout DLL.

15 is a block diagram 1500 that illustrates the features of a dynamic generator. 15 includes a series of blocks 1505 - 1582 , Even if in the example of 15 In addition, other examples may rearrange the blocks, skip one or more blocks, and / or execute two or more blocks in parallel using multiple processors or a single processor organized as two or more virtual machines or sub-processors. In addition, still other embodiments may implement the blocks as two or more specific interconnected hardware or board modules having interconnected control and data signals communicated between and over the modules. Therefore, every process flow (process flow) applies to software, firmware, hardware and hybrid implementations.

The reference numerals in 15 describe:

LIST OF REFERENCE NUMBERS

1505

Data associated with a plurality of panel housings and a set of rules for the design of a panel are provided

1510

A selection of two or more components for placement in the panel housings are received

1515

Information about the two or more components is retrieved from a database

1520

One or more layouts are created

1525

The panel housings are dynamically selected as a function of the one or more sets of controls, the two or more components, a device to be controlled by the cabinet, and an application of the device

1530

A library of rules for the design of a panel is used to create a panel profile

1535

The panel profile is used to apply the library of rules and to select a particular panel housing

1540

The panel layout is dynamically created by placing the two or more components in the particular panel housing as a function of a relationship between the two or more components to the particular panel housing

1550

The system checks for an overlap in the placement of the two or more components or a compatibility conflict between the two or more components

1552

The system chooses a larger enclosure if it is determined that a q current enclosure contains an overlap

1,554

The system receives a selection of the two or more components from a bill of material

1556

The information about each of the two or more components includes one or more sizes, shapes, assembly information, drawings, and point of connection information

1558

The system generates one or more computer aided design (CAD) drawings and a solid model using one or more layouts

1560

The system applies a selection of the two or more components to a specially selected panel housing

1562

The system places a particular component in a plurality of versions of a particular panel housing at various locations in the plurality of versions

1564

The system places a particular housing in the plurality of panel housings and removes a particular housing from the plurality of panel housings during creation of the one or more layouts

1566

The system will create a new panel enclosure if none of the large number of panel panels results in a working layout

1568

The set of rules or library of rules includes rules that were previously used by a panel engineer during a pre-drafting process

1570

The system uses the set of rules or the library to create a variety of panel profiles, with each panel profile intended for a particular panel application

1572

The system complements the library by receiving and saving additional panel design rules

1574

The particular panel application includes a generic panel application with one or more sizes or forms of a panel

1576

The particular panel includes a specific panel application with one or more specific types, brands and models of the equipment to be controlled by the panel

1578

The system creates several switchboard profiles

1580

The system creates a large number of switchboard layouts

1582

The system chooses a larger enclosure if it is determined that a current enclosure contains an overlap

With reference to 15 become at 1505 Data is provided in conjunction with a plurality of panel housings and a set of rules for the design of a panel. at 1510 For example, a selection of two or more components is received for placement in a panel housing. at 1515 Information about the two or more components is retrieved from a database. at 1520 One or more layouts are created. The one or more layouts include the placement of the two or more components in at least one of the plurality of panel housings as a function of the set of rules for the design of a panel. at 1525 For example, the panel housings are dynamically selected as a function of the one or more sets of rules, the two or more components, a device to be controlled by the cabinet, and an application of the device.

In an alternative embodiment, as indicated at 1530 begins, a library of rules for the design of a panel is used to create a panel profile. The dashboard profile contains design criteria for a particular dashboard application. at 1535 the dashboard profile is used to apply the library of rules and select a particular dashboard housing. at 1540 For example, the panel layout is dynamically created by placing the two or more components in the particular panel housing as a function of a relationship between the two or more components and a relationship of the two or more components to the particular panel housing.

at 1550 the system checks for an overlap in the placement of the two or more components, or a compatibility conflict between the two or more components. at 1552 the system will choose a larger case if an existing case is found to contain an overlap. at 1554 the system receives a selection of the two or more components from a bill of material. at 1556 For example, the information about each of the two or more components includes one or more sizes, shapes, assembly information, drawings, and connection point location information. at 1558 The system generates one or more computer aided design (CAD) drawings and a solid model using one or more layouts.

at 1560 The system applies a selection of the two or more components to a specially selected panel housing. at 1562 The system places a particular component in a plurality of versions of a particular panel housing at various locations in the plurality of versions. at 1564 The system adds a particular housing to the plurality of panel housings and removes a particular housing from the plurality of panel housings during the creation of the one or more layouts. at 1566 The system creates a new panel enclosure when none of the multiple panel cabinets results in a working layout. at 1568 For example, the set of rules or the library of rules includes rules that were previously used by a panel engineer during a pre-design process (pre-design process).

at 1570 For example, the system uses the set of rules or the library to create a variety of panel profiles, with each panel profile intended for a particular panel application. at 1572 The system complements the library by receiving and saving additional panel design rules. at 1574 For example, the particular panel application includes a generic panel application having one or more sizes or shapes of a panel. at 1576 For example, the particular panel includes a specific panel application having one or more particular types, brands and models of the instrument to be controlled by the panel. at 1578 The system creates several panel profiles. at 1580 The system creates a large number of switchboard layouts. at 1582 the system will choose a larger case if an existing case is found to contain an overlap.

Example of the dynamic generator

The following sections, Tables 3.1, 3.2, the in the example shown below for a panel component profile and 18 and 19 illustrate an example implementation of the dynamic generator.

Tables 3.1 and 3.2 are an example of a bill of materials (BOM).

Table 3.1: device tag PRODUCTION PART NUMBER CBL1 C45-72 CR3 RPM41F7 CR3 RPZF4 CR3 8WH9150-0CA00 CR5 RPM41F7 CR5 RPZF4 CR7 RPM41F7 CR7 RPZF4 CR7 8WH9150-0CA00 CR8 RPM41F7 CR8 RPZF4 CR9 RPM41F7 CR9 RPZF4 CR10 RPM41F7 CR10 RPZF4 DOB1 XB4BD33 DOB1 DRC 006844 DPT1 2641010WD11TIC DPT1 DRC 001260 DS1 GS1GU3 DS1 GS1AE21 DS1 GS1AH430 DS1 DRC 001261 DS1 D03000201 DS1 349927664 DS1 GTT-2-2-W / C DS1 LPJ-45-SP DS3 GS1EU3 DS3 GS1AD020 DS3 DRC 001261 DS3 LPJ-30-SF DS3 349927661 DS3 D03000201 DS4 GS1EU3 DS4 GS1AD020 DS4 DRC 001261 DS4 LPJ-30 SP DS4 349927661 DS4 D03000201 EXHAUST G172-10HA F1A FNQ-R-4 F1B FNQ-R-4 F1C FNQ-7 Table 3.2: device tag PRODUCTION PART NUMBER FAN1 OA172SAP-11-1TBXC FAN1 G172-10HA FAN1 193422601 FAN1 193422501 FAN1 349937605 FAN1 349937603 FB50 6M30A1SQ FB50 CC630 FB50-FU50C FNQ-20 FU50 CCP 2-30CC FU50 FNQ-R-12 FU50 DRC 010492 FU50 193403801 GLG1 2 / 0TP GLG1 DRC 001433 GLG1 DRC 001264 GLG2 2 / 0TP GLG2 DRC 001433 GLG2 DRC 001264 GLG3 2 / 0TP GLG3 DRC 001433 GLG3 DRC 001264 GRD1 PK4GTA GRD1 349939009 LR1 KDRC3H LR1 DRC 001277 LR1 DRC 001276 LR1 DRC 001258 LR2 KDRC3H LR2 DRC 001277 LR2 DRC 001276 LR2 DRC 001258 LT1 ZB4BV043 LT1 ZB4BVG4 LT1 DRC 006844 LT2 ZB4BV043 LT2 ZB4BVG4 LT2 DRC 006844 LT3 ZB4BV043 LT3 ZB4BVG4 LT3 DRC 006844 LT4 ZB4BV063 LT4 ZB4BVG6

An example of a panel component profile is illustrated below. This is part of a profile (VFD (Variable Frequency Drive) profile example):

*** group name: VFD ***

At the front: BP
Placed at 0% of the total panel width
Placed at 0 [%] of the total panel height
X-orientation: Left
Y-alignment: Top

Parts in this group.
Total parts: 6
*** Device ID: VFD <> ***
Type of part: VFD
DIN rail preference: standard
This part can be placed in relation to the following parts
Total relative parts: 1
*** Relative Part: VFD <->: VFD ***
Placed on the side: Right
0% over the relative part
Mind. of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Device ID: GLG <1-49> ***
Type of part: GLG
This part can be placed in the padding of other parts
This part is rotated at DRC.DynamicLayout.Data.Angle degree
DIN rail preference: standard
This part can be placed in relation to the following parts
Total relative parts: 1
*** Relative Part: VFD <-1>: VFD ***
Placed on the side: Below
Added 0.5 inches of extra space between parts
0% over the relative part
Mind. of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Device ID: VFD1 ***
Type of part: VFD
An absolute location is used for this part
Place 0 inches from the left side of this group
Place 0 inches from the top of this group
DIN rail preference: standard

*** Device ID: DPT <> ***
Type of part: PS
This part is rotated at DRC.DynamicLayout.Data.Angle degree
DIN rail preference: standard
This part can be placed in relation to the following parts
Total relative parts: 3

*** Relative Part: DPT <->: PS ***
Placed on the side: Top
0% over the relative part
Mind. of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Relative Part: VFD1: VFD ***
Placed on the side: left
100% over the relative part
Max of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Relative Part: VFD <+>: VFD ***
Placed on the side: left
100% over the relative part
Max of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Device ID: WARMERAD ***
Type of part: VFD
DIN rail preference: standard
This part can be placed in relation to the following parts
Total relative parts: 1
*** Relative Part: VFD <MAX>: VFD ***
Placed on the side: Right
0% over the relative part
Mind. of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

*** Device ID: GLG50 ***
Type of part: GLG
This part can be placed in the padding of other parts
This part is rotated at DRC.DynamicLayout.Data.Angle degree
DIN rail preference: standard
This part can be placed in relation to the following parts
Total relative parts: 1
*** Relatives Part: WARMERAD: VFD ***
Placed on the side: Below
Added 0.5 inches of extra space between parts
0% over the relative part
Mind. of the part is placed
X coordinate is placed relative to this part
Y coordinate is placed relative to this part

18 and 19 illustrate two exemplary layouts that show the results when the dynamic layout generator profile is used to place the components from the BOM in two different sized enclosures.

The example profile rules illustrated in the above panel component profile describe the placement of the VFD components. First, all VFDs are grouped together with some other smaller components. Then, the first VFD found in the BOM is placed in the upper left corner of the housing. If the dynamic generator finds additional VFDs in the BOM, it places them to the right of the first VFD. In this BOM example, there are two VFDs that finds and processes the profile.

The profile can be used to place the components in the BOM in different size cases. In the first exemplary layout diagram ( 18 - Overlapping layout), the housing is too small and there is an overlap. The dynamic generator can then try a larger case until everything fits, as in the second example layout (FIG. 19 - Valid layout).

20 FIG. 12 is an overview diagram of a hardware and operating environment with which embodiments of the invention may be put into practice.

The reference numerals in 20 describe:

LIST OF REFERENCE NUMBERS

21

Processing unit

22

system memory

23

system

24

ROME

26

BIOS

32

Interface of the hard disk drive

33

Interface of the optical disk drive

34

Interface of the optical drive

35

operating system

36

Application programs

37

Other program modules

38

program data

46

Serial port

47

monitor

48

video adapter

49

Remote computer

51

Local Area Network

52

Wide Area Network

53

Network interface

54

modem

The description of 20 is intended to provide a brief, general description of suitable computer hardware and a suitable computing environment with which the invention may be implemented. In some embodiments, the invention is described in the general context of computer-executable instructions, for example, program modules that may be executed by a computer, such as a personal computer. In general, program modules include routines, programs, objects, components, data structures, etc., that perform certain tasks or implement certain abstract data types.

In addition, it will be apparent to those skilled in the art that the invention can be practiced with other computer system configurations, such as handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. A. The invention may also be practiced in distributed computing environments in which tasks are performed by I / O remote processing devices connected via a communications network. In a distributed computing environment, program modules can reside in both local and remote storage devices.

In the embodiment which is in 20 is presented, a hardware and operating environment is provided that applies to all servers and / or remote clients shown in the other figures.

As in 20 As shown, an embodiment of the hardware and operating environment includes a general-purpose computing device in the form of a computer 20 (eg a PC, a workstation or a server) with one or more processing units 21 , a system memory 22 and a system bus 23 containing various system components including system memory 22 with the processing unit 21 operatively couple. It may only be one or it may be more than one processing unit 21 give, so the processor of computer 20 includes a single CPU or a plurality of processing units, commonly referred to as a multiprocessor or parallel processor environment. A multiprocessor system may include cloud computing environments. In various embodiments, computer is 20 a conventional computer, a distributed computer, or another type of computer.

The system bus 23 can be any type of bus structure, including a memory bus or memory controller, a peripheral bus, and a local bus using a variety of bus architectures. The system memory may also be referred to simply as memory and, in some embodiments, includes read-only memory (ROM). 24 and Random Access Memory (RAM) 25 , A Basic Input / Output System (BIOS) program 26 which contains the basic routines involved in the transfer of information between items in computers 20 help, for example, during startup, can in ROM 24 be saved. computer 20 further includes a hard disk drive 27 for reading from and writing to hard disk, not pictured, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29 and an optical disk drive 30 for reading from or writing to a removable optical disk 31 , for example a CD-ROM or other medium.

The hard disk drive 27 , magnetic disk drive 28 and optical disk drive 30 are with a hard drive interface 32 , an interface for the magnetic disk drive 33 or an interface for the optical disk drive 34 coupled. The drives and associated computer-readable media provide nonvolatile storage with computer readable instructions, data structures, program modules and other data for computers 20 , It should be apparent to those skilled in the art that any type of computer-readable medium that can store data that can be accessed by a computer, such as magnetic cassettes, flash memory cards, digital video discs, Bernoulli cassettes, Random Access Memories (RAMs), ROMs (Read Only Memories), redundant arrays of independent discs (eg, RAID storage devices), and the like may be used in the example operating environment.

A variety of program modules can be on the hard disk, the magnetic disk 29 , the optical disk 31 , ROME 24 or RAM 25 stored, including an operating system 35 , one or several application programs 36 , other program modules 37 and program data 38 , A secure transmission engine plug-in for the present invention may reside on one or a number of these computer-readable media.

A user can enter commands and information via input devices such as a keyboard 40 and a pointing device 42 in computer 20 enter. Other input devices (not shown) may include a microphone, a joystick, a game pad, a satellite dish, a scanner, or the like. These other input devices are often via a serial port 46 that with system bus 23 coupled to the processing unit 21 but can also be connected through other interfaces, such as a parallel port, a game port, or a Universal Serial Bus (USB). A monitor 47 or another type of display device may also be via an interface, for example a video adapter 48 , with system bus 23 get connected. monitor 40 can display a graphical user interface for the user. In addition to monitor 40 For example, computers typically include other peripheral output devices (not shown), such as speakers and printers.

computer 20 can use logical connections to one or more remote computers or servers, such as remote computers 49 be operated in a networked environment. These logical connections are achieved by a communication device that comes with a computer 20 coupled or part of computer 20 is, wherein the invention is not limited to a particular type of computing device. Remote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device, or another common network node, and typically includes many or all of the computer I / O elements described above 20 even if only a storage device 50 is shown. In the 20 illustrated logical connections include a Local Area Network (LAN) 51 and / or a Wide Area Network (WAN) 52 , Such networking environments are commonplace in office networks, enterprise-wide computer networks, intranets, and the Internet, that is, all types of networks.

When used in a LAN network environment, is computer 20 with LAN 51 via a network interface or adapter 53 connected, that is a kind of communication device. In some embodiments, computer includes 20 usually a modem when used in a WAN network environment 54 (Another type of communication device) or another type of network device z. As a wireless transceiver, for the preparation of communication over the wide-area network 52 , for example the internet. modem 54 , which can be internal or external, is via the serial port 46 with system bus 23 connected. In a networked environment, program modules that are related to computers 20 are illustrated on the remote storage device 50 the remote computer or server 49 get saved. It will be understood that the illustrated network connections are exemplary and other means and communication devices may be used to establish a communication link between the computers, for example fiber-optic coax hybrid, T1-T3 lines, DSLs, OC-3 and / or OC -12, TCP / IP, microwaves, wireless application protocol, and other electronic media through appropriate switches, routers, outlets, and power lines known to those skilled in the art.

Therefore, an exemplary system, method, and machine readable medium has been described for the dynamic generation of panel layouts. Although specific exemplary embodiments have been described, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be considered as illustrative and not restrictive. The accompanying drawings, which are part of the drawings, illustrate, by way of illustration and not limitation, specific embodiments in which the article may be practiced. The illustrated embodiments will be described in sufficient detail to enable one skilled in the art to practice the teachings herein. Other embodiments may be utilized and derived from such that structural and logical substitutions or changes may be made without departing from the scope of this disclosure. Therefore, this detailed description should not be construed as limiting, and the scope of various embodiments is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

Such embodiments of the subject invention may be individually and / or collectively referred to herein by the term "invention" purely for convenience and without any intention to voluntarily limit the scope of this application to a single invention or concept of invention, if indeed more than one is disclosed. Therefore, while specific embodiments are illustrated and described herein, it should be apparent that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover all adaptations and variations of various embodiments. Combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art after reviewing the above description.

The abstract is available to correspond to 37 C. F. R. § 1.72 (b). It is designed to ensure that the reader quickly identifies the nature and key message of the technical disclosure. It is understood that this summary may not be used to interpret or limit the scope or meaning of the claims.

In the foregoing description of the embodiments, various features are summarized in a single embodiment to streamline the disclosure. However, this method of disclosure is not to be construed as expressing an intent that the claimed embodiments have more features than are detailed in each claim. Rather, as the following claims reflect, the subject invention may consist of less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description of the embodiments, with each claim independently depicting a separate exemplary embodiment.

conclusion

The above-described embodiments and claims are merely intended to illustrate or teach one or more ways of putting into practice or implementing the present invention, and not limiting its breadth and scope. The true scope of the invention, which includes all modes of implementation and implementation of the teachings of the invention, is defined only by the appended claims and their equivalents.

Claims (35)

A system comprising: a computer memory comprising data associated with a plurality of panel housings and a set of rules for designing a control panel; and one or more computer processors configured by: to receive a selection of two or more components for placement in panel housings; Retrieve information about the two or more components from a database; and generate one or more layouts, the one or more layouts comprising placing the two or more components in at least one of the plurality of panel housings as a function of the set of rules for designing a panel; wherein the panel housings are dynamically selected as a function of the one or more sets of rules, the two or more components, a device to be controlled by the cabinet, and an application of the device. The system of claim 1, comprising a computer processor configured to check for an overlap in the placement of the two or more components or a compatibility conflict between the two or more components. The system of claim 2, comprising a computer processor configured to select a larger enclosure when it is determined that a current enclosure contains an overlap. The system of claim 1, wherein the computer processor is configured to receive a selection of two or more components from a parts list. The system of claim 1, wherein the information about each of the two or more components includes one or more sizes, shapes, assembly information, drawings, and connection point location information. The system of claim 1, comprising a computer processor configured to generate one or more computer aided design (CAD) drawings and a solid model using the one or more layouts. The system of claim 1, comprising a computer processor configured to apply a selection of the two or more components to a particular selected panel housing. The system of claim 1, comprising a computer processor configured to place a particular component in a plurality of versions of a particular panel housing at different locations in the plurality of versions. The system of claim 1, comprising a computer processor configured to add a particular housing to the plurality of panel housings and to remove a particular one of the plurality of panel housings during the creation of the one or more layouts. The system of claim 1, comprising a computer processor configured to create a new panel housing when none of the plurality of panel housings results in a functioning layout. The system of claim 1, wherein the set of rules comprises rules previously used by a panel engineer during a pre-design process. The system of claim 1, wherein the set of rules comprises a library of dashboard design rules. The system of claim 12 comprising a computer processor configured to use the library to generate a plurality of panel profiles, each panel profile intended for a particular panel application. The system of claim 12, comprising a computer processor configured to supplement the library by receiving and storing additional panel design rules. A system comprising: a computer memory having data associated with a plurality of panel housings and a library of rules for designing a control panel; and a computer processor configured to: use the library of rules to create a panel profile, the panel profile comprising design criteria for a particular panel application; receive an identification of two or more components for placement in a switchboard layout; use the dashboard profile to apply the library of rules and select a specific dashboard housing; and dynamically creating the panel layout by placing the two or more components in the particular panel housing as a function of a relationship between the two or more components and in relation to the two or more components to the particular panel housing. The system of claim 15, comprising a computer processor configured to supplement the library by receiving and storing additional circuit design rules. The system of claim 15, wherein the two or more components are included in a bill of material. The system of claim 15, wherein the particular panel application comprises a generic panel application having one or more sizes or shapes of a panel. The system of claim 15, wherein the particular control panel comprises a specific panel application having one or more particular types, brands, and models of the device to be controlled by the control panel. The system of claim 15, wherein the computer processor is configured to create a plurality of panel profiles. The system of claim 15, wherein the computer processor is configured to create a plurality of switchboard layouts. The system of claim 15, comprising a computer processor configured to check for an overlap in the placement of the two or more components or a compatibility conflict between the two or more components. The system of claim 22, comprising a computer processor configured to select a larger enclosure when it is determined that a current enclosure contains an overlap. The system of claim 15, wherein the identification of the two or more components comprises one or more sizes, shapes, assembly information, drawings, and connection point location information. The system of claim 15, comprising a computer processor configured to generate one or more computer aided design (CAD) drawings and a solid model using the one or more panel layouts. The system of claim 15, comprising a computer processor configured to apply a selection of the two or more components to a particular selected panel housing. The system of claim 15, comprising a computer processor configured to place a particular component in a plurality of versions of a particular panel enclosure at different locations in the plurality of versions. The system of claim 15, comprising a computer processor configured to add a particular housing to the plurality of panel housings and to remove a particular one of the plurality of panel housings during the creation of the one or more panel layouts. The system of claim 15, comprising a computer processor configured to create a new panel enclosure when none of the plurality of panel housings results in a functioning layout. The system of claim 15, wherein the library of rules comprises rules previously used by a panel engineer during a pre-design process. The system of claim 30 comprising a computer processor configured to use the library to generate a plurality of panel profiles, each panel profile intended for a particular panel application. A process comprising: Receiving a selection of two or more components in a computer processor for placement in one or more of a plurality of panel housings; Retrieving information about the two or more components from a database with the processor; and Generating one or more layouts with the processor, the one or more layouts including placing the two or more components in at least one of the plurality of panel housings as a function of the set of rules for designing a panel; wherein the panel housings are dynamically selected as a function of the one or more sets of rules, the two or more components, a device to be controlled by the cabinet, and an application of the device. A computer-readable medium comprising instructions executing a process when executed by a processor, comprising: Receiving a selection of two or more components for placement in one or more of a plurality of panel housings; Retrieving information about the two or more components from a database; and Generating one or more layouts, the one or more layouts comprising placing the two or more components in at least one of the plurality of panel housings as a function of the set of rules for designing a control panel; wherein the panel housings are dynamically selected as a function of the one or more sets of rules, the two or more components, a device to be controlled by the cabinet, and an application of the device. A process comprising: using a processor and a library of rules to create a panel profile, the panel profile comprising design criteria for a particular panel application; Receiving an identification of two or more components for placement in a switchboard layout in the processor; Use the dashboard profile to apply the library of rules and select a specific dashboard housing; and dynamically creating the panel layout with the processor by placing the two or more components into the particular panel housing as a function of a relationship between the two or more components and a relationship of the two or more components to the particular panel housing. A computer-readable medium comprising instructions executing a process when executed by a processor, comprising: Using the library of rules to create a panel profile, the panel profile comprising design criteria for a particular panel application; Receiving an identification of two or more components for placement in a switchboard layout; Use the dashboard profile to apply the library of rules and select a specific dashboard housing; and dynamically creating the panel layout by placing the two or more components into the particular panel housing as a function of a relationship between the two or more components and a relationship of the two or more components to the particular panel housing.

Images