ISO/TS 22240:2008

Road vehicles - Vehicles safety information model (VSIM)

ISO/TS 22240:2008 presents an enhanced data exchange and data storage format for all data relevant for vehicle safety tests. The underlying data model is based on ASAM ODS, and the corresponding exchange format is XML.

Véhicules routiers — Modèle d'information pour la sécurité des véhicules (VSIM)

General Information

• Status: Published
• Publication Date: 21-Apr-2008
• ICS: 43.040.80 - Crash protection and restraint systems
• Technical Committee: ISO/TC 22/SC 36 - Safety and impact testing
• Drafting Committee: ISO/TC 22/SC 36/WG 3 - Instrumentation
• Current Stage: 9060 - Close of review
• Completion Date: 04-Mar-2029

Overview

ISO/TS 22240:2008 - Road vehicles: Vehicles safety information model (VSIM) defines a standard data model, storage approach and exchange format for all data relevant to vehicle safety tests. VSIM builds on the ASAM ODS base model for database storage and uses XML (including ATF/XML influences) for file-based data exchange. The specification covers metadata, test definitions, measurement channels, and references to multimedia results (photos, movies, diagrams, reports).

Key topics

• Data model foundation
  • VSIM entities are derived from ASAM ODS base entities (Ao...). Core entities include VSIM, Safety_Test, Test_Object, Test_Component, Possible_Channel, channel, Physical_Unit, and Physical_Dimension.
• Exchange & storage formats
  • Primary exchange format: XML (compatible with ATF/XML and ISO-MME conventions). Storage supports both database (ASAM ODS) and file-system references for large media.
• Measurements & channels
  • Support for multidimensional channels, discrete values and calculated channels. Channels use ISO-MME location codes (composed of Test_Object, Position, Main_Loc, Fine_Loc, Dimension, Direction, Filter Class).
  • Attributes such as default_filter_type and grouping (Possible_Channel_Group) help standardize signal handling.
• Results & multimedia
  • Entities for photo, movie, diagram, report, and Image_History reference externally stored files while preserving descriptive metadata per ISO-MME.
• Units and dimensions
  • Physical units and SI-based physical dimensions (exponents for length, mass, time, etc.) are represented using ASAM ODS entities.
• Test metadata
  • Structured definitions for Type_Of_Test, Subtype_Of_Test, contact and requirement to capture administrative and legal/test-procedure context.

Applications

• Vehicle manufacturers (OEMs): standardize crash-test and active-safety test data across departments and suppliers.
• Test laboratories and certification bodies: exchange, archive and reproduce test datasets reliably for audits and regulatory submissions.
• Software/tool vendors: implement ASAM ODS-compliant repositories and XML import/export (VSIM) for data management, visualization and analysis tools.
• Researchers & integrators: combine sensor channels, video, and reports into consistent datasets for analysis, simulation feeding or long-term archiving.

Benefits include improved interoperability, long-term accessibility of safety data, and consistent channel naming using ISO-MME codes.

Related standards

• ISO/TS 13499 - Multimedia data exchange format for impact tests (ISO‑MME)
• ISO/PAS 22720 - ASAM Open Data Services (ASAM ODS) 5.0

Keywords: ISO/TS 22240:2008, VSIM, vehicle safety information model, ASAM ODS, XML, vehicle safety tests, ISO‑MME, channel code, test data exchange.

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 22240
First edition
2008-05-01
Road vehicles — Vehicles safety
information model (VSIM)
Véhicules routiers — Modèle d'information pour la sécurité des
véhicules (VSIM)
Reference number
©
ISO 2008
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2008
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2008 – All rights reserved

Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Normative references. 1
3 Terms and definitions. 1
3.1 Tests. 1
3.2 Measurements. 3
3.3 Results. 4
4 Application model. 5
4.1 General. 5
4.2 VSIM Overview. 5
4.3 Test definition . 8
4.4 Measurement. 9
4.5 Results. 9
5 Related electronic documents. 10
Bibliography . 11

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of document:
⎯ an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
⎯ an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 22240 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 12,
Passive safety crash protection systems.
iv © ISO 2008 – All rights reserved

Introduction
The vehicle safety information model (VSIM) provides a standard model for the filing and exchange of vehicle
safety test data.
Figure 1 shows the many forms of data that can be exchanged from vehicle safety testing. VSIM offers a
flexible structure for the filing and exchange of data.

Figure 1 — Forms of data exchange
VSIM serves the already existing ASAM ODS (Association for Standardization of Automation and Measuring
Systems Open Data Services) mechanisms. This provides the advantage that the data are available both in a
database and a file system. In addition, the data can be exchanged in XML (eXtensible Markup Language)
format.
ASAM ODS offers suitable structures for the filing of measurement data. As a result, multidimensional
channels and discrete values can be continuously saved.
ASAM ODS offers one model for storing the data either in file or in database, and this method guarantees
access to data even after a long period of time.
ASAM ODS is described in ISO/PAS 22720.
VSIM data exchange was developed from the following standards:
⎯ ISO-MME (Multimedia exchange) (see ISO/TS 13499),
⎯ ASAM ATF (ASAM Transport Format), and
⎯ XML (ATF also available as ATF/XML).

TECHNICAL SPECIFICATION ISO/TS 22240:2008(E)

Road vehicles — Vehicles safety information model (VSIM)
1 Scope
This Technical Specification presents an enhanced data exchange and data storage format for all data
relevant for vehicle safety tests.
The underlying data model is based on ASAM ODS, and the corresponding exchange format is XML.
NOTE 1 Related electronic documents are available on the ISO website.
NOTE 2 The entities defined in Clause 3 are parts of the VSIM data model and are used in Figures 3 to 7.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/TS 13499, Road vehicles — Multimedia data exchange format for impact tests
ISO/PAS 22720, ASAM Open Data Services 5.0
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1 Tests
3.1.1
vehicle safety information model
VSIM
root of the whole data model
NOTE The entity describes the environment of the VSIM data model and holds the ISO-MME and ASAM ODS
version numbers of the application model for vehicle safety.
3.1.2
Type_Of_Test
root entity of the administration of the Safety_Test, which stores a possible test type list
NOTE 1 It is advisable that the value of “Type_Of_Test” be part of a possible type list, as is the case in the existing
vehicle safety analysis model defined by the German workgroup “Messdatenverarbeitung Fahrzeugsicherheit” (data
processing for vehicle safety).
NOTE 2 The values of the Type_Of_Test are not standardized and depend on the customized definition.
3.1.3
Subtype_Of_Test
specific type of test which makes it possible to enter the crash side or the legal codes of practice
NOTE The values of Subtype_Of_Test are not standardized.
3.1.4
Safety_Test
any kind of test performed in vehicle safety
EXAMPLE Crash test, sled test, component test, active safety test, biomechanical test.
3.1.5
contact
object that summarizes the contact information used for customer and laboratory contact for a safety test
NOTE A contact always refers to a person. This is identified with their email address.
3.1.6
Contact_Relation_Type
information that indicates what association the contact has to the Safety_Test.
NOTE The type could be customer, laboratory or “authorized”. It belongs to the ASAM ODS base entity AoAny.
3.1.7
Test_Object
group of components with the same initial state (e.g. speed, direction of movement) at impact time
EXAMPLE Vehicles, barriers, pedestrian dummies.
3.1.8
Possible_Component
list of possible component types (e.g. door, airbag) that can be used in a test
3.1.9
Possible_Component_Attribute
list of attributes belonging to the possible components
3.1.10
Value_List
allowed values for a Possible_Component_Attribute (e.g. “left”, “right”)
NOTE The same list can be used for several attributes.
3.1.11
value
element used to hold values which are grouped by an instance of Value_List
NOTE An example for such groups is the content of selections lists, e.g. of “Position”.
3.1.12
Test_Component
entity that contains the attributes of a component being tested
NOTE 1 The test object consists of one or more test components. For example, the door, B-pillar, airbag module and
dummies are components of a vehicle safety test object.
NOTE 2 Test_Component is taken out of the Possible_Test_Components.
2 © ISO 2008 – All rights reserved

3.1.13
Test_Component_Attribute
entity that contains one attribute per instance of a component being tested
EXAMPLE The time to fire of airbags or type of dummy.
3.1.14
requirement
legal or customer specific requirement for the test procedure,which is related to “Safety_Test”
3.2 Measurements
3.2.1
channel
entity that describes the measured quantity within a measurement
NOTE If the measurement type is a signal measurement or a calculated channel, the name of the quantity is
generated from the ISO-MME location
...