Browse Topic: Standardization
This SAE standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a The supplier shall ascertain customer requirements b The supplier shall meet customer requirements c The supplier shall assure that customer requirements have been met
The useability of development processes in the automotive sector has decreased in the past years to a level at which their application and true benefit to is being questioned. Such degradation can be attributed to new additions to the processes and introduction of FuSa and Cybersecurity standards. The processes try to keep up with the shift from the traditional ‘plan–implement–test–roll-out' methodology to more agile methods. In addition, process departments typically in charge of these processes, focus on compliance to the letter of the standard to achieve certification, often with little thought to the actual implementation and the process they will be used by their engineering teams. Process growth to meet the needs of new and more complex technologies often mandates the use of new tools, which if implemented incorrectly can lead to unnecessary bureaucracy and additional overheads. Furthermore, the language of these new processes is in a form from assessor, making it difficult for an engineer to understand, interpret and implement. As a result, engineers become annoyed, losing productivity and motivation when working with what they perceive as burdensome standards, that simply exist to slow development. This has a huge impact on the competitiveness of companies especially in markets that are facing existential threats from internal and external pressures such as the automotive industry. Against popular belief, the application of generative AI (and large language models) will not solve the problem. On the contrary, it risks automating complex processes in the same unfamiliar language and creating documents to serve process overhead, rather than engineering development. This paper presents inefficiencies in the current state-of-the art processes used in the automotive sector and proposes a structured approach that increases the efficiency of automotive software development. It does so by documenting and implementing development processes based on how engineers actually perform their work. In the second step the adjustments that are necessary to ensure compliance of the product with industry standards are made. Such an approach produces efficient, compact and compliant process definition.
The automotive industry is evolving from a reactive, independently self-determined approach to cybersecurity, complicated by a complex supply chain. Over time, this has resulted in a fragmented industry comprised of any number of proprietary solutions verses a standardized, regulated paradigm to facilitate a platform-oriented approach. This document, an update on collaborative work from the SAE Vehicle Electrical Hardware Security Task Force (TEVEES18B) and GlobalPlatform Automotive Task Force, outlines this transition strategy. An extensible number of additional examples of use cases of Global Platform Technologies are explored in this document.
The automotive industry is undergoing a fundamental transformation in Electrical/Electronic (E/E) architecture, evolving from traditional distributed and domain-based designs toward zonal configurations. The rapid growth of software-defined functionality, cross-domain integration, and centralized computing has exposed inherent limitations of legacy architectures in scalability, wiring complexity, and system integration. Zonal E/E architecture addresses these challenges by consolidating computing and Input/Output (I/O) resources into high-performance controllers distributed across physical zones of a vehicle. This transformation, however, cannot occur instantaneously, as contemporary vehicle designs and E/E system solutions are the result of decades of incremental development based on distributed and domain-based paradigms. Moreover, key enabling technologies for zonal E/E architecture—such as high-performance Central Compute Platform (CCP) and zonal controllers, high-speed automotive Ethernet, and standardized software architecture—are still maturing. To ensure safety, reliability, and cost-effectiveness, Original Equipment Manufacturers (OEMs) must therefore adopt carefully planned evolution strategy to progressively consolidate functions, realizing the zonal design step by step. This paper proposes a unified architectural framework that systematically maps the full spectrum of evolutionary paths toward zonal E/E architecture. The framework identifies major transition stages, key engineering activities, and alternative migration paths, including distributed and domain-based architectures, vertical and horizontal function integration, various domain fusion patterns, mixed E/E architecture, continuous function migration to CCP and zonal controllers, and ultimately, the full realization of zonal E/E architecture. By organizing and contrasting these evolutionary paths, the framework provides OEMs with architectural insight and practical guidance for planning low-risk, staged transition toward fully zonal E/E architecture capable of supporting next-generation Software-Defined Vehicles (SDVs).
The roles of aerospace and defense engineers have profoundly changed. Systems integrators and acquisition programs require “standardized openness” while also wishing for boxes that take up less space, weight, and power. Despite the push towards Modular Open Systems Approach (MOSA), Sensor Open Systems Architecture (SOSA), and similar open standards, there are still opportunities to use non-standardized, small form factor (SFF) designs. As outlined in the project examples below, a purpose-built SFF module can address technical system requirements better than any current approach focused on open standards.
This paper reviews the current situation in the terms and definitions that influence the development of testing and prediction in automotive, aerospace and other areas of engineering. The accuracy of these terms and definitions is very important for correct simulation, testing and prediction. This paper aims to define accurate terms and definitions. It also includes the author’s recommendations for improving this situation and preparing new standards.
Aerospace and defense system designers are demanding scalable and high-performance I/O solutions. While traditional mezzanine standards have proven reliable, they often fall short of meeting modern bandwidth, size, and flexibility requirements. This challenge is particularly evident in aerospace and defense applications where high-speed data processing must align with stringent size, weight, and power (SWaP) constraints. Current mezzanine solutions also face significant limitations in scalability, thermal management, and I/O density. These constraints can lead to compromised system performance and limited upgrade paths in applications where adaptability is crucial. This article explores how the new VITA 93 (QMC) standard addresses these challenges through its innovative QMC architecture, enabling unprecedented flexibility, scalability, and rugged reliability while maintaining compatibility with existing and future systems. It also covers how VITA 93 (QMC) builds on lessons learned from previous standards, blending their best features with new capabilities for the future.
SAE J3108 Recommended Practice (RP) provides fuel and hazard guidance for first and second responders of incidents associated with alternative fueled vehicles. The intent of SAE J3108-1 is to present responders with a limited number of intuitive letters and colors. The International community is in the process of adopting International Standards Organization (ISO) 17840, which provides first and second responders with a standardized format for emergency information. While the ISO 17840 format in coloring and lettering can be adopted and should be encouraged when possible, it is intended for large and heavy vehicles. SAE J3108-1 provides a means for responders to recognize fuel and vehicle type on North American light duty vehicles due to size constraints preventing use of ISO 17840 labels.1 While encouraged to be adopted or referenced by vehicle manufacturers, this RP has been developed for the use of States and other Governmental bodies. The RP is not intended to replace the standards for SAE J2990 format emergency response guide (ERG) created by automotive manufacturers for use at the scene of an emergency. This coding should be consistent with other vehicle badging with the goal of providing additional clarity. This RP does not include detailed equipment and procedures such as tools, personal protective equipment, or other aspects required for addressing vehicles which have been involved in accidents or incidents. Other documents providing those aspects are contained in the list of references. This RP is independent of existing U.S. Department of Transportation (DOT) hazardous labeling and nomenclature provided by Code of Federal Regulations Title 49. The ten hazard symbols and four levels of severity rating are insufficient to identify the unique aspects of configurations which may be specific to various vehicles designs. Those symbols are typically not used on the passenger types of vehicles this RP is meant for. This RP also does not supersede current DOT requirements, U.S. Federal Regulations, or other regional regulations for identifying vehicle fuel and critical first responder information.
When a physician injects a patient with medication from a glass vial, they want to know that the drug inside that vial is sterile and stable. That’s where Genesis Packaging Technologies comes in. Genesis Packaging Technologies, formally a division of the West Company, was founded in 1946. Today, Genesis is a one of the leaders in the science and technology of parenteral vial sealing and residual seal force testing.
Pulsed field ablation (PFA) is a nonthermal method of tissue ablation technology that uses high amplitude pulsed electrical fields (PEF) to create irreversible electroporation (IRE) in tissues. Unlike traditional thermal ablation technologies, PFA does not rely on heating to damage and destroy tissue. Instead, PFA creates nanopores in cell membranes due to transient, high-voltage exposure that disrupts cell wall integrity, which leads to cell death.1
SAE updates gasoline fuel-injection standards, additions expected Gasoline Fuel Injection Standards Committee (GFISC) updates three standards and plans to publish two more. The Gasoline Fuel Injection Standards Committee (GFISC) plays a pivotal role in developing and maintaining SAE's Standards, Recommended Practices (RP) and Information Reports (IR) for the mechanical and electrical components of gasoline fuel-injection systems. Since a prior update was published in May 2019, the committee has made significant progress to ensure the relevancy and accuracy of these standards, with three updated standards published since 2021 and the expected publication of two more in 2024.
SAE International announced in late June, 2023, that it intended to standardize the Tesla-developed North American Charging Standard (NACS) EV charging connector for North America. SAE then created the J3400 NACS Task Force to expedite creation of the J3400 NACS Electric Vehicle Coupler standard. Grayson Brulte, host of SAE's Tomorrow Today podcast, subsequently interviewed Christian Thiele, Director, Global Ground Vehicle Standards, SAE International, and Dr. Rodney McGee, Ph.D., P.E. Chairman, SAE J3400 NACS Task Force and Chief Engineer at the University of Delaware, regarding the work of the J3400 Task Force and other aspects of standardization as electrification technology proliferates throughout the light- and heavy-duty vehicle sectors. This Q&A is an abbreviated portion of that interview and the podcast can be heard in its entirety at: https://www.sae.org/podcasts/tomorrow-today/episodes/sae-to-standardize-teslanacs-connector
Items per page:
50
1 – 50 of 1239