Your Destination for Mobility Engineering Resources

The implemented Vehicle-to-Everything (V2X) infrastructure for CI must adhere to the minimum performance outlined in the CTI Implementation Guide (CTI 4501/1) to ensure interoperability basic RLVW application within vehicles. The basic RLVW application operates at the onset of the yellow phase during the yellow phase duration of a through movement. This assessment tool and procedure aims to confirm that the duration of the yellow phase, as generated by the Traffic Signal Control (TSC) system during the transition from green to yellow, is precise, and that the information broadcasted by the Roadside Unit (RSU) maintains a consistent periodicity for RLVW. A set of criteria has been established to evaluate and verify the performance of the CI. Conformance – The broadcast SPaT message adheres to: Required data elements for RLVW application as per CTI 4501 Message structure and data format as outlined in SAE J2735 Data values within the range specified in SAE J2735 Periodicity – The CI infrastructure ensures consistent broadcast message periodicity. Accuracy – The CI infrastructure assures the accuracy of signal phase status and timing information. Latency – The CI infrastructure broadcasts messages in a timely manner. This document describes the following: An example test data acquisition system and procedure for collecting field data from a connected intersection Test scenarios to verify the real-world performance of a CI Analysis of broadcast message structure, data format and required data elements as per SAE J2735 and CTI 4501/1 Analysis of broadcast SPaT message accuracy relative to the actual signal controller actions that represents the ground truth for signal phase start time and duration Analysis of SPaT information generation and processing latency from signal controller actions to message broadcast Analysis of stability and reliability of the information flow to connected vehicles
Connected Transportation Interoperability Committee
SAE J3078/5 specifies a test method for testing defrosting systems. It is applicable to off-road self-propelled work machines as defined in SAE J1116 and agricultural tractors as defined in ANSI/ASAE S390. The full list of machines covered is included in Table 1.
HFTC6, Operator Accommodation
Connected Transportation Interoperability (CTI) 4501 establishes requirements for SAE J2735 MAP Message node point accuracy supporting in-vehicle Red Light Violation Warning (RLVW) applications. These requirements are specified in relation to pavement markings defining ingress and egress lane boundaries for mapped intersections. Commercial mobile mapping services typically use a combination of scanning Light Detection and Ranging (LiDAR) technology in conjunction with high-accuracy positioning and multi-axis high-resolution photography to create three-dimensional (3D) models of roadways which include the locations of lane markings, curbs, stop lines, and crosswalks. This document describes testing and assessment methodologies using this information to verify the accuracy of MAP node point data focusing on through movement ingress lanes to support basic in-vehicle RLVW applications.
Connected Transportation Interoperability Committee
G-3, Aerospace Couplings, Fittings, Hose, Tubing Assemblies
This SAE Aerospace Standard (AS) establishes the requirements for bite-type sleeves for use with 24-degree cone flareless fluid connection fittings per AS18280.
G-3, Aerospace Couplings, Fittings, Hose, Tubing Assemblies
G-3, Aerospace Couplings, Fittings, Hose, Tubing Assemblies
G-3, Aerospace Couplings, Fittings, Hose, Tubing Assemblies
Given the limited adaptability of conventional single-model model predictive control (MPC) to the complex driving conditions encountered by intelligent vehicles on varying road surfaces, as well as the trade-off between modeling accuracy and computational efficiency, this study proposes an adaptive multi-model-switching MPC strategy for trajectory tracking control. First, three prediction models with different levels of complexity are developed, including a kinematic model, a linear two-degree-of-freedom (2-DOF) dynamic model, and a nonlinear tire dynamic model. A model-switching mechanism based on vehicle speed, road curvature, and road-surface friction is then designed to select the appropriate prediction model according to the prevailing driving conditions. In addition, a lateral-deviation feedback correction strategy is introduced to further improve tracking accuracy and smooth the steering response. Finally, joint simulations using MATLAB/Simulink and CarSim are conducted under four representative driving scenarios. The results show that, compared with conventional single-model MPC, the proposed strategy effectively reduces lateral tracking errors and steering-angle fluctuations while maintaining favorable computational efficiency and vehicle stability. These results demonstrate the potential of the proposed method to achieve accurate and robust trajectory tracking for intelligent vehicles under complex and varying operating conditions.
Lai, Fei, Sun, Junhao, Huang, Chaoqun
The following listed definitions are intended to establish terminology and criteria for describing the various kinds of automotive transmissions. A specific arrangement may be described by a combination of several of these definitions.
Automatic Transmission and Transaxle Committee
G-3, Aerospace Couplings, Fittings, Hose, Tubing Assemblies
This document identifies and expands upon many of the issues and challenges in obtaining high-quality total-pressure measurements at the designated Aerodynamic Interface Plane (AIP). More specifically, it applies to the measurement of inlet total pressure used to characterize and quantify inlet distortion and inlet total-pressure recovery for gas turbine applications where they factor into turbine engine stability or performance. This includes ground (subscale or full-scale wind tunnel and engine tests) and flight test pressure measurements. Static pressure measurements are also useful for understanding inlet flow characteristics; therefore, a section is included describing static pressure installation considerations within an inlet.
S-16 Turbine Engine Inlet Flow Distortion Committee
AS5259 covers design requirements, performance requirements, and methods of procurement for tools and associated accessories used to crimp wire barrels of aircraft electrical wiring components including ferrules, terminals, splices, and connector contacts on wire/cable sizes 8 to 4/0.
AE-8C2 Terminating Devices and Tooling Committee
ACBG Rolling Element Bearing Committee
Methanol is emerging as a promising potential fuel for the commercial marine industry. However, because methanol is challenging to ignite from compression alone, it is not directly suited as a drop-in compression ignition fuel. One of the most straightforward ways to use methanol in the compression ignition engines is to premix the methanol, such as with port fuel injection during the intake stroke, and then to ignite it with a diesel pilot injection. Although this is the most straightforward approach for methanol, high pressure rise rates occur, which historically have limited methanol utilization. The present work explores pathways that could increase methanol utilization in dual-fuel engines by employing injection strategies and engine control parameters. Results from these approaches are shown in this work to increase methanol utilization up to 75%–90% across a wide range of loads, spanning break-even power to full load operation at 1,800 rpm. A thermodynamic evaluation of the pathways used to achieve these results is presented, along with the utility of employing multiple injections of the diesel pilot fuel.
Splitter, Derek, Jatana, Gurneesh, Szybist, James, Svensson, Kenth, Montgomery, Dave
To address the issue of excessive computational time consumption associated with finite element analysis in calculating the contact pressure distribution of the internal combustion engine piston skirt, this study proposes a deep learning–based mapping approach from low-dimensional geometric parameters to high-dimensional images. The improved U-Net model embedded with a convolutional block attention module, bilinear upsampling, and partitioned weighted hybrid loss function is augmented with an extra feature projection layer to boost mapping performance. The results indicate that the proposed model shows good agreement with the numerical simulation results in forecasting the contact pressure distribution. The mean absolute percentage error of the prediction results is below 7%, and each independent prediction requires approximately 2.8 s, demonstrating the computational efficiency of the proposed surrogate model. Under the maximum-torque condition, the proposed method reproduced the overall thrust side contact pressure distribution of unseen profiles, demonstrating its capability as a rapid surrogate model for piston skirt contact pressure evaluation within the parameter range.
Hao, Jiang, Manying, Yang, Dong, Fei
The scope of this SAE Information Report is an evaluation of the ports and tools used on automotive air-conditioning systems to evacuate and charge systems with approved refrigerants during vehicle service. A task force was formed in April 2021 to perform this evaluation and concluded its work in September 2021. The scope of the task force was to evaluate issues being reported from service repair shops with air-conditionings service ports and the tools being used to connect to these ports. The task force also evaluated published SAE J Standards and discovered many of these standards did not include the necessary requirements for service ports and tools. The task force published a final report of its findings and recommendations. The report includes recommendations to correct and publish new SAE Standards related to the scope of this project.
ICTMS Supplier Committee
The scope of this information report is battery packs containing lithium-ion battery cells with liquid electrolyte, focusing on automotive applications like passenger cars and trucks. This document assumes that venting of the gases produced during thermal runaway and emergency degassing is allowable according to local safety regulations and requirements. It is the manufacturer’s responsibility to confirm compliance with application-specific safety and regulatory requirements which can be chemistry-dependent. Considering different operating conditions as well as durability and safety requirements, some of its contents might provide guidance for other applications. The same applies to battery cell chemistries not covered in this report (e.g., sodium-ion or solid-state battery cells).
Battery Pack Venting Committee
CTI 4501 defines the key capabilities and interfaces a connected signalized intersection must support to ensure interoperability with vehicles, including production vehicles, for state and local IOOs. A connected intersection is defined as an infrastructure system that broadcasts SPaT, MAP, and optionally position correction data to vehicles. The CTI 4501 family of documents define procurement and implementation guidance and the expectations leading to minimum performance requirements for a connected intersection. It is intended to be used by IOOs to provide guidance on how to implement an interoperable connected intersection. For OEMs and other application developers, these recommended practices provide an explanation on what data and connected vehicle messages are being provided from an interoperable connected intersection so safety applications can be developed for production vehicles, with an initial focus on the Red Light Violation Warning (RLVW) application. Although the focus is on the RLVW application, requirements for other V2X applications related to connected intersections, including requirements for traffic signal controllers to generate the SPaT information, are also addressed assuming the connected intersection configuration and messages can support them and no significant effort was needed. The Needs to Requirements Traceability Matrix (NRTM) in CTI 4501 6.2.3 provides the guidance to IOOs for the procurement of a connected intersection. Recognizing that some stakeholders require more in-depth guidance on specific aspects of connected intersections, Version 2 of the CI Implementation Guide has been reorganized into a main document and several companion sub-documents. The main document establishes the overarching framework - following a Systems Engineering Process (SEP) - and includes a Concept of Operations (ConOps) and an NRTM for a connected intersection and the generic requirements, generic system design details, and an RTM for those generic requirements. These elements enable users to identify and procure connected intersection solutions that satisfy their specific needs. The companion documents elaborate on specialized areas such as SPaT, MAP, security, and testing and validation, providing requirements and design details tailored for those subject areas. Figure 1 depicts the relationships among these sub-documents and other documents that support the implementation of a connected intersection. By separating out these focused topics, the guide more effectively supports IOOs, OEMs, suppliers, and application developers who need targeted information. Taken together, the main guide and the companion documents ensure that connected intersection deployments align with national standards and support a high level of interoperability, ultimately facilitating safer and more efficient automated transportation systems. This document offers procurement and implementation guidance specific to SPaT messages in one focused resource while aligning with the overall structure and methodology of the main CTI 4501 document. It provides the requirements, design guidance, and testing considerations necessary to achieve minimum performance requirements for providing SPaT messages tailored for IOOs, OEMs, and application developers. This document allows stakeholders seeking detailed guidance on SPaT-related requirements and design considerations to access all relevant information in one focused resource while equipping practitioners with a comprehensive set of tools to design and deploy interoperable connected intersections. For IOOs, this document provides actionable guidance on specifying and deploying SPaT-capable equipment to support interoperable connected intersections. For OEMs and developers, it explains which SPaT-related data and connected vehicle messages will be broadcast from compliant intersections, enabling the development of safety-critical applications such as RLVW.
Connected Transportation Interoperability Committee
CTI 4501 defines the key capabilities and interfaces a connected signalized intersection must support to ensure interoperability with vehicles, including production vehicles, for state and local IOOs. A connected intersection is defined as an infrastructure system that broadcasts SPaT, MAP, and optionally position correction data to vehicles. The CTI 4501 family of documents define procurement and implementation guidance and the expectations leading to minimum performance requirements for a connected intersection. It is intended to be used by IOOs to provide guidance on how to implement an interoperable connected intersection. For OEMs and other application developers, these recommended practices provide an explanation on what data and connected vehicle messages are being provided from an interoperable connected intersection so safety applications can be developed for production vehicles, with an initial focus on the Red Light Violation Warning (RLVW) application. Although the focus is on the RLVW application, requirements for other V2X applications related to connected intersections, including requirements for traffic signal controllers to generate the SPaT information, are also addressed assuming the connected intersection configuration and messages can support them and no significant effort was needed. The Needs to Requirements Traceability Matrix (NRTM) in 6.2.3 provides the guidance to IOOs for the procurement of a connected intersection. Recognizing that some stakeholders require more in-depth guidance on specific aspects of connected intersections, Version 2 of the CI Implementation Guide has been reorganized into a main document and several companion sub-documents. The main document establishes the overarching framework - following a Systems Engineering Process (SEP) - and includes a Concept of Operations (ConOps), System Requirements (Functional Requirements), System Design Details, and an NRTM. These elements enable users to identify and procure connected intersection solutions that satisfy their specific needs. The companion documents elaborate on specialized areas such as SPaT, MAP, security, and testing and validation, providing requirements and design details tailored for those subject areas. Figure 1 depicts the relationships among these sub-documents and other documents that support the implementation of a connected intersection. By separating out these focused topics, the guide more effectively supports IOOs, OEMs, suppliers, and application developers that need targeted information. Taken together, the main guide and the companion documents ensure that connected intersection deployments align with national standards and support a high level of interoperability, ultimately facilitating safer and more efficient automated transportation systems. This Security Guidance document equips practitioners with targeted security guidelines, helping foster reliable, resilient connected intersections that maintain public trust and support the broader goals of interoperable, secure connected intersections. The document addresses multiple facets of security, while aligning with the overall structure and methodology of the main CTI 4501 document, including: Data Trustworthiness - Ensuring the integrity and authenticity of information originating from both infrastructure and vehicles. Communications Security - Protecting data exchanges across all relevant interfaces. System Management and Recovery - Defining best practices for updates, operational modes, and restoration procedures. Verification Requirements - Outlining checks to confirm that security measures are properly implemented. For IOOs, this document provides actionable guidance on specifying and deploying security capabilities and functions to support robust, trustworthy connected intersections. For OEMs and developers, it explains how to secure the data and messages which will be broadcast from interoperable intersections, enabling the development of safety-critical applications such as RLVW.
Connected Transportation Interoperability Committee
CTI 4501 defines the key capabilities and interfaces a connected signalized intersection must support to ensure interoperability with vehicles, including production vehicles, for state and local Infrastructure Owner Operators (IOOs). A connected intersection is defined as an infrastructure system that broadcasts SPaT, MAP, and optionally position correction data to vehicles. This recommended practice defines procurement and implementation guidance and the expectations leading to minimum performance requirements for a connected intersection. It is intended to be used by IOOs to provide guidance on how to implement an interoperable connected intersection. For OEMs and other application developers, this recommended practice provides an explanation on what data and connected vehicle messages are being provided from an interoperable connected intersection so safety applications can be developed for production vehicles, with an initial focus on the Red Light Violation Warning (RLVW) application. Although the focus of the recommended practice is on the RLVW application, requirements for other V2X applications related to connected intersections, including requirements for traffic signal controllers to generate the SPaT information, are also addressed assuming the connected intersection configuration and messages can support them and no significant effort was needed. The Needs to Requirements Traceability Matrix (NRTM) in 6.2.3 provides the guidance to IOOs for the procurement of a connected intersection. Recognizing that some stakeholders require more in-depth guidance on specific aspects of connected intersections, Version 2 of the CI Implementation Guide has been reorganized into a main document and several companion subdocuments. The main document establishes the overarching framework – following a Systems Engineering Process (SEP) – and includes a Concept of Operations (ConOps) and an NRTM for a connected intersection; and the generic requirements, system design details, and a Requirements Traceability Matrix (RTM) for those generic requirements. These elements enable users to identify and procure connected intersection solutions that satisfy their specific needs. The companion documents elaborate on specialized areas such as SPaT, MAP, security, and testing and validation, providing requirements and design details tailored for those subject areas. Figure 1 depicts the relationships among these subdocuments and other documents that support the implementation of a connected intersection. SAE J3258 addresses positioning corrections for all V2X applications in addition to connected intersections. SAE J3305 addresses Assured Green Period and utilizes SPaT messages, linking this document with CTI 4501/1. SAE J3238/1 links to both CTI 4501/1 and CTI 4501/4 by providing an example method for the testing and validation of SPaT information broadcasts. SAE J3238/2 similarly links CTI 4501/2 and CTI 4501/4 by providing an example method for linking the testing and validation of MAP broadcasts. By separating out these focused topics, this recommended practice more effectively supports IOOs, OEMs, suppliers, and application developers who need targeted information. Taken together, this recommended practice (hereafter called the implementation guide) and the companion documents ensure that connected intersection deployments align with national standards and support a high level of interoperability, ultimately facilitating safer and more efficient automated transportation systems.
Connected Transportation Interoperability Committee
CTI 4501 defines the key capabilities and interfaces a connected signalized intersection must support to ensure interoperability with vehicles, including production vehicles, for state and local Infrastructure Owner Operators (IOOs). A connected intersection is defined as an infrastructure system that broadcasts SPaT, MAP, and optionally position correction data to vehicles. The CTI 4501 family of documents define procurement and implementation guidance and the expectations leading to minimum performance requirements for a connected intersection. It is intended to be used by IOOs to provide guidance on how to implement an interoperable connected intersection. For OEMs and other application developers, these recommended practices provide an explanation on what data and connected vehicle messages are being provided from an interoperable connected intersection so safety applications can be developed for production vehicles, with an initial focus on the Red Light Violation Warning (RLVW) application. Although the focus is on the RLVW application, requirements for other V2X applications related to connected intersections, including requirements for traffic signal controllers to generate the SPaT information, are also addressed assuming the connected intersection configuration and messages can support them and no significant effort was needed. The Needs to Requirements Traceability Matrix (NRTM) in CTI 4501, 6.2.3, provides the guidance to IOOs for the procurement of a connected intersection. Recognizing that some stakeholders require more in-depth guidance on specific aspects of connected intersections, Version 2 of the CI Implementation Guide has been reorganized into a main document and several companion subdocuments. The main document establishes the overarching framework – following a Systems Engineering Process (SEP) – and includes a Concept of Operations (ConOps), System Requirements (Functional Requirements), System Design Details, and a Needs to Requirements Traceability Matrix (NRTM). These elements enable users to identify and procure connected intersection solutions that satisfy their specific needs. The companion documents elaborate on specialized areas such as SPaT, MAP, security, and testing and validation, providing requirements and design details tailored for those subject areas. Figure 1 depicts the relationships among these subdocuments and other documents that support the implementation of a connected intersection. By separating out these focused topics, the guide more effectively supports Infrastructure Owner Operators (IOOs), OEMs, suppliers, and application developers who need targeted information. Taken together, the main guide and the companion documents ensure that connected intersection deployments align with national standards and support a high level of interoperability, ultimately facilitating safer and more efficient automated transportation systems. This MAP Message document offers procurement and implementation guidance specific to MAP messages in one focused resource, while aligning with the overall structure and methodology of the main CTI 4501 document. It provides the requirements, design guidance, and testing considerations necessary to achieve minimum performance requirements for providing MAP messages, tailored for Infrastructure Owner Operators (IOOs), automotive OEMs, and application developers. This document allows stakeholders seeking detailed guidance on MAP-related requirements and design considerations to access all relevant information in one focused resource, while equipping practitioners with a comprehensive set of tools to design and deploy interoperable connected intersections.
Connected Transportation Interoperability Committee