 |
The V5 Product
Structure model is based on the instance-reference model which meets
assembly requirements. There is a second need of organizational nature.
This is why this new functionality has been created: the insertion of new
objects allowing data structuring and organization. |
 |
The WBS functionality is only available in the
context of the ENOVIA LCA/CATIA V5 interoperability. |
 |
You import an existing WBS arborescence into a
CATProduct. One of the created GCO Views
(Generic component) can be designated as the active
View and after the File/Open operation you immediately have access to the
active View. You can associate the
instance of a product to a GCO, with the following constraints: the
instance must be a first instance (directly under the root product), and
this instance can appear only once in a View. You can use the Copy /
Paste or drag and drop functionalities (Light Copy format).
Note that you can copy a GCO under another GCO or under another PRC, this
is the PCO format, also called the GCO format.
You can insert components, products, parts,...
into a GCO node. These elements are under the root product, and an
association between the created instance and the GCO node takes place.
There are four navigation/visualization modes: Global View, Active View,
Product Structure View and GCO View.
In a V5 industrial Assembly, the first assembly levels are generally
dedicated to organizational purposes whereas the other levels play the
role of an assembly structure:
|
|
In this schema, the
red nodes correspond to the assembly structure whereas the blue ones
represent the organizational role. You can now insert a new type of
object: CATGco (blue nodes in the following schema). It allows you to
improve the assembly model and bring flexibility in the organization
data:
|
|
The WBS arborescence
has the following benefits:
- you can avoid the weight of the instance model when you do not need
it
- there is no impact on the product architecture which has the same
behavior
- there are several choices of Views
- the product section is separated from the organizational part. You
can modify the organizational part or the association of the
organizational part with the product section without impacting on the
product section.
|
|
|
-
In ENOVIA LCA, create a Product Class and a new
Product: TestWBS for instance.
-
Send this Product to Product Editor and
click New in the contextual menu of TestWBS. You can edit
the name of the Product Component Id which will determine the name of
the GCO. The user can define several Views in
ENOVIA LCA (not in CATIA V5, no creation of Generic Component). And an
Assembly can have several Views in different contexts that can be
visualized, activated in CATIA V5.
-
Send this Product to CATIA V5.
|
 |
For more information
about manipulating ENOVIA LCA documents, please refer to Sending an
ENOVIA LCA Document into CATIA V5 in ENOVIA / CATIA Interoperability
User's Guide. |
 |
-
In CATIA V5, open the Product (with Views) you had
created in ENOVIA LCA. Click the contextual command of a View and
select Set Active View to visualize both
GCO nodes and products.
You can note that the Active
View is always underlined: View1.
-
You can also Insert a new
component / product / part / an existing component in the
View.
|
|
|
If you want to
create a new View, you need to return into ENOVIA LCA. |
|
-
In the View -> Toolbars
menu, you can activate the WBS toolbar because it is not active by
default. Four navigation / visualization modes are available:
Global View: complete Specification
Tree, with the Product Structure and the WBS arborescence, which is
useful to drag & drop components.
Active View: GCO nodes and products.
You can only visualize the products associated to the active View.
You are in this mode after the File/Open operation.
Product Structure View: the
Specification Tree with the Product Structure, all the products can
be visualized.. No access to the GCO nodes.
View Tree: a tree with only the WBS
arborescence (Views and GCO) and no product structure.
-
Click the contextual menu of a product,
Part4 for instance, in GCO2 to remove it:
And Part4 disappears:
|
 |
