ASD-STAN PREN 9300-115-2012 Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D CAD and PDM data Part 115 Explicit CAD as.pdf

《ASD-STAN PREN 9300-115-2012 Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D CAD and PDM data Part 115 Explicit CAD as.pdf》由会员分享，可在线阅读，更多相关《ASD-STAN PREN 9300-115-2012 Aerospace series LOTAR LOng Term Archiving and Retrieval of digital technical product documentation such as 3D CAD and PDM data Part 115 Explicit CAD as.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM prEN 9300-115 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 115: Explicit CAD assembly structure Srie arospatiale LOTAR Archivage Long Terme et rcupration des donnes techniques produits numriques, telles que CAD 3D

3、et PDM Partie 115 : Structure dassemblage CAO explicite Luft- und Raumfahrt LOTAR Langzeitarchivierung und Bereitstellung digitaler technischer Produktdokumentationen, beispielsweise 3D CAD und PDM Daten Teil 115: Explizite CAD-Baugruppenstrukturen This “Aerospace Series“ Prestandard has been drawn

4、up under 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 t

5、he publication 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 dr

6、aft 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

7、standards conflicting with the EN. Edition approved for publication 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-115:2012 (E) 2 White page Foreword This standard was pr

8、epared jointly by AIA, ASD-STAN, PDES Inc 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

9、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. PDES Inc is an international non-p

10、rofit association in USA. The mission of PDES Inc is to accelerate the development 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 resear

11、ch organizations. PDES Inc. supports this standard as an industry resource to 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 revisio

12、ns and that any reference made herein to any other standard implies its latest 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

13、standard under the number NAS 9300xxx. The content in the EN 9300 and NAS 9300 documents will be the same. The differences will be noted in the reference documentation (i.e. for EN 9300 Geometric Dimensioning The management of different occurrences of the same part that have different geometry; The

14、management of different occurrences of the same part that have different attributes; The archiving of assembly-by-constraint (where, for example, the position of a part is given as “perpendicular to part X“, rather than given as a positioning matrix); The archiving of the Geometrical Dimensioning an

15、d Tolerance (GD The archiving of assembly Form Features. NOTE Product assembly structure may be defined based on the data base management system approach. This case uses other fundamental concepts not covered in this part. See family EN 9300-2xx. 2 Normative references The following referenced docum

16、ents 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 (including any amendments) applies. EN 9300 (All parts), Aerospace series LOTAR LOng Term Archiving and Retrieval o

17、f digital technical product documentation such as 3D, CAD and PDM data ISO 10303-44:2000, Industrial automation systems and integration Product data representation and exchange Part 44: Integrated generic resource: Product structure configuration PDM and CAX implementor forum documents: “Usage Guide

18、 for the STEP PDM schema v1.2“ Released 4.3 January 2002; “Recommended Practices for External References with References to the PDM Schema Usage Guide“; “Recommended Practices for Geometric Validation Properties“; “Recommended practices for Assembly Validation Properties“; 3 Terms, definitions and a

19、bbreviations For the purposes of this standard, the terms, definitions and abbreviations given in EN 9300-007 shall apply. 4 Applicability Refer to applicability of EN 9300-001, paragraph 4. prEN 9300-115:2012 (E) 7 5 Business specifications for the long term archiving and retrieval of the explicit

20、CAD assembly structure 5.1 Use cases The following sections record the potential use cases for the archiving of an explicit CAD assembly structure. “Annex A: Recommended archiving scenarios“ identifies the main archiving scenarios corresponding to these two use cases. 5.1.1 UC1: Full archiving The t

21、erm “full archiving“ is used where the complete assembly structure is archived as a single unit, and all the assembly structure data are contained in the same Submission Information Package (SIP). The assembly may be contained in one file or in a set of files (see Figure 3: archiving overview of the

22、 submission information package). Figure 3 Archiving overview of the submission information package 5.1.2 UC2: Bottom up and incremental archiving The assembly structure is archived subset by subset. The assembly structure files are submitted in different submission information packages. For example

23、, in bottom-up archiving, the assembly structure files are submitted from the lower level up to the top level (see Figure 4). Figure 4 Bottom up archiving of the assembly structure 6 Essential information for explicit CAD assembly structure The following list describes the essential information for

24、a CAD assembly structure. The essential information are captured, verified and validated through the core model and the rules. The core model is described in the section “7 Validation rules off an explicit CAD assembly structure 96H“ and the rules are described in the sections “97H8 Verification rul

25、es of CAD explicit assembly structure“ and “9 Validation rules off an explicit CAD assembly structure“. prEN 9300-115:2012 (E) 8 1. CAD Nodes representing part and assembly Part identification: Part number: Unique Identifier of a part; Name: Human readable name of the part (e.g. bolt-CHC-M6); Descri

26、ption: Additional human readable information about the part; Version (optional): Unique identification of the version (e.g. A001). Part properties /attributes (optional): View / context of definition: e.g. As Designed; Systems Unit (mm, ). Occurrence / Instance identification (optional) 2. CAD Assem

27、bly structure relationship Child / parent identification Identification of the two nodes - the parent and the child (optional: Occurrence/ Instance identification for the parent and the child); Geometric positioning Defining the location and orientation of the related geometric component relative to

28、 the relating geometric assembly, eg., Positioning matrix (translation X, Y,Z, Rotation, ); 3. References on sub-assembly files or 3D model files This information is only relevant to leaf nodes representing parts. External Part identification: part number, name, description, version; External file i

29、dentification: Name: Unique identifier of the file; Version (optional): Unique identifier of the file version. File properties: Format: Specification of the file format, e.g., ISO 10303-214; Type: For a geometry file, identification of the type of geometry, e.g. surface model, closed volume, solid m

30、odel etc. prEN 9300-115:2012 (E) 9 Files reference namelocationFormatrelationshipFather child identificationOccurrence identification PositioningAssembly relationshipFather child identificationOccurrence identification Positioningfather fatherchildchildAnd / orAdditional Properties or attributesAsse

31、mbly identification IdentifierNamedescription Part or Assembly identification IdentifierNamedescription father fatherAdditional Properties or attributesAssembly identification Ide ntifierNamedescription Additional Properties or attributesAssembly identification Identif ierNamedescription Files refer

32、ence namelocationFormatPart or Assembly identification IdentifierNamedescription Figure 5 Main essential objects of the assembly file to be preserved 7 Definition of Core Model for an explicit CAD assembly structure 7.1 Core model STEP AIM level The core model is based on a subset of the STEP PDM sc

33、hema v1.2 and the associated usage guide PDM. The STEP PDM Schema is a core set of entities in STEP that support the concepts for Product Data Management (PDM). The PDM Schema has been established to promote interoperability between STEP APs (AP214 and AP203) in the area of product data management.

34、The following list identifies which subsets of the “usage Guide for the STEP PDM schema v1.2“ are reused for the core model of the part 115. 1 Part Identification 1.1 Part as Product 1.1.1 Product Master Identification 1.1.2 Context Information / Next assembly 1.1.3 Type Classification 2 Specific Pa

35、rt Type Classification 2.1 Classification of parts and managed documents prEN 9300-115:2012 (E) 10 3 Part Properties 3.1 General Part Properties 3.1.1 Properties Associated with Product Data 3.2 External Part Shape 3.2.1 Geometric Shape Property 3.2.3 Relating Externally Defined Part Shape to an Ext

36、ernal File 3.3 External Geometric Model Structure 3.3.1 Relating Part Shape 3.3.3 Additional Geometric Model Structures 3.4 Relative Orientation and Location of Related Geometric Models i. Implicitly defined transformations between geometric models 4 Part Structure and Relationships 4.1 Explicit Ass

37、embly Bill Of Material 4.2 Multi-Level Assembly Digital Mock Up 4.3 Different Views on Assembly Structure 4.4 Relating Part Shape Properties to Product Structure 4.4.2 Implicit Relationships Between Assembly Components 7 External Files 7.1 External File Identification 9 Document and File Properties

38、9.1 Product Definition or Document Representation 9.2 Document content property 9.3 Document creation property 9.4 Document format property 9.5 Document size property 9.6 Document source property 9.8 Document type classification 9.8.1 Document type classification for document files 16 Measure and un

39、its 16.1 Measure with unit specification 16.2 Unit definition 16.2.1 Simple and predefined units 16.2.2 Converted units 16.2.3 Derived units 16.2.4 User defined units In addition, the document “Recommended Practices for External References with References to the PDM Schema Usage Guide“ defines the c

40、ore model for the file reference. prEN 9300-115:2012 (E) 11 8 Verification rules of CAD explicit assembly structure 8.1 Rules description The following section describes the verification rules to apply to the archived data. This list is not exhaustive, and can be adapted and extended to meet the nee

41、ds of a particular business situation. 8.1.1 Unique CAD assembly structure A file must contain an unique assembly structure. The following figure illustrates a file that is considered invalid because it contains two assembly structures which are not logically connected / related. Figure 6 Illustrati

42、on of a quality issue: a file containing multiple assembly structures 8.1.2 No orphans Each node has to be linked to the assembly structure by an assembly relationship. The following figure illustrates a file that is considered invalid because it contains an orphan node. Figure 7 Illustration of a q

43、uality issue: a file containing an orphan node 8.1.3 Acyclic assembly structure The assembly structure must be a directed acyclic graph (that is, it must not contain a loop-back in which a node is the parent of a higher assembly). The following figure illustrates a file that is considered invalid be

44、cause it contains an assembly A including an assembly B and an assembly B includes assembly A. Figure 8 Illustration of a quality issue: a file containing a cyclic structure prEN 9300-115:2012 (E) 12 8.1.4 Content of the assembly occurrences Multiple occurrences of the same assembly must be composed

45、 of the same parts. The following figure illustrates a file that is considered invalid because it contains a first occurrence of the assembly B composed of parts C and D and a second occurrence of the assembly B composed of parts C and E. Figure 9 Illustration of a quality issue: a file containing a

46、ssembly occurrences with different content 8.1.5 3D explicit positioning of assemblies and parts Several occurrences of the same assembly must be composed with the same parts and the relative position of the parts within that assembly. The following figure illustrates a file that is considered inval

47、id because the positioning of the part D in the assembly B_1 is different to that in the second occurrence B_2. A_1B_1 B_2C_1 D_1 C_2 D_1Tx2 Rx2Ty2 Ry2Tz2 Rz2Tx4 Rx4Ty4 Ry4Tz4 Rz4Tx4 Rx4Ty4 Ry4Tz4 Rz4Tx6 Rx6Ty6 Ry6Tz6 Rz7Tx5 Rx5Ty5 Ry5Tz5 Rz5Figure 10 Illustration of a quality issue: a file containi

48、ng assembly occurrences with positioning issue 8.1.6 Identification of parts and assemblies Each part and each sub assembly in the assembly structure must have a unique identifier. 8.2 Definition of verification level for EN 9300-115 The different verification levels correspond to the rules used dur

49、ing the verification. The different validation levels are: EN 9300-115-Ingest-verification-level-0: No verification. This level of validation corresponds to a high level of risk of data or information loss; EN 9300-115-Ingest-verification-level-1: Verification of the rules defined in section 8.1H above. This is the usual level of validation; EN 9300-115-Ingest-verification-level-2: Both the validation rules defined in section 8.1 above and additional rules specific to the company and not