1、DRAFT FOR DEVELOPMENTDD ISO/TS 22240:2008Road vehicles Vehicles safety information model (VSIM)ICS 43.040.80g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g
2、47g36g58DD ISO/TS 22240:2008This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 BSI 2008ISBN 978 0 580 57492 4National forewordThis Draft for Development is the UK implementation of ISO/TS 22240:2008. This publication is not to
3、be regarded as a British Standard.It is being issued in the Draft for Development series of publications and is of a provisional nature. It should be applied on this provisional basis, so that information and experience of its practical application can be obtained.Comments arising from the use of th
4、is Draft for Development are requested so that UK experience can be reported to the international organization responsible for its conversion to an international standard. A review of this publication will be initiated not later than three years after its publication by the international organizatio
5、n so that a decision can be taken on its status. Notification of the start of the review period will be made in an announcement in the appropriate issue of Update Standards.According to the replies received by the end of the review period, the responsible BSI Committee will decide whether to support
6、 the conversion into an international Standard, to extend the life of the Technical Specification or to withdraw it. Comments should be sent to the Secretary of the responsible BSI Technical Committee at British Standards House, 389 Chiswick High Road, London W4 4AL.The UK participation in its prepa
7、ration was entrusted to Technical Committee AUE/7, Automobile occupant restraint systems.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible fo
8、r its correct application.Amendments/corrigenda issued since publicationDate CommentsReference numberISO/TS 22240:2008(E)TECHNICAL SPECIFICATION ISO/TS22240First edition2008-05-01Road vehicles Vehicles safety information model (VSIM) Vhicules routiers Modle dinformation pour la scurit des vhicules (
9、VSIM) DD ISO/TS 22240:2008ii iiiContents 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
10、 . 9 5 Related electronic documents. 10 Bibliography . 11 DD ISO/TS 22240:2008iv 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
11、 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 collaborate
12、s 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
13、. 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 req
14、uirement 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 mem
15、bers 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 th
16、ree 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 S
17、tandard 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, S
18、ubcommittee SC 12, Passive safety crash protection systems. DD ISO/TS 22240:2008vIntroduction 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
19、 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
20、 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 o
21、ffers 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), ASA
22、M ATF (ASAM Transport Format), and XML (ATF also available as ATF/XML). DD ISO/TS 22240:2008blank1Road 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
23、 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 followi
24、ng 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
25、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 d
26、ata 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
27、 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. DD ISO/TS 22240:200
28、82 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
29、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
30、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,
31、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”, “r
32、ight”) 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
33、 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. DD ISO/TS 22240:200833.1.13 Test_Comp
34、onent_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 t
35、hat 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 code. 3.2.2 VSTD_Interface entity that describes a vehicle safety test definition (VSTD) interface 3.
36、2.3 Physical_Unit entity that describes the physical unit NOTE The entity belongs to the ASAM ODS base entity AoUnit. 3.2.4 Physical_Dimension entity represented by the seven dimensional exponents of the SI base dimensions: length, mass, time, temperature, current, molar amount and light intensity N
37、OTE 1 The SI base dimensions are measured in the following SI base units: length (m), mass (kg), time (s), temperature (K), current (A), molar amount (Mol), light intensity (cd). NOTE 2 Many of the exponents are usually zero. In particular, the dimensionless units (e.g. “%”) all have exponents equal
38、 to zero. NOTE 3 Several physical dimensions can exist which have the same set of exponents. The entity belongs to the ASAM ODS base entity AoPhysicalDimension. 3.2.5 Possible_Channel entity that describes the possible channels NOTE For the possible channels, the application attribute “default_filte
39、r_type” describes a default filtering for measured channels. Possible_Channels are named by using channel codes (3.2.7). 3.2.6 Possible_Channel_Group groups used to build groups of channels that are related 3.2.7 channel code attribute of the application elements “channel” and “possible channel”, wh
40、ich contains the ISO-MME location code NOTE 1 This location code has several code elements which are concatenated to the location. Figure 2 shows the convention to compose the content of this attribute. DD ISO/TS 22240:20084 Figure 2 ISO-MME location code NOTE 2 ISO-MME also defines the values of co
41、de elements and describes them. There are entities defined in the VSIM application model for retaining this code element information. Their entity names are “Test_Object_Code”, “Position_Code”, “Main_Loc_Code”, “Fine_Loc_1_Code”, “Fine_Loc_2_Code”, “Fine_Loc_3_Code”, “Direction_Code”, “Filter_Cls_Co
42、de” and “Dimension_Code”. The entity “Test_Object_Code” belongs to the ASAM ODS base entity AoUnitUnderTest. The other entities belongs to the ASAM ODS base entity AoAny (see Table 1). Table 1 Relationship between ISO code and entity name ISO Code Entity name Test Object Test_Object_Code Position Po
43、sition_Code Transducer Main Location Main_Loc_Code Fine Location 1 Fine_Loc_1_Code Fine Location 2 Fine_Loc_2_Code Fine Location 3 Fine_Loc_3_Code Dimension Dimension_Code Direction Direction_Code Filter Class Filter_Cls_Code NOTE 3 In channel codes, question marks (“?”) are used as placeholders, ea
44、ch for one DT_STRING character. These are replaced by valid combinations (see the related electronic documents). 3.3 Results 3.3.1 photo entity that describes the photos of the test NOTE 1 All pictures created during the test are organized in this entity. NOTE 2 The photos are stored in the file sys
45、tem. The application model contains external references to the photo files and some descriptive attributes as they are given in the ISO-MME format. The photos have a relation to “Test_Object” and/or “Safety_Test”. DD ISO/TS 22240:200853.3.2 movie entity that describes movies of the test NOTE 1 All m
46、ovies created during the test are organized in this entity. NOTE 2 The movies are stored in the file system. The application model contains external references to the movie files and some descriptive attributes as they are given in the ISO-MME format. The movies have a relation to “Safety_Test” and/
47、or “Test_Object”. 3.3.3 Correction_Parameter entity that contains additional information for movie analysis 3.3.4 Image_History entity that describes the history of the images NOTE The history of the images is a short description of the processes done by the imaging processing tools on the related i
48、mage. The history of the image is logged in the instances of this entity. 3.3.5 diagram entity that describes the attributes of a test diagram, such as the location where the diagram is stored and the channels used in the diagram, a simplified and structured visual representation of test data NOTE T
49、est diagrams are stored in the file system. The application model contains external references to the diagram files. The diagrams are related to “Safety_Test”. 3.3.6 report entity that describes the attributes of a test report, such as the location where the report is stored and the version of the report, a textual representation of the result of the test data NOTE Test reports are stored in the file system. The application model contains external references to the report files. The reports are related to “Safety_Test”. 4 Application model 4.1 General The appli
