"Drawing-Free Product Documentation" Project Group of The VDA's "PLM" Group

VDA Recommendation 4953-2 -1- November 2014
VDA Drawing-free Product Documentation

4953
Part 2
The first part of VDA Recommendation 4953 described working with simplified drawings combined
with 3D models and a master data sheet.
Part 2 of the Recommendation describes the means available to the automotive industry for
producing product documentation within a drawing-free process (DFP)
It describes how all the information required for product documentation is brought together in a
DFP container (PDF/A-3). This consists of a 3D portion with annotated geometry representation
(JT format), a metadata portion (STEP AP242 BO XML), a representation of this metadata
(PDF/A), as well as additional optional, user-defined components suitable for long-term archiving. It
further discusses the appropriateness for practical use of suitable data formats and makes
recommendations for different use cases on the basis of examples.
The use of a DFP container makes it possible to work within the process chains deployed in
product lifecycle management (PLM) without discontinuities between media and additional
conversion activities. There is no longer any need to derive drawings. This minimizes the extra
effort required for the parallel management of product information in 3D models, in drawings and in
product data management, and also improves data consistency.
The following subject areas are addressed:
 Structuring and mapping of product data in the metadata and 3D portions
 Reference process for the creation of the content data for the DFP container as well as the
generation, provision and use of the DFP container in the process chain.
 Use cases relating to the use of the DFP container
 Minimum contents of the 3D portion and metadata record and structure of the DFP container
 Revision descriptions
 Machine readability and handling of multilingual scenarios
 Typical application scenarios in the Drawing-free Process.
This Recommendation was produced by the 'Drawing-free Product Documentation in Automotive
Industry' Working Group of the VDA's "PLM" Group.
"Drawing-free Product Documentation" Project Group of the VDA's "PLM"

Group
Published by: German Association of the Automotive Industry (VDA)

Behrenstr. 35 Copyright
10117 Berlin Reproduction, in whole or in part,
Tel +49 (30) 897842 -0 is only permitted with the prior approval of
Fax +49 (30) 897842 -600 the publisher
E-mail: info@vda.de
Internet: www.vda.de
Copyright: VDA
Disclaimer
The document is a translated version of the German edition. Therefore the German of the
document represents the original and shall be referenced in the case of discrepancies. Due to
the translation it might be possible that the English text gives place for interpretations, because
terms are grounded often deep in the original language and therefore it is not possible in any
case to translate them uniquely into another language.
Content
1 Preface....................................................................................................................4
2 Purpose...................................................................................................................4
3 Scope ......................................................................................................................5
4 Target groups and potential benefits .......................................................................5
4.1 Technical development ............................................................................................ 5
4.1.1 Design ..................................................................................................................................... 5
4.1.2 Release ................................................................................................................................... 6
4.2 Procurement ............................................................................................................. 6
4.3 Production planning and control ............................................................................ 6
4.4 Operating equipment design ................................................................................... 7
5 Structure of a DFP container and fundamental requirements .................................7
6 DFP reference process ...........................................................................................9
6.1 Create content data .................................................................................................. 9
6.2 Generate document.................................................................................................. 9
6.3 Provide document .................................................................................................... 9
6.4 Use document ........................................................................................................ 10
6.5 Quality assurance .................................................................................................. 10
7 Use cases for DFP containers .............................................................................. 10
8 Product representation by means of 3D model and metadata record ................... 13
9 Minimum content and implementation................................................................... 18
9.1 Minimum content and implementation of the 3D portion .................................... 18
9.2 Minimum content of the metadata record ............................................................ 19
9.3 Query capability and machine readability of properties and free texts .............. 20
9.4 Multilingual capability ............................................................................................ 21
9.5 Grouping of data, control of visibility and filters ................................................. 21
10 Information structure in the DFP process .............................................................. 22
10.1 Structure of the metadata record .......................................................................... 24
10.2 Architecture of a DFP container ............................................................................ 25
11 Special use cases in the Drawing-free Process .................................................... 26
11.1 Assemblies ............................................................................................................. 26
11.2 Variants ................................................................................................................... 26
Copyright: VDA
11.3 Geometries of connecting faces and adjacent parts ........................................... 27

11.4 Pseudo-mirrored and mirrored parts .................................................................... 28
11.5 Components without reference numbers ............................................................. 28
11.6 References to other applicable documents.......................................................... 28
12 Application scenarios ............................................................................................ 29
13 Conclusions and prospects ................................................................................... 29
14 Open issues .......................................................................................................... 31
15 References (other applicable documents)............................................................. 31
16 Glossary ................................................................................................................ 32
Annexes....................................................................................................................... 35
List of figures
Figure 1 Representation of the product data through the combination of the 3D portion and
metadata record in the Drawing-free Process.................................................................... 8
Figure 2 DFP reference process............................................................................................... 9
Figure 3 Example use cases during the utilization of a DFP container.................................... 11
Figure 4 Structure of a DFP container (example: Volkswagen Aktiengesellschaft) ................. 25
Figure 5 Depiction of variants in the DFP container ................................................................ 27
List of tables
Table 1 Examples of the use cases for a DFP container ........................................................ 13
Table 2 Overview of drawing simplification in accordance with VDA 4953 or removal of
drawing in accordance with VDA 4953-2 ......................................................................... 17
Table 3 Example language IDs............................................................................................... 21
Table 4 Property groups and typical characteristics that may relate to geometry .................... 23
Table 5 Terms and abbreviations ........................................................................................... 35
Copyright: VDA
1 Preface
At present, drawing sets are produced in different variants. They are important documents for
the technical description of components, products and their properties. Depending on its
intended use, a drawing may contain different types of descriptive information relating to a
product. In the past, a conventional technical drawing was the primary, and often the only,
source of such information.
Following the deployment of 3D technologies, the use, for example, of CAD and PDM systems
and, increasingly, the mapping of product manufacturing information (PMI) in 3D CAD models,
product description information is now primarily handled in the systems used to create and
manage the product data and is now to be found (if it is available at all) only as a derived
representation in drawings used for documentation purposes. Nevertheless, a wealth of
information (e.g. texts), whether or not it has any direct relationship to the product geometry, is
managed in drawings and can therefore only be taken over into other IT systems at the
expense of considerable effort.
The Recommendation envisages relocating information that has traditionally been present in
technical drawings to 3D models, files, database objects or other forms of digital representa-
tion so that it can be created, maintained, documented, stored and further processed in
computer systems more efficiently. It describes the transition from conventional drawings (2D)
to product documentation within a DFP container as part of a Drawing-free Process.
It recommends relocating organizational and technological metadata, as well as design
properties that relate to components as a whole, to separate files, databases or product data
management systems that are independent of the 3D model and drawing. This will simplify the
management of this product data in the enterprise's preferred PDM system and the system-
independent transfer of this data. If an enterprise does not as yet use any product data
management system then the adoption of VDA 4953-2 will help prepare for the subsequent
introduction of PDM.
In a Drawing-free Process, the task of communicating and documenting the product data,
which was previously present in a 2D drawing, is now handled using a DFP container based
on 3D technology, as well as through the provision of metadata. As a result, it is possible in
many cases to do away with the need to derive and manage 2D drawings.
As far as possible, the alphanumerical, non-geometric information and other information
unrelated to geometry in a DFP container should be combined in a metadata record and
handled separately from the geometrical portion of the information.
2 Purpose
The current Recommendation describes the concepts and methods for replacing conventional
(2D) drawings as the leading medium for conveying product information by documentation
based on the use of DFP containers. It describes the structuring and handling of the relevant
information (2D, 3D, metadata) in the DFP container together with its architecture. It does not,
however, describe the handling of the information in the product management systems (e.g.
PDM/DMS systems) or authoring systems. It also, for example, derives the requirements
placed on authoring systems and their users in order to make it possible to generate and use
DFP containers. If necessary, it should also be possible to provide electronic feedback of
information from a DFP container. The CAD and PDM system architecture required for this
may take very different forms. It depends on the enterprise's internal processes and IT
strategies and is therefore not standardized within the present Recommendation.
Copyright: VDA
3 Scope
The present Recommendation is applicable whenever, for the documentation of components:
 Information that is directly related to the geometry is created and managed in 3D
models
 No or only very few drawings are derived
 In contrast to the case of conventional technical drawings, metadata is removed from
the geometry portion and is managed and communicated separately
The term "components" as used in this Recommendation comprises individual parts (P) and
assemblies (A) and on through to complete products. The starting point is the information that
describes the product and not the information that describes the tool or manufacturing
process. Depending on the intended utilization, a drawing may contain different contents in
terms of the descriptive product information and this may be present in different levels of
detail.
Annex A provides a number of examples of typical types of drawings as a function of the
involved user groups and the time of creation of the drawings within the PEP. It is not possible
within the scope of the current Recommendation to examine all drawing types and all their
specific characteristics. The recommendations therefore focus on drawings prepared for
requests for proposals, drawings of finished parts, and other aspects of drawings illustrating
the scope of delivery or module drawings. Alongside finished parts drawings for individual
parts, module drawings or component drawings are very important in securing OEM release,
in particular with regard to communication with system or component manufacturers. The
current recommendations can also be applied to other types of drawing.
4 Target groups and potential benefits

The Recommendation is intended for all persons who create and use conventional technical
drawings during technical development and the subsequent downstream process chains in the
PEP.
The most interesting potential benefits lie in the fact that information that is currently made
available in the form of drawings, such as technical directives, test specifications, references
to standards or revision descriptions, can be supplied to the product data management
systems as content that can be processed electronically.
The following sections provide corresponding examples of different target groups and potential
benefits. The underlying use cases are described in section 7, Figure 3 (p. 11).
4.1 Technical development

4.1.1 Design
Design engineers, persons responsible for design and development activities, software
developers for development systems or technical systems, developers of CAD and PDM
methods and persons responsible for CAD and PDM processes, persons responsible for PDM,
DMS and similar management systems for technical specifications and documentation (role of
data originator (DO))
 5-10% savings1 during initial creation, small savings through the transfer of activities
from 2D modeling to 3D
1
Time savings based on expert assessments made by the companies that drafted the Recommenda-
tion
Copyright: VDA
 10-30% savings1 on changes due to the elimination of the need to produce CAD
drawings
 Entries are made in accordance with the single-source principle, no redundant data
entry in the CAD and PDM systems
 No additional management of 2D CAD data because changes are made directly in the
3D information or in the PDM system (easier-to-use editors)
4.1.2 Release
Persons responsible for conducting release verifications, quality assurance, persons
responsible for design and development activities (role of data consumer (DC))
 Reduction in the volumes to be handled during drawing and quality inspections in the
release process thanks to
 consistent, non-redundant metadata entry in a leading authoring system (e.g. CAD
or PDM)
 avoidance of errors during the transfer of all the contained information through ad-
herence to the single-source principle
 assurance of the reliability of the information taken from the employed source sys-
tems (e.g. use only of approved materials from the materials database)
 consequently, less reworking and fewer corrections during the release process
 possibility of automating inspection work through the provision of machine-
readable information
4.2 Procurement
Purchasers
(role of data consumer (DC))
 No longer any need to additionally provide potential suppliers with native 3D CAD
models over and above the drawings accompanying the invitation to tender
 3D portion fully present in JT, thus allowing the partner to perform component analysis
and evaluation
 Digital searches and/or analyses possible in the 3D documents, including across
individual procurement scopes (e.g. identical materials)
 If required, it is possible to access the 3D geometries of the components even without
a CAD system
4.3 Production planning and control

Production/manufacturing planners
 Use of the 3D documents and the digitally processable metadata they contain instead
of various multiple inputs requiring the use of different data sources
 More content available in 3D rather than in 2D form, thereby reducing queries relating
to component design and possible corrections or extensions made necessary due to
"missing" information
 Increased value of the information present in the DFP container in contrast to the
simple black-and-white pixels of a drawing (raster graphics)
 Digital searches (e.g. using search functions)
 Rapid retrieval of information through referencing between metadata and geometry
(PDF ↔ JT)
Copyright: VDA
 Intelligent searches as a result of referencing and IT functions instead of manual

searches in drawing sections and tables
 One central document instead of multiple accesses to PDM systems in order to
obtain different digital information elements
 In addition, the native CAD data also contains other useful information (e.g. PMI) and
contributes greater added value to the process chain
4.4 Operating equipment design

Operating equipment designers/planners
 (see production planning)
(role of data originator (DO))
 (see also technical development, design)
 Preparation of standard parts and standard assemblies including full annotations (e.g.
dimensions, tolerances, 3D texts)
 Avoidance of follow-up documentation for standard parts employed in the context of
operating equipment
5 Structure of a DFP container and fundamental requirements

Unlike a conventional technical drawing, the product description for a component for the
purposes of this Recommendation comprises:
 One or more 3D models
 A metadata record1
 Possibly other additional technical documents
The dimensions in the 3D model should be presented in a way that is suitable for manufactur-
ing and verification purposes. Modern NC planning systems use the 3D model as the basis for
programming. As a result, the fully dimensioned description of the shape and design of the
component in the form of a drawing is no longer required. In the case of free-form geometries,
such a description is largely impossible. This is also unreservedly true in the case of the
Drawing-free Process.
Text information is generally managed in a metadata record. The term "metadata" here refers
to all non-geometrical data, both technological and organizational, that relates to the overall
part.
The metadata record can be managed in a separate file or database system and can be
viewed using a suitable viewer. It references the associated 3D model. It may contain
descriptions of revisions as well as the entire revision history. If necessary, the relevant data
can be output in paper form.
Since the metadata record can be subject to version management, all the documents that form
part of the product description can be uniquely identified as such at any time. It is possible to
define company-specific metadata, maintain metadata in different languages, and map data
for different companies in parallel.
1
Previously referred to as master data sheet in the context of Simplified Drawings
Copyright: VDA
In the Drawing-free Process, the complete description of the component, which is binding for
the purposes of component release, is achieved by combining the metadata record with the
associated 3D model - the 3D portion in the DFP container - including the geometrical
references (Figure 1, p. 8). The requirements regarding the geometrical specification are
unambiguously represented in the 3D CAD model in a way that reflects the design intentions.
The graphical representation of the 3D portion should comply with applicable standards (e.g.
ISO16792).
The mode and implementation of the graphical representation of the 3D portion in the DFP
container do not form part of the current Recommendation.
A DFP container may contain additional documents in a representational form that permits
long-term archiving (as an adaption of VDA 4958) if these are relevant for the context
(intended use) of the container.
Figure 1 Representation of the product data through the combination of the 3D portion and
metadata record in the Drawing-free Process
The formal structure of a DFP container is described in 10.2 (p. 25).
Copyright: VDA
6 DFP reference process

Because the DFP container used in the Drawing-free Process completely replaces the
technical drawing, it must fulfill the requirements placed on audit-proof documentation and
may also ensure long-term archiving in accordance with VDA 4958. Figure 2 (p. 9) provides a
diagrammatic overview of the reference process for drawing-free product documentation.
Figure 2 DFP reference process
6.1 Create content data

The "create content data" phase of the DFP reference process identifies the process, usually
present within the enterprise, by which content data (such as 3D CAD models, technical
performance descriptions, organization and technological metadata) is generated using
authoring systems (e.g., 2D/3D CAD, PDM, Office tools, editors)
6.2 Generate document

In the "generate document" process step, the relevant content data is extracted from the
authoring systems, prepared and/or converted, and transferred to the DFP container.
Preparation includes, for example, the grouping or target group-oriented compilation (filtering)
of the metadata (see 9.5, p. 21). Creation of the DFP container can be supported by a PDM or
DMS system. This also simplifies the version management of the DFP container if required.
Generation can alternatively be performed by means of an independent batch process. A table
of contents should be generated for the components present in the DFP container. When the
DFP container is created, only the data that is relevant for the intended use (context) of the
container should be taken over into it (see below "Use document" or Use Cases).
6.3 Provide document

It is essential that the DFP container is provided in a suitable management system (e.g. PDM,
DMS, archive, file system) before the following phases can take place. It is possible to
automate the provision process and this improves process reliability.
The distribution, version management and control of the lifecycle of a DFP container must be
adapted to the requirements of the relevant process chain.
Copyright: VDA
VDA Recommendation 4953-2 - 10 - November 2014
6.4 Use document

In the "use document" step, the requirements placed on the DFP container may vary greatly. A
DFP container must be produced that meets the needs of the use case that is to be supported
(Figure 3, p. 11). It must always be possible to view all the content (content data). It is also
recommended that the content should permit derivations for subsequent data-based
processes.
Changes to existing content within a DFP container itself are not permitted. Changes may be
made only in the source or authoring systems. The new version of the DFP container must
then be derived or generated on the basis of these revisions.
In the same way as a conventional drawing constitutes an important source of descriptive
product information for a number of different sectors and users, so too can DFP containers be
used to meet the needs of different application scenarios.
6.5 Quality assurance

Throughout the DFP, it is necessary to ensure the quality and consistency of the information
used for and present in the DFP container, including during the use of the container contents.
The necessary measures, the verification criteria and the scope of the checks performed
during data verification and validation (see Table 1, p. 13) must be defined, for example, in the
light of the significance and sensitivity of the information. Recommendations on the quality
assurance of DFP containers and on the use of the corresponding quality management tools
do not form part of the present VDA 4953-2 (section, 14, p. 31).
7 Use cases for DFP containers

Figure 3 (p. 11) presents important example applications for DFP containers in the form of a
use case diagram in accordance with UML. The following dependencies (relations) are
depicted:
Hierarchy/inheritance
in use case diagrams, indicates a specific instance of the associated use
case, i.e. the use case in question is a specific instance of the associated
use case and inherits its properties
<<incl.>> <<include>>
in use case diagrams, specifies that the associated use case is included
(mandatory condition, prerequisite)
<<ext.>> <<extend>>
in use case diagrams, defines a (possible) extension via the associated use
case (option)
Table 1 (p. 13), which follows Figure 3 (p. 11), presents typical examples for the creation and
use of a DFP container and further details the scope of the present version of VDA 4953-2.
Copyright: VDA
Figure 3 Example use cases during the utilization of a DFP container
Copyright: VDA
Ite Use cases Brief description Role:

m data
consumer
originator
(DO)
(DC)
1 Viewing Viewing or presentation of the information in a DFP X X
container (3D model and metadata)
2 Individual Company-specific generation of a DFP container using X
generation of tools that extract the content data from the authoring
DFP containers system, convert it to the representational form required
for the DFP container and generate the container itself
3 Standardized Generation of a DFP container as in item 2 but using X
generation of standardized methods and tools
DFP containers
4 Opt. printing of Optional printing of the metadata and all the views of X X
the metadata the 3D portion as required
and views
5 Filtering on Interactive or automatic filtering or searches for the X X
information contents of a DFP container
clusters
6 Redlin- Incorporation of notes or comments (redlining) in a X
ing/commenting DFP container, if necessary with feedback of the
comments to the author of the container
7 Provision to Provision of the component information in a DFP X
downstream container to the processes located downstream of the
processes design stage
8 Data export from Export of metadata (XML) and/or geometry data (JT) X
DFP container from a DFP container for computer use or for further
processing of the content
9 Derivation of Generation or derivation of service documents as a X
service possible use case for provision to downstream
documents processes
10 Delivery to Transfer of the information in the DFP container to X
Planning and Planning or of an order to Manufacturing
Manufacturing
11 Ensure Ensure that the DFP container is binding X
binding nature
12 Component Use of a DFP container to document a binding X X
release component version as an example of ensuring the
binding nature of the container
13 Validate data Check the data (contents) in the DFP container against X
the authoring systems, e.g. via validation properties as
per VDA 4958 or ISO EN/NAS 9300 (LOTAR), usually
by means of corresponding validation tools (checkers)
14 Verify data Check a DFP container for compliance with VDA 4953- X
2
15 Documentation Ensure that a DFP container is documented and X
Archiving archived in compliance with VDA 4958 or ISO EN/NAS
9300
Copyright: VDA
Ite Use cases Brief description Role:

m data
consumer
originator
(DO)
(DC)
16 Data exchange Use of DFP container for data (content) exchange with X X
internal and external partners
17 Create request Creation of a request for proposal as a special case of X X
for proposal data exchange with suppliers
18 Control Control communication (workflows) within the X X
communication framework of data exchange, e.g. in a change process
as per VDA 4965
19 Data processing Use of a DFP container for two-way communication in X
in cooperative scenarios in which it is possible to extend
change/cooperati or add comments to the data in the container (e.g.
ve processes redlining), while taking account of item 21
20 Check change Check a change request as a possible trigger for data X
request processing in a change/cooperative scenario
21 Change data in Revisions or extensions to the metadata and/or X
authoring geometry (notation) that result in a new DFP container
systems (new/modified version)
22 Implement Implementation of solutions to fulfill a change request X
change request
Table 1 Examples of the use cases for a DFP container
If a DFB container is used for archiving and as a binding document then VDA 4958 shall apply.
In this case, the processes should be designed in such a way that it is not possible for the
content to be changed or the information to be corrupted on transfer from the authoring/source
system to the DFP container. In the event of the (long-term) archiving of the DFP container, it
is necessary to ensure that the contents are validated and verified in accordance with VDA
4958.
This presentation of application scenarios makes no claim to completeness. The utilization and
scope of use of a DFP container are the responsibility of the owner (author). The minimum
requirements are described in section 9 (p. 20).
8 Product representation by means of 3D model and metadata

record
Within the process chain from creation through to manufacturing, the 3D model constitutes the
primary documentation of the geometry. The metadata record is the main description of the
non-geometrical data.
Information that relates directly to the component geometry (e.g. dimensions with special
tolerances or properties that describe only subsections of the part geometry) is depicted in the
3D model in the Drawing-free Process.
It is necessary to make sure that the metadata record and the 3D model can be exchanged
and viewed all the way along the process chain and that all changes can be incorporated in a
consistent way. This includes the possibility of conversion operations.
Copyright: VDA
All applicable drawing and release guidelines, CAD and other standards must be observed
during the creation, modification, documentation and release of the 3D model and metadata
record.
Redundant information should be avoided. If this is not possible then it must be identical in the
3D model and in the metadata record.
In the event of a change of hardware and/or software, it is necessary to ensure that the
existing product data can still be read and analyzed. Archiving must be ensured in accordance
with DIN 6789-6 and VDA 4958.
Based on DIN 6789, Table 2 (p. 17 ) provides an overview of the changes in the component
properties that have to be described compared to a conventional drawing.
Section 10.1 (p. 24) describes how the metadata record for Drawing-free Processes should be
implemented and provides recommendations for the 3D portion of the DFP container.
Copyright: VDA
Properties of a Terms in DIN 6789, Conventional drawing VDA 4953 VDA 4953-2
component Part 2 simplified drawing, DFP - Drawing-free
3D-CAD model and process
master data sheet
Form/shape Description of geometry, Views, sections, details Fully modeled in the 3D CAD Fully modeled in the 3D CAD
views, (possibly derived from the 3D model (solid or surface model), model and mapped in the 3D
sections, details CAD model) dimensionally accurate to model (solid or surface
nominal dimensions. The 3D model), dimensionally
CAD model is the primary accurate to nominal
geometrical description. dimensions.
Views, sections, details derived Views, sections, details in
exclusively from the 3D CAD the 3D CAD model with
model. Possibly transparent "Named Views"/"Captures".
mode. Defined view layout.
Use more spatial views.
Position Position of objects Presentation of drawings of Same as conventional drawing 3D A, DMU
assemblies in views, sections,
details (if necessary in
3D A, DMU
coordinate system/vehicle
grid)
Dimensions Dimension line, subsidiary Part completely described In drawing: main/functional In 3D portion:
line, dimension figure using dimensioned dimensions and dimensions for main/functional dimensions
presentations in views, which specific tolerances have and dimensions for which
sections, details to be defined specific tolerances have to
be defined.
Tolerances Dimensional tolerance, Specifications in views, Same as conventional drawing In 3D portion, in accordance
geometrical tolerance sections, details, possibly with ISO 16792 etc.
using dimension figure
General tolerances In title block Master data sheet Metadata record
Copyright: VDA
master data sheet
Organizational Company, copyright notice In title block / frame of Master data sheet Metadata record
metadata Document number, release drawing
status, date of issue, created Note referring to current 3D Note: 'Drawing-free process
by, checked by, data data record. according to VDA 4953-2'
processing key, ID number, Note: 'Simplified drawing
name title according to VDA 4953'
Design metadata Unit, weight, quantity, In title block / frame of Master data sheet Metadata record
relating to the material, hardness, drawing
overall part tempering, material
treatment, semifinished
product, surface treatment,
coating, after-treatment,
surface finish
Revisions. Revision index Revision index for geometry in Same as conventional drawing; In 3D portion, identified via
identification on views, sections, details also specification of 3D referencing (e.g. unique
geometry coordinates label with reference)
Revisions: Revision index Revision table in title block or Master data sheet Metadata record
description separately, reference via
revision index
Notes and Technical specification, As text in drawing Master data sheet Metadata record
instructions supply agreement, technical
relating to overall directives, company
part standards
Copyright: VDA
master data sheet
Characteristics, Material, hardness, As text with reference to Same as conventional drawing In 3D portion: via referencing
notes and technical tempering, material geometry in views, sections, (e.g. unique label and text in
directives relating treatment, surface treatment, details metadata record)
to geometry coating, after-treatment,
surface finish, technical
specification, company
standard, parts identification,
technical directives
Table 2 Overview of drawing simplification in accordance with VDA 4953 or removal of drawing in accordance with VDA 4953-2
Copyright: VDA
9 Minimum content and implementation

The following sections provide an overview of the minimum requirements and implementation
of the modules described in 5 (p. 7) and 8 (p. 13) (3D CAD model, metadata record, 3D
portion of the DFP container).
9.1 Minimum content and implementation of the 3D portion

The 3D CAD model is fully modeled as a solid model and is taken over into the 3D model (see
6.2, p. 9). Surface models can only be used in special cases. Wire frame models are generally
unsuitable for comprehensive documentation.
With regard to data quality, the agreed or context-dependent standards and recommendations
must be adhered to.
It is possible to reduce the geometry of required connecting or assembly faces to the mating
surfaces.
The component must be represented completely and dimensioned accurately (nominal
dimensions). This means that all shaping elements such as angled surfaces, fillets, holes and
ribs must also be represented. Threads and teeth are not fully modeled but are shown or
identified accordingly in the 3D model
All the information that is to appear in the 3D portion of the DFP container must be generated
in full in the 3D CAD model in the source/authoring system. Alongside the geometrical
description, this also comprises geometry-related annotations, so-called PMI, component
properties and similar information.
The identification of individual geometry elements must be taken over in a consistent,
traceable way from the 3D CAD model into the 3D model.
The 3D portion of a DFP container as specified in VDA 4953-2 must possess at least the
following content in addition to the simple geometrical description of the 3D form:
 Identifier of the 3D portion
 Revision level of the 3D portion in the DFP
 A view named "Initial" that contains all the information
 Geometrical dimensions and tolerances
 Characteristics, notes and technical directives relating to geometry
 Date created
 Identifier of the metadata record or reference to a metadata record with the same
number
 The note "3D model as per VDA 4953-2" (translated if necessary)
In addition to the note of ownership in the metadata for the entire DFP container, it is also
advisable to include a note of ownership within the 3D model.
It is also necessary to specify all the information that is required for the understanding,
manufacture and/or utilization of the component. It may only be used together with the
metadata portion. The standard used for modeling must be specified in the 3D portion (e.g.
ISO, ASME, ANSI) and may also be indicated in the metadata record.
The 3D portion in the DFP container must be implemented in the light of the following
requirements:
 Geometrical representation
 Depending on the use case and the agreements made, the partners in the process
must decide whether to implement the geometry as BREP or as a tessellated ge-
ometry.
 Views and sections
Copyright: VDA
 These must be realized in an identifiable way in accordance with a documented

classification scheme
 Only the views and sections that are relevant for the intended use (context) of the
container are taken over into it.
 All the views and sections that are available in the container must be present in a
list from which they can also be selected.
 Geometrical dimensions and tolerances
 These must be realized in accordance with agreed standards.
 The content of the 3D portion should be described by specifying the toleranced
main and functional dimensions and should permit a general evaluation of the
component.
 Furthermore, only those dimensions that must be specifically toleranced should be
given.
 Identification of revisions
 Revisions to the 3D portion must be identified in the 3D model in accordance with
the established processes and agreements.
 Referencing (link between the revision and the geometrical representation) must be
performed in accordance with a documented classification scheme.
 Characteristics, notes and technical directives relating to geometry
 These must be realized in accordance with agreed standards.
 Referencing (link between the revision and the geometrical representation) must be
performed in accordance with a documented classification scheme.
 Multilingual capability
 Text specifications must be entered in a uniform (generally, a legally appropriate)
language.
 Other languages may be available either in full or in part.
 Component properties, such as dimensions, tolerances and specifications that are
assigned to a geometry element, must be presented as set out in ISO 16792 and it
must be possible to query them (see 9.2).
9.2 Minimum content of the metadata record

Metadata is organizational and technological information which may optionally also relate to
geometry. The metadata record must at least contain the following specifications:
 Owner (company name) / company
 Identifier of the metadata record
 Revision level of the metadata record
 Created by
 Date of issue
 Responsible person
 Part number
 Name / part
 Part revision level
 Tolerancing principle
 Unit system used
 Identifier of the 3D CAD model
 Revision level of the 3D CAD model
Copyright: VDA
 Binding language
 Confidentiality level
 Identifier of the 3D model in the DFP container
 Revision level of the 3D model in the DFP container
 Reference to the quality standard with which the 3D portion complies
 Component-related properties
Notes on revisions are recorded in the metadata record and indicate:
 Revision identifier
 Order number of revision (number of the design order for the completed revision)
 Date of revision order (date on which the revision order was issued)
 Revision level (revision level of metadata record or 3D model to which the text of the
revision refers, in accordance with owner's definition)
 Position (identification of the link between the revision text and the position of the
revision in the metadata record or the 3D model)
 Revised by (name of the person carrying out the revision)
 Revision date (date on which the revision was made)
 Language (language in which the revision text was written)
 Revision text (short description of the revision)
Keywords and other information are described in section 10 (p. 22).
9.3 Query capability and machine readability of properties and free

texts
Properties in the 3D model, such as dimensions, tolerance specifications and other PMI, are
usually related to the geometry and can be mapped as properties in the 3D model. These
properties should be entered in machine-readable form. A suitable viewing capability as per
ISO16792 should be supported. To improve the viewing and machine readability of free texts
that do not comply with any ISO standard, these should be structured as follows:
 Separator for information = ";" (semicolon)
 Separator for lists = "," (comma)
 Nesting of information = "< >" (greater than, smaller than symbols)
 Keywords used to identify information
Examples of free texts structured in this way are:

 Basic definition: specification of a tightening torque in the form
"Tightening torque; MA; GS 90003; 7.6NM; III-C"
 As nested information:
"L;8;PN1.52;1728817;hex bolt with collar M6x14;<tightening
torque;MA;GS90003;7.6NM;III-C>"
 List:
"Oblong hole;6±0.2x6.5±0.2;nozzle fixing SWA, KTL, assembly hole"
The instructions for forming (string syntax) the keywords and separators (legend) must be
provided with the DFP container (in the metadata or optional elements). The specifications
arrived at regarding the machine readability of properties in the model should comply with ISO
16792 and with the agreements reached by the CAD and processor manufacturers in the
Copyright: VDA
"Recommended Practices" of the CAx Implementor Forum. Any machine readability of

structured free texts and properties that go beyond the above agreements must be defined as
an enterprise-specific solution.
Alternatively, properties such as reference points can also be read from the CAD model and
be viewed as XML in the metadata portion, e.g. as a table or list. Such representations must
be assigned a geometry reference that can be found in the 3D portion as required.
Machine readability is ensured by one or more "properties" in the 3D model element and with
a graphical depiction of the property or properties as PMI, as (free) text (string) at the
reference OR as XML in the metadata portion with a corresponding reference to the
geometry.1
If a property is only depicted graphically as PMI then it can generally only be read and
understood by human users.
9.4 Multilingual capability

The language declared as the enterprise-specific, binding language must be supported as the
primary language in the DFP container. A DFP container may also contain other languages.
The language(s) must be uniquely identified in the metadata in accordance with the
corresponding standard. As far as possible, the language variant(s) used for annotations (PMI)
in the 3D model must be identical to those used in the metadata section and at least
correspond to the language declared as the binding language.
Language IDs are specified in accordance with DIN 2335 / ISO 639.
de German
en English
es Spanish
fr French
Table 3 Example language IDs
9.5 Grouping of data, control of visibility and filters

The standard functions of the employed viewers for searching in and filtering the contents of a
DFP container are generally available. For this to be possible, information must be machine-
readable and permit queries (see 9.3, p. 20).
The primary grouping of the information takes place in the 3D model through the structuring of
the geometry elements and in the metadata portion by combining the information through the
PDF display of the XML representation in the DFP container.
If, in addition to these capabilities, predefined information groups or filters are required then
these must be defined in the authoring system. In the case of the 3D model, the view and
section mechanisms (see 9.1 p. 18) must be used for predefined filters. The capabilities
available in the metadata portion can be extended by adding further sections or pages in the
PDF display of the XML representation.
1
The CAD methods and translators that are currently employed in productive use do not yet all support
working with properties and the ability to display such properties as PMI.
Copyright: VDA
10 Information structure in the DFP process

Part 1 of VDA 4953 contains definitions of the attributes that have in the past been entered as
texts in drawings and which, in the future, will be mapped in the metadata record. The
attributes were selected on the basis of the DIN 6789-2 standard, ISO 7200-1 and 2, VDA
4958, and the enterprise-specific documents of the companies forming the Working Group.
For reasons of clarity, the metadata in the master data sheet in VDA4953 were subdivided into
the following areas on the basis of DIN 6789:
1. Organizational information
2. Technological information
3. Geometrical information
The same subdivision can be applied to the DFP process. The organizational information also
contains the data used to identify the elements in a DFP container as described in section 5
(p. 7) and 8 (p. 13). The possibility of identifying the component, 3D model and metadata
record using different identifiers and revision levels ensures that it is possible to manage
related documents in a way that is independent of the numbering system and data storage
mechanism.
The geometry information forms part of the 3D model (see 9.1, p. 18). This geometry
information can be referenced in the metadata portion (e.g. list of available views and sections
in the 3D model, notes on revisions that relate to geometry).
Table 4 presents a selection of typical component information and properties that may relate to
geometry. This list makes no claim to completeness as it will vary depending on the type of
component. This grouping should help to categorize other information and properties.
Explanation Main Information Examples

characteristic
Notes on Identification Identification of parts Stamp, position, plate,
identification and engraving, embossing
position
Position identification in Reference: "Position 1"
geometry
Properties that Function Notes on function Center of rotation, connector,

explain the mode limit position
of functioning
Description of Geometry Geometrical indicators Center of gravity, moment of
geometrical inertia, partial volume, partial
constraints area
Tolerance specifica- Dimensional tolerance,
tions geometrical tolerance and
positional tolerance
Additional geometrical Connecting surfaces of
constraints adjacent components
Notes on specific Material Auxiliary materials Bonding seam using

material properties adhesive Xy
Copyright: VDA
Explanation Main Information Examples

characteristic
Notes on coatings, Specification of build-up
local application of welding
materials
Notes on permeability Permeability of a surface
with a through-hole
Notes on Manufacture Manufactured Specification of bore, hole,
manufacturing geometrical element groove
details
Notes on tools Direction of mold release,
bore with center drill Xx
Surface treatment Specification of surface

protection, chromated
Notes on local changes Specification of foam settings

of thickness
Notes on assembly Assembly Notes on adjacent Reference number

properties components
Notes on assembly Maximum tightening torque y

details [Nm]
Description of test Operation Technical directives "Insert in transport

and operating mechanism here"
properties
Weight specifications Weights of part geometries
Notes on revisions Revision Revision relating to "Rib added"

made geometry
Table 4 Property groups and typical characteristics that may relate to geometry
The table in Annex B provides detailed recommendations on the following aspects of the
relevant information.
The "Metadata record" column describes whether the maintenance of the information in the
metadata record of a DFP container is
 mandatory (m)
 desirable if possible (x = extend)
 optional (op), or whether it should
 not (n)
be maintained.
This indication of relevance has been adapted from VDA 4958-3 section 4.4.3. The information
marked as "m" must always be provided. It may be necessary to make corresponding
adaptations in the source/authoring system or, if required, in the process chain. The absence
of such information must be explicitly indicated.
Copyright: VDA
If an item of information marked as "x" is present then this must also be documented, i.e. data
preparation and documentation functionalities must be provided. Information items marked as
"x" may also be declared as "mandatory" on a company-specific basis.
Optional information may be relevant at an industry-, product- or company-specific level.
Information marked as "op" may be declared as "x" or "m" on a company-specific basis.
The "Occurrences per company" column indicates whether an attribute for a company may
occur
 once (1),
 not at all (0), or
 any number of times (n)
in a metadata record.
Independently of this specification, an attribute that may only occur once in a metadata record
may also be present translated into other languages.
The "Multilingual" column identifies the attributes for which multilingual contents are possible.
10.1 Structure of the metadata record

The structure of the content of the metadata record is described below. No specifications are
given concerning the actual structure of a metadata record in a given data format.
The metadata record contains the geometry-independent and, by way of an extension to the
master data sheet described in VDA 4953, also the geometry-related metadata for the design.
In the case of Drawing-free Processes, the following structure should be used for the display
of the metadata in the DFP container.
 Organizational information
 Document-related specifications
 Technical, material-related, part-related specifications
 Technological information
 Material-related specifications
 Quality-related specifications
 Surface-related specifications
This structure forms the basis for the detailed presentation of the contents of the metadata
record in the data dictionary in Annex B.
Copyright: VDA
10.2 Architecture of a DFP container

A DFP container is a combination of the geometrical, technological and organizational
(previously drawing) data for a component (individual part or assembly) in a standardized,
published representational form.
 3D portion
with annotated representation of the geometry
(JT format as set out in ISO 14306)
 Metadata portion
o Metadata record
Structured metadata, separated from the 3D portion
(STEP AP242 BO XML format as set out in ISO 10303-242)
o Presentation of the metadata
(PDF/A as set out in ISO 19005)
 Optional elements
(standard formats suitable for long-term archiving)
This data is combined within a DFP container in the form of file attachments with a uniform
representational form based on PDF/A-3 (ISO 19005-3). Figure 4 provides an example of this
type of structure.
Figure 4 Structure of a DFP container (example: Volkswagen Aktiengesellschaft)
The presentation of the metadata in the form of a display of the metadata record is the central
component, while simultaneously providing the first or "home" page for the DFP container. All
the other components of the DFP container (3D portion, metadata record and optional
elements) must be implemented as file attachments as described in ISO 19005-3.
At least the 3D model and the metadata record must be present in machine-readable
(derivable) form and the (human) recipient must be able to display them using license-free
and/or commercially available tools.
The DFP container permits two-way data communication with partners, e.g. via the
standardized XML STEP AP242 Business Object Model, and the provision of visual
information and data to the process chain downstream from design as a comprehensive
replacement for technical drawings (see also section 12, p. 29).
Copyright: VDA
11 Special use cases in the Drawing-free Process

11.1 Assemblies
All the requirements and recommendations from the preceding chapters apply to assemblies
(A) and assembled constructions in just the same way as they do for individual parts (P). In
addition, the following recommendations also apply to assemblies:
 Only items that are relevant for installation (component geometry, PMI etc.) and
assembly-related information should be present.
 The PMI for the installed components (individual parts, subassemblies) themselves
should not be present.
 A DFP container for an assembly contains only one structure level (modular), at which
the installed components are interpreted exclusively as references since the binding
documentation is provided in the DFP container corresponding to the component.
 The 3D portion for an assembly contains the component geometry (individual parts or
assemblies) necessary for the assembly's context in the correct position.
 In the initial view, the assembly must be depicted in its assembled state.
 As an option, it is also possible to depict further views with the components in other
positions, e.g. for exploded representations, limit positions or functional positions.
 The 3D representation is realized as a JT monolith.
 The installed components must be individually identifiable in the assembly and it must
be possible to show or hide them.
 The PMI for assemblies reference component geometry elements, such as reference
surfaces, center lines or similar.
 As a minimum, all the surfaces and reference elements necessary for the components
(see above) must be depicted accurately and in full.
 The components of the assembly must be listed as references in the metadata portion
of the DFP container (11.6 p. 28).
11.2 Variants
Variants may take many different forms and be described in very different ways depending on
the specific component and context. In such cases, the variance may relate to different levels
of the product structure such as the product as a whole, individual modules, assemblies and/or
replacement parts. The variance may exist with reference to one specific characteristic or as a
combination of the following and other criteria:
 Geometries within a component (e.g. length of a part)
 Position of components in assemblies (e.g. different fixing points)
 Applicability of individual components for use in an assembly (e.g. a part is sometimes
present and sometimes not)
 Functionality (e.g. different performance parameters for the same geometry, position-
ing and applicability for use)
When describing variance, a distinction is made between the depiction of

 concrete (discrete) variants
 continuous variance or a very large number of variants or range of combinations
The geometrical depiction of individual, concrete (discrete) variants can take one of the
following three forms:
Copyright: VDA
 In a similar way to current drawing views, through the use of suitable views that are
depicted in exactly one 3D portion
 In separate 3D portions within a DFP container
 In separate DFP containers, in which case they are treated as independent compo-
nents
At least one embodiment of this variance must be geometrically depicted in the authoring
system (as a generic depiction) and taken over into the 3D portion The presence of variance
must be made evident in a suitable way, e.g. by indicating dimensions with variables rather
than with exact measurements.
The variance must be documented in one or more tables, i.e. it must be present in the
metadata in the DFP container (XML and PDF representation).
The description of the variants can also be located in the optional elements (e.g. as a table in
PDF form or similar). Where necessary, the descriptions of the variants may be accompanied
by a reference (geometry reference) (annotation in the 3D portion).
Every documented variant must be assigned a unique ID (e.g. a reference number or used-at
location).
Figure 5 Depiction of variants in the DFP container
Figure 5 illustrates the three ways of depicting component variants using one or more DFP
containers In cases 1) and 2), the geometries of the variants are fully modeled and are
explicitly present in the 3D portion.
In 3), the different variants may not be fully modeled. Instead, one or more positions are
depicted by way of an example. These example positions may be, for example, the two end or
extreme positions. In this case, the variants are described via a generation instruction (variant
table). In case 3), all the variants must be depicted in combination in the initial view in the 3D
portion if this contains multiple variants.
11.3 Geometries of connecting faces and adjacent parts

In the context of the present Recommendation, connecting or environment geometry covers
everything that does not belong to the component geometry in the DFP container. It usually
serves to depict edge, installation, fastening constraints or similar requirements in order to
support a so-called "design in context". The depiction of the connecting geometry and adjacent
parts also serves to document the compliance of the components with the (predefined)
boundary conditions or installation environment.
Copyright: VDA
If the connecting geometry and adjacent parts are to be depicted then the following
requirements and recommendations apply:
 They should be represented separately from the actual component geometry and
structure.
 It should be possible to filter them out in the depiction in order to hide them or control
their visibility.
 The geometry of connecting faces or adjacent parts should be represented as a wire
frame.
11.4 Pseudo-mirrored and mirrored parts

A distinction is made between mirrored and pseudo-mirrored parts Mirrored parts have mirror
symmetry, i.e. they can be geometrically mapped 100% using a mirror matrix for generation
purposes. The following requirements and recommendations apply to mirrored parts:
 Mirrored parts can be present in the same DFP container under two different reference
numbers (parts numbers) but with a single 3D portion containing the description of the
geometry and the generation instructions for the mirrored part.
 The fact that the shared 3D portion applies equally to the two reference numbers must
be explicitly documented in the metadata.
 Alternatively, mirrored parts can also be explicitly represented in two separate 3D
portions or even in separate DFP containers. If these alternatives are used then no
generation instructions are needed. However, if they are represented in two separate
DFP containers then the mirrored parts are treated as separate parts.
Pseudo-mirrored parts are mirrored parts with minor constructional differences. The following
requirements and recommendations apply to pseudo-mirrored parts:
 Pseudo-mirrored parts must be explicitly represented and may be located in one and
the same DFP container or separated into two DFP containers.
 If the two parts are located in the same DFP container then a geometry in the 3D
portion contains an annotation indicating the constructional difference.
If each of a pair of mirrored parts or pseudo-mirrored parts is present in a separate DFP

container then the recommendations set out in 11.6 may also apply.
11.5 Components without reference numbers

In the description of the delivery scope, not all the components are managed under a separate
reference number in a separate company context. It is therefore necessary to make it possible
to identify the components that have to be described in greater detail by means of a unique
identifier in the context of the delivery scope. The component identifiers must be listed in the
metadata in the same way as is recommended for assemblies (see 11.1, p. 27). For selected
components, it should be possible to provide not only the identifier but also additional
metadata in the DFP container.
11.6 References to other applicable documents

In a DFP container, it is possible to reference other documents (e.g. other DFP containers,
conventional or simplified drawings, representations of manufacturing stages etc.) that contain
additional information on the current component in the same way as the references currently
included on drawings. These references must be listed, at least in the metadata portion, in the
form of an entry under "other applicable documents".
In addition to the references in the metadata portion, these references can also optionally be
stored in the 3D portion if there is a corresponding reference to the geometry.
Copyright: VDA
Variant parts that are represented in separate DFP containers as described under case 1) in
11.2 (p. 26) should cross-reference one another in the metadata. However, the method used
to do this is component- and company-specific and must be agreed on a case-by-case basis.
Mirrored parts or pseudo-mirrored parts (see 11.4, p. 28) which are represented in separate
DFP containers should each contain a reference to the other, corresponding part.
Other possible use cases for references could be:
 References to the DFP containers of the components in an assembly
 In the case of the constructional differences between pseudo-mirrored parts, it is
possible to indicate a reference to the applicable PMI for the referenced mirrored part,
i.e. all specifications that apply to both parts can be taken from the mirrored part
 Different representations of part variants in which only the variable elements are
present as PMI and everything else is present in the referenced part
However, such use cases may differ greatly and must therefore be agreed on on a case-by-
case basis
12 Application scenarios
Annex C describes examples of typical application scenarios that may occur throughout the
DFP reference process (Figure 2 (p. 9) and Figure 3 (p. 11)) and provides recommendations
that give an overview of the elements present in a DFP container.
Table 1 in Annex C illustrates a possible scenario in the context of a request for proposals in
which an OEM sends a request concerning a component to a supplier.
Table 2 in Annex C presents a possible scenario for the documentation of a finished part to be
supplied to downstream processes as this was previously done with conventional manufactur-
ing and release drawings.
Table 3 in Annex C illustrates a possible scenario for the description of a module as might, for
example, occur between a system supplier and its customer. The focus here is on the
documentation of the key properties of the module and the corresponding constraints relating
to its use and installation. Compared to example scenarios 1 and 2, what is important here is
the provision of the installation and/or environment geometry.
13 Conclusions and prospects

It must be stated in conclusion that it has only been possible in this recommendation to deal
with some of the ideas and suggestions relating to a Drawing-free Process under discussion
when this working group was set up. The reasons for this are presented briefly below.
This recommendation is based on the assumption of a hybrid system environment of the sort
currently found in the participating companies. In a recommendation which is intended to apply
to all VDA member companies, the ability to exchange product information across corporate
and system boundaries must take precedence over single-system solutions.
All currently available commercial CAD systems make it possible to embed the information
which can still be found in technical drawings or is present in the simplified drawing in the 3D
CAD model and display it. This relates to dimensions and tolerances in just the same way as
to properties, notes and technical directives relating to geometry or revision identifications.
With this current Part 2 of the VDA 4953 Recommendation for the Drawing-free Process
(DFP), technical drawings can be completely replaced by a 3D representation accompanied by
an applicable metadata record.
However, some of the neutral CAD and PDM interfaces are not yet capable of transferring the
3D information and metadata referred to above fully and correctly.
Copyright: VDA
Work is being conducted both nationally and internationally in various standardizing bodies in
order to develop uniform procedures for the use of these techniques. One component here is,
for example, ISO 16792 which standardizes 3D depictions. It will be necessary for system
vendors and interface suppliers to work together with user companies in order to implement
the recommendations in an efficient and standardized way.
It must also be remembered that in order to make the intention of the design clear, it is first
necessary to consider the required views of the part or assembly and the information
contained. The procedures and methods for creating (simplified) technical drawings that have
been available for some decades have reached a high level of maturity in terms of application
and data exchange. By bringing with it all the advantages of a purely 3D approach, a similar
level should be achieved in a considerably shorter time through the widespread use of the
Drawing-free Process in accordance with the current Recommendation.
The DFP container represents an alternative to conventional CAD data exchange. The DFP
container makes it possible to exchange 3D design information and the relevant metadata
across corporate and system boundaries by means of standardized formats.
As a transitional solution from simplified drawings (VDA 4953) to the DFP (VDA 4953-2), users
could initially agree, on a case-by-case basis, to use only the container architecture as set out
in 10.1 (p. 24) in combination with a metadata portion and, for the moment, to replace the 3D
portion with a (simplified) drawing (2D representation in a standardized format).
The rapid implementation of the current recommendations on the DFP should be encouraged.
In this way, the DFP container can and should ideally become the binding, primary source of
information during data exchange. When it comes to product data, the DFP container is the
document, the documentation and the "means of transport" all rolled into one. The advantages
of a Drawing-free Process are:
 Cost savings through
 efficient CAD methods
 (complete/partial) elimination of the need to produce, manage and preserve draw-
ings
 protection of investments and simplified data storage
 prevention of the migration of released data content
 attainment of a higher level of system-independence
 faster release and availability of product information as required for simultaneous
engineering
 Improved information provision to the process chain through the simple use and secure
(binding) communication of product-related 3D data and metadata
 Simple, fast revision processes
 Increased process reliability through
 automatable, single-source DFP containers as a single document
 possibility of inherent protection (IPP)
 compatibility for long-term archiving in accordance with VDA 4958
Efforts will be made to ensure the continuous further development of VDA 4953-2 in the light
of all the above-mentioned national and international work that is being conducted in this
sector.
Copyright: VDA
14 Open issues
The current status of VDA 4953-2 has made it possible to identify further open issues,
application scenarios and potentials which may be the object of further development or
harmonization in later versions:
 Interconnection/linking of Design and Production in the field of archiving (compo-
nent/vehicle/assembly-oriented)
 Handling of derived product documents and data
 Quality assurance for DFP containers as required in order to ensure that the contents
of the authoring systems have been correctly and fully represented in the DFP contain-
er.
 Incorporation of the DFP requirements in corporate standardization
 Roll-out of VDA 4953-2 in enterprises and in combination with their partners, i.e. if a
supplier provides DFP then the OEM must also be able to accept the container. Pur-
chasing should be consulted in connection with this requirement
 Extension of the reference process to include the possibility of using DFP containers
for two-way communications, e.g. in order to permit the extension of the information in
the DFP container, for example to include comments (redlining).
 Methods to ensure the IP protection of DFP containers must be developed.
 Mapping of the data requirements (data dictionary Annex B) to the XML schema (STEP
AP242 XML BO)
15 References (other applicable documents)

The relevant standards applicable to the documentation of product data in enterprises will
continue to apply. Relevant international legal requirements must also be observed.
The comments presented in 3 (p. 7) must be observed. The definition of a falsification-proof
version and the joint archiving of the 3D data together with the metadata in accordance with
VDA 4958 must be ensured.
The following also apply:
DIN 2335 German language designations for the alpha-2 code according to ISO
639-1
DIN 6789 Systematic arrangement of documents
DIN 6789-2 Sets of documents for technical product documentation
EN/NAS 9300 LOTAR – Long-term archiving of digital product data
Note: based on ISO 14721 (Open Archival Information System, OAIS) and
VDA 4958 (Long-term archiving)
ISO 7200-1 Technical product documentation - Document headers and title blocks
Part 1: General structure and content
ISO 7200-2 Technical product documentation - Document headers and title blocks
Part 2: Title blocks for mechanical engineering
ISO 10303-242 Managed Model Based 3D Engineering ("STEP")
ISO 16792 Technical product documentation – Digital product definition data
practices
ISO 14306 Industrial automation systems and integration – JT file format specification
for 3D visualization
ISO 19005 Document management – Electronic document file format for long-term
preservation
Copyright: VDA
Part 1: Use of PDF 1.4 (PDF/A-1)

Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)
ISO 32000-1 Document management – Portable document format
Part 1: PDF 1.7
VDA 4953 Simplified CAD drawing, version 2003-11
VDA 4955 Product data quality
VDA 4958 Long-term archiving (LTA) of digital product data which are not based on
technical drawings
16 Glossary
Table 5 below describes terms and abbreviations as used within the context of the Recom-
mendation. Such definitions do not exclude the possibility that these terms and abbreviations
may be understood and interpreted in different ways in other (technical) contexts separate
from VDA 4953.
Term Abb. Definition Equivalent terms
3D portion 3D 3-dimensional form of representation, usually for 3D geometry

3D model the description and depiction of a component. 3D
3D CAD model geometries are usually created using a CAD
system. In VDA 4953-2, the 3D CAD model refers
to the representation of the model in the CAD
authoring system, whereas the 3D model is a
system-neutral representation as represented in the
3D portion of the DFP container.
2D CAD model 2D 2-dimensional form of representation, usually for 2D drawing,

the description and depiction of a component. 2D drawing,
geometries are usually created using a CAD system 2D model
but can also be derived from a 3D geometry and
form the basis for the creation of, or are part of, a
drawing. In VDA 4953-2, the 2D CAD model refers
to the representation of the model or the drawing in
the CAD authoring system.
Assembly A An assembly is a self-contained object consisting of Item, combination
the arrangement of two or more lower-level parts of parts
and/or assemblies in accordance with the
systematic arrangement of documents set out in
DIN 6789.
Component C A component is an individual part (P) or an Part, item
assembly (A)
Standard CS A standard component is a component that is used
component in the fields of technology, construction, electronics
or mechanical engineering and all of whose details
are defined and described in a standard.
Variant CV A component that may occur in various forms and
component whose precise appearance or actual properties are
specified or determined in more detail by the actual
configuration in which it is used.
Copyright: VDA
Computer aided CAD CAD is a computer-assisted working method in the

design fields of development, engineering design and work
preparation which usually includes the sectors of
design, draft design, engineering design, drawing or
drawing derivation.
Data see Information
Database DB A database system is a system for electronic data
(system) management. It consists of two components:
- database management system (DBMS) = the
management software, and
- the database (DB) itself.
A database is a structured set of data that maps
objects with certain properties.
Data consumer DC A data consumer uses the information generated by
a data originator (DO) in the PEP or DFP process
Data originator DO A data originator is responsible for creating or
generating information in the PEP or DFP process
Document DMS A DMS is a database-assisted IT system used to

management manage documents.
system
Part P A part, which cannot itself be further subdivided, of Item, single part
a subassembly (sub-unit), assembly (unit) or a
system/object. A part cannot usually be further
reduced using nondestructive means.
Information Information constitutes the data – including its
interpretation (semantics) – which is under
consideration, i.e. which is of interest in the current
context
Geometric Geo Refers to graphical information and form-related
information in the 3D model. It is characterized by
having a spatial location (x, y, z coordinates).
Non-geometrical nGeo This refers to information that has no specific
geometrical location, e.g. organizational,
technological or process-related information
Geometry- This describes information that refers to geometrical
related information, i.e. that contains a reference (geometry
reference) to the geometry
Identifier ID An attribute that uniquely identifies an object ID number,
identification
Jupiter JT CAD system-independent format for representing
tesselation 3D model data in accordance with ISO 14306
Copyright: VDA
Metadata Metadata consists of the alphanumerical Master data,

information relating to a component or product that PDM data
does not directly serve to describe its shape. This
comprises all the non-geometrical data (e.g.
reference number, designation, material) of a
design-related, technological or organizational
nature but which may also be related to the
geometry (e.g. revision note, partial surface
property).
Metadata record The metadata record contains the geometry- Metadata record,
independent and, by way of an extension to the master data
master data sheet described in VDA 4953, also the record, master
geometry-related metadata for the design. data list, metadata
collection
Product data PDM IT systems used to generate and manage data that PDM, PLM, TDM
management sys- describes the properties and variants of a product system
systems tem as well as data that represents process-related or
organizational aspects.
Product PEP PEP is typically understood to refer to the phases in Product process,
engineering a product lifecycle from the idea for the product product
process through development and on to the manufacture development
and marketing of the product.
Product data PDM Method for administering the product information PDM system
management generated in PEP It also covers the documents that
result from product development.
Product lifecycle PLM Organization of the information in all phases from PLM system
management the product idea through to the point at which the
product no longer exists.
Product PMI Information about a component or product that is Functional
Manufacturing relevant for its manufacture Dimensioning and
Information Tolerancing
(FD&T)
Annotation
Master data The representational form for metadata specified in Metadata sheet
sheet VDA 4953.
STandard for the STEP Standard for the Exchange of Product Data (ISO
Exchange of 10303)
Product model The international STEP standard defines the
data uniform description and exchange of product model
data.
Team data TDM Name of a data management component in a CAx
management system that is used for communication within
(development) teams.
Copyright: VDA
Simplified 2D representational form as set out in VDA 4953.

drawing Usually used to describe the shape of and specify a
component and its properties. In such drawings, the
information content of the drawing is reduced by
relocating the text information to a master data
sheet.
Drawing DRW 2D representational form. Usually used to describe Technical
the shape of and specify a component and its drawing, 2D,
properties. See also 2D CAD model. 2D drawing,
drawing
Drawing-free DFP Drawing-free Process as described in VDA 4953-2
Process based on CAD, PDM and similar systems as well as
on the use of 3D documents instead of technical
drawings.
DFP container Combination of geometrical (3D model), non- 3D document
geometrical and geometry-related data (metadata)
in a system-neutral document in accordance with
VDA 4953-2.
Table 5 Terms and abbreviations
Annexes
Annex A Examples of typical drawing types in the PEP as a function of user group
Annex B Metadata in the DFP (data dictionary)
Annex C Examples of typical application scenarios
Copyright: VDA

"Drawing-Free Product Documentation" Project Group of The VDA's "PLM" Group

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

"Drawing-Free Product Documentation" Project Group of The VDA's "PLM" Group

Încărcat de

Drepturi de autor:

Formate disponibile

VDA Recommendation 4953-2 -1- November 2014

VDA Drawing-free Product Documentation

"Drawing-free Product Documentation" Project Group of the VDA's "PLM"

Published by: German Association of the Automotive Industry (VDA)

11.3 Geometries of connecting faces and adjacent parts ........................................... 27

4 Target groups and potential benefits

4.1 Technical development

4.3 Production planning and control

 Intelligent searches as a result of referencing and IT functions instead of manual

4.4 Operating equipment design

5 Structure of a DFP container and fundamental requirements

The formal structure of a DFP container is described in 10.2 (p. 25).

6 DFP reference process

Figure 2 DFP reference process

6.1 Create content data

6.2 Generate document

6.3 Provide document

6.4 Use document

6.5 Quality assurance

7 Use cases for DFP containers

Figure 3 Example use cases during the utilization of a DFP container

Ite Use cases Brief description Role:

Ite Use cases Brief description Role:

8 Product representation by means of 3D model and metadata

9 Minimum content and implementation

9.1 Minimum content and implementation of the 3D portion

 These must be realized in an identifiable way in accordance with a documented

9.2 Minimum content of the metadata record

Keywords and other information are described in section 10 (p. 22).

9.3 Query capability and machine readability of properties and free

Examples of free texts structured in this way are:

"Recommended Practices" of the CAx Implementor Forum. Any machine readability of

9.4 Multilingual capability

9.5 Grouping of data, control of visibility and filters

10 Information structure in the DFP process

Explanation Main Information Examples

Properties that Function Notes on function Center of rotation, connector,

Notes on specific Material Auxiliary materials Bonding seam using

Explanation Main Information Examples

Surface treatment Specification of surface

Notes on local changes Specification of foam settings

Notes on assembly Assembly Notes on adjacent Reference number

Notes on assembly Maximum tightening torque y

Description of test Operation Technical directives "Insert in transport

Notes on revisions Revision Revision relating to "Rib added"

10.1 Structure of the metadata record

10.2 Architecture of a DFP container

Figure 4 Structure of a DFP container (example: Volkswagen Aktiengesellschaft)

11 Special use cases in the Drawing-free Process

When describing variance, a distinction is made between the depiction of

Figure 5 Depiction of variants in the DFP container

11.3 Geometries of connecting faces and adjacent parts

11.4 Pseudo-mirrored and mirrored parts

If each of a pair of mirrored parts or pseudo-mirrored parts is present in a separate DFP

11.5 Components without reference numbers

11.6 References to other applicable documents

13 Conclusions and prospects

15 References (other applicable documents)

Part 1: Use of PDF 1.4 (PDF/A-1)

Term Abb. Definition Equivalent terms

3D portion 3D 3-dimensional form of representation, usually for 3D geometry

2D CAD model 2D 2-dimensional form of representation, usually for 2D drawing,

Term Abb. Definition Equivalent terms