SAE J2546
SAE J2546 2002-FEB-01 Model Specfcaton Process Standard
The modeling requirements listed in this document provide guidelines for specifying:
Analysis requirements
Computer-Aided Engineering (CAE) simulator
Model fidelity
System assumptions
Model architecture
Validation requirements
Deliverables
for electrical/electronic components and the integral interfacing systems (mechanical, thermal, hydraulic) associated with these components.
The simulation models are primarily intended to facilitate functional specification and operational evaluation between component and system manufacturers, and are not intended to otherwise constrain or restrict the use of CAE simulation tools for automotive design, analysis and validation.
Background - The advances in computer technology since the 1970's have enabled the development of powerful CAE tools. These tools are being increasingly applied to the highly competitive automotive industry for the development of new components and systems. CAE tools allow companies to reduce the number of prototype phases and are considered key enablers in their product development process to produce designs in less time, with higher quality and lower costs.
However, over the years many custom tools have been developed with specific modeling and analysis objectives. Today, suppliers are asked more and more to deliver component models that satisfy different sets of objectives. This leads to the development of numerous simulator specific models of the same basic component. When component models are developed with different objectives and with unspecified degrees of fidelity, it is difficult to capture component interactions that allow system trade-off investigations and thus, system design optimization.
With the need to produce more cost-effective designs, the automotive industry is ready for the development of the Model Specification Process Standard.
Purpose - The Model Specification Process Standard is intended to define a common set of standards in defining model requirements for automotive electrical/electronic and mechatronic components. These requirements include functional specifications, their intended applications and the deliverables.
Model Development - This standard provides a guide for writing a simulation model specification by the end user, known as the Requester, and is detailed in the Model Specification Process shown in Figure 1.
The general process steps are:
a. The Requester requires a component model to perform system simulations and submits the component specification based on this standard to the component supplier, known as the Producer.
b. The Producer receives the model specification and, possessing detailed knowledge of their component, develops a specific component model. This model can be developed from the ground up or it can be developed from generic component models that are assembled to provide the proper performance. These generic component models can be developed by the CAE simulator supplier or by other component manufacturers.
c. The Producer validates the specific model against the Model Specification and delivers the model to the Requester.
d. The Requester receives the requested model and performs the necessary system simulations.
This process has the benefits of having a common vocabulary and standard interpretation of what is being requested and what will be delivered. Essentially, this Standard improves the communication between the system integrators and the component manufacturers in the automotive industry and will enable the development of automotive systems that represent high customer value.
This document will focus on developing the model requirement guidelines (highlighted oval in Figure 1) and this will allow the development of the SAE Commodity Model Standards.
Application - This standard provides a guide for the development of model request specifications on a commodity-by-commodity basis. Each request specification describes the fundamentals of commodity behavior and contains a general "request form." This request form in turn contains pre-defined checklist table entries for feature/level options as well as placeholders for free-form text descriptions, graphics and other request-dependent information. A model Requester can then fill out a "blank" form for a given commodity to specify the level of detail and desired functionality that is expected for a generic model of a particular device. A model Requester can also request characterization of an existing generic model to make a model of a specific component or part number.
Customers who purchased SAE J2546