BS EN 9300-003:2012 BSI Standards Publication Aerospace series — LOTAR — Long term archiving and retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 003: Fundamentals and concepts BS EN 9300-003:2012 BRITISH STANDARD National foreword This British Standard is the UK implementation of EN 9300-003:2012 The UK participation in its preparation was entrusted to Technical Committee ACE/1, International and European Aerospace Policy and Processes A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © The British Standards Institution 2012 Published by BSI Standards Limited 2012 ISBN 978 580 73887 ICS 01.110; 35.240.30; 49.020 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2012 Amendments issued since publication Date Text affected BS EN 9300-003:2012 EN 9300-003 EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM September 2012 ICS 01.110; 35.240.30; 49.020 English Version Aerospace series - LOTAR - Long term archiving and retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 003: Fundamentals and concepts Série aérospatiale - LOTAR - Archivage long terme et récupération des données techniques produits numériques, telles que CAD D et PMD - Partie 003: Fondamentaux et concepts Luft- und Raumfahrt - LOTAR - Langzeit-Archivierung und Bereitstellung digitaler technischer Produktdokumentationen, wie zum Beispiel von 3D-, CADund PDM-Daten - Teil 003: Grundlagen und Konzepte This European Standard was approved by CEN on 10 March 2011 CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels © 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members Ref No EN 9300-003:2012: E BS EN 9300-003:2012 EN 9300-003:2012 (E) Contents Page Foreword 4 Scope 5 Normative references 5 Terms, definitions and abbreviations 6 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.3 4.4 Major differences of terms 6 Introduction 6 General 6 Invariance .6 Objectives for keeping digital data 6 Length of time of keeping data 7 Stored Form 7 Terminology 8 General 8 Product information model 8 Product model 9 Business Application 9 Retention 10 Long Term Archiving 10 Scope of EN 9300 11 Relation to Legal Admissibility Standards 12 Applicability 13 6.1 6.2 6.2.1 6.2.2 6.2.3 6.3 6.3.1 6.3.2 6.3.8 Overview of referenced standards .13 General 13 Introduction to OAIS — ISO 14721 .13 General 13 The OAIS Environment 14 The OAIS model 14 Introduction to ISO 10303 15 General 15 ISO 10303-203:1994 and Edition draft, Configuration controlled 3D designs of mechanical parts and assemblies 17 ISO 10303-214:2001 and ISO 10303-214:2003, Core Data for Automotive Mechanical Design Processes 17 ISO 10303-233, System engineering data representation .18 ISO 10303-209:2001, Composite and metal structural analysis and related design 18 ISO 10303-237, Computational fluid dynamics 18 ISO 10303-210:2001 and Edition draft, Electronic assembly, interconnect and packaging design 18 ISO 10303-212:2001, Electro technical design and installation 18 7.1 7.2 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 Fundamentals and concepts 18 Overview .18 Processes .20 Data .20 Archiving Product Models vs Archiving Documents 20 Data content 22 Data formats 24 Archiving approach for complex product models 25 Data quality assurance 25 6.3.3 6.3.4 6.3.5 6.3.6 6.3.7 BS EN 9300-003:2012 EN 9300-003:2012 (E) 7.3.6 7.4 7.5 7.6 Process phases and cycles 27 Mapping approach onto physical data representations 30 Fundamentals for testing the LOTAR process and components 31 System Architecture Framework 33 Description methods 33 BS EN 9300-003:2012 EN 9300-003:2012 (E) Foreword This document (EN 9300-003:2012) has been prepared by the Aerospace and Defence Industries Association of Europe - Standardization (ASD-STAN) After enquiries and votes carried out in accordance with the rules of this Association, this Standard has received the approval of the National Associations and the Official Services of the member countries of ASD, prior to its presentation to CEN This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by March 2013, and conflicting national standards shall be withdrawn at the latest by March 2013 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights 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 platform 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 milestone 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 According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom BS EN 9300-003:2012 EN 9300-003:2012 (E) Scope This European Standard defines basic terms, e.g Long Term Archiving and Retention and identifies the context and scope of EN 9300 The section Fundamentals describes the basic concepts and approaches of EN 9300 and referenced related standards Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies EN 9103, Aerospace series — Quality management systems — Variation management of key characteristics 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) ISO 10303-203:1994 and Edition draft, Industrial automation systems and integration — Product data representation and exchange — Part 203: Application protocol: Configuration controlled 3D designs of mechanical parts and assemblies ISO 10303-209:2001, Industrial automation systems and integration — Product data representation and exchange — Part 209: Application protocol: Composite and metallic structural analysis and related design ISO 10303-210:2001, Industrial automation systems and integration — Product data representation and exchange — Part 210: Application protocol: Electronic assembly, interconnection, and packaging design ISO 10303-212:2001, Industrial automation systems and integration — Product data representation and exchange — Part 212: Application protocol: Electrotechnical design and installation ISO 10303-214:2001 and ISO 10303-214:2003, Industrial automation systems and integration — Product data representation and exchange — Part 214: Application protocol: Core data for automotive mechanical design processes ISO/DIS 10303-233, Industrial automation systems and integration — Product data representation and exchange — Part 233: Systems engineering data representation1) ISO 10303-237, Industrial automation systems and integration — Product data representation and exchange — Part 237, Application protocol: Fluid dynamics1) ISO 14721, Space data and information transfer systems — Open archival information system — Reference model ARP9034, A Process Standard for the Storage, Retrieval and Use of Three-Dimensional Type Design Data BP 0008, Code of Practice for Legal Admissibility and Evidential Weight of Information Stored electronically * And all parts quoted in this standard 1) In preparation at the date of publication of this standard BS EN 9300-003:2012 EN 9300-003:2012 (E) Terms, definitions and abbreviations For the purposes of this document, the terms, definitions and abbreviations given in EN 9300-007 apply Major differences of terms 4.1 Introduction 4.1.1 General Different user communities have different definitions for long term archiving and retention This clause explains the major differences of both terms and their relation to the scope of EN 9300 Companies within the aerospace industry need to keep data to fulfil business, certification and legal requirements For modern definitions this data is usually digital These requirements lead to four main areas of consideration regarding the retention of digital data Invariance: how important is it to ensure that digital data is not altered Objectives: why keeping of digital data is required Length of time: the required length of time for retaining digital data Stored Form: the stored format of the digital data The following subchapters consider these questions for long term archiving and retention and are the basis for the scope definition of EN 9300 The scope of EN 9300 is a combination of aspects from long term archiving and retention 4.1.2 Invariance Invariance covers the need to ensure that the information has not changed and so provide evidential weight that the design intent has not changed, see Figure 13 Three categories can be distinguished: Auditable – where validation methods and test suites ensure that information cannot be changed without the change being detected Implicit – where the system is designed to prevent changes The system must supervise activities which would result in changes of the digital data The supervision, for example, could be realized within a separate write-protected vault The proof of "no change" is shown by an absence of change having been recorded AND that by showing that the system itself is reliable Not required – where changes to data are not explicitly controlled Of the three, auditable invariance is the strongest, and is likely to be the most suitable where the information is used in legal proceedings 4.1.3 Objectives for keeping digital data For digital data, the challenge is that the data are often stored in a proprietary, native format and will most likely become not interpretable after a time The use of a neutral archiving data format safeguards the interpretability of the stored data for a much longer time, perhaps for the entire retention period EN 9300 recommends the use of standard formats for long term archiving rather than native formats, accompanied by regular and frequent migrations of storage media and, if necessary, of data format Because a data migration may lead to data loss, usually time stamps and digital signatures (which are used ensuring the integrity and immutability of archived data/ data packages) have to be renewed The use of auditable archiving and retrieval processes ensures the data readability and integrity within current and future systems BS EN 9300-003:2012 EN 9300-003:2012 (E) The objectives for keeping the data are distinguished into two major subcategories: Legal requirements/certification requirements, such as for proof of technical documentation for actions in law Business requirements, such as keeping knowledge Within the two subcategories EN 9300-003 offers four characteristics which describe the objectives in more detail: To preserve the original data (generated by a source system) so that it can be used as evidence of what data was at a particular date This characteristic fits with the subcategory ‘legal requirement’ To keep data available to new users over the period for which it is kept This characteristic fits with the subcategories ‘legal requirement’ and ‘business requirement’ To be able to preserve the source of the kept data This characteristic fits with the subcategory ‘business requirement’ To be able to reuse the data, for example, by modifying design data to meet new requirements This characteristic fits with the subcategory ‘business requirement’ 4.1.4 Length of time of keeping data The life cycle of software and hardware is relatively short compared to the life cycle of aircraft The life cycle of digital data can be described in terms of software versions and generations The release of a new software version within a generation general alters only a small part of the functionalities of the software without affecting the data format A generation change occurs when the software used changes substantially, for example, to a new architecture The change of a generation may result in new data formats Currently, for CAD software, the period between versions is of the order of months to 12 months, while between generations is of the order of years to10 years This should be compared to an aircraft life cycle which may be 30 years to 50 years or longer This gives rise to the following definitions within EN 9300: Short term - within one or two versions Medium term - within one generation Long term - over multiple generations Additionally to the technical aspects, legal requirements have to be considered when defining archiving terms For further information see EN 9300-001 (Structure) and EN 9300-002 (Requirements) 4.1.5 4.1.5.1 Stored Form General A key distinction is between a representation and a presentation In a representation, the computer holds the information about the concept, whereas in a presentation the computer holds a form which is its appearance to a human For example, a musical score is a representation of a piece of music, whereas a recording of the piece is a presentation The stored form has been divided into three main subcategories: Detail Level: the description level of model; Representation: describing the different logical forms of data representation; Format: describing the different physical formats of the data BS EN 9300-003:2012 EN 9300-003:2012 (E) 4.1.5.2 Detail level An accurate representation is where data elements are described in the original level of detail, independent of whether they are represented in a native or other format; An approximate representation is where data elements are described in a lower level of detail than the accurate representation, e.g where a curved surface is approximated by a set of small, flat faces 4.1.5.3 Representation A native representation is that created by and private to the source system; A derived representation is a transformation of the native data, which may be based on a native format or on a standardized format, e.g a html version may be derived from a text document as an alternative representation; A presentation is a visualization of data to a user, e.g a drawing or a print out of product structure information as a snapshot of the current data representation 4.1.5.4 Format A native format is a specific format of data in a syntax which is proprietary and dependent on a specific system or interface A native format depends directly on the life cycle (versions, generations) of the related system or interface; A standardized open format is a format of data in a syntax, which is defined by a broad community, such as by ISO, and which is independent of specific system or interface “Open” means completely and precisely documented in syntax and semantics and is applicable for free In addition, standardisation processes regulates the change processes for the standard Note that the motivation for including the accurate and approximate representation is that both may be archived in parallel in a standard representation such as STEP, which is openly documented and which may be stable for a much longer period than native formats 4.2 Terminology 4.2.1 General From descriptions in 4.1, the following definitions of terms are derived: Product information model, Product model, Business Application, Retention and Long Term Archiving These definitions are used within EN 9300 4.2.2 Product information model The Product information model represents an information model which provides an abstract description of facts, concepts and instructions about a product, e.g STEP ) Application reference model or STEP Application interpreted model 2) ISO 10303-1:1994 BS EN 9300-003:2012 EN 9300-003:2012 (E) standard allows for the association of contextual information with the product model, and may mandate certain elements of that information 7.3.2 7.3.2.1 Data content General The data content of the information packages is divided into four categories: The core model; The required metadata; The engineering approvals data (as an electronic signature); The validation information The various pasts in the EN 9300-1xx and 2xx series detail each of the categories for each type of product model, together with the data quality criteria that apply to each category 7.3.2.2 Definition of the core model The core models identify the essential minimum of data which are required to preserve the design intent for a given purpose The domain specific parts of EN 9300 identify a purpose or set of purposes through appropriate use cases, and therefore the core model which is required to support the business cases The core model is defined as a system of data elements together with their representation and interpretation and the data quality criteria they must meet The use of the core model does not preclude the archiving of additional information or the duplication of information using alternative formats These may provide additional functionality, either in terms of retaining additional design knowledge or in providing interoperability with a particular tool set However, it is to be recognised that there is at greater risk of this information being unusable within the lifetime of the archive The extent of this additional information is identified in the ingest agreement The following figure illustrates the way a core model for a single geometric part may be extended to include both additional information and formats 22 BS EN 9300-003:2012 EN 9300-003:2012 (E) Key essential information set e g Part110: shape of a single part within general tolerance extension in format extension in information Figure 10 — Concept of a core model 7.3.2.3 Meta data Metadata is data required for the management and use of information packages In EN 9300, the scope considered is limited to data used to retrieve the package and data used to validate the data and its provenance E.g for a part: part number; part name; part description; model name; model originator; date of origin; approval; quality check results; intellectual property right information The scope of the metadata depends on the particular use cases it applies to, and is detailed in the domain specific parts These also detail any data quality criteria applicable to the metadata Additional metadata may be applied, and should be agreed in the ingest agreement Data used in the internal management of the archive is outside of the scope of EN 9300 In addition the detailed Intellectual property right information may be explicitly identified, described, documented in the Archival Information package during the Ingest and after Retrieval process 23 BS EN 9300-003:2012 EN 9300-003:2012 (E) 7.3.2.4 Definition of digital (engineering) signatures A digital (engineering) signature supports a business release process With it the data producer asserts that the prepared data fits with the process and quality requirements from the engineering point of view Similarly to meta data, the digital (engineering) signature is domain dependent and the use of it should be agreed between the producer and the archive A digital (engineering) signature may allow an identification of the approver 7.3.3 7.3.3.1 Data formats General The standard considers different data formats within archiving processes 7.3.3.2 Native 3D model geometry representation The native data representation is system dependent and out of scope for EN 9300 7.3.3.3 Archive format For the core models data, representations and formats used shall be open and standardized “Open” means completely and precisely documented in syntax and semantics and shall be applicable for free ISO 10303 (STEP) is available for no more than the publication costs Standardization ensures the common understanding by the designated community and public availability and stability over many years Standardisation processes ensure regulated change processes Therefore, in EN 9300, ISO 10303 (STEP) Application Protocols such as 214 –“Core Data for Automotive Mechanical Design Processes” or 203 (Edition 2) “Configuration Controlled 3D Designs of Mechanical Parts and Assemblies” are the preferred protocols for 3D geometry and product structure data (see 6.3) Additional conventions such as the “PDM Schema”3) may be agreed for a company specific archive implementation and are also supported by EN 9300 although not ISO 10303 issued Other STEP Application Protocols are also within the scope of EN 9300, even though they are currently not referenced 7.3.3.4 Archive signatures EN 9300 aims to guarantee the integrity of the stored documents/data packages Therefore the following signatures will be used within EN 9300: Digital (engineering) signatures (personal created signatures) guaranteeing the integrity of the content of digital data Digital time signature (automatic created signatures) safeguarding the integrity of the archived data packages during the storage period The further usage and application of digital signatures will be described in EN 9300-005 7.3.3.5 Digital (engineering) signature A digital signature is a sort of seal of digital data It is produced by using mathematical algorithm with the help of a private cryptographic key With the help of the related public key the signature can be checked at any time to identify the signature-key-owner and to proof the integrity of the data The digital signature may follow the rules given by, among other: 3) The “PDM (Product Data Management) Schema” is an industrial agreement for a reference information model for the exchange of a central, common subset of the data being managed within a PDM system It represents the intersection of requirements and data structures from a range of STEP Application Protocols, all generally within the domains of design and development of discrete electro/mechanical parts and assemblies 24 BS EN 9300-003:2012 EN 9300-003:2012 (E) Directive in 1999/93/EC of the European parliament and the council from the 13th of December, 1999 about collective basic conditions of digital signature The signature has to be renewed every approximately 5-6 years For EN 9300, therefore, the digital signature will be used to safeguarding the data integrity for the short period between the producers' release and the transfer to the archive system 7.3.3.6 Digital time signature A digital time signature is characterized by the addition of an automatic created time stamp to the digital signature The integrity of the stored data can be rechecked at any time The renewal of the digital time signature has to be proved by the business The length of the validity period of the production algorithm is defined by law The current German production algorithm has to be renewed approximately every 20 years The digital time signature will be used within the Archival Storage process, see EN 9300-013 7.3.3.7 Information packages - Preservation Description Information (PDI) The PDI identifier (ID) defines the information which is necessary to preserve the interpretation of the Content Information and which can be categorized as Provenance, Reference, Fixity, and Context information According to OAIS, the four categories can briefly describe as follows: Provenance describes the source of the Content Information, who has had custody of it since its origin, and its history (including processing history); Context describes how the Content Information relates to other information outside the Information Package For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available in the archive; Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another; Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration For example, it may involve a check sum over the Content Information of a digital Information Package 7.3.4 Archiving approach for complex product models It is assumed that complex and large product models can be structured into a set of sub models, which simplifies their representation and avoids duplication at ingest by incrementally archiving the sub models and capturing the overall context by cross reference mechanisms Those mechanisms will be defined within the appropriate domain specific parts (1xx and 2xx series) This approach applies especially to the archiving of product structure data and will therefore be used and defined in parts 115 (CAD-assembly-model structure) and 220 (PDM-Part-Assembly-product structure) 7.3.5 7.3.5.1 Data quality assurance General The key approach of data quality is conformance to agreed specification for the data From the OAIS this will be defined through the Ingest agreement, and assurance is characterized by: data checks at preparation, validation, 25 BS EN 9300-003:2012 EN 9300-003:2012 (E) verification Data quality assurance is performed through data validation and verification (7.3.5.2, 7.3.5.3) and is required to be performed prior to the ingest process Furthermore data quality assurance is required for attested copies of archived data within the retrieval process to ensure correct delivery of the data to the consumer 7.3.5.2 Definition of validation properties EN 9300 defines sets of Validation Properties The Validation Properties are used within automatic or manual processes to check the consistency of data content during transformations from one representation and/or format into another representation and/or format EN 9300 defines domain specific validation properties, for example, for CAD and PDM Further extensions of validation properties are possible by user agreement The use of validation properties is mandatory, ensuring the data integrity and process security Recommended subsets of STEP validation properties are described within EN 9300-100 series and EN 9300-200 series A validation property should be something that is relatively simple to compute, compact to store, but which detects the most important errors It is recommended to use at a minimum validation properties for the key and the global characteristics of the object the validation properties are assigned to For example, geometric models may include validation criteria such as surface area, volume, or centre of gravity, which are highly sensitive to errors in the model Engineering correctness is out of scope for the validation properties Validation properties in EN 9300 analyse only the correctness of the representation of the core model However, it should be noted that an invalid representation is often an indication of an engineering error 7.3.5.3 Definition and application of verification rules Whereas the purpose of validation is to ensure that the information that has been captured is right, the intention of verification is to ensure, that the data is correctly represented Verification rules shall ensure that a data representation meets the quality requirements within defined tolerances A verification is successful if no verification rule is violated The verification rules are domain specific and are defined within the EN 9300-1xx series and EN 9300-2xx series Only verification rules belonging to the core models are part of EN 9300 The following figure gives an overview about the concept of validation and verification Figure 11 — Concept of validation/verification 26 BS EN 9300-003:2012 EN 9300-003:2012 (E) As a consequence EN 9300-1xx series or EN 9300-2xx series will contain chapters defining the core model and its essential information set (as described in EN 9103 as key characteristics), the quality verification and validation rules and a detailed definition of the assignment of information to the sub packet of the AIP The key characteristics has to be explicitly identified, described, documented and checked in the Archival Information package during the Ingest and after Retrieval process 7.3.6 Process phases and cycles Key AIP Archival Information Package DIP Dissemination Information Package SIP Submission Information Package VP Validation Properties a Data conversion b c Data validation Source/Target Representation d e Data definition Archive Representation f Archive Data definition Figure 12 — Overview of data conversion and data definitions Because submission and retrieval are separated by the passage of time - up to 30 years to 50 years or longer in the case of the aerospace industry - it is not possible to directly validate the retrieved information against that submitted originally The various cycles of translation and validation shown in the figure link together to form an unbroken chain of validations, with the intention that this chain validly demonstrates that the submission is not altered by the process of archive and retrieval EN 9300 defines a sequence of phases for archiving derived from the OAIS standard Within each phase the data will be converted from one representation into another The quality of conversion results will be validated 27 BS EN 9300-003:2012 EN 9300-003:2012 (E) by the usage of predefined validation properties The main phases are Data Preparation, Ingest, Archival Storage, Access and Retrieval: 1) the data will be prepared for archiving The source representation (application data in native format native representation, see 4.1.5) will be converted into the target representation SIP (Submission Information Package, defined as the source document for the archiving process) The data verification ensures the data quality for both representations Quality control of native formatted data is strongly recommended to ensure efficient data generation and data preparation The definition of data quality controls for data generation is out of scope for EN 9300 2) the source representation SIP will be converted into the target representation AIP An accurate representation of data, (see 4.1.5) will be transferred into the archives storage section The end of the conversion process (source representation into target representation) closes a domain specific release process by setting a digital time signature From this moment the data package AIP represents the digital original EN 9300 recommends the declaration of the digital original as the only relevant source representation for 3D product data, comparable with a released and signed paper for 2D drawing The validation properties ensure the integrity and consistency of both representations 3) the data selection represents the first step of the retrieval process The accurate representation (AIP) will be selected by a consumer or administrator during the access process The target representation (a selection list) will be generated, additionally a copy of the selected accurate representation may be prepared The management information ensures the available selection items meet the access rights management policy 4) during the retrieval process the target representation DIP will be generated from the requested selection list items The DIP is a derived representation (see 4.1.5) and contains a digital copy of the accurate representation The derived representation has to fulfil the requirements for the target application data and will be transferred to the consumer The validation properties ensure the integrity and consistency of both representations The following Figure 13 gives an explicit example 28 BS EN 9300-003:2012 EN 9300-003:2012 (E) Figure 13 — Explicit process example During the long term Archival Storage period the accurate representation (AIP) may possibly be converted into a new archiving representation The conversion of the archiving representation (see Figure 14, case D) represents a worst case scenario and should be avoided as long as possible The use of standards supports the constancy for the archive format within storage period The conversion of the archive representation (see Figure 14, case D) increases the potential danger of unauthorized changes during the conversion process It is necessary to review data consistency and reset the digital time signature 29 BS EN 9300-003:2012 EN 9300-003:2012 (E) Figure 14 — Special use cases Figure 14 provides an overview about the special use cases which can occur during the archiving period The standard use case (t = constant) says that the digital original representation will not be changed during its storage period In the exceptional (special) use cases it could be possible to change the representation 7.4 Mapping approach onto physical data representations EN 9300 recommends a three level approach (see Figure 15) Figure 15 — Mapping approach onto physical data representation The first level defines the domain specific view Within this view the engineering data required for archiving will be identified 30 BS EN 9300-003:2012 EN 9300-003:2012 (E) The second level defines the representation of the data The representation is equivalent to a data schema (such as the PDM Schema) and will be based on the requirements coming from domain specific view The second level shall define the schema following existing standards The third level defines the archiving format of the data, such as STEP Part 21 or XML 7.5 Fundamentals for testing the LOTAR process and components The objective of testing the LOTAR process and components is certification of the entire LOTAR environment The test checks for the software and hardware components chain shall be part of an audit of the environment High data quality requirements, which ensure the interpretability of archived data in the future, make the definition of test methods essential Test methods shall be established for data and processes in scope The testing of archiving processes and data quality can be supported by well defined, certified test suites The test suites will perform quality checks using the verification rules and by comparison of validation property values Within a test suite two types of functional test scenarios shall be covered: “Good”, i.e correct test files (without any error) “Bad” test files, which includes known errors to test the verification and validation systems The correct test cases are used to check the accuracy, for example, of the conversion process from SIP to AIP or AIP to DIP representation In this case the validation properties shall be generated firstly by the source system for the test case and then secondly within the target system after data conversion of the source representation into the target representation The comparison of both data representations (of the source and target representation) is performed using the validation properties If the result is in a defined tolerance, the component has passed the “good” test scenarios The following Figure 16 shows the basic procedure for comparison of validation properties, following the process phase number ‘transfer to archive’, (see Figure 12) 31 BS EN 9300-003:2012 EN 9300-003:2012 (E) Key AIP Archival Information Package DIP Dissemination Information Package SIP Submission Information Package VP Validation Properties a b Data conversion Data validation c d Source Representation Data definition e f Target Representation Data definition Figure 16 — Data validation by comparison of defined validation properties In the case of the “bad” test scenarios, the process component should end with an explicit error either identifying the failure within the source representation or with a result outside the defined tolerance frame Further test suites shall be used to test the components, verifying a specific data representation against the defined verification rules In the case of “good” test scenarios, the component should pass the test files without a detection of a rule violation In the case of “bad” test scenarios the component shall identify completely and correctly the object(s) violating the verification rules and which rules are violated The main motivation for establishment of EN 9300-016 (Test Suites) is to enhance the reliability of archived product data for aerospace companies archiving product data following certified processes The aim of the test suites is to prove that the processes and tools will be able to detect data quality deficits, as defined in other parts of EN 9300, and to ensure the unchangeability of the data This ability is central points to EN 9300 These main points are: Processes Programs Archiving system itself, (out of scope of EN 9300) Testing shall be implemented in several levels: The first test level is covers the process consistency The tests shall demonstrate correct performance of the processes, i.e the correctness of results at the end of process steps (e.g AIP or SIP) This level shall be audited by an independent authority The second test level covers the integrated archiving tools, such as data conversion tools This includes validation of conversions - e.g from the source format and representation into the recommended archiving 32 BS EN 9300-003:2012 EN 9300-003:2012 (E) format (STEP ISO 10303) It describes requirements for testing for STEP Files These requirements build on ISO 10303 Parts 31, 32 and 34, which define conformance testing for STEP The third test level covers the archiving system itself This should include checks on the realization of the main functions, such as the correct implementation of access rights, the use of the correct storage media or the provision of search results during a retrieval process This test level is out of scope of EN 9300 7.6 System Architecture Framework EN 9300 provides a conceptual system architecture overview (see EN 9300–006 ‘System Architecture Framework’) The intention of the system architecture is to define the interaction between the IT-systems involved The system architecture supports the definition of terms as well as the consistency of archived data and processes Description methods For the establishment and later interpretation of standards it is important to ground the information in a common understanding Accepted and standardized description methods support this aim EN 9300-004 provides details for the methods used within the standard, such as UML or EXPRESS 33 This page deliberately left blank This page deliberately left blank NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW British Standards Institution (BSI) BSI is the national body responsible for preparing British Standards and other standards-related publications, information and services BSI is incorporated by Royal Charter British Standards and other standardization products are published by BSI Standards Limited About us Revisions We bring together business, industry, government, consumers, innovators and others to shape their combined experience and expertise into standards -based solutions Our British Standards and other publications are updated by amendment or revision The knowledge embodied in our standards has been carefully assembled in a dependable format and refined through our open consultation process Organizations of all sizes and across all sectors choose standards to help them achieve their goals Information on standards We can provide you with the knowledge that your organization needs to succeed Find out more about British Standards by visiting our website at bsigroup.com/standards or contacting our Customer Services team or Knowledge Centre Buying standards You can buy and download PDF versions of BSI publications, including British and adopted European and international standards, through our website at bsigroup.com/shop, where hard copies can also be purchased If you need international and foreign standards from other Standards Development Organizations, hard copies can be ordered from our Customer Services team Subscriptions Our range of subscription services are designed to make using standards easier for you For further information on our subscription products go to bsigroup.com/subscriptions With British Standards Online (BSOL) you’ll have instant access to over 55,000 British and adopted European and international standards from your desktop It’s available 24/7 and is refreshed daily so you’ll always be up to date You can keep in touch with standards developments and receive substantial discounts on the purchase price of standards, both in single copy and subscription format, by becoming a BSI Subscribing Member PLUS is an updating service exclusive to BSI Subscribing Members You will automatically receive the latest hard copy of your standards when they’re revised or replaced To find out more about becoming a BSI Subscribing Member and the benefits of membership, please visit bsigroup.com/shop With a Multi-User Network Licence (MUNL) you are able to host standards publications on your intranet Licences can cover as few or as many users as you wish With updates supplied as soon as they’re available, you can be sure your documentation is current For further information, email bsmusales@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK We continually improve the quality of our products and services to benefit your business If you find an inaccuracy or ambiguity within a British Standard or other BSI publication please inform the Knowledge Centre Copyright All the data, software and documentation set out in all British Standards and other BSI publications are the property of and copyrighted by BSI, or some person or entity that owns copyright in the information used (such as the international standardization bodies) and has formally licensed such information to BSI for commercial publication and use Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI Details and advice can be obtained from the Copyright & Licensing Department Useful Contacts: Customer Services Tel: +44 845 086 9001 Email (orders): orders@bsigroup.com Email (enquiries): cservices@bsigroup.com Subscriptions Tel: +44 845 086 9001 Email: subscriptions@bsigroup.com Knowledge Centre Tel: +44 20 8996 7004 Email: knowledgecentre@bsigroup.com Copyright & Licensing Tel: +44 20 8996 7070 Email: copyright@bsigroup.com