F42.08 - Data

SIGNIFICANCE AND USE
5.1 The converted file will be organized in a specific structure to reflect the relationship between the in-process monitoring data with the quality of the printing process.  
5.2 This standard file structure will help ensure the data compatibility across various printing systems, analyses, and illustration software. It aims to be self-explaining and easy to use to accommodate data sharing in a large base of users.  
5.3 The converted file can be used for the evaluation of printing quality and the detections of defects and anomalies.
SCOPE
1.1 This guide provides standardized procedures and requirements for converting acquired in-process monitoring data into one file representing the printing process of powder bed fusion (PBF) for quality evaluation.  
1.2 Many of the operational descriptions included in this guide are intended as general overviews. They may not present the detailed information required.  
1.3 This guide covers:  
1.3.1 Data registration,  
1.3.2 Extraction of in-process data, and  
1.3.3 File conversion and visualization.  
1.4 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.5 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.

SCOPE
1.1 This specification has been developed to facilitate exchanging and analyzing particle size distribution (PSD) by light scattering data from databases, data management systems, point of origin, or other data sources that may use different data dictionaries, schemas, or formats.  
1.2 This specification prescribes the use of a common exchange format in such a way that PSD data defined through proprietary means can be easily exchanged for process understanding and qualification.  
1.3 This specification facilitates the interoperability of PSD data by identifying the data elements defined in standardized terminology, as well as defining those salient terms with indisputable meanings. In doing so, this specification extends the common AM data dictionary defined in Practice F3490 to encapsulate PSD process-specific data elements. Generic data elements and relationships present in that standard are inherited and applied in this practice where relevant.  
1.4 This specification specifies names that serve to uniquely identify the PSD 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 or reporting guidelines in existing standards.  
1.5 This specification prescribes a file format and structure for the exchange of PSD data. This format defines a method for sharing data via the defined PSD data elements herein and provides a basis for validation of data exchanged using this format.  
1.6 This specification recommends levels of data sharing that vary from minimal to robust. It prescribes best practices for checking conformance based on the common data exchange format.  
1.7 This specification does not specify:  
1.7.1 An exhaustive set of data items that could be exchanged related to PSD by light scattering.  
1.7.2 A definition of a minimum viable data set for PSD by light scattering.  
1.7.3 Data items or an exchange format for PSD methods other than light scattering, for example, imaging or sieving.  
1.7.4 Data elements for data modules related to PSD (for example, for personnel, material, or equipment).  
1.7.5 The implementation details of how data should be imported to proprietary data management systems from the common data exchange format.  
1.7.6 The implementation details of how data should be exported from proprietary data management systems to the common data exchange format.  
1.7.7 Guidelines for creating unique identifiers for data module records  
1.8 The values stated in SI units are to be regarded as standard. No other units of measurement are included in this standard.  
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.

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...