🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN 9300-200:2018

BS EN 9300-200:2018

$198.66

Aerospace series. LOTAR. LOng Term Archiving and Retrieval of digital technical product documentation suchas 3D, CAD and PDM data – Common Concepts for LOng Term Archiving and Retrieval of Product Structure Information

Published By Publication Date Number of Pages
BSI 2018 52
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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 (…)

PDF Catalog

PDF Pages PDF Title
2 National foreword
4 1 Preface
2 Scope
Annex A (informative)Notional Information Objects in relation to product life cycle views
6 0BForeword
7 1.1 Justification
1.2 Long Term Archiving and Retrieval of PDM data in EN 9300 context
8 1.3 Location in EN 9300 document structure
2.1 PDM data in EN 9300 context
9 2.2 Objectives and scope of application
10 2.2.1 Architecture Definition
2.2.2 Archival of frequently changing PDM data
2.2.3 CAD Authored Data Replicated in PDM
2.3 Out of Scope
11 3 Normative references
12 4 Terms, definitions and abbreviations
20 5 Applicability
6 Fundamentals and concepts for long term archiving and retrieval of PDM data
6.1 Usage of basic EN 9300 principles
6.1.1 Usage of EN 9300 processes
6.1.2 Employment of OAIS model
6.1.3 Requirements justified by business scenarios
21 6.1.4 Identification of essential information
6.1.5 Usage of open standards (STEP)
6.1.6 Qualification methods for LTA&R of PDM data
6.2 Unique identification
22 6.3 Retention trigger points
6.4 Data to be retained
23 6.4.1 Data Status/Maturity of Data
24 6.4.2 Retention of complete product data structures versus changes
6.4.3 Structures and related information objects retained independently but connected by reference
25 6.5 PDM and Product Life Cycle Stages
29 6.6 Display/re-use of LTA&R format in active PDM systems
7 Requirements for customization of off-the-shelf PDM systems
30 8 Methods of implementation of the given requirements
8.1 Configured Baselines
8.1.1 Predefined (sub-) structure
31 8.1.2 Baselines (configured/verified structure set)
8.1.3 Saved relations to referenced information objects
32 8.2 Process Documentation
8.3 Essential Data in Relation to Business Scenarios to Be Supported
33 8.4 Qualification methods for long term archiving and retrieval of PDM data
8.4.1 Verification rules
34 8.4.2 Content verification
8.4.2.1 Verification level 1 – Mandatory rules
35 8.4.2.2 Verification level 2 – Mandatory plus optional rules
8.4.3 Validation rules
36 8.4.4 Content Validation
8.4.4.1 Validation Level 1 – Mandatory rules
8.4.4.2 Validation Level 2 – Mandatory plus optional rules
9 Preservation Planning for archived PDM information
9.1 Preservation Planning Introduction
38 9.2 General Provisions
9.2.1 Divergence from Recommendations
9.2.2 Requirements on handling of reference data libraries (RDL)
9.2.3 Live vs. Archived Data
9.2.4 System Replacement
9.2.5 Recovery to Live PLM System
39 9.2.6 Complex Use Cases
9.3 Change Management
40 9.3.1 External Records of Change Sources
9.3.2 External Records of Change Completion
9.3.3 Evidential weight for External Records
9.3.4 Traceability of Change Requests and Orders to Configuration Items
9.3.5 Traceability of Change Requests and Orders to Product Structure
9.3.6 Reuse of Change Requests and Orders
9.3.7 Reverse Traceability
9.4 Configuration Management
9.4.1 Committee Membership
41 9.4.2 Configuration Management Plans and Processes
9.4.3 Evidence for Authorization
9.4.4 Configuration Audit
9.4.5 Evidential Weight
9.5 Data Management
9.5.1 Evidential Weight
42 9.5.2 Audit of Evidential Weight
9.6 Product Structure Management
9.6.1 Multiple Product Structures
9.6.2 Relations between Product Structures
9.6.3 Substructures of Product Structures
43 9.7 Product Data Database
9.7.1 Database Elements
9.7.2 Mapping Archived Data to Current System
10 Administration and monitoring
44 11 Definition of Archive Information Packages for PDM Data
11.1 General
45 11.2 Content Information
11.2.1 Items in a Structure
46 11.2.2 Relationships
11.2.3 Product Structures
11.3 Packaging Information
11.4 Preservation Description Information
47 11.5 Digital Signature Information
12 Conformance Classes
48 12.1 Concept of Conformance Classes
12.2 Three Conformance Levels are used in this standard
12.2.1 Low: Viewing format only
12.2.2 Medium: Partly re-usable Data
12.2.3 High: Fully re-usable data
49 12.3 Benefits of Conformance Levels
12.3.1 Covering Different Use Cases
12.3.2 Covering Different Views Of The Product Data
12.3.3 Allowing scaled system auditing/certification

Related products

BS EN 9300-200:2018
$198.66