Road vehicles -- Product data exchange between chassis and bodywork manufacturers (BEP)

ISO/TS 21308-4:2007 describes the mapping to STEP application protocol 239 for the exchange of dimensional data between truck chassis manufacturers and bodywork manufacturers. It applies to commercial vehicles, as defined in ISO 3833, which have a maximum gross vehicle mass greater than 3 500 kg. The process of exchanging the above information can involve the chassis manufacturer, the chassis importer, the chassis dealer, one or more bodywork manufacturers, and bodywork component suppliers, e.g. manufacturers of demountable bodies, cranes and loading equipment, tipping equipment.

Véhicules routiers -- Échange de données de produit entre les fabricants de châssis et de carrosseries (BEP)

General Information

Status
Published
Publication Date
25-Nov-2007
Current Stage
9020 - International Standard under periodical review
Start Date
15-Oct-2021
Ref Project

Buy Standard

Technical specification
ISO/TS 21308-4:2007 - Road vehicles -- Product data exchange between chassis and bodywork manufacturers (BEP)
English language
32 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

TECHNICAL ISO/TS
SPECIFICATION 21308-4
First edition
2007-12-01
Road vehicles — Product data exchange
between chassis and bodywork
manufacturers (BEP) —
Part 4:
Mapping to STEP application
protocol 239
Véhicules routiers — Échange de données de produit entre les
fabricants de châssis et de carrosseries (BEP) —
Partie 4: Élaboration en accord avec le protocole d'application 239
de STEP
Reference number
ISO/TS 21308-4:2007(E)
ISO 2007
---------------------- Page: 1 ----------------------
ISO/TS 21308-4:2007(E)
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.

COPYRIGHT PROTECTED DOCUMENT
© ISO 2007

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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2007 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 21308-4:2007(E)
Contents Page

Foreword............................................................................................................................................................ iv

Introduction ........................................................................................................................................................ v

0.1 General................................................................................................................................................... v

0.2 Intentions of this Technical Specification.......................................................................................... v

0.3 Relationship with STEP........................................................................................................................ v

1 Scope ..................................................................................................................................................... 1

2 Normative references ........................................................................................................................... 1

3 Terms and definitions........................................................................................................................... 2

4 Abbreviated terms ................................................................................................................................ 2

5 Overview ................................................................................................................................................ 3

5.1 General................................................................................................................................................... 3

5.2 Mapping techniques and instantiation diagrams .............................................................................. 4

6 Exchange specification........................................................................................................................ 4

6.1 General................................................................................................................................................... 4

6.2 Data exchange sets and capabilities .................................................................................................. 6

6.3 Type and individual data...................................................................................................................... 7

6.4 External_class_library.......................................................................................................................... 7

6.5 Attributes ............................................................................................................................................... 7

6.6 Partitioning of mapping examples...................................................................................................... 8

7 Instantiation diagrams and related part files ..................................................................................... 8

7.1 Part/type root......................................................................................................................................... 8

7.2 Classification of part .......................................................................................................................... 10

7.3 Individual root ..................................................................................................................................... 11

7.4 Classification of individual root ........................................................................................................ 12

7.5 Type properties ................................................................................................................................... 13

7.6 Individual properties........................................................................................................................... 14

7.7 Organization information ................................................................................................................... 15

7.8 Project information – Example 1 ....................................................................................................... 16

7.9 Project information – Example 2 ....................................................................................................... 17

7.10 Purchase order information............................................................................................................... 18

7.11 Delivery information ........................................................................................................................... 19

7.12 Legal reference ................................................................................................................................... 20

Annex A (informative) STEP information background ................................................................................. 22

Annex B (informative) Complete Part 21 text file (with data taken from earlier examples) ...................... 23

Annex C (informative) Complete Part 28 OSEB XML file (with data taken from earlier examples).......... 26

Bibliography ..................................................................................................................................................... 32

© ISO 2007 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/TS 21308-4:2007(E)
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 21308-4 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 6,

Terms and definitions of dimensions and masses.

ISO/TS 21308 consists of the following parts, under the general title Road vehicles — Product data exchange

between chassis and bodywork manufacturers (BEP):
⎯ Part 1: General principles [Publicly Available Specification]
⎯ Part 2: Dimensional bodywork exchange parameters
⎯ Part 3: General, mass and administrative exchange parameters
⎯ Part 4: Mapping to STEP application protocol 239 [Technical Specification]
iv © ISO 2007 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 21308-4:2007(E)
Introduction
0.1 General

Truck chassis manufacturers deal with the configuration of chassis in infinite numbers of possible

combinations, and bodywork manufacturers produce highly customized superstructures on these chassis.

Bodywork manufacturers build their superstructures on chassis of several different truck brands.

The production efficiency of a specific truck chassis and its body combinations can be greatly improved by

ensuring that the correct technical and commercial information about the specific chassis is communicated

with the bodywork manufacturer in advance. The information needs to be reliable such that the bodywork

manufacturer has sufficient confidence to prefabricate the body or the superstructure before the chassis is

delivered. With uniform conditions, unambiguous dimensions and supplementary information can be

established, transferred and correctly interpreted by the receiver. Increased information efficiency improves

quality and reduces lead times.

The ISO 21308 series specifies a system of codes to exchange specific data between chassis and bodywork

manufacturers, providing a platform for efficient communication between the parties. The process of

exchanging data according to the ISO 21308 series is not dependent on the degree of IT sophistication. Any

medium can be used, from fax or e-mail to a STEP (standard for the exchange of product model data)

protocol.

Exchanging codes in accordance with the ISO 21308 series is useful in various situations, e.g. for design and

manufacturing, technical specifications, technical drawings and leaflets.

The codes provide the basic information level, and are also the basic input parameters for a data exchange

system based on the STEP protocol. This Technical Specification covers the mapping of these data to STEP

application protocol 239 (STEP AP 239).
0.2 Intentions of this Technical Specification

This Technical Specification is aimed at those parties interested in using STEP for their transmission of

product data. STEP can be implemented in different ways when used for the exchange of BEP (bodywork

exchange parameter) data. The intention with this Technical Specification is to create a basis for compatible

STEP applications when used for exchanging BEP data. In order to achieve this, it is necessary to map the

BEP properties to the STEP application in a uniform way. This Technical Specification specifies the general

principles of this mapping and shows examples of mapping of specific properties, as well as a complete STEP

file for the transmission of data.

This Technical Specification is intended for use by implementation and software design experts with in-depth

knowledge of the ISO 10303 series on STEP product data. Special knowledge of object-oriented syntaxes and

the data descriptive language of STEP, EXPRESS and EXPRESS-G (the graphical notation) is necessary for

the understanding and assimilation of this Technical Specification.
0.3 Relationship with STEP

The product data model schema of main interest is the ARM (application reference model) contained in STEP

application protocol 239 (ISO 10303-239), published in 2005.

In addition, complementary standards and documentation are developed within OASIS (a part of W3C) to

further assist in a successful usage and implementation of STEP AP 239 based solutions, referred to as data

exchange sets (DEXs).
© ISO 2007 – All rights reserved v
---------------------- Page: 5 ----------------------
TECHNICAL SPECIFICATION ISO/TS 21308-4:2007(E)
Road vehicles — Product data exchange between chassis
and bodywork manufacturers (BEP) —
Part 4:
Mapping to STEP application protocol 239
1 Scope

This Technical Specification describes the mapping to STEP application protocol 239 for the exchange of

dimensional data between truck chassis manufacturers and bodywork manufacturers. It applies to commercial

vehicles, as defined in ISO 3833, which have a maximum gross vehicle mass greater than 3 500 kg.

The process of exchanging the above information can involve
⎯ the chassis manufacturer,
⎯ the chassis importer,
⎯ the chassis dealer,
⎯ one or more bodywork manufacturers, and

⎯ bodywork component suppliers, e.g. manufacturers of demountable bodies, cranes and loading

equipment, tipping equipment.
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 10303-11, Industrial automation systems and integration — Product data representation and exchange —

Part 11: Description methods: The EXPRESS language reference manual

ISO 10303-239, Industrial automation systems and integration — Product data representation and

exchange — Part 239: Application protocol: Product life cycle support

ISO 21308-2, Road vehicles — Product data exchange between chassis and bodywork manufacturers

(BEP) — Part 2: Dimensional bodywork exchange parameters

ISO 21308-3, Road vehicles — Product data exchange between chassis and bodywork manufacturers

(BEP) — Part 3: General, mass and administrative exchange parameters
© ISO 2007 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/TS 21308-4:2007(E)
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 10303-239, ISO 10303-11 and the

following apply.
3.1
product type
type
typical (generic) description of a product
NOTE Types are usually described by part definitions.
3.2
product individual
individual
individual with given characteristics specified from the type description

NOTE Individuals are typically defined by a specific combination (configuration) of parts and components.

3.3
STEP file
data file
import file

file package containing the truck descriptive data in accordance with ISO 10303-239 and this Technical

Specification
3.4
Reference Data Library
RDL

mechanism to allow dynamic semantic interpretation of data content in a STEP file at run-time

3.5
instance
individual object of a certain entity or class
4 Abbreviated terms
BEP Bodywork Exchange Parameter
DEX Data Exchange Set
OASIS Organisation for the Advancement of Structured Information Standards
PLCS Product Life Cycle Support
STEP STandard for the Exchange of Product model data
URN Uniform Resource Name
2 © ISO 2007 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/TS 21308-4:2007(E)
5 Overview
5.1 General

Figure 1 illustrates the information exchange model and scope of this Technical Specification.

Figure 1 — Information exchange model and scope of this Technical Specification

Clauses 6 and 7 specify how exchange parameters defined in ISO 21308-2 and ISO 21308-3 should be

mapped against STEP AP 239.

NOTE 1 In this Technical Specification, the term “STEP” refers to the STEP AP 239 model.

Table 2 identifies how the information entities defined in the Information Content document are generally

mapped against the corresponding STEP AP 239 entity.

Subclauses 7.1 to 7.12 include an instantiation example diagram with explanatory text, where applicable.

NOTE 2 In case of doubt, it is advisable always to refer to the STEP AP 239 documentation and the corresponding

DEX capabilities documentation.

The instantiation example diagrams show EXPRESS-G instantiation charts providing an overview of how a

cluster of data should be instantiated and grouped.
Compulsory relationships may or may not be shown, if relevant in the context.

Optional attribute values are typically omitted, e.g. with description attributes that are usually optional and of a

descriptive nature (in comparison with data that has a defined semantic meaning in the STEP standard, e.g.

the name of a product class).
© ISO 2007 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/TS 21308-4:2007(E)

The STEP standard has many file representation formats (of the same data), the most common being a

binding called “Part 21” (ISO 10303-21), which is a plain text file format. XML (Extensible Markup Language)

is also available, referred to as "Part 28" (ISO 10303-28).

NOTE 3 Examples using Part 21 and Part 28 are used in this Technical Specification. Annex B summarizes the

examples given in this Technical Specification as a complete Part 21 text file. Annex C summarizes in the same way the

examples as a complete Part 28 XML file.

For complete scheme definitions and descriptions, the ISO 10303-239 documentation should be consulted.

5.2 Mapping techniques and instantiation diagrams

This Technical Specification relies heavily on instantiation diagrams to portray how the BEP data (and

additional truck chassis data) is carried in the STEP file. All examples are DEX compliant as far as possible.

The model and instantiation diagrams used are in accordance with ISO 10303-11, STEP EXPRESS-G (see

Figure 2).

Figure 2 — Explanation of instantiation diagrams used in this Technical Specification

6 Exchange specification
6.1 General

The exchange data package consists of a core STEP file designated PRODUCT_DATA_239. All relevant

information about structure, identification data and technical data information is contained here. From here,

other information entities, such as external geometry documents or drawings, are referenced. See Figure 3.

4 © ISO 2007 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/TS 21308-4:2007(E)
Figure 3 — Overview of STEP AP 239 data package and formats

Table 1 provides an overview of the information package physical structure and content.

Figure 4 provides an overview of the logical structure.
Table 1 — Overview of the information package physical structure
Information package envelope directory Content overview Format Optional
Purchase order or offer information
Logistics information
Chassis technical data, preferably using
Chassis identity number
BEP codes defined in ISO 21308-2 and STEP AP 239 No
Chassis structure (optional)
ISO 21308-3
Technical data
References to other information items
Two-dimensional drawing of chassis
b c

Chassis individual drawing individual (alternatively chassis family PDF, DXF Yes

type)
STEP AP214
Three-dimensional geometry of the
cc1/2 AIM ,
individual chassis, either complete
Chassis three-dimensional mock-up data Yes
STEP AP203 ,
chassis or per component
f c
STL
Document of interest to the truck body-
Other documentation of relevance MS Word, PDF Yes
builder, e.g. mounting instructions
There are optional data entities and structures within the STEP data.
PDF = Portable Document Format; DXF = Data Exchange Format.
Or any other format agreed on bilaterally.
AIM = Application Interpreted Model; see ISO 10303-214.
See ISO 10303-203.
STL = Standard Template Library.
© ISO 2007 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/TS 21308-4:2007(E)
Figure 4 — Overview of logical build-up of STEP data structure
6.2 Data exchange sets and capabilities

Data exchange sets (DEXs) are OASIS standards that identify a subset of STEP AP 239 PLCS to be used to

support a particular business process. Capabilities are the building blocks for DEXs. The following capabilities

have been used when developing this Technical Specification:
⎯ Capability (C001): assigning_identifiers
⎯ Capability (C002): representing_parts
⎯ Capability (C005): representing_documents
⎯ Capability (C010): assigning_reference_data
⎯ Capability (C010): assigning_reference_data
⎯ Capability (C016): representing_person_organization
6 © ISO 2007 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/TS 21308-4:2007(E)
⎯ Capability (C036): assigning_date_time
⎯ Capability (C045): representing_product_as_individual
⎯ Capability (C060): referencing_product_as_individual
⎯ Capability (C079): representing_properties_numerically
⎯ Capability (C080): representing_properties_textually
6.3 Type and individual data

In STEP AP 239, both a type of truck and a specific individual (planned or already produced) can be

represented. Properties, represented by the “BEP codes” can be attached (associated) with both kinds of

representation, and from the perspective of the recipients there should not be any difference.

Certain properties should however always be associated with the truck individual.

A data transfer file should always contain data for at least one individual vehicle.

6.4 External_class_library

External_class_library is a central part of STEP AP 239. It is used to reference external libraries for data

definition.

This allows for dynamic configuration and a continued life-cycle for the definitions of BEP codes and other

data references. External class libraries are identified by a name that uniquely specifies the library, typically a

uniform resource name (URN) or similar.

NOTE In this Technical Specification, the following (fictitious) external libraries are used:

⎯ “urn:iso:std:iso:21308” and “urn:iso:std:iso:10303-239” are used as library references;

⎯ “urn:iso:std:iso:21308” corresponds to the URN of the BEP codes (name and description for the BEP codes);

⎯ “urn:iso:std:iso:10303-239” corresponds to the URN of the PLCS reference data (information about classes and

usage of STEP AP 239 PLCS).
6.5 Attributes

In STEP AP 239, the attributes are seldom used to represent any information. Instead,

identification_assignment and classification_assignment are used in accordance with the usage guidelines

developed within OASIS. To avoid data inconsistency, the rules below are used in this Technical Specification.

a) Mandatory attributes:

⎯ /IGNORE means value represented in another way, i.e. through identification_assignment and

classification_assignment;
⎯ “ ”(empty string) means not used.
b) Optional attributes:

⎯ /IGNORE means value represented in another way, i.e. through identification_assignment and

classification_assignment;
⎯ $ means not used.
© ISO 2007 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/TS 21308-4:2007(E)
6.6 Partitioning of mapping examples

Table 2 shows where to find the mapping of related BEP codes in this Technical Specification.

L, H, and W codes refer to ISO 21308-2. G, M, and A codes refer to ISO 21308-3.
Table 2 — Mapping of BEP codes
BEP code STEP AP 239 PLCS entity Subclauses in this Technical Specification
BEP-L001 - BEP-L106
BEP-H001 - BEP-H104
7.5 Type properties
BEP-W001 - BEP-W102 Assigned_property
7.6 Individual properties
BEP-G001 - BEP-G150
BEP-M001 - BEP-M120
BEP-A001 - BEP-A003 Organization 7.7 Organization information
BEP-A010, BEP-A011,
Project 7.8 – 7.9 Project information 1 & 2
BEP-A032 - BEP-A034
BEP-A020, BEP-A030,
Contract 7.10 Purchase order information
BEP-A031
BEP-A021, BEP-A051 Calendar_date 7.11 Delivery information
BEP-A040, BEP-A050 Identification_assignment 7.4 Individual root
BEP-A060, BEP-A070 Assigned_property 7.12 Legal reference
7 Instantiation diagrams and related part files
7.1 Part/type root
7.1.1 Part/type root instantiation diagram

The instantiation diagram in Figure 5 shows how a part, a part version and an associated view (mechanical

design/design) is represented in STEP AP 239, as well as how to identify a part (identification assignment).

The view mechanism allows for multiple filterable views of the product/truck information, e.g. mechanical vs.

electrical configuration.
8 © ISO 2007 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/TS 21308-4:2007(E)
Figure 5 — Part/type root instantiation diagram
7.1.2 Corresponding part of Part 21 text file
#1 = PART('/IGNORE','/IGNORE',$);
#2 = PART_VERSION('/IGNORE',$,#1);
#3 = PART_VIEW_DEFINITION('',$,$,#4,(),#2);
#4 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE',$);
#5 = IDENTIFICATION_ASSIGNMENT('123456','',$,(#1));
#6 = IDENTIFICATION_ASSIGNMENT('Truck 143','',$,(#1));
#7 = IDENTIFICATION_ASSIGNMENT('A','',$,(#2));
#8 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#9,'',(#5,#6,#7));
#9 = ORGANIZATION($,'/IGNORE');
#10 = IDENTIFICATION_ASSIGNMENT('ABC','',$,(#9));
7.1.3 Corresponding part of Part 28 OSEB XML file



ID1

ID1

ID2

© ISO 2007 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/TS 21308-4:2007(E)

ID5ID6ID7



ID9
7.2 Classification of part
7.2.1 Classification of part instantiation diagram

The instantiation diagram in Figure 6 shows how part name, identifiers and version identifiers are represented

in STEP AP 239. By using an external class reference data library (RDL), it is possible to verify at run-time

against the standard if naming and identification schemes are compliant. The RDL can be updated over time.

Figure 6 — Classification of part instantiation diagram
7.2.2 Corresponding part of Part 21 text file
#4 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE',$);
#5 = IDENTIFICATION_ASSIGNMENT('123456','',$,(#1));
#6 = IDENTIFICATION_ASSIGNMENT('Truck 143','',$,(#1));
#7 = IDENTIFICATION_ASSIGNMENT('A','',$,(#2));
#8 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#9,'',(#5,#6,#7));
#10 = IDENTIFICATION_ASSIGNMENT('ABC','',$,(#9));
#11 = CLASSIFICATION_ASSIGNMENT(#12,(#4),$);
#12 = EXTERNAL_CLASS('','Design',$,#13);
#13 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:10303-239',$);
10 © ISO 2007 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/TS 21308-4:2007(E)
#14 = CLASSIFICATION_ASSIGNMENT(#15,(#4),$);
#15 = EXTERNAL_CLASS('','Mechanical_design',$,#13);
#16 = CLASSIFICATION_ASSIGNMENT(#17,(#5),$);
#17 = EXTERNAL_CLASS('','Part_identification',$,#13);
#18 = CLASSIFICATION_ASSIGNMENT(#19,(#6),$);
#19 = EXTERNAL_CLASS('','Part_name',$,#13);
#20 = CLASSIFICATION_ASSIGNMENT(#21,(#7),$);
#21 = EXTERNAL_CLASS('','Version_identification',$,
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.