Refine Your Search

Topic

Search Results

Event

Digital Summit - WCX™ World Congress Experience

2024-04-19
If you are not able to attend WCX 2022 in-person, you will have the opportunity to join a selected number of live technical and executive discussions online that will advance your skill set in propulsion, connectivity security and safety as well as the business of technology.
Event

Registration - WCX™ World Congress Experience

2024-04-19
Count on SAE International®—the global leader in technical learning for mobility professionals—to deliver emerging research, consumer metrics, regulatory standards and the latest innovations to advance mobility at the WCX World Congress event.
Event

Digital Summit - WCX™ World Congress Experience

2024-04-19
If you are not able to attend WCX 2022 in-person, you will have the opportunity to join a selected number of live technical and executive discussions online that will advance your skill set in propulsion, connectivity security and safety as well as the business of technology.
Standard

Hardware Protected Security for Ground Vehicles

2020-02-10
CURRENT
J3101_202002
Access mechanisms to system data and/or control is a primary use case of the hardware protected security environment (hardware protected security environment) during different uses and stages of the system. The hardware protected security environment acts as a gatekeeper for these use cases and not necessarily as the executor of the function. This section is a generalization of such use cases in an attempt to extract common requirements for the hardware protected security environment that enable it to be a gatekeeper. Examples are: Creating a new key fob Re-flashing ECU firmware Reading/exporting PII out of the ECU Using a subscription-based feature Performing some service on an ECU Transferring ownership of the vehicle Some of these examples are discussed later in this section and some have detailed sections of their own. This list is by no means comprehensive.
Standard

Requirements for Probe Data Collection Applications

2022-06-09
CURRENT
J2945/C_202206
Connected vehicles can provide data from multiple sensors that monitor both the vehicle and the environment through which the vehicle is passing. The data, when shared, can be used to enhance and optimize transportation operations and management—specifically, traffic flow and infrastructure maintenance. This document describes an interface between vehicle and infrastructure for collecting vehicle/probe data. That data may represent a single point in time or may be accumulated over defined periods of time or distance, or may be triggered based on circumstance. The purpose of this document is to define an interoperable means of collecting the vehicle/probe data in support of the use cases defined herein. There are many additional use cases that may be realized based on the interface defined in this document. Note that vehicle diagnostics are not included within the scope of this document, but diagnostics-related features may be added to probe data in a future supplemental document.
Technical Paper

Review on CAN Bus Protocol: Attacks, Difficulties, and Potential Solutions

2023-04-11
2023-01-0926
The new generation vehicles these days are managed by networked controllers. A large portion of the networks is planned with more security which has recently roused researchers to exhibit various attacks against the system. This paper talks about the liabilities of the Controller Area Network (CAN) inside In-vehicle communication protocol and a few potentials that could take due advantage of it. Moreover, this paper presents a few security measures proposed in the present examination status to defeat the attacks. In any case, the fundamental objective of this paper is to feature a comprehensive methodology known as Intrusion Detection System (IDS), which has been a significant device in getting network data in systems over many years. To the best of our insight, there is no recorded writing on a through outline of IDS execution explicitly in the CAN transport network system.
Standard

Requirements for a COTS Assembly Management Plan

2020-08-03
CURRENT
EIA933C
This document applies to the development of Plans for integrating and managing COTS assemblies in electronic equipment and Systems for the commercial, military, and space markets; as well as other ADHP markets that wish to use this document. For purposes of this document, COTS assemblies are viewed as electronic assemblies such as printed wiring assemblies, relays, disk drives, LCD matrices, VME circuit cards, servers, printers, laptop computers, etc. There are many ways to categorize COTS assemblies1, including the following spectrum: At one end of the spectrum are COTS assemblies whose design, internal parts2, materials, configuration control, traceability, reliability, and qualification methods are at least partially controlled, or influenced, by ADHP customers (either individually or collectively). An example at this end of the spectrum is a VME circuit card assembly.
Training / Education

Managing Energy Data: Advanced Analytics

Anytime
Introduction to Managing Energy Data: The Internet of Things (IoT) revolution (eg. the vast spread of smart meters worldwide) is generating massive amounts of energy data, drastically transforming the sector and current energy systems. This digital transformation gives rise to more intelligent ways of managing energy and brings about opportunities for energy companies to improve their business models and services. This course contains a brief introduction to the topics presented in the course, from smart meters and smart metering data to data science.
Standard

VENDOR COMPONENT PROGRAM DATA FILE INTERFACE FOR OEM ASSEMBLY OPERATIONS

1997-02-01
HISTORICAL
J2286_199702
This interface document SAE J2286 revises the requirements for file formats as described in SAE J1924. This document describes Interface 1 (I/F 1) in SAE J2214. This document does not imply the use of a specific hardware interface, but may be used with other hardware interfaces such as SAE J1939. The requirements of SAE J2286 supersede the requirements defined by SAE J1924.
Magazine

SAE Truck & Off-Highway Engineering: April 2018

2018-04-05
Connectivity takes center stage Telematic links have become the norm, helping fleet owners and operators improve efficiency and letting OEMs predict component failures. More power, less noise, fewer emissions These key attributes drive development of new generators both big and small. TARDEC pursues advanced power generation U.S. Army, GM collaborate on fuel-cell-generated electricity to power the vehicle's propulsion system and onboard electronics, while providing off-vehicle power via an Exportable Power Take-Off unit. Developing an alternative engine concept Ricardo's CryoPower engine leverages two unique combustion techniques for reduced emissions and fuel consumption-liquid nitrogen and split combustion. Long-haul trucking and stationary power generation will be the first beneficiaries of the technologies. Technology time-warp The road to autonomous driving has been under construction for decades, as showcased by SAE's Mobility History Committee at the 2018 WCX in Detroit.
Article

Software needs security, and security needs software: a scientific overview

2019-04-22
Software needs security. That's a consequence of using software to control critical systems. It's difficult because software is inherently a complex artifact, even when the code just consists of a single sequential program in a single programming language, with well-defined inputs and outputs. Of course, actual software rarely if ever has such a simple structure. Security needs software. That's a consequence of the complexity just mentioned. No process can ensure security at scale unless it is automated by using software itself: programming languages, verification tools, software platforms.
X