2.1在EN 9300环境下的PDM数据 在大多数现代工业环境中，使用产品数据管理（PDM）系统来维护和管理产品数据。一般来说，这些系统: - 管理所使用的主要技术数据，例如CAD模型和文档; - 允许将主要技术数据组织成代表相关产品的结构; - 支持产品的定义和维护流程。 在EN 9300的情况下，几个特定领域的部分解决了LTA用于创建信息不在范围内。得到的信息，例如更改授权文件，审批/签名，CAD模型，属性数据等。 产品管理数据密切反映了每家公司的本地业务和数据处理流程。因此，一个开放的标准只能定义总体需求的一个共同的通用子集。其他仅与本地相关或依赖于本地应用程序环境的数据由本地过程定义。对于每个应用环境，应根据开放标准，行业标准或公司标准和程序来定义和归档与归档产品管理数据相关的全套标准，方法和程序。强烈建议尽可能使用开放标准来简化数据交换，共享，归档和审计能力。 LTA的三个主要目标在相关的产品管理数据中。 2.2.1体系结构定义 产品管理数据和主要技术数据可以在不同的环境中进行管理（例如，产品管理数据的数据库系统和主要技术数据的文件系统，并在数据库中引用文件的唯一标识符和位置） 。在许多情况下，主要技术数据由附属于PDM主干架构的主生成系统（例如CAD，系统工程工具集）保存。 产品管理数据和主要技术数据之间的关系通常通过参考机制来确定。归档时应考虑引用机制和管理它们的系统。 这可以通过描述涉及管理相关信息的系统的完整体系结构以及定义通用系统要求和程序（如同步，应用质量级别，安全要求和审计）来完成。体系结构的整体功能要求体系结构内的所有系统都符合通用要求。 完整的体系结构定义应符合适用的EN 9300通用流程中定义的要求部分。 2.2.2存档频繁更改的PDM数据 （。）

2.1 PDM data in EN 9300 context In most modern industrial environments, product data is maintained and managed using product data management (PDM) systems. In general, these systems: - Manage the use of the primary technical data contained, for example, in CAD models and documents; - Allow organization of primary technical data into structures to represent the relevant products; - Support definition and maintenance processes for products. Within the EN 9300 context, several domain specific parts address LTA&R for the primary technical data (e.g. CAD, CAx, Documents) as generated by the relevant technical "authoring" systems. The EN 9300 2xx series provides information for LTA&R of product management data for the relevant documents, structures and processes. NOTE The terms "PDM data" and "product management data" are synonymous. This is illustrated in the Figure below. (.) Figure 1 - PDM Data and Primary Technical Data 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. Three main objectives for LTA&R of product management data are: - enable the proper retrieval of archived primary technical data when performing queries relative to product structure, relationships, effectivity, status, etc.; - preserving the links between primary technical data and the associated product management data; - providing all relevant properties of primary technical data as contained within the associated product management data. 2.2.1 Architecture Definition The product management data and the primary technical data may be managed in different environments (e.g. a database system for the product management data and a file system for the primary technical data with a reference in the database to the unique identifier and location for the file). In many cases, the primary technical data are held by the primary generating systems (e.g. CAD, systems engineering tool set) attached to a PDM backbone architecture. The relationship between product management data and primary technical data is typically established by referencing mechanisms. The referencing mechanisms and the systems managing them shall be taken into account when archiving. This can be done by describing the complete architecture of systems involved in the management of the relevant information and by defining common system requirements and procedures, such as synchronization, applied quality level, security requirements, and auditing. The overall capability of the architecture requires all systems within the architecture to comply with the common requirements. The complete architecture definition shall comply with requirements defined in the applicable EN 9300 common process parts. 2.2.2 Archival of frequently changing PDM data (.)