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

(1)

Tipo Doc.:

Doc.Type: TECHNICAL NOTE

N° DRD: DRD N°: NA N° Doc.: Doc. N°:

MOS-TN-CGS-MWI-0028

Ediz.: Issue:

01

Data: Date:

07/11/2014

Pagina Page

1

Di Of

16

Titolo:

Title : CAD Data Exchange

Nome &Funzione Name & Function

Firma Signature Data Date LISTA DI DISTRIBUZIONE DISTRIBUTION LIST N A I Preparato da:

Prepared by: MWI Team

Interna / Internal

MWI Team 1 X

Approvato da:

Approved by: T. Lupi (CGS-SE)

L. Cremonesi (CGS-PA) C. Cinquepalmi (CGS-CC) 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 di copie A=Applicazione I=Informazione

N=Number of copy A=Application I=Information

Gestionedocumenti:

Data Management:

Firma / Signature Data / Date File:

MOS-TN-CGS-MWI-0028_Is1_CAD_Data_Exchange.docx 07/11/2014 07/11/2014 07/11/2014 10/11/2014 2014.11.10 09:10:02 +01'00'

(2)

REGISTRAZIONE DELLE MODIFICHE / CHANGE RECORD EDIZIONE ISSUE DATA DATE AUTORIZZAZIONE CHANGE AUTHORITY

OGGETTO DELLA MODIFICA E SEZIONI AFFETTE REASON FOR CHANGE AND AFFECTED SECTIONS

(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 - 16 01

(4)

TABLE OF CONTENTS

1. DOCUMENT SCOPE AND APPLICABILITY ... 7

1.1 SCOPE ... 7

1.2 APPLICABILITY ... 7

2. REFERENCES ... 8

2.1 RELATED DOCUMENTS ... 8

2.2 BACKGROUND DOCUMENTS ... 8

2.3 DEFINITIONS AND ABBREVIATIONS ... 8

2.3.1 DEFINITIONS ... 8

2.3.2 ABBREVIATIONS ... 8

2.3.3 TERMS ... 8

3. CAD DATAV EXCHANGE WORKFLOW SCHEMA ... 8

3.1 DATA EXCHANGE AGREEMENT (DEA) ... 8

3.2 MODEL CHECK BEFORE SENDING ... 9

3.3 NOTICE OF TRANSFER... 9

3.4 NOTICE OF RECEIPT ... 9

3.5 MODEL CHECK OF RECEIVED DATA ... 9

3.6 NOTICE OF ACCEPTANCE ... 9

4. ASTRIUM CAD SYSTEM CONFIGURATION ... 9

4.1 APPLICABLE CATIA VERSION ... 9

4.2 DIGITAL MOCK UP MANAGEMENT SYSTEM ... 9

4.3 PLATFORM ... 9

4.4 ASTRIUM NAMING CONVENTION ... 9

4.5 CAD MODEL MAIN REFERENCE FRAME ... 9

4.6 CAD MODEL LEVEL OF DETAIL ... 9

4.7 GENERAL PREPARATION OF THE DATA... 10

4.8 MISCELANEOUS ... 10

5. SENDING NATIVE CATIA V5 FILES ... 10

5.1 GENERAL COMMENTS ... 10

5.2 CATIA V5 CONFIGURATION FILES ... 10

5.3 STRUCTURE, NAMING AND NUMBERING OF A V5 FILE ... 10

5.4 GENERAL SAVE CONDITIONS FOR V5 FILES ... 10

5.5 SAVE CONDITIONS FOR V5 CATPART FILES ... 10

5.6 EXCHANGE OF CATPARTS ... 10 5.7 EXCHANGE OF CATPRODUCTS ... 10 5.8 EXCHANGE OF CATDRAWINGS ... 10 5.9 SPECIAL ELEMENTS ... 10 5.10 2D-CATALOGUES... 10 5.11 3D-CATALOGUES... 10

5.12 FINAL CONTROL - MODEL CHECKS ... 11

6. SUPPLIER/PARTNER CAD ENVIRONMENT: CATIA V5 ... 11

6.1 FORMAT FOR SINGLE MODEL EXCHANGE ... 11

6.2 FORMAT FOR CAD ASSEMBLY EXCHANGE ... 11

6.3 FORMAT FOR CAD DRAWING EXCHANGE ... 11

6.4 CATIA MODEL PRECISION ... 11

7. SUPPLIER/PARTNER CAD ENVIRONMENT: OTHER THAN CATIA V5 ... 11

7.1 FORMAT FOR SINGLE MODEL EXCHANGE ... 11

7.2 FORMAT FOR CAD ASSEMBLY EXCHANGE ... 11

(5)

8. DATA EXCHANGE MEDIA ... 13

8.1 FOR UNIX ENVIRONMENT ... 13

8.2 FOR WINDOWS ENVIRONMENT ... 13

8.3 FOR « WINDOWS TO UNIX » OR « UNIX TO WINDOWS » TRANSFER ... 13

8.4 TRANSFER OF FILES ... 13

9. PREPARING AND SENDING NATIVE UNIGRAPHICS NX 7.5 FILES ... 14

9.1 GENERAL COMMENTS ... 14

9.2 LAYERS AND ATTRIBUTES OF A UNIGRAPHICS FILE ... 14

9.3 IMPLEMENTATION OF MASS PROPERTIES INFORMATION ... 14

9.4 GENERAL SAVE CONDITIONS FOR A UNIGRAPHICS FILE ... 14

9.5 CREATION AND EXCHANGE OF PARTS ... 14

9.6 CREATION AND EXCHANGE OF ASSEMBLIES ... 15

(6)

LIST OF FIGURES

Figure 9-1: Load Options definition ... 15

LIST OF TABLES Table 1-1: CAD Exchange Data Format Priority ... 7

Table 2-1: Applicable Documents ... 8

Table 2-2: Additional Acronyms ... 8

Table 7-1: Physical properties summary table (case of neutral 3D format) ... 12

(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 sending 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 of 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 of the standard Astrium Product CAD Data Exchange [AD104] which is made fully applicable through this Jacket. This format allows to clearly identifying all add-ons and modification with respect to the standard company CAD Data Exchange rules..

The requirements contained in the Jacket (this document) allow refining, modifying or complementing the standard CAD Data Exchange AD104. Therefore the METOP-SG MWI Jacket CAD Data Exchange 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 CAD Data Exchange rules and specifically for NX 7.5 CAD Data Exchange.

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).

CAD Data Exchange shall be subject to the following priority table:

Priority Subco / Partner CAD format Sending 3D CAD Format File Sending 2D CAD Format File

1 UG NX 7.5 UG NX 7.5 + Step File UG NX 7.5 + 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 of information and increase the amount of 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 of 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 of specific Data Exchange Agreement to be written and agreed by the Instrument Prime and the supplier/partner company.

(8)

2. REFERENCES

In case of conflicts, this specification supersedes - within the scope of 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.1054 1 rev. 1 Satellite CAD Data Exchange

Requirement Specification A

Table 2-1: Applicable Documents

2.1

2.2 BACKGROUND DOCUMENTS

Refer to AD104

2.3 DEFINITIONS AND ABBREVIATIONS

2.3.1 DEFINITIONS

Refer to AD104

2.3.2 ABBREVIATIONS

In addition to the abbreviations defined in AD104, the following applies:

ACRONYM MEANING

AD Applicable Document

AP Application Protocol

CoG Center of Gravity

DEA Data Exchange Agreement

DXF Drawing Interchange Format – Standard format for 2D-CAD data exchange

FTP File Transfer Protocol – Standard communication format for network transfers

JT Jupiter Tesselation – Standard format for 3D CAD data visualization

MoI Moments of Inertia

PDF Portable Document Format

RD Reference Document

Table 2-2: Additional Acronyms

2.3.3 TERMS

Refer to AD104

3. CAD DATAV EXCHANGE WORKFLOW SCHEMA

AD104 section 3 applies

(9)

In addition to the provisions of AD104, the data exchange agreement (DEA) shall contain/define:

 what kind of data shall be exchanged (native NX 7.5 / native V5 / STEP e.g.)

 the type of transfer (Email / CD / FTP / DVD)

3.2 MODEL CHECK BEFORE SENDING

AD104, section 3.2 is applicable

3.3 NOTICE OF TRANSFER

3.4 NOTICE OF RECEIPT

3.5 MODEL CHECK OF RECEIVED DATA

3.6 NOTICE OF ACCEPTANCE

4. ASTRIUM CAD SYSTEM CONFIGURATION

CGS adopts the same naming convention and General Rules defined in Astrium CAD Data Exchange [AD104]. In this section, each reference to CATIA V5 shall be applied similarly to NX 7.5.

4.1 APPLICABLE CATIA VERSION

4.2 DIGITAL MOCK UP MANAGEMENT SYSTEM

4.3 PLATFORM

4.4 ASTRIUM NAMING CONVENTION

4.5 CAD MODEL MAIN REFERENCE FRAME

4.6 CAD MODEL LEVEL OF DETAIL

(10)

4.8 MISCELANEOUS

5. SENDING NATIVE CATIA V5 FILES

5.1 GENERAL COMMENTS

5.2 CATIA V5 CONFIGURATION FILES

5.3 STRUCTURE, NAMING AND NUMBERING OF A V5 FILE

5.4 GENERAL SAVE CONDITIONS FOR V5 FILES

5.5 SAVE CONDITIONS FOR V5 CATPART FILES

5.6 EXCHANGE OF CATPARTS

5.7 EXCHANGE OF CATPRODUCTS

5.8 EXCHANGE OF CATDRAWINGS

5.9 SPECIAL ELEMENTS

5.10 2D-CATALOGUES

5.11 3D-CATALOGUES

(11)

5.12 FINAL CONTROL - MODEL CHECKS

6. SUPPLIER/PARTNER CAD ENVIRONMENT: CATIA V5

6.1 FORMAT FOR SINGLE MODEL EXCHANGE

6.2 FORMAT FOR CAD ASSEMBLY EXCHANGE

6.3 FORMAT FOR CAD DRAWING EXCHANGE

6.4 CATIA MODEL PRECISION

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 of assemblies.

Step File Size

Because the size of 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 dimensions of the files to be exchanged could be agreed by both receiver and sender.

Consequently a tip to reduce the amount of data may consist in dividing 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 of assemblies.

Export Step File

Before exporting any 3D geometry into STEP, the models shall be cleaned according to the list in Chapter 4.7 . Additionally all options affecting the STEP export must be checked for correctness in the translator module of the exporting software.

When exporting assemblies, the structure of the part tree shall be maintained inside the STEP format. Physical properties

(12)

extension .xls) summary table resuming the following physical properties of all parts:

 material

 density

 mass

 CoG, with respect to the main coordinate system

 moments of 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 of Inertia

Sub-assembly A Component A-1 Material A-1 Density A-1 Mass A-1 CoG A-1 Moment of Inertia A-1

Component A-2 Material A-2 Density A-2 Mass A-2 CoG A-2 Moment of Inertia A-2

… … … …

Component A-N Material A-3 Density A-N Mass A-N CoG A-N Moment of Inertia A-N

Table 7-1: Physical properties summary table (case of neutral 3D format) Final Control before Sending

Before sending the STEP file the logfile of the conversion (if available) must be controlled first. It normally contains a list of elements translated or not.

Depending on the importance of the data another recommended check is to reimport the STEP file and examine the result. When possible a software different 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 of gravity and to compare it with the original data.

7.3 FORMAT FOR CAD DRAWINGS EXCHANGE

(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 dedicated portal or exchange software 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 dedicated portal or exchange software to exchange data shall be agreed by the Instrument Prime.

8.3 FOR « WINDOWS TO UNIX » OR « UNIX TO WINDOWS » TRANSFER

8.4 TRANSFER OF FILES

(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 of UNIGRAPHIC NX 7.5. In case of 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 modifying 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 Coordinate Systems

59 Standard Parts (commercial parts)

70 to 99 Lines and all entities for drafting

201 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 4.7

9.5 CREATION AND EXCHANGE OF PARTS

When creating a new part or modifying 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

(15)

9.6 CREATION AND EXCHANGE OF ASSEMBLIES

When creating a new assembly or modifying 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 coordinate system

 the load options shall be consistent with the following assumptions: - Part Versions: From Search Directory

- Scope: Structure Only and Use Partial Loading

- Reference Sets: SOLID in 1st options and As Saved in 2nd, 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 loading of files without errors)

(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 embodied 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 modified; it is also needed to transfer the associated Part/Assembly. When the Part/Assembly and the Drawing are not stored into the same directory, there will be a problem after the exchange, because the old path is still stored in the Drawing and it is normally different to the path used by the recipient. Any delivery of a Drawing shall include both the 2D-drawing itself and the source Part/Assembly.

Additional save settings shall be considered:

 sheet 1 activated

 drawing frame in the background