Teamcenter Engineering Basics and Structure

Management Overview
Amy Strucko
Teamcenter Product Management
PLMWorld 2006

Overview

Object Management

Revisioning

Part Management

Structure Management:

Effectivity Management / Incremental Change

Configuration Context

Variability Management

Supersedure / BOM Compare

Where Used / Where Referenced

UGS Corp. 2006. All rights reserved.

UGS Confidential

Product Lifecycle Management

A Product is the
sum of its
life cycle process,
and not its
manufactured
parts.
B. Huthwaite

UGS Corp. 2006. All rights reserved.

UGS Confidential

Object Management
f

Items are objects representing the logical control items for the
Customer
X

Revision control

Workflow

Release Status

Unique IDs

X
X

Manage datasets

Document

Module

Document

Component

Assembly

Change Request

Structure

Datasets represent bulk data

X

Datasets can encapsulate one or more files

Files point to physical file system

PDF File

Word File
UGS Corp. 2006. All rights reserved.

UGS Confidential

CAD Drawing
4

Revisioning
f

A key element to Configuration Management is the ability to

manage multiple iterations of an item as it evolves over time.
Some iterations may be important to preserve and may
trigger key business processes. Others are work in progress
and can be discarded

Iteration schemes include the ability to check-in and out an

item therefore producing multiple versions and to freeze/
release and then revise an item at key business stages
producing multiple revisions

In a product structure, the validity of each revision is defined

according to configuration rules such as effectivity. The
structure can be filtered for the appropriate revisions by
applying Configuration Context (e.g. revision effectivity,
release staus, latest/working etc)

UGS Corp. 2006. All rights reserved.

UGS Confidential

Teamcenter Engineering Data

Folder

Database

381-Pen Cap

Metadata Physical
Volume
data
Volume

Volume

Item
381-Pen Cap/A

Item Revision
Form : Item Rev Master

Specification
Relation

Dataset : UG Master
Dataset : UG Part

Manifestation
Relation

Dataset : Direct Model Dataset

Dataset : Text

BOM View
Revision Relation

BOMView Revision

files
cap_model.prt

cap_drawing.prt
cap_image.jt
Text describing
the cap design

cap_spec.txt

PSE
17.An
Summary
Navigator
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
A
Another
Item
Items
Engineering
and
As
Other
The
Whereas
It
When
pen
separate
also
item
example
such,
revisions
association
consist
cap
types
is
a
BOMView
possible
contains
must
revision
useful
user
the
TC
is
items,
dataset
of
an
of
application
have
of
Engineering
contain
wants
a
dataset
data
change
example
one
master
to
dataset
data
item
data
revisions:
have
at
isor
found
to
used
least
which
data,
revisions,
has
is
more
view
objects
isdatasets
is
in
of
one
aprovides
with
the
one
for
in
which
an
principally
special
representations
describes
the
revisions.
Navigator
with
the
item,
UG
an
revision.
(containers
contents
forms
you
for
drawing
an
item
Master
a
form
because
text
.jt
clear
see
forms
and
aItem
revision
include
image
In
part,
that
files
of
the
solid
file,
this
for
aof
all
to
Teamcenter
contains
metadata,
the
most
data
e.g.
make
revisions
case,
item
model.
cap_drawing.prt
file
and
datasets
distinction
dataset,
is
folders
EC
product
defined
for
processes)
Office
datasets.
models,
revisions
you
when
one,
lightweight
for
In
structure.
aare
need
are
this
using
named
between
organizing
documents
you
the
drawings,
abstract
the
case,
Forms
have.
and
need
containing
pen
relations.
most
representation
reference
work
physical
a
cap
Itdata
contain
data...
data,
part
can
(Word,
important
specs
is
with
The
such
forms
file
created,
contain
ais
data
additional,
dataset
on
Excel,
called
used
two
as
asuch
concept
of
stored
daily
ainformation
significant
an
the
to
spec
etc).
represents
as
fetch
initial
part
bases.
non-TC
on
the
in
outlining
Usually,
one
TC
in
the
ones
PV.
or
a
important
of which
the
item
revision.
Metadata
requirements
revision,
Engineering,
such
cap_model.prt
these
more
physical
are
Engineering
specification
as
volumes
datasets
production
file,
data.
/A
Change
is
stored
because
company-specific
and
Eg
and
also
will
(important
visualization
ais
contain
abstract
cost,
on
created.
UG
Order
these
amodel
volume.
material
supporting
checklist...
dataset,
metadata
are
of
describing
information,
used
aand
The
part
locked
stored
to
ERP
information,
volume
inmanage
what
PV.
on
in the
a
is associated
with
physical
data
through
datasets.
part
changes
whereas
attributes
such
may
database.
release)
looks
contain
as aand
and
datasets
to
requirements
like
populate
amanifestation
track
number
are
history.
an
references
ofspec.
ERP
versions
(supporting
database.
toofphysical
thedata).
dataset.
data.

Engineering Change
Form: ECO Checklist
UGS Corp. 2006. All rights reserved.

named references

Item Master
Relation

Cost,
material,
ERP
attributes, ...

UGS Confidential

Item and Item Revision

f

For many Items, an interface for the object is defined (for

example form, fit and function) and separated into its own
Item Object. The Item applies globally and may have
multiple associated Revision Objects each conforming to the
same master definition

Many kinds of Business Objects in Teamcenter are modeled

with Items and Revisions
X

E.g. parts, documents, change requests

Items insulate related objects from

X

WIP (work in process) dynamics

interchangeability

UGS Corp. 2006. All rights reserved.

UGS Confidential

Item-Revision Model

Item

Invariance zone

P1

SPEC

Has Revision
LEGEND
Item

Revision

B
Rev

Variance zone, changed through object

acquisition for definition
UGS Corp. 2006. All rights reserved.

UGS Confidential

Revision Based Configuration Management

f

Revision based
configuration management
assumes all previous changes
accumulate into the latest
revision there is no
representation of the change
itself, just the result of
applying it to the latest
configuration
Later we will discuss an
alternative approach to
revision based configuration
management called
Incremental Change

EC2

Problem Item

EC1

Problem
Item

P1
UGS Corp. 2006. All rights reserved.

UGS Confidential

Affected Item

Affected Item

Assy 123
A

B
P2

C
P3

P4
9

What is Product Structure?

f

An integrating mechanism for lifecycle data management

Its constantly changing
Manual
Regulation

EBOM

throughout the products life

Change in customer demand
Engineering changes

Performance
Data

Specification

Work in progress
Release states

It needs to be configuration
Position

Drawing

managed to ensure:
User access to accurate

information

Note
Drawing

Collaboration
As shared information

Model
Image

changes users can be

notified

Drawing
Change
Request
UGS Corp. 2006. All rights
reserved.

UGS Confidential

10

Customer Demands for Product

Structure
Collaborative Design
Digital Mock-Up

Mass Customization
Design for Variability

CAD Product
Modeling

Multi-CAD Integration
MRP Integration

r in
c tu
a
f
nu
Ma BOM

Gen
eric
Str Prod
u
uct
ure ct

MBOM
Cost

BOM

Accountability

Single Source

of Product Data

Product Planning
Systems Engineering

al
n
o
Performance target setting cti re
u
un uct
F
r
Concept DMU
St

Space allocation

Reuse

(new program startup)

UGS Corp. 2006. All rights reserved.

Multi-View

M Cha
an ng
ag e
em
en
t

Managing Product

Change

UGS Confidential

ECO
11

Revision Effectivity
Example: Revision Rule

Each revision of an Item can be

qualified by an effectivity range

sets the date to be Feb 5

P123
A

P123
Feb 16 on

Jan 1 Feb 15

Feb 2 on
UGS Corp. 2006. All rights reserved.

A
Jan 1 Jan 10

Feb 1 Feb 15

Jan 1 Feb 1

P456

P789

P456

P234

P234

Feb 7 on

Feb 16 on

Jan 11 Feb 6
UGS Confidential

12

Structures and Effectivity

P1

Revision effectivity applies between an Item and its

revisions

Structure effectivity applies between a parent and its

children

Master-Revision insulates parent from updates to its

children
Latest
Released

B
Structure
Effectivity

P3

P4

P5

DERIVES
Revision
Effectivity

UGS Corp. 2006. All rights reserved.

P4
A
Latest

P4
B

Released Released Working Released

UGS Confidential

P1
B
P5
A
P1
B
P5
A

Revision Effectivity vs Structure Effectivity

Assy 100

Revision Effectivity
Start: 01/01/00
End: 04/30/00

-5

Structure Effectivity

-6

Start: 05/01/00
End: Onwards
WIP -> AP
(Released on 05/01/00)

-7

-8

Assy 100
1/1/00 - 4/30/00

5/01/00 - on
5/01/00 - on

1/1/00 - 4/30/00

-5
UGS Corp. 2006. All rights reserved.

UGS Confidential

-6

-7

-8
14

Product Structure and Revision Rules

Revision Rule: Latest Working
Send to PSE

383-Barrel

Copy and
Paste into
PSE

361-Top (red)

Send to PSE

390-Body Assy/A

Copy and Paste into PSE

390-Body Assy

400-Pen/A

361-Top (red)/A
383-Barrel/A

370-Nib (thick)
385-Felt

390-Body Assy/A
361-Top (red)/A
383-Barrel/A
370-Nib (thick)/A
385-Felt/A

381-Pen Cap (red)

381-Pen Cap (red)/B

351-Ink (red)

351-Ink (red)/A

BOMView Revision (BVR):

single level structure

Multi-level structure:
BVR embedded into
another BVR

Revision Rule: Latest Released

400-Pen/A
390-Body Assy/A

A structure can be made static

with revisions hard-wired into it
by setting the BVR to PRECISE.

361-Top (red)/A

Ign o
re R

383-Barrel/A

evis
ion
R

370-Nib (thick)/A
385-Felt/A

Summary
Whereas
Creating
4.
5.
6.
7.
8.
9.
10.
Revision
3.
Dynamic
2.
The
Again,
A
IfHowever,
the
BVR
pen
top
body
revision
Pen
components
user
Structure
Rules
and
the
Navigator
with
and
structure
isassy
chooses
top
Static
one
sent
abarrel
shown
PRECISE
level
is
now
item
of
toshows
of
Structures
ais
the
PSE
items
sub-structure
to
structure
the
is
has
created
components
use
determined
then
pen
a
the
structure
are
BVR
another
sent
are
relations
in
copied
has
the
containing
copied
tomade
associated
is
by
revision
same
PSE,
ofstatic
from
the
between
this
from
up
which
way
and
of
rule,
1.
-has
Structures
A
Pen
The
structure
created
that
for
was
shows
a
in
created
pen
PSE
revisions
consists
by
copying
of
configured
astructure,
and
byof
items
the
is
Occurrences.
as
Navigator
with
structure
current
different
where
the
top
revisions
itstructure
and
abody
and
revision
BOMViewRevision.
revisions
product
isand
data,
also
barrel
assy
hard-wired
An
pasted
rule.
the
a
structure
occurrence
structure.
only.
may
BVR:
Product
In
into
be
this
To
multi-level
into
the
configured.
is
create
First
case,
This
Structure
created.
represents
it.
Pen.
body
Care
itisLatest
this
is
structures
Note
still
assy
necessary
has
Editor
Innumber
athe
Working,
this
that
in
single
toPSE.
be
link
case,
the
to
it
components,
pasting
revision
-taken
Revision
items.
rules
each
isHowever,
can
dynamic.
component
be
used
PSE
A
dynamic
to
shows
being
configure
item
an
structure
individual
revisions
has
shows
is
Doing
between
have
Body
level
contain
showing
the
first
structure
structure.
aassy
with
this
necessary
the
pen
components
revision
a rules
defines
static
relations
component
components
item.
shows
structures,
actually
tothe
between
create
latest
that
top
and
need
have
being
and
revisions
aits
because
body
an
not
parent.
barrel
BVRs
worked
item
be
assy
released:
copied,
to
UG
and
themselves.
be
item.
on
cannot
other
child
and
just
not
item.
revisions,
a
-show
Dynamic
BVR
which
not
vs.
is
items.
Static
setrevs
as
structures
being
IMPRECISE.
items.
components
the
necessarily
those
assy
two
that
itself.
different
are
released.
of
being
the
body
manufactured.
ofassy.
same
item.
UGS Corp. 2006. All rights reserved.

ul e

Dynamic Structures are IMPRECISE BVRs

showing revisions configured by revision rules

400-Pen

381-Pen Cap (red)/A

351-Ink (red)/A
UGS Confidential

15

Revision configuration vrs

Incremental Change
f

The traditional revision based

configuration management
assumes all previous changes
accumulate into the latest revision

There is no representation of the

change itself, just the result of
applying it to the latest
configuration

EC2
EC1

affects
Results in

Results in

Assy 123

affects

In contrast, an incremental
change is a change that defines
the evolution of an object or
group of objects by documenting
the differences between two
states of the object

Supports changes to structure,

attributes, related data, etc

Assy 123

P1

remove

P1

P2

UGS Corp. 2006. All rights reserved.

P3

P4
UGS Confidential

P2

P3

P4

add remove add

EC1

EC2
16

Revision Configuration of Flat Structures

f

Traditionally, when a change to a

structure is required, then the parent
is revised
X

This copies the entire structure

to the new rev

If the structure has many

children, then for a simple
change, there is a lot of
unnecessary duplication of data

Change required to one occurrence

means whole structure needs to be revised

A100/B

Large, flat structures tend to have

many changes applied to them
X

A100/A

Lots of revisioning, which is

difficult to manage

The user may also want to track the

changes made and associate data
with the change.
UGS Corp. 2006. All rights reserved.

UGS Confidential

Unnecessary duplication
for required change

17

Incremental Change (IC) Basics

f

IC is a collection of Adds and

Removes that together
represent a change. These are
incremental change elements

A100/A

remove

Change is configured into a

structure using a revision rule
X

Adds are displayed

Removes are filtered out

Changes can be carried out

where they are needed without
revising entire structure
UGS Corp. 2006. All rights reserved.

Base structure
Effective for PENDING release status 1-Jan-2004 to UP

add

IC1/A

Incremental Change
Effective for PENDING release status 1-Feb-2004 to UP
January 2004

February 2004

UGS Confidential

A100/A

A100/A

Net result of IC1/A

this occurrence is replaced
as of 1-Feb-2004

18

Configuration Context
f

A Configuration Context represents Configuration

Recipe
the collection of qualification

parameters needed to configure a

representation
f

Configuration Recipes define the

conditions under which product
lifecycle data is valid
Allows the application of certain
selection criteria when navigating
a product structure
Note: Combinations of these
parameters can be applied
together e.g. latest released or
effective date 2/1/02 in
Engineering View

UGS Corp. 2006. All rights reserved.

Sample Configuration Context

parameters

Revision

Latest/ All

Effectivity

Specified date or unit

Maturity State

e.g. Working or Released

View

e.g. Design or Manufacturing

Variant
Conditions

SOS (Selected Option Set) e.g.

LX Model with Manual
Transmission, Air Conditioning
and Cruise control

Incremental
Change

e.g. ECO1 and ECO3 have been

incorporated but not ECO2

UGS Confidential

19

Variant Configuration
Pen Variant: Red with Thick Nib

Option
Defaults:
Values of
options for
default model

400-Pen/A
390-Body Assy/A

Rule Checks:
Value y of option b is incompatible
with value x of option a

Generic Pen Structure

Options:

400-Pen/A

Colour (Red or Blue)

Nib (Thick or Thin)

361-Top (red)/A
390-Body Assy/A
383-Barrel/A

Variant Rule:

361-Top (red)/A

Red with Thick Nib:

Colour = Red
Nib = Thick

370-Nib (thick)/A
385-Felt/A

360-Top (blue)/A

Colour=Red
Colour=Blue

383-Barrel/A
381-Pen Cap (red)/A
370-Nib (thick)/A

Nib=Thick

351-Ink (red)/A
371-Nib (thin)/A

Pen Variant: Blue with Thin Nib

400-Pen/A

Nib=Thin

385-Felt/A
381-Pen Cap (red)/A

390-Body Assy/A

380-Pen Cap (blue)/A

360-Top (blue)/A
383-Barrel/A
371-Nib (thin)/A
385-Felt/A

Variant Rule:

351-Ink (red)/A
350-Ink (blue)/A

Black with Thin Nib:

Colour = Blue
Nib = Thin

circumstances
under which a
line is shown

Colour=Red
Colour=Blue

Colour=Red
Colour=Blue

Summary
Whereas
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Variants
Up
Another

Both
Variant
Additionally,
Option
The
Components
and
until
ofrevision
the
component
these
now,
pen
defaults
are
conditions
rules
components
described
variant
we
variants
itdefine
configuration
isthat
can
have
possible
required
associate
might
are
the
be
are
been
by
required
used
required
values
the
in
be
tofor
looking
fact
uses
incorporate
aoption
values
toa
blue
of
define
by
specific
thin
thick
torules
options
all
create
at
pen
values
for
nib...
nib...
the
pens.
the
towith
rule
awith
All
a
Variant
rules
are
used
tofour-door
specific
identify
structure
thin
models
red
blue
components
Options
individual
needed
values
checks.
pen...
nib.
pen...
of
specific
of
to
For
associated
The
of
options
structure
aconfigure
ageneric
example,
that
components
red
revisions
are
ifpen
no
lines.
with
pen.
specific
specific
with
arule
aconfigure
Various
This
in
that
structure.
a
has
athick
models
to
structure,
generic
differentiate
been
individual
operators
option
nib.
In
of
applied.
This
pen
this
the
variant
for
variants
is
itgeneric
iscan
afrom
the
only
car
models
of
ain
generic
structure
based
on
ofor
configuration
one
other
union
are
example,
be
product.
Defaults
cannot
used
shown
ofpens
ofaalso
all
to
Variant
number
can
pen
precisely
are
pen
have
have
PSE
uses
variants
the
variants,
rules
of
awith
fixed
rules
top,
soft-top
different
define
can
have
acap,
values
to
containing...
V.
be
identify
the
roof
a
nib
types
created
colour
or
allowable
and
option.
be
of
the
ink.
option
pen
derived
at values
run
values
Variants.
(red
time
from
different
options.
components
blue)
that
or
values
pre-defined
will
and
ofdisplay
other
a nib
ofand
options.
specific
option
the loaded
given
(thick
models
line.
when
or thin).
ofneeded.
a product.

380-Pen Cap (blue)/A

350-Ink (blue)/A
UGS Corp. 2006. All rights reserved.

Variant
Conditions:

UGS Confidential

20

Supersedure and Structure Compare

f

Supersedure shows a structure

BEFORE and AFTER a change is
applied

Structure Compare enables user to

compare two revisions of a
structure or two different structures.

Supersedure highlights changes

both graphically and in the
stucture tree view

Compare Modes:
X

Single level

Lowest Level

All Levels

Insert PSE Compare Screen Clip

UGS Corp. 2006. All rights reserved.

UGS Confidential

21

Where Used/Where Referenced Filters

f

Choose which Item

Revision property to
display
Filter results to show only
referencing items of a
specified item type or
view type

Specify PSE window rule

to be used

Where
Used
Report
Wizard
UGS Corp. 2006. All rights reserved.

Configuration Rule

Filter results by
Item Type
Default display
property is Object

UGS Confidential

22

Summary

UGS Corp. 2006. All rights reserved.

UGS Confidential

23

Questions?