advanced concepts - wichita€¦ · enovia lca advanced concepts enovia® v5r15 introduction, page...

Advanced Concepts

NATIONAL INSTITUTE FOR AVIATION RESEARCHWichita State University

Revision 15Copyright 2006. All rights reserved.

www.cadcamlab.org

None of this material may be reproduced, used or disclosed, in part or in whole, without the expressed written permission of:

National Institute for Aviation ResearchWichita State University

Wichita, KS

Copyright 2006. All rights reserved.

www.cadcamlab.org

ENOVIA LCA Advanced Concepts ENOVIA® V5R15

Table of Contents, Page i© Wichita State University

TABLE OF CONTENTS

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1ENOVIA LCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Manual Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Logging into ENOVIA LCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4ENOVIA is a Multi-User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Product Class Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7New Product Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9New Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Configuring a Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Component Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Categories Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Creating Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Adding Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Associate Categories and Specifications to the Product . . . . . . . . . . . . . . . . . . . . . 35

Rules Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Inclusion Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Expression Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Product Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Change Request Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Change Order Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Action Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Effectivity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Effectivity Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Associating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuration Management Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135


Table of Contents, Page ii ©Wichita State University

Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Creating New Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Viewing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Create Additional Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Changing the Document Object Primary Format . . . . . . . . . . . . . . . . . . . . . . . . . . 165Check In / Check Out Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Iterations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171My Docs and My Checked Out Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Table of Contents(TOC) objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Associating Documents to existing ENOVIA objects . . . . . . . . . . . . . . . . . . . . . . 185Unlinking associated documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Revising Document Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Viewing CATIA parts as document objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Deleting document objects from ENOVIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Deleting CATIA documents from ENOVIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Publish Subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

ENOVIA Portal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Category Editor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Change Orders Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Content Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Part Editor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Product Editor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Rules Editor Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Impacted By Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Impacts On Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218


Introduction, Page 1© Wichita State University

Introduction

ENOVIA LCA Advanced Concepts

Upon completion of this course the student should have a full understanding of thefollowing topics:

– Creating new Product Classes and Products

– Create generic components within a product

– Create categories and specifications and associate them to a product

– Create rules to govern specifications

– Understand change the change management capabilities in ENOVIA

– Create change requests, change orders, and actions

– Add and deleted documents directly in the database


Introduction, Page 2 ©Wichita State University

ENOVIA LCA

As stated in the ENOVIA LCA Concepts book, ENOVIA is an object oriented PLMdatabase. In the concepts course you learned how to navigate and utilize ENOVIA toretrieve information and send it to the various editors such as CATIA and Word. Thiscourse is going to extend on that knowledge and look at how those types of objects areactually created in the ENOVIA environment. You will also look at the changemanagement process and build upon a change request through the change order and down tothe individual actions created therein. This course will also introduce you to CATIA’sassembly design capabilities for creating and inserting parts into the database.



Manual Format

It is important to understand the format of the manual in order to use it most effectively.This manual is designed to be used along with an instructor; however, you will need to do alot of reading as well, in order to fully understand ENOVIA LCA. The exercises in thisbook will list steps for you to complete, along with explanations that try to inform you whatyou have just done and what you are getting ready to do. The actual steps are in bold typeand the information that follows the steps is for your benefit. Anything that appears initalics refers to a message ENOVIA provides—this includes information in pull-downmenus, pop-up windows and other messages.

An example of a step and its explanation is shown below (note: normally the lines will notbe there):

Select a location to the right of the origin. This specifies the other end point of the line.You will continue specifying locations in order to complete your profile. It should appearsimilar to the diagram shown below.

As you can see, the desired action blends in with the text except that it appears in bold. Theinformation following the step explains what that step accomplished and where you aregoing next. It is important for you to read this information to help in your understanding ofENOVIA.

Also, you will find that the exercises build upon themselves. Later exercises often assumeyou know how to do certain steps which have been covered in earlier exercises. If you didnot quite pick up what you needed to know from an exercise, you will probably wish toreview it several times before moving on to the more advanced sections. As you progressthrough the manual, it expects that you are learning and therefore you are able to do a lotmore with fewer steps. Eventually, you are expected to be able to perform actions withoutany steps.



Logging into ENOVIA LCA

ENOVIA utilizes a username and password database that is generally independent of theusername and password you log into your computer with. Before logging into ENOVIA,you must have a username and password defined. Your account will also have an associatedrole. A role defines what a user can and cannot do in the database. This includes not onlyread and write access to the database, but also functionality access such as the ability toperform tasks in the database. All three parts of your login credentials must be supplied inthe login screen before you have access to the ENOVIA database.

Take a moment and look at the login screen for ENOVIA.

Username This will be the username provided to you. Theusername might, or might not, be the same as theaccount you logged into the computer with.

Password This is the password used with your username.

Language This allows you to choose between various languagesused in ENOVIA.

Host The host field allows you to choose between variousENOVIA servers. Generally, there will only be onehost set up, however, if you have multiple ENOVIAservers running on your network, all of them can beaccessible though the portal.

Check to choose role at logon This allows you to choose or change your role withinENOVIA.

Enter your username and password, then click Logon. Once you click logon, you willbe prompted for a role and workbook.



Choose a Role This will display the list of roles available with your login ID.

Choose a Workbook This defines the workbook project that you will utilize. When used ina group setting, this will allow your group to view the same data andmake things more uniform.

Generally, the first time you log into ENOVIA, you will have to define the Role andWorkbook that you want to use for this session. Anytime you wish to change roles, you willhave to log out of ENOVIA and log back in. The roles defined with your user account areset up by an ENOVIA administrator. If you find that you are unable to perform functions inthe database that you need to have access to, you will have to have an ENOVIAadministrator adjust the roles associated with your user ID.

Choose the role TRAINEE.ENOVIATRAINING.DEFAULT. This will define thedefault training role for your work.

Change the Workbook to DefaultProject if not already there. For now, the defaultproject will be used.

Click Apply Role and Project. This will log you into the ENOVIA portal.



ENOVIA is a Multi-User Database

As you create objects in the database it is important to remember that this is a multi-userdatabase. This means that everyone in your class, as well as other classes are all utilizingthe same database and vault for storage. This is an advantage of ENOVIA to be able toshare data between all users of the database locally and across the globe.

One important aspect to draw from this is that your book may vary slightly from what yousee on the screen. The book may show that there are no product classes, when in fact youmay see many product classes. This will be due to other users creating objects in thedatabase. Keep in mind, this book is written from a blank database, hence only a fewobjects created by the author will exist. As you, your classmates, and other ENOVIA basedcourses create objects in the database, it will quickly be populated with objects similar to theone you are creating.

Another important aspect is the necessity to create unique objects in the database. This isthe same principle as working with files on a computer. If you place an image on yourdesktop called “Funny Picture”, then you save another image on your desktop as “FunnyPicture”, you will only end up with the last one saved since it would have overwritten theoriginal. This is why you would name the new image “Funny Picture 2" or a different,unique name. ENOVIA is no different. As you create objects in the database, you will wantto be sure that your object is unique to you and only you. This is why the book will ask youto create an object with your user ID. All user ID’s are unique to the database, and shouldnot be repeated in a class session. The book will utilize the user ID TRN000, a user ID notused by anyone else. Any time you wish to create an object in the database, be sure toinclude your unique user ID. This is not an issue at companies utilizing ENOVIA for datastorage since all objects will be identified by a unique part number. This is only a concernwith the training environment since everyone will be creating the same objectssimultaneously.

In order to keep consistency, the book will use the following convention when creatingobjects utilizing your user ID:

Key {USERID} - Object Type for the Object ID.

Then when you look at the picture you would see:

In this case, any time you see {USERID} you will use your user ID. The book will alwaysuse the user ID TRN000.


Product Class Editor, Page 7© Wichita State University

Product Class Editor

In the concepts course, you learned to navigate the product class editor to find product,product specifications, and product types. In this course, you will learn how to generateproduct classes and products. In this course, you will create product classes and products.

Under the engineering life cycle folder of the ENOVIA home workbook, activate theProduct Classes application. If you remember, the product classes application allows youto view and create product classes.

Note: For a description of the icons, please refer to your ENOVIA LCA Concepts course.


Product Class Editor, Page 8 ©Wichita State University

In order to keep some organization of the database, you will not create a product class root.Creating a product class root is as simple as selecting the New icon from the standardtoolbar, then entering a product class root name.

Since ENOVIA is a multi-user database, if everyone were to create product class roots, youwould end up with a very large product class tree. Instead, you will be creating a newproduct class to store your data.



New Product Class

New product classes are easy to create and will help you keep your products organized asyou work through this course.

Select then right click on the LCA Advanced product class root, then select New. If youremember from your concepts course, there are many times when you need to select on theobject prior to right clicking. This is to tell ENOVIA exactly which object you are workingwith. If you did not select it first, your right click would act on the currently selected object,wherever it might be in the product class tree.

The new option here will allow you to create objects under the product class root. Take amoment to look at the different options.

Product Class This allows you to create a product class within the currentlyselected product class

Product This allows you to create an unconfigured product

Product Reference (by copy) Creates a new product from a copy of a selected product

Product Type Creates a major product variant specification to help organizea product

Product Specification Creates a specific product variant based on categories andspecifications

Select Product Class. This will allow you to generate a new product class within the LCAAdvanced product class root. This will display the New Product Class pane.

Take a moment to look at the new product class pane. This pane will be very similar toother types of object creation panes.



Environment This allows you to select the specific environment from which tocreate the new type of object

Type This defines the specific type of object created

Product Class ID This defines the unique product class identifier

Name Any user defined name for the product class. This does not have tobe unique in the database

Description A user defined description of the product class

OK This creates the object, then closes the creation window

Add This creates the object, but leaves the creation window open to allowyou to create additional objects without having to reselect new eachtime

Reset Resets the fields back to the default entries, which is generally blankfields

Cancel Cancels the creation of the object. Any objects already added willexist even if you cancel.

Notice the red exclamation point next to the product class ID.

Mandatory Anytime you see a red exclamation point next to a field, it indicatesthat it is a mandatory field. Generally, all ID fields will bemandatory, however, an ENOVIA installation can have any numberof mandatory fields.



Key in the product class ID of {USERID} - Product Class. Remember, this is where youwill use your TRN account ID to insure the uniqueness of each product class ID created.

Key in {YOUR NAME} in the Name field. This does not need to be a unique field since itjust an attribute of the product class.

Key in My Products as the description. Again, this does not have to be unique in thedatabase since it is just an attribute of the product class.

Select OK when done. This will create the product class in the database.



You should get a prompt in the bottom left corner of the pane to indicate that the productclass was successfully created.

At any point in time, you can edit the properties.

Select the Edit icon in the bottom center of the properties pane. This will allowyou to edit and change the ID, Name, and Description.



Notice you cannot change the owner, dates, or status. These are changed through differentmechanisms. You will look at how to change those entries later.

Change the Description to be My Products and Product Classes. Select OK when done.This will change the description of the product class.



This will have your own unique product class created. Anytime you wish to create a newproduct or new product class to further organize your data, feel free to place it in thisproduct class.

Select the Save icon from the standard toolbar. This will save and commit thechanges to the database. Although objects created are generally saved directly to thedatabase, it is wise to always save often.

Create a new product class under your product class called {USERID} - Exercise 1.By creating sub-product classes, you will be able to organize your products within yourproduct class.

Enter a Name and Description if desired. Since these fields are not mandatory, you havethe option fill them in or not. From this point on, it will be left to you to enter a name and /or a description.

Now you are going to look at creating a new product.



New Product

Creating a new product is no different than creating a new product class.

Select then right click your exercise 1 product class. Select New then Product. Thiswill display the new product for product class pane to allow you to define a new product.

Look familiar? This the same window as for creating a product class, just this time you arecreating a product. You will find this very common for all object creations inside ENOVIA.

Key in {USERID} - Product 1 for the product ID. Again, it will be left to you to enter aname and description.

Select Add. This will add the product to your product class.

Notice the new product for product class pane is still active and still contains all theinformation you entered before. This will allow you to add multiple products, productclasses, or any other ENOVIA object in repetition without having to constantly keep re-entering names and descriptions.

Change the Product ID to TRN000 - Product 2. Select OK when done. This will createa second unconfigured product in your product class.



Save your new products. This is done by selecting the Save Icon.

Notice both of your products are unconfigured.

By default, anytime you create a product, it will be unconfigured. You have to configure theproduct in a second step.



Configuring a Product

If you remember from your basics class, a configured product has the abilities to haveconfiguration attributes, history tracking, and actions applied. In order to have any sort of acomplex product (basically anything with constraints applied) you will have to have aconfigured product. Only the most simplistic one or two part products will be unconfigured.

Select then right click on your Product 2 from the product class view. Select Productfrom the contextual menu. This will display the product actions that can be performed.

Configure Configures a product to allow for configuration attributes tobe applied

Copy Associated Object Copies the product as an associated object to allow it to bepasted as an associated object in an action or change order

Move / Cut Removes a product from the current product class

Paste Pastes a moved / cut product into a different product class

You will copy the associated object when you start working with actions. If after creatingnew product classes, you find that you want to reorganize your products you can always cutthem from one product class then paste them into a new one. For now, you will just want toconfigure your product.

Select Configure. That is all it takes to configure a product.



Notice now your product indicates that it is a configured product, and there is aconfiguration tab. You will also get a prompt at the bottom left of the screen to indicate theproduct is configured.

Keep in mind, once a product is configured, it cannot be unconfigured. Although this istrue, there are extremely few reasons not to have a configured product.

Configure your Product 1. Again, just right click on the product, select the Productoption, then select configure. If the configure option is not available, be sure you selectedon the product before right clicking on it. Remember, ENOVIA performs the right clickaction on whatever is currently selected, not what the cursor is pointing to.

Save your ENOVIA session. This just insures that the changes are committed to thedatabase. You should now have two configured products.

Note: If you would like to see your other classmates products and product classes, select therefresh icon, then refresh all trees. Your ENOVIA screen does not automatically update.


Component Editor, Page 19© Wichita State University

Component Editor

The component editor allows you to generate generic components in a product structure. Inthe ENOVIA concepts course, you found that a product can have a variety of organizationschemes based on the generic component structure. Although the generic components(GCOs) are not mandatory, they can prove very beneficial when working in a large datastructure. Take a look at creating a few GCOs in your product.

In the Product Class Editor, find your Product 1. If you closed your product class editorfrom the previous exercise, you will need to re-open it and locate your product.

Right click on your product 1, then select Send To. If you remember from the basicscourse, this will allow you to send the product to various editors. You will notice towardsthe top of the list is the component editor.

Select Component Editor. This will send the product to the component editor.


Component Editor, Page 20 ©Wichita State University

The component editor is a very simplistic editor that only allows for the creation anddeletion of the generic components. Notice there is not even a toolbar specific for thecomponent editor on the left hand side of the window. You only have the standard toolbarat the top.

The component editor comprises of two panes. The left hand pane is the generic componenttree. This is where generic components are created and deleted via right click options. Theright hand pane is the properties pane for the generic components and product.

Right click on your product from the Generic Component Tree. This will display youroptions for creating a generic component. Most of the options are standard right clickoptions, however, there are two options that are specific to creating the first genericcomponent.

Insert Child Creates a child generic component. This will be a component belowthe currently selected object.

Import Template This imports a generic component tree from another product. This isuseful for replicating a generic component tree that has already beenestablished.

If you right click on a generic component from the GCO tree, you will get one additionaloption.

Note: You currently do not have any GCOs in your tree. This is for future reference only.

Insert Parent This creates a generic component as a parent of the selected genericcomponent. This means that the GCO selected, and any childrenGCOs, will be placed under this one parent GCO.


Component Editor, Page 21© Wichita State University

Important Note: The GCO tree can not be rearranged. If you create a series of children orparents, and you decide you want to change location or position in the tree, you cannot cutand paste or move the GCOs in any way. You must delete the GCO tree and re-create it.This will also involve re-linking all instances to the new GCO objects.

Select Insert Child.This will display the new generic component creation pane.

As you might have already noticed, this is the same sort of object creation pane that is usedthroughout ENOVIA.

Enter GCO-1 as the Product Component ID. Since this is the only mandatory field, youhave the option to fill in the rest of the pane.

Note: Notice you were not instructed to add your account to the GCO. Since GCOs arechild objects of the product, you do not have to worry about duplicate names. You do haveto worry about duplicate GCO ID’s within the product though.

Select OK when done. This will create the generic component in the product.

With GCO-1 selected, select on the Insert child icon from the standard toolbar. Inmost other editors, this would be considered the New icon, but in this editor, its name ischanged. This is the same as the right click, insert child option.

Enter Sub GCO-1 as the Product Component ID. Again, the rest of the information willbe up to you to enter.


Component Editor, Page 22 ©Wichita State University

Select OK when done. This will create a child object to the GCO-1.

Create a new child to GCO-1. ID this new child Sub2 GCO-1. The process will be thesame, select on the GCO-1, then insert a new child either through the right click or icon,then enter the ID and any other information.

Select OK when done. You should now have a GCO tree that has one parent GCO and twochild GCOs.

Note: If your tree does not appear as above, you can delete the GCOs, then re-create them.

Right click on Sub2 GCO-1 and select Insert Parent. Make sure it is selected before rightclicking.

Enter the ID of Parent GCO, then select OK when done. Notice this puts the new GCOabove the Sub2 GCO.

As you work with your products, you may find you want to create a GCO structure tocontrol and organize your product. Feel free to create GCOs as you feel necessary.

Save and close the Generic Component Editor.

Other available courses

CATIA V5 and ENOVIA• CATIA Basic Concepts• CATIA Part Design & Sketcher• CATIA Assembly Design• CATIA Drafting• CATIA Wireframe & Surfaces• CATIA Prismatic Machining • CATIA Surface Machining• CATIA Fitting Simulation & Kinematics• CATIA Functional Tolerancing & Annotation• CATIA Stress Analysis• ENOVIA DMU Viewer• ENOVIA LCA Basic Concepts• ENOVIA LCA Advanced Concepts• ENOVIA LCA Product Design

To enroll in any of the above courses, contact us at: (316) 978-3283toll-free at: 1-800-NIARWSU or email: [email protected]