Edu Cat en Sr1 Ai v5r16 Toprint

Structure Design Administration Expert
CATIA Training
Foils
Structure Design Administration

Copyright DASSAULT SYSTEMES
Version 5 Release 16 November 2005 EDU-CAT-EN-SR1-AI-V5R16
Instructor Notes:
Course Presentation
In this course you will learn methods to administrate a SR1 project.
Objectives of the course
Experienced CATIA V5 users
Targeted audience
4 days
Prerequisites
CATIA V5 Fundamentals, SR1, PKT, KWA (Optional)
Instructor Notes:
Planning
Day 1
MORNING EDU-CAT-E-SR1FF-V5R16 Chapter 1: Project Resource Management EDU-CAT-E-SR1FX-V5R16 Step 1: Creating a new Project EDU-CAT-E-SR1FF-V5R16 Chapter 2: Feature Dictionary Edition EDU-CAT-E-SR1FX-V5R16 Step 2:Adding New Attributes EDU-CAT-E-SR1FX-V5R16 Step 3: Modifying a Standard Section Catalog
Day 2
EDU-CAT-E-SR1FF-V5R16 Chapter 3: Standard Section Catalogs
Day 3
EDU-CAT-E-SR1FF-V5R16 Chapter 4: Standard End-cut EDU-CAT-E-SR1FX-V5R16 Step 4: Creating a Standard End-Cut EDU-CAT-E-SR1FF-V5R16 Chapter 4: Contextual End-cut EDU-CAT-E-SR1FX-V5R16 Step 5: Creating a Contextual End-Cut
Day 4
EDU-CAT-E-SR1FF-V5R16 Chapter 4: Standard Slot EDU-CAT-E-SR1FX-V5R16 Step 5: Creating a Standard Slot EDU-CAT-E-SR1FF-V5R16 Chapter 4: Small Assemblies EDU-CAT-E-SR1FX-V5R16 Step 5: Creating a T-Chock
Exercises
AFTERNOON
Exercises
Instructor Notes:
Table of Contents
1. Project Resource Management
Introducing the PRM Understanding the PRM Structure Discipline Resources Accessing the PRM Checking the PRM
p5
p6 p7 p11 p12 p15
2. Feature Dictionary
About the Feature Dictionary Starting the Feature Dictionary Editor Managing Attributes Discrete Values Managing ID Number
p16
p17 p18 p19 p21 p22
3. Standard Section Catalogs

Managing Parametric Sections Generating Resolved Parts Creating/Modifying Standard Section Catalogs p32
p24
p25 p30
4. Detailing Features
Design Rules and Recommendations End-Cuts Slots Small Assemblies Storing Detailing Features in a catalog
p34
p35 p38 p44 p47 p50
Instructor Notes:
Project Resource Management

This task shows you how to manage project resources like catalogs and dictionaries. These changes can only be made at system administrator level.
Introducing the PRM (the CNEXT Project) Understanding the PRM Structure Discipline Resources Checking the PRM in SR1
Instructor Notes:
Introducing the PRM?

Unlike other Mechanical Products (e.g. Part Design, Sheetmetal, ) SR1 resources are manage through the project resource management (PRM) file and call for a Projectbased notion The project resource management (PRM) file identifies resources (such as Standard Section catalogs, Thickness table, etc.) to the application. the PRM file identifies each resource and its location (directory path). The PRM file organizes the resources by discipline and application, associating resources to specific applications. A sample file is provided with this application. The default location is ...\intel_a\startup\EquipmentAndSystems\ProjectData and the file is named Project.xml. You need to make a project resource management file for each project at your site. To view the project resource management file (Project.xml) in an internet browser, you need a specific file named Project.dtd. The default location is ...\intel_a\startup\reffiles\disciplines To edit the Project.xml file you need a text editor.
Instructor Notes:
Understanding the PRM (1/4)

The resource management file is organized into several sections to make it easier to manage and utilize resources.
Instructor Notes:

The Project box refers to the project for which the PRM file has been created, and will frequently be identified by the file name. In this case it is Project.xml.
Project Resources: Any resources you place under the heading Project Resources can be used by all applications that are included in the file.
Structure Discipline Resources: All resources placed under this discipline can be used by all the applications which are listed under it. Warning !
Instructor Notes:

Structure Design Application: Any resource referred to at this level can only be used by that application.
Must be commented
Instructor Notes:

PRM Key-words.
Do not change the Resource Name, even if you replace a resource with a different one You can change the Description if you want to this is a brief explanation of the resource Some resources have the entry "Visible = yes". If you set the value to No then this resource cannot be used and will not be visible in the Tools - Project Management dialog box.
The Type field refers to file type. If the Type field says Catia, it refers to a file type unique to Catia, such as .catalog
File EnoviaV5 Smarteam
The Location field usually gives the location of the resource. If this is a directory path then you can change the location, with an associated change in the PRM file
Some resources have the entry Access="RW" or "R". These refers to file permissions: read-write or read
If your resources do not reside in Enovia or Smarteam, enter File in the Driver field. Define the Location field using the provided aliases.
it is preferable to enter absolute paths - including the drive letter

If your resources are Smarteam-based, enter Smarteam in the Driver field. For Smarteam-based resources, all you need to enter in the Location field is the file name of the resource without the file extension. For instance, the catalog AISC_Resolved.catalog would be entered as Aisc_Resolved.
Instructor Notes:
Structure Discipline Resources (1/4)

--> <Resource Name="StructureDesignIDSchema" Description="Structure Design ID Schema Directory" Visible="yes"> <ID Type="Path" Driver="File" Location="${Startup_Directory}\StructureDesign\DataDictionary" Path="No Description" Access="R" /> </Resource> -->        - <Resource Name="StructureDetailDesignCatalog" Description="Structure Detail Design Catalog" Visible="yes"> <ID Type="Catia" Driver="File" Location="${Startup_Directory}\Structure\DetailingFeatures\FeatureCatalogs\Parametric\DetailingFeatures.catalog" Path="No Description" Access="R" /> </Resource>  <Resource Name="StructureDesignIDSchema" Description="Structure Design ID Schema Directory" Visible="yes"> <ID Type="Path" Driver="File" Location="${Startup_Directory}\StructureDesign\DataDictionary" Path="No Description" Access="R" /> </Resource>
<?xml version="1.0" ?> <!DOCTYPE Doct (View Source for full doctype...)> - <Doct> <schema_ATT value="ShapeType" /> <schema_SEP value="_" /> <schema_CST value="Shape_" /> <schema_SeqNbr seq_IEND="999" seq_NMIN="3" seq_ISTART="1" /> </Doct>
The numeral 1 after the file name is used for a reference part.
ID Sequence Number Definition Directory : Give the system the path where to store the Sequence Number files
<!---> <Resource Name="IDSequenceNumber" Description="ID Sequence Number Definition Directory" Visible="yes">
<ID Type="Path" Driver="File" Location="E:\SERVER\DS.DB\H2O\DesignData\ApplicationData\IDSequenceNumbers" Access="RW Path="No Description" /> </Resource>
Instructor Notes:
G Gf v RG yx xG xp GvGGuGRGGGGGfge bc v yq x c p wf c ft si r fqpfih d
Managing ID Number (2/2)

This task shows you how to modify or define the object naming rules.
1 In the specifications tree, double-click the class to which you want to modify the ID Number. 2 Click on the Define ID schema button
The Define ID Schema dialog box opens:

You have two options In the ID usage field, Instance and Reference, and you usually have to define naming rules for each object using both options. The naming rules you define under the Instance option are used by the application when you are placing a part in a document. Select Yes or No for Sequence number. Yes or No cannot be selected if you have Reference as the ID usage. Minimum length refers to the number of digits in the numbering scheme. For instance, 3 means the number will show up as 001.
Click on Define/Modify ID Schema button The Define/Modify ID Schema dialog box will display.
Instructor Notes:
Standard Section Catalog

You will see how to generate grids by assigning the basic parameters needed to create the grid.
Managing Parametric Sections Generating Resolved Parts Creating/Modifying Standard Section Catalogs
Instructor Notes:
Managing Parametric Sections (1/5)

Section Part creation (1/2)
Structure parts must have a parameter called "ProfileType". Each parametric part must refer to a design table. The design table must have a column called "PartNumber", which should have a value. This value is used to name the generated resolved part.
1 Create a CATPart
Create a Sketch By convention in XY Plane. 3 Rename the driving offsets of the sketch
Instructor Notes:

Section Part creation (2/2)
4 Create the Parameter call: ProfileType Value it: Beam. 5 Create a dimension table Give it the name of the final CATPart. Its a Tabulated text file that reflect the parameters you create for your Sketch. It contains a column PartNumber.
Associate this dimension table to the CATPart
Save the CATPart
Use the following naming convention: catalogname_familyname.CATPart (e.g. EN_IPSpecial)
Instructor Notes:

Defining Anchor Points for Sections
1 Edit the Sketched section
create an appropriate construction point
Rename the point Use the prefix catStr, for example catStrOffsetTopCenter.
Save the CATPart
Instructor Notes:

Naming Section Characteristics
1 Click the Name Section Characteristics icon
Specify the location of the folder containing user sketches
Select the sketch of interest in the Name box
Name sketch edges using the contextual menu Right-click a line and select the name from the list of pre-defined names in the contextual menu.
Repeat to identify all sketch edges
Click OK when done
Instructor Notes:

Default names for typical shapes.
Typical I Shape Typical L Shape
Typical T Shape
Typical U Shape
Instructor Notes:
Generating Resolved Parts (1/2)

SR1 is only using Resolved Standard Section Catalog
A .bat file is provided to ease the generation of all the resolved section, family by family
1 Create a directory and place in it the parametric CATPart documents and associated design table documents. You MUST specify the first set of coordinates at step 6.
Create a directory in which output resolved CATPart documents will be placed
Open a command prompt window and change to the directory ...intel_a\code\command.
Instructor Notes:
Generating Resolved Parts (2/2)

4 Type the following and press Enter: CATCloGenerateResolvedParts.bat <directorypath1> <directorypath2> -appl Structure
<directorypath1> is the full path name of the input directory you created in Step 1, including the drive letter, e.g. C:\ToBeResolved. <directorypath2> is the full path name of the output directory you created in Step 2, e.g. C:\ResolvedParts. If no output directory is specified, resolved parts are placed in the input directory <directorypath1>. -appl Structure is an argument that ensures the proper migration of applicative parametric parts.
Instructor Notes:
Creating/Modifying Standard Section Catalogs (1/2)

This task shows how to modify a Standard Section Catalog.
The creation process is similar to what is explain hereunder
1 Open an existing Standard Section Catalog
Select Create/Modify Catalog icon The Create/Modify Catalog window is displayed
Instructor Notes:
Creating/Modifying Standard Section Catalogs (2/2)

3 Value the needed fields
Application : select Structure Design Parts directory field: the directory where the resolved parts are stored Parts list field: give the path to list of resolved parts (a text file)
Click OK
Instructor Notes:
Detailing Features
This task shows you how to build a catalog of Detailing Features. This is usually done by an administrator.
Design Rules and Recommendations End-Cuts Slots Small Assemblies Storing Detailing Features in a catalog
Instructor Notes:
Design Rules and Recommendations (1/3)

General
Always explicitly define points and never use implicit points, for example those at the ends of lines. Wherever possible, make selections in the specification tree.
Oriented Planes and Lines

Never invert the orientation of a plane without first checking whether or not the plane has children. In general, plane orientation must be known. This applies in particular to planes tangent to surfaces, planes offset or parallel to oriented planes, planes at an angle or normal to an oriented plane if the axis of rotation is a line of known direction. Instantiate user feature SurfaceOrientation.CATPart to force plane orientation. Always work with oriented lines, especially when used as axes of rotation. When creating lines via the Intersection command, instantiate user feature CurveOrientation.CATPart to force line orientation. User features are to be found in folder ..\intel_a\startup\EquipmentAndSystems\StructureDetailDesign\SampleData.
Input Geometry
Do not use input geometry in knowledgeware rules or formula [F(x)]. If you need to do so, duplicate the surfaces using Offset (0 offset) or Extract commands and reference duplicated geometry in the rule or formula.
Instructor Notes:

Sketching
Always sketch using the Sketch with Absolute Axis definition command Never set distance constraints in the Sketcher. To dimension distances, create offset planes in the Wireframe and Surface Design workbench, then set coincidence constraints based on these planes in the Sketcher. Avoid creating circles constrained in tangency. Defining as much as possible using the Wireframe and Surface Design workbench is recommended.
Creating Slots, End-cuts and Small Assemblies

Always reference input geometry and never part document planes. Always select input surfaces and not surfaces of starter model plates and shapes. Always ensure that the geometric entities are properly ordered, for example an intersection of two lines must be placed after the two lines. Use the Reorder command if necessary. For slots and end-cuts, always reference at least one entity of the plate or shape that will contain the feature. For end-cuts, ensure that Split cutting planes are oriented with respect to geometric elements. For end-cuts, ensure that the first Part Design feature (pocket, split, etc.) describing the end-cut is the active feature. Select this component first when creating the template (UDF).
Instructor Notes:

Convention Naming for End-Cuts
Shape to which endcut will be applied:
Shape_(name of published shape surface or edge) For example, Shape_Edge_MoldedFlange1_Start
Other shape surfaces:

Shapen_(name of the published shape surface or edge) where n is a number identifying the number of parts to be selected by the user when instantiating the slot feature
Convention Naming for Slots

Plate/shape in which slot will be located:
Plate_(name of published plate surface or edge) Shape1_(name of published shape surface or edge) For example, Plate_Face_Standard
Other plate/shape surfaces:

Platen_(name of the published plate surface or edge) Shapen_(name of the published shape surface or edge) where n is a number identifying the number of parts to be selected by the user when instantiating the slot feature. For example, Shape1_Face_MoldedFlange1
Convention Naming for Small Assemblies

Plate/shape to be selected by the user:
Platen_(name of the published plate surface or edge) Shapen_(name of the published shape surface or edge) where n is a number identifying the number of parts to be selected by the user when instantiating the assembly template. For example, Plate1_Face_Standard, Shape1_Face_MoldedFlange1.
Instructor Notes:
Catalog Standard End-Cut (1/3)

This task shows you how to build a catalog standard end-cut.
1 Create the contextual Environment. Typically, a Product containing a Shape called Starter_Model Use Manage Structure Publication icon found in Tools Customize - Commands All Commands category
Add Publications
Extract the needed edge\faces of the member, selecting from the publications, into a geometrical set called Inputs Rename them using the naming convention 4 Create the construction geometry into an ordered geometrical set Use an oriented Sketch for the pocket to be defined later on.
Instructor Notes:

5 Create Parameters and associate them to the construction elements
Create a Pocket
Create a User Define Feature
The Userfeature Definition dialog box opens:

Give the end-cut template a meaningful name. This is the name the user will see when he instantiates the end-cut in his design. Select the pocket and the end-cut Internal_Feature in the specification tree.
Instructor Notes:

8 Publish parameters
The Outputs tab must contain only the Pocket!
Store the end-cut template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.
Instructor Notes:
Catalog Contextual End-Cut (1/3)

This task shows you how to build a catalog contextual end-cut.
1 Create the contextual Environment. Typically, a Product containing 3 Shapes called:
r-Shape (Active Object: the shape to be cut) r-Shape1 r-Shape3 (For internal inputs creation) This shape will be delete later on.
Use Manage Structure Publication icon found in Tools Customize - Commands All Commands category
Add Publications Only on r-Shape1 and r-Shape3 3 Extract the needed edge\faces of the member, selecting from the publications of r-Shape1 and r-Shape3. r-Shape must be active. Rename them using the naming convention:
Shape_ (for the extractions of r-Shape3) Shape1_ (for the extractions of r-Shape1) You need to isolate Shape1_ elements and delete the extracts
Create the construction geometry into an ordered geometrical set
Instructor Notes:

Create a Slot

Give the end-cut template a meaningful name. This is the name the user will see when he instantiates the end-cut in his design. Select the pocket and the End-cut Internal_Feature in the specification tree.
Instructor Notes:

The Outputs tab must contain only the Slot!
Store the end-cut template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.
Instructor Notes:
Catalog Slot (1/3)

This task shows you how to build a catalog slot.
1 Create the contextual Environment. Typically, a Part containing 2 bodies: one for the plate and one for the Shape. 2 Extract the needed edge\faces, selecting from the bodies, into a geometrical set called Inputs Rename them using the naming convention
Create the construction geometry
Instructor Notes:
Catalog Slot (2/3)

Create a Pocket

Give the Slot template a meaningful name. This is the name the user will see when he instantiates the Slot in his design. Select the pocket and the Slot_Internal_Feature in the specification tree.
Instructor Notes:
Catalog Slot (3/3)

The Outputs tab must contain only the Pocket!
Store the slot template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.
Instructor Notes:
Catalog Small Assembly (1/3)

This task shows you how to build a catalog small assembly.
1 Create the contextual Environment. Typically, a Product containing:
a Shape (Active Object) a sub-product (it will contain the small assembly skeleton and definition)
Add Publications
Use Manage Structure Publication icon found in Tools Customize - Commands All Commands category
Extract the needed edge\faces of the member, selecting from the publications of Shape1 and r-Shape3. The small assembly skeleton part must be active. Rename them using the naming convention:
Shape1_ xxxx You need to isolate Shape1_ elements and delete the extracts
Create the construction geometry into an ordered geometrical set
Instructor Notes:
Catalog Small Assembly (2/3)

5 Create Parameters and associate them to the construction elements 6 Create the physical elements 7 Create a User Define Feature
The Document Template Definition dialog box opens:

Select the Inputs (Only those which are used will be selectable)
Instructor Notes:

Edit the list of available parameters to be published
Rename and store the small assembly template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.
Instructor Notes:
Storing Detailing Features in a catalog (1/2)

A sample catalog, DetailingFeatures.catalog, of slots, end-cuts and small assemblies is provided with the product. By default, this catalog, which is managed as a project resource at structure discipline level, is located in folder .../intel_a/startup/EquipmentAndSystems/Structure/DetailingFeatures/FeatureCata logs/Parametric.
1 Open the sample catalog
If necessary, expand the chapters to view their contents.
Instructor Notes:
Three chapters have been defined: Endcuts, Slots and SmallAssemblies. Each chapter corresponds to a folder containing the associated parts and features. Sub-chapters have also been defined. In the case of endcuts and slots, these correspond to the various types of shape on which the endcut or slot will be applied. It is important to respect the endcut and slot sub-chapter naming. This will ensure that the Catalog Selection dialog box proposes appropriate endcuts or slots to the user for the type of shape selected. In the case of assembly templates, it is important to respect the naming of chapters SmallAssemblies and UserTemplates.
Storing Detailing Features in a catalog (2/2)
Click the Add Component command The Description Definition dialog box appears. 3 Click Select external feature
Select the slot, endcut or small assembly template in the specification tree of the document containing your template.
Click OK
The slot, end-cut or small assembly is added to the catalog.

Save the catalog when done.
Instructor Notes:

Edu Cat en Sr1 Ai v5r16 Toprint

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Edu Cat en Sr1 Ai v5r16 Toprint

Enviado por

Direitos autorais:

Formatos disponíveis

Structure Design Administration Expert

Structure Design Administration

Version 5 Release 16 November 2005 EDU-CAT-EN-SR1-AI-V5R16

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Objectives of the course

Experienced CATIA V5 users

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

3. Standard Section Catalogs

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Project Resource Management

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Introducing the PRM?

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Understanding the PRM (1/4)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Understanding the PRM (2/4)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Understanding the PRM (3/4)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Understanding the PRM (4/4)

File EnoviaV5 Smarteam

it is preferable to enter absolute paths - including the drive letter

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Structure Discipline Resources (1/4)

The following Resources are used by the Structure Design application

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

E E E E E E E E E E E E E aHGT22XVGGPa2PGXV T RPGG2GE E E E E E E E E E E E E E E I PF HI ` Y W SU S Q IHF

 $3 !( ! '  1 !!5 B 12!!# ! 0 5% !4 ' & 04 3(C 1$ "A @ 0 '

Structure Design Administration Expert

Accessing the PRM (1/3)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Accessing the PRM (2/3)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Accessing the PRM (3/3)

Copyright DASSAULT SYSTEMES

Copyright DASSAULT SYSTEMES

Structure Design Administration Expert

Checking the PRM

The errors are explained below.

Copyright DASSAULT SYSTEMES

E E E E E E E E E E E E E aHGT22XVGGPa2PGXV T RPGG2GE E E E E E E E E E E E E E E I PF HI ` Y W SU S Q IHF

$3 !( ! ' 1 !!5 B 12!!# ! 0 5% !4 ' & 04 3(C 1$ "A @ 0 '

G Gf v RG yx xG xp GvGGuGRGGGGGfge bc v yq x c p wf c ft si r fqpfih d