1、ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM ASD-STAN prEN 9300-200 Edition P 1 June 2016 PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATION Rue Montoyer 10 - 1000 Brussels - Tel. + 32 2 775 8126 - Fax. + 32 2 775 8131 - www.asd-stan.orgICS: Descriptors: ENGL
2、ISH VERSION Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data Part 200: Common Concepts for LOng Term Archiving and Retrieval of Product Structure Information Luft- und Raumfahrt LOTAR Langzeitarchivierung und Bereitstell
3、ung digitaler technischer Produktdokumentationen beispielsweise 3D CAD und PDM Daten Teil 200: Allgemeine Konzepte fr die Langzeitarchivierung und Wiederverwendung von Produktstruktur-Informationen Srie arospatiale LOTAR Archivage long terme et rcupration des donnes techniques produits numriques tel
4、les que CAD 3D et PDM Partie 200 : Concepts gnraux pour larchivage long terme et la rutilisation des informations de structure de produits This “Aerospace Series“ Prestandard has been drawn up under the responsibility of ASD-STAN (The AeroSpace and Defence Industries Association of Europe - Standard
5、ization). 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 not be changed to an extent that interchangeab
6、ility is affected, physically or functionally, without re-identification of the standard. After examination and review by users and formal agreement of ASD-STAN, the ASD-STAN prEN will be submitted as a draft European Standard (prEN) to CEN (European Committee for Standardization) for formal vote an
7、d 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. ASD-STAN Technical Committee approves that: “This document i
8、s published by ASD-STAN for the needs of the European Aerospace Industry. The use of this standard is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” ASD-STAN reviews each
9、standard and technical report at least every five years at which time it may be revised, reaffirmed, stabilized or cancelled. ASD-STAN invites you to send your written comments or any suggestions that may arise. All rights reserved. No parts of this publication may be reproduced, stored in a retriev
10、al system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of ASD-STAN. Order details: E-mail: salesasd-stan.org Web address: http:/www.asd-stan.org/ Edition approved for publication 1stJune 2016 Comments sho
11、uld be sent within six months after the date of publication to ASD-STAN Engineering Procedures Domain Copyright 2016 ASD-STAN prEN 9300-200:2016 (E) 2 Foreword This standard was prepared jointly by AIA, ASD-STAN, PDES Inc. and the PROSTEP iViP Association. The PROSTEP iViP Association is an internat
12、ional 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 le
13、vels 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 development and implementation of ISO 10303,
14、 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 sustain the interoperabity of digi
15、tal product information, ensuring and maintaining authentic longevity throughout their product life cycle. Readers of this standard should note that all standards undergo periodic revisions and that any reference made herein to any other standard implies its latest edition, unless otherwise stated T
16、he 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 documents will be the same. The dif
17、ferences will be noted in the reference documentation (i.e. for EN 9300 Geometric Dimensioning (2) one of a series of sequentially created units or instances of a product. Configuration ISO 10303-214:2010(E) A Configuration is the association of a Class_condition_association or a Class_specification
18、_association object with a design or with a process in order to define a valid usage of it in the context of a certain Product_class. NOTE 1 The validity of the association may be limited by a time period through assigning an Effectivity object to it. NOTE 2 The semantics of the kind of association
19、is defined by the attributes configuration_type and inheritance_type. Configuration ISO 9000:2000. Arrangement of the elements of a system. Configuration control ISO 10007. Activities comprising the control of changes to a configuration item after formal establishment of its configuration documents.
20、 Configuration management EIA 649 B. A management process for establishing and maintaining consistency of a products performance, functional, and physical attributes with its requirements, design and operational information throughout its life. Configuration management EN 9300-007: 2007. (1) The dis
21、cipline of managing the information relating to a product design, encompassing planning and management, change management, configuration identification, status accounting and audit. NOTE This is the preferred sense in the aircraft industry, and in the EN 9300 documentation. (2) The rules relating to
22、 the choice and combinations of options used when configuring a particular physical example of a product. Content ISO/IEC 82045, 3.2.2. Subject information of a document. prEN 9300-200:2016 (E) 11 Data ISO/IEC 2382-1:1993. Reinterpretable presentation of information in a formalized manner suitable f
23、or communication, interpretation or processing. Designated community EN 9300-003:2007. From OAIS, the community for which the system is designed. In the case of EN 9300, it is the community that will use the information retained in an archive. Document EN 9300-007:2007. This term covers a family of
24、usages, from a physical paper document, through electronic files which can be thought as representing a document, to synthetic view derived from multiple sources for which the users conceptual model is that of reading a document. See also EN 9300-003, 5.3.1 “Archiving Product Models vs. Archiving Do
25、cuments“. Domain specific part EN 9300-007:2007. LOTAR parts are either general or domain specific. LOTAR parts 100 upwards are the domain specific parts, and deal with the particularities of each type of data such as 3D CAD. The general parts (1 to 99) apply tom all types of data. Effectivity. Attr
26、ibute associated with PDM structures which define application of PDM structure nodes and associated documents to individual units. Values of effectivity attribution may include options, range of units, and date. A resolved product structure is determined by evaluating effectivity for selected option
27、s, range, and/or date. Effectivity EIA 649 B. A designation, defining the product range; e.g. serial numbers, block numbers, batch numbers, lot numbers, model, dates or event, at which a specific product configuration applies, a change is to be or has been affected, or to which a variance applies. E
28、ffectivity ISO 10303-214:2010(E), 4.1.25. This unit of functionality provides the capability to represent information concerning the validity of data. Implicit propagation of data specifying validity is not available. The validity of data can be expressed by effectivities that specify time ranges wi
29、thin which data may be used and by retention periods that specify how long data have to be kept and when they may or have to be deleted. Both concepts can make use of explicit dates or of dates expressed by events in order to represent the relevant points in time. Effectivity ISO/IEC 82045, 3.4.2. I
30、dentification of the valid use of a document version tracked by date or event. Electronic signature EN 9300-007:2007. A defined method to sign an object in electronic environments. It provides means to authenticate the signatory and the signed object in an unambiguous and safe way by attaching to or
31、 logically associating data in electronic form to other electronic objects. (See EN 9300-005) Evidential weight EN 9300-007:2007. From Code of Practice for Legal Admissibility, in the case where electronic information is used as evidence in a court case, the degree of reliance that the information i
32、s what it purports to be. Fixity information EN 9300-007:2007. Ancillary information that show a particular set of information is unchanged. Management data See metadata. Maturity level ISO/IEC 82045, 3.4.1. Purpose-oriented degree of completeness of information with regard to the intended final obj
33、ect which is reflected in documents. Media EN 9300-007:2007. The physical material on which data is recorded, such as an optical disc. Metadata EN 9300-007:2007 (1) Data about data. For example, the file name is meta data about a CAD design held as a file. (2) The data required for the management an
34、d use of information packages. NOTE This is the preferred sense in the EN 9300 documentation. prEN 9300-200:2016 (E) 12 Metadata for documents ISO/IEC 82045. Data for the description of documents and their management. Object IEC 61346-1, modified. Entity treated in the process of design, engineering
35、, realization, operation, maintenance and demolition. NOTE 1 The entity may refer to something, which is either physical or non-physical or to a set of information associated with it. NOTE 2 Depending on its purpose, an object may be viewed in different ways called “aspects”. OAIS model EN 9300-007:
36、2007. The Open Archival Information System reference model (see normative references). Preservation planning EN 9300-007:2007. From the OAIS model, the services and functions for monitoring the environment of the OAIS and providing recommendations to ensure that the information stored in the OAIS re
37、mains accessible to the Designated User Community over the long term, even if the original computing environment becomes obsolete. Presentation EN 9300-007:2007. (of data) the transformation of data into a form readable or viewable by a human (see also Representation). For example, a point may be di
38、splayed as a dot on a computer screen. (cf. Representation) Primary technical data EN 9300-200:2015. Models, drawings, and documents essential to describing, defining, verifying, etc. the product. Product IEC 61346-1, 3.3.1. Intended or accomplished result of labor labour, or of a natural or artific
39、ial process Product, part, item and article EN 9300-007:2007. In general aerospace usage during the design phase, Part, Item and Article are treated as synonyms referring to unitary parts or simple assemblies that are treated as a single unit, such as composite material part or an electrical connect
40、or. The term Product tends to be used to refer to something that is complex and deliverable, such as an aeroplane. In ISO 10303, Product is the general class of any deliverable, from individual components upwards, and allows for the fact that even a simple bolt is the product of a bolt manufacturer.
41、 ISO 10303-239 (PLCS) uses Part as a subtype of Product to identify the design of a physically realisable component or assembly, as distinct from other subtypes such as Product_breakdown or Interface. It also uses the term Product_as_realised to distinguish a physical realisation of a design from th
42、e design itself. That is, the terminology is context sensitive. Since the initial focus of LOTAR was the design phase for the manufacturers of aircraft and aircraft engines, the terminology follows the general aerospace usage. Product data management (PDM) EN 9300-007:2007. The tracking, control and
43、 status control of product data, either as files, or through a database. The usage is frequently confined to the design stage of product development, although may extend to planning for manufacture. Product information model EN 9300-003, 3.2.1. The product information model is an information model w
44、hich provides an abstract description of facts, concepts and instructions about a product, such as a STEP Application reference model or STEP Application interpreted model. Product life cycle ISO 15226, 3.3.2. Period from the conceptual idea to the ultimate disposal of a product Product life cycle m
45、anagement (PLM) EN 9300-007:2007. The tracking, control and status control of product data, either as files, or through a database. PLM extends the scope of PDM to include each physical product produced from a design, including deviations from the design and usage of the product. Product management
46、data. The product management data describe the primary technical data generically in a PDM framework, independently of their specific type (CAD data, for example), which are described in the domain specific parts of EN 9300 series. prEN 9300-200:2016 (E) 13 Product model EN 9300-003, 3.2.2. The Prod
47、uct model represents an occurrence of a product information model for a particular product, e.g. the geometric model of part a123. Provenance EN 9300-007:2007. The information describing the context in which information was created. Product structure EIA 649 B. A hierarchical view of the relationshi
48、p of products and component products. Provenance EN 9300-007:2007. The information describing the context in which information was created. Representation EN 9300-007:2007. The way in which a concept is modeled as a system of data elements. For example, a point may be defined as a set of three numbe
49、rs, representing its x, y, and z co-ordinates (cf. presentation). Static information. Information that is unchanging. For example, the product structure that results when resolved for a specific effectivity value. Use case EN 9300-007:2007. A description of a particular situation in which the system is used. Use cases form a part of the UML methodology (cf. EN 9300-004 section 5 and UML reference). Validation EN 9300-007:2007: (1) The assurance that a collection of information has the correct
