Ediz.: Issue: Firma Signature. Data Date 07/11/ /11/ /11/2014

Transcription

1 Tipo Doc.: Doc.Type: N Doc.: Doc. N : TECHNICAL NOTE N DRD: DRD N : NA 1 Di Of Titolo: Title : Preparato da: Prepared by: Nome &Funzione Name & Function MWI Team Firma Signature Data Date LISTA DI DISTRIBUZIONE DISTRIBUTION LIST Interna / Internal N A I MWI Team 1 X Approvato da: Approved by: T. Lupi (CGS-SE) L. Cremonesi (CGS-PA) C. Cinquepalmi (CGS-CC) 10/11/24 Applicazione autorizzata da: Application authorized by: F. Tominetti (CGS-PM) Esterna / External ESA 1 X Customer / Higher Level Contractor Accettato da: Accepted by: Approvato da: Approved by: N=Numero copie A=Applicazione I=Informazione N=Number copy A=Application I=Information Gestionedocumenti: Data Management: Firma / Signature Data / Date File: MOS-TN-CGS-MWI- 0028_Is1_CAD_Data_Exchange.docx

2 2 EDIZIONE ISSUE DATA DATE REGISTRAZIONE DELLE MODIFICHE / CHANGE RECORD AUTORIZZAZIONE CHANGE AUTHORITY First issue OGGETTO DELLA MODIFICA E SEZIONI AFFETTE REASON FOR CHANGE AND AFFECTED SECTIONS

3 3 LISTA DELLE PAGINE VALIDE / LIST OF VALID PAGES PAGINA PAGE EDIZIONE ISSUE PAGINA PAGE EDIZIONE ISSUE PAGINA PAGE EDIZIONE ISSUE PAGINA PAGE EDIZIONE ISSUE PAGINA PAGE EDIZIONE ISSUE 1 -

4 4 TABLE OF CONTENTS 1. DOCUMENT SCOPE AND APPLICABILITY SCOPE APPLICABILITY REFERENCES RELATED DOCUMENTS BACKGROUND DOCUMENTS DEFINITIONS AND ABBREVIATIONS DEFINITIONS ABBREVIATIONS TERMS CAD DATAV EXCHANGE WORKFLOW SCHEMA DATA EXCHANGE AGREEMENT (DEA) MODEL CHECK BEFORE SENDING NOTICE OF TRANSFER NOTICE OF RECEIPT MODEL CHECK OF RECEIVED DATA NOTICE OF ACCEPTANCE ASTRIUM CAD SYSTEM CONFIGURATION APPLICABLE CATIA VERSION DIGITAL MOCK UP MANAGEMENT SYSTEM PLATFORM ASTRIUM NAMING CONVENTION CAD MODEL MAIN REFERENCE FRAME CAD MODEL LEVEL OF DETAIL GENERAL PREPARATION OF THE DATA MISCELANEOUS SENDING NATIVE CATIA V5 FILES GENERAL COMMENTS CATIA V5 CONFIGURATION FILES STRUCTURE, NAMING AND NUMBERING OF A V5 FILE GENERAL SAVE CONDITIONS FOR V5 FILES SAVE CONDITIONS FOR V5 CATPART FILES EXCHANGE OF CATPARTS EXCHANGE OF CATPRODUCTS EXCHANGE OF CATDRAWINGS SPECIAL ELEMENTS D-CATALOGUES D-CATALOGUES FINAL CONTROL - MODEL CHECKS SUPPLIER/PARTNER CAD ENVIRONMENT: CATIA V FORMAT FOR SINGLE MODEL EXCHANGE FORMAT FOR CAD ASSEMBLY EXCHANGE FORMAT FOR CAD DRAWING EXCHANGE CATIA MODEL PRECISION SUPPLIER/PARTNER CAD ENVIRONMENT: OTHER THAN CATIA V FORMAT FOR SINGLE MODEL EXCHANGE FORMAT FOR CAD ASSEMBLY EXCHANGE FORMAT FOR CAD DRAWINGS EXCHANGE... 12

5 5 8. DATA EXCHANGE MEDIA FOR UNIX ENVIRONMENT FOR WINDOWS ENVIRONMENT FOR «WINDOWS TO UNIX» OR «UNIX TO WINDOWS» TRANSFER TRANSFER OF FILES PREPARING AND SENDING NATIVE UNIGRAPHICS NX 7.5 FILES GENERAL COMMENTS LAYERS AND ATTRIBUTES OF A UNIGRAPHICS FILE IMPLEMENTATION OF MASS PROPERTIES INFORMATION GENERAL SAVE CONDITIONS FOR A UNIGRAPHICS FILE CREATION AND EXCHANGE OF PARTS CREATION AND EXCHANGE OF ASSEMBLIES CREATION AND EXCHANGE OF DRAWINGS...

6 6 LIST OF FIGURES Figure 9-1: Load Options definition LIST OF TABLES Table 1-1: CAD Exchange Data Format Priority... 7 Table 2-1: Applicable Documents... 8 Table 2-2: Adtional Acronyms... 8 Table 7-1: Physical properties summary table (case neutral 3D format) Table 9-1: Layers conventions for NX 7.5 files... 14

7 7 1. DOCUMENT SCOPE AND APPLICABILITY 1.1 SCOPE This document specifies the requirements for the CAD data exchange e.g. how to prepare and check the data before senng it to the Instrument Prime and the acceptance checking at the Instrument Prime side. This document is applicable for all CAD data exchange done in the frame the MetOp-SG MWI project between the Instrument Prime and any partner, subcontractor and/or supplier companies. This document, is built as a Jacket document on top the standard Astrium Product [AD104] which is made fully applicable through this Jacket. This format allows to clearly identifying all add-ons and mofication with respect to the standard company rules.. The requirements contained in the Jacket (this document) allow refining, mofying or complementing the standard AD104. Therefore the METOP-SG MWI Jacket always supersedes AD104. The supplier shall establish full requirement control on both the present jacket document and [AD104]. This Jacket Document shall be the applicable document for generic rules and specifically for NX 7.5. For all rules necessary to prepare and send native CATIA v.5 files, refer to [AD104]. The baselines for the 3D and 2D formats data exchange is UNIGRAPHICS NX 7.5 (file extension.prt) or CATIA v.5 (file extension.catpart for parts, file extension.catproduct for assemblies, file extension.catdrawing for 2D drawings). shall be subject to the following priority table: Priority Subco / Partner CAD format Senng 3D CAD Format File Senng 2D CAD Format File 1 UG NX 7.5 UG NX Step File UG NX DXF File + PDF 2 CATIA V5 CATIA V5 + Step File CATIA V5 + DXF File + PDF 3 Other formats Step File DXF File + PDF Table 1-1: CAD Exchange Data Format Priority Other formats are second choice and only STEP AP214 or AP203 (file extension.stp or.step) will be accepted as an alternative. But using the STEP format will lead nevertheless to the loss information and increase the amount reworking. Moreover, in that case, a summary Excel table (file extension.xls) shall be associated to the STEP file in order to resume the physical properties all parts (see chapter 7.2 ). 1.2 APPLICABILITY This document is applicable to all the CAD exchanges made between the Instrument Prime and any other supplier/partner. The waiver or particularity will be the subject specific Data Exchange Agreement to be written and agreed by the Instrument Prime and the supplier/partner company.

8 8 2. REFERENCES In case conflicts, this specification supersedes - within the scope the conflict only - [AD104] contents; the conflict shall anyhow be reported to the Instrument Prime for proper resolution. AD Doc. No. Iss./Rev. Title Remarks Applicability AD104 ADS.E rev. 1 Satellite Requirement Specification Table 2-1: Applicable Documents A 2.1 RELATED DOCUMENTS Refer to AD BACKGROUND DOCUMENTS Refer to AD DEFINITIONS AND ABBREVIATIONS DEFINITIONS Refer to AD ABBREVIATIONS In adtion to the abbreviations defined in AD104, the following applies: ACRONYM AD AP CoG DEA DXF FTP JT MoI PDF RD MEANING Applicable Document Application Protocol Center Gravity Data Exchange Agreement Drawing Interchange Format Standard format for 2D-CAD data exchange File Transfer Protocol Standard communication format for network transfers Jupiter Tesselation Standard format for 3D CAD data visualization Moments Inertia Portable Document Format Reference Document Table 2-2: Adtional Acronyms TERMS Refer to AD CAD DATAV EXCHANGE WORKFLOW SCHEMA AD104 section 3 applies 3.1 DATA EXCHANGE AGREEMENT (DEA)

9 9 In adtion to the provisions AD104, the data exchange agreement (DEA) shall contain/define: what kind data shall be exchanged (native NX 7.5 / native V5 / STEP e.g.) the type transfer ( / CD / FTP / DVD) 3.2 MODEL CHECK BEFORE SENDING AD104, section 3.2 is applicable 3.3 NOTICE OF TRANSFER AD104, section 3.3 is applicable 3.4 NOTICE OF RECEIPT AD104, section 3.4 is applicable 3.5 MODEL CHECK OF RECEIVED DATA AD104, section 3.5 is applicable 3.6 NOTICE OF ACCEPTANCE AD104, section 3.6 is applicable 4. ASTRIUM CAD SYSTEM CONFIGURATION CGS adopts the same naming convention and General Rules defined in Astrium [AD104]. In this section, each reference to CATIA V5 shall be applied similarly to NX APPLICABLE CATIA VERSION AD104, section 4.1 is applicable 4.2 DIGITAL MOCK UP MANAGEMENT SYSTEM AD104, section 4.2 is applicable 4.3 PLATFORM AD104, section 4.3 is applicable 4.4 ASTRIUM NAMING CONVENTION AD104, section 4.4 is applicable 4.5 CAD MODEL MAIN REFERENCE FRAME AD104, section 4.5 is applicable 4.6 CAD MODEL LEVEL OF DETAIL AD104, section 4.6 is applicable

10 GENERAL PREPARATION OF THE DATA AD104, section 4.7 is applicable 4.8 MISCELANEOUS AD104, section 4.8 is applicable 5. SENDING NATIVE CATIA V5 FILES 5.1 GENERAL COMMENTS AD104, section 5.1 is applicable 5.2 CATIA V5 CONFIGURATION FILES AD104, section 5.2 is applicable 5.3 STRUCTURE, NAMING AND NUMBERING OF A V5 FILE AD104, section 5.3 is applicable 5.4 GENERAL SAVE CONDITIONS FOR V5 FILES AD104, section 5.4 is applicable 5.5 SAVE CONDITIONS FOR V5 CATPART FILES AD104, section 5.5 is applicable 5.6 EXCHANGE OF CATPARTS AD104, section 5.6 is applicable 5.7 EXCHANGE OF CATPRODUCTS AD104, section 5.7 is applicable 5.8 EXCHANGE OF CATDRAWINGS AD104, section 5.8 is applicable 5.9 SPECIAL ELEMENTS AD104, section 5.9 is applicable D-CATALOGUES AD104, section 5.10 is applicable D-CATALOGUES AD104, section 5.11 is applicable

11 FINAL CONTROL - MODEL CHECKS AD104, section 5.12 is applicable 6. SUPPLIER/PARTNER CAD ENVIRONMENT: CATIA V5 6.1 FORMAT FOR SINGLE MODEL EXCHANGE AD104, section 6.1 is applicable 6.2 FORMAT FOR CAD ASSEMBLY EXCHANGE AD104, section 6.2 is applicable 6.3 FORMAT FOR CAD DRAWING EXCHANGE AD104, section 6.3 is applicable 6.4 CATIA MODEL PRECISION AD104, section 6.4 is applicable 7. SUPPLIER/PARTNER CAD ENVIRONMENT: OTHER THAN CATIA V5 7.1 FORMAT FOR SINGLE MODEL EXCHANGE Preferred Step Format For data exchange AP214 shall be used because this AP covers more features than AP 203 (e. g. color and layer information). But both AP s can be used for the exchange assemblies. Step File Size Because the size STEP files can be rather large, the maximum file size shall be limited. Generally STEP files should not exceed 70 MB for single parts and 300 MB for assemblies to get a proper performance afterwards. In any case mensions the files to be exchanged could be agreed by both receiver and sender. Consequently a tip to reduce the amount data may consist in ving the assembly in sub-assemblies by making sure the assembly structure don t get lost. Alternative format If the drawing is supplied only for visualization purposes, the JT format (file extension.jt) is accepted as an alternative to the STEP AP214 one. 7.2 FORMAT FOR CAD ASSEMBLY EXCHANGE Preferred Step Format For data exchange AP214 shall be preferred to AP203 because this AP covers more features than AP 203 (e. g. colour and layer information). But both AP s can be used for the exchange assemblies. Export Step File Before exporting any 3D geometry into STEP, the models shall be cleaned accorng to the list in Chapter 4.7. Adtionally all options affecting the STEP export must be checked for correctness in the translator module the exporting stware. When exporting assemblies, the structure the part tree shall be maintained inside the STEP format. Physical properties Physical properties (such as mass, CoG, etc.) are not supported in the STEP format files.

12 12 So, in order to export those properties in case neutral 3D formats, it is necessary to export also an Excel (file extension.xls) summary table resuming the following physical properties all parts: material density mass CoG, with respect to the main coornate system moments inertia, with respect to the principal axes Such a table shall be able to characterize all those properties for each component which is included in the exported main assembly by respecting the correct part tree and clearly identifying each single sub-assembly and component, as shown in the following table. Sub-assembly Component Material Density Mass CoG Moment Inertia Sub-assembly A Component A-1 Material A-1 Density A-1 Mass A-1 CoG A-1 Moment Inertia A-1 Component A-2 Material A-2 Density A-2 Mass A-2 CoG A-2 Moment Inertia A-2 Component A-N Material A-3 Density A-N Mass A-N CoG A-N Moment Inertia A-N Table 7-1: Physical properties summary table (case neutral 3D format) Final Control before Senng Before senng the STEP file the logfile the conversion (if available) must be controlled first. It normally contains a list elements translated or not. Depenng on the importance the data another recommended check is to reimport the STEP file and examine the result. When possible a stware fferent from the exporting one should be used. A simple test, if the geometry has been reimported correctly, is for example to calculate the volume and/or center gravity and to compare it with the original data. 7.3 FORMAT FOR CAD DRAWINGS EXCHANGE AD104, section 7.3 is applicable

13 13 8. DATA EXCHANGE MEDIA AD104, section 8 is applicable 8.1 FOR UNIX ENVIRONMENT File transfer can be via any FTP site agreed by the Instrument Prime. Any decated portal or exchange stware to exchange data shall be agreed by the Instrument Prime. 8.2 FOR WINDOWS ENVIRONMENT File transfer can be via any FTP site agreed by the Instrument Prime. Any decated portal or exchange stware to exchange data shall be agreed by the Instrument Prime. 8.3 FOR «WINDOWS TO UNIX» OR «UNIX TO WINDOWS» TRANSFER AD104, section 8.3 is applicable 8.4 TRANSFER OF FILES AD104, section 8.4 is applicable

14 14 9. PREPARING AND SENDING NATIVE UNIGRAPHICS NX 7.5 FILES 9.1 GENERAL COMMENTS It is strictly recommended that the partner, subcontractor and/or supplier company has the same release UNIGRAPHIC NX 7.5. In case data delivery the version shall be less/equal to this. NX 7.5 configuration files affect graphical properties and local settings (paths, libraries). Mechanical properties like mass, tolerances and materials shall be stored within the parts. 9.2 LAYERS AND ATTRIBUTES OF A UNIGRAPHICS FILE When creating a new NX 7.5 file or mofying an existing one, the following conventions for layers shall be considered: LAYER DRAWING ELEMENTS 1 to 19 Solids 20 to 39 Points and Curves 40 to 49 Datum Planes, Datum Axis, Planes 50 to 55 Coornate Systems 59 Standard Parts (commercial parts) 70 to 99 Lines and all entities for drafting 2 to Free Table 9-1: Layers conventions for NX 7.5 files 9.3 IMPLEMENTATION OF MASS PROPERTIES INFORMATION It is extremely important that the NX 7.5 file contains the information about mass properties (CoG and MoI). So the correct density shall be assigned and saved to each part. 9.4 GENERAL SAVE CONDITIONS FOR A UNIGRAPHICS FILE The following settings shall be accomplished before storing a NX 7.5 file: layer: all solid models activated on Layer 1 no main geometry hidden (without comment/note) see also chapter CREATION AND EXCHANGE OF PARTS When creating a new part or mofying an existing one, the following steps shall be considered: check the file name in accordance with the project s rules (see chapter 4.4 ) assign the correct material and density properties use the correct layers in accordance with Table 9-1 Furthermore, for the exchange parts the general recommendations chapter 5.6 shall be respected.

15 CREATION AND EXCHANGE OF ASSEMBLIES When creating a new assembly or mofying an existing one, the following steps shall be considered: check the file name in accordance with the project s rules use the correct layers in accordance with Table 9-1 add any new part with layer option: original include all subassemblies in the main reference coornate system the load options shall be consistent with the following assumptions: - Part Versions: From Search Directory - Scope: Structure Only and Use Partial Loang - Reference Sets: SOLID in 1 st options and As Saved in 2 nd, Apply to All Assembly Levels - Bookmark Restore Option: Parts to Load as Previously Visible Components and Restore Reference Sets (it allows a faster and lighter loang files without errors) Figure 9-1: Load Options definition

16 9.7 CREATION AND EXCHANGE OF DRAWINGS Because a Drawing normally refers to a 3D-model, any 2D-drawing shall be linked to the respective Part/Assembly. This means that it is strictly forbidden that both the Part/Assembly and the Drawing are emboed in a unique file. The Drawing shall contain only the link to the 3D-model and its name shall be namefile-dwg.prt and these two files shall evolve together. For this reason, it is not enough to transfer the Drawing when it needs to be mofied; it is also needed to transfer the associated Part/Assembly. When the Part/Assembly and the Drawing are not stored into the same rectory, there will be a problem after the exchange, because the old path is still stored in the Drawing and it is normally fferent to the path used by the recipient. Any delivery a Drawing shall include both the 2D-drawing itself and the source Part/Assembly. Adtional save settings shall be considered: sheet 1 activated drawing frame in the background all mensions must be associative (this means no red mensions visible in the Analysis Display Mode )