48
Glossary
primary document
File object that doesnotrelyon other documentsand can be opened in an application
such as Teamcenter lifecycle visualization or Adobe Acrobat. Also called a base
document.
Aprimary document can have secondary types ofdocumentsthat depend on it, such
as markups or snapshots, but the primary document itself is not dependent upon
any other file. Primary documents usually consist of one file, such as a PDF file or a
logical set of files such as an assembly and parts.
privileged user (workflow)
Responsible party, process owner, or member of the system administration group.
Privileged users have greater control over workflow tasks. For example, they can
promote, demote, and skip workflow tasks.
privileges
Type and degree of access to data. Privileges can be granted to groups, roles, users,
teams, and projects.
problem item
Item revision that the impacted item revision is replacing, typically the latest
released revision of the impacted item. The problem item is compared with the
impacted item to generate the changes (BOM change objects) when the edits to
the impacted item are saved. This item is displayed in the Structure Manager
right-hand pane to show removed components (highlighted in red).
product
Item or assembly (hierarchy ofcomponents and subassemblies) to be manufactured.
product data
Product definition data stored and managed by Teamcenter site, related descriptive
metadata, and associated volume data existingata site (owned or replicated). These
data are commonly referred to as items in Teamcenter.
product lifecycle management (PLM)
Product lifecycle management (PLM) is an essential element in effectively creating
and using global innovation networks to enable organizations and their partners
to collaborate at every stage of the product life cycle. PLM provides businesses
with unified information at every stage of the product life cycle including planning,
development, execution, and support.
properties
Keys and values that specify the configuration settings for an application in the
Teamcenter rich client.
properties file
File containingthe attributes (keys and values) that specify how an application is to
behave in the Teamcenter rich client.
property format finder (PFF)
Feature that allows you to gather and reportdata related to the objects returned by
aquery. PFF objects provide the necessary links and relationships required to locate
arbitrary data without reformatting the query instance. PFFobjects also enable you
to acquire additional informationthata single querywould be incapableofrendering.
PLM00185 F
GettingStartedwithDocumentManagement
A-9
48
Appendix A
Glossary
pseudofolder
Special container in Teamcenter that stores and displays item and item revision
relations in My Teamcenter. See alsosmartfolder.
Q
Query Builder
Teamcenter application thatenables a system administrator to create and maintain
customized searches for objectsin the Teamcenter databases, both local and remote.
Saved queries are subject to standard objectprotection and can be accessed by users
through the search feature in My Teamcenter.
query form
Predefined query used in My Teamcenter to quickly search the database without
building a custom query. Query forms limitsearch criteria to boxes displayed in the
form. Accessing additional search capabilities requiresbuilding a custom query.
R
reference item
Teamcenter object that contains information related to the problem report, change
request, or change notice. For example, it can be an analysis document or systemlog.
Any Teamcenter object, including a dataset, can be a reference item.
relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.
release status
Status associated with a workspace object when it is released through a workflow
process.
render
Process that invokes the data translations specified for an item, such as a document
revision, to generate derived visualization data. Translate is an action on a dataset.
Render is an action taken on an object, such as a document. See alsotranslate.
resource
Item used to performanoperationor define a process. Examples of resources include
robots, tools, and machines. Both standard equipment and custom tools can be
identified as resources.
review task
Task template that includes the select-signoff-team and perform-signoffs subtasks.
Each subtask contains a unique dialog box for executing the process.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server. Compare to
thin client.
rich client framework
Component of the rich client that integrates and runs various applications from a
common platform. These applications can be off-the-shelf applications such as NX
CAD/CAM/CAE, Microsoft Office, custom applications, and Java plug-ins.
A-10
GettingStarted with DocumentManagement
PLM00185F
45
Glossary
RIG approver
User who is a signoff in a workflow process with a specified role and group. In
Access Manager, the RIG approver accessor is used in Workflow ACLs and matches
the signoff definition (that is, role in group) for the release level associated with
the Workflow ACL. This accessor ensures that only signoffs are given privileges,
not a user who matches the role in group. See alsoapprover,groupapprover, and
role approver.
role
Function-oriented cluster of users that models skills and/or responsibilities. The
sameroles are typically found in manygroups. InAccessManager,role is anaccessor
used to grant privileges to all users with the same skills and/or responsibilities
regardless of project.
role approver
User who is a signoff in a workflow process with a specific role. In Access Manager,
the role approver accessor is used in Workflow ACLs and matches the sign-off
definition (that is, role in group) for the release level associated with the Workflow
ACL. This accessor ensures that only signoffs are given privileges, not a user who
matches the role. See alsoapprover,groupapprover, andRIGapprover.
role in group
Specific role in a specific group. In Access Manager, role in group is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
in the same group.
role in owning group
Specific role in the object’s owning group. In Access Manager, role in owning
group is an accessor used to grant privileges to users with the same skills and/or
responsibilities on the same project. For example, all designers in the owning group
are usually granted write privilege on their development data.
role preference
Teamcenter preference applying to an entire role.
rule handler
Handler used to integrate workflow business rulesinto Enterprise Process Modeling
processes at the task level. Rule handlers attach conditions to an action. See also
task handler.
rules-based protection
Conditions or rules that control who can or cannot access objects. These rules are
global (that is, they affect the entire Teamcenter site) and are enforced by the Access
Manager. These rules are defined by a system administrator.
rule tree
Access Manager component the system administrator uses to grant users access to
Teamcenter objects. Itis a tree of rules and access permissions that when processed
determines the access that each user has to a specified object.
PLM00185 F
GettingStarted with DocumentManagement
A-11
47
Appendix A
Glossary
S
secondary document
File objectthat is meaningful only in the contextof another document. Also called a
derived document. For example, markup data and snapshot files can be viewed only
in the context of a primary document, such as a JT file.
serial number generator
Number generator that can be configured on a neutral part to create serial numbers
for every instance of a physical part. You can set characteristics for the serial
numbers, such as a prefix, a suffix, the number increment, and the maximum
number of characters in the serial number. During the instantiation of the physical
structure from the neutral structure, you can choose to automatically assign the
serial numbers to the newly created physical parts.
server
System software component that performs a specifically defined set of software
services on behalf of one or more clients. In a typical Teamcenter installation,
servers are centralized on dedicated hosts that support a large number of clients.
Clients are distributed on hosts connected to the servers via various networking
techniques. See alsoclient.
setup
In a manufacturing environment, configuration of the work area. The setup also
identifies the parts consumed and the resources used.
Setup Wizard
Teamcenter application that facilitates postinstallation setup of a Teamcenter
database using an input file to populate the information required to create the
basic components of the Teamcenter organization. Using Setup Wizard, a system
administrator can create user/person definitions, assign a group/role to a user, and
optionally define a default volume for assigned groups.
Sign
Seedigitallysign.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.
site preference
Teamcenter preference that applies to the entire site.
smart folder
Pseudofolders configured in a hierarchical structure used to applyhierarchical levels
of filtering to project data. See alsopseudofolder.
snapshot
Folder that contains all the revisions of a configured product structure. A snapshot
can be used to redisplay the as-saved structure.
A-12
GettingStarted with DocumentManagement
PLM00185F
46
Glossary
solution item
New item revision released with the change that has a release status attached. The
item revision may be a new component part which replaces the old componentin the
parent impacted item. It may also be a new assembly that is being released.
source data
In document management and visualization, the original data format from which
derived visualization data is produced, for example, a CAD assembly and part files,
Word documents, and spreadsheet files.
status (workflow)
State applied to an object after it goes through a workflow. Typical statuses are
Pending and Approved.
Structured Query Language
ANSI standard command and embedded language for manipulating data in a
relational database.
subclass
In the Classification Search Dialog, subclass instances represent a subset of
attributes corresponding to a class. Subclasses inherit the attributes of their parent
classes. Unlike classes, which inherit every attribute of their parent classes and
cannot be edited, users can define the inherited attributesassigned to a subclass.
subscription
Combination of a workspace object and an event for which a Teamcenter user
requests notification of occurrence. Teamcenter notifies a subscribed user when the
event occurs in association with the object. Users can subscribe to objects from
Teamcenter applications, such as My Teamcenter and Structure Manager.
subscription (Schedule Manager, Service Scheduler)
Object that informs only the creator of the subscription when a specific task-related
event occurs. Compare withnotification.
T
task (workflow)
Fundamental building block used to construct a process. Each task defines a set of
actions, rules, and resources used to accomplish that task.
task dependency
Link between two tasks creating an order of completion.
task handler
Small Integration Toolkit program or function. Handlers are the lowest level
building blocks in Enterprise Process Modeling. They are used to extend and
customize tasks. There are two kindsofhandlers: action handlersand rule handlers.
See alsoactionhandlerandrulehandler.
TC XML
XMLformatused to import and exportTeamcenter dataintoand outof aTeamcenter
site. For example, this format is required for Data Exchange transfers and allows
mapping of objects between two sites that have different data models.
PLM00185 F
GettingStartedwithDocumentManagement
A-13
47
Appendix A
Glossary
Teamcenter data directory
Directory location of the Teamcenter shared data subdirectories and files. The
TC_DATA environment variable defines this location. Each data directory is
associated with a single database instance.
Teamcenter Environment Manager (TEM)
Tool with a wizard-style interface that installs Teamcenter servers and two-tier and
four-tier rich clients. TEM also performs maintenance operations, such asupgrading
servers, applying maintenance packs, and installing patches. Teamcenter installers
launch TEM using the tem.bat command (on Windows systems) or the tem.sh
command (on UNIX or Linux systems).
Teamcenter location
Physical location that hosts a database and possibly other server-side components
for one or more Teamcenter sites.
Teamcenter option
Seepreferenceanduserpreference.
Teamcenter Services
Set of services that allow customers to connect their applications to Teamcenter.
Teamcenter Services use service-oriented architecture (SOA).
Teamcenter site
Teamcenter deploymentthathas its own server-side components, suchas adatabase,
volumes, and a corporate server.
TEM
SeeTeamcenterEnvironmentManager(TEM).
thin client
Teamcenter user interface thatprovidesa streamlined browser-based viewofproduct
information stored in a Teamcenter database. The thin client is configured in the
Web tier, which creates and serves its Web pagesto the client. Compare torichclient.
translate
Process that converts data from one file format into another file format. In the
context of Teamcenter document management, source data is converted to derived
visualization data formats. The conversion is based on available translators.
Translate is an action on a dataset. Render isan action taken onan object, such as a
document. Seerender.
translation server
Web-accessible, scalable, and configurable software that performs translation from
and to various file formats.
two-tier architecture
Teamcenter architecture thatincludes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
Contrast withfour-tierarchitecture.
A-14
GettingStarted with DocumentManagement
PLM00185F
45
Glossary
U
user
Definition that is the mechanism by which Teamcenter identifies and interacts with
each user. User definitions contain a name (derived from the person definition), user
ID, operating system name, and password.
user preference
Teamcenter preference applying to a specific user.
V
value
Content of a field or variable. It can refer to alphabetic, numeric, or alphanumeric
data.
view
Software element in a rich client user interface perspective. It provides the ability to
navigate hierarchies of information, display information about selected objects, open
an editor, or display properties. See alsoperspective.
visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
W
Web tier
Teamcenter architectural tier that comprises a Java application running in a Java
2Enterprise Edition (J2EE) application server. The Web tier is responsible for
communication between the client tier and enterprise tier.
workflow
Automation of the concept that all work flows through one or more business
processes to accomplish an objective. Using workflow, documents, information, and
tasks are passed between participants during the completion of a particular process.
Workflow Designer
Teamcenter application thatenables administrators to graphically design workflow
process templates, incorporating company business practices and procedures into
the templates. Teamcenter users initiate workflow processesusing these templates.
Workflow Viewer
Teamcenter application that enables users to view the progress of a workflow
process. Users are not required to be participating members of the process being
viewed. Depending on preference settings, Workflow Viewer also allows ad hoc
process modification. See alsoadhocprocessmodification.
world
All users regardless of group or role.
X
XML object list
Data Integration Services Adapter file that is formatted in XMLand provides a list
of the parts and assemblies to be populated into the JT cache.
PLM00185 F
GettingStartedwithDocumentManagement
A-15
Documents you may be interested
Documents you may be interested
