# Industrial Design of Electric Machines Supported with Knowledge-Based Engineering Systems
## 4 Use Case Example: KBE System Implemented for the Elevator Industry Domain
### Domain-Specific Design  
This stage involves many micro-processes. To provide a better understanding, these are grouped into six major processes. Figure 14 shows the user interface. It can be seen that it is composed of six main tabs corresponding to each major process. These processes are now described. 1. Cost function and sizing parameters: The tab \"input parameters for dimensioning\" holds two main features. First, the designer can enter a cost function through MATLAB code, see Figure 14. Inputs of the function are predetermined. During the search of solutions, this function is executed and compared to the cost (requirement) to check its viability. The other feature is in the subtab called \"main inputs\", where the referenced values of the motor selected in the previous stage are loaded automatically. The designer can enter the length of stack values he wishes to check, i.e., a sweep of length from a minimum to a maximum value. He also has the ability to change any parameter of the referenced motor model regarding its material properties. After this, the main algorithm is executed, where for each length of stack solution, alternatives satisfying the requirements are searched by adjusting the number of turns per phase. 2. Winding configuration: The tab name is \"coil construction model\". Here the designer can change any configuration of the winding. The values of the referenced motor (data stored in the PDM system) can be loaded. The designer can then change the wires diameter, number of wires in parallel, number of turns per coil, span, layers, and others. The outputs are parameters that will be used to search for solution alternatives. Figure 14: User interface for the domain-specific design stage of the KBE application. Furthermore, it provides tools to check the star of slots as well as the winding factor spectrum and others. 3. Solution alternatives visualization: The output of the previous processes are solution alternatives (if it exists for the given requirements). Next, in the tab \"alternatives visualizer\", the designer can check the results. The tool provides the capability of graphing any selected parameter as well as table formats. The performance values of each alternative are given in ambient and operating temperature (from the thermal model). Figure 15 shows the tools. For each length of stack, several alternatives can be obtained, one for each number of turns per coil. 4. Multicriteria analysis: The KBE application provides four multi-criteria decision-making methods (MCDM) to support selecting the best solution alternative. Of course, the designer has the freedom of not using it and selecting it by his/her judgment. The methods are the Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS), Weighted Sum Model (WSM), Weighted Product Model (WPM), and Weighted Aggregated Sum Product Assessment (WASPAS). For references, please see [18; 19]. The designer has the option of selecting the criteria (nine available: rated current, maximum current, efficiency, copper temperature, magnet temperature, cost, length, voltage, mass) and inputs their weights according to his judgment. The performance scores are computed based on the weights and the method selected. The output is a list sorted in descendent order. 5. Performance characteristics: The characteristics curves of the chosen motor solution are computed. The data is available in both formats, curves and tables. These characteristics are later compared with the curves of the prototype testing stage. Figure 16 shows some of these features. Once the motor solution is selected, the requirement results column (Figure 14) is filled out automatically with the performance values. Based on the results, the resolution column is also filled out automatically. This column states if the requirement passed or failed. It also shows the warning lamps that turn green on the left if the requirement is satisfied or red if it is not.