Teamcenter Enterprise 4.

PRODUCT
DATA
MANAGEMENT
Object Management Framework Usage Training Manual
Object Management
Framework Usage
Table of Contents

Chapter 1: PDM Concepts

1.1 What is PDM?
1.2 Teamcenter Approach to PDM
Chapter 2: Teamcenter User Data
2.1 Object Technology Introduction
2.2 Business Items
2.3 Data Items
2.4 Work Locations
2.5 Organizational Items
Chapter 3: User Interaction with Teamcenter
3.1 Starting a Teamcenter Enterprise Session
3.2 Browser
3.3 Dialog Windows
3.4 Usage Overview – Pulldown Menus
Table of Contents
Chapter 4: Populating the Teamcenter System with Information
4.1 Information: What is it?
4.2 How does information get into the system?
4.2.1 Creating Work Locations
4.2.2 Creating Data
4.2.3 Registering and Unregistering data
Chapter 5: Locating Information
5.1 Introduction
5.2 Query Menu
5.3 Navigation
Chapter 6: Basic Data Manipulation
6.1 Introduction
6.2 Open
6.3 Update
6.4 Edit
Table of Contents
6.5 View
6.6 Get Item Info
6.7 Refresh
6.8 Move
6.9 Delete Item
Chapter 7: Understanding Relationships
7.1 Introduction
7.2 Managing Relationships
7.3 OMF Relationships
7.4 Creating Relationships
7.5 Viewing Relationships
7.6 Hiding Relationships
7.7 Deleting Relationships
Table of Contents
Chapter 8: Sharing Information
8.1 Introduction
8.2 Vaults
8.3 Transfer
8.4 Check Out
8.5 Check In
8.6 Copy
8.7 Freeze
8.8 Revise
 stages

Chapter 1
PDM Concepts
1. PDM Concepts

1.1 What is PDM?

1.2 Metaphase Approach to PDM
1.1 What is PDM?

Enterprise Product Data Management Functions

Product
Configurators
Auditability
Structure Views
Effectivity Planning
Product Structuring
Part - Document Tracking
Component Management
Process Automation
Release Management
Change Control
File / Document Vaulting
Relationship Management
Revision Control
Application Interfacing
1.1 What is PDM?

cover.doc

PN 1000-Rev A plate_assy.asm.1
Attaches
Type: Design
body.doc
PN 2000-Rev A
Type: Specification
Is Described
By glossary.doc
PN 1000-Rev A specs.doc
Type: Specification

Is Described
By

PN 1000-Rev A PN 2000-Rev A PN 2000-Rev A plate.prt.1

Plate Assembly Plate Type: Design

Uses PN 3000-Rev A
Gasket

PN 2000-Rev A plate.mfg.3
Type: Manufacturing

PN 4000-Rev A PN 4000-Rev A screws.doc

Screws Design
1.2 Teamcenter Approach to PDM

Teamcenter Product Modules:

• OMF: Data Management Frame Advanced
Product
• LCM: Workflow, Process Mgmt Configurator

• MC: Change Control Life Object Product

Cycle Management Structure
• DM: Document Mgmt Manager Framework Manager

System
• PSM: Product Definition Services

• APC: Configuration Mgmt

Change
Control
Part
Family
Manager Manager
• PFM: Part Information
• IT: Integrator Toolkit Document
Manager

Integrator
Toolkit
1.2 Teamcenter Approach to PDM

• System Services: User Interface, Operating Systems, DBMS

• Object Management Framework (OMF): Object, Relation Management

• MetaChange (MC): Manage Product Change

• Document Manager: Documents Management

• Life Cycle Manager (LCM): Workflow, Process Management

• Product Structure Manager (PSM): Product Structures, BOM

• Advanced Product Configurator (APC): Configuration Mgmt, Views, Effectivity

• Part Family Manager (PFM): Group Technology

• Integrator Toolkit (IT): Modeling Tools, APIs

 Chapter 2
Metaphase User Data
2. Teamcenter User Data

2.1 Object Technology Introduction

2.2 Business Items
2.3 Data Items
2.4 Work Locations
2.5 Organizational Items
2.1 Object Technology Introduction

To perform their daily work in Metaphase, users access many kinds of

information. Metaphase uses Object Technology to manage this
information. Everything within the Metaphase system maps to an object, that
has a set of defined attributes, characteristics, and behavior.

A class describes the general attributes of an object, acting as a template for

its definition. The implementation of classes in Metaphase is via a table within
a relational database.

An instance of a class is when values are applied to the general attributes of

that class. The implementation of a class instance is via a database record, a
row within the class table.

All classes form a class hierarchy that organizes or groups those classes
that share common attributes, characteristics, and behavior. The higher level
or parent classes share their attributes via a mechanism called inheritance.
2.1 Object Technology Introduction

Items in Teamcenter are objects.

object (specifications, ECN’s, drawings, users, groups etc.... )
SPEC

object
Objects have meta data that
define and describe those objects.
(date of creation, owner, revision, etc.....)

object Objects have

object relationships
object to other objects.
2.1 Object Technology Introduction

User information can be described by the following categories:

– Business Items

– Data Items

– Work Locations

– Organizational Items
2.2 Business Items

Business Items represent the business-related information

about an enterprise’s products such as a product’s revision level.
Business Items do not have any physical representation - they
reside only in the Metaphase database.

Documents are examples of a Business Item.

Document
Documents are used to organize and control product information.
Data items associated with a specific product or part of a product
can be attached to a Document so that they may be managed
together.
2.3 Data Items

Data Items represent the physical data that describe a product.

This data consists of items such as:
– design specifications created within a word processing application
– drawings generated on a CAD system
– test results in spreadsheets
– marketing collateral in hard-copy format

Data Items are usually created by an application and have both a

physical and a Teamcenter database representation.
2.3 Data Items

Examples of OMF Data Items are shown below:

Editable Text File
Represents a file whose contents are editable ASCII text
characters. An editable text file can be viewed or edited with many
different tools on many different computer systems.

Directory
Represents the same concept as a directory on an operating
system. Any action (e.g., move, copy, delete) applied to the
directory affects all of the files and subdirectories contained within
the directory

Note
Represents a “post-it” note concept which allows the user to
provide comments which can then be attached to another object
such as a document.
2.3 Data Items

Aggregate
An abstract concept which represents a group of simple computer
files or directories that must be treated as a single unit. Because of
the application that generated them, the file system items should
not be accessed individually.

Independent Binary File

A simple computer file whose contents are known to be of a binary
format that may be exchanged between various types of computer
systems in a useful manner. A GIF file is an example of an
independent binary file.

OS Dependent Binary File

A simple computer file whose contents are known to be of a binary
format that may not be freely transferred among various types of
computer systems in a useful manner. A compiled program is an
example of an OS dependent binary file.
2.3 Data Items

Non-Editable Text
A text file which is not intended to be edited using normal text
editing tools even though it could be viewed or edited. A PostScript
file is an example of a non-editable text file.

Report
A text file that contains information about Metaphase objects and
relationships.

Paper
Represents a hard-copy item in a file cabinet or on someone’s
desk.
2.4 Work Locations

Metaphase manages file system items such as files and

directories that are owned by users in work locations. Each
work location is associated with exactly one user.

Users can have multiple work locations

– on different hosts
– on a single host to organize data by project, for example

Mywork

User
Penwork
2.5 Organizational Items

Organizational Items are not product data, but are used by

users to organize their work more efficiently.

Examples of OMF organizational items are shown below.

Collection
Collections are used by users to organize items. They form a
logical grouping of items of any type.

Saved Query
A Saved query is not a collection of objects, but rather the
query selection criteria that retrieve a set of objects. Each time a
Saved Query is opened, a query is executed and the objects returned
from the query may be different because objects were added or
deleted from the system.
2.5 Organizational Items

SortPref ColumnPref DbPref DeletePref MovePref ExpandPref

Saved Preference
A Saved Preference contains a user’s preference for a particular
aspect of metaphase behavior. Each time a user double-clicks
on a Saved Preference, the preference is applied to the current
session. There are different preference types for different types
of behaviors.
 Chapter 3
User Interaction with
Teamcenter
3. User Interaction with Teamcenter

3.1 Starting a Teamcenter Enterprise Session

3.2 Browser
3.3 Dialog Windows
3.4 Usage Overview - Pulldown Menus
3.1 Starting a Teamcenter Enterprise Session

The omf command launches a Teamcenter session.

The following options may be specified:

– omf - starts Teamcenter with no options
– omf -u <user name> - starts Teamcenter as the specified user
Example: omf -u Joe
–omf -b <browser font> - uses the specified browser font
Example: omf -b large
– omf -d <dialog font> - uses the specified dialog box font
Example: omf -d large
– omf -l <locale name> - uses the specified local language
Example: omf -l en_us
– omf -h - prints out the entire help/usage message
3.2 Browsers

Browsers are used for viewing objects, navigating relationships, and

initiating actions to manipulate objects and relationships.
Title

Menu Bar

Status Area View Area

3.2 Browsers

Home Collection
– First browser displayed to the user
– Items created in the Home Collection remain in the Home Collection
for all subsequent sessions unless removed by the user
– File menu displays Exit
3.2 Browsers

Home Collection
The Home Collection contains default start-up objects for all users.

Startup Preferences
This is a special type of collection that is created the first time a user logs
in. It is initially empty, but can be used to specify the preferences a user
wishes to be applied to a session when it is started.

my work items
This is a saved query that is created the first time a user logs in. Opening
this saved query returns all objects owned by that user.

work collection
This is initially an empty collection that is created the first time a user logs
in. It can be used to organize a user’s current work items.
3.3 Dialog Windows

Dialog Windows
A window or form that is shown to the user, typically to either
display detailed output or gather detailed input.

The following dialog window is displayed when a user wants to

create an editable text file:
3.3 Dialog Windows

Common Buttons

OK Executes the action and removes the dialog window.

Apply Executes the action and the dialog window remains open.

Save...
Creates a Saved Query on query dialog windows or a Saved
Preference on a preference dialog window.

Recall Refills the dialog with the last selections executed or saved entered.

Clear Clears the contents of every editable field.

Cancel Exits the dialog without completing the action.

Help Gives descriptive information about the current dialog window.

3.3 Dialog Windows

– Dialog window entry fields have list buttons when multiple

choices are available
– If a button label has an underlined character, pressing the Alt
(or meta) key along with the underlined character activates the
button
List
Button
3.4 Usage Overview – Pulldown Menus

A typical browser has the following menus:

 menus are activated by depressing the left mouse button on

the menu desired
 mnemonics allow quick access to the menus without use of
a mouse
 To display a menu, press the Alt (or meta) key and the

underlined character
 To choose an option from the menu, press the option’s

underlined character
3.4 Usage Overview – Pulldown Menus

The options displayed on each menu depend upon:

 The application modules that are installed
For example, the LCM Work List option only appears on the Window
pulldown menu if the Life Cycle Manager module is installed
 The rules for the user
Rules can be written so that a given user may only view objects; therefore,
the Edit option is not displayed for that user.

Some options may be “grayed-out” depending upon:

 The type of object selected
This is most specifically for the Action menu. For example, collections
cannot be copied. Therefore, selecting a collection and displaying the
Action menu shows Copy as gray-shaded. This means the user cannot
perform this action.
3.4 Usage Overview – Pulldown Menus

File Menu

 Change Host and Directory allows a user to specify the host and directory
where file system operations will occur
 Page Setup sets printing values such as paper size and orientation
 Print Contents prints the entire contents of a window
 Print Window prints the visible portion of a window
 Select All selects each item in the browser
 Remove From Window removes the selected object(s) from the browser
 Close Window closes the current browser
3.4 Usage Overview – Pulldown Menus

Action Menu

 the Action menu displays options which manipulate metaphase data

3.4 Usage Overview – Pulldown Menus

Info Menu

 the Info menu displays options which allow a user to display or update
information about data managed by Metaphase
3.4 Usage Overview – Pulldown Menus

Create Menu

 the Create menu displays the types of data a user can create in Metaphase
3.4 Usage Overview – Pulldown Menus

Query Menu

 the Query menu allows a user to locate different types of information stored in
the system. These queries present a dialog window to further define the
selection criteria.
3.4 Usage Overview – Pulldown Menus

Window Menu

 A New Object Browser is an empty browser. Open one when you do not
want to create items and have them remain in the Home Collection
 Choosing Browse Selected Items opens a new browser containing only the
selected items. Use this option to work with a smaller number of items than
are displayed in the current browser
 Choosing Collect Selected Items creates a new collection containing the
selected objects
 Launch Tool allows a user to specify options in a dialog box before launching
a selected tool
3.4 Usage Overview – Pulldown Menus

Options Menu

 Change password allows a user to change his/her Metaphase password

 Change User Profile allows a user to change personal information, Email
address, and whether the user accepts objects transferred from other users or
vaults
 Change Preferences allows a user to change preferences for the current
session and create saved preferences. The OMF preferences are:
 Database
 Item Delete
 Item Movement
 Expansion Level
3.4 Usage Overview – Pulldown Menus

View Menu

The View menu allows a user to change:

 the displayed view
 browser preferences
3.4 Usage Overview – Pulldown Menus

View Menu

– Icon View displays large icons, which makes specific objects

easier to locate and to drag and drop onto other icons\

– List View displays detailed information about each object

including its relationships

– Tree View is used to graphically navigate relationships

The left side of the window displays an overall view of all objects
3.4 Usage Overview – Pulldown Menus

View Menu
– Change List View Columns allows a user to specify the attributes
and column widths for the column headings in the list view browser
– The settings may be applied to the current browser or saved for future
use

 Column titles can be changed by entering new strings in the lower bar.
 Columns can be added, removed, or replaced by following the options in
the popup for each column.
 Click OK to apply or Save… to save and name this preference.
3.4 Usage Overview – Pulldown Menus

Help Menu
– Provides Help to the user in various categories.
3.4 Usage Overview – Pulldown Menus

Help Menu
– Session Information displays information about the user and host
which launched the Metaphase product.

– General Help displays information about the current browser

window.

– Menus displays information about the menus on the current

browser window.

– Product Information displays the Metaphase version number and

copyright information.

– Online Manual allows a user to search any manual for a specified

topic.
 Chapter 4
Populating the Metaphase
System with Information
4. Populating Teamcenter with Information

4.1 Information: What is it?

4.2 How does information get into the system?
4.2.1 Creating Work Locations
4.2.2 Creating Data
4.2.3 Registering and Unregistering data
4.1 Information: What is it?

Metaphase manages all product data such as:

– Part Information
– Process Plans
– Printed documents
– Electronic CAD drawings and models
– Design Engineering Specifications
– Manufacturing Specifications
– Technical Publications
– Configuration Management Information
– Bill of Material & Parts Lists
– ECPs (Engineering Change Proposals)
4.2 How does information get into the system?

DATABASE \\users\pdm\work1\dwg

Business Items are purely metadata

/usr/pdm/work/design

Data Items consist of both

metadata and physical data

/usr/pdm/work/analysis

Offline Items
4.2.1 Creating Work Locations

Teamcenter uses work locations to store online items such as files

and directories that are owned by users.

– To create a new Work Location choose Create ---> Work Location

4.2.1 Creating Work Locations

Tips on Creating Work Locations:

– The Work Location Name can be any name which is unique
for the user
– The Full Path of the work location must be a sub-directory of
a user’s home or of the root directory
– If Accept Transfers is selected, other users may be allowed to
transfer file system items to this work location
– The OS Permissions for Transferred Files specify the
permissions applied to files copied, moved, or transferred to
this work location. Not all permissions apply to all platforms
– If the specified directory already exists, Metaphase registers it;
if it does not exist, Metaphase creates that directory
– Once the work location is created, a user may access it from
the host where it was created and from any other hosts that are
members of the same host group as the original host
4.2.1 Creating Work Locations

The following steps occur when a user creates data:

Step 1  Present Dialog to user to gather information

This step allows the user to add the proper data descriptions.
The attributes displayed in these dialogs will vary based on the type of data
created.

Step 2  Store the information about the data in the database

Step 3  Create the actual data in the case of file system data
Only Data Items exist as bulk data on a file system.

Step 4  Display the user’s data in the current browser window

4.2.2 Creating Data

Creating and registering data makes the user the owner of the data

A file system item created by a user is owned by that user and is

mapped to a physical directory called a work location.

Each user may have multiple work locations for bulk data. Only file
system items are mapped to work locations.

DP 101

creates owned by
Ray

Work Location
creates located in for Ray DP
101.doc
Ray DP 101 DP 101

DP 101.doc
4.2.3 Registering Data

Information may already exist electronically

Stored in a
Marketing Work Location
on a PC

Choose Register
Select Text File
via Action Menu
Spec 101
Work Location Spec 101
Database

 Registering data allows it to be managed by Metaphase

4.2.3 Registering Data
4.2.3 Unregistering Data

It is possible to remove a File System item (File or Directory)

from the Metaphase database, without deleting it from disk, by
selecting the item and choosing:
 Chapter 5
Locating Information
5. Locating Information

5.1 Introduction
5.2 Query Menu
5.3 Navigation
5.1 Introduction

Database

Dialog Window Browser Window

5.1 Introduction

The items displayed to any user locating data depend on the

following:
– access to objects as determined by rules
– the user’s database scope
– the application modules that are installed

Scope of items:
• Items are retrieved from the database in the user’s current scope
• A user’s scope is usually the local user database
• The scope can be changed through the Database preference

Change Database Preference:

Options  Change Preferences  Database

5.2 Query Menu
5.2 Query Menu

• Pulldown displays all items that rules allow the user to query
• Pulldown is dependent on Application Modules that are installed,
including customizations
• More Classes --> allows the user to span the criteria across classes
• A dialog is always presented to further the selection criteria
• Pressing Save… on a query dialog allows the user to Save the query
for quick access of frequent queries. The results of this saved query
may change if the objects and/or their attributes change. The saved
query icon will be displayed in the Home Collection for the user.
• A query browser is displayed presenting the resulting objects
• Users may stop large queries before they complete by pressing the
Stop button on the progress window.
5.3 Navigation

Navigation allows the user to locate objects through relationships using

list view or tree view

Navigating relationships is accomplished by:

1. Selecting the object
2. Depressing the right mouse button
3. Choosing Expand Relationship or Expand Multiple Levels
4. Choosing the desired relationship

If Expand Multiple Levels is chosen, the number of levels in the

expansion can be changed through the Expansion Level preference.
5.3 Navigation
 Chapter 6
Basic Data Manipulation
6. Basic Data Manipulation

6.1 Introduction
6.2 Open
6.3 Update
6.4 Edit
6.5 View
6.6 Get Item Info
6.7 Refresh
6.8 Move
6.9 Delete Item
6.1 Introduction

What does it mean to use an object ?

 Look at the object
 Change information about the object
 Change the actual object
 View the object
 Learn information about the object
 Move the object to a new location
 Remove the object from the system
6.2 Open

To open an object means the user wants to look at the data.

Double-click opens an object. Looking at different types of
objects results in different actions or methods to be called.

For example, Opening a:

– Document displays the Update Document dialog window
– Text File launches the editor
– Collection displays a browser containing the contents of the
collection
– Saved Query displays a browser with the requested objects
– Saved Preferences applies the preference
6.3 Update

– To Update an object means to change the database information

about the object
– Update can be done with double-clicking on some objects
– Updating an object displays a dialog window containing the
attributes of the object. The attributes displayed depend on the type
of object selected.
Note: Attributes which make
an object unique cannot be
changed through update.
Copying the object allows a
user to set these attributes as
desired

Updating a text file means changing attributes of the text file -

not its contents
6.4 Edit

 Editing a Saved Query means changing the selection criteria of the query
 Editing a Saved Preference means changing the behavior of the
preference
 Editing a Text File means changing the physical contents of the file
 Edit is not available for all objects (eg, Document )
6.5 View

 Viewing the following items means looking at then in a read-

only mode:
 Text files
 Saved Queries
 Saved preferences
6.6 Get Item Info

Selecting an object, depressing the right mouse button, and selecting

Get Item Info displays read-only information about an object.
No change to the object occurs with this function.
6.6 Get Item Info

The information presented:

– Name
– Creator
– Revision
– Sequence
– User/Vault
– Project Name
– Life Cycle State
– Description
– Title
– Creation Date
– Database Name
– Work/Vault Location
– Full Path
6.7 Refresh

Selecting an object, depressing the right mouse button, and selecting

Refresh queries for the latest information about an object and updates
the browser. Use this option when
– Working on data in more than one browser
– Keeping browser windows open for extended periods of time
– Multiple users are working on the same object

• Get Item Info does an automatic Refresh

• Setting the Automatic Refresh? toggle on the Database preference
dialog window causes objects to always be refreshed when selected
for an action. The benefit of setting this option is that you do not
have to manually refresh the object if needed. The drawback of this
setting is that objects are refreshed whether they are out of date or
not, which may slow performance.
6.8 Move

• Only file system items require this action because of their

physical status
• Dragging file system item icon and dropping it onto the icon of
a directory or of a work location moves the item
Source Destination

Mywork Penwork

DP 101.doc

DP 101.doc

 The user must be the owner

 The destination must also be owned by the user
6.8 Move

• If the file system item already exists, Metaphase generates a

unique name for the item
• When a directory is moved, all components are also moved to
the new owner and relative paths of the components
maintained
Source Destination

Mywork Penwork

DP 101.doc DP 101.doc

 Useful for renaming file system objects

6.9 Delete Item
6.9 Delete Item

• Removes an object from the database

• Removes any physical file system items unless the object is a
work location or a vault location
• Users may only delete objects they own
6.9 Delete Item

If a user wishes to be prompted before deleting a directory, the

Delete Preference can be used.

 Press OK to apply the preference to this session

 Press Save… to create a Saved Preference to be applied to future sessions
 Drop the Saved Preference into the Startup Preferences collection to
apply it at the beginning of each session
 Chapter 7
Understanding Relationships
7. Understanding Relationships

7.1 Introduction
7.2 Managing Relationships
7.3 OMF Relationships
7.4 Creating Relationships
7.5 Viewing Relationships
7.6 Hiding Relationships
7.7 Deleting Relationships
7.1 Introduction

Understanding Relationships

 Managing Relationships

 OMF Relationships

 Creating Relationships

 Viewing Relationships

 Hiding Relationships

 Deleting Relationships
7.1 Introduction

What makes relations valuable?

Users and applications create individual objects, but

relationships give Metaphase the power to organize and
share product data.

The following sections give an overview of the relationships

available in OMF.
7.2 Managing Relationships

material
specification

top design
component document
CAD/CAE

bottom publications
assembly
component document
Cost

tooling mfg
assembly document
NC
Code
7.3 OMF Relationships

Attach
– Relationship between a Business Item and Data Items
– Used to organize several Data Items that pertain to the same
product

Engineering Spec

physically represented by

Sprocket

Sales Brochure

CAD Model
7.3 OMF Relationships

Attach
– Business Item Attaches Data Items
Antenna Report

Antenna
Antenna - DWG
A att
1

Antenna - MFG

 Data Items Is Attached By Business Item

Antenna - MFG Antenna

attBy A
1
7.3 OMF Relationships

Dependency
– Relation between any two Work Items (Business Items or Data
Items), indicates that one object depends upon another object

Document Depends On Note

Antenna Quality Issue

A dep
1

Note Is Depended On By Document

Quality Issue Antenna

depBy A
1
7.3 OMF Relationships

Application Dependent
– Relation between file system items (files or directories), indicates that
one item references another item within an application
• Example is a text file that contains a reference or a link to a
graphic file such that the text file depends on the graphic
whenever it is used
– Usually created by application interfaces, but can be created by users

Text File App Depends On Note

sprocket sprocket.dwf
1 apDep 1

Graphics File App Is Depended On By Text File

sprocket.dwf sprocket
aDpBy 1
7.3 OMF Relationships

Work Location Contains

– Relation between a work location and the registered and non-
registered files and directories in it
A Work Location Contains files and directories
Antenna - MFG

pdmWork CurrentWork
has

DP 101.doc

Text file Is In Work Location

Antenna - MFG pdmWork

in
7.3 OMF Relationships

Directory Contains
– Relation between a directory and the registered and non-
registered files and directories in it
Directory Contains files and directories

Sprocket Spec
1
Project111
1 has
TestResults
1

Text file Is In Directory

Sprocket Spec Project111

1 in 1
7.3 OMF Relationships

Collection Relation
– Relation between a collection and the items contained in the collection

Work Collection Contains objects and is in the Home Collection

Antenna
A

Antenna Inst

Antenna - DWG
has

Antenna - MFG
work collection
Quality Issue

Home
in
7.3 OMF Relationships

Revised
– Relation between Business Items
– Indicates that one object is a revision of another object. The
revised object is now superseded.
Document A Is Superseded By Document B
(Document A Is Revised As Document B)

Metaphone2 Metaphone2
A revAs B

Document B Supersedes Document A

(Document B is Revision Of Document A)

Metaphone2 Metaphone2
B revOf A
7.3 OMF Relationships

Check Out
– Relation between Work Items (Business Items or Data Items)
– Indicates that an object has been checked out from another
user or a vault. The predecessor object is now superseded.
Text File Is Superseded By Text File
(Text File Is Checked Out As Text File)

Antenna - DWG4 Antenna - DWG

co As

Text File Supersedes Text File

(Text File is a Check Out Of Text File)
Antenna - DWG Antenna - DWG4
co Of
7.3 OMF Relationships

Copied
– Relation between Work Items (Business Items or Data Items)
– Indicates that an object was originally copied from another
object
– Used to track the original item or to determine who has copies
of something in order to notify them of changes
Text File Is Copied As Text File
Antenna - MFG Copy of MFG
cpyAs

Text File is Copy Of Text File

Copy of MFG Antenna - MFG
cpyOf
7.3 OMF Relationships

How do relationships get created?

 Drag and drop on icon
 Drag and drop on window
 Application interfaces
7.3 OMF Relationships

Drop on Icon

Some OMF Relationships are created using drag and drop on icon:
1. Select an object
2. Drag the pointer over the object icon that you wish to create the
relationship to
3. Release the left mouse button

Hint: When working with a large number of objects, remember to use the
Browse Selected Items menu option to make the drag and drop on icon
operation easier.

The following OMF default relationships can be created in this manner:

• Business Item Attaches Data Item
• Collection Contains Object
• Directory Contains File System Item
• Work Location Contains File System Item
7.3 OMF Relationships

Drop on Window

All OMF Relationships are created using drag and drop on window:
1. Select an object
2. Press the right mouse button
3. Choose Edit Relationship
4. Choose the relationship you wish to create or modify and a
relationship browser will be displayed
Note: The browser title is very important here
5. Select the object(s) you wish to create the relationship with
6. Using the left mouse button, drag the object(s) onto the
relationship browser and release the left mouse button
7.4 Creating Relationships

Application Interfaces
– Depending on the level of integration that is done, application
interfaces can automatically create relationships for you

User Actions
– The following relationships are not explicitly created by users,
but rather by OMF as the result of user actions:
• Is Revised As/Revision Of
• Is Checked Out As/Check Out Of
• Is Copied As/Copy Of
• Is Shadow Copied As/Shadow Copy Of
7.4 Creating Relationships

Creating the Depends on Relationship

7.4 Edit Relationships

Dragging the Quality Issues Note onto this relationship

browser displays the following:
Note: The browser title is very important

Quality Issues

Only one Drag and Drop on Icon relationship can be defined

as the default between objects. Therefore, because of all the
relationships available in Metaphase, the relationship
browser becomes necessary.
7.5 Viewing Relationships
Depends on the browser view

Icon View
Right click  Show Relationship presents a new browser displaying
the items that have the specified relationship with the selected item
7.5 Viewing Relationships

Resulting relationship browser

Note the title of the Browser

7.5 Viewing Relationships
List View and Tree View

Right click  Expand Relationship displays the items that have the
specified relationship with the selected item in the same browser
7.6 Hiding Relationships
To hide a relationship expansion that you no longer wish to view:
Highlight the relationship object using the right mouse
button, select Hide Relationship
7.7 Deleting Relationships
When a relationship is no longer useful, the relationship may be deleted by:
1. Selecting the object from an Edit Relationship browser or
selecting an object on the right side of the relationship.
2. Choose Action  More Actions  Delete Relationship
 Chapter 8
Sharing Information
8. Sharing Information

8.1 Introduction
8.2 Vaults
8.3 Transfer
8.4 Check Out
8.5 Check In
8.6 Copy
8.7 Freeze
8.8 Revise
8.1 Introduction

Sharing information using a PDM tool supports increased

productivity and concurrent engineering

Issues faced when sharing data:

• Who can change the data?
• Who owns the data?
• What happens when multiple users attempt to access the data
at the same time?
• Where should the data be stored so all users can access it?
• How can users prevent changes from being made to data?
• What if a user needs to change data that has been “frozen”?
8.2 Vaults

Every Business Item and Data Item is owned by “someone”. When an

object is created it is owned by a user. When a user no longer wishes
to control the object, it is usually placed in a vault. Once an object is
placed in a vault it becomes owned by the vault.

Vault
A vault is a secure place for storing and sharing information. Both
Business Items and Data Items may be stored in a vault. A vault
is not a directory but an owner of objects that may span many
machines.

Vault Location
A vault Location contains files and directories and provides the
mapping between the objects the Vault owns and file system
locations. When a Data Item is placed into a vault, its files must
be placed into one of the vault locations associated with the vault.
8.2 Vaults

Vaults and Users contain locations for file and directories

Vault

Vault Location Vault Location

User
Work Location
8.3 Transfer

Transfer changes ownership of an object

Vault

Transfer

User2
User1
Work Location
Work Location 1 for User2
1 for User1

Transfer 2
8.3 Transfer

• Vault owns all items transferred to it

• File system objects must be stored in a vault location

transferred
to
sto
re d
es in
e at
cr Doc 1
Vault

Joe cr Database
ea in
tes
tor ed
transferred s
to
1
Text File Vault Location
8.3 Transfer

Non-File Systems Items

 Some or all attached data items may optionally be included

when transferring business items
8.3 Transfer

Files and Directories

 If Include Application Dependent Items? Is selected,

items with an Application Dependent relation to the selected
object are also transferred
8.3 Transfer

Files and Directories

– If Maintain Directory Structure is selected, the
path relative to the original Work/Vault Location is
maintained for file system items (intermediate
directories are created as needed)

Source Destination

Transfer
8.3 Transfer

Files and Directories

– If Maintain Directory Structure is not selected, the
item is transferred directly to the specified work/vault
location

Source Destination

Transfer
8.3 Transfer

Files and Directories

– When a directory is transferred, all components are also
transferred to the new owner and relative paths of the
components are maintained
Source Destination

Transfer

 Location Selection Rules are used to determine possible destination

Work/Vault Locations for file system items
 Names of file system items being transferred to a vault are randomized if the
Randomizes File Systems Names flag on the destination vault location is
set
8.3 Transfer
• Multiple items may be transferred at the same time
• Objects may be transferred to a vault or to a user
– If the destination is a user and the object is a non-file system
item, the Accepts Transfers flag must be set on the destination
user
– If the destination is a user and the object is a file system item,
the Accepts Transfers flag must be set on the destination work
location
Accepts Transfers?
metauser Change User Profile

Work Location
Doc2

Directory Text1 Accepts Transfers?

Doc1 Update Work Location
8.4 Check Out

Copy with Interlock

Vault

DP 101
1
Copy

Check Out User2

User1

Work Location Work Location

for User1 for User2
DP 101
DP 202 2
1
8.4 Check Out

• A Check Out relation is created between the original (predecessor)

and new (successor) item
Sprocket Sprocket
A co As A
1 2

 Check Out is used to create a working sequence of an existing object in

order to make minor changes and eventually replace the existing Business
Item when the successor is checked in. When it is checked out, the
predecessor object will be marked superseded so that it cannot be modified.
 Objects may be checked out from a vault or from another user
 The successor object has the same name and revision as the predecessor,
and the sequence is incremented by 1
 Multiple items may be checked out at the same time
8.4 Check Out

Non-File System Items

 Some or all attached data items may optionally be included

when checking out business items
8.4 Check Out

Business Item Test4 Document and attachments are checked out

Document Test4, A,2 and Test4 Text File seq 2 are the successors
8.4 Check Out

Metaphase creates a Checked Out As relationship between

the (predecessor) Test4, A,1 and the (successor)Test4,A,2c
8.4 Check Out

Document Check-In/Out, A,1 is the predecessor and

attachments are not checked out

Document Check-In/Out, A,2 is the successor

8.4 Check Out

Files and Directories

– If Check Out/Copy Type is set to Maintain directory
structure, the path relative to the original Work/Vault Location
is maintained for file system items (intermediate directories are
created as needed)

Source Destination

Check Out
8.4 Check Out

Files and Directories

– If Check Out/Copy Type is set to Create directly under Work
Location, the item is checked out directly to the specified work
location

Source Destination

Check Out
8.4 Check Out

Files and Directories

– If Check Out/Copy Type is set to User specified structure,
the checked out item is placed in the directory specified in the
Destination Directory field

Source Destination

Destination
Check Out Directory
8.4 Check Out

Files and Directories

– When a directory is checked out, all components are copied to the
new owner and relative paths of the components are maintained
Source Destination

Check Out

 When the name of the predecessor file system item is not compatible
with the operating system where the successor will be located, the
physical name of the successor is modified. The original name and
path format are stored in the database (Working File Name and
Working Path Format) are used to restore the physical name when
the file system item is checked in.
8.4 Check Out
Effect on Related Items
– Some or all attached data items may be optionally checked
out when checking out business items
– The successor item has attach relations with all attachments of
the predecessor
– The successor item is dependent on the same items as the
predecessor

Predecessor Sprocket, A,1 depends on Comments

Sprocket
Comments
A dep 1
1

Successor Sprocket, A,2 depends on Comments

Sprocket
Comments
A dep 1
2
8.5 Check In

Changes Ownership
Vault

Vault Location

Vault Location

Check In Check In
Check In

Work Location
User Text File
Directory
Document
8.5 Check In

• Objects do not have to be checked out to be checked in.

– Check In transfers an object to a Vault or User if the item is not
checked out
– If objects are checked out, they are checked in to the same
place from which they were checked out
• Check in Mode determines whether predecessor is retained
– Check in Replace for Users
– Can be checked In No Replace, Replace, or No Check In
Allowed for Vaults
• Business Items by default are replaced unless the original is
frozen
• Data Items follow the Check In Mode of the Vault/User of the
predecessor (If the predecessor is frozen, No Replace is used)
• Multiple items may be checked in at the same time
8.5 Check In

Effect on Related Items

Some or all attached data items may be included when checking
in business items. Document Test4, A,2 is checked out
including attached Data Item.
8.5 Check In

Check In - Business Item - Original is Frozen

Vault

1 2

Document
Document

Copy Check In
Check Out

2
Work Location Work Location

User1
User2
8.5 Check In

Check In - Business Item - Original is Not Frozen

Vault

1 2

Check In
Copy
Check Out 2

Work Location Work Location

User1 User2
8.5 Check In

Check In - Data Item - Original is Frozen

Vault
1 2

File File

2
Check In
Check Out
Copy

Work Location
Work Location

User1 User2
8.5 Check In

Check In - Replace - Data Item - Original is Not Frozen

Vault
1 2

Check In
Check Out 2
Copy

Work Location
Work Location

User1 User2
8.5 Check In

Check In - No Replace - Data Item - Original is Not Frozen

Vault
1 2

File File

Check In
Check Out 2
Copy

Work Location
Work Location

User1 User2
8.6 Copy

• Copy is used to create a new working version of an existing object

• When any object is copied, the database information about that
object is copied. When a file system item is copied, both the
database information and the physical item are copied
• A Copied relation is created between the original (predecessor) and
new (successor) item

Copy of FEA Antenna - FEA

cpyOf

 The successor object has a new name, and the revision and sequence
are reset to their initial values
8.6 Copy

• Path relative to the original Work/Vault Location is determined by

the Check Out/Copy Type and Destination Directory values for
files and directories

 When a directory is copied, all components are also copied to the new
owner and relative paths of the components are maintained
8.6 Copy

Effect on Related Items

– Attachments are not maintained from the predecessor to the
successor because a data item can be attached by only one
business item
– The successor item is dependent on the same items as the
predecessor
– Derive relationships with the predecessor are not duplicated
with the successor
8.6 Copy

Document Antenna, A,3 is the predecessor

att Antenna.dwg

Antenna
Antenna Note
A dep
3

Antenna
co Of A
2

Document Antenna Copy, A,1 is the successor

Antenna Note
dep
AntennaCopy
A
1 Antenna
cpyOf A
3
8.7 Freeze

• Data that has reached a point in the product cycle where it can no
longer be changed is ready to be “frozen”
• Business Items and Data Items are Frozen
• Freezing prevents modification and deletion unless the
administrator has modified the condition
FrozenManipulationAllowed to allow it
• A Business Item and all of its attachments must be in the same
vault in order to freeze the Business Item
• Multiple objects may be frozen with a single action
• Effect on Related Items
– Dependent items must already be frozen
– All attachments are frozen when an attaching business item is
frozen
8.8 Revise
• Once a business item has been frozen and changes need to be
made, the revise action is used to create a new revision that can be
updated
• The new revision is owned by the user
• A Revise relation is created between the original (predecessor) and
new (successor) item
Metaphone2 Metaphone2
A revAs B

 The successor object has the same name as the predecessor, the sequence
is reset to the initial value, and the revision is incremented by one
 Effect on Related Items
 The successor item has attach relations with all attachments of
the predecessor
 The successor item is dependent on the same items as the
predecessor
8.8 Revise

Document Antenna, A,2 is the predecessor

Antenna.dwg
att
Antenna
A
2 Antenna Note
dep

Document Antenna, B,1 is the successor

att Antenna.dwg

Antenna
Antenna Note
B dep
1

Antenna
rev Of A
2