Edu Cat en Sr1 Ai v5r16 Toprint

Instructor Notes:

Structure Design Administration Expert

Copyright DASSAULT SYSTEMES �

��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

1

Structure DesignAdministration

CATIA TrainingFoils

Version 5 Release 16November 2005

EDU-CAT-EN-SR1-AI-V5R16

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Course PresentationObjectives of the courseIn this course you will learn methods to administrate a SR1 project.

Targeted audienceExperienced CATIA V5 users

PrerequisitesCATIA V5 Fundamentals,SR1, PKT, KWA (Optional)

4 days

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Planning

EDU-CAT-E-SR1-FX-V5R16Step 3: Modifying a Standard Section Catalog

EDU-CAT-E-SR1-FF-V5R16Chapter 3: Standard Section Catalogs

Day 2

EDU-CAT-E-SR1-FX-V5R16Step 2:Adding New Attributes

EDU-CAT-E-SR1-FF-V5R16Chapter 2: Feature Dictionary Edition

EDU-CAT-E-SR1-FX-V5R16Step 1: Creating a new Project

EDU-CAT-E-SR1-FF-V5R16Chapter 1: Project Resource Management

Day 1

EDU-CAT-E-SR1-FX-V5R16Step 5: Creating a Contextual End-Cut

EDU-CAT-E-SR1-FF-V5R16Chapter 4:Contextual End-cut

EDU-CAT-E-SR1-FX-V5R16Step 4: Creating a Standard End-Cut

EDU-CAT-E-SR1-FF-V5R16Chapter 4: Standard End-cut

Day 3

EDU-CAT-E-SR1-FX-V5R16Step 5: Creating a T-Chock

Exercises

EDU-CAT-E-SR1-FF-V5R16Chapter 4: Small Assemblies

AFTERNOON

EDU-CAT-E-SR1-FX-V5R16Step 5: Creating a Standard Slot

Exercises

EDU-CAT-E-SR1-FF-V5R16Chapter 4:Standard Slot

MORNING

Day 4

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Table of Contents

1. Project Resource Management p5Introducing the PRM p6Understanding the PRM p7Structure Discipline Resources p11Accessing the PRM p12Checking the PRM p15

2. Feature Dictionary p16About the Feature Dictionary p17Starting the Feature Dictionary Editor p18Managing Attributes p19Discrete Values p21Managing ID Number p22

3. Standard Section Catalogs p24Managing Parametric Sections p25Generating Resolved Parts p30Creating/Modifying Standard Section Catalogs

p32

4. Detailing Features p34Design Rules and Recommendations p35End-Cuts p38Slots p44Small Assemblies p47Storing Detailing Features in a catalog p50

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Project Resource ManagementThis 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 PRMStructure Discipline ResourcesChecking the PRM in SR1

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

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 Project–based notionThe 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\disciplinesTo edit the Project.xml file you need a text editor.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


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:


Copyright DASSAULT SYSTEMES

��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


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

Must be commented

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


PRM Key-words.

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.

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

FileEnoviaV5Smarteam

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

Instructor Notes:


Copyright DASSAULT SYSTEMES ��

��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Structure Discipline Resources (1/4)

The following Resources are used by the Structure Design application -<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="NamingSectionCharacteristics" Description="Naming for section characteristic sub-elements" Visible="yes">

<ID Type="Misc" Driver="File" Location="CATStrSectionNamingKeys" Access="R" Path="No Description" /></Resource>

- <Resource Name="StructureSectionsCatalog" Description="Structure Sections Catalog" Visible="yes">

<ID Type="Catia" Driver="File" Location="${Components_Directory}\StructuralCatalogs\AISC\AISC_Resolved.catalog" Access="R" Path="No Description" /></Resource>

- <Resource Name="StructureSectionsPath" Description="Structure Sections Path" Visible="yes">

<ID Type="Path" Driver="File" Location="${Components_Directory}\StructuralCatalogs\ModelsResolved" Access="RW" Path="No Description" /></Resource>

- <Resource Name="StructureThicknessList" Description="Structure Thickness List" Visible="yes">

<ID Type="Catia" Driver="File" Location="${Components_Directory}\StructuralCatalogs\ThicknessTables\ThicknessListSample.txt" Path="No Description" Access="R" /></Resource>

- <Resource Name="StructureOpeningsCatalog" Description="Structure Openings Catalog" Visible="yes">

<ID Type="Catia" Driver="File" Location="${Components_Directory}\StructuralCatalogs\OPENINGS\SFD_Openings_BigScale.catalog" Path="No Description" Access="R" /></Resource>

- <Resource Name="StructureMaterialsCatalog" Description="Structure Materials Catalog" Visible="yes">

<ID Type="Catia" Driver="File" Location="${Components_Directory}\StructuralCatalogs\Materials\StructureMaterials.CATMaterial" Access="R" Path="No Description" /></Resource>

- <Resource Name="StructureDrawingSymbolsCatalog" Description="Structure Drawing Symbols Catalog" Visible="yes">

<ID Type="Catia" Driver="File" Location="${Components_Directory}\StructuralCatalogs\DrawingSymbols\Structure2DSymbols-Cust.catalog" 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="CATStructureDesignUserDictionary" Description="Structure Design User Dictionary" Visible="yes">

<ID Type="Misc" Driver="File" Location="CATStructureDesignSample.CATfct" Path="No Description" Access="R" /></Resource>

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Accessing the PRM (1/3)

Set the variable in the Environment Editor. You do this by opening the Environment Editor dialog box and entering against the line CATDisciplinePath the directory in which your PRM files are:

From SR1 workbench, launch the project resource management (PRM)command by selecting Tools - Project Management - Select/Browse from the menu bar.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


The Select tab lists all the XML projects setup found in the directory defined by the environment variable CATDisciplinePath.Select the project of your choice, here TST_SR1. The corresponding PRM file is read.

Select the Browse tab. The dialog box lists all the applications defined for the chosen discipline, the description of the active application, and the list of resources of that application. The list of resources displayed is always that for the active application.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


When the Project Resource Management dialog box first displays it may contain a third tab - XML Parsing Error. This indicates that there is an XML syntax error in the file that corresponds to the Project you have chosen.

Select the XML Parsing Error tab to display the error, as shown in the image below.

You will need to correct the PRM file to get rid of the error. Errors in defining resources in the PRM file are explained in Checking the PRM chapter.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Checking the PRM

From SR1 workbench, launch the project resource management (PRM)command by selecting Tools - Project Management - Validation from the menu bar.

The errors are explained below.Resource definition has incorrect type: The value of the 'Type' field in the resource's PRM entry is incorrect. The Type field refers to file type. See the PRM task for more information. Resource not found in the project management xml file: There is no entry for the resource in the PRM file. Resource Data not found: The file or directory corresponding to the resource cannot be found at the location defined in the PRM file. Access specified for location for resource is not correct: Some entries have a field called 'Access'. This refers to the permissions set for the file corresponding to the resource. One common error is that some files need to have access set to RW (read-write) and not R (read only).

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Feature DictionaryThis task shows you how to start the Feature Dictionary Editor, to add properties to an object class and to define Discrete Values for a property.

About the Feature DictionaryStarting the Feature Dictionary EditorManaging AttributesDiscrete ValuesManaging ID Number

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

About the Feature Dictionary

The feature dictionary manages object classes. Object classes are classifications under which you create various objects, like components, for storing in the catalog. In the sample dictionary provided with the application, CATStructureDesignSample.CATfct file, two basic classes are managed: plates and shapes.You cannot add subclasses under plates or shapes, but you can add attributes and their values

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Starting the Feature Dictionary Editor

To view the sample dictionary, open the CATStructureDesignSample.CATfctfile, which is located, by default, in the install_folder under …/intel_a/resources/graphic. The Feature Dictionary Editor opens showing the sample dictionary.

CATGraphicPath: this Environment variable is used to manage the path directory of the CATStructureDesignSample.CATfct file

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Managing Attributes (1/2)

This is the general process to add an attribute.

1 In the specifications tree, double-click the class to which you want to add a property.

Click on the Add Attribute button2

The Add Attribute dialog box will display.

Enter an Attribute name3

Select an Attribute type4

Select Single Value or Discrete Values in the With field

5

Enter a Default value6

Not Mandatory.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Managing Attributes (2/2)

This is the general process to delete an attribute.

1 In the Local attributes frame, select the attribute you want to delete.

Select Delete button2

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Discrete Values

You may want to specify an attribute 'Type' for shapes with a list of discrete values like beam, column, brace, etc.Discrete Values lists are stored, by default, in …\intel_a\startup\EquipmentAndSystems\DiscreteValuesDiscreteValues is a resource manage by the PRM:<Resource Name="DiscreteValues" Description="Discrete Values Directory" Visible="yes"><ID Type="Path" Driver="File" Location="E:\SERVER\DS\Setup\EquipmentAndSystems\DiscreteValues" Path="No Description" Access="R" /></Resource>

1 Create a text file

The name of the text file must reflect the name of the attribute it refers to.

<Shift> <Enter><Shift> <Enter><Shift> <Enter><Shift> <Enter>

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Managing ID Number (1/2)

Every object that you create or part that you place, in your design document can be given a unique identifier. The default name is based on certain rules. A set of default rules is included with this application.ID Schema Resources : Give the system the path of the Structure Design ID Schema directory<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>

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>

The numeral 1 after the file name is used for a reference part.

<?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>

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Managing ID Number (2/2)

This task shows you how to modify or definethe object naming rules.

1 In the specifications tree, double-click the class to which you want to modify the ID Number.

Click on the Define ID schema button2

Click on Define/Modify ID Schema button

3

The Define/Modify ID Schema dialog box will display.

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.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Standard Section CatalogYou will see how to generate grids by assigning the basic parameters needed to create the grid.

Managing Parametric SectionsGenerating Resolved PartsCreating/Modifying Standard Section Catalogs

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Managing Parametric Sections (1/5)

1 Create a CATPart

Rename the driving offsets of the sketch 3

By convention in XY Plane.

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.

Create a Sketch 2

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


Create a dimension table 5

Value it: Beam.

Create the Parameter call: ProfileType4

Section Part creation (2/2)

Give it the name of the final CATPart. It’s a Tabulated text file that reflect the parameters you create for your Sketch. It contains a column “PartNumber”.

Associate this dimension table to the CATPart6

Save the CATPart7 Use the following naming convention: catalogname_familyname.CATPart (e.g. EN_IPSpecial)

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


create an appropriate construction point2

Edit the Sketched section 1

Defining Anchor Points for Sections

Rename the point3

Save the CATPart4

Use the prefix catStr, for example catStrOffsetTopCenter.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


Specify the location of the folder containing user sketches

2

Click the Name Section Characteristics icon

1

Naming Section Characteristics

Select the sketch of interest in the Name box

3

Name sketch edges using the contextual menu

4

Right-click a line and select the name from the list of pre-defined names in the contextual menu.

Repeat to identify all sketch edges5

Click OK when done6

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


Default names for typical shapes.

Typical I Shape

Typical L Shape

Typical U ShapeTypical T Shape

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Generating Resolved Parts (1/2)

1 Create a directory and place in it the parametric CATPart documents and associated design table documents.

2 Create a directory in which output resolved CATPart documents will be placed

3 Open a command prompt window and change to the directory ...intel_a\code\command.

You MUST specify the first set of coordinates at step 6.

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

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

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

The Create/Modify Catalog window is displayed

Select Create/Modify Catalog icon 2

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Creating/Modifying Standard Section Catalogs (2/2)

Application : select Structure Design

Parts directory field: the directory where the resolved parts are stored

Parts list field: give the path to list of resolvedparts (a text file)

Value the needed fields 3

Click OK 4

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Detailing FeaturesThis task shows you how to build a catalog of Detailing Features. This is usually done by an administrator.

Design Rules and RecommendationsEnd-CutsSlotsSmall AssembliesStoring Detailing Features in a catalog

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Design Rules and Recommendations (1/3)

GeneralAlways 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 LinesNever 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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


SketchingAlways sketch using the Sketch with Absolute Axis definition commandNever 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 AssembliesAlways 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 shapethat 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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


Convention Naming for End-CutsShape to which endcut will be applied:� Shape_(name of published shape surface or edge)

For example, Shape_Edge_MoldedFlange1_StartOther 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 SlotsPlate/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 AssembliesPlate/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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Standard End-Cut (1/3)

This task shows you how to build a catalog standard end-cut.

Create the contextual Environment.

1

2 Add Publications

3 Extract the needed edge\faces of the member, selecting from the publications, into a geometrical set called “Inputs”

Typically, a Product containing a Shape called Starter_Model

Use Manage Structure Publication icon found in Tools -Customize - Commands -All Commands category

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:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


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.

5 Create Parameters and associate them to the construction elements

6 Create a Pocket

7 Create a User Define Feature

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S


8 Publish parameters

9 Store the end-cut template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.

The Outputs tab must contain only the Pocket!

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Contextual End-Cut (1/3)

This task shows you how to build a catalog contextual end-cut.


1

2 Add Publications

3 Extract the needed edge\faces of the member, selecting from the publications of r-Shape1 and r-Shape3. r-Shape must be active.



Typically, a Product containing 3 Shapes called: r-Shape (Active Object: the shape to be cut)r-Shape1r-Shape3 (For internal inputs creation)This shape will be delete later on.

Only on r-Shape1 and r-Shape3

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

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S



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.


6 Create a Slot


Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S



9 Store the end-cut template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.

The Outputs tab must contain only the Slot!

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Slot (1/3)

This task shows you how to build a catalog slot.


1

2 Extract the needed edge\faces, selecting from the bodies, into a geometrical set called “Inputs”

Typically, a Part containing 2 bodies: one for the plate and one for the Shape.

Rename them using the naming convention

3 Create the construction geometry

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Slot (2/3)


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.


5 Create a Pocket


Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Slot (3/3)


8 Store the slot template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.

The Outputs tab must contain only the Pocket!

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Small Assembly (1/3)

This task shows you how to build a catalog small assembly.


1

2 Add Publications

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



Typically, a Product containing: a Shape (Active Object)a sub-product (it will contain the small assembly skeleton and definition)

Rename them using the naming convention: Shape1_ xxxxYou need to isolate Shape1_ elements and delete the extracts

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Catalog Small Assembly (2/3)

The Document Template Definition dialog box opens:

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


6 Create the physical elements


Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S



9 Rename and store the small assembly template in the Detailing Feature catalog: by default, DetailingFeatures.catalog.

Edit the list of available parameters to be published

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

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/FeatureCatalogs/Parametric.

Open the sample catalog 1

If necessary, expand the chapters to view their contents.

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.

Instructor Notes:



��

Cop

yrig

ht D

AS

SA

ULT

SY

STE

ME

S

Storing Detailing Features in a catalog (2/2)

The slot, end-cut or small assembly is added to the catalog.

Save the catalog when done.

2 Click the Add Component command

3 Click Select external feature

4 Select the slot, endcut or small assembly template in the specification tree of the document containing your template.

The Description Definition dialog box appears.

5 Click OK

Documents

Edu Cat en Sr1 Ai v5r16 Toprint