1、ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM prEN 9300-002 Edition P 1 May 2012 PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATIONAvenue de Tervuren, 270 - B-1150 Brussels - Tel. + 32 2 775 8126 - Fax. + 32 2 775 8131 - www.asd-stan.orgICS: Descriptors: ENGLI
2、SH VERSION Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 002: Requirements Srie arospatiale LOTAR Archivage Long Terme et rcupration des donnes techniques produits numriques, telles que CAD 3D et PDM Partie 002 :
3、 Exigences Luft- und Raumfahrt LOTAR Langzeitarchivierung und Bereitstellung digitaler technischer Produktdokumentationen, beispielsweise 3D CAD und PDM Daten Teil 002: Anforderungen This “Aerospace Series“ Prestandard has been drawn up under the responsibility of ASD-STAN (The AeroSpace and Defence
4、 Industries Association of Europe - Standardization). It is published for the needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned Domain following member comments. Subsequent to the publication of this Prestandard, the technical content shall no
5、t be changed to an extent that interchangeability is affected, physically or functionally, without re-identification of the standard. After examination and review by users and formal agreement of ASD-STAN, it will be submitted as a draft European Standard (prEN) to CEN (European Committee for Standa
6、rdization) for formal vote and transformation to full European Standard (EN). The CEN national members have then to implement the EN at national level by giving the EN the status of a national standard and by withdrawing any national standards conflicting with the EN. Edition approved for publicatio
7、n 01 May 2012 Comments should be sent within six months after the date of publication to ASD-STAN Engineering Procedures and Processes Domain Copyright 2012 by ASD-STAN prEN 9300-002:2012 (E) 2 Foreword This standard was prepared jointly by AIA, ASD-STAN, PDES Inc and the PROSTEP iViP Association. T
8、he PROSTEP iViP Association is an international non-profit association in Europe. For establishing leadership in IT-based engineering it offers a moderated platform to its nearly 200 members from leading industries, system vendors and research institutions. Its product and process data standardizati
9、on activities at European and worldwide levels are well known and accepted. The PROSTEP iViP Association sees this standard and the related parts as a milestone of product data technology. PDES Inc is an international non-profit association in USA. The mission of PDES Inc is to accelerate the develo
10、pment and implementation of ISO 10303, enabling enterprise integration and PLM interoperability for member companies. PDES Inc gathers members from leading manufacturers, national government agencies, PLM vendors and research organizations. PDES Inc. supports this standard as an industry resource to
11、 sustain the interoperability of digital product information, ensuring and maintaining authentic longevity throughout their product lifecycle. Readers of this standard should note that all standards undergo periodic revisions and that any reference made herein to any other standard implies its lates
12、t edition, unless otherwise stated The Standards will be published under two different standards organizations using different prefixes. ASD-Stan will publish the standard under the number EN 9300xxx. AIA will publish the standard under the number NAS 9300xxx. The content in the EN 9300 and NAS 9300
13、 documents will be the same. The differences will be noted in the reference documentation (i.e. for EN 9300 Geometric Dimensioning EN 9300 describes related requirements applicable for this constraint. (See also EN 9300-003 “Fundamentals and Concepts“). Then, this document describes requirements for
14、 standardized processes (and associated technologies) that ensure product data are retrievable, reproducible and usable for the required retention period. The long term archiving and retrieval process is described in terms of the Open Archival Information System (OAIS) Reference Model ISO 14721.2003
15、 that provides a conceptual framework for archive systems. prEN 9300-002:2012 (E) 6 The long term archiving and retrieval process is structured into sub-processes for: Ingest: introducing new material into the archive, Data management: managing the data and metadata, Archive storage: managing the ph
16、ysical systems, Access: retrieving information and providing it to users and Preservation planning: planning the evolution of the repositories. Specific requirements for the archiving of product data are put into this framework. 6 Key requirements Within the aerospace industry, a lot of requirements
17、 are known for a risk mitigation with respect to certification and legal demands. The following list of requirements are categorized into: Acceptance (see paragraph 6.1), Legal demand (see paragraph 6.2), Security (see paragraph 6.3), Certification (see paragraph 6.4). 6.1 Acceptance The first requi
18、rement category covers users acceptance of the manageability of archived documents and the minimizing of costs of archiving within the long term archiving system: Table 1 Requirements of category “Acceptance“ No. Requirement AC1 Each document within an archive has to be retrievable AC2 Each document
19、 has to be found in a predefined time frame (e.g. 3 days required by JAR) AC3 The life cycle costs for archiving and access shall be minimized AC4 The data (a copy of the archived data) shall be available for further use or manipulation (preservation of the design intent), but possibly with limited
20、functionality with respect to the original source. (For example, one use case may only be required to visualize the model and measure distances between the geometric entities, while another may require updates to the model, which in turn entails that the original parametric information would need to
21、 be preserved.) AC5 A planned retention period shall be provided for archived documents/data, i.e., a point in time when a document or a set of data has reached its retention period it must be reviewed prior to removal. The Archive system provides a report that the document has been removed from the
22、 archive. 6.2 Legal Requirements The second requirement category covers the compliance with legal demands. Because of the fact that legal demands (LD) are not fully described by laws, the following list of requirements covers the known and expected demands. prEN 9300-002:2012 (E) 7 Table 2 Requireme
23、nts in category “Legal Requirements“ No. RequirementLD1 The ability to verify that a part or product conforms to its archived documentation (a form of configuration audit) LD2 The users shall be enabled to meet the provisions of relevant laws regarding data security and protection of data privacy ov
24、er the life cycle of the archives LD3 The processes of archiving and retrieval shall be auditable The goal of requirement LD1 is to ensure the conformity of a part or product with the associated documentation. Requirement LD2 ensures the ability of the long term archiving system to provide informati
25、on about aspects of IT security. Throughout the IT security the long term archiving system ensures the integrity of archived data during archiving time and protects data against unauthorized changes. It requires auditable archiving and retrieval processes. 6.3 Security and integrity The third requir
26、ement category covers the various aspects of integrity and accuracy. The first priority for accuracy and integrity is to retrieve the same content for a document as it was archived. The second priority is that the content of a document is semantically understood in the same way as when it was create
27、d (i.e. preservation of the design intent of the user by the formal description of the key characteristics of the information to be preserved), meassures should be provided which enable ckecking of predefined properties (validation properties based on the essential information) of the digital produc
28、t documentation against given quality parameters. prEN 9300-002:2012 (E) 8 Table 3 Requirements of category “Security“ No. Requirement S1 It shall be impossible to destroy a document during its scheduled lifetime. S2 Each document1shall be protected against unauthorized changes while archived. S3 Th
29、e document retrieved shall match search criteria. According to a predefined relevant method. S4 All actions that change the organization and structure of data within the archives shall be recorded so that it will be possible to retrieve of the original contents over the complete retention period. S5
30、 Documentation and data structure (e.g. Product Structure, documents, physical documents, and product definition models) shall be retrievable and reproducible for the retention period required. This may exceed the period of 50 years. S6 It is required to provide supporting evidence that product met
31、the design rules from the period when the design was archived. S7 Guarantee the integrity (ensure information is persistent and unaltered) of data for the period required which may exceed the period of 50 years. S8 The risk, expenses and costs arising from change of the archiving system or its relea
32、se shall be managed, (i.e. via a cost model etc.). S9 Electronic archives shall be designed to allow migration to new platforms, media, software versions and components without loss of information. S10 The information content of the document shall not be changed during the archiving, retrieval and m
33、igration processes S11 Each document should be able to be displayed and represented consistent with the form as recorded. (This will assure the archived data is unchanged.) S12 The processes by which the document is inserted into an archive, migrated or retrieved from the archive should not delete o
34、r remove any document from the archive, and should be certifiable to this effect Document removal will be dictated by a retention schedule and determined by an archive administrator. S13 The archive shall provide fixity information against each archived document / set of data. Evidence of security o
35、f an archive may also be provided through a certified process. S14 The archiving system shall provide adequate measures when technically feasible to check predefined properties within the documents which enable that information are understandable by the Designated Community without the assistance of
36、 the information producers. Furthermore this requirement should be supported where required by providing links to the documents describing the correct interpretation of the context and content of an archived document. It is required to provide the contextual information (methods, procedures, guideli
37、nes, ) associated with the product information, in order to ensure its correct interpretation after retrieving S15 An audit trail for the archiving process is required. This provides assured information about the actions of relevant processes, and may provide evidence about what occurred. S16 Collec
38、tion management is required. I.e. archiving processes which include CAD or PDM data, documents, etc. Supporting information should be managed within the Archive Information Packages (AIP). S17 The archive shall record the information about the management of access rights. 6.4 Certification This cate
39、gory covers further requirements which shall be fulfilled for the archiving of type design documents relevant for certification of a product. Based on an analysis of certification standards and guidelines the ASD-STAN LOTAR came to the conclusion, that the requirements resulting from certification d
40、emands are less restricted than of the other three categories above, therefore certification requirements are already covered by the requirements listed above. prEN 9300-002:2012 (E) 9 6.5 Requirements Refinement The business requirements identify the business functions that the archive shall suppor
41、t, however these give no detailed criteria for assessment of whether a particular implementation will meet those requirements. The OAIS standard provides a reference to compare different archiving standards, but does not mandate any particular approach to the solution. It has been recognised that OA
42、IS gives a thorough and effective analysis of the archiving problem, and can be used as the starting point for defining a normative standard. Therefore, the detailed requirements below use the OAIS standard terminology to define a normative set of requirements for the process to archive digital prod
43、uct documentation and data. These requirements can be divided into key process requirements and concomitant process requirements. Key process requirements are those needed to meet the business requirements. Concomitant requirements arise from the decision to formulate the requirements in terms of th
44、e OAIS model, and are required to give a complete and consistent process. 7 Application of the OAIS Model 7.1 The Open Archive Information System (OAIS) Reference Model The problem of archiving data is not unique to the aerospace industry. In the aeronautics industry, the Consultative Committee for
45、Space Data Systems developed the Reference Model for an Open Archival Information System (OAIS). This model is a framework for describing archiving systems and processes. The OAIS model has been the basis of a number of archiving systems in several industries and is considered a mature model. The OA
46、IS functional model is separated into seven functional entities (Common Services, Ingest, Archive Storage, Data Management, Administration, Preservation Planning and Access) and related interfaces. See Annex A, Figure A.1. EN 9300 standard series is described in terms of the OAIS model, and requirem
47、ents are allocated against the elements of the OAIS reference model. A brief overview is described in the part 9300-003 “Fundamentals and Concepts“, paragraph 4.1. and a summary of the terms used in the model is provided in Annex A. For clarity, the detailed description of the operational processes
48、is included in the relevant requirement sections. 7.2 Product Data Archiving using the OAIS Model Product Data is created throughout the complete product lifecycle. This data is authorized and approved through controlled processes. The data for a particular product is archived in the repository for
49、the required archiving period. Users who require access to the product data may include regulatory agencies, customers, organizations that support in-service operations, design organizations for updates and re-use, etc. The use of an OAIS repository for the archiving of data is shown in Figure 1. prEN 9300-002:2012 (E) 10 Figure 1 Product data archiving using the OAIS Model In order to meet the anticipated requirements of the consumers, the key characteristics of the data shall be identified. For example, for the automatic machining of a mechanical par
