Working with Knowledgeware and Technological Packages

It is possible to create Knowledge data at the exploded product level to define assemblies containing parameters and relations in ENOVIA V5 VPM thus allowing collaborative work and concurrent engineering.

Knowledge objects are inserted into technological packages associated with the product. These technological packages are stored as entities in ENOVIA.

Technological packages are entities that are created by you. You may decide to create one or several technological packages under the same product. Only one of these technological packages is considered as active. After creating the application data in the active product, it is added to the current active technological package.
Technological packages can be considered as folders (for the representation in V5 tree view), and as separate documents associated with the product (for the persistency aspect) even if they are not implemented as documents.
Technological packages can be heterogeneous in terms of included applicative data.
Each technological package can be loaded or not in CATIA (via VPM Navigator).
User rights and lock capabilities can be granted/assigned to a technological package.
When loading a product structure, technological packages are not loaded by default: You can identify the technological packages associated with the product structure and decide to load them or not. This capability is available through the VPM Navigator user interface.
Pointings Expositions: The exposed link is not on the Part document but on the instance of the Part.

Knowledge objects usually make reference to other objects that may belong to the product structure itself, to other technological packages, or to part documents that belong to the product structure. Thus, those references need to be stored in ENOVIA and navigated through VPM Navigator.

The following Knowledge features are supported:

Infrastructure

Knowledge Advisor

Product Engineering Optimizer

Knowledge Expert

Parameters
Parameters Sets
Formulas
Relations Sets
Laws
Inspector
Design Tables
Equivalent Dimensions

Rules

Checks
Sets of Equations
Reactions
Actions
Lists
Loops
VBScripts

Optimizations
Designs of Experiments
Constraints Satisfaction

RuleBases with Links
Standard RuleBases

The solution coverage depends on the kind of information that can be referenced through Knowledgeware relations.

The following features can be referenced:

Part parameters (or work package products parameters).

Part publications of parameters.

Parameters that belong to other technological packages.

The following features cannot be referenced:

Offset parameters of constraints.

Kinematics mechanisms parameters.

Features in documents.

Objects that belong to other technological packages.