EN 9300-200:2018

European foreword
Foreword
1 Preface
2 Scope
3 Normative references
4 Terms, definitions and abbreviations
5 Applicability
6 Fundamentals and concepts for long term
   archiving and retrieval of PDM data
7 Requirements for customization of
   off-the-shelf PDM systems
8 Methods of implementation of the given requirements
9 Preservation Planning for archived PDM information
10 Administration and monitoring
11 Definition of Archive Information Packages for PDM Data
12 Conformance Classes
Annex A (informative) - Notional Information Objects in
        relation to product life cycle views

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

NOTEThe 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.2Objectives 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.1Architecture 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.2Archival of frequently changing PDM data

(...)