Space Engineering: Product Data Exchange
Space Engineering: Product Data Exchange
16 April 2010
Space engineering
Product data exchange
ECSS Secretariat
ESA-ESTEC
Requirements & Standards Division
Noordwijk, The Netherlands
ECSS‐E‐TM‐10‐20A
16 April 2010
Foreword
This document is one of the series of ECSS Technical Memoranda. Its Technical Memorandum status indicates
that it is a non-normative document providing useful information to the space systems developers’ community
on a specific subject. It is made available to record and present non-normative data, which are not relevant
for a Standard or a Handbook. Note that these data are non-normative even if expressed in the language
normally used for requirements.
Therefore, a Technical Memorandum is not considered by ECSS as suitable for direct use in Invitation To
Tender (ITT) or business agreements for space systems development.
Disclaimer
ECSS does not provide any warranty whatsoever, whether expressed, implied, or statutory, including, but not
limited to, any warranty of merchantability or fitness for a particular purpose or any warranty that the contents of
the item are error-free. In no respect shall ECSS incur any liability for any damages, including, but not limited
to, direct, indirect, special, or consequential damages arising out of, resulting from, or in any way connected to
the use of this Standard, whether or not based upon warranty, business agreement, tort, or otherwise; whether or
not injury was sustained by persons or property or otherwise; and whether or not loss was sustained from, or
arose out of, the results of, the item, or any services that may be provided by ECSS.
2
ECSS‐E‐TM‐10‐20A
16 April 2010
Change log
0B
3
ECSS‐E‐TM‐10‐20A
16 April 2010
Table of contents
Introduction................................................................................................................6
1 Scope.......................................................................................................................7
4 Provisions .............................................................................................................11
4
ECSS‐E‐TM‐10‐20A
16 April 2010
4.3.7 Source: Human factors engineering ........................................................... 17
4.3.8 Source: Electronics..................................................................................... 17
4.3.9 Source: Electrical power............................................................................. 17
4.3.10 Source: Electro-magnetic compatibility ...................................................... 18
4.3.11 Source: Radio-frequency systems.............................................................. 18
4.3.12 Source: Electrical interfaces and interconnections..................................... 18
4.3.13 Source: Optical ........................................................................................... 18
4.3.14 Source: Mechanical – CAD ........................................................................ 18
4.3.15 Source: Mechanical – Thermal................................................................... 20
4.3.16 Source: Mechanical – Structures................................................................ 20
4.3.17 Source: Mechanical – Mechanisms............................................................ 21
4.3.18 Source: Mechanical – ECLS....................................................................... 21
4.3.19 Source: Mechanical – Propulsion ............................................................... 21
4.3.20 Source: Mechanical – Pyrotechnics ........................................................... 21
4.3.21 Source: Software ........................................................................................ 21
4.3.22 Communication engineering....................................................................... 22
4.3.23 Source: Control engineering....................................................................... 22
4.3.24 Source: Manufacture, assembly, integration and test (MAIT) .................... 22
4.3.25 Source: Materials, mechanical parts and processes .................................. 22
4.3.26 Source: Operations engineering................................................................. 22
Bibliography.............................................................................................................24
Tables
Table 4-1 List of applicable disciplines for product data exchange and their associated
U
5
ECSS‐E‐TM‐10‐20A
16 April 2010
Introduction
1B
This document forms part of the system engineering branch (ECSS-E-10) of the space
engineering area of the ECSS System.
Reliable and easy-to-use exchange of computer-interpretable product data between all
parties, disciplines and persons involved in space projects, is generally recognized as
one of the important means to enable efficient and effective project execution. Product
data in this context comprises all data which specifies one or more aspects of a product
throughout its life cycle.
Reliable electronic exchange of product data cannot be achieved without the
establishment and adoption of formal protocols by the parties exchanging the data. The
present document aims to facilitate the establishment of a set of applicable product data
exchange protocols between the parties participating in a space project.
Throughout the present document, reference is made to many parts of ISO 10303
“Industrial automation systems and integration – Product data representation and
exchange”, more commonly known as the “Standard for the Exchange of Product model
data (STEP)”. ISO 10303 is the most important, global, cross-industry set of standards
for the exchange of product data. The objective of ISO 10303 is explained in the
Introduction of ISO 10303-1:
“ISO 10303 is an International Standard for the computer-interpretable
representation and exchange of product data. The objective is to provide a
mechanism that is capable of describing product data throughout the life cycle of
a product, independent of any particular system. The nature of this description
makes it suitable not only for neutral file exchange, but also as a basis for
implementing and sharing product databases and archiving.”
When reading the present document it is very helpful if the reader has access to
information on the ISO 10303 suite of standards. This information can be obtained from
the national standard bodies representing ISO or from ISO itself and on the world-wide
web from SC4ONLINE. See Clause 2 and Annex A for reference details.
The actual exchange of product data is performed via one of the following processes:
sending and receiving self-contained exchange datasets in off-line mode in the
form of computer files via appropriate media (for example, computer networks,
computer tape cartridges, or CD-ROMs);
by sharing data on-line through standardized data access interfaces to data stores
that are connected to a computer network.
Space project engineering is a multidisciplinary activity employing a wide range of
technologies, with no one person able to master all of the disciplines at the level of
expertise required to ensure a successful outcome. Consequently, resources from a
number of engineering disciplines generally contribute to the engineering process, at
least at the higher levels of complexity.
6
ECSS‐E‐TM‐10‐20A
16 April 2010
1
Scope
3B
This document describes the methods and protocols for the exchange of
computer-interpretable product data in space projects. Product data is defined as all data
that specifies one or more aspects of a product throughout its life cycle. This document
describes which standard protocol to use in what data exchange context by making
reference to existing external standards. It does not cover the contents of any product
data exchange protocol itself.
Two categories of product data exchange are distinguished:
exchange of data between alternative tools used within one discipline, where the
tools share similar functionality, and
exchange of data between tools of different disciplines.
For the second category, in most cases only a subset of the product data represented in
one discipline can be transferred meaningfully to a representation in another discipline.
Explicitly not within this document’s scope are:
identification or availability of software tools to perform product data exchange,
data compression standards, and
data encryption standards.
This document can be applied to all participants in space programmes and throughout
the complete product life cycle. The participants include customers, suppliers and
partners at all levels and from all disciplines.
7
ECSS‐E‐TM‐10‐20A
16 April 2010
2
Normative references
4B
The following normative documents contain provisions which, through reference in this
text, constitute provisions of this ECSS Technical Memorandum. For dated references,
subsequent amendments to, or revision of any of these publications do not apply.
However, parties to agreements based on this ECSS Technical Memorandum are
encouraged to investigate the possibility of applying the more recent editions of the
normative documents indicated below. For undated references, the latest edition of the
publication referred to applies.
8
ECSS‐E‐TM‐10‐20A
16 April 2010
3
Terms, definitions and abbreviated terms
5B
For the purposes of this document, the terms and definitions given in ECSS-S-ST-00-01
apply.
2.2.1 application
group of one or more processes creating or using product data
[ISO 10303-1]
9
ECSS‐E‐TM‐10‐20A
16 April 2010
For the purpose of this document, the abbreviated terms from ECSS-S-ST-00-01 and the
following apply:
Abbreviation Meaning
AP application protocol
BREP boundary representation
CAD computer aided design
CAE computer aided engineering
CAM computer aided manufacturing
CC conformance class
CSG constructive solid geometry
ECLS environmental control and life support
FTP file transfer protocol
IETF Internet Engineering Task Force
RFC request for comment
MAIT manufacturing, assembly, integration and test
PDE product data exchange
PDF portable document format
PDM product data management
SI international system of units - système internationale des unités
NOTE It is specified in ISO 31 and ISO 1000.
STEP standard for the exchange of product model data
. NOTE STEP is the commonly known name
for ISO 10303
10
ECSS‐E‐TM‐10‐20A
16 April 2010
4
Provisions
6B
4.1 Principles
10B
4.1.1 Disciplines
13B
This document describes the protocols to be used for product data exchange between all
relevant combinations of disciplines. The following eight groups of disciplines are
recognized:
system engineering
electrical-electronic
mechanical
software
communications engineering
control engineering
production engineering
operations engineering
Each of these disciplines consists of a number of “subdisciplines” which take care of
specific aspects of the overall system that constitutes a complete space product. For a
presentation of the engineering disciplines involved in a space project see ECSS-S-ST-
00.
Table 4-1 lists the disciplines addressed in the present document for product data
exchange, with their associated ECSS Standards.
11
ECSS‐E‐TM‐10‐20A
16 April 2010
Table 4-1 List of applicable disciplines for product data exchange and their associated
ECSS documents
Discipline Associated discipline-specific ECSS documents
System engineering ECSS-E-ST-10
Space engineering – System engineering general requirements
Configuration and information ECSS-M-ST-40
management Space project management – Configuration and information management
Integrated logistic support ECSS-M-70
Space project management – Integrated logistic support
Mission analysis ECSS-E-ST-10
Space engineering – System engineering general requirements
Space environmental effects ECSS-E-ST-10-04
Space engineering – Space environment
Human factors engineering ECSS-E-ST-10-11
Space engineering – Human factors engineering
Electronics ECSS-E-ST-20
Space engineering – Electrical and electronic
Electrical power ECSS-E-ST-20
Space engineering – Electrical and electronic
Electromagnetic compatibility ECSS-E-ST-20
Space engineering – Electrical and electronic
Radio-frequency systems ECSS-E-ST-50
Space engineering – Communications
Electrical interfaces and ECSS-E-ST-20
interconnections Space engineering – Electrical and electronic
Optical ECSS-E-HB-21
Space engineering – Optical guidelines
ECSS-E-ST-32
Space engineering – Structural general requirements
ECSS-E-ST-10
Mechanical – CAD Space engineering – System engineering general requirements
ECSS-E-ST-32-08
Space engineering – Materials
Mechanical – Thermal ECSS-E-ST-31
Space engineering – Thermal control general requirements
Mechanical – Structures ECSS-E-ST-32
Space engineering – Structural general requirements
Mechanical – Mechanisms ECSS-E-ST-33-01
Space engineering – Mechanisms
Mechanical – ECLS ECSS-E-ST-34
Space engineering – ECLS
Mechanical – Propulsion ECSS-E-ST-35
Space engineering – Propulsion general requirements
Mechanical – Pyrotechnics ECSS-E-ST-33-11
Space engineering – Explosive systems and devices
Software a) ECSS-E-ST-40
Space engineering – Software
Communications ECSS-E-ST-50
Space engineering – Communications
12
ECSS‐E‐TM‐10‐20A
16 April 2010
Discipline Associated discipline-specific ECSS documents
Control engineering ECSS-E-HB-60
Space engineering – Control engineering handbook
ECSS-E-ST-20
Space engineering – Electrical and electronic
Manufacture, assembly, ECSS-E-ST-10-02
integration and test (MAIT) System engineering – Verification
ECSS-E-10-03 b)
System engineering – Testing
ECSS-E-ST-70
Space engineering – Ground systems and operations
ECSS-M-70
Space project management – Integrated logistic support
ECSS-Q-ST-70
Space product assurance – Materials, mechanical parts and processes
Materials, mechanical parts and ECSS-Q-ST-70
processes Space product assurance – Materials, mechanical parts and processes
ECSS-E-ST-10
Space engineering – System engineering general requirements
ECSS-E-ST-32-08
Space engineering – Materials
Operations engineering ECSS-E-ST-70
Space engineering – Ground systems and operations
a)
Exchange of software product data is limited to configuration items as defined in 4.2.3 .
X X
b)
To be replaced by ECSS-E-ST-10-03.
The provisions for product data exchange in the present document are split into two
categories:
general provisions pertaining to all product data exchange;
specific provisions pertaining to product data exchange in a given product data
exchange context.
A product data exchange context is defined by three elements:
a source discipline, which holds the source representation of the product data;
a destination discipline, which receives the data and converts it into its target
representation of the product data;
the intended purpose for the transfer, which describes the product data to be
transferred.
The source and the destination discipline can be the same, in case of exchange of data
between two tools used for one discipline or in case of long term data archiving for one
tool.
The general provisions are given in the clause 4.2.
The specific provisions are given as clauses under clause 4.3, and written in a structured
way. For each discipline listed in Table 1 there is a level 3 clause (4.3.x) which
designates the source discipline. Each source discipline clause contains a collection of
13
ECSS‐E‐TM‐10‐20A
16 April 2010
applicable destination disciplines, referenced as 4.3.x.y. The body of all specific
provision clauses adheres to the following template:
Table (example)
Reference Source Destination Product data to be Standard
representation representation transferred reference to apply
4.3.x.y
a. Throughout all product data exchanges the units for all values of all physical
quantities shall be explicitly specified in the protocol.
b. Throughout all product data exchanges SI units should be used for all values of
physical quantities.
c. The conversion rule from the actually used unit to the equivalent SI unit shall be
explicitly included in the protocol, in case the values of physical quantities are
not specified in SI units.
d. The conversion of units should conform to ISO 31 and ISO 1000.
e. If the conversion rule deviates from ISO 31 or ISO 1000 the origin of the
conversion rule shall be specified.
f. The applicable units and conversion rules shall be specified and agreed prior to
starting exchange of data by the parties involved the data exchange.
NOTE The specification is usually initiated by the sending
party.
a. The media for transfer of the product data to be exchanged shall be agreed by the
parties involved.
NOTE Example: Suitable media are, for example, CD-ROM,
4 mm DAT cartridge, and FTP server connected to the
Internet.
14
ECSS‐E‐TM‐10‐20A
16 April 2010
15
ECSS‐E‐TM‐10‐20A
16 April 2010
management
a. To transfer product data from an information-documentation management
representation to the destination representations and for the product data stated in
Table 4 , the standard references specified in such a table shall be used.
b. In the case specified in Table 4-4, reference 4.3.3.1, the applicable CC shall be
mutually agreed.
16
ECSS‐E‐TM‐10‐20A
16 April 2010
The standard reference to be used to exchange data from a space environmental effects
representation to any applicable discipline listed in Table 4-1 is presently under
consideration.
The standard reference to be used to exchange data from a human factors engineering
representation to any applicable discipline listed in Table 4-1 is presently under
consideration.
17
ECSS‐E‐TM‐10‐20A
16 April 2010
interconnections
The standard reference to be used to exchange data from a electrical interfaces and
interconnections representation to any applicable discipline listed in Table 4-1 is
presently under consideration.
The standard reference to be used to exchange data from a optical representation to any
applicable discipline listed in Table 4-1 is presently under consideration.
18
ECSS‐E‐TM‐10‐20A
16 April 2010
Table 4-8 Data transfer from a mechanical – CAD representation
Destination
Source representati Product data to be Standard reference
Reference representation on transferred to apply
4.3.14.1 Mechanical - CAD Configuration PDM data: configuration ISO 10303-203 CC1
management controlled design information
(1) without shape
4.3.14.2 Mechanical - CAD Integrated PDM data: configuration ISO 10303-203 CC1
logistic support controlled design information
(1) without shape
4.3.14.3 Mechanical - CAD Mechanical – Configuration controlled design ISO 10303-203 CC4
CAD (1) information and shapes
represent-ed by manifold
surface models with topology
4.3.14.4 Mechanical - CAD Mechanical – Configuration controlled design ISO 10303-203 CC5
CAD (2) information and shapes
represent-ed by facetted
boundary-representation
models
4.3.14.5 Mechanical - CAD Mechanical – Configuration controlled design ISO 10303-203 CC6
CAD (3) information and shapes
represent-ed by advanced
boundary-representation
models
4.3.14.6 Mechanical - CAD Mechanical – Component design with 3D ISO 10303-214 CC1
CAD (4) shape
4.3.14.7 Mechanical - CAD Mechanical – Assembly design with 3D ISO 10303-214 CC2
CAD (5) shape
4.3.14.8 Mechanical - CAD Mechanical – Component drawings with ISO 10303-214 CC3
CAD (6) wireframe or surface shape
representation
4.3.14.9 Mechanical - CAD Mechanical - Assembly drawings with ISO 10303-214 CC4
CAD (7) wireframe, surface or solid
shape representation
4.3.14.10 Mechanical - CAD Thermal 3D surface shape models ISO 10303-203 CC4
analysis (1)
4.3.14.11 Mechanical - CAD Thermal 3D explicit shape models with ISO 10303-203 CC6
analysis (2) advanced BREP for thermal
radiative analysis
4.3.14.12 Mechanical - CAD Mechanical – 3D explicit shape model with ISO 10303-203 CC6
Structures (1) advanced BREP
4.3.14.13 Mechanical - CAD Mechanical – 3D CSG model ISO 10303-214 CC4
Structures (2)
4.3.14.14 Mechanical - CAD Ground PDM data: configuration ISO 10303-203 CC1
systems and controlled design information
operations (1) without shape
4.3.14.15 Mechanical - CAD Ground 3D explicit shape model with ISO 10303-203 CC6
systems and advanced BREP for shape
operations (2) representation
19
ECSS‐E‐TM‐10‐20A
16 April 2010
20
ECSS‐E‐TM‐10‐20A
16 April 2010
Table 4-10 Data transfer from a mechanical-structures representation
Standard
Source Destination Product data to be reference to
Reference representation representation transferred apply
4.3.16.1 Mechanical - Mechanical – CAD (1) 3D explicit shape model ISO 10303-203
Structures with advanced BREP for CC4
structural analysis
4.3.16.2 Mechanical - Mechanical – CAD (2) 3D CSG model for ISO 10303-214
Structures structural analysis CC4
4.3.16.3 Mechanical - Mechanical – Structures Linear static finite element ISO 10303-209
Structures (1) analysis model
21
ECSS‐E‐TM‐10‐20A
16 April 2010
Table 4-11 Data transfer from an electrical power representation
Standard
Source Destination Product data to be reference to
Reference representation representation transferred apply
4.3.21.1 Software Configuration PDM data: ISO 10303-203
management (1) Configuration controlled design CC1
information without shape
4.3.21.2 Software Integrated logistic PDM data: ISO 10303-203
support (1) Configuration controlled design CC1
information without shape
processes
The standard reference to be used to exchange data from a materials, mechanical parts
and processes representation to any applicable discipline listed in Table 4-1 is presently
under consideration.
22
ECSS‐E‐TM‐10‐20A
16 April 2010
Annex A (informative)
References to electronic copies
At the time of the publication of the present document, electronic copies of referenced
documents can be found at:
ISO-website The official website of ISO. For electronic copies of documents
http://www.iso.ch
U
ions/PDFReference.pdf
23
ECSS‐E‐TM‐10‐20A
16 April 2010
Bibliography
2B
24
ECSS‐E‐TM‐10‐20A
16 April 2010
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 Industrial automation systems and integration - Product
data representation and exchange - Part 214: Application
protocol: Core data for automotive mechanical design
processes
ISO 10303-232:2002 Industrial automation systems and integration - Product
data representation and exchange - Part 232: Application
protocol: Technical data packaging core information and
exchange
STEP-TAS STEP-based Application Protocol - Thermal Analysis for
Space - ESA/ESTEC 1 )
F F
PDF Reference, 3rd PDF Reference, 3rd Edition, Adobe Portable Document
Edition 1) Format, Version 1.4
1)
See download information in Annex A.
25