Next Article in Journal
Energy Optimisation of Industrial Limestone Grinding Using ANN
Previous Article in Journal
Measuring the Circularity of Bio-Based Fertilizers: Applying the BIORADAR Product Circularity Monitoring Framework
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

Implementing CAD API Automated Processes in Engineering Design: A Case Study Approach

by
Konstantinos Sofias
1,
Zoe Kanetaki
1,*,
Constantinos Stergiou
1,
Antreas Kantaros
2,*,
Sébastien Jacques
3 and
Theodore Ganetsos
2
1
Department of Mechanical Engineering, University of West Attica, 12241 Athens, Greece
2
Department of Industrial Design and Production Engineering, University of West Attica, 12244 Athens, Greece
3
University of Tours, CEDEX 1, 37020 Tours, France
*
Authors to whom correspondence should be addressed.
Appl. Sci. 2025, 15(14), 7692; https://doi.org/10.3390/app15147692
Submission received: 19 June 2025 / Revised: 5 July 2025 / Accepted: 7 July 2025 / Published: 9 July 2025
(This article belongs to the Section Mechanical Engineering)

Abstract

Featured Application

This work demonstrates modular automation using Autodesk Inventor API and VBA for component-based manufacturing, such as turbocharger reconditioning; automates CAD tasks including file creation, drawing, archiving, and cost estimation with metadata-rich Excel and Word outputs; and cuts documentation time by up to 90%, enhances consistency, and offers scalable, AI-integrable solutions for SMEs.

Abstract

Increasing mechanical design complexity and volume, particularly in component-based manufacturing, require scalable, traceable, and efficient design processes. In this research, a modular in-house automation platform using Autodesk Inventor’s Application Programming Interface (API) and Visual Basic for Applications (VBA) is developed to automate recurrent tasks such as CAD file generation, drawing production, structured archiving, and cost estimation. The proposed framework was implemented and tested on three real-world case studies in a turbocharger reconditioning unit with varying degrees of automation. Findings indicate remarkable time savings of up to 90% in certain documentation tasks with improved consistency, traceability, and reduced manual intervention. Moreover, the system also facilitated automatic generation of metadata-rich Excel and Word documents, allowing centralized documentation and access to data. In comparison with commercial automation software, the solution is flexible, cost-effective, and responsive to project changes and thus suitable for small and medium enterprises. Though automation reduced workload and rendered the system more reliable, some limitations remain, especially in fully removing engineering judgment, especially in complex design scenarios. Overall, this study investigates how API-based automation can significantly increase productivity and data integrity in CAD-intensive environments and explores future integration opportunities using AI and other CAD software.

1. Introduction

Automatically repeating parameter-based tasks in models is a valuable asset in modern manufacturing and mechanical design environments [1,2]. Increasing product complexity with proportionate increases in design diversity, in turn, increases the need for scalability, traceability, and modularity in automation tools [3]. Traditional CAD processes, specifically in environments that simulate assemblies/part families, typically rely on manual duplicate and edit, increasing the risk for error and inefficiency [4]. This work proposes a systematic and modularity-based design automation approach implemented in VBA in CAD environments for streamlining repetitive tasks in design, imposing naming conventions and archive standards, and maintaining traceability in iterations.
In this context, internal combustion engines and turbochargers are critical components with various applications in industrial and manufacturing-related sectors, providing enhanced reliability and enhanced performance for industrial applications. Diesel engines especially offer durability and combustion efficiency, while turbochargers improve engine performance by increasing power density and efficiency, resulting in higher power output and reduced emissions [5]. Mostly composed of cast iron, turbochargers account for 20% of sales in this industry and are a major source of greenhouse gas emissions, making them a prime target for reducing emissions [6]. During the machining process, the crucial factor for manufacturing components is the precision of cutting tools meeting tolerance demands with energy-assisted subtracting technologies for avoiding efficiency reduction and surface integrity deterioration [7].
Information comprised of a set of data is processed, analyzed, and organized in such a way that it is complete and solid [8]. Currently, designers are forced to implement effective information organization techniques to be responsive and efficient, as the highly competitive, dynamic, and strongly regulated industrial sector faces a growing number of challenges. For industrial users in a wide range of sectors, including engineering, one challenge is to gain total control over processes through real-time management. For example, the workflow ranges from raw material purchasing to transformation via production, equipment, logistics, traceability, and distribution until it reaches the final consumer. According to questionnaires sent out to engineers, 20–30% of the time spent on information-based tasks is devoted to researching specific information and data [9]. Furthermore, data organization is considered of paramount importance for a product’s traceability. The word “traceability”, derived from the word “trace”, refers to the ability to “track” and “trace” the history, location, and lifecycle of a product by utilizing data stored. To achieve this, data should be inseparable from a product and marked by a unique number. In addition, for the acquisition and organization of engineering data, the repeatability factor must be taken into consideration. Acceptable information retrieval times can be assessed not only when human error is eliminated, but also when the data storage process is carried out automatically.
CAD (computer-aided design) API, a set of programming interfaces that allows developers to interact with and extend the functionality of CAD software, enabling the automation of design tasks, customization of workflows, and integration with external systems, may be utilized across a wide range of industries and types of companies where automation and customization are significant factors for corporate development. Beyond engineering, some of them include manufacturing, construction, product design and consumer goods, renewable energy, supply chain, as well as research and academia for performing experimental design and analysis.
The objectives of this study are as follows: (a) improving the optimization of the design process using the example of engines’ parts and turbochargers; (b) guaranteeing the traceability of the documentation of each specific product; and (c) automating repetitive tasks for minimizing human error.
In view of all the elements described above, the aim of this paper is to propose and implement a fully modular optimization approach to streamline design workflows. The specific methodology is applied to mechanical engineering for the documentation of a newly designed product. To this end, our study will be based on the Application Programming Interface (API) of Autodesk Inventor (San Francisco, CA, USA), a computer-aided design (CAD) tool widely used and recognized in the world of mechanical engineering. Nevertheless, due to the wide area of CAD API’s implementation, the methodology may be generalized and be applicable to other sectors.
The present work aligns with the context of knowledge-based engineering (KBE), which represents a technology at the intersection of many fundamental disciplines, including computer programming, CAD, and artificial intelligence (AI) [10,11]. To the authors’ knowledge, the research gap that has been identified is the fact that there are no published literature works on the direct link between design applications and technical information. Therefore, the key objective is to build a multidisciplinary approach to information storage, including not only formal but also informal ones [12]. In the end, in order to meet the aforementioned requirements dictated in automated processes, a script, created using Visual Basic for Applications (VBA), was developed and implemented using Autodesk Inventor API (V2022). This automated process interacts directly with the user, resolving human errors and archiving design data more efficiently.
Based on the challenges outlined above, this study addresses the following three key research questions: (RQ1) To what extent can a company’s design process be optimized using Autodesk Inventor’s API? (RQ2) Can documentation tasks be automated to both eliminate human error and ensure traceability? (RQ3) How many aspects of this process can be automated while accounting for practical limitations? The proposed methodology leverages the modular structure of CAD APIs in conjunction with a design intent-oriented approach, implemented through a Visual Basic for Applications (VBA) script in Autodesk Inventor. A practical case study from an industrial design workshop demonstrates the methodology’s application, focusing on repetitive design and documentation tasks. The motivation stems from widespread inefficiencies in file organization and data traceability, which often lead to delays and inconsistencies in documentation. By identifying and automating the most repetitive and error-prone tasks, this work aims to reduce time-to-market, enhance productivity, and minimize operational risk. The study’s main contribution lies in its practical deployment under real working conditions, ensuring that the automation solution is not only technically sound but also aligned with actual industrial needs. Finally, the potential for generalization to other CAD systems is discussed, highlighting the broader implications for CAD-based automation in engineering workflows.
The remainder of this article is structured as follows: Section 2 (Related Work and Context) outlines relevant studies on design automation, optimization, and the use of CAD APIs. Section 3 (Methodology and System Architecture) describes the proposed automation framework and its modular implementation using Autodesk Inventor’s API. Section 4 (Case Studies) presents industrial applications of methodology in an industrial setting, highlighting recurring design challenges and automation outcomes. Section 5 (Results and Discussion) analyzes the performance improvements and practical benefits of the proposed approach. Finally, Section 6 (Conclusions and Future Work) summarizes the findings, answers the research questions, and discusses the broader potential of CAD-based automation across other engineering environments.

2. Related Work and Context

2.1. Historical Evolution of Automation

During the first Industrial Revolution, in the early 19th century [13], innovations like the steam engine and the greater transition from manual labor to mechanized production were immense. The origin of the term “automation”, credited to D.S. Harder, then Director of Engineering at Ford Motor Company [14], was gradually adopted in the context of manufacturing that was vastly modernized. Automation, the application of machines to tasks once performed by human beings or, increasingly, to tasks that would otherwise be impossible. These machines are concerned with performing a process by means of programmed commands combined with automatic feedback control to ensure proper execution of the instructions. Later on, in the mid-20th century, during the 1960s, CAD and computer-aided manufacturing (CAM) systems were introduced, enabling engineers to design and translate their designs directly into automated manufacturing instructions [15], followed by the integration of programmable logic controllers (PLCs), enabling real-time control of machines and production lines [16]. The rise of robotics and flexible manufacturing systems (FMSs) in the 1980s and 1990s broadened the scope of automation from repetitive tasks to more complex, adaptive processes [17]. As an example, in [18], the authors describe the transition to Industry 4.0, where the synergy of physical and digital systems creates “smart factories” able to actively adapt to production needs [19], complemented with technologies like cyber–physical systems, the Internet of Things (IoT), and artificial intelligence (AI), which includes machine learning (ML) and deep learning (DL).
The introduction of Industry Revolution 5.0 emphasizes human–machine collaboration, sustainability, and value creation beyond efficiency and automation [20]. Researchers in [21] investigated the technologies, the challenges, and the opportunities related to this transition, revealing a growing interest in Industry 5.0, a strong link between them, as well as the creation of new business models requiring personnel with new advanced technological skills [22].

2.2. Automation Systems and CAD API Integration

Automating a task or system, as shown in Figure 1, involves the depicted steps. By following these steps, a structured approach to integrating automation into engineering processes becomes possible, ensuring both an effective and efficient transition from manual to automated workflows.
Knowledge-based engineering (KBE) refers to the integration of knowledge management into the design and manufacturing process. This enables engineering expertise and data to be reused to automate more complex tasks. Thus, KBE represents a powerful design approach that uses explicitly represented knowledge to automatically generate product variants [23,24]. In [25], the authors consider that KBE is capable of drastically decreasing the time devoted to repetitive, labor-intensive tasks by automating the processes that traditionally involve manual intervention. According to [10], KBE not only automates recurring tasks but also improves decision-making by drawing on past experiences and design rules. This helps to reduce iteration cycles and accelerate adaptation to new requirements. The authors of [9] support this view by stating that shortening is of paramount importance in modern engineering, as it is imperative to be able to respond quickly to dynamic market demands. Moreover, as the authors of [10] point out, the automated retrieval and application of previous design data enables KBE to minimize redundant tasks in alignment with Kugler’s assertion, as published in [25]. The overall result is a leaner, more efficient workflow, where time and resources are optimized, thus meeting strict project deadlines and improving the overall quality of final products, allowing engineers to become more creative and innovative [26].
Product design and engineering design are closely linked disciplines [27], where the former defines user needs and vision, while the latter connects creativity with technical execution [28]. Advances in manufacturing increasingly rely on the effective reuse of engineering knowledge [29], data science integration, and flexible, modular automation systems—such as microservice-based industrial control architectures—to reduce information loss and enhance design efficiency [30].
In the current study, an API (Application Programming Interface), which is the basis of a modern CAD system, will be utilized [31]. Application Programming Interfaces (APIs) serve as intermediaries between software systems, facilitating seamless communication and interoperability among them [32], automating repetitive tasks in CAD systems, and reducing the need for manual intervention [33]. This makes APIs an essential tool for automating a wide range of engineering tasks, from routine operations to more complex processes such as parametric modeling and design validation. In [34], the authors point out that these platforms guarantee greater interoperability. APIs can thus be exploited to extend the capabilities of CAD systems for better integration with other tools and data sources. The transition to cloud-based solutions facilitates enhanced computational performance, improved collaborative capabilities, and increased flexibility in design environments, thereby better addressing the evolving demands of diverse industrial sectors [35].
Despite the considerable automation potential offered by Application Programming Interfaces (APIs) in CAD systems, their effective implementation often entails certain challenges, such as the requirement for programming proficiency and ongoing system maintenance. Nevertheless, those limitations are outweighed by the substantial advantages of API-driven automation, particularly in reducing repetitive manual input and enabling engineers to focus on higher-level design tasks. Various commercial CAD platforms provide API support to facilitate such automation. For instance, CATIA V5 [36], developed by Dassault Systems, incorporates tools like PowerCopy, UserFeature, and macros to automate modeling through generic inputs, while SolidWorks utilizes both API and VBA functionalities for similar purposes [37]. Autodesk Inventor represents another prominent example, where its dedicated API enables the automation of routine procedures through streamlined commands, thereby reducing the cognitive and operational load on engineers [38,39]. Beyond traditional automation, contemporary CAD systems are increasingly integrating artificial intelligence (AI), including machine learning (ML) and deep learning (DL), to further enhance adaptability and intelligence in design processes. Recent studies have introduced DL-based CAD/CAE frameworks capable of autonomously generating and analyzing 3D models during the conceptual design phase [40]. These systems employ advanced techniques such as transfer learning, dimensionality reduction, and generative design, allowing real-time optimization and autonomous decision-making [41]. The synergy between conventional API-based automation and AI-driven methodologies signifies a transformative evolution in CAD technologies, with future research expected to focus on developing robust and versatile knowledge models to support a broader range of design applications [42].

3. Methodology and System Architecture

As part of this research, a structured methodology was developed and implemented with the objective of addressing inefficiencies and uncertainties in the technical documentation process through the use of the Autodesk Inventor API. The primary aim was to automate key aspects of the design and documentation workflow to improve operational efficiency, reduce manual workload, and minimize the likelihood of human error. The methodology was applied and evaluated within the context of a practical case study, drawing data from an actual manufacturing workshop. Initial analysis focused on identifying recurring bottlenecks and repetitive tasks—particularly those related to CAD file creation, documentation, and information management—that were prone to error and consumed substantial engineering time. Based on the frequency of these tasks, their criticality, and their potential for potential automation, specific processes were selected, including part file generation, folder structuring, manufacturing drawing creation, and centralized data archiving.
Following problem identification and process selection, automation development was carried out using the Autodesk Inventor API, employing a modular and scalable code structure written in VBA. A user-centric interface was designed through interactive forms to facilitate seamless data input and ensure completeness and consistency of user-provided information. The implementation adopted an iterative development model, utilizing turbocharger parts—chosen for their complexity and documentation demands—as test cases to improve and validate the approach. Early prototypes were compiled in the workshop environment, and iterative feedback was used to enhance the system’s robustness and functionality. As development progressed, advanced automation features, such as the automatic generation of manufacturing drawings, were incorporated. The final version of the code was deployed in the live production setting, offering a fully integrated, stable, and user-friendly solution within the CAD environment. The result was a significant cut-off in documentation time and an improvement in accuracy, aligning with the research goals of enhancing productivity and traceability in engineering workflows.
In this context, three main combined methodologies are proposed: reverse engineering, manufacturing, and quality control, following the specified order depicted in Figure 2. The term ‘final product’ encompasses not only tangible items, such as a fully manufactured part, but also data-driven outputs, such as a manufacturing drawing from reverse engineering or a quality control inspection report.
In real-world workshop settings, engineers are frequently confronted with a high volume of quotation requests, each requiring prompt and accurate assessment. To manage each case effectively, engineers must address several fundamental questions: Has the customer provided a demonstrator of the part to be manufactured? Is a metrological inspection sufficient for the supplied item? Should reverse engineering be performed, or are manufacturing documents already available? Answering these questions necessitates a precise and comprehensive data acquisition process. The requirement for traceability and thorough documentation remains constant, whether dealing with a small component for basic inspection or a complex assembly for large-scale production. A CAD model inherently encapsulates a significant volume of information about a part or assembly, serving as the foundation for generating manufacturing drawings and bills of materials (BOMs), which subsequently initiate a series of downstream engineering procedures. The design engineer must either create or retrieve the appropriate CAD file, and if it does not exist, the prerequisite information must first be collected and securely stored. Once the design is completed, it becomes essential to organize and archive these data in a manner that ensures accessibility and traceability across teams. To streamline this process, the current approach leverages Autodesk Inventor’s API to automate the generation of 3D models, enabling rapid configuration of customizable designs and minimizing the downside need of repetitive documentation tasks [43,44]. An overview of the user interaction with the system and the primary input parameters handled by the automation code is illustrated in Figure 3.

3.1. Software Environment

This study was conducted within the operational context of a specialized industrial company engaged in the maintenance and reconditioning of turbochargers, offering services that include health checks, intermediate and major overhauls, precision repairs, and the remanufacturing of critical components. Given the sector’s strong emphasis on operational efficiency and strict adherence to production schedules, the need for reliable, scalable, and time-saving design processes is paramount. The software environment selected for this research reflects the aforementioned practical demands. Autodesk Inventor was chosen as the main CAD platform due to its widespread use in this sector and its accessible API, which supports advanced automation through VBA scripting. The system was implemented and tested under real working conditions, addressing practical challenges in design data handling and part documentation. The customization options and modularity of the environment were tailored to fit the specific requirements of the turbocharger industry, ensuring relevance, applicability, and adaptability of the developed automation framework.

3.2. Automation Workflow Design

The automation framework developed in this work was designed to streamline repetitive tasks commonly encountered in mechanical engineering design and documentation workflows [45]. Utilizing the Autodesk Inventor API, a quantitative and iterative approach was employed to implement a modular and scalable system capable of minimizing manual interventions and improving data traceability. The workflow was compiled using custom scripts developed in Visual Basic for Applications (VBA), enabling the automation of core design operations such as part file creation, folder generation, drawing documentation, and metadata management.
The core of the design focused on user-guided interactions through input forms, ensuring that essential information is collected consistently and accurately before model generation. This allowed for the seamless transition from raw input to structured output, reducing the risk of error and enforcing standardized documentation procedures. The automation logic was developed to be both hierarchical and reusable, facilitating the deployment of the system across a variety of design scenarios.
Three representative case studies were used to inform and validate the automation process, selected for their complexity, frequency, and the degree of task repetition involved. These cases, selected from daily operations within the collaborating industrial company, served both as testbeds for iterative code development and, at the same time, as validation scenarios evaluating the robustness and applicability of the proposed solution. The integration of this workflow within Autodesk Inventor not only enabled rapid and repeatable model creation but also ensured alignment with actual engineering demands.
For clarity and readability, detailed implementation aspects of the automation system have been relocated to Appendix A. This includes the structure and logic of the VBA code, the design of user input forms, the directory and file-naming conventions, and the workflow for generating CAD files and manufacturing drawings. Additionally, screenshots, interface examples, and a breakdown of modular subroutines are provided to support reproducibility and facilitate potential adaptation to other engineering contexts.

4. Case Studies

To evaluate the practical effectiveness of the proposed automation workflow, three representative case studies were selected from the daily operations of a mechanical engineering company specializing in turbocharger servicing and reconditioning. These cases were chosen based on their frequency, complexity, and relevance to repetitive design and documentation tasks. Each case highlights a distinct engineering scenario in which the implemented automation system was applied to streamline workflow processes, reduce manual effort, and ensure traceability. For each case, the presentation follows a structured format, outlining the specific design objective, the automated workflow applied using Autodesk Inventor’s API, and the outcomes observed in terms of time savings, consistency, and error reduction. Detailed code structures, interface laments, and procedural walkthroughs related to these cases are provided in Appendix A for reference and reproducibility. Figure 4 depicts the content of the three cases, which will be further elaborated.

4.1. Case Study 1: Automated Folder and Archiving Structure for Design Documentation

  • Goal
The objective in the first case study was to make data archiving related to reverse engineering tasks simpler by automating common folder hierarchies and index files. This is a mandatory step toward attaining traceability, consistency, and proper project-linked documentation organization, particularly for components such as those in this case in a turbocharger.
  • Process
Using the user interface designed for this case (illustrated in Figure 3), engineers begin by entering basic part-related information into a form. Upon clicking the “Next” button, the system automatically generates a predefined folder hierarchy tailored to the selected project type. This includes directories for part analysis, scan data, and reverse engineering outputs. A notification confirms the folder creation path, while additional prompts inform the user of archiving options. To support accessibility and future data analysis, an Excel index file is generated (Figure 5), which contains hyperlinks to all relevant subdirectories and files. The automation logic ensures uniformity in folder naming and structure, eliminating variation between users and minimizing manual input errors. The specific directory naming structure and file system logic are detailed in Appendix A.5.
  • Result
The automation of folder generation and data archiving significantly improved documentation efficiency by removing the need for manual folder setup. It ensured that all project data followed a consistent structure, enhancing file retrieval and version control. The use of an automatically generated Excel spreadsheet as a centralized index allowed users to manage documentation through a single interface, with embedded hyperlinks enabling rapid navigation to any stored file. Apart from structural organization, the Excel index also offers potential as a statistical dashboard, supporting future data-driven evaluations of part characteristics or project metrics.

4.2. Case Study 2: Automated Drawing Generation from CAD Models

  • Goal
The objective for Case Study 2 was to extend automation processes with the generation of completely annotated mechanical drawings from part files in CAD. Integrating drawing generation into the same automated chain that generates folder hierarchies and metadata, the objective was to save time in manual drafting and ensure that drawing output is within pre-specified standards.
  • Process
Building on the folder-generation routine of Case 1, the engineer first completes the initialization form (Figure 3) and selects the CAD STEP option. This triggers the API script to open the existing .ipt part file and automatically invoke the drawing environment. The routine generates a new .idw (or .dwg) drawing file in the project’s “Engineering Drawings” folder, populating three standard views—left, top, and isometric—and inserting the title block information captured in the form. Basic dimensions are added to the primary view according to a template, and prompts notify the user of the drawing’s save location.
  • Result
The automated drawing procedure reduced the time required to create and annotate a part drawing from over an hour to under five minutes while guaranteeing consistent formatting and eliminating transcription errors. Figure 6 illustrates the resulting project folder containing both the .ipt model and .idw drawing files. Figure 7 presents a representative output, showing the three views, populated title block, and template-driven dimensions. By integrating drawing generation into the broader automation framework, this case demonstrated both a substantial productivity gain and a robust mechanism for maintaining drawing quality and traceability.

4.3. Case Study 3: Full Workflow Automation with Cost Estimation and Reporting

  • Goal
The third case study demonstrates the widespread potential of the automation system created by integrating higher-level features such as automated drawing generation, fiscal data processing, structured archiving, and report generation. The ultimate objective was to emulate an actual current-day workflow of an engineering environment in which technical deliverables such as CAD files and drawings, along with cost estimates and part documentation, are all automated, thus providing an integrated as well as component-level approach to reducing design time, human error, and inconsistency.
  • Process
Building upon the procedures in Cases 1 and 2, Case 3 starts with the engineer filling in the required metadata and activating the “Financial Data” and “Reverse Engineering” tabs through the input interface. These options prompt the user to insert key cost-related variables like material price, process times, and consumable costs (see Table 1. Upon submission, the system generates a CAD part file (.ipt) and its relevant drawing file (.idw), as shown in Figure 8, that includes multiple standard views and an autocompleted title block.
The system then proceeds to automatically generate a structured directory of folders for engineering drawings, manufacturing data, quality control files, and reverse engineering outputs. An MS Word-based report file is also created (Figure 9), containing a summary of user-provided data, a snapshot of the part drawing, a footprint box outlining the raw part dimensions, and the total calculated manufacturing cost. The footprint box supports the selection of the appropriate raw material dimensions, eliminating manual measurements. This reporting functionality enhances documentation accuracy and promotes communication among design, costing, and production teams.
All directory paths and coding logic used in this case are documented in Appendix A.7, while Figure 10 illustrates the automatically generated report with embedded drawing and financial summary. Appendix A.7 outlines the key variables used in the financial analysis of the part production process. These include material costs, time required for reverse engineering and machine setup, and the cost of consumables. Each variable contributes to the accurate calculation of total production costs. Upon saving, the system automatically processes these data to support decision-making.
  • Result
Implementation of Case 3 confirmed the modularity and scalability of the implemented system. The automation substituted folder development, drawing preparation, and preliminary cost estimates, reducing switching between tasks. The system processed finance data safely using embedded calculators with precalculated calculations (e.g., hourly rates and material markups) and could present an overall cost summary on request. Modularity in the code supports dynamic value updating and possible expansion of the costing model in the future. Word reporting offers accessibility, while graphical integration enhances interpretability. This case demonstrates the ability of the system to encapsulate complicated tasks of an engineer through integrating the processes of design, costing, and documentation within an automated process.
Together, the three case studies in this chapter collectively present the versatility, scalability, and practical applicability of the suggested automation system to varying levels of design complexity. Spanning from basic folder generation and metadata management to drawing automation and integration with cost estimation, the system proved it could solve common problems in actual engineering environments. Each case demonstrated an aspect of the system’s capability that justified the system’s assertion of reducing manual effort, maintaining standardized documentation, and enhancing traceability of the information. By matching the level of automation with the nature of the work at hand, the approach strikes an equilibrium between flexibility and control that supports rapid deployment as well as extended extensibility.

5. Results and Discussion

This section presents the main outcomes of the automation framework developed using Autodesk Inventor’s API, focusing on its impact on design efficiency, error reduction, and scalability in mechanical engineering workflows. By comparing automated processes with established manual methods across three representative case studies, the analysis exhibits tangible improvements in productivity and consistency, particularly in routine documentation and data archiving tasks.
In Case 1, automation was applied to streamline folder creation and metadata organization through an MS Excel-based index system. While seemingly simple, these tasks consume considerable time in manual workflows and are prone to inconsistencies. As shown in Figure 11, the manual documentation process required approximately 2.9 h for an annual batch of 50 parts. In contrast, the automated process reduced this to just 8 min (Figure 12), highlighting an over 90% reduction in task time. The Excel file served as a centralized, hyperlink-driven archive, improving file accessibility and reducing the likelihood of misplacement or duplication.
Case 2 introduced drawing generation from CAD part files, expanding the automation framework to include visual and dimensional documentation. This feature eliminated the need for manual drawing setup, title block editing, and view placement. When scaled across multiple parts, the time savings and error reduction became more pronounced, especially in enforcing standardized drawing formats. Figure 13 illustrates cumulative time savings as production volumes increase, clearly indicating the scalability of the approach and its growing benefits in high-throughput environments.
Case 3 showcased the full integration of automation features, combining drawing generation, structured archiving, report compilation, and cost estimation within a single workflow. This advanced use case demonstrated how modular code could address both technical and financial aspects of the design process. The automatically generated Word report included part metadata, dimensional previews, and calculated cost estimates, providing a comprehensive reference for design, production, and managerial teams. The modularity of the codebase allowed real-time updates to pricing parameters and logic, ensuring adaptability to future changes in cost structures or part specifications.
Overall, the results provide strong evidence of the system’s ability to reduce design lead time, minimize documentation errors, and standardize file management. The visualizations in Figure 10, Figure 11 and Figure 12 confirm that automation gains compound with production scale, making the framework particularly advantageous in industrial contexts requiring frequent design iterations or part customization.
A key contribution of this work lies in its non-commercial, in-house development model. Unlike proprietary automation platforms with rigid workflows and high subscription costs, the proposed system offers full code transparency and modification capabilities. Engineers with basic programming knowledge can adapt the tool to evolving project needs, enabling organizations to avoid vendor lock-in and reduce long-term maintenance expenses. This agility allows teams to extend functionality, integrate additional modules, or respond to operational feedback more quickly than would be feasible with commercial systems.
Moreover, the cost-effectiveness of the proposed approach is significant. Many commercial automation solutions are financially inaccessible to small companies or startups. In contrast, the use of VBA within Autodesk Inventor, a platform already present in many engineering firms, enables the creation of powerful automation tools without incurring additional licensing costs. The system’s self-sufficiency fosters internal expertise development, reducing dependence on external software providers and promoting continuous process improvement.
In summary, this study demonstrates that a modular, customizable automation framework can deliver measurable efficiency gains and operational flexibility in mechanical design environments. The solution is particularly well suited to organizations seeking scalable, cost-efficient alternatives to commercial automation packages, including those with limited technical or financial resources. The following chapter outlines the broader conclusions of this work and proposes directions for further development and optimization.
To provide a concise overview of the performance gains observed across the three case studies, Table 2 presents a comparative summary of the key outcomes. This table highlights the specific automation objectives addressed in each case, the primary features implemented, and the resulting benefits in terms of time savings, error reduction, and scalability.

6. Conclusions and Future Work

This study set out to investigate the potential of CAD-based automation to improve efficiency, traceability, and error minimization in mechanical design documentation workflows. Through the development and deployment of a modular automation framework using Autodesk Inventor’s API, the research addressed three primary questions concerning optimization (RQ1), traceability and error reduction (RQ2), and the extent and limitations of automation in practice (RQ3). The results from three structured case studies clearly demonstrate that automating repetitive engineering tasks significantly reduces documentation time and enhances consistency, particularly in high-volume or high-variation production environments.
Regarding RQ1, the framework proved highly effective in optimizing core design processes, especially in tasks such as CAD file creation, drawing generation, and directory structuring. Time savings were consistently demonstrated, with automated processes requiring a fraction of the time needed for their manual equivalents. In response to RQ2, the methodology ensured improved traceability through standardized documentation and archiving routines. The integration of metadata into both CAD models and linked Excel/Word outputs significantly lowered the risk of incomplete or inconsistent records, supporting regulatory compliance and downstream process reliability. For RQ3, while the automation system achieved substantial coverage of routine operations, certain limitations persist. Complex design tasks such as advanced geometric modeling or engineering judgment in drawing comprehension still require human intervention, stressing the ongoing importance of human oversight in design engineering.
While the proposed framework delivered substantial time and error reduction benefits, its current implementation is limited to the Autodesk Inventor platform and relies on VBA scripting, which may constrain portability and extensibility. Additionally, the impact of automation on reducing human error could not be quantitatively measured due to the subjective nature of manual processes. These limitations dictate the need for broader validation and structured error analysis in future work.
Regarding broader implications, this study contributes to the body of knowledge pertaining to sustainable engineering practices. By eliminating unnecessary manual labor and reducing errors, the automation process results in greater resource effectiveness combined with a reduced need for costly rework. These advantages not only enhance operational excellence but also aid in the attainment of sustainability goals in terms of minimizing material waste and energy consumption.
For this purpose, several future research directions are proposed. First, extension of the framework to accommodate other CAD systems or integrated Product Lifecycle Management (PLM) systems would enhance its value considerably. Second, envisioning the integration of machine learning (ML) or artificial intelligence (AI) technologies into the automation logic could provide adaptive capabilities, i.e., proactive prediction of errors, smart parameter recommendation, or process adaptation automatically based on usage feedback. Machine learning (ML) has become a valuable asset in materials science due to its ability to capture nonlinear relationships and identify patterns within complex, high-dimensional data [46]. The rational design of photoanode materials is pivotal for advancing photoelectrochemical (PEC) water splitting toward sustainable hydrogen production. This review highlights recent progress in the machine learning (ML)-assisted development of nanostructured metal oxide photoanodes, focusing on bridging materials discovery and device-level performance optimization. We first delineate the fundamental physicochemical criteria for efficient photoanodes, including suitable band alignment, visible-light absorption, charge carrier mobility, and electrochemical stability. Conventional strategies such as nanostructuring, elemental doping, and surface/interface engineering are critically evaluated. We then discuss the integration of ML techniques—ranging from high-throughput density functional theory (DFT)-based screening to experimental data-driven modeling—for accelerating the identification of promising oxides (e.g., BiVO4, Fe2O3, and WO3) and optimizing key parameters such as dopant selection, morphology, and catalyst interfaces. Particular attention is given to surrogate modeling, Bayesian optimization, convolutional neural networks, and explainable AI approaches that enable closed-loop synthesis–experiment–ML frameworks. ML-assisted performance prediction and tandem device design are also addressed. Finally, current challenges in data standardization, model generalizability, and experimental validation are outlined, and future perspectives are proposed for integrating ML with automated platforms and physics-informed modeling to facilitate scalable PEC material development for clean energy applications. While cutting-edge AI and VR tools offer transformative potential in advanced sectors like aerospace or automotive design, cost and complexity often limit their applicability in traditional mechanical workshops. Thus, the approach advocated in this study favors accessible, scalable, and internally manageable automation solutions—especially suited for small-to-medium-sized enterprises seeking cost-effective digital transformation.
Furthermore, security and IT infrastructure would need to be addressed for long-term system development, particularly as automated workflows are handling more sensitive design information and collaborative access. Version control procedures would prevent inadvertent overwrites and make it easier to track design revisions. In addition, the integration of secure data storage, encryption, and role-based user access would further strengthen the architecture for networked or multi-user setups. These features become increasingly critical as the system is scaled up or integrated with more comprehensive enterprise systems such as PLM or cloud-based CAD systems.
Lastly, future work could explore the use of simulation tools or open-source platforms (e.g., FreeCAD (San Francisco, CA, USA), Autodesk Generative Design (San Francisco, CA, USA)) for constraint-driven optimization. However, the methodology developed here remains intentionally grounded in practical, low-barrier technologies, making it particularly relevant for industries where customization, traceability, and process control are key priorities, yet advanced digital infrastructure may be limited.

Supplementary Materials

The following supporting information can be downloaded at: https://www.mdpi.com/article/10.3390/app15147692/s1.

Author Contributions

Conceptualization, K.S. and C.S.; methodology, K.S. and C.S.; software, K.S.; validation, K.S. and Z.K.; formal analysis, K.S., A.K. and Z.K.; investigation, Z.K. and S.J.; resources, K.S.; data curation, K.S.; writing—original draft preparation, K.S., A.K. and Z.K.; writing—review and editing, Z.K., A.K. and S.J.; visualization, Z.K.; supervision, K.S., Z.K., T.G. and C.S.; project administration, Z.K., C.S. and T.G.; funding acquisition, Z.K. All authors have read and agreed to the published version of the manuscript.

Funding

This research received no external funding.

Data Availability Statement

The original contributions presented in this study are included in the article and Supplementary Materials.

Acknowledgments

The authors would like to express their sincere gratitude to. Paraskevi Zacharia (Department of Industrial Design and Production Engineering, University of West Attica, Greece) for her valuable guidance and insightful suggestions during the preparation of this manuscript. Her thoughtful input and support in structuring and organizing the paper have been truly appreciated.

Conflicts of Interest

The authors declare no conflicts of interest.

Abbreviations

The following abbreviations are used in this manuscript:
AIartificial intelligence
APIApplication Programing Interface
BOMBill of Materials
CADcomputer-aided design
CAMcomputer-aided manufacturing
CATIAComputer-Aided Three-Dimensional Interactive Application
CMMcoordinate measuring machine
DLdeep learning
FMSsflexible manufacturing systems
IGESInitial Graphics Exchange Specification
ISOInternational Organization for Standardization
IoTInternet of Things
KBEknowledge-based engineering
MLmachine learning
NCnumerically controlled
PDFportable document format
PLCprogrammable logic controller
PLMProduct Lifecycle Management
RQresearch question
VBAVisual Basic for Applications

Appendix A

Appendix A.1. Documentation Process

The use of VBA enables seamless integration with Microsoft (MS) Office applications such as Word and Excel to enable data exchange, automate report generation, and simplify the documentation process. This collaboration significantly improved workflow efficiency, particularly during the design and documentation stages, by reducing manual effort, minimizing errors, and ensuring consistency in data handling and reporting.
The methodology used is composed of the following two key procedures. Firstly, an in-depth task identification process was carried out to determine the repetitive and tedious operations in typical mechanical design workflows. Next, an in-depth exploration of Autodesk Inventor was carried out to gain a better understanding of the scope of its functionalities and how best to exploit them.

Appendix A.2. Methodology Steps

The methodological approach also involved several essential steps. First, a comprehensive analysis was carried out to identify repetitive and time-consuming tasks within standard mechanical design tasks. This was followed by an in-depth exploration of the Autodesk Inventor API to assess its capabilities and determine how its features could be effectively leveraged to address the identified tasks. These steps led to the development of tailored automation solutions aimed at optimizing design processes and improving overall efficiency.
Building on these insights, custom scripts were carefully designed and implemented to automate specific tasks. These included the automatic generation of part drawings directly from three-dimensional models and the consistent application of standardized dimensioning across similar components. This approach not only streamlined repetitive processes but also enhanced accuracy and uniformity in the design output, contributing to a more efficient and reliable workflow.
Once developed, these scripts were then integrated into the Autodesk Inventor software as add-on modules. This ensured easy access and use by end-users. To assess the functionality, efficiency, and reliability of the automated processes, extensive testing was carried out using a range of sampling plans. The iterative testing phase enabled us to identify and rectify any errors or bugs and fine-tune the scripts to achieve optimum performance.
An essential element of the method is performance evaluation, with the efficiency and effectiveness of automated processes being systematically compared with those of traditional manual methods. To achieve this, quantitative measures such as reduced design time were carefully recorded and analyzed.
As mentioned above, Autodesk Inventor and its API have become indispensable in the field of mechanical engineering. What has also justified the use of this CAD tool are its customization capabilities, which are widely extended for the development of tailor-made automation solutions. When it comes to repetitive tasks, their automation removes a bottleneck in engineering design processes, making a significant contribution to improving productivity, consistency, and accuracy in mechanical design and documentation practices.

Appendix A.3. Programming Tasks

The aim of this section is to explain the code developed for improving the efficiency of the documentation and the design procedure. Its flowchart is illustrated in Figure 3 and follows a logical progression of the queries to be asked during the design process. This minimizes human error while automating the procedure.

Appendix A.3.1. Main Input Parameters of the Developed Code

If the user already has a 3D CAD model, the next step is to run the macro directly from the “Tools” tab of the Autodesk Inventor environment, as shown in Figure 3. Once this step has been completed, the user will see the first prompt on his screen, comprising three main options and a checkbox in the bottom right-hand corner. One of the main assets of the Autodesk Inventor API is its ability to be modulated, as mentioned above. It should be noted that the choices we have made refer to a leading company in the marine turbocharger industry and that the options offered to the user are therefore adapted to these particular needs. However, the focus of this research is on the broad outlines of the program rather than the options themselves.
The first prompt contains two options—“TURBO” and “CUSTOMER”—as well as a “CANCEL” button. When a company is actively involved in the production and repair of turbocharger parts, specific requirements arise with regard to its documentation. In the face of repetitive tasks and standard design methods, the first button follows an approach that enables the designer to meet the specific documentation and traceability needs that will be detailed in the following sections. The “CUSTOMER” feature takes a more abstract approach to the design process, simply asking the user for enough information to perform general tasks. It is necessary to clarify that the “TURBO” option also refers to customer parts, while the “CUSTOMER” option was selected for the purpose of the study. For instance, a company specializing in pumps and impellers could have those two options with their respective paths. Finally, there is an optional financial analysis option that works with both of the aforementioned options.
Numerous variables need to be recorded in accordance with Table A1.
Table A1. Key variables in the financial analysis.
Table A1. Key variables in the financial analysis.
Financial Analysis FeaturesExplanation
Material price (EUR)Amount paid by the manufacturer to acquire the piece in stock needed to manufacture the part
Reverse engineering duration (hours)Time required by the engineer to complete reverse engineering tasks during the part design process (if applicable)
Setup duration (hours)Time required to calibrate and set up the machine to perform operations on the part. This variable is of great importance but is often overlooked when the setup time for the first part is considerably longer than for the rest of the production run. It is therefore essential to calculate this variable as part of the financial analysis
Consumables (EUR)Integration of consumables such as the tools required to complete tasks
When the end-user presses the “SAVE” button, a pop-up window shows that the financial data have been successfully saved, and the program performs the necessary calculations in the background.
Designers usually work on several parts at the same time, which means that once the user has selected the “TURBO” or “CUSTOMER” options, a prompt will ask again for the part to be examined. In this study, the part will be called “Project Part 1.ipt”, with the *ipt extension corresponding to the part designed from AutoCAD Inventor software (v2022).
If the user has chosen the “TURBO” option, they must select the turbocharger options. As shown in Table A2, ten text fields must be filled in by the user.
Table A2. Ten turbocharger options to be completed by the user.
Table A2. Ten turbocharger options to be completed by the user.
Turbocharger Data
Project IDProject identification number
EngineerEngineer in charge of the project
MakerTurbocharger manufacturer
TypeType of turbocharger
PartType of turbocharger part
SpecSpecification of the Turbocharger (if applicable)
Part NrPart number
OriginOrigin of the turbocharger part
ConditionStatus of the turbocharger parts: repaired and damaged
ScopeScope of the part
The information mentioned above will serve as an essential input for the code as we go on to analyze the program. Where certain information is not accessible to the user, it is possible to leave the text fields empty without concern. The project ID is the only required field, which will be used as the name for the folder containing all the data stored by the program.
A pop-up window notifies the user that a folder has been created in a particular directory. The folder name will be precisely that which the user has entered in the “Project identity” text box. The final step is to use the archive options form, which comprises four tabs: engineering drawings, manufacturing files, reverse engineering files, and quality control files. The following paragraph explains the logic of this form.
The designer should have a precise methodology and an order between the tasks to be accomplished when dealing with engineering parts. In line with this principle, the aim of this archiving system is to ensure that human error is eliminated and that all data are inserted into the appropriate folders and subfolders. When a box is selected, the code creates a folder within the main folder mentioned above. Each subfolder created is designed to store essential engineering information.
The first tab is called “Engineering Drawings”, and its sole purpose is to store final technical drawings in portable document format (PDF) so that they can be consulted by all departments.
The second tab contains the following six boxes for the production information:
-
“Suppliers”: This dialog box is used to generate a folder containing all the data collected by suppliers, whether invoices, prices, or e-mails.
-
“Machining Material”: This folder includes the material certificate or hardness test certificate for the material purchased for manufacturing.
-
“CAM”: This folder contains all the CAM files relating to manufacturing.
-
“Routing”: This folder is used to store all the routing sheets, helping to improve project repeatability.
-
“Photos”: This folder contains all the photos of the manufacturing process.
-
“General Project Remarks”: This file provides all the essential information needed to complete the project.
The stages in the reverse engineering process can be entered in a third tab comprising the following seven check boxes:
-
“Part Analysis”: This folder includes all the analysis data for the part. This covers spectrographic material analysis reports, hardness reports, and roughness test summary reports.
-
“Scan Point Cloud”: This folder provides the point cloud data captured by the 3D laser scanner.
-
“Reverse Eng. Software Files: This folder stores the reverse-engineered model, generally from a file taken from the 3D scanner (file with STL extension). A STEP file is created at the end of this process.
-
“Remarks”: This file must contain an automated report that will be created by the program and that will be discussed in more detail in the following parts of the study.
-
“CAD-STEP”: This folder stores the three-dimensional CAD model that the user has created and also contains a drawing that will be generated automatically by the program.
-
“CMM”: This folder includes the coordinate measuring machine (CMM) reports and models after the part has been inspected.
-
“Screenshot-Photos”: This folder will store images of all the reverse engineering procedures as well as screenshots of the software that was used. Keeping screenshots allows you to gain an overall idea of the project more quickly, without needing to access specific applications.
Finally, the “Quality Control” tab contains the International Organization for Standardization (ISO) certificates that are drawn up once the work has been completed, with the aim of guaranteeing certification of the processes and the end result of the project. A folder, called “Quality Control Files”, can also be created, which contains the quality control data for a production run (e.g., CMM inspection files, measurements, statistical analysis).

Appendix A.3.2. Main Output Parameters and Definition of the Three Cases

A set of VBA routines has been created to simplify the documentation and archiving process in Autodesk Inventor. These routines automate tasks such as financial analysis, file creation, and document production, significantly reducing human error and increasing production. As mentioned earlier, the routines communicate with the user using forms. In this section, we will show the output and end result of these forms.
In order to highlight the automation code and its functionality, we will show various situations where the user has chosen different inputs using forms. Each input will lead to a separate path depending on the desired result. By default, all paths will take into account the part selection and the turbocharger option in the part category selection prompt.
Table A3 summarizes the content of the three cases, which will be further elaborated.
Table A3. Turbocharger data: Cases #1, #2, and #3.
Table A3. Turbocharger data: Cases #1, #2, and #3.
Turbocharger Data Cases
Project IDCase #1Case #2Case #3
EngineerK.SofiasK.SofiasK.Sofias
MakerExample Maker 1Example Maker 2Example Maker 3
TypeExample Type 1Example Type 2Example Type 3
PartExample Part 1Example Part 2Example Part 3
Spec123451234512345
Part Nr202420242024
OriginN/AN/AN/A
ConditionUsedUsedUsed
ScopeMetrology InspectionMetrology InspectionMetrology Inspection

Appendix A.4. Limitations and Applicability

The system developed through this research offers significant potential for integration into a wide range of applications across various sectors, contingent upon the complexity of the tasks involved. Its modular design enables customization, meaning that it can be adapted to meet the specific needs of different industries, provided the appropriate data are available for each application.
One of the key strengths of this system is its flexibility, which allows it to be employed in various engineering fields, from mechanical design to manufacturing processes, as long as the necessary engineering methodologies and data are available. The code’s modular nature ensures that it can be extended or modified as required, making it adaptable to changing needs or advancements in technology. However, the effectiveness and applicability of the system are ultimately dependent on the skills and expertise of the programmer who adapts and configures the system for specific tasks or environments.
While the system is versatile, it is essential to note that its success is also influenced by the quality and accuracy of the input data and the specific engineering processes defined by the user. Thus, the limitations of the system are primarily determined by the boundaries set by the user and the programming implementation, as opposed to inherent constraints within the system itself.
If we were to identify an inherent limitation of the code, it would be that adding all the necessary dimensions automatically takes more programming time than manually inserting them into a drawing. In fact, the process of adding dimensions automatically is equivalent to inserting them manually in terms of time and effort. However, this limitation becomes less significant in scenarios where a company frequently handles variations of the same product. For example, a furniture manufacturer who produces the same bolts in different sizes or drawers in various lengths would benefit from automating the dimensioning process, as the time investment in programming would be offset by the efficiency gained across numerous variations. This highlights the system’s applicability for companies dealing with product variations, further extending its potential to a broader range of industries.

Appendix A.5. Case Study 1 Detailed Specific Directory Naming Structure and File System Logic

The data are added by the engineer as shown in Table A3. After clicking on the “Next” button, the user receives a message from the system indicating the path created after completing the process from the form.
The user is prompted when a file is created and has access to the various archiving options (i.e., part analysis, point cloud, and reverse engineering software files).
Once the user has clicked on the “Submit” button, two information messages are sent at the same time, providing further information on the process. A base folder has been created as follows for archiving data from Case #1:
C:\ExampleUser\Turbocharger Part\THESIS CASE 1
The subfolders are then automatically created from the procedure as follows:
C:\ExampleUser\Turbocharger Part\PROJECT CASE 1\REVERSE ENGINEERING FILES
Final sub folders created for Case 1
C:\Thesis\Turbocharger Part\PROJECT CASE 1\REVERSE ENGINEERING FILES\01 PART ANALYSIS
C:\Thesis\Turbocharger Part\PROJECT CASE 1\REVERSE ENGINEERING FILES\02 SCAN POINT CLOUD
C:\Thesis\Turbocharger Part\PROJECT CASE 1\REVERSE ENGINEERING FILES\03 REVERSE ENG. SOFTWARE FILES

Appendix A.6. Detailed Directory Structures and VBA Routines for Case Study 2

A base folder and subfolders (i.e., the final drawings, machining, quality control, and reverse engineering files) for archiving data and options (i.e., Part Analysis, Scan Point Cloud, Reverse Eng. Software files, and CAD STEP) in Case #2 are created as follows:
C:\ExampleUser\Turbocharger Part\PROJECT CASE 2
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 2\REVERSE ENGINEERING FILES
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 2\REVERSE ENGINEERING FILES\05 CAD STEP

Appendix A.7. Detailed Directory Paths and Coding Logic Used in Case Study 3

A base folder and subfolders (i.e., the final drawings, machining, quality control, and reverse engineering files) for archiving data in Case #3 are created as follows:
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 3
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 3\ENGINEERING DRAWINGS
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 3\ENGINEERING DRAWINGS\Engineering Drawings
C:\ ExampleUser\Turbocharger Part\PROJECT CASE 3\MANUFACTURING FILES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\MANUFACTURING FILES \01 SUPPLIERS
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\MANUFACTURING FILES \03 CAM
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\QUALITY CONTROL FILES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\QUALITY CONTROL FILES\01 ISO CERTIFICATES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\QUALITY CONTROL FILES\02 QUALITY CONTROL FILES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\01 PART ANALYSIS
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\02 SCAN POINT CLOUD
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\03 REVERSE ENG. SOFTWARE FILES
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\04 REMARKS
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\04 REMARKS
C:\ ExampleUser\Turbocharger Part\ PROJECT CASE 3\REVERSE ENGINEER-ING FILES\05 CAD STEP
The code (presented below) starts by validating and converting the data entered into the text fields (e.g., Finance1, Finance2, etc.) into numerical values using CDbl to ensure that the data entered is in the correct format for subsequent calculations. During this conversion process, if an error occurs, the error handler will prompt the user to enter valid digits, ensuring that only the correct data are processed.
Private Sub SavebuttonFinance_Click()
Dim materialPrice As Double
Dim reverseEngineeringTime As Double
Dim setUpTime As Double
Dim machiningTime As Double
Dim tools As Double
Dim totalCost As Double

Dim materialCost As Double
Dim reverseEngineeringCost As Double
Dim setUpCost As Double
Dim machiningCost As Double

‘ Validate and convert input data
On Error GoTo ErrorHandler
materialPrice = CDbl(Finance1.Text)
reverseEngineeringTime = CDbl(Finance2.Text)
setUpTime = CDbl(Finance3.Text)
machiningTime = CDbl(Finance4.Text)
tools = CDbl(Finance5.Text)

‘ Perform calculations
materialCost = materialPrice * 1.15
reverseEngineeringCost = reverseEngineeringTime * 60
setUpCost = setUpTime * 30
machiningCost = machiningTime * 30
totalCost = materialCost + reverseEngineeringCost + setUpCost + machiningCost + tools

‘ Update global variables
materialCostGlobal = materialCost
reverseEngineeringCostGlobal = reverseEngineeringCost
setUpCostGlobal = setUpCost
machiningCostGlobal = machiningCost
totalCostGlobal = totalCost

MsgBox “Financial data saved successfully!”, vbInformation
Unload Me
   Exit Sub

References

  1. Cimino, A.; Elbasheer, M.; Longo, F.; Mirabelli, G.; Solina, V.; Veltri, P. Automatic Simulation Models Generation in Industrial Systems: A Systematic Literature Review and Outlook towards Simulation Technology in the Industry 5.0. J. Manuf. Syst. 2025, 80, 859–882. [Google Scholar] [CrossRef]
  2. Automation in Model-Driven Engineering: A Look Back, and Ahead. Available online: https://arxiv.org/html/2405.18539v2 (accessed on 4 July 2025).
  3. Roy, M.-A.; Abdulnour, G. Integrating Modular Design Concepts for Enhanced Efficiency in Digital and Sustainable Manufacturing: A Literature Review. Appl. Sci. 2024, 14, 4539. [Google Scholar] [CrossRef]
  4. ElMaraghy, W.; ElMaraghy, H.; Tomiyama, T.; Monostori, L. Complexity in Engineering Design and Manufacturing. CIRP Ann. 2012, 61, 793–814. [Google Scholar] [CrossRef]
  5. Chen, S.; Ma, C.; Zhang, H.; Xu, C.; Lei, F.; Feng, T.; Cao, G.; Yang, H.; Wei, C. Engine Performance Improvements through Turbocharger Matching and Turbine Design. Energy Sci. Eng. 2022, 10, 3384–3396. [Google Scholar] [CrossRef]
  6. Kim, D.-Y.; Lee, J.-H.; Hwang, Y.-W.; Kim, Y.-H.; Kang, H.-Y. Life Cycle Greenhouse Gas Reduction Effects Induced by Turbocharger Multiple Remanufacturing in South Korea. Energies 2024, 17, 6248. [Google Scholar] [CrossRef]
  7. Zhao, B.; Wang, Y.; Peng, J.; Wang, X.; Ding, W.; Lei, X.; Wu, B.; Zhang, M.; Xu, J.; Zhang, L.; et al. Overcoming Challenges: Advancements in Cutting Techniques for High Strength-Toughness Alloys in Aero-Engines. Int. J. Extrem. Manuf. 2024, 6, 062012. [Google Scholar] [CrossRef]
  8. Storga, M.; Marjanovic, D.; Savsek, T. Reference Model for Traceability Records Implementation in Engineering Design Environment. In Proceedings of the 18th International Conference on Engineering Design, Copenhagen, Denmark, 15–18 August 2011. [Google Scholar]
  9. Court, A.; Ullman, D.; Culley, S. A Comparison Between the Provision of Information to Engineering Designers in the UK and the USA. Int. J. Inf. Manag. 1998, 18, 409–425. [Google Scholar] [CrossRef]
  10. Rocca, G.L. Knowledge Based Engineering: Between AI and CAD. Review of a Language Based Technology to Support Engineering Design. Adv. Eng. Inform. 2012, 26, 159–179. [Google Scholar] [CrossRef]
  11. Gao, R.X.; Krüger, J.; Merklein, M.; Möhring, H.-C.; Váncza, J. Artificial Intelligence in Manufacturing: State of the Art, Perspectives, and Future Directions. CIRP Ann. 2024, 73, 723–749. [Google Scholar] [CrossRef]
  12. Howard, T.J. Information Management for Creative Stimuli in Engineering Design. Ph.D. Thesis, University of Bath, Bath, UK, 2008. [Google Scholar]
  13. Groumpos, P.P. A Critical Historical and Scientific Overview of All Industrial Revolutions. IFAC Pap. 2021, 54, 464–471. [Google Scholar] [CrossRef]
  14. Hitomi, K. Automation—Its Concept and a Short History. Technovation 1994, 14, 121–128. [Google Scholar] [CrossRef]
  15. Shivegowda, M.D.; Boonyasopon, P.; Rangappa, S.M.; Siengchin, S. A Review on Computer-Aided Design and Manufacturing Processes in Design and Architecture. Arch. Comput. Methods Eng. 2022, 29, 3973–3980. [Google Scholar] [CrossRef]
  16. Walker, M.; Bissell, C.; Monk, J. The PLC: A Logical Development. Meas. Control 2010, 43, 280–284. [Google Scholar] [CrossRef]
  17. Javaid, M.; Haleem, A.; Singh, R.P.; Suman, R. Enabling Flexible Manufacturing System (FMS) through the Applications of Industry 4.0 Technologies. Internet Things Cyber-Phys. Syst. 2022, 2, 49–62. [Google Scholar] [CrossRef]
  18. Gorecky, D.; Schmitt, M.; Loskyll, M.; Zühlke, D. Human-Machine-Interaction in the Industry 4.0 Era. In Proceedings of the 2014 12th IEEE International Conference on Industrial Informatics (INDIN), Porto Alegre, Brazil, 27–30 July 2014; pp. 289–294. [Google Scholar]
  19. Soori, M.; Arezoo, B.; Dastres, R. Internet of Things for Smart Factories in Industry 4.0, a Review. Internet Things Cyber-Phys. Syst. 2023, 3, 192–204. [Google Scholar] [CrossRef]
  20. Mastrantonas, A.; Kokkas, P.; Chatzopoulos, A.; Papoutsidakis, M.; Stergiou, C.; Vairis, A.; Kanetaki, Z. Identifying the Effects of Industry 4.0 in the Pharmaceutical Sector: Achieving the Sustainable Development Goals. Discov. Sustain. 2024, 5, 460. [Google Scholar] [CrossRef]
  21. Piccarozzi, M.; Silvestri, L.; Silvestri, C.; Ruggieri, A. Roadmap to Industry 5.0: Enabling Technologies, Challenges, and Opportunities towards a Holistic Definition in Management Studies. Technol. Forecast. Soc. Change 2024, 205, 123467. [Google Scholar] [CrossRef]
  22. Sindhwani, R.; Afridi, S.; Kumar, A.; Banaitis, A.; Luthra, S.; Singh, P.L. Can Industry 5.0 Revolutionize the Wave of Resilience and Social Value Creation? A Multi-Criteria Framework to Analyze Enablers. Technol. Soc. 2022, 68, 101887. [Google Scholar] [CrossRef]
  23. Sobieszczanski-Sobieski, J.; Morris, A.; van Tooren, M.; Rocca, G.L.; Yao, W. Multidisciplinary Design Optimization Architectures. In Multidisciplinary Design Optimization Supported by Knowledge Based Engineering; John Wiley & Sons, Ltd.: New York, NY, USA, 2015; pp. 155–207. ISBN 978-1-118-89707-2. [Google Scholar]
  24. Cooper, R.G.; Edgett, S.J.; Kleinschmidt, E.J. New Product Portfolio Management: Practices and Performance. J. Prod. Innov. Manag. 1999, 16, 333–351. [Google Scholar] [CrossRef]
  25. Kügler, P.; Dworschak, F.; Schleich, B.; Wartzack, S. The Evolution of Knowledge-Based Engineering from a Design Research Perspective: Literature Review 2012–2021. Adv. Eng. Inform. 2023, 55, 101892. [Google Scholar] [CrossRef]
  26. Pech, R.M. Achieving the Innovative Edge in Technology, Engineering Design, and Entrepreneurship. J. Innov. Entrep. 2016, 5, 6. [Google Scholar] [CrossRef]
  27. Jo, H.H.; Parsaei, H.R.; Sullivan, W.G. Principles of Concurrent Engineering. In Concurrent Engineering: Contemporary Issues and Modern Design Tools; Parsaei, H.R., Sullivan, W.G., Eds.; Springer: Boston, MA, USA, 1993; pp. 3–23. ISBN 978-1-4615-3062-6. [Google Scholar]
  28. Chiarello, F.; Belingheri, P.; Fantoni, G. Data Science for Engineering Design: State of the Art and Future Directions. Comput. Ind. 2021, 129, 103447. [Google Scholar] [CrossRef]
  29. McAlpine, H.; Hicks, B.J.; Huet, G.; Culley, S.J. An Investigation into the Use and Content of the Engineer’s Logbook. Des. Stud. 2006, 27, 481–504. [Google Scholar] [CrossRef]
  30. Raza, S.M.; Minerva, R.; Martini, B.; Crespi, N. Empowering Microservices: A Deep Dive into Intelligent Application Component Placement for Optimal Response Time. J. Netw. Syst. Manag. 2024, 32, 84. [Google Scholar] [CrossRef]
  31. Towards Applying API Gateway to Support Microservice Architectures for Embedded Systems. Available online: https://www.researchgate.net/publication/361952256_Towards_Applying_API_Gateway_to_Support_Microservice_Architectures_for_Embedded_Systems#fullTextFileContent (accessed on 24 November 2024).
  32. Panjuta, D.; Jabbarzadeh, J. C# Application Programming Interface. In Learning C# Through Small Projects; Panjuta, D., Jabbarzadeh, J., Eds.; Springer Nature: Cham, Switzerland, 2024; pp. 341–391. ISBN 978-3-031-51914-7. [Google Scholar]
  33. Automation in Business: Enhancing Efficiency and Reducing Costs|OpenAPIHub Community. Available online: https://www.fabrixai.com/blog/automation-in-business-enhancing-efficiency-and-reducing-costs (accessed on 24 November 2024).
  34. Brazhenenko, M.; Petrivskyi, V.; Bychkov, O.; Sinitcyn, I.; Shevchenko, V. Enabling Big Data Query with Modern CAD Systems Redundant Data Stores. In Proceedings of the 2021 IEEE 16th International Conference on the Experience of Designing and Application of CAD Systems (CADSM), Lviv, Ukraine, 22–26 February 2021; IEEE: New York, NY, USA, 2021; pp. 5–9. [Google Scholar]
  35. Heikkinen, T.; Johansson, J.; Elgh, F. Review of CAD-Model Capabilities and Restrictions for Multidisciplinary Use. Comput. Aided Des. Appl. 2018, 15, 509–519. [Google Scholar] [CrossRef]
  36. Gloria Del Río-Cidoncha, M.; Martínez-Palacios, J.; Ortuño-Ortiz, F. Task Automation for Modelling Solids with Catia V5. Aircr. Eng. Aerosp. Technol. 2007, 79, 53–59. [Google Scholar] [CrossRef]
  37. Esanakula, D.J.R. A Process for Creating and Designing Automated CAD Models Through the SolidWorks API. IJIMSR 2024, 2, 23–41. [Google Scholar] [CrossRef]
  38. Inventor 2024 Help|Introduction to Using Inventor’s Programming Interface|Autodesk. Available online: https://help.autodesk.com/view/INVNTOR/2024/ENU/?guid=GUID-6FD7AA08-1E43-43FC-971B-5F20E56C8846 (accessed on 24 November 2024).
  39. Chernikov, O. Increasing Computer Modeling Capabilities by Using API (at the Example of Autodesk Inventor Package). Bull. KhNAHU 2022, 99, 111–117. [Google Scholar] [CrossRef]
  40. Yoo, S.; Lee, S.; Kim, S.; Hwang, K.H.; Park, J.H.; Kang, N. Integrating Deep Learning into CAD/CAE System: Generative Design and Evaluation of 3D Conceptual Wheel. Struct. Multidisc Optim. 2021, 64, 2725–2747. [Google Scholar] [CrossRef]
  41. Sofias, K.; Kanetaki, Z.; Stergiou, C.; Jacques, S. Combining CAD Modeling and Simulation of Energy Performance Data for the Retrofit of Public Buildings. Sustainability 2023, 15, 2211. [Google Scholar] [CrossRef]
  42. Kaldheim, W.A.; Haaland Paaske, H.; Valvik, J.E.; Lobov, A. Building Design Automation: Knowledge Fusion-Based KBE System. In Proceedings of the 2023 IEEE 28th International Conference on Emerging Technologies and Factory Automation (ETFA), Sinaia, Romania, 12–15 September 2023; IEEE: New York, NY, USA, 2021; pp. 1–8. [Google Scholar]
  43. Autodesk Inventor Software. Available online: https://www.autodesk.com/products/inventor/overview (accessed on 24 November 2024).
  44. Gembarski, P.C. Joining Constraint Satisfaction Problems and Configurable CAD Product Models: A Step-by-Step Implementation Guide. Algorithms 2022, 15, 318. [Google Scholar] [CrossRef]
  45. Kantaros, A.; Zacharia, P.; Drosos, C.; Papoutsidakis, M.; Pallis, E.; Ganetsos, T. Smart Infrastructure and Additive Manufacturing: Synergies, Advantages, and Limitations. Appl. Sci. 2025, 15, 3719. [Google Scholar] [CrossRef]
  46. Liang, X.; Yu, S.; Meng, B.; Ju, Y.; Wang, S.; Wang, Y. Machine-Learning-Guided Design of Nanostructured Metal Oxide Photoanodes for Photoelectrochemical Water Splitting: From Material Discovery to Performance Optimization. Nanomaterials 2025, 15, 948. [Google Scholar] [CrossRef]
Figure 1. Stages of the automation process.
Figure 1. Stages of the automation process.
Applsci 15 07692 g001
Figure 2. Components of the processing chain.
Figure 2. Components of the processing chain.
Applsci 15 07692 g002
Figure 3. Block diagram of the code proposed in this study.
Figure 3. Block diagram of the code proposed in this study.
Applsci 15 07692 g003
Figure 4. Case studies examined.
Figure 4. Case studies examined.
Applsci 15 07692 g004
Figure 5. Organization of data archiving in the form of an MS Excel index spreadsheet.
Figure 5. Organization of data archiving in the form of an MS Excel index spreadsheet.
Applsci 15 07692 g005
Figure 6. Case #2: CAD file (ipt) and automatically created drawing file (idw). Note: Detailed directory structures and the VBA routines underpinning this drawing-generation workflow are provided in Appendix A.
Figure 6. Case #2: CAD file (ipt) and automatically created drawing file (idw). Note: Detailed directory structures and the VBA routines underpinning this drawing-generation workflow are provided in Appendix A.
Applsci 15 07692 g006
Figure 7. Example of an automatically code-generated drawing for the respected part of Case #2.
Figure 7. Example of an automatically code-generated drawing for the respected part of Case #2.
Applsci 15 07692 g007
Figure 8. Case #3: CAD file (ipt) and automatically created drawing file (idw).
Figure 8. Case #3: CAD file (ipt) and automatically created drawing file (idw).
Applsci 15 07692 g008
Figure 9. Report file automatically created for the respected part of Case #3.
Figure 9. Report file automatically created for the respected part of Case #3.
Applsci 15 07692 g009
Figure 10. Automatic report for Case #3.
Figure 10. Automatic report for Case #3.
Applsci 15 07692 g010
Figure 11. Time required for design documentation using the manual method.
Figure 11. Time required for design documentation using the manual method.
Applsci 15 07692 g011
Figure 12. Time required for design documentation using the automatic method.
Figure 12. Time required for design documentation using the automatic method.
Applsci 15 07692 g012
Figure 13. Time savings on design documentation: comparison between manual and automatic methods.
Figure 13. Time savings on design documentation: comparison between manual and automatic methods.
Applsci 15 07692 g013
Table 1. Financial data for Case #3.
Table 1. Financial data for Case #3.
Financial Data
Material Price (EUR):300
Reverse Engineering Time (hours)6
Setup Time (hours)4
Machining Time (hours)6
Consumables (EUR):250
Table 2. Summary of key outcomes from case study automation scenarios.
Table 2. Summary of key outcomes from case study automation scenarios.
Case StudyAutomation FocusMain Features ImplementedTime SavingsError ReductionScalability
Case 1Folder creation and structured data archivingAuto-generation of folders, Excel-based index with hyperlinks~90% reduction (2.9 h → 8 min)Eliminated manual folder errorsHigh—reusable across all part types
Case 2Drawing generation from CAD part filesAutomated .idw file creation, three-view layouts, title block completion, metadata insertionSignificant for batch processesStandardized output, minimized omissionsHigh—adaptable to various drawing types
Case 3Full workflow automation with cost estimationCAD + drawing generation, directory creation, financial calculator, automated MS Word report with footprint boxEnd-to-end automationFull integration of metadata and cost dataVery high—modular, fully expandable
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content.

Share and Cite

MDPI and ACS Style

Sofias, K.; Kanetaki, Z.; Stergiou, C.; Kantaros, A.; Jacques, S.; Ganetsos, T. Implementing CAD API Automated Processes in Engineering Design: A Case Study Approach. Appl. Sci. 2025, 15, 7692. https://doi.org/10.3390/app15147692

AMA Style

Sofias K, Kanetaki Z, Stergiou C, Kantaros A, Jacques S, Ganetsos T. Implementing CAD API Automated Processes in Engineering Design: A Case Study Approach. Applied Sciences. 2025; 15(14):7692. https://doi.org/10.3390/app15147692

Chicago/Turabian Style

Sofias, Konstantinos, Zoe Kanetaki, Constantinos Stergiou, Antreas Kantaros, Sébastien Jacques, and Theodore Ganetsos. 2025. "Implementing CAD API Automated Processes in Engineering Design: A Case Study Approach" Applied Sciences 15, no. 14: 7692. https://doi.org/10.3390/app15147692

APA Style

Sofias, K., Kanetaki, Z., Stergiou, C., Kantaros, A., Jacques, S., & Ganetsos, T. (2025). Implementing CAD API Automated Processes in Engineering Design: A Case Study Approach. Applied Sciences, 15(14), 7692. https://doi.org/10.3390/app15147692

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop