DS - WhitePapers - Links Management in 3DEXPERIENCE DesignEngineering Apps
DS - WhitePapers - Links Management in 3DEXPERIENCE DesignEngineering Apps
DS - WhitePapers - Links Management in 3DEXPERIENCE DesignEngineering Apps
LINKS MANAGEMENT IN
3D EXPERIENCE
Design / Engineering Applications
3DEXPERIENCE R2014x
White Paper
Executive Summary
The management of Links and Relations is important in understanding the
relation between the components under a Tree Structure; how they are
dependent on each other and what impact could a change in one entity have
on the other. This paper covers the concept of Link Foundation, commonly
experienced Relations in Design/Engineering Applications and the
management of the Links and Relations. The goal is to provide a consolidated
document to help users in identifying the Relations generated and in
effectively managing them.
2
White Paper
Contents
1. Links Foundation............................................................................................................ 4
1.1. PLM Core Modeler Overview ...................................................................................... 4
1.2. Aggregation Link and Instance Reference Link........................................................... 4
1.3. Identifying Links and Relation ..................................................................................... 5
1.4. Difference between Link and Relation ........................................................................ 5
2. Common Link Types ...................................................................................................... 6
2.1. Contextual Links ......................................................................................................... 6
2.1.1. Contextual Masks ................................................................................................... 8
2.2. Engineering Connection ........................................................................................... 10
2.3 Assembly Symmetry Links........................................................................................ 12
2.3. Implement Connections ............................................................................................ 12
2.4 Paste Special Links .................................................................................................. 14
3
White Paper
1. Links Foundation
The PLM kernel consists of three layers as illustrated by the following figure, from the
bottom to the top:
A PLM component is defined as a single entity with its identification, to which are
appended PLM information units like extensions, vault links, relations and lists.
PLM core model consists of 6 basic entities with pre-defined behaviors
Reference
Instance
Port
Connection
Representation Reference
Representation Instance
4
White Paper
In summary, here is the figure that illustrates all the PLM Core components and how
they fit together:
In 3DExperience, Links and Relations can be identified from Action Bar using Tools –
Links and Relation
5
White Paper
The path to the components specifies a relation; the path to the elements
underneath components specifies a link.
When an element that belongs to a component is deleted, the link is broken but
the relation is not broken as the component is not deleted. Any change made to
the component is reflected in the relation status marked as "desynchronized".
Relations are synchronized during a PLM Update.
Interfacing parts are designed using elements from one another so that they match
correctly with each other. This type of design is called as Contextual Design.
“Keep link with selected object” is a setting that allows creating a link with selected
object. This option is selectable from Tools / Option as shown in the image:
6
White Paper
In 3DEXPERIENCE R2014x Design / Engineering Apps the link works as explained below.
Following Relation Roles are generated while creating any Contextual Link.
1) Context – Indicates the path of the Instances under which Contextual Links have
been created.
2) Import- Indicates the Relation with the Original Contextual reference.
3) Import (Link) - It is the Link with the actual Imported External References.
7
White Paper
Three occurrences of contextual product exist (these masks are applied in the tree on
products and representations):
- Contextual Occurrence. This mask defines the context. This icon shows that the
reference is contextual and this occurrence is the context.
Example: Create a pad inside a 3Dshape using up to Last surface and use the
surface of another 3DPart inside the Assembly. An External Reference will get
created and the 3D Shape will get converted into Contextual instance.
8
White Paper
Example: Create a Physical Product and Insert a Contextual Reference inside it.
Example: Create an out of Context Instance and then delete the Original Contextual
Reference. The out of Context Instance will change into Not a Contextual Instance.
9
White Paper
Following are the relation roles which are created when we create an Engineering
connection between two components:
1) Impacted By
2) Impacts On
3) Support
Impacted by relation is created with the Second component involved in connection which is
impacted.
Support Link is created with other features involved in the Engineering connection like the
Axis, face etc.
10
White Paper
Which component would move in the Engineering connection and thereby which component
will have impact on and which component would be impacted by, is decided by the
Engineering Connection Definition box.
However if the user selects the option of automatically position Components, both the
components are identified by Impacts On.
If the engineering connection is created between a child product of the active product and a
product that does not belong to the active product, then a contextual engineering connection
is created which is identified by the contextual Link.
11
White Paper
While working with Assembly Symmetry various Links and Relations are generated which
are displayed as below:
2) Original Instance: This identifies the Relation with the Original Instance.
3) Symmetric Instance: This identifies the Relation with the Symmetric Instance created.
4) Original product: This is the Relation with the Original Reference Product.
5) Symmetric Product: This is the Relation with the Symmetric Product created.
12
White Paper
Whatever object you first select when creating an implement link, the implement relation is
always created from the lower level abstract category to the higher level abstract category.
In other words:
13
White Paper
A PartBody can be pasted from one Physical product to another physical product in the
following three types:
1) Paste or Paste Special-As specified in part Document: If features are pasted using
the regular paste or paste Special-As specified in part Document, all the features are
copied and no link is maintained to the source file.
2) Paste Special-As Result: If features are pasted using Paste special- As Result, the
geometry is copied (without features) and no Link is maintained to the source file.
3) Paste Special-As Result with Link: If features are pasted using Paste Special-As
Result with Link, the geometry is copied (and not the features) and the link is
maintained to the source file. These links are identified as Import Links. This
operation takes place beyond a context, unlike contextual links.
14
White Paper
Following are the Relation Roles which are created while generating Drawing View of any
Component:
1) Is a View Of
2) Is projected
3) Result
Projected:
It identifies the Link of the actual 3D representation/3D Shape with the drawing.
Link to 3D Axis system feature for a view associated to an axis system.
Link to Part Design Thread features that have a symbolic representation in the view.
Result:
It identifies the Link of the resultant View generated with the Physical Product.
Links to the product instances listed in the Bill of Material.
Apart from these Links, any interactively created modifications on the drawing like Addition
of Datum Surface or Text with Leader are added as Extended Specification Links.
15
White Paper
16
White Paper
While generating a Design Table either with pre-existing file or current parameter
value, a “Design table source file Link” is generated between the Excel/Text File and
the Physical Product.
17
White Paper
If some data is being accessed by a Resource table a set of links and relations
are generated:
1. Parametric Relation: It indicates the relation with the Physical Product under
which the Resource is inserted.
2. Parametric Relation Link: It is the Link generated between the Rule/Action
accessing the Resource from the Resource Table and the Physical product.
3. Resource: It indicates relation with the resource which is imported in the
Physical Product.
4. Resource Link: It is the Link generated between the Imported Resource and
the Resource Table.
18
White Paper
On creating a publication of a feature e.g. face or Axis, a Publish Link is established between
the published feature and the pointing Physical Product or 3D shape.
When a Material is attached to the Product or 3D Shape a “Core/Covering Material Link” and
“Material to Reference Link” are created between the “Product/3D Shape” and the “Material
Database” respectively.
19
White Paper
Edits Links and Relations is the primary tool used to diagnose incidents on links and
relations.
Edit Links and Relations dialog box comprises the following sections/commands as shown in
the image:
20
White Paper
“Relation filters” is used to filter links or relations. With the help of relation filters, user
can determine whether roles and status should be hidden or visible.
Isolate Link is used if user wants to isolate any unwanted Link from the List. However
when you isolate any relation, all its links are isolated as well.
21
White Paper
The synchronization process affects the status of a relation. The table below describes the
symbols that indicate the following situations:
Symbol - Meaning
Status icon
The relation is not synchronized and references a minor version that is not the
current "minor" of the pointed component.
22
White Paper
Symbol - Meaning
Status icon
The relation is not loaded in the current session. The pointed component
exists in the database.
The relation has been broken in the current session. The relation status has
not been saved to the database.
The relation has been broken. The relation status has already been saved to
the database.
User can reconnect relations manually provided that the pointed components are of
the same type: a 3D shape with another 3D shape, a product with another product. It
is only available when a component is selected. It is also possible to replace the
context of a contextual link.
Relations can also be automatically reconnected when another version (major, minor,
evolution) of the missing pointed component is found in session. The purpose of this
action is to assist end-user to automate as much as possible the reconnect of the
relations.
23
White Paper
The Reconnect Assistant dialog box will appear when at least one alternative
component is found in session.
Apply proposed Action directly opens the Reconnect Assistant if there is any
proposed action in the Edit Links & Relations dialog Box.
4. Document History
Document
Date Revised By Changes/Notes
Revision
24
White Paper