Professional Documents
Culture Documents
Airbus Deutschland
History
Version 07
Date: 04/10/02
Status: Currently being worked on
Author: von Bloh
File: VPMBasisschulung_Modul01_Version07_eng.doc
2 Product Structure....................................................................................................................................... 31
2.1 Objectives ............................................................................................................................................ 31
2.2 Opening the PSN ................................................................................................................................. 31
2.3 PSN...................................................................................................................................................... 32
2.4 Creating a Structure ............................................................................................................................. 38
2.5 Example: Creating a Structure............................................................................................................. 43
2.6 PSN Toolbar ........................................................................................................................................ 45
2.7 PSN Menu ........................................................................................................................................... 46
4 Release Management.................................................................................................................................. 56
4.1 Objectives ............................................................................................................................................ 56
4.2 General ................................................................................................................................................ 56
4.3 Maturity ............................................................................................................................................... 56
4.4 Maturity on Part and Model / Issue ..................................................................................................... 57
4.5 Issue on Part and Model ...................................................................................................................... 58
7 Glossary....................................................................................................................................................... 64
1 VPM Introduction
1.1 Objectives
Understanding the VPM working method (what Parts, Models, Attributes, etc.)
Choosing the VPM User role
Choosing a Project and Environment
Working in VPMA (VPM Objects displayed in a list)
Creating VPM-Parts and Models (Create & Save)
Starting Catia in VPM
1.2 General
The EnoviaVPM (Virtual Product Model) for virtual preparation of the complete product
(e.g. A380) with controlled access of all employees that are participating in the development
process. For managing, creating, processing and providing product data, the VPM is the
central function to start with.
EnoviaVPM TAKSY
Catia V4 DMU-Navigator
1.4 Objects
The objects are prepared and managed in a list in the VPMA, and in a tree structure in the
PSN.
Links serve for interconnection and data transfer between the objects. Links enable the
preparation of assemblies.
In the VPM, the following objects describe the product data:
Parts, Models (= Object classes)
Part
A Part is the basic object in VPM and incorporates company-specific attributes (Airbus
specific attribute e.g. according to AP2610 as ATA, Part Type, etc.) that help identifying
and describing the Part. Usually a Part is linked to a Model and/or Document that describes
this Part. Furthermore, Parts are used for describing Assemblies.
For better understanding, a Part may be regarded as a book that has Attributes and other
Objects as content:
DRW Model
SOL Model
Model
A VPM Model consists of descriptive Attributes and a CAD Model (CatiaV4 Model).
Just as for the Part, the Model Attributes are company specific and partly consist of drawing
number and version. The CatiaV4 models may be available in different forms as e.g. 2D,
3D, kinematics, etc.
One part must be allocated to every VPM model. The relation between Part and Model(s) is
1àn. This means that every time a Model is created, a Part must be created simultaneously
or an existing Part must be allocated.
1àn MODEL
PART MODEL
MODEL
1x
1x
1x
VPM Role
When you start VPM, the first thing queried is the role of the user.
The administrator allocates certain rights to every role. These rights depend on the UNIX
user. Via the role, the access rights for VPM objects are controlled. In general, there are the
following roles:
DESIGNER_<ATA> Writing and deleting access to all relevant data (ATA)
Reading access to all data
ZONI_<ATA> Enhanced writing and deleting access to all relevant data (ATA)
(Zone integrator) Reading access to all data
READER Reading access to all data
Furthermore, the roles (except for READER) are subdivided in ATA chapters.
This is implemented in the role by the _<ATA>, suffix, e.g. 53 for structure.
From the menu,
User name choose a user role
1x
Confirm
VPMA Window
After you confirm in the Start window, the VPMA window is displayed.
Selecting the
Environment
Object list
Selecting an object
from the list
Selecting a Viewer
Help window
Functions for
object selection
Information Bar
Displays the name of the current window, environments, and type of object.
Menu Bar
The menu bar is subdivided into different sub menus, that are described in the following
chapters.
Tool Bar
The tool bar provides frequently used commands that are represented by icons. All
commands represented in the tool bar can normally also be found in one of the menus.
Icons, which are not available are dimmed.
Defining an Environment
Here, you define the Environment, in which you want to operate. However, a selection of
Environments is already defined when you select your role (see VPM Start) (Environment
see chapter 1.6).
With simple operations you may select objects from the database. Via the
button you can search the database for certain object attributes for the manually entered
strings.
More differentiated search options are described in the following chapters.
The objects selected via query are listed here with their attributes (see fig.). You may
determine which attributes you want to display. This option is described in chapter 6.
You can select an object by clicking on the mouse button (marked white). Click Shift or
Ctrl together with the mouse button in order to select more than one object (multiple
selection).
Selecting a Viewer
Here, you select the viewers for the object types. A Viewer serves to view an object; in the
VPM this is usually the PSN, CatiaV4, the DMU Navigator or a text editor.
With simple operations you may select objects from the Objects list.
Help Window
This window displays a short description on the function, over which the mouse cursor is
held.
· Replace/Add:
Here you select , whether the objects selected via a query Replace the objects currently
loaded in the VPMA or are Added to these.
· Clear:
With this function you delete the objects from the VPMA.
· Add Object:
Via this function you can display copied objects in the results list.
Project Environment
A380PROG
A380PROG A380DSGN
A380DSGN
A400PROG
A400PROG A400DSGN
A400DSGN
A400MANU
A400MANU
GENERAL
GENERAL GESTDLIB
GESTDLIB
EADSPREP
EADSPREP
Selecting an Object 1x
If you click the button, all objects pertaining to the selected object type and
existing within this environment are displayed. If you select Models or Documents, the Parts
associated with these are also displayed in the same window, in a separate list. At this point,
the relation/ dependency between Part and Model (Document) becomes clear.
Create&Save Window
Further ist possible to create a part or model directly out of the contextmenue from a part in
the PSN. This function will be explained in chapter 2.
The window for creating a Model with Part is illustrated below, as an example. In case you
create only one Part, only the Part window will open.
PART
MODEL
The attributes relevant for the Part are found in the upper section of the window, and the
attributes relevant for the model are found in the lower section of the Create&Save window.
The names of the attributes are listed to the left and usually describe Airbus specific data,
such as the Part ID, English description or the type of CAD model (SOLID, DRAW, etc.).
The attributes and their permissible values are described in chapter 1.8 "Airbus Attribute
Identification".
· There are two types of attributes:
Mandatory Attributes: To this Attribute type a value must be allocated. Without this
step, it is not possible to create the object. The Icon indicates such an Attribute.
Optional Attributes: It is not necessary to define a value for these Attributes. Via the
Triangle symbol in the middle column you can set the value to "Null" (àis null).
Attribute value
Attribute name Attribute value
= Null
Attribute
value has
been assigned
· To every VPM model, a CAD model (usually CatiaV4) must be allocated. The CAD
model can be originated from four different sources:
· For the sources "Copy from", "Move from" und "Startup", click on the Source
Icon to select the UNIX path or model pool, in which your CatiaV4 model is stored.
In this case the model is deleted from the source directory and can thus not be called up
directly under CatiaV4 (without VPM).
Selection of the
model via UNIX List field with
path or model pool predefined values for
the model source
· Click OK to check the entered values. If you click Apply, the window will remain
opened for further entries.
After you have confirmed the entries, another window is displayed (Confirm Write
window), in which you finally confirm (YES) or reject (NO) the creation or overwriting
of the part, or the part and model.
The Confirm Write window displays the following messages if you create or overwrite a
part or part with model:
Creating a PART:
You can only update attribute of an existing part, which are not necessary for
unambiguous identification of the part in the database (s. Chapter 1.8 –Airbus Attribute
Identification). In the A380 and M400DSG environment, the following attribute is a key
attribute: Part ID
For an existing part, these attribute is locked for changes!
· The part, or part and model has/have now been added to the objects list in the VPMA or
has/have been overwritten.
A list field is identified via the symbol. If you click on this symbol, a list with predefined
values for the attribute will open.
A value description for the attributes Model Type and Part Type is
included in the DAP8157.
For the identification of a part the attribute Part ID is used for. The value of this attribute
will be checked depending on the value of the attribute Part Class.For all Parts in the
Environment A380DSGN und M400DSGN who are subject to the AP2610 (Single Parts,
Assemblies design by/for Airbus, Master Geometrie, Space Allocation, Drawings, etc.) the
Parc Class value AIP applies.
Further values for Part Classes are FINs (Functional Item Number) or EQT (Equipments).
Exceptions who are not managed with a Part Class are Standard Parts who are administrated
in theGESTDLIB Environment.
The Attributes Projekt, ATA, Sub-ATA, Sequent Code, Sequent Number, Part Code and
Special Code from the AP2610 will be abstraceted in one value in the attribut Part ID.
Basically there are the following Parts represented in the Part ID: Basic Parts, Drawing Parts
and Extended Parts (for special design cases). For detailed information in terms of these
Parts are found in the following DAPs / DAMs:
Common
DAP8157 - VPM Naming conventions - with EnoviaVPM/CatiaV4
Drawing Parts
DAM8127 - Drawings with EnoviaVPM/CatiaV4
DAM8128 – Assembly drawings with EnoviaVPM/CatiaV4
Extended Parts
DAP8201 – Product structure in EnoviaVPM/Catia V4
Detailed methods for special desing cases like Composites, Fastener, Kinematics, etc.
DB Server Prod. File Server Prod. DB Server Prod. File Server Prod.
caxhhp02 caxhhp01 caxhbp02 caxhbp01
DB Replication
(synchron)
HP HP HP HP
File Replication
(asynchron)
Hamburg Bremen
Locking/Unlocking in VPM
In VPMA you can lock (check out) or unlock (check in)
the access to a part for other users. For this purpose, in the
Parts context menu or in the Tools menu, you find the
Check Out (locking) and Check In (unlocking) functions.
You can only work on a model, if the part associated to
this model is checked out.
The part can usually only be checked in by the person
who checked out the part.
In VPMA via the CO-USER attribute, the status of a part
is displayed (Check In/Check Out). In chapter 6 – User-
Defined Settings, the attributes, which are displayed, are
described.
In PSN, the status of a part is displayed via an icon in
front of the part.
Check Out
In VPMA, select the part that you want to lock. For this case, multiselection is possible, so
that you may lock several parts with one Check Out command.
In the Parts context menu, select Check In. A window is displayed, in which you may enter a
comment and a short description on the Lock type.
Via the Lock Type, you can determine different levels of Locking. However, presently, only
the Lock type "U" is available, with which the part is locked with all its models from the
access of other users.
After you click OK, a new window is displayed, in which you confirm (OK) or Cancel the
Check-Out.
The User-ID of the user who has checked out the part is now allocated to the CO-USER
attribute.
Check In
In VPMA, select the part that you want to unlock. For this case, multiselection is not
possible. If you select more than one part, the Check-In is applied only to the part selected,
which comes first in VPMA.
In the Parts context menu, select Check Out. A new window is displayed, in which you
confirm (OK) or Cancel the Check-In.
After you have confirmed, the following message is displayed:
This message is no error message, but a note. Click OK to close the window.
In this case you can ignore the "Error: 99" message!
The system just indicates a replication that is initiated by the Check-In. This replication is
necessary so that identical datasets of the unlocked object (part or part and model) are
available in the Hamburg and Bremen locations (see. chapter 1.9 – Check-Out for Changes).
As long as the replication is processed, the object data are locked. In this case, the value
"XVPMINTX" is displayed in the CO-USER field. If the replication is finished, the value
"0" (zero) is assigned to the attribute. In VPMA however, this value will only be displayed
after you initiate a new search.
Every night an update from all models (checked in and check out models) between
Hamburg and Bremen will be made (state of march 2002).
Part
The following prerequisites must be given, so that you may delete a part in VPM.
No models shall be allocated to the part
The part shall not be included in any product structure/ PSN (see chapter 2 "Product
Structure")
No higher versions of the part shall exist (see chapter 5 "Version Management")
The part must have the Status/Maturity IWDSG (see chapter 4 "Release Management").
The part must be checked in.
Model
The following prerequisites must be given, so that you may delete a model in VPM.
The model must not have a Multi Model Link (MML) to other models (MML see VPM
Basic Training – Module 2)
The model must have the Status/Maturity IWDSG.
The model must be checked out.
In order to delete a VPM object, select this object in the VPMA. In this case, multiselection
is not possible.
Generally, you cannot restore deleted objects via rollback, undo or other commands.
3. Create&Save-Button selektieren
1. select the
or
Environment
FILE à CREATE&SAVE
· To start CatiaV4, in VPMA, click , or select Toolsà Executeà Catia (or the F9
key).
· If you have selected models in the object list, these will also be called up on starting
CatiaV4.
· Another possibility to load a selected model into CatiaV4 in the VPMA as well as PSN
is that you call up the context menu of a selected model and from this menu select "Open
Model" ( click with the right mouse button on the selected model).
CatiaV4 is now automatically called up in a new window. VPM remains activated, so that
(depending on the operating system) you can switch between the different windows
(CatiaV4 / VPMA/PSN). This is also necessary for working with VPM and CatiaV4.
If you want to close a model opened in CatiaV4, in the same menu select "Close Models".
If you start CatiaV4 via ToolsàExecuteàCatia, you can choose between quick start and
cold start.
these via the icon, in the viewer selection in VPMA. Only models loaded out of the
VPMA are influenced with this setting.
Viewer-selection in VPMA:
Single: All models opened in CatiaV4 are closed, and only the selected model is opened (in
case of Multiple selection in VPM the one selected last)
Replace Active: The active model in CatiaV4 is replaced by the selected model.
Add Active: The model is loaded in CatiaV4 as active model.
3. select a model
Help
Action
Part (in this case selected object)
Model
see Module 02, chapter 2.2 "Querying in the Product Structure", Relation Menu
1.16 Airbus Illustration of the Complete Process for Preparing DEFINITION DOSSIERS
MOD/MP-list
per A/C
create
3D-Models
Create
manage parts, Create Create
derivative administrative ECN
3D-Models and BOM BSB / Parts Usage
2D-Drawing Drawing information
Drawings
Release process
(kick off TAKSY) Archive
Manufacturing,
Distribution engineering drawings and specifications
,…
2 Product Structure
2.1 Objectives
Product Structure
Working in PSN (Produxt Structure Navigator)
Creating a structure / linking objects
Copy & Paste method
Once you have created a part with model, you have already created a small structure. If you
want to view this structure, load the objects in PSN:
· First, select the desired part.
· In order to open the VPMA, click , or the part's context menu select "Open Part", or
double-click on the desired part.
· The PSN with the selected part and its allocated objects is displayed.
2.3 PSN
You will recognize some areas in the PSN (menu bar, help window, viewer selection, etc.)
from VPMA. The new areas are described in the following paragraphs.
Differentiated opening
functions for
of structures
graphical display
2
graphical display
Graphical Display
In PSN, the part, model and document are represented by squares of different colors, in
which diverse, also combined, attribute values of the current object are written.
PART MODEL
Part Name
Version Model Type
Status Sheet No.
Issue Revision
Part Type Status
Description
Link
VPMA
Levels
The structure is divided into levels, and a link connects one level to the next. The models
allocated to one part belong to the same level.
Assemblies
An assembly consists of parts and their models, which constructively form a group. An
assembly represents part of the product structure, in which it can be present multiple times.
In VPM, every part that itself contains parts with their models, is an assembly. In general,
there is however no difference between parts with and without models. This means, that you
can link a model to a part at any time.
Part, representing an
assembly
Links
The individual links between the parts are local links, which are thus only valid between two
levels.
Example 1
If you cut part 2 from its structure, you also cut its complete structure on the lower level.
The links between 2, 4, and 5 are maintained, though. A product structure thus consists of
four local links that may be cut in a product structure, but the following links (in this case 4
and 5) are maintained.
Cut
4
L53E 71234 212
002 00 SOL
2 Part 2 01
L53E 71234 002 00
Sub-Assy
1 L53E 71234 202
002 00 SOL
L53E 71234 000 00 Part 3 01
Assembly 5
L53E 71234 200 00 SOL
Part 1 01
3
4
L53E 71234 212
002 00 SOL
2 Part 2 01
L53E 71234 002 00
Sub -Assy
L53E 71234 202
002 00 SOL
Part 3 01
5
1 3
L53E 71234 000 00 L53E 71234 200 00 SOL
Assembly Part 1 01
Example 2
Furthermore, you can copy parts with their substructures several times, and can paste them a
second (and so forth) time into the structure (copy from 2 and paste in 1).
1. Copy
4
2. Paste L53E 71234 212
002 00 SOL
2 Part 2 01
L53E 71234 002 00
Sub-Assy
1 L53E 71234 202
002 00 SOL
L53E 71234 000 00 Part 3 01
Assembly 5
L53E 71234 200 00 SOL
Part 1 01
3
Cut 4 or 4*
2 4*
L53E 71234 212
002 00 SOL
2* Part 2 01
L53E 71234 002 00
Sub -Assy
L53E 71234 202
002 00 SOL
Part 3 01
5*
4
L53E 71234 212
002 00 SOL
1 2 Part 2 01
L53E 71234 000 00 L53E 71234 002 00
Assembly Sub -Assy
L53E 71234 202
002 00 SOL
Part 3 01
5
L53E 71234 200 00 SOL
Part 1 01
3
If you cut parts from the following structure, this will have an effect on every copy of this
structure. If you cut Part 4 from the structure, this means that Part 4* will also be cut. Thus,
these are only copies (or instances, to be more definite).
next page
2* 5*
L53E 71234 002 00 L53E 71234 002
202 00 SOL
Sub-Assy Part 3 01
1
L53E 71234 000 00 2L53E 71234 002 00 5 L53E 71234 002
202 00 SOL
Assembly Sub-Assy Part 3 01
As for the copy and paste function copies of existing parts are used, no new parts are
created. Physically there is also only one part, although this part may be present in the
product structure several times (and of course also in several structures). The copies of parts
are never exact copies but only links to an original; this helps to save disk space for the
database.
In an extreme case, a large product structure can thus contain only a little number of parts,
but many instances or links.
All physically existing parts are represented in VPMA; the links are not shown here.
A Part could have more than one instance. The number of all instances from a Part is
the summation from all positions from this Part in the product structure.
VPMA PSN
Part Instance 1
Part Instance 3
In VPM, this link is usually obtained via copy, paste, and cut. You find these in the context
1x
VPMA
1x
PSN
In PSN, the created link is marked yellow. Yellow in this case means that the link has not
been written to the database yet. Click to save the changes in the database. After you
have saved the changes, the line color changes to black, which means that the graphical
display and the database content are equal.
Navigating in PSN
In order to navigate within the graphical display, you have the following options:
Duplicate
In PSN you can duplicate a part with its associated links. With this function, a new part is
created with its links to further parts.
If you want to duplicate a part, open the part's context menu and
select .
An "Environment" window is displayed. Here you select the
environment, in which you want to create a part.
In the following Create and Save window, you must define the
part's attributes.
If you only want to duplicate the links to other parts, in the
following window click "Yes". If you click "Duplicate", all
models of the respective part are also duplicated.
The new part is displayed as a list in a new window. From here, you can use Copy & Paste
to paste the part into the structure.
the respective part (1 click ), copy the part, and paste it into the structure in PSN.
Associate Funktion
Further it is possibel to create a Part
or model directly in the PSN at the
selected Part. To create a new object
there are different functions in the
context menue “Associate” from the desired Part:
· New Part ...
A new Part and an Instance from this Part will be created. The Instance is created direcly to
the desired Part.
Firstly ist is necessary to select an Environment where the Part will be created. In the
following Create&Save window the values for the new Part have to be filled in.
· New Model ...
A new Model will be created directly to the desired Part.
In the following Create&Save window the values for the Part are shadowed. So it’s only
possible to fill in the values for the Model.
· (Model from CATIA – Function doesn’t work correct! Never use this function!)
· Model moved from clipboard
An VPM Model will be moved from his originaly Part to the desired Part.
With the function „Copy“ the desired Model in the PSN or VPMA will be copied. With the
function „Model moved from clipboard” started from the desired Part the model will be
linked to the Part and deleted at his previous originaly Part.
It is necessary that both Parts are checked out by the user.
Further You have to mention that the desired Part won’t receive the position matrix from the
originaly Part. In this case normaly the model has a new geometric position.
Replace Funktion
The function enables to replace in the product structure a selected Part with an other. You
can use this function both in PSN and VPMA.
If You start this function in VPMA the Part will be replaced global in all structures. Started
in the PSN only the local selected Part ( the instance) in this structure will be replaced.
In the context menue from the desired Part there are the functions „Replace where used“
(VPMA) and „Replace“ (PSN). The following sub functions enables different methods to
replace a Part:
· From clipboard
Firstly copy the Part You want to replace with. The Part You want to replace will be
replaced global (VPMA) or local (PSN) with the one You copied before.
· Part version ...
If more than one version of a Part exist it’s possible to change the selected Part Version
(global – VPMA or local – PSN) with this function.
· Replace in products – possible only in VPMA
Firstly copy the Part You want to replace with. After executing the function a new window
open where all Rootparts are listed where the selected Part is part of the structure. In the
selected Rootparts the relevant Part is replaced.
VPMA PSN
3. Select a part, to
which a structure
shall be expanded or
modified.
VPMA
6. Select the part, which you want to
position, and then, in the context
menu, click "Copy". or
PS
1x
8. In the part's context menu:
- paste
- paste same position à to paste the part with same 9. save structure
position matrix (XYZ) of the copied part
- paste quantity à select number of times you want to
paste the part.
Save structure
Switch PSN window to active mode, if several PSN windows are opened.
3.1 Objectives
3.2 General
You can explicitly select VPM objects via their attributes present in the database.
You can define a query in VPMA as well as in PSN and refer to one or several attributes.
Simple Query
In the Simple Query a String is queried that is contained the attributes Part Name or English
Description. For a more determined query, only the options "With", "Like", or "=" are
available.
In VPMA, you can start the Simple Query "Search Now".
Intermediate Query
The Intermediate Query option can basically be divided into Part And/Or Model. I.e. the
search criteria must be contained in the Parts and Models, or in the Parts or Models. The
further query aims at attributes that are linked via "And" or "Or functions. You will find a
list of operations for an attribute query in the next figure. If you want to place more than one
query on an attribute, you may duplicate the attribute by clicking , or delete it by clicking
. In the new line, you can define another query on the same attribute.
If you want to query in VPMA, you must define the object type in the Objects menu.
Advanced Query
In case of an Advanced Query a simple database language is used that you must enter via the
keyboard or via the three pull-down menus. These are simple link options.
The Advanced Query offers the most complex possibility to query data. For this application
however, basic knowledge in SQL and/or DB languages are beneficial.
Options
possible via the Zone/ Volume filter function in PSN. Click to start the filter in PSN.
All other functions of this filter are explained in the VPM Basic Training Module 02.
In the Zone /Volume Filter window, activate the Filter method "Filter by identification".
Click on the "Edit Filter" icon to open the Query window, in which you define the query.
The query, like every query in PSN, refers to the opened product structure. A new,
temporary structure is created with the selected objects.
At the moment (march 2002) the function Filter by Identification doesn’t work correct.
4. intermediate query
5. select „Intermediate“
8. Click OK or Apply
result
2. Click "Select
Object", or, on the
3. select PART or
MODEL
4. select „Intermediate“
7. select OK or Apply
result
4 Release Management
4.1 Objectives
4.2 General
For Release Management, the Maturity is used in VPM. For release however, TAKSY will
continue to be the master system.
4.3 Maturity
Parts and models in VPM are have maturity.
It defines the state of development of every
object. Via the maturity, the release
procedure is controlled. You have the
following options in order to change the
maturity.
to demote it.
Via an object's context menu or under
Toolsà Change Maturity, you can directly
select a new maturity.
The last possible maturiy is the „frozen Maturity“ who depends on the objekt (Model or
Part) and the VPM role from the user (DESIGNER or ZONI). To get a object out of the
frozen maturity there is the following function in the contextmenue from the object :
Airbus UtilitiesàLauch demote from frozen maturity
The Issue on Part and Model is explained in detail in DAP8036, "Version Management
for Parts and Models in VPM for the A380 Program".
The following figure illustrates how maturity develops, depending on the working process:
Description
1 Creation of drawing master data (T10Z)
TAKSY VPM/CATIA 2 Determination of drawing schedule (TC60M)
10
Creation of drawing sheet data in TC40Z
CATIA 2D 6 7 Assignment of parts to the CATIA 2D drawing sheets
derivations 11 Creation of gross data (TC37S/38S)
10 12 Creation of ECN. Checking whether drawing and
Drawing administrative data are formally ok. The CATIA parts
sheet data to be released must be in status "RLST2". After
11 8 signing in the field "DRAWN" (TC80Z) initiation of
Gross VPM control phase.
12 data
ECN Meta Files 13 In TAKSY, check of parts participating in the control
Creation data phase (part list issue = drawing issue). Sending check
requirement for every sheet from TC40Z, which
13 participates in control phase, to VPM.
Check phase VPM-DB
TAKSY
(Status 2) Check RLST2
14 Feedback to TAKSY on the check requirements,
and listing the models, which participate in the
15 14 control phase. Software-technical completion of
Check Feedback to
No TAKSY
ECN data
Ok ?
15 Correction of all mistakes, new control phase
Yes 16 16 Completion of signatures in ECN. Initiation of control
Completing ECN
phase ( Status 3) after field "SYSTEM"(TC80Z) has
been signed.
Release phase VPM-DB 17 System check of data. Check and Release
TAKSY
(Status 3) 17
Check RLST2 requirements for the concerned parts and
drawings to VPM.
20 18 18 For every Check and Release requirement, VPM
Check Feedback to
No
TAKSY
returns a result report.
Ok ?
19 19 If drawing and part list data are ok,
VPM-DB the drawing release program sets the status in
Yes 21 RLST3 + ACE Issue TAKSY to 3/3. The status of the models is set to
No more changes possible "RLST3" in VPM. The ACE issue of the concerned
parts and models in VPM is synchronized
automatically , depending on the TAKSY issue.
Released Released
Requiring lists for lists for 20 Correction of all mistakes, new control phase 2
Announcement
BAUVERSY VPM printer ZAMIZ
STL + Graphics
Release 21 Flow of the release procedure. Adjacent systems are
to ZAMIZ
supplied.
5 Version Management
5.1 Objectives
5.2 General
For the version management of parts and models in VPM there are the areas "Revision" and
"Version".
A new version of a part and/or revision of a model is generally created in case the
geometrical data are modified. In such a case the type of versioning depends on the type of
modification. The operating procedure at this point in VPM depends on the procedures
within the company.
The modification procedure is explained in detail and with many examples in the
DAP8036, "Version Management for Parts and Models in VPM for the A380 Program".
6 User-defined Settings
In VPMA, you may via FileàSettings you may adapt user-defined settings. Thus, you have
a few options to modify your own working environment.
In the sub menu Display, you may adjust the settings for the main windows.
In VPMA, if you want to switch off the first column for numbering, deactivate the "Lines
number column" function.
In the Result, Query, Rename and Save sub menu, you can determine attributes and their
order, in which they are displayed in list of the VPMA, Query, Save and Rename window.
In the Open Model sub menu you can adapt all parameters related to opening CAD models
in CatiaV4.
In CatiaV4, if you want to activate another model than the currently active model from one
of the loaded models, you must deactivate the "Lock as passive" function.
In the Relation sub menu, you determine, which environments and how many levels are
queried in case of relation queries.
7 Glossary
A
Attribute Identification – Chapter 1.8
Airbus specific attributes. See also Naming, Numbering.
C
Context menu
Object orientated menu, which is opened by clicking the right mouse button over the
selected object.
Copy, Paste ,Cut – Chapter 2.4
With the Copy, Paste and Cut functions, VPM objects are copied, pasted and cut. The Cut
function can only be applied to objects in PSN.
Check in, Check out – Chapter 1.9
A user may lock/unlock objects so that other users have no access. This procedure is
necessary to make sure that different users do not work on one object at the same time, and
that data inconsistency between Hamburg and Bremen is avoided.
D
Document (not implemented) – Chapter 1.4
Consists of a document file and attributes, which describe this document.
Duplicate – Chapter 2.4
With this function, a part and its associated links are duplicated. From the PSN, a new part is
created with its links to other parts.
E
Environment – Chapter 1.6
In the environment, several settings are fixed (list names, object attributes, etc.). Several
environments can be summarized in one Project.
K
Key attributes
Attributes that are necessary in a database for unambiguous identification of a dataset.
L
ã Airbus Deutschland 2002 Page 64 of 67 02.05.02, 15:42
EnoviaVPM Basic Training – Module 01
Airbus Deutschland
M
Maturity – Chapter 4.1
Degree of maturity of a part or model, via which the release is controlled. There are four
different states of Maturity (IWDSG, RLPUB, RLST2, RLST3).
Meta data, VPM Meta data
VPM Data such as attributes for parts and models, product structures or position matrices
are called VPM Meta data and are saved to the database.
MML – Multi Model Link - Modul 02, Chapter 3
An MML represents a dependency between individual CatiaV4 models (e.g. 2D derivation
of 3D model). An MML is managed in VPM.
Model – Chapter 1.4
Consists of a CAD model and attributes, which describe this model.
N
Naming, Numbering – Chapter 1.8
Regulation for Attribute identification. Based on ABD0004, ABD0036 and AP2610.
O
Overview – Module 02, Chapter 2.1
Gives an Overview over large product structures.
Objects, VPM - Chapter 1.4
VPM Objects are e.g. Part, Model and Document.
P
PSN – Product Structure Navigator- Chapter 2.3
Serves to display/work on a product structure.
Part – Chapter 1.4
VPM object, Describes a component or assembly. Serves as the basis for product structures.
People & Organisation (P&O)
VPM Module for creating and managing roles, VPM users, access rights, etc. Is established
by the VPM administrator.
Q
Query, Simple, Intermediate, Advanced – Chapter 3.1
Query methods in their order of increasing complexity for detailed queries of VPM objects.
R
Release management – Chapter 4
Serves to control the release of parts. The release is controlled via VPM and TAKSY. See
also Maturity.
Relation menu– Module 02, Chapter 2.2
Via the Relation menu in PSN several links of one part to other parts (Parents, Brothers,
etc.) can be selected.
Replication of VPM meta data and models
The VPM meta data and models exist in Hamburg and Bremen. The "compensation" of
these data shall guarantee that in Hamburg and Bremen the same data are available. This
"compensation" is called replication.
Revision – Chapter 5
Serves to manage different modification states of a model. A revision status is defined by a
three-digit number.
Role – Chapter 1.5
Defines rights in VPM, which the user has within an environment (Training, Test,
Production). Roles are assigned via the User ID. It must be chosen by the user before
starting to work with VPM.
VPM meta data are replicated immediately on creating or modifying – CatiaV4 models on
creation – and on Check in/Check out.
Depending on the workload, the replication of models may take a couple of minutes. Meta
data are replicated immediately.
S
Set current – Module 02, Chapter 1.3
With the Set current function from the context menu of a part in PSN this part is selected as
reference tpart for following Positioning.
Settings – Chapter 6
User-defined settings are adapted under FileàSettings.
T
Transformation matrix – see Position matrix
U
User-defined Settings – see Settings.
V
Version – Chapter 5
Serves to manage different modification states of a part. A version status defined by a three-
digit number.
Version management – Chapter 5
Serves to control modifications on VPM objects. Different modification states in VPM are
marked by Versions (part) and Revisions (model).
VPM – Virtual Product Model
VPMA – VPMAccess - Chapter 1.5
VPM objects are displayed in a list.
Z
Zone/Volume Filter – Module 02, Chapter 2.3
With a Zone /Volume Filter objects can be selected in the threedimensional area with VPM
and CatiaV4 VPM .