Standard Practice for Additive Manufacturing - General Principles - Overview of Data Pedigree

SIGNIFICANCE AND USE
5.1 This standard can be used by AM data-system developers to design or update a database that meets business and process requirements. The information modules provide a foundation for an AM data structure. Standard definitions of data elements, their data types, and allowable values can be used directly to define the attributes for AM databases.  
5.2 This standard is intended for organizations and personnel who wish to share AM data or who develop AM data management systems. The information modules defined in this standard represent a primary set of AM concepts. These concepts can be used to develop a common data model and a common data-exchange format, thereby enabling the transfer of data between different AM data management systems. Since legacy AM data management systems may use different data element definitions, translators will be needed to map their proprietary data into the common data exchange format. This common format will support both exporting from and importing to the original native formats.  
5.3 This standard serves as the source for creating common definitions of and representations for all the AM data elements that have been agreed-upon by the community. Previously, standard definitions existed for only a few, high-level, data elements. This limited the ability of organizations to share AM data elements that were not included in those standards. Additionally, most commercially available AM data management software applications used each organization’s internally defined data elements, thereby inadvertently hindering the ability to easily share full AM data sets with other organizations’ software solutions.  
5.4 This standard significantly eases the communication and use of AM data elements across the industry. It does this by providing, in a single location, a common understanding of individual elements within 15 information modules. Each organization can have increased confidence in using and analyzing AM data sets that adhere to this stan...
SCOPE
1.1 The scope of this document outlines the interpretation of additive manufacturing (AM) data. Currently, legacy AM data is stored in different databases or data management systems, each of which uses its own data dictionary. A common data dictionary allows AM data pedigree to be discovered, mapped, federated, and analyzed to improve both the understanding and qualification of AM processes and parts.  
1.2 A common data dictionary facilitates the interoperability, searchability, and reusability of AM data by (1) identifying the general AM data pedigree elements already defined in a standardized terminology and (2) defining those salient terms with indisputable semantics (meanings). The goal of this document is to provide a first subset of the common data dictionary by which AM data may be collected, curated, and shared, regardless of which technology platform and software are used for data storage and exchange.  
1.3 The common data dictionary also specifies a way to group AM data pedigree into fifteen information modules pertaining to different aspects of the entire additive manufacturing process.  
1.4 The common data dictionary approach specifies data element names that serve to uniquely identify the AM data elements. The data type, value domain, and term definition for each data element are also specified in this practice. References are provided for those data elements with established definitions in existing standards.  
1.5 The data elements identified in this common data dictionary are considered essential, because they are most frequently encountered in AM, process agnostic and technology independent. They are broadly applicable to all the process categories defined in ISO/ASTM 52900. It is intended to be a starting point, not all-encompassing.  
1.6 The common data dictionary does not specify:  
1.6.1 A complete set of data items to be exchanged through AM development lifecycle and value chains.  
1.6.2...

General Information

Status
Published
Publication Date
14-Dec-2021
Drafting Committee
Current Stage
Ref Project

Relations

Standard
ASTM F3490-21 - Standard Practice for Additive Manufacturing — General Principles — Overview of Data Pedigree
English language
17 pages
sale 15% off
sale 15% off

Frequently Asked Questions

ASTM F3490-21 is a standard published by ASTM International. Its full title is "Standard Practice for Additive Manufacturing - General Principles - Overview of Data Pedigree". This standard covers: SIGNIFICANCE AND USE 5.1 This standard can be used by AM data-system developers to design or update a database that meets business and process requirements. The information modules provide a foundation for an AM data structure. Standard definitions of data elements, their data types, and allowable values can be used directly to define the attributes for AM databases. 5.2 This standard is intended for organizations and personnel who wish to share AM data or who develop AM data management systems. The information modules defined in this standard represent a primary set of AM concepts. These concepts can be used to develop a common data model and a common data-exchange format, thereby enabling the transfer of data between different AM data management systems. Since legacy AM data management systems may use different data element definitions, translators will be needed to map their proprietary data into the common data exchange format. This common format will support both exporting from and importing to the original native formats. 5.3 This standard serves as the source for creating common definitions of and representations for all the AM data elements that have been agreed-upon by the community. Previously, standard definitions existed for only a few, high-level, data elements. This limited the ability of organizations to share AM data elements that were not included in those standards. Additionally, most commercially available AM data management software applications used each organization’s internally defined data elements, thereby inadvertently hindering the ability to easily share full AM data sets with other organizations’ software solutions. 5.4 This standard significantly eases the communication and use of AM data elements across the industry. It does this by providing, in a single location, a common understanding of individual elements within 15 information modules. Each organization can have increased confidence in using and analyzing AM data sets that adhere to this stan... SCOPE 1.1 The scope of this document outlines the interpretation of additive manufacturing (AM) data. Currently, legacy AM data is stored in different databases or data management systems, each of which uses its own data dictionary. A common data dictionary allows AM data pedigree to be discovered, mapped, federated, and analyzed to improve both the understanding and qualification of AM processes and parts. 1.2 A common data dictionary facilitates the interoperability, searchability, and reusability of AM data by (1) identifying the general AM data pedigree elements already defined in a standardized terminology and (2) defining those salient terms with indisputable semantics (meanings). The goal of this document is to provide a first subset of the common data dictionary by which AM data may be collected, curated, and shared, regardless of which technology platform and software are used for data storage and exchange. 1.3 The common data dictionary also specifies a way to group AM data pedigree into fifteen information modules pertaining to different aspects of the entire additive manufacturing process. 1.4 The common data dictionary approach specifies data element names that serve to uniquely identify the AM data elements. The data type, value domain, and term definition for each data element are also specified in this practice. References are provided for those data elements with established definitions in existing standards. 1.5 The data elements identified in this common data dictionary are considered essential, because they are most frequently encountered in AM, process agnostic and technology independent. They are broadly applicable to all the process categories defined in ISO/ASTM 52900. It is intended to be a starting point, not all-encompassing. 1.6 The common data dictionary does not specify: 1.6.1 A complete set of data items to be exchanged through AM development lifecycle and value chains. 1.6.2...

SIGNIFICANCE AND USE 5.1 This standard can be used by AM data-system developers to design or update a database that meets business and process requirements. The information modules provide a foundation for an AM data structure. Standard definitions of data elements, their data types, and allowable values can be used directly to define the attributes for AM databases. 5.2 This standard is intended for organizations and personnel who wish to share AM data or who develop AM data management systems. The information modules defined in this standard represent a primary set of AM concepts. These concepts can be used to develop a common data model and a common data-exchange format, thereby enabling the transfer of data between different AM data management systems. Since legacy AM data management systems may use different data element definitions, translators will be needed to map their proprietary data into the common data exchange format. This common format will support both exporting from and importing to the original native formats. 5.3 This standard serves as the source for creating common definitions of and representations for all the AM data elements that have been agreed-upon by the community. Previously, standard definitions existed for only a few, high-level, data elements. This limited the ability of organizations to share AM data elements that were not included in those standards. Additionally, most commercially available AM data management software applications used each organization’s internally defined data elements, thereby inadvertently hindering the ability to easily share full AM data sets with other organizations’ software solutions. 5.4 This standard significantly eases the communication and use of AM data elements across the industry. It does this by providing, in a single location, a common understanding of individual elements within 15 information modules. Each organization can have increased confidence in using and analyzing AM data sets that adhere to this stan... SCOPE 1.1 The scope of this document outlines the interpretation of additive manufacturing (AM) data. Currently, legacy AM data is stored in different databases or data management systems, each of which uses its own data dictionary. A common data dictionary allows AM data pedigree to be discovered, mapped, federated, and analyzed to improve both the understanding and qualification of AM processes and parts. 1.2 A common data dictionary facilitates the interoperability, searchability, and reusability of AM data by (1) identifying the general AM data pedigree elements already defined in a standardized terminology and (2) defining those salient terms with indisputable semantics (meanings). The goal of this document is to provide a first subset of the common data dictionary by which AM data may be collected, curated, and shared, regardless of which technology platform and software are used for data storage and exchange. 1.3 The common data dictionary also specifies a way to group AM data pedigree into fifteen information modules pertaining to different aspects of the entire additive manufacturing process. 1.4 The common data dictionary approach specifies data element names that serve to uniquely identify the AM data elements. The data type, value domain, and term definition for each data element are also specified in this practice. References are provided for those data elements with established definitions in existing standards. 1.5 The data elements identified in this common data dictionary are considered essential, because they are most frequently encountered in AM, process agnostic and technology independent. They are broadly applicable to all the process categories defined in ISO/ASTM 52900. It is intended to be a starting point, not all-encompassing. 1.6 The common data dictionary does not specify: 1.6.1 A complete set of data items to be exchanged through AM development lifecycle and value chains. 1.6.2...

ASTM F3490-21 is classified under the following ICS (International Classification for Standards) categories: 25.030 - Additive manufacturing. The ICS classification helps identify the subject area and facilitates finding related standards.

ASTM F3490-21 has the following relationships with other standards: It is inter standard links to ASTM E2077-00(2016), ASTM A1080-15, ASTM A1080-14, ASTM A1080-12, ASTM E2339-11, ASTM E2077-00(2010), ASTM E2339-10, ASTM E1338-09, ASTM E2339-08, ASTM E2339-06, ASTM E2077-00(2005), ASTM E2339-04, ASTM E1338-97(2003), ASTM E2077-00, ASTM E1338-97. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.

You can purchase ASTM F3490-21 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ASTM standards.

Standards Content (Sample)


This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: F3490 − 21
Standard Practice for
Additive Manufacturing — General Principles — Overview of
Data Pedigree
This standard is issued under the fixed designation F3490; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope 1.6.1 Acomplete set of data items to be exchanged through
AM development lifecycle and value chains.
1.1 Thescopeofthisdocumentoutlinestheinterpretationof
1.6.2 Aminimum set of data items to be exchanged forAM
additive manufacturing (AM) data. Currently, legacy AM data
lifecycle and value chain activities.
is stored in different databases or data management systems,
1.6.3 A common AM data exchange format.
each of which uses its own data dictionary. A common data
1.6.4 The details associated with how the common descrip-
dictionary allowsAM data pedigree to be discovered, mapped,
tions of data items should be implemented for the development
federated, and analyzed to improve both the understanding and
of new data systems or data federations among heterogeneous
qualification of AM processes and parts.
data systems.
1.2 A common data dictionary facilitates the
1.7 Additional data elements beyond those defined in exist-
interoperability, searchability, and reusability of AM data by
ing ASTM, ISO, AWS, NASA and SAE standards have been
(1) identifying the generalAM data pedigree elements already
introduced to provide increased utility forAM.These new data
defined in a standardized terminology and (2) defining those
items are generally common-sense and frequently used in the
salient terms with indisputable semantics (meanings).The goal
AM industry.
ofthisdocumentistoprovideafirstsubsetofthecommondata
1.8 This standard does not purport to address all of the
dictionary by which AM data may be collected, curated, and
shared, regardless of which technology platform and software safety concerns, if any, associated with its use. It is the
responsibility of the user of this standard to establish appro-
are used for data storage and exchange.
priate safety, health, and environmental practices and deter-
1.3 The common data dictionary also specifies a way to
mine the applicability of regulatory limitations prior to use.
group AM data pedigree into fifteen information modules
1.9 This international standard was developed in accor-
pertaining to different aspects of the entire additive manufac-
dance with internationally recognized principles on standard-
turing process.
ization established in the Decision on Principles for the
1.4 The common data dictionary approach specifies data
Development of International Standards, Guides and Recom-
element names that serve to uniquely identify the AM data
mendations issued by the World Trade Organization Technical
elements. The data type, value domain, and term definition for
Barriers to Trade (TBT) Committee.
eachdataelementarealsospecifiedinthispractice.References
are provided for those data elements with established defini-
2. Referenced Documents
tions in existing standards.
2.1 ASTM Standards:
1.5 The data elements identified in this common data
A1080 Practice for Hot Isostatic Pressing of Steel, Stainless
dictionary are considered essential, because they are most
Steel, and Related Alloy Castings
frequently encountered in AM, process agnostic and technol-
E1338 Guide for Identification of Metals and Alloys in
ogy independent.They are broadly applicable to all the process
Computerized Material Property Databases
categories defined in ISO/ASTM 52900. It is intended to be a
E2077 Specification for Analytical Data Interchange Proto-
starting point, not all-encompassing.
col for Mass Spectrometric Data
E2339 Practice for Digital Imaging and Communication in
1.6 The common data dictionary does not specify:
Nondestructive Evaluation (DICONDE)
This practice is under the jurisdiction of ASTM Committee F42 on Additive
Manufacturing Technologies and is the direct responsibility of Subcommittee For referenced ASTM standards, visit the ASTM website, www.astm.org, or
F42.08 on Data. contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
Current edition approved Dec. 15, 2021. Published March 2022. DOI: 10.1520/ Standards volume information, refer to the standard’s Document Summary page on
F3490-21. the ASTM website.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F3490 − 21
2.2 ISO/ASTM Standards: Powder for Additive Manufacturing, 62Ni – 21.5Cr –
52900 Terminology for Additive Manufacturing Technolo- 9.0Mo – 3.65Nb
gies SAE ARP1917 Rev. A Aerospace Recommended Practice,
52915 Specification for additive manufacturing file format Clarification of Terms Used in Aerospace Metals Specifi-
(AMF) Version 1.2 cations
52921 Terminology for Additive Manufacturing—
2.5 NASA Standards:
Coordinate Systems and Test Methodologies
MSFC-STD-3716 Standard for Additively Manufactured
52930 Additive manufacturing qualification principles —
Spaceflight Hardware by Laser Powder Bed Fusion in
Installation, operation and performance (IQ, OQ, PQ) of
Metal
PBF-LB equipment
MSFC-SPEC-3717 Specification for Control and Qualifica-
tion of Laser Powder Bed Fusion Metallurgical Processes
2.3 ISO Standards:
ISO 5127 Information and documentation — Foundation 2.6 ASME Standard:
ASME Y14.46 – 2017 Product Definition for Additive
and vocabulary
ISO/IEC6523-1 Informationtechnology—Structureforthe Manufacturing
identification of organizations and organization parts —
2.7 AWS Standard:
Part 1: Identification of organization identification
AWS D20.1/D20.1M Specification for Fabrication of Metal
schemes
Components using Additive Manufacturing
ISO 8601-1 Date and time — Representations for informa-
3. Terminology
tion interchange — Part 1: Basic rules
ISO 11145 Optics and photonics — Lasers and laser-related
3.1 Acronyms:
equipment — Vocabulary and symbols
3.1.1 CAD—computer aided design
ISO 11161 Lasers and laser-related equipment — Test meth-
3.1.2 DB—database
ods for laser beam widths, divergence angles and beam
3.1.3 DOD—Department of Defense
propagation
ISO/IEC 11179-1 Information technology — Metadata reg-
3.1.4 ID—identifier
istries (MDR) — Part 1: Framework
3.1.5 ITAR—International Traffic in Arms Regulations
ISO/IEC 11179-3 Information technology — Metadata reg-
3.1.6 PLM—product lifecycle management
istries (MDR) — Part 3: Registry metamodel and basic
3.1.7 TIC—test / inspection / characterization
attributes — Amendment 1
ISO 11238 Health informatics — Identification of medicinal 3.1.8 URI—uniform resource identifier
products — Data elements and structures for the unique
3.1.9 UUID—universally unique identifier
identification and exchange of regulated information on
3.2 Definitions of Terms Specific to This Standard:
substances
3.2.1 controlled vocabulary, n—finite set of values that
ISO/IEC 11404 Information technology — General-Purpose
represent the only allowed values for a data item. ISO
Datatypes (GPD)
11238:2018
ISO/IEC 11578 Information technology — Open Systems
3.2.2 data dictionary, n—formal repository of terms used to
Interconnection — Remote Procedure Call (RPC)
ISO 16781 Space systems — Simulation requirements for describe data. ISO 19165-1: 2018
control system
3.2.3 data element, n—a unit of information as defined by a
ISO 19160 Addressing — Part 4: International postal ad-
single entry in the data dictionary. E2339
dress components and template language
3.2.4 data element name, n—a unique name for each data
ISO 19165-1 Geographic information — Preservation of
element.
digital data and metadata — Part 1: Fundametals
3.2.5 data type, n—the kind of data to be included in the
ISO 22745-2 Industrial automation systems and integration
data element, such as numbers, character string, and date.
— Open technical dictionaries and their application to
E1338
master data — Part 2: Vocabulary
ISO/IEC 29155 Systems and software engineering – Infor- 3.2.6 definition, n—themeaningofadataelementdefinedin
mation technology project performance benchmarking a standard or common sense.
framework
3.2.7 enumerated value domain, n—value domain that is
2.4 SAE Standards: specified by a list of all its permissible values. ISO/IEC
SAE AMS 2750 Pyrometric Requirements for Heat Treat- 11179-3:2013
ments
SAEAMS7001 NickelAlloy,CorrosionandHeat-Resistant,
Available from the NASA Technical Standards System at the NASA website
www.standards.nasa.gov.
Available from American Society of Mechanical Engineers (ASME), ASME
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St., International Headquarters, Two Park Ave., New York, NY 10016-5990, http://
4th Floor, New York, NY 10036, http://www.ansi.org. www.asme.org.
4 7
Available from SAE International (SAE), 400 Commonwealth Dr.,Warrendale, Available from American Welding Society (AWS), 8669 NW 36 St., #130,
PA 15096, http://www.sae.org. Miami, FL 33166-6672, http://www.aws.org.
F3490 − 21
3.2.8 permissible value, n—expression of a value meaning standard represent a primary set of AM concepts. These
allowed in a specific value domain. ISO 22745-2:2010 concepts can be used to develop a common data model and a
common data-exchange format, thereby enabling the transfer
3.2.9 unit of measure, n—actual units in which the associ-
of data between differentAM data management systems. Since
ated values are measured. ISO/IEC 11179-1:2015
legacy AM data management systems may use different data
3.2.10 value, n—a component of a value field.Avalue field
element definitions, translators will be needed to map their
may consist of one or more of these components. E2339
proprietary data into the common data exchange format. This
3.2.11 value domain, n—set of permissible values with
common format will support both exporting from and import-
defined unit of measure. ISO/IEC 11179-1: 2015
ing to the original native formats.
5.3 This standard serves as the source for creating common
4. Summary of Practice
definitions of and representations for all theAM data elements
4.1 The purpose of the common data dictionary is to
that have been agreed-upon by the community. Previously,
establish a common lexicon to facilitate the unambiguous
standard definitions existed for only a few, high-level, data
exchange of AM information. This language allows AM
elements. This limited the ability of organizations to shareAM
practitioners to use the same terminology and data types,
data elements that were not included in those standards.
thereby promoting a common understanding of their data and
Additionally, most commercially available AM data manage-
promoting the ability to share and reuse that data. Both
ment software applications used each organization’s internally
capabilities will ultimately accelerate growth in theAM sector.
defined data elements, thereby inadvertently hindering the
4.2 The common data dictionary contains terms and defini- ability to easily share full AM data sets with other organiza-
tions that pertain broadly to a variety of currently used AM tions’ software solutions.
processes that include laser powder bed fusion and wire
5.4 Thisstandardsignificantlyeasesthecommunicationand
directed energy deposition, among others. Terms and defini-
use of AM data elements across the industry. It does this by
tions that apply to a specific AM process will be contained in
providing, in a single location, a common understanding of
a separate standard practice.
individual elements within 15 information modules. Each
4.3 Each defined element includes the data element name,
organization can have increased confidence in using and
data type, value domain (permissible values or units of
analyzingAM data sets that adhere to this standard, even when
measure, or both), and a definition, which is based on a
those data sets are generated by another organization. This
standard reference if one exists. The data element name
standard will also provide a starting point from which to build
solidifies the common language around captured data items.
a common data format that will facilitate the transfer of AM
The data type represents how the value should be represented
data sets among those organizations.
in a database; examples include a string, a real, and a
5.5 Not all the data elements are applicable to all the use
hyperlink. Value Range and Value Set both limit the values a
cases. Some of the definitions of the data items are only
data element can take. Primary Unit is prescribed to ensure
applicable to certain cases. For example, “Specimen Orienta-
simplified sharing of data. The scope of this practice includes
tion” and “Specimen Location” are only applicable to speci-
(1) data elements with existing terminology or reporting
mens extracted from a built part, not powder specimens.
guideline standards and (2) data elements with commonly
agreed-upon or intuitive descriptions. Data elements of the
6. Information Modules
former type reference the applicable standard, while those of
the second type include a brief description that has undergone
6.1 AM data pedigree covers all the phases of AM part-
reviews by the AM community.
development lifecycle and all nodes of a supply chain. Based
on when and where the data is generated, each AM data
4.4 As this standard continues to evolve, data elements and
element can be grouped into information modules. The addi-
information modules may be added or amended. It is possible
tive manufacturing data elements presented in this practice are
that this will cause datasets to become non-conforming with
grouped into 15 discrete information modules as shown in Fig.
the latest data pedigree standard practice. A dataset should
1. The information modules are defined in this section. Data
specify the version of this practice it is conforming to in order
element definitions are described in Section 7.
to reduce miscommunications.
6.2 Project—Atemporary designation when creating one or
5. Significance and Use
more unique AM products or AM services (ISO/IEC 29155).
This module contains data relating to an entire project, includ-
5.1 This standard can be used by AM data-system develop-
ing related builds and information about project execution and
ers to design or update a database that meets business and
administration.
process requirements. The information modules provide a
foundation for an AM data structure. Standard definitions of
6.3 Build—All the information generated during a single,
data elements, their data types, and allowable values can be
AM process cycle during which one or more components are
used directly to define the attributes for AM databases.
‘built up’ in layers inside the process chamber of the additive
5.2 This standard is intended for organizations and person- manufacturing system (ISO/ASTM 52900). The Build data
nel who wish to share AM data or who develop AM data module acts as a central reference point for all data related to
management systems. The information modules defined in this abuild.Itcontainsreferencelinkstoothermodulesinvolvedin
F3490 − 21
FIG. 1 AM Information Modules
the build process (for example, Material for feedstock post processing of that data. Elements related to specific AM
information, Parts for information about parts produced in the
processtypesareomittedinthisdocument;theywillbedefined
build). in separate standards.
6.4 Part Design—Detailed information associated with the
6.10 Test/Inspection/Characterization (TIC)—Any inspec-
design of a part, including but not limited to an AMF, STL or
tion or test performed on any material from any stage of the
other 3-D format file, a CAD model, a reverse engineered
additive manufacturing fabrication process (excluding in-
model, output from medical radiology segmentation software,
process monitoring). This includes specimen information, the
3-D modeling, simulation or optimization. Part Design also
test methodology, and test results. Readers are referred to
includes assembly designs. (See ISO/ASTM 52915.)
terminology or reporting guideline standards where applicable.
6.5 Built Part—Instances of part or assembly designs in the
6.11 Synthesized Data—Data that has been reduced from its
as-built state. One build can have multiple built parts or
original raw form and often indicates clearer, more human-
assemblies of the same design. This module captures informa-
friendly, interpretable results. This could include statistical or
tion for parts and assemblies produced by a build.
trend-related results, material cards (for design/simulation), or
6.6 AM System—AM system includes the AM machine,
similar.
machine software / firmware and any auxiliary, in situ moni-
6.12 Organizations—The organization performing a task or
toring equipment used during a build. Manufacturer-provided
providing services or products.This module details the creden-
specifications are included, but details specific to AM process
tials of vendors, manufacturers, suppliers, and contractors.
types are omitted.
6.13 Personnel—The individuals performing tasks and their
6.7 Material—Details for materials used in theAM process,
including feedstock, build platform, and environmental gases; credentials, including their roles, experience, and qualifica-
details include order information, characterization, storage tions.
details, and more.
6.14 Non-AM Equipment—This module includes informa-
6.8 Process Control—Controls of the manufacturing pro-
tion for non-AM system equipment required for pre-
cesses utilized to produce a certified AM component or part.
processing, post-processing, tests, inspections, or
This module contains process settings and parameters. Ele-
characterizations, for example, microscopes, sieves, flow me-
ments related to specific,AM-process types are omitted in this
ters.
practice since they will be defined in separate standards.
6.15 Software—The details of computer programs used
Post-process settings and parameters are included in this
duringdesign,AMfabricationprocesses,analysis,andsoforth.
module.
6.16 Simulation—The data used and generated from com-
6.9 Process Data—The direct data, or derived outputs from
that data, is obtained from the AM system and in situ puter programs using physics-based models. This includes
information about the models, configurations, and simulation
monitoring equipment during a build process. This module
captures actual observed and recorded data from a build or the inputs and outputs.
F3490 − 21
7. Data Element Definitions characterizations. The Test, Inspection, and Characterization
NOTE 1—The data elements defined under individual information
group is sometimes referred in general as “TIC”.
modules are listed and described in this section.
7.10.1 General Information—See Table 15.
7.1 Data Type and Common Value Set Definition—The data
7.10.2 Configuration and Specimen Information—See Table
types and common value sets used by the data element
16.
definitions are captured in Tables 1 and 2.
7.10.3 Test Results—See Table 17.
7.10.4 Test / Inspection / Characterization Value Sets—See
7.2 Project—See Table 3.
Table 18.
7.3 Build—See Table 4.
7.11 Synthesized Data—See Tables 19 and 20.
7.4 Part Design—See Table 5.
7.12 Organizations—See Tables 21 and 22.
7.5 Built Part—See Table 6.
7.13 Personnel—See Table 23.
7.6 AM System—See Tables 7 and 8.
7.14 Non-AM Equipment—See Table 24.
7.7 Material—See Tables 9 and 10.
7.15 Software—See Table 25.
7.8 Process Control—See Tables 11 and 12.
7.9 Process Data—See Tables 13 and 14. 7.16 Simulation—See Table 26.
7.10 Test / Inspection / Characterization—This section is
8. Keywords
broken into several sub-sections to help organize the data
elements and avoid duplication of common or general data 8.1 additive manufacturing; data dictionary; data exchange;
elements that apply to a multitude of tests, inspections, and data format; data pedigree
TABLE 1 List of the Data Types Used by This Standard
Data Type Definition Standard
integer The mathematical datatype comprising the exact integral values XSD, ISO/IEC 11404
string String data types are used for values that contains character strings XSD
stringArray An array of strings
real Real is a family of datatypes, which are computational approximations to the mathematical ISO/IEC 11404
datatype that comprises the “real numbers”. Specifically, each real datatype designates a collec-
tion of mathematical real values, which are expressed in some finite precision and must be dis-
tinguishable to at least that precision.
date The date data type is used to specify a date. The date is specified in the following form 9YYYY- ISO 8601; XSD
MM-DD (Time Zone)9
dateTime The dateTime data type is used to specify a date and a time. The dateTime is specified in the ISO 8601; XSD
following form 9YYYY-MM-DDThh:mm:ss (Time Zone)9
duration The duration data type is used to specify a time interval. The time interval is specified in the fol- ISO 8601; XSD
lowing form 9PnYnMnDTnHnMnS9
where:
P indicates the period (required)
nY indicates the number of years
nM indicates the number of months
nD indicates the number of days
T indicates the start of a time section (required if you are going to specify hours, minutes, or
seconds)
nH indicates the number of hours
nM indicates the number of minutes
nS indicates the number of seconds
time The time data type is used to specify a time. hh:mm:ss (Time Zone) ISO 8601; XSD
anyURI A data type used to specify a URI XSD
3dCoordinate (x, y, z) as real numbers defined in a coordinate system N/A
globalAddressFormat International address specified by ISO 19160 includes: Full name, street address, city, state/ ISO 19160-4:2017
province/region and country name place, and zip code
document Recorded information or material object, which can be treated as a unit in a documentation pro- ISO 5127:2017
cess
F3490 − 21
TABLE 2 Common Value Sets Defined Across the 15 Information Modules
Value Set Name Definition Definition Source
Process Atmosphere Type Enumeration {Argon, Helium, CO , Oxygen, Nitrogen, Others} N/A
Pass Fail Enumeration {pass, fail}
TABLE 3 Data Elements in the Project Information Module
Data Element Name Data Type Value Range, Value Set, or Primary Units Definition / Standard
Project ID string free text (unique) Identifier of a project. This field is required to be unique
across all instances of data records.
Project Creator string Organization ID Organization that created the project
Project Sponsor string Organization ID Provider of money and requirements for the project
Project Distribution Statement string Selection of standard DOD distribution Documentation of any access restrictions to the
statements distribution of data collected and analyzed under this
project, by organizations other than the authoritative
source
Project Distribution Control string free text ITAR, copyright, patent. and other IP licensing
declarations, for example, restrictions
Project Start Date date The date is specified in the following form Start date of a project
9YYYY-MM-DD (Time Zone)9
Project End Date date The date is specified in the following form End date of a project
9YYYY-MM-DD (Time Zone)9
Project Delivery Date date The date is specified in the following form Delivery date of a project
9YYYY-MM-DD (Time Zone)9
Project Plan anyURI hyperlink Document describing how a project is to be conducted,
organized, and so forth
Project Owning Materials DB string free text (unique) A unique identifier (or equivalent) to identify the
authoritative Materials DB that houses this project and all
corresponding data
Project Repository anyURI hyperlink Link or reference to the host system (product lifecycle
management repository or database), which houses the
authoritative data in this data set
Project Builds stringArray Build ID List of identifiers to builds associated to this project
Project Standards string free text Set of standards used in the project
Project Quality Control Plan anyURI hyperlink Document describing the quality control plan for the site
performing the project
Project Quality Process Control anyURI hyperlink Document describing the quality process control plan for
Plan the site performing the project
F3490 − 21
TABLE 4 Data Elements in the Build Information Module
Value Range, Value Set, or
Data Element Name Data Type Definition / Standard
Primary Units
Build ID string free text (unique) Identifier for an AM build; This field is required to be unique across
all instances of data records
Project ID string Project ID Reference to the associated project that produced this build. Links to
a Project record.
AM System ID list stringArray AM System ID Reference to the associated AM system(s) for this build. Links to a
list of AM System records.
Part Design ID list stringArray Part Design ID Reference to the part designs used for this build. Links to Part
Design records.
Built Part ID list stringArray Built Part ID Reference to set of Built Parts that are incorporated into this build.
Links to Built Part records.
Process ID list stringArray Process ID Reference to Processes associated with the entire build. Links to a
list of Process records. Individual, Built Part records will have part-
specific processes associated with them.
Specimen ID list stringArray Specimen ID List of Specimens associated with this build. Links to a set of
Specimen records.
Process Data ID list stringArray Process Data ID Reference to list of Process Data records for data gathered during
this build
TIC ID list stringArray TIC IDs Reference to list of test/inspection/characterization records
associated to the whole build (TIC performed on built parts or
specimens would be linked from those records)
Simulation ID list stringArray Simulation ID Reference to Simulation records associated to this build. Links to a
list of Simulation records.
Software ID list stringArray Software ID Reference to list of software used in build. Links to Software
records.
Organization ID string Organization ID Reference to production Organization for this build. Links to an
Organization record.
NonAMEquip ID list stringArray NonAMEquip ID Reference to list of Non-AM Equipment records. Links to NonAM
Equipment record.
Material ID list stringArray Material ID Reference to material feedstock records for build. Links to Material
records.
Build Personnel stringArray Personnel ID Reference to personnel associated with the build (that is, operators,
inspectors). Links to Personnel records.
SynthData ID list stringArray SynthData ID Reference to Synthesized Data records associated to this build
Build Plan string/anyURI free text or hyperlink Document that describes the specific, build-design intent and
requirements, which must include specified dimensional unit of
measure, accuracy (number of digits), and precision (tolerance of ±),
for build parts and assemblies. This may include platform layout,
witness coupons, object quantity, and position/orientation.
Build Platform Definition string/anyURI free text or hyperlink File that describes the contents of the build platform (objects and
locations). This is intended to be a CAD file that models the build
platform and individual component layouts, that would be fed to the
AM System processing software to perform the build.
Build Type string free text Description of the primary purpose of the Build (end use component,
specimens, research, and so forth)
Build Platform string Build Platform ID Unique identifier to associate a physical build platform with a Build
record
Build Job File anyURI hyperlink File (or pointer to file) containing the build job defined by the
machine
F3490 − 21
TABLE 5 Data Elements in the Part Design Information Module
Value Range, Value Set, or
Data Element Name Data Type Definition / Standard
Primary Units
Part Design ID string Part Design ID Identifier for the part design
Part Revision Number string free text Revision number of the part design
Object Definition File string hyperlink File that pertains to the part design description
Derived from Part Design string Part Design ID Part Design ID of the original part this object is derived from (if
ID applicable)
Part Design ID list stringArray Part Design ID List of part designs and relative locations in this object - this is
intended for part designs of assemblies, where the model is
comprised of multiple individual part designs that are brought into
the file via reference (like a build platform definition, for example)
Part Design Primary anyURI hyperlink Primary source file (or pointer to file) for a part design; also known
Source File as Authoritative File defined by DOD.
Part Design CAD file anyURI hyperlink File (or pointer to file) containing CAD for part design, which must
include specified dimensional unit of measure, accuracy (number of
digits), and precision (tolerance of ±), for build parts and assemblies
Part Design Augmented anyURI hyperlink File (or pointer to file) containing source CAD for the augmented
Source File part design, complete with augmentation for support structures and
other AM-specific data, which must include specified dimensional
unit of measure, accuracy (number of digits), and precision
(tolerance of ±)
Part Design Originating string Organization ID Developer of the source CAD file. Links to Organization.
Organization
Part Design Developer string Personnel ID Reference to personnel who created CAD file. Links to Personnel.
Part Design Software string Software ID Reference to CAD software name/version. Links to Software.
Part Criticality string Industry specific part Criticality designation of part or parts to be developed in this project
criticality categories or free
text
Part Requirements string hyperlink Document describing requirements or goals for components/
specimens to be manufactured
Dimensional Unit of string Metrics or English unit Indicates unit of measure, that is, micrometer, mm, inches, and so
Measure measure forth
TABLE 6 Data Elements in the Built Part Information Module
Value Range, Value Set, or
Data Element Name Data Type Definition / Standard
Primary Units
Built Part ID string Built Part ID Identifier for a built part
Build Producing this Part string Build ID Identifier of the build from which this part was produced. Links to a
Build record.
Built Part Process string Process ID Sequence of events occurring to this part. Links to Process.
Sequence
Part Location on Build 3dCoordinate mm The location of the box center of the part, or an accepted reference
datum
Part Orientation real angles in degree The orientation of the part placed in the build volume, defined in
ISO/ASTM 52900 and 52921.
Design of this Part string Part Design ID Design information for the build Part. Links to Part Design.
TIC Performed on this Part stringArray TIC IDs TIC that has been performed on the built part. Links to TIC records.
F3490 − 21
TABLE 7 Data Elements in the AM System Information Module
Data Element Name Data Type Value Range, Value Set, or Definition / Standard
Primary Units
AM System ID string free text A unique Identifier of an AM system in a local facility
AM System Name string free text Name of an AM system
AM System Location globalAddressFormat global address format defined by Physical location of the AM System, in the format defined in
ISO 19160 ISO 19160-4:2017 Addressing — Part 4: International postal
address components and template language
AM Machine Name string free text Name of an AM machine - section of the additive manufac-
turing system including hardware, machine control software,
required set-up software and peripheral accessories neces-
sary to complete a build cycle for producing parts. ISO/ASTM
52900:2015(E).
AM Machine Manufacturer string Organization ID Manufacturer identifier of an AM Machine
AM Machine Model Name string Searchable vendor defined AM Manufacturer’s model name of an AM Machine
machine model name
AM Machine Serial Num- string free text Serial number of an AM machine defined by the machine
ber manufacturer
AM Machine Firmware Ver- string free text Description of the version numbers of the firmware of the
sion components of an AM Machin
...

Questions, Comments and Discussion

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

Loading comments...