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 standard, even when those data sets are generated by another organization. This standard will also provide a starting point from which to build a common data format that will facilitate the transfer of AM data sets among those organizations.
5.5 Not all the data elements are applicable to all the use cases. Some of the definitions of the data items are only applicable to certain cases. For example, “Specimen Orientation” and “Specimen Location” are only applicable to specimens extracted from a built part, not powder specimens.
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 A minimum set of data items to be exchanged for AM lifecycle and value chain activities.
1.6.3 A common AM data exchange format.
1.6.4 The details associated with how the common descriptions of data items should be implemented for the development of new data systems or data federations among heterogeneous data systems.
1.7 Additional data elements beyond those defined in existing ASTM, ISO, AWS, NASA and SAE standards have been introduced to provide increased utility for AM. These new data items are generally common-sense and frequently used in the AM industry.
1.8 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.
1.9 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.
