Browse Topic: Product development
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 Sixties. 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
This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.
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.
Industries are following a tedious product development cycle for developing their product. In product development major steps includes design ideas, Drawings, CAD, CAE, Testing and design improvement cycle. This is a monotonous process and takes time which impacts on its time to deliver product and cost on development. Now a days industries are fast growing and targeting to reduce development cycle time and cost. AI&ML is impacting almost all areas in the industry and significantly reducing efforts time and cost. To make use of AI&ML in CAE, Altair Physics AI is an effective tool. To ensure the design of product traditional way is to develop a CAD of the product, develop, perform CAE and analyze performance. If we consider CAE procedure it is time consuming process which includes FEA model build, applying boundary conditions, running simulation and analyzing results which could take minutes to hours. By using ML with Physics AI we can make predictions on new design of the product in
The automotive industry is subject to major transformation initiated by societal and economical pull (reducing emissions, zero fatalities, European competitiveness) and accelerated by technology push (electrification, Cooperative, Connected and Automated Mobility (CCAM), and Cooperative Intelligent Transport Systems (C-ITS)). Following this trend, the Software-Defined Vehicle (SDV) targets the integration of software (SW) development methodologies for vehicle development as well as the value delivery shift toward customers along the entire lifecycle. It promises to create benefits for the car manufacturers in terms of faster time to market, easier update – as well as for the car users (private persons, fleet operators) in terms of personalized user experience, upgradability. At the same time, SDV requires a much more integrated and continuous development framework to enable different experts to efficiently develop and validate concurrently the different parts of the vehicles, to gather
Items per page:
50
1 – 50 of 4155