BS EN 9300-200:2018 pdf download.Aerospace series – LOTAR – LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 200: Common Concepts for LOng Term Archiving and Retrieval of Product Structure Information.
1.1 Justification LTA&R of only the original technical data defining a product does not give sufficient information to satisfy the obligation to provide supporting documents for proof of evidence, since essential usage information for these data will be missing. Hence evidential weight of these data in most cases can only be guaranteed by long term archiving and retrieval of a minimum set of the respective metadata. Two business scenarios describe the basic requirements for LTA&R of PDM data: 1) Assure evidence of product data for verification, certification, or product liability. This is the minimum requirement for LTA&R and provides sufficient product management data to indicate the proper usage of the primary technical data. Since this is limited to static information on defined product instances and their configurations and is only intended to enable viewing of these data, it can be extracted from PDM systems with attached primary technical data in a viewing format. However this will not allow the re-use of the PDM data. 2) Enable reuse of the archived product data. LTA&R of PDM data which enables reuse of product data over the complete life cycle of a product is needed for business requirements which increasingly assume the availability of this data. However, this requires deeper integration of processes and PDM data compared to the previous scenario. More detailed information on these scenarios and their use cases is given in the detailed EN 9300-2xx Parts.
2.2 Objectives and scope of application This part covers long term archiving (LTA&R) for product management data and relevant process related information (e.g. product structure requirements). Regarding process related information, only the process results are considered in scope as these have stable and static characteristics. The workflow used to create the information is not in scope. The resulting information, e.g. change authorization document, approvals/signatures, CAD models, attribute data, are in scope. Product management data closely reflects the local business and data handling processes of each company. Therefore, an open standard can define only a common generic subset of the overall requirements. Other data that are only of local relevance or dependent on the local application environment are defined by local procedures. For each application environment, the complete set of standards, methods, and procedures related to the archived product management data shall be defined and documented by open standards, industry standards, or company standards and procedures. It is strongly recommended to use open standards whenever possible to ease data exchange, sharing, archiving, and ability to audit.BS EN 9300-200 pdf download.