This section provides an overview of technological packages. If you need specific information regarding the use of technological packages in the workbenches in which they are implemented, refer to the corresponding workbench documentation. | |||||||||||
"Technological
package" is a new notion that enables you to group and manage design
specifications as well as DMU applicative data in order to save them in
ENOVIA V5 VPM context. Technological packages can be created in CATIA
Version 5 products using ENOVIA V5-based resources. However, they can be
saved and deleted in ENOVIA V5 only. Each technological package is considered as a single entity and can contain the following elements:
A technological package is always linked to a product structure and therefore, it is not possible to configure a technological package outside a product. |
|||||||||||
Technological Package Creation |
|||||||||||
Technological packages can be
created under any product in Explode mode (i.e. Structure
Exposed - Document not kept). How are technological packages created?
|
|||||||||||
You can create, display and
manage in context several technological packages in the same product or in
a single CATIA Version 5 session or in sub-levels of the product that is
currently open. In all cases, the technological package is always created in the UI-active product. When creating a technological package, you can specify:
As soon as a technological package is created, it is displayed as a node named "Technological Package" preceded by its category in the specification tree: |
|||||||||||
This node will be made up of several sub-nodes, each sub-node corresponding to a type of data. The example below shows a technological package into which a DMU Review (named "DMU Review.1") has been created: | |||||||||||
Note that there is no semantic relation between the category of a technological package and the data it contains. For instance, a "DMU" technological package may contain or not DMU specifications AND other data such as Knowledgeware rules: | |||||||||||
More than one technological package can be saved in a single structure (either a product or a PRC) with the same name and the same properties. A technological package can therefore not be made unique in the ENOVIA V5 database. | |||||||||||
Technological Package Activation |
|||||||||||
To set a technological package
as active, you need first to select in the specification tree the
technological package to be activated then right-click and select Set
as current. You can create as many technological packages as needed
but bear in mind that only one can be set as current, i.e. considered as
active in the active product. Any new data will be created in the active
technological package. |
|||||||||||
For an example, refer to Setting a Technological Package as Current. | |||||||||||
Each time you set a new product
as "active", one of the technological packages it contains (if any) becomes
active using the following process:
Note that the active technological package is not a persistent data. |
|||||||||||
In case no technological package exists, a new one is automatically created (without having to access the Technological Package Creation dialog box) when creating data for the first time. | |||||||||||
Technological Package Storage |
|||||||||||
All the data contained in a
technological package are automatically saved when you do a save in ENOVIA
V5 VPM using the Save data in ENOVIA V5 command.
|
|||||||||||
About File>Desk and Edit>Links |
|||||||||||
The following table sums up the information displayed in the Desk or in the Links dialog box when working in an ENOVIA V5-based environment: | |||||||||||
|
|||||||||||
Where To Find More Information? |
|||||||||||
More specific information on
technological packages can be found in the following user's guides:
|
|||||||||||