EN 9300-003:2012

SLOVENSKI STANDARD
01-april-2014
$HURQDYWLND/27$57UDMQRDUKLYLUDQMHLQ]DJRWDYOMDQMHGLJLWDOQHWHKQLþQH
GRNXPHQWDFLMHNRWVR'&$'LQSRGDWNL3'0GHO2VQRYHLQSRMPL
Aerospace series - LOTAR - Long term archiving and retrieval of digital technical product
documentation such as 3D, CAD and PDM data - Part 003: Fundamentals and concepts
Luft- und Raumfahrt - Langzeitarchivierung und Bereitstellung digitaler technischer
Produktdokumentationen beispielsweise 3D CAD und PDM Daten - Teil 003: Grundlagen
und Konzepte
Série aérospatiale - LOTAR - Archivage long terme et récupération des données
techniques produits numériques, telles que CAD D et PMD - Partie 003: Fondamentaux
et concepts
Ta slovenski standard je istoveten z: EN 9300-003:2012
ICS:
01.110 7HKQLþQDGRNXPHQWDFLMD]D Technical product
L]GHONH documentation
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 9300-003
NORME EUROPÉENNE
EUROPÄISCHE NORM
September 2012
ICS 01.110; 35.240.30; 49.020
English Version
Aerospace series - LOTAR - Long term archiving and retrieval of
digital technical product documentation such as 3D, CAD and
PDM data - Part 003: Fundamentals and concepts
Série aérospatiale - LOTAR - Archivage long terme et Luft- und Raumfahrt - LOTAR - Langzeit-Archivierung und -
récupération des données techniques produits numériques, Bereitstellung digitaler technischer
telles que CAD D et PMD - Partie 003: Fondamentaux et Produktdokumentationen, wie zum Beispiel von 3D-, CAD-
concepts und PDM-Daten - Teil 003: Grundlagen und Konzepte
This European Standard was approved by CEN on 10 March 2011.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2012 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 9300-003:2012: E
worldwide for CEN national Members.

Contents Page
Foreword . 4
1 Scope . 5
2 Normative references . 5
3 Terms, definitions and abbreviations . 6
4 Major differences of terms . 6
4.1 Introduction . 6
4.1.1 General . 6
4.1.2 Invariance . 6
4.1.3 Objectives for keeping digital data . 6
4.1.4 Length of time of keeping data. 7
4.1.5 Stored Form . 7
4.2 Terminology . 8
4.2.1 General . 8
4.2.2 Product information model . 8
4.2.3 Product model . 9
4.2.4 Business Application . 9
4.2.5 Retention .10
4.2.6 Long Term Archiving .10
4.3 Scope of EN 9300 .11
4.4 Relation to Legal Admissibility Standards .12
5 Applicability.13
6 Overview of referenced standards .13
6.1 General .13
6.2 Introduction to OAIS — ISO 14721 .13
6.2.1 General .13
6.2.2 The OAIS Environment .14
6.2.3 The OAIS model .14
6.3 Introduction to ISO 10303 .15
6.3.1 General .15
6.3.2 ISO 10303-203:1994 and Edition 2 draft, Configuration controlled 3D designs of
mechanical parts and assemblies.17
6.3.3 ISO 10303-214:2001 and ISO 10303-214:2003, Core Data for Automotive Mechanical
Design Processes .17
6.3.4 ISO 10303-233, System engineering data representation .18
6.3.5 ISO 10303-209:2001, Composite and metal structural analysis and related design.18
6.3.6 ISO 10303-237, Computational fluid dynamics .18
6.3.7 ISO 10303-210:2001 and Edition 2 draft, Electronic assembly, interconnect and packaging
design .18
6.3.8 ISO 10303-212:2001, Electro technical design and installation .18
7 Fundamentals and concepts .18
7.1 Overview .18
7.2 Processes .20
7.3 Data .20
7.3.1 Archiving Product Models vs. Archiving Documents .20
7.3.2 Data content .22
7.3.3 Data formats .24
7.3.4 Archiving approach for complex product models .25
7.3.5 Data quality assurance .25
7.3.6 Process phases and cycles . 27
7.4 Mapping approach onto physical data representations . 30
7.5 Fundamentals for testing the LOTAR process and components . 31
7.6 System Architecture Framework . 33
8 Description methods . 33

Foreword
This document (EN 9300-003:2012) has been prepared by the Aerospace and Defence Industries Association
of Europe - Standardization (ASD-STAN).
After enquiries and votes carried out in accordance with the rules of this Association, this Standard has
received the approval of the National Associations and the Official Services of the member countries of ASD,
prior to its presentation to CEN.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by March 2013, and conflicting national standards shall be withdrawn at
the latest by March 2013.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
This standard was prepared jointly by ASD-STAN and the PROSTEP iViP Association.
The PROSTEP iViP Association is an international non-profit association in Europe. For establishing
leadership in IT-based engineering it offers a moderated platform to its nearly 200 members from leading
industries, system vendors and research institutions. Its product and process data standardization activities at
European and worldwide levels are well known and accepted. The PROSTEP iViP Association sees this
standard and the related parts as a milestone of product data technology.
Users should note that all standards undergo revision from time to time and that any reference made herein to
any other standard implies its latest edition, unless otherwise stated.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece,
Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

1 Scope
This European Standard defines basic terms, e.g. Long Term Archiving and Retention and identifies the
context and scope of EN 9300. The section Fundamentals describes the basic concepts and approaches of
EN 9300 and referenced related standards.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
EN 9103, Aerospace series — Quality management systems — Variation management of key characteristics
*
EN 9300-007 , Aerospace series — LOTAR — Long Term Archiving and Retrieval of digital technical product
1)
documentation such as 3D, CAD and PDM data — Part 007: Terms and references
ISO 10303-203:1994 and Edition 2 draft, Industrial automation systems and integration — Product data
representation and exchange — Part 203: Application protocol: Configuration controlled 3D designs of
mechanical parts and assemblies
ISO 10303-209:2001, Industrial automation systems and integration — Product data representation and
exchange — Part 209: Application protocol: Composite and metallic structural analysis and related design
ISO 10303-210:2001, Industrial automation systems and integration — Product data representation and
exchange — Part 210: Application protocol: Electronic assembly, interconnection, and packaging design
ISO 10303-212:2001, Industrial automation systems and integration — Product data representation and
exchange — Part 212: Application protocol: Electrotechnical design and installation
ISO 10303-214:2001 and ISO 10303-214:2003, Industrial automation systems and integration — Product data
representation and exchange — Part 214: Application protocol: Core data for automotive mechanical design
processes
ISO/DIS 10303-233, Industrial automation systems and integration — Product data representation and
1)
exchange — Part 233: Systems engineering data representation
ISO 10303-237, Industrial automation systems and integration — Product data representation and
1)
exchange — Part 237, Application protocol: Fluid dynamics
ISO 14721, Space data and information transfer systems — Open archival information system — Reference
model
ARP9034, A Process Standard for the Storage, Retrieval and Use of Three-Dimensional Type Design Data
BP 0008, Code of Practice for Legal Admissibility and Evidential Weight of Information Stored electronically

*
And all parts quoted in this standard.
1) In preparation at the date of publication of this standard.
3 Terms, definitions and abbreviations
For the purposes of this document, the terms, definitions and abbreviations given in EN 9300-007 apply.
4 Major differences of terms
4.1 Introduction
4.1.1 General
Different user communities have different definitions for long term archiving and retention. This clause
explains the major differences of both terms and their relation to the scope of EN 9300.
Companies within the aerospace industry need to keep data to fulfil business, certification and legal
requirements. For modern definitions this data is usually digital. These requirements lead to four main areas of
consideration regarding the retention of digital data.
 Invariance: how important is it to ensure that digital data is not altered
 Objectives: why keeping of digital data is required
 Length of time: the required length of time for retaining digital data
 Stored Form: the stored format of the digital data
The following subchapters consider these questions for long term archiving and retention and are the basis for
the scope definition of EN 9300. The scope of EN 9300 is a combination of aspects from long term archiving
and retention.
4.1.2 Invariance
Invariance covers the need to ensure that the information has not changed and so provide evidential weight
that the design intent has not changed, see Figure 13. Three categories can be distinguished:
 Auditable – where validation methods and test suites ensure that information cannot be changed without
the change being detected.
 Implicit – where the system is designed to prevent changes. The system must supervise activities which
would result in changes of the digital data. The supervision, for example, could be realized within a
separate write-protected vault. The proof of "no change" is shown by an absence of change having been
recorded AND that by showing that the system itself is reliable.
 Not required – where changes to data are not explicitly controlled.
Of the three, auditable invariance is the strongest, and is likely to be the most suitable where the information is
used in legal proceedings.
4.1.3 Objectives for keeping digital data
For digital data, the challenge is that the data are often stored in a proprietary, native format and will most
likely become not interpretable after a time. The use of a neutral archiving data format safeguards the
interpretability of the stored data for a much longer time, perhaps for the entire retention period. EN 9300
recommends the use of standard formats for long term archiving rather than native formats, accompanied by
regular and frequent migrations of storage media and, if necessary, of data format. Because a data migration
may lead to data loss, usually time stamps and digital signatures (which are used ensuring the integrity and
immutability of archived data/ data packages) have to be renewed. The use of auditable archiving and
retrieval processes ensures the data readability and integrity within current and future systems.
The objectives for keeping the data are distinguished into two major subcategories:
 Legal requirements/certification requirements, such as for proof of technical documentation for actions in
law.
 Business requirements, such as keeping knowledge.
Within the two subcategories EN 9300-003 offers four characteristics which describe the objectives in more
detail:
 To preserve the original data (generated by a source system) so that it can be used as evidence of what
data was at a particular date. This characteristic fits with the subcategory ‘legal requirement’
 To keep data available to new users over the period for which it is kept. This characteristic fits with the
subcategories ‘legal requirement’ and ‘business requirement’.
 To be able to preserve the source of the kept data. This characteristic fits with the subcategory ‘business
requirement’.
 To be able to reuse the data, for example, by modifying design data to meet new requirements. This
characteristic fits with the subcategory ‘business requirement’.
4.1.4 Length of time of keeping data
The life cycle of software and hardware is relatively short compared to the life cycle of aircraft. The life cycle of
digital data can be described in terms of software versions and generations. The release of a new software
version within a generation general alters only a small part of the functionalities of the software without
affecting the data format. A generation change occurs when the software used changes substantially, for
example, to a new architecture. The change of a generation may result in new data formats.
Currently, for CAD software, the period between versions is of the order of 6 months to 12 months, while
between generations is of the order of 3 years to10 years. This should be compared to an aircraft life cycle
which may be 30 years to 50 years or longer. This gives rise to the following definitions within EN 9300:
 Short term - within one or two versions
 Medium term - within one generation
 Long term - over multiple generations
Additionally to the technical aspects, legal requirements have to be considered when defining archiving terms.
For further information see EN 9300-001 (Structure) and EN 9300-002 (Requirements).
4.1.5 Stored Form
4.1.5.1 General
A key distinction is between a representation and a presentation. In a representation, the computer holds the
information about the concept, whereas in a presentation the computer holds a form which is its appearance
to a human. For example, a musical score is a representation of a piece of music, whereas a recording of the
piece is a presentation.
The stored form has been divided into three main subcategories:
 Detail Level: the description level of model;
 Representation: describing the different logical forms of data representation;
 Format: describing the different physical formats of the data.
4.1.5.2 Detail level
 An accurate representation is where data elements are described in the original level of detail,
independent of whether they are represented in a native or other format;
 An approximate representation is where data elements are described in a lower level of detail than the
accurate representation, e.g. where a curved surface is approximated by a set of small, flat faces.
4.1.5.3 Representation
 A native representation is that created by and private to the source system;
 A derived representation is a transformation of the native data, which may be based on a native format or
on a standardized format, e.g. a html version may be derived from a text document as an alternative
representation;
 A presentation is a visualization of data to a user, e.g. a drawing or a print out of product structure
information as a snapshot of the current data representation.
4.1.5.4 Format
 A native format is a specific format of data in a syntax which is proprietary and dependent on a specific
system or interface. A native format depends directly on the life cycle (versions, generations) of the
related system or interface;
 A standardized open format is a format of data in a syntax, which is defined by a broad community, such
as by ISO, and which is independent of specific system or interface. “Open” means completely and
precisely documented in syntax and semantics and is applicable for free. In addition, standardisation
processes regulates the change processes for the standard.
Note that the motivation for including the accurate and approximate representation is that both may be
archived in parallel in a standard representation such as STEP, which is openly documented and which may
be stable for a much longer period than native formats.
4.2 Terminology
4.2.1 General
From descriptions in 4.1, the following definitions of terms are derived: Product information model, Product
model, Business Application, Retention and Long Term Archiving. These definitions are used within EN 9300.
4.2.2 Product information model
The Product information model represents an information model which provides an abstract description of
2)
facts, concepts and instructions about a product, e.g. STEP Application reference model or STEP
Application interpreted model.

2) ISO 10303-1:1994
4.2.3 Product model
The Product model represents an occurrence of a product information model for a particular product, e.g. the
geometric model of part a123. Companies will create product models of different types, depending on the life
cycle stages or disciplines, e.g. there are product models of type "space allocation mock up". Product models
are independent from their presentation.
As a further determination EN 9300 distinguishes:
 A dynamic or temporary Product Model (in internal memory of the computer),
 The static Product Model (e.g. represented as a file or as a data base on permanent storage media, such
as disks or tapes);
Product Models can be consulted and queried via applications only via the loading of the static form of the
Product Model into the dynamic form in memory of the same Product Model.
Additionally there are different usages of a Product Model, optimized for different functions/users intents.
EN 9300 distinguishes:
 the Working Form Product Model, used for creation & modification by the native application; it
corresponds generally to the design stage of the Product Model; this Working Form is often in the native
format of the COTS (Component off the shelf ) application.
 the Original Product Model, used specially to keep the design intent for Long Term Archiving in the
context of certification & legal requirements for proof. It can be stored in a native or standardized format.
Based on these definitions, EN 9300 recommends the archiving for long term of the original & accurate
Product Models in a static standardized open format like STEP. These Product Models, after retrieval, will
be loaded in applications as temporary dynamic form, enabling the check of validation properties and
specified operations (consultation, …)
In the scope of EN 9300, an application is a piece of software, which allows processing the Product Model
according to a dedicated purpose. This purpose can be:
 the visualisation with possible 3D measurement,
 a type of simulation (FEA, aerodynamics, …),
 NC programming for Manufacturing,
 …
4.2.4 Business Application
Typically, a Business Application is the software X generating native Product Models for creation and
modifications that will have to be converted in a standardized Product Model for Long Term Archiving.
Examples of Business Applications relevant for CAD Product Models are: Unigraphics, Catia V5, CADDS5,
Pro/Engineer, … Other examples of Business Applications relevant for PDM Product Models are: VPM,
Metaphase, Enovia, Windchill, …
The starting point of the Long Term Archiving activity for a special type of Product Model is the description of
Use Cases that the Retrieved Product Model will have to support. Some Use Cases for Long Term Archiving
of 3D Definition models will result in visualisation of information. Other Use Cases for Long Term Archiving of
Finite Element Analysis models may result in replaying the simulation, in order to demonstrate that the sub
assembly support the associated load cases.
See the next Figure 1 illustrating the types of functions of Business applications for Product Model processing.

Figure 1 — Example for retrieve use case for specification of long term retention
4.2.5 Retention
“Retention”: Storage of data for reuse of a later date:
 aiming for data re-use and to keep data available;
 retaining any of the representations needed, but not the presentations;
 working over medium and short term;
 expecting invariance, though this is not mandatory;
 migration of the data format is allowed to guaranty data quality and interpretability.
4.2.6 Long Term Archiving
“Long Term Archiving”: Storage of a copy of data in an appropriate way for record, certification and legal
purposes.
 The data will be preserved and kept available for a use within the archive and possibly for further re-use.
 With certified conversion processes, the native data representation generated by the source system can
be converted into a representation which is appropriate for long term archiving. To fulfil legal and
certification requirements, the stored form can be an accurate or approximate representation of the
source.
 Integrity must be ensured by a digital signature.
 The data is retained over the long term.
 Invariance is mandatory.
 Business, legal and certification requirements are covered.
The relation of these two terms to the concepts is shown in the following Figure 2.

Figure 2 — Retention and Long Term Archiving
4.3 Scope of EN 9300
According to definitions of previous clauses, the scope of EN 9300 can be described as follows:
 The reasons for archiving of digital data include business and certification as well as legal requirements,
keeping data available for re-use and preserving the original information
 An accurate representation is retained. An approximate representation may be retained as a means of
validating the geometry of files recovered from storage. Keeping the native representation is relevant only
for short and medium terms. A visualization (a presentation) supports the retrieval process and is
optional.
 Retention is for the long term.
 Invariance must auditable to fulfil business and certification requirements.
The following Figure 3 gives an overview of the scope for EN 9300.

Key
a ←  mandatory
b ←     optional
Figure 3 — Scope of EN 9300
Within Figure 3 the mandatory aspects of the scope are illustrated via a solid line with arrow, whereas the
optional aspects of the scope for EN 9300 are illustrated via a dashed line with arrow.
4.4 Relation to Legal Admissibility Standards
"Code of Practice for Legal Admissibility and evidential weight of information stored electronically"
Existing standards, such as BP 0008, "Code of Practice for Legal Admissibility and Evidential Weight of
Information Stored electronically" provide a detailed guide to the business practices and processes needed to
give legal weight to electronic documents. In so far as they provide a general framework, these are not only
compatible with LOTAR, but provide a context for LOTAR, both for the stages of the information life cycle
outside of the processes defined in LOTAR, and within the archive itself.
The EN 9300 series is primarily concerned with preserving model information, rather than documents, in
which the software used to generate and manipulate the data embeds a high level of knowledge about the
data and its structure. Experience in CAD and PDM data exchanges has shown that transfer of data between
systems and between different generations of systems can be prone to a degree of error which is
unacceptable in a high integrity product such as an aircraft. The EN 9300 series explicitly recognises these
risks, and provides mitigation through an explicit archive (from the OAIS standard, see Clause 6), through
identification of stable, public and well defined information standards (primarily ISO 10303, see Clause 6) and
though the identification of validation methods to ensure that the model recovered conforms to the model
stored.
5 Applicability
This EN 9300-003 is applicable to existing records, on current and earlier products, produced using previous
regulations.
6 Overview of referenced standards
6.1 General
To fulfil the scope description for long term archiving described in 4.3, EN 9300 is based on international
standards. The use of international standards raises the level of acceptance for the designated community,
and the level of interoperability between systems and data formats. The use of standards improves the length
of time the data may be kept, simplifies the definition of processes, system architecture and implementation,
as well as reduces costs by modularisation and component re-use based on standardized interfaces.
Furthermore EN 9300 has the objective of a harmonization of requirements and approaches with the
international aerospace community, as already started with the IAQG Initiative (P03/04 “Long Term Archiving
and Retrieval of Design & PDM Data”) which harmonizes EN 9300 and the SAE Aerospace document
ARP9034. By adapting the OAIS ISO standard further harmonization may be possible with other sectors such
as the automotive or ship industry.
EN 9300 references extensively ISO 14721 "Open reference model for Archiving Information System" (OAIS)
and ISO 10303 (STEP).
6.2 Introduction to OAIS — ISO 14721
6.2.1 General
OAIS is a framework describing the significant entities and relationships among entities in an archive
environment.
An OAIS-type archive is expected to meet certain minimum responsibilities:
 negotiate and accept appropriate information from information producers;
 obtain sufficient control of the information to ensure long term preservation;
 determine the scope of the Designated Community;
 ensure the information is understandable by the Designated Community without the assistance of the
information producers;
 follow documented policies and procedures to ensure the information is preserved against reasonable
contingencies, and to enable the information to be disseminated as authenticated copies of the original or
as traceable to the original;
 make the information available to the Designated Community.
The OAIS reference model details a conceptual design for an archive, including its primary components and
their associated functions and relationships, to support these requirements.
6.2.2 The OAIS Environment
The OAIS environment is derived from the interaction of four roles: producers, consumers, management and
the archive itself.
Producers supply the information that the archive preserves.
Consumers use the preserved information. A special class of consumers is the Designated Community that is
a subset of consumers who are expected to understand the archived information.
Management is responsible for establishing the broad policy objectives of the archive (e.g. determining what
types of information are to be archived, identifying sources, etc.). Management does not include the day-to-
day administration of the archive; this task is performed by a functional entity within the archive itself.
The Archive, see Figure 4.
Figure 4 — OAIS Environment
6.2.3 The OAIS model
OAIS standardizes a reference model for a system architecture of archiving systems and processes.
The OAIS functional model is shown in Figure 5.
Figure 5 — Functional Model of OAIS
OAIS focuses on the five main process modules: Preservation Planning, Data Management, Access, Ingest
and Administration. The basic functions of process module Archival Storage is assumed by EN 9300 to be
already covered by existing archival systems (Data base, Storage, Media, etc.). The process module Archival
Storage will be extended by EN 9300 with functionality of setting digital time signatures. If not explicitly
extended by EN 9300 the remaining process modules ‘Data Management’ and ‘Administration’ are covered by
OAIS and are out of scope for the EN 9300 series.
OAIS offers a framework for the significant entities and relationships. OAIS makes NO recommendations
about the definition of an archiving format, or resulting minimum subsets for archiving of, e.g., 3D geometry
models and PDM information, or about process definitions like e.g. activity sequences, security aspects,
business and legal requirements of long term archiving. Therefore EN 9300 extends OAIS and does not
replace it.
6.3 Introduction to ISO 10303
6.3.1 General
ISO 10303 is generally referred to as the STandard for the Exchange of Product model data (STEP)
ISO 10303 is an international standard for the computer sensible representation and exchange of product
data. The objective is to provide a mechanism capable of describing product data throughout the lifecycle of a
product, independent of any particular system. The nature of this description makes it suitable not only for file
exchange, but also as a basis for implementing and sharing product databases and archiving. (See Figure 6)
Key
1 implementation implementations methods for data exchange and integration
2 description method for product data (EXPRESS)
3 neutral building blocks for product description
4 application-oriented data models for product description (e.g. AP214, AP212, AP203)
5 methods for testing of STEP implementations
Figure 6 — Overview about Structure of ISO 10303
The key approach of the standard is to apply STEP methods to transform real (product) data descriptions into
a neutral format for long term archiving without loss of meaning. The following Figure 7 illustrates an approach
for mapping the mathematical description of two circles to STEP.
Figure 7 — Application example, formal schema definition and mapping onto Part 21 file format
The STEP development community is working to ensure these standards to support international product
model exchange and sharing requirements. The aerospace community is participating to ensure that their
product model data can be applied to support real business processes.
Integrated Resource parts in STEP address, geometry, materials, tolerances, configuration management, and
other general requirements.
The following subsections describe the most relevant Application Protocols (AP) within the development of
EN 9300 Common PARTS. A further extension of the list is possible.
6.3.2 ISO 10303-203:1994 and Edition 2 draft, Configuration controlled 3D designs of mechanical
parts and assemblies
AP 203 is used to exchange geometry, product structure, and configuration management data between
almost all business processes. It is supported by every major CAD vendor and several Product Data
Management vendors. The draft version of Edition 2 (available since 2003) will be modular and adds
tolerances, construction history, layers, validation properties and colours to the 3D exchanges.
6.3.3 ISO 10303-214:2001 and ISO 10303-214:2003, Core Data for Automotive Mechanical Design
Processes
AP 214 (Edition 2) is used to exchange and share geometry, drawing, geometric tolerances & dimensions,
product structure, configuration management, generic product structure, presentation, validation properties,
kinematics and process plan data. It is supported by every CAD vendor and several Product Data
Management vendors. It is used routinely by the Automotive industry and the European aerospace industry.
AP 203 Edition 2 is compatible with AP 214 for the common scope (both are harmonized by the PDM Schema
which builds the core of the new modular architecture of STEP standards).
6.3.4 ISO 10303-233, System engineering data representation
AP 233 addresses the need to exchange system representations at the aircraft or spacecraft level. The scope
includes: conformity to the concept of a system; configuration control; requirements, requirement analysis; and
functional allocation/analysis/ behaviour; and physical architecture.
6.3.5 ISO 10303-209:2001, Composite and metal structural analysis and related design
AP 209 specifies computer-interpretable composite and metallic structural product definition data
representation such as: shape, idealized analysis shape, finite element analysis (FEA) model, analysis results,
and material properties. The design and related analysis information are managed within a PDM product
structure.
6.3.6 ISO 10303-237, Computational fluid dynamics
AP 237 defines a data representation for the exchange of fluid dynamics data. The information within scope
includes: digital flow field data, surface data, and integrated data from (1) analysis and computation, (2)
ground test (e.g., wind tunnel test), and (3) flight test. The first edition focuses on data related to analysis and
computation.
6.3.7 ISO 10303-210:2001 and Edition 2 draft, Electronic assembly, interconnect and packaging
design
AP 210 specifies the data representation for printed circuit card design. This includes: physical layout of the
printed circuit card assembly; description of the connection among functional objects, packaged parts, and the
physical interconnection; configuration management; and actual parameters for parts and functional objects.
6.3.8 ISO 10303-212:2001, Electro technical design and installation
AP 212 is a STEP exchange standard that specifies data representation for electro technical plants and
industrial systems design information. It addresses electrical product definition necessary to support electrical
and cable tray: current analysis; equipment; lighting; cable sizing; electrical connectivity checks; and cable
tray interference detection.
7 Fundamentals and concepts
7.1 Overview
The fundamentals of this standard aim to assure the integrity of data and the authenticity of the associated
provenance information. This is considered under four headings:
 Definition of processes (EN 9300-010 – 01x)
 Definition of data content (EN 9300-1xx and 2xx)
 Definition of data formats and description methods for data conversion (EN 9300-1xx and 2xx)
 Definition of test suites and description of certification methods (EN 9300-016)
The starting point for an archival procedure is the business case for archiving information. This is elaborated
through a series of use cases for which one or more core data models are defined. These core models
capture the information required by the business case. The following Figure 8 provides an overview.

Figure 8 — Distinction of Business requirements, Business Cases and Use Cases
Process views are given for Data Preparation, Ingest, Archival Storage and Retrieval, in which validation steps
and methods are clearly defined (Parts in the series EN 9300-010 to 019). These views are normative within
the scope of the view.
To ensure the integrity of data after conversion, data content, data quality and validation properties are
defined (Parts in the EN 9300-1xx and 2xx series).
The definition of data formats and their associated description methods helps ensure the integrity of the
transformations between the source system, the archive and the consumer system (Also covered in the Parts
in the EN 9300-1xx and 2xx series).
The test suites and certification methods (EN 9300-016) verify that the archive correctly implements the
recommendations of other parts of the standard.

SIST EN 9300-003:201
...