SAE J3049_202505

The “Model Architecture and Interfaces Recommended Practice for Ground Vehicle System and Subsystem Dynamical Simulation” defines the architectural structure of a ground vehicle system dynamical model by partitioning it into subsystem models and by defining subsystem interfaces required to enable plug-and-play operation of a dynamical simulation models. All types of ground vehicle were considered in the development of the architecture, such as, passenger cars, light and medium duty trucks, heavy duty tractor trailer trucks, and vehicles/equipment for military, farming, construction, and mining. Versatility of this architectural partitioning is demonstrated by showing how it can be applied to different vehicle configurations. Application examples of architecture are provided for a large number of the publicly known ground vehicle configurations in production, testing, or development. This recommended practice encompasses standards to enable seamless plug-and-play reusability of dynamical models for simulating the functional behavior of a ground vehicle system and its subsystems. A single ground vehicle system is the system of interest. The architecture and interfaces support vehicle models that describe vehicle motion in one dimension (longitudinal), two dimensions (longitudinal and lateral or longitudinal and vertical), and three dimensions (longitudinal, lateral, and vertical). The scope includes defining recommended practices for: 1 Model architectural structure, and interfaces that enable the plug-and-play development of: (1) a top-level ground vehicle system model from subsystem models, and (2) subsystem models from other subsystem models; and 2 Model architecture and interfaces for all hardware and controller interfaces; however, the internal structure of control algorithms and software will not be included in this recommended practice. Since, other groups (such as, AUTOSAR) are addressing architecture and interfaces of models for control applications and software; they are not included in the scope of the recommended practice. However, in the future, the internal structure of control algorithms and software should be addressed for special issues of dynamical modeling and simulation of ground vehicle systems that are not covered by other standards groups. Increasingly, global vehicle engineering teams span domains of engineering and physics within organizations and include external collaborations between commercial businesses (original equipment manufacturers (OEMs), and suppliers), government agencies, and research institutions. For increased efficiency, reduced costs, faster design iterations, and fewer hardware prototypes, these teams use math-based engineering methods to build and test virtual ground vehicles in simulation environments. These types of inter-organizational engineering collaborations require a common shared simulation model for an entire ground vehicle system and/or the related subsystems of which it is composed. Use of dynamical modeling and simulation for virtual engineering development and testing of the functional performance of ground vehicles by inter-organizational teams has increased and resulted in a need for standardizing the architecture and interfaces of a ground vehicle system model by partitioning it into subsystem models to enable plug-and-play of subsystem simulation models. A standardized ground vehicle system model with an architectural structure partitioned into subsystem models, and with defined subsystem model interfaces enables: (1) model reuse, (2) division of modeling tasks across multifunctional teams, (3) parallel model development, verification and validation, and (4) rapid and efficient integration of subsystem models for reduced development time and costs. The recommended practice for model architecture and interfaces will: (1) create a common language, (2) increase productivity of processes, (3) promote uniform testing, (4) permit common interfaces, and (5) reduce costs. SAE J3049 has been reaffirmed to comply with the SAE Five-Year Review policy.

Please request information about the document. Contact Page