ISO/TS 21308-4:2007

Road vehicles - Product data exchange between chassis and bodywork manufacturers (BEP) - Part 4: Mapping to STEP application protocol 239

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) — Partie 4: Élaboration en accord avec le protocole d'application 239 de STEP

General Information

• Status: Published
• Publication Date: 25-Nov-2007
• ICS: 43.080.01 - Commercial vehicles in general
• Technical Committee: ISO/TC 22/SC 40 - Specific aspects for light and heavy commercial vehicles, busses and trailers
• Drafting Committee: ISO/TC 22/SC 40 - Specific aspects for light and heavy commercial vehicles, busses and trailers
• Current Stage: 9060 - Close of review
• Completion Date: 02-Sep-2028

Relations

• Consolidated By: ISO 10545-1:2014 - Ceramic tiles - Part 1: Sampling and basis for acceptance
• Effective Date: 06-Jun-2022

Overview

ISO/TS 21308-4:2007 - "Road vehicles - Product data exchange between chassis and bodywork manufacturers (BEP) - Part 4: Mapping to STEP application protocol 239" defines how Bodywork Exchange Parameter (BEP) data is mapped to the STEP Application Protocol 239 (ISO 10303-239). It covers the exchange of dimensional and related technical/administrative data for commercial vehicles (as per ISO 3833) with a maximum gross vehicle mass greater than 3 500 kg. The Technical Specification creates a consistent, DEX‑compliant approach for transferring chassis information between chassis manufacturers, importers, dealers, bodywork manufacturers and bodywork component suppliers.

Key Topics

• Mapping BEP to STEP AP 239: Specifies principles and examples for translating BEP properties (from ISO 21308-2 and ISO 21308-3) into the STEP AP 239 product data model (ARM).
• Type vs Individual data: Distinguishes product type (generic part definitions) and product individual (specific configurations) and explains their STEP instantiation.
• Instantiation diagrams & EXPRESS-G: Uses EXPRESS-G diagrams to show how clusters of BEP data should be instantiated in a STEP file for compatibility.
• File formats: Demonstrates both Part 21 (ISO 10303-21 plain text) and Part 28 (XML, ISO 10303-28) representations; complete file examples are provided in annexes.
• Data Exchange Sets (DEX) and RDL: Aligns with OASIS DEX practices and discusses Reference Data Libraries (RDL) for semantic interpretation at run-time.
• Implementation focus: Intended for software designers and implementers familiar with ISO 10303 (EXPRESS, PLCS) and object‑oriented data description techniques.

Applications

• Bodywork prefabrication: Enables bodywork manufacturers to prefabricate superstructures confidently before chassis delivery using unambiguous dimensional data.
• Multi‑supplier integration: Facilitates exchange among chassis makers, dealers, multiple body builders and component suppliers (demountables, cranes, tipping gear).
• Design & manufacturing data exchange: Supports technical specifications, drawings, configuration management and downstream PLM processes.
• System and software vendors: Guides developers of CAD/PLM, ERP and integration solutions to implement a compatible BEP → STEP AP 239 mapping.

Who Should Use It

• Chassis and bodywork manufacturers and their suppliers
• Systems integrators and software vendors implementing STEP AP 239 exchanges
• Technical teams responsible for CAD/PLM, data exchange, and configuration management
• Standards and compliance specialists in commercial vehicle product data

Related Standards

• ISO 10303-239 (STEP AP 239, Product Life Cycle Support)
• ISO 10303-11 (EXPRESS language)
• ISO 10303-21 (Part 21 file format) and ISO 10303-28 (Part 28 XML)
• ISO 21308-2 / ISO 21308-3 (BEP dimensional, mass and administrative parameters)
• ISO 3833 (vehicle classification)

Keywords: ISO/TS 21308-4:2007, STEP AP 239, BEP, product data exchange, chassis and bodywork manufacturers, EXPRESS-G, Part 21, Part 28, DEX, RDL.

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 2007
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 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 [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2007 – All rights reserved

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

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

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).
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
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

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).
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

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
a
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
d
cc1/2 AIM ,
individual chassis, either complete
Chassis three-dimensional mock-up data Yes
e
STEP AP203 ,
chassis or per component
f c
STL
Document of interest to the truck body-
c
Other documentation of relevance MS Word, PDF Yes
builder, e.g. mounting instructions
a
There are optional data entities and structures within the STEP data.
b
PDF = Portable Document Format; DXF = Data Exchange Format.
c
Or any other format agreed on bilaterally.
d
AIM = Application Interpreted Model; see ISO 10303-214.
e
See ISO 10303-203.
f
STL = Standard Template Library.
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

⎯ 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.
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

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

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

#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',$,#13);
#22 = CLASSIFICATION_ASSIGNMENT(#23,(#10),$);
#23 = EXTERNAL_CLASS('','Name',$,#13);
#24 = CLASSIFICATION_ASSIGNMENT(#25,(#8),$);
#25 = EXTERNAL_CLASS('','Owner_of',$,#13);
7.3 Individual root
7.3.1 Individual root instantiation diagram
The individual root is the purchase order/chassis numbered individual described in the STEP file. The
instantiation diagram in Figure 7 also shows how the individual is identified. By using this mapping of the data,
any STEP AP 239 PLCS compliant application should be able to read the basic vehicle information.

Figure 7 — Individual root instantiation diagram
7.3.2 Corresponding part of Part 21 text file
#1 = PART('/IGNORE','/IGNORE',$);
#2 = PART_VERSION('/IGNORE',$,#1);
#4 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE',$);
#26 = PRODUCT_AS_INDIVIDUAL('/IGNORE',$,$);
#27 = PRODUCT_AS_REALIZED('/IGNORE',$,#26);
#28 = PRODUCT_AS_INDIVIDUAL_VIEW('',$,$,#4,(),#27);
#29 = PRODUCT_DESIGN_TO_INDIVIDUAL(#1,#26);
#30 = PRODUCT_DESIGN_VERSION_TO_INDIVIDUAL(#2,#27);
#31 = IDENTIFICATION_ASSIGNMENT('1111:2222','',$,(#26));
#32 = IDENTIFICATION_ASSIGNMENT('3','',$,(#27));
7.4 Classification of individual root
7.4.1 Classification of individual root instantiation diagram
The instantiation diagram in Figure 8 shows how the identification of the order/chassis number (the root item)
is defined as also being a “BEP code”, BEP-A040.p (Serial number), referenced in the external library. In
PLCS the RDL can also contain any additional explanatory information about this BEP code and its definition,
and can be updated and maintained separately of any application using this construct.

Figure 8 — Classification of individual root instantiation diagram
7.4.2 Corresponding part of Part 21 text file
#13 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:10303-239',$);
#31 = IDENTIFICATION_ASSIGNMENT('1111:2222','',$,(#26));
#32 = IDENTIFICATION_ASSIGNMENT('3','',$,(#27));
#33 = CLASSIFICATION_ASSIGNMENT(#34,(#31),$);
#34 = EXTERNAL_CLASS('','BEP-A040.p',$,#39);
#35 = CLASSIFICATION_ASSIGNMENT(#36,(#32),$);
#36 = EXTERNAL_CLASS('','Version_identification_code',$,#13);
#37 = SUBSET('','',$,#34,#38);
#38 = EXTERNAL_CLASS('','Serial_identification_code',$,#13);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
12 © ISO 2007 – All rights reserved

7.5 Type properties
7.5.1 Type properties instantiation diagram
The instantiation diagram in Figure 9 shows how specific BEP codes for textual properties, such as general
and administrative data, are mapped into STEP AP 239, as properties of the product/chassis definition. As an
example BEP-G001 (Vehicle type) and BEP-G081.1 (Battery data) are used. Again the RDL is used to
dynamically update the definition and meaning of the BEP code at run-time.

Figure 9 — Type properties instantiation diagram
7.5.2 Corresponding part of Part 21 text file
#3 = PART_VIEW_DEFINITION('',$,$,#4,(),#2);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#40 = ASSIGNED_PROPERTY($,'/IGNORE',$,#3);
#41 = PROPERTY_REPRESENTATION($,#40,#42,$);
#42 = REPRESENTATION($,'',$,#44,(#43));
#43 = STRING_REPRESENTATION_ITEM('','swap body truck');
#44 = REPRESENTATION_CONTEXT('','');
#45 = CLASSIFICATION_ASSIGNMENT(#46,(#40),$);
#46 = EXTERNAL_CLASS('','BEP-G001',$,#39);
#47 = ASSIGNED_PROPERTY($,'/IGNORE',$,#3);
#48 = PROPERTY_REPRESENTATION($,#47,#49,$);
#49 = REPRESENTATION($,'',$,#44,(#50));
#50 = STRING_REPRESENTATION_ITEM('','24V, 180 Ah');
#51 = CLASSIFICATION_ASSIGNMENT(#52,(#47),$);
#52 = EXTERNAL_CLASS('','BEP-G081.1',$,#39);
7.6 Individual properties
7.6.1 Individual properties instantiation diagram
The instantiation diagram in Figure 10 shows how specific BEP codes for numerical properties, such as
measurements and weights, are associated to the product information. The type of numerical property is
defined by the PLCS RDL and should follow the standard. The specific BEP code measurement is classified
as being of type BEP-L031.2 (End of chassis mounted object, length).
This mapping covers a majority of the BEP codes as specified in ISO 21308-2 and ISO 21308-3.

Figure 10 — Individual Properties instantiation diagram
7.6.2 Corresponding part of Part 21 text file
#13 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:10303-239',$);
#28 = PRODUCT_AS_INDIVIDUAL_VIEW('',$,$,#4,(),#27);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#53 = ASSIGNED_PROPERTY($,'/IGNORE',$,#28);
#54 = PROPERTY_REPRESENTATION($,#53,#55,$);
#55 = PROPERTY_VALUE_REPRESENTATION($,'',$,#57,(#56));
#56 = NUMERICAL_ITEM_WITH_UNIT('',#60,4600.);
#57 = NUMERICAL_REPRESENTATION_CONTEXT('','',$,$);
#58 = CLASSIFICATION_ASSIGNMENT(#59,(#53),$);
#59 = EXTERNAL_CLASS('','BEP-L031.2',$,#39);
14 © ISO 2007 – All rights reserved

#60 = UNIT('/IGNORE',.T.);
#61 = CLASSIFICATION_ASSIGNMENT(#62,(#60),$);
#62 = EXTERNAL_CLASS('','mm',$,#13);
7.7 Organization information
7.7.1 Organization information instantiation diagram
The instantiation diagram in Figure 11 shows how organisational data is mapped into STEP AP 239.
Identifiers and names have references to the standard STEP AP 239 library, and the example shows how
BEP-A001 to BEP-A003, containing organisation names, addresses, etc. are mapped and referenced.

Figure 11 — Organization information instantiation diagram
7.7.2 Corresponding part of Part 21 text file
#9 = ORGANIZATION($,'/IGNORE');
#13 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:10303-239',$);
#23 = EXTERNAL_CLASS('','Name',$,#13);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#63 = IDENTIFICATION_ASSIGNMENT('Company ID','',$,(#9));
#64 = CLASSIFICATION_ASSIGNMENT(#65,(#63),$);
#65 = EXTERNAL_CLASS('','BEP-A001.p','$',#39);
#66 = SUBSET('','',$,#65,#67);
#67 = EXTERNAL_CLASS('','Organization_identification',$,#13);
#68 = IDENTIFICATION_ASSIGNMENT('Company Name','',$,(#9));
#69 = CLASSIFICATION_ASSIGNMENT(#70,(#68),$);
#70 = EXTERNAL_CLASS('','BEP-A002.p',$,#39);
#71 = SUBSET('','',$,#70,#23);
#72 = ADDRESS_ASSIGNMENT($,#73,(#9));
#73 = ADDRESS($,$,$,'4325',$,$,'SE-11100','Sweden',$,$,$,$,$,$);
#74 = CLASSIFICATION_ASSIGNMENT(#75,(#73),$);
#75 = EXTERNAL_CLASS('','BEP-A003.p',$,#39);
7.8 Project information – Example 1
7.8.1 Project information – Example 1 instantiation diagram
The instantiation diagram in Figure 12 shows how the standard parameters BEP-A010.p (Reference id), BEP-
A011.p (Project description), BEP-A032.p (Order version) are mapped into STEP AP 239.

Figure 12 — Project information – Example 1 instantiation diagram
16 © ISO 2007 – All rights reserved

7.8.2 Corresponding part of Part 21 text file
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#65 = EXTERNAL_CLASS('','BEP-A001.p','$',#39);
#76 = PROJECT('/IGNORE','',$,(),$,$,$,$);
#77 = IDENTIFICATION_ASSIGNMENT('Proj_0134-332','',$,(#76));
#78 = CLASSIFICATION_ASSIGNMENT(#79,(#77),$);
#79 = EXTERNAL_CLASS('','BEP-A010.p',$,#39);
#80 = DOCUMENT_ASSIGNMENT(#81,#76,'');
#81 = DOCUMENT('',$,$);
#82 = DOCUMENT_VERSION($,'This is the description of .',#81);
#83 = CLASSIFICATION_ASSIGNMENT(#84,(#81),$);
#84 = EXTERNAL_CLASS('','BEP-A011.p',$,#39);
#85 = IDENTIFICATION_ASSIGNMENT('Rev 3','',$,(#76));
#86 = CLASSIFICATION_ASSIGNMENT(#87,(#85),$);
#87 = EXTERNAL_CLASS('','BEP-A032.p',$,#39);
7.9 Project information – Example 2
7.9.1 Project information – Example 2 instantiation diagram
The instantiation diagram in Figure 13 shows the mapping of parameters BEP-A033.p (Order version date)
and BEP-A034.p (Order version update information) for project.

Figure 13 — Project information – Example 2 instantiation diagram
7.9.2 Corresponding part of Part 21 text file
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#76 = PROJECT('/IGNORE','',$,(),$,$,$,$);
#88 = DATE_OR_DATE_TIME_ASSIGNMENT(#89,'',(#76));
#89 = CALENDAR_DATE(2006,1,15);
#90 = CLASSIFICATION_ASSIGNMENT(#91,(#88),$);
#91 = EXTERNAL_CLASS('','BEP-A033.p',$,#39);
#92 = DOCUMENT_ASSIGNMENT(#93,#76,'');
#93 = DOCUMENT('',$,$);
#94 = DOCUMENT_VERSION('','Written comments of changes.',#93);
#95 = CLASSIFICATION_ASSIGNMENT(#96,(#93),$);
#96 = EXTERNAL_CLASS('','BEP-A034.p',$,#39);
7.10 Purchase order information
7.10.1 Purchase order information instantiation diagram
The instantiation diagram in Figure 14 shows how purchase orders are mapped to contract using specific
classification. BEP-A020.p (Approval statement) is mapped to a blank document. In similar fashion BEP-
A030.p (Order number) is mapped to the identification of the contract and BEP-A031.p (Order confirmation) is
mapped to the calendar date entity.

Figure 14 — Purchase order information instantiation diagram
7.10.2 Corresponding part of Part 21 text file
#26 = PRODUCT_AS_INDIVIDUAL('/IGNORE',$,$);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#76 = PROJECT('/IGNORE','',$,(),$,$,$,$);
#98 = CONTRACT_ASSIGNMENT(#97,(#26,#76));
#99 = CLASSIFICATION_ASSIGNMENT(#100,(#97),$);
18 © ISO 2007 – All rights reserved

#100 = CLASS('','Purchase_order',$);
#101 = DOCUMENT_ASSIGNMENT(#102,#97,'');
#102 = DOCUMENT('',$,$);
#103 = CLASSIFICATION_ASSIGNMENT(#104,(#102),$);
#104 = EXTERNAL_CLASS('','BEP-A020.p',$,#39);
#105 = IDENTIFICATION_ASSIGNMENT('4225_8676','',$,(#97));
#106 = CLASSIFICATION_ASSIGNMENT(#107,(#105),$);
#107 = EXTERNAL_CLASS('','BEP-A030.p',$,#39);
#108 = DATE_OR_DATE_TIME_ASSIGNMENT(#109,'',(#97));
#109 = CALENDAR_DATE(2006,4,5);
#110 = CLASSIFICATION_ASSIGNMENT(#111,(#108),$);
#111 = EXTERNAL_CLASS('','BEP-A031.p',$,#39);
7.11 Delivery information
7.11.1 Approval information instantiation diagram
The instantiation diagram in Figure 15 shows BEP-A021.p (Date of final specification) and BEP-A051.p
(Product delivery date) represented as two dates.

Figure 15 — Approval information instantiation diagram
7.11.2 Corresponding part of Part 21 text file
#27 = PRODUCT_AS_REALIZED('/IGNORE',$,#26);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#112 = DATE_OR_DATE_TIME_ASSIGNMENT(#113,'',(#27));
#113 = CALENDAR_DATE(2006,4,6);
#114 = CLASSIFICATION_ASSIGNMENT(#115,(#112),$);
#115 = EXTERNAL_CLASS('','BEP-A021.p',$,#39);
#116 = DATE_OR_DATE_TIME_ASSIGNMENT(#117,'',(#27));
#117 = CALENDAR_DATE(2006,4,7);
#118 = CLASSIFICATION_ASSIGNMENT(#119,(#116),$);
#119 = EXTERNAL_CLASS('','BEP-A051.p',$,#39);
7.12 Legal reference
7.12.1 Legal reference instantiation diagram
The instantiation diagram in Figure 16 shows the STEP AP 239 representation of BEP-A060 (Country of
registration) and BEP-A070.p (Legal reference) represented as text string properties.

Figure 16 — Legal reference instantiation diagram
20 © ISO 2007 – All rights reserved

7.12.2 Corresponding part of Part 21 text file
#3 = PART_VIEW_DEFINITION('',$,$,#4,(),#2);
#39 = EXTERNAL_CLASS_LIBRARY('urn:iso:std:iso:21308',$);
#44 = REPRESENTATION_CONTEXT('','');
#120 = ASSIGNED_PROPERTY($,'/IGNORE',$,#3);
#121 = PROPERTY_REPRESENTATION($,#120,#122,$);
#122 = REPRESENTATION($,'',$,#44,(#123));
#123 = STRING_REPRESENTATION_ITEM('','Legal_reference');
#124 = CLASSIFICATION_ASSIGNMENT(#125,(#120),$);
#125 = EXTERNAL_CLASS('','BEP-A070.p',$,#39);
#126 = ASSIGNED_PROPERTY($,'/IGNORE',$,#3);
#127 = PROPERTY_REPRESENTATION($,#126,#128,$);
#128 = REPRESENTATION($,'',$,#44,(#129));
#129 = STRING_REPRESENTATION_ITEM('','SE');
#130 = CLASSIFICATION_ASSIGNMENT(#131,(#126),$);
#131 = EXTERNAL_CLASS('','BEP-A060',$,#39);
Annex A
(informative)
STEP information background
A.1 General
The “STEP” standard is a set of ISO information model standards and related tools. These standards together
define “product models”, i.e. computer interpretable semantic representation of how “a product” is designed,
configured and maintained.
The STEP models are independent of implementation [application (e.g. Pro/E; Windchill; Enovia, CATIA) and
programming language (e.g. C++, Java, VBA)], system platform [operating system (e.g. UNIX, Windows) and
CPU (Intel, IBM)], and even of persistent storage and file representation [databases (e.g. Oracle, SQL server)
1)
and file formats (e.g. XML, ASCII CSV)].
STEP AP 239 “PLCS” used in this Technical Specification represents one of the latest STEP APs which is
more modularized and reusable. The scope of STEP AP 239 is the full product life-cycle, meaning that
information from “cradle to grave” is covered (with some limitations). STEP AP 239 also covers the information
management pertaining to the individual products, and how these products are supported and serviced “in-life”,
with connections to the original design data.
A.2 Suitability of STEP for communication of BEP data
The truck body building process that the ISO 21308 series covers is about product individuals, some not yet
manufactured, but still specific to a certain order or project.
For the foreseeable future, there will be a mix of measurements (BEP codes) and varying degrees of
individual chassis descriptions, starting with chassis type drawings going all the way to unique product
individual with three-dimensional visualization models. The STEP format can cope and grow with these
expectations and demands for many years.
If the ambition is only to transport a set of simple BEP codes, then STEP is not needed. A much simpler
representation using HTML (Hypertext Markup Language) or XML can be used, or even just ASCII (American
Standard Code for Information Interchange) or an MS Excel sheet. It is important to understand that XML
basically is an information envelope, and does not contain any semantic definitions of its contents, unless
specified in a DTD (Document Type Definition) or XML schema. These semantics are what STEP
standardizes.
There will always be a need for new dimensions or more detailed information about “object
...