1、ASD STANDARD NORME ASD ASD NORM prEN 9300-012 Edition P 1 October 2006 PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATIONGulledelle 94 - B-1200 Brussels - Tel. + 32 2 775 8126 - Fax. + 32 2 763 3565 - www.asd-stan.orgICS: Descriptors: ENGLISH VERSION Aerospace
2、series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 012: Reference process description Ingest Srie arospatiale LOTAR Archivage Long Terme et rcupration des donnes techniques produits numriques, telles que CAD 3D et PDM Partie 01
3、2 : Description du processus de rfrence Soumission Luft- und Raumfahrt LOTAR Langzeitarchivierung und Bereitstellung digitaler technischer Produktdokumentationen, beispielsweise 3D CAD und PDM Daten Teil 012: Referenzprozessbescheibung Aufnahme This “Aerospace Series“ Prestandard has been drawn up u
4、nder the responsibility of ASD-STAN (The AeroSpace and Defence 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 p
5、ublication of this Prestandard, the technical content shall not 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
6、European Standard (prEN) to CEN (European Committee for Standardization) 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 stan
7、dards conflicting with the EN. Edition approved for publication 31 October 2006 Comments should be sent within six months after the date of publication to ASD-STAN Engineering Procedures and Processes Domain Copyright 2006 by ASD-STAN prEN 9300-012:20062 Contents Page Foreword3 1 Scope 4 2 Normative
8、 references 4 3 Terms, definitions and abbreviations4 4 Applicability4 5 Ingest 5 6 Detailed process steps description .5 6.1 General5 6.2 Submit for Ingest .6 6.3 Receive data.6 6.4 Check quality assurance.6 6.5 Send confirmation .7 6.6 Generate AIP 7 6.7 Approval Content Information7 6.8 Error han
9、dling for denied SIP.8 6.9 Receive Confirmation8 6.10 Error handling for generate AIP .8 7 Support Process Steps: Preservation Planning.8 8 Data descriptions.8 8.1 General8 8.2 Involved roles.9 8.3 Involved data9 9 Definition Transfer to Data Generation (Milestone) 10 Bibliography. 11 Figure Figure
10、1 Overview of Ingest process5 prEN 9300-012:20063 Foreword This standard was prepared jointly by ASD-STAN and the PROSTEP iViP Association. The PROSTEP iViP Association is an international non-profit association in Europe. For establishing leadership in IT-based engineering it offers a moderated pla
11、tform to its nearly 200 members from leading industries, system vendors and research institutions. Its product and process data standardization activities at European and worldwide levels are well known and accepted. The PROSTEP iViP Association sees this standard and the related parts as a mileston
12、e of product data technology. Users should note that all standards undergo revision from time to time and that any reference made herein to any other standard implies its latest edition, unless otherwise stated. prEN 9300-012:20064 1 Scope EN 9300-012 provides a detailed description for the recommen
13、ded process of transferring data to the archive as overviewed in EN 9300-010. This transfer includes the conversion of the Content Information into the archiving format STEP and the generation of the Archive Information Package. Further the main focus for the process description is on the validation
14、 and verification of the converted Content Information. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (inclu
15、ding any amendments) applies. ISO 14721:2003, Space data and information transfer systems Open archival information system Reference model OAIS. EN 9300-003, Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 003: Fun
16、damentals and concepts. 1)EN 9300-007, Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 007: Terms and References. 1)EN 9300-010, Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product
17、 documentation such as 3D, CAD and PDM data Part 010: Overview Data Flow. 2)3 Terms, definitions and abbreviations For the purposes of this standard, the terms, definitions and abbreviations given in EN 9300-007 shall apply. 4 Applicability This EN 9300-012 is applicable to new 3-D product data reco
18、rds and may be applicable to existing 3D product data records, on current and earlier products, produced using previous regulations, standards and procedures. The current version is focused on product data as defined in the domain specific parts. 1) In preparation at the date of publication. 2) Publ
19、ished as ASD Prestandard at the date of publication of this standard. prEN 9300-012:20065 5 Ingest See Figure 1. Figure 1 Overview of Ingest process During the Ingest process the data producer submits the Submission Information Package (SIP) from the working into the archiving environment. The archi
20、ve receives the data packages and checks if the SIP contains data of the recommended format and generates the Archiving Information Package (AIP) afterwards. After submitting the SIP to the archive the source data gets the status read only. Input data: SIP Output data: AIP Content Information (CI) S
21、IP 6 Detailed process steps description 6.1 General Input and output data described in this standard represent the minimal requirements for the fulfilment of the process steps. Additional data may be added, but must match at a minimum the requirements for the information package. (See EN 9300-003, s
22、ection 5.3.2.1 “Definition of the core model”). prEN 9300-012:20066 6.2 Submit for Ingest The producer initiates the submission of the SIP from his personal working environment to the archive. With the initiation of the submission the producer applies the approval for that SIP. A further change of t
23、he content data should not be possible otherwise the changed data must be archived by a new approval and data preparation process. Input data: SIP Output data: SIP 6.3 Receive data The archive receives the SIP for archiving from the producing system through data transfer. The SIP shall be kept withi
24、n the archives working environment for further processing during the ingest process. Input data: SIP Output data: SIP 6.4 Check quality assurance A function within the Archive environment checks the quality of the ingested data. This includes the successful transfer of the SIP to the staging area. F
25、or digital submissions, these mechanisms may include Cyclic Redundancy Checks (CRCs), or checksums associated with each data file, or the use of system log files to record and identify any file transfer, or checking for media read/write errors. In addition to OAIS recommendations, the function check
26、s the types of data formats used and the existence of PDI within the received SIP. The exchanged data and its representations must be stipulated in the ingest agreement between the archive and the producer. Stipulations may cover aspects such as CAD data formats and Model files or PDM data formats s
27、uch as STEP. The agreement shall include, at a minimum, the specification of: the key characteristics of the product information to preserve, the Descriptive Information of the SIP, the acceptance criteria used for the verification, the validation properties of the source information to archive, the
28、 related KPIs. Each agreement will be archived itself, as part of the context information of the new category of product information to archive. Input data: SIP Data formatting and document standards prEN 9300-012:20067 Output data: If the quality assurance check is successful: SIP Confirmation Info
29、rmation Otherwise: Error report 6.5 Send confirmation The archive creates a report of the successful receiving of the SIP into the archives working environment. Input data: Confirmation Information Output data: Confirmation report 6.6 Generate AIP The archive performs the generation of an Archival I
30、nformation Package (AIP) automatically. This includes the conversion of the Content Information (with validation) from the submitted native format into the archiving format, the validation of the converted data, and the generation of any additional Preservation Descriptive information (PDI) and Desc
31、riptive Information (the meta data for the Content Information). “Generate AIP” shall ensure that the design intent of the source file of the producer is preserved conforming to the domain specific parts. It is based on the verification and on the validation of the key characteristics of the product
32、 data. Input data: SIP Output data: If generation is successful: AIP If generation fails: Error report. The failure of the generation of the AIP is related to the conversion of the representation of the Content Information to its final format and its validation 6.7 Approval Content Information This
33、process step is recommended, but not mandatory, and is applicable only to new data. This step synchronizes with the producers engineering approval process (not shown), such that the final engineering approval is only given if the information passes the archiving criteria, and conversely, the archive
34、 only proceeds if the engineering approval is given. NOTE In effect this step means that, if the data is not fit to archive, it is not fit to be approved for use. Since many of the archive checks should be performed automatically, putting archivability as a quality gate before engineering approval m
35、eans that the cost of an additional (expensive) engineering approval is avoided if the data needs rework in order to be archived. prEN 9300-012:20068 Input data: AIP Output data: AIP CI 6.8 Error handling for denied SIP The producer should perform an error check in the case that the data is rejected
36、 by the archive. Further, the Producer should restart the Data Preparation, which includes the changing of the data, in order to make it fit to archive. Input data: Error report Output data: SIP (identifying the data) 6.9 Receive Confirmation The producer receives the archives confirmation report. I
37、nput data: Confirmation report 6.10 Error handling for generate AIP Within this process the Producer and/or the Administrator has to perform an error handling procedure. This includes the decision whether data is still usable or has to be generated again. The administrator will be informed. Input da
38、ta: Error report 7 Support Process Steps: Preservation Planning The process provides services and functions for monitoring the environment of the archive and recommendations to ensure that the information stored in the archive remains accessible to the consumer over the long term, even if the origin
39、al computing environment becomes obsolete. Preservation Planning functions include developing recommendations for archive standards and policies and monitoring changes in the technology environment, archiving format and the addressed consumer. Output data: Data formatting and document standards 8 Da
40、ta descriptions 8.1 General The descriptions here are informative; the definitions are found in the part EN 9300-007. prEN 9300-012:20069 8.2 Involved roles 8.2.1 Archive The Archive is the archiving environment, which usual supports at least the key functions of an archiving architecture according
41、to ISO 14721:2003 (OAIS). Key functions are administration, data management, archival storage, access control, preservation planning. 8.2.2 Producer The producer is an organization, person, or client system, which provides the information to be preserved. This can include other archives or internal
42、archive personnel or system components. Typical roles of type “producer“ may be. System Designers, Design Engineers, Subcontractors, Manufactures or Test Engineers. 8.2.3 Approving team Represents the approving organizations of a company. The approving team approves the AIP before the AIP is stored
43、within the Archive. 8.3 Involved data 8.3.1 Archival Information Package (AIP) The AIP consists of the following elements: Content Information (CI) (archiving formatted and optionally native formatted) Packaging Information (PI) Preservation Description Information (PDI) (Validation Properties, cont
44、ext information for the Content Information) Digital Signature Information The Content Information is the set of information that the producer requires to retain and has all the qualities needed for permanent storage. Packaging information is the information that is used to bind and identify the com
45、ponents of an Information Package. Preservation Description Information is the information which is necessary for adequate preservation of the Content Information and which can be categorized as Provenance, Reference, Fixity, and Context information. Digital Signature Information is the information
46、about authenticity (identify the signature-key-owner), data integrity and time stamp. 8.3.2 Submission Information Package (SIP) The SIP consists of following main information objects: CI (native formatted data) PDI (Validation Properties, context information regarding the CI) PI 8.3.3 Content Infor
47、mation (CI) The Content Information includes the set of information that is the original target of preservation. 8.3.4 Confirmation Information Contains the information that the relevant process was performed. prEN 9300-012:200610 8.3.5 Confirmation report Gives the role the information that the rel
48、evant process was performed successfully. 8.3.6 Data formatting and document standards Supporting data from preservation planning 8.3.7 Error report Represents error information showing the kind of error occurring during relevant process steps. 9 Definition Transfer to Data Generation (Milestone) Ev
49、ery process step is started by a milestone. The use of milestones allows the integration of required references to and from other processes. The definition of milestones is out of scope for EN 9300 generally. Furthermore the description of the milestone Transfer to Data Generation is necessary. The data generation process is not under the direct influence of EN 9300 and will be defined within each company separately. Definition Transfer to Data Genera
