Browse Topic: Product development
In this study, we propose a methodology for predicting the acoustic modes and natural frequencies of a sedan using artificial intelligence and demonstrate the feasibility of controlling its acoustic characteristics by modifying the hole distribution of the package tray. In typical sedan structures, the cabin cavity and trunk cavity are acoustically coupled through holes in the package tray. The distribution of these holes significantly affects the natural acoustic modes and frequencies of the vehicle. However, once the exterior shape of the vehicle is finalized during the design stage, options for structural modifications to mitigate noise issues caused by these modes become extremely limited. To address this challenge efficiently, we develop a deep learning-based neural network model trained on data derived from a simplified acoustic analysis model of a sedan that includes a package tray. Finite element analysis is performed to generate acoustic modes and natural frequencies, which
Noise phenomena in automobiles caused by the stick-slip effect are increasingly among the most frequent reasons for customer complaints and therefore represent a critical vehicle quality attribute. To proactively address such issues, stick-slip testing of contacting material pairs is commonly applied during development. However, the predictive capability of current stick-slip test methods remains limited, particularly when highly flexible materials and realistic, stochastic excitation conditions are involved. The flexibility of sealing systems often allows the actual relative motion at the contact interface to be accommodated through adhesion and elastic deformation, thereby delaying or even preventing sliding. To date, this effect has not been represented by any characteristic parameter in conventional stick-slip testing. Instead, existing evaluations focus exclusively on the analysis of occurring stick-slip oscillations. For the initiation of stick-slip phenomena, however, not only
The aerospace industry is undergoing a significant digital transformation in the way system requirements are defined, communicated, and managed. Major OEMs are moving towards fully model-based development processes, with plans to deliver requirements exclusively in the form of models. It is no longer sufficient to manage requirements using traditional document-based approaches; instead, organizations must adopt tools and processes that enable the consumption, interpretation, and implementation of model-based requirements. However, MBSE itself does not ensure that the requirements defined within the model are complete or consistent. Without rigorous validation techniques, even well-structured models can carry forward poorly defined or conflicting requirements — leading to errors that propagate throughout the development lifecycle. This work proposes an approach that integrates formal methods into MBSE workflows by enabling completeness and consistency checks of SysML-based requirements
The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance
The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance
The concept of the vehicle has changed as a result of many innovations over the last decade in the fields of connected, autonomous/automated, shared, and electric (CASE) technologies. At the same time, labor shortages in Japan are becoming more serious due to a decline in the working population. To help resolve these issues, a remote-controlled autonomous vehicle driving system called Telemotion has been developed that automates the movement of vehicles in production plants. This system is an autonomous driving and transportation system in which the recognition, judgment, and operation functions of driving are handled by a control system outside the vehicle that communicates wirelessly with the vehicle. This system utilizes artificial intelligence (AI) and other advanced technologies to realize safe unmanned autonomous driving, and is already in operation in production plants. Currently, efforts are under way to build a digital twin environment and conduct AI learning using computer
This paper builds on last year’s paper presenting DevOps automation in the context of model-based development. Following that paper, we interviewed Simulink users in passenger automotive, motorsports, commercial vehicles, aviation, rocketry, and industrial automation. We discovered that much of the benefit of DevOps platforms to reduce product development cycle time relies on their interactive features. We prototyped new tools to bridge interactive DevOps Git-based platforms with model-based development workflows, and then gathered reactions from another round of interviews. Here we present these interactive DevOps workflows with the feedback from these interviews to contextualize how engineering teams could adopt them to accelerate their own model-based workflows.
Items per page:
50
1 – 50 of 4162