01 Team Center Engineering Introduction

© UGS Corp. 2006. All rights reserved. © UGS PLM Solutions Inc. 2006. All right reserved.

Teamcenter Engineering

Introduction

Chan Seow Cheng曾绍清

Chan Seow Cheng曾绍清

© UGS Corp. 2006. All rights reserved..

Course ObjectivesCourse Objectives

Basic understanding of PDM

Familiar with Teamcenter Engineering Portal UI

Use Teamcenter Engineering Application to create, manage and share data


Product Data management (PDM)Product Data management (PDM)

Product Data Management (PDM) is a tool that helps manages all the processes, applications, and information required to support a product throughout its life cycle.

PDM provides a framework for

Users to create data to support a product at different stages of its life cycle.Enterprise data to be stored, managed & controlledDistributing right info to the right person (design, manufacturing, marketing, sales, purchasing, suppliers etc), at the right time


PDM Application DomainPDM Application Domain


PDM FunctionsPDM Functions

Data Vault & Data Management

Data Security authorization, version & revisionWorkFlow & Process Management

Product release, change and approvalProduct Structure Management

Management of product configurationPart & Component Management

Classification and retrieval


PDM BenefitsPDM Benefits

Shorter Time to Market

Improved Design Productivity

Improved Design and Manufacturing Accuracy

Data Integrity Safeguarded

Better Management of Engineering Change

Cost Savings

A Major Step Toward Total Quality Management


Important Teamcenter Applications and Concepts

Navigator

Contains the data a user needs regular access toProduct Structure Manager (PSM)

Editing and configuration of product structure (e.g. assemblies)Caching of configured structure as appearances

Organization (users, groups and roles)

How Teamcenter represents the actors of product dataWorkflow

Viewing, managing and modeling enterprise processes


Teamcenter Representation of OrganizationTeamcenter Representation of Organization

Engineering.Design

Engineering.Analysis

Manufacturing.Planning

Manufacturing.Production

peter

infodba

claire

james

sue

alan

david

dba

Detailer

Designer

Engineer

Senior EngineerUp until now, we have discussed the different types of data within TC Eng and how it can be manipulated. This slide focuses on the people who act on that data.

1. The organization within TC Eng consists of groups, users, persons, roles and group members. These will now be described and the interaction between them shown.

2. Groups are collections of people carrying out specific roles. Some groups can be designated as ‘Sys Admin Groups’ - any member of these groups is a ‘System Administrator’ and can perform SA functions

3. There can also be groups within groups, hence the concept of hierarchical groups.4. Roles are the functions that can be undertaken within a group. A group can have many roles and a role many groups.

5. A user is the login ID and password associated with someone using TC Eng. infodba and the DBA group are shipped with TC Eng so that initial system admin tasks can be performed.

6. A person is the name and contact details (Tel, address etc) of a user. The UI displays owning user as Person Name (user id), e.g. James Walker (james).

7. Group members are the users belonging to a group and the roles that they can adopt within that group. Users can have multiple roles in different groups.

SummaryThe Teamcenter organization are the actors on Teamcenter data. The organization consists of users who adopt various roles in the groups they are members of.

Hierarchical Groups Users Persons

Roles Group Members

Engineering

Manufacturing

DBA (System Admin Group)

Claire Smith

James Walker

Peter Jones

Sue Pierce

Alan Barker

David Doors

infodba

(System Administrators)


Data in the NavigatorData in the Navigator

Navigator is the application in which you see the data you need and work with on a daily bases.

Item

Folder

Item Revision

Dataset

Dataset

Dataset

Dataset

Form

381-Pen Cap

381-Pen Cap/A

: Item Rev Master

Cost, material,ERP,attributes, ...

files

named references

Specification Relation

Item Master Relation

Manifestation Relation

BOMView Revision PSEBOM View Revision Relation

Form: CO Checklist

Change

Physical data

Metadata VolumeVolumeVolume

: UG Master cap_model.prt

: UG Part cap_drawing.prt

: Direct Model Dataset cap_image.jt

: Text Text describingthe cap design cap_spec.txt

1. An item contains data which describes a part, e.g. models, drawings, specs2. A pen cap is an example of an item, because to make one, you need data such as a spec outlining requirements and a UG model describing what the part looks like

3. Items consist of one or more revisions. Item revisions are the most important concept in TC Eng, because these are used to manage changes and track history.

4. An item must have at least one revision. In this case, when the pen cap is created, an initial revision, ‘/A’ is also created.

5. Item revisions contain data, principally forms and datasets. Forms contain additional, non-TC Eng, company-specific information, whereas datasets are references to physical data (files).

6. An item revision master is a special form that all item revisions have. It can contain information such as production cost, material and ERP attributes to populate an ERP database.

7. An example of a dataset is the UG Master solid model. In this case, a part file called cap_model.prt

8. A separate dataset is used for the drawing file, cap_drawing.prt9. Another useful dataset is one with an .jt image file for lightweight representation of the part in PV.10. It also possible to have datasets for text files and Office documents (Word, Excel, etc). Usually, these datasets will contain supporting information, such as a requirements spec.

11. Whereas items, item revisions, forms and datasets are abstract data, a dataset represents a physical file, stored on a ‘volume’. The volume may contain a number of versions of the dataset.

12. As such, TC Eng provides a clear distinction between physical data stored on one or more volumes and abstract metadata stored in a database.

13. When a user wants to view the contents of a dataset, a named reference is used to fetch the physical data. E.g. visualization of a part in PV.

14. The association data has with an item revision is defined using relations. The two significant ones are specification (important dataset, locked on release) and manifestation (supporting data).

15. Other types of data found in Navigator include folders for organizing data... 16. …Engineering change objects (containers for EC processes) containing forms such as the Engineering Change Order checklist...

17. …and BOMView revisions: representations of product structure.SummaryTeamcenter contains metadata, the most important of which is the item revision. Metadata is associated with physical data through datasets.

Database


Product Structure and Revision RulesProduct Structure and Revision Rules

A structure can be made static with revisions ‘hard-wired’ into it by setting the BVR to PRECISE.

381-Pen Cap (red)

361-Top (red)

383-Barrel

370-Nib (thick)

385-Felt

351-Ink (red)

390-Body Assy Copy and

Paste into PSE

Send to PSE

400-Pen Send to PSE

Copy and Paste into PSE

Revision Rule: Latest Working

390-Body Assy/A

400-Pen/A

BOMView Revision (BVR):single level structure

Multi-level structure:BVR embedded intoanother BVR

Whereas Navigator shows the relations between items and data, the Product Structure Editor shows the relations between an item and other items.

Creating Structure1. The structure for a pen consists of a number of components, each component being an individual item.

2. The body assy is a sub-structure made up of the top and barrel only. To create this structure, it is first necessary to create a body assy item.

3. The body assy item is then sent to PSE, which is where product structure is created.4. The top and barrel items are copied from Navigator and pasted into the body assy in PSE. Doing this defines the top and barrel to be child components of the body assy.

5. The body assy now has a BVR containing Occurrences. An occurrence represents the link between a component and its parent.

6. The pen structure is created in the same way as the body assy structure. First it is necessary to have a pen item.

361-Top (red)/A

383-Barrel/A

361-Top (red)/A

383-Barrel/A

390-Body Assy/A

381-Pen Cap (red)/B

370-Nib (thick)/A

385-Felt/A

351-Ink (red)/A

361-Top (red)/A

383-Barrel/A

Revision Rule: Latest Released

400-Pen/A

390-Body Assy/A

381-Pen Cap (red)/A

370-Nib (thick)/A

385-Felt/A

351-Ink (red)/A

7. The Pen is sent to PSE 8. The components of the pen are copied from Navigator and pasted into the Pen. Note that the Body assy components need not be copied, just the assy itself.

9. Again, the top level structure has associated with it a BOMViewRevision. This is still a single level structure.

10. However, one of the components of this structure is also a BVR: multi-level structures contain components that have BVRs themselves.

Revision Rules1. Pen structure was created by copying and pasting items. However, PSE shows item revisions, not items.

2. The revision shown is determined by the current revision rule. In this case, Latest Working, showing revision actually being worked on and not necessarily released.

3. If the user chooses to use another revision rule, different revisions may be configured. In this case, the structure shows latest revisions released: those that are being manufactured.

Dynamic and Static Structures1. A structure that shows revisions configured by revision rules is dynamic. A dynamic structure has a BVR which is set as being IMPRECISE.

Dyn

amic

Stru

ctur

es a

re IM

PR

ECIS

E B

VRs

show

ing

revi

sion

s co

nfig

ured

by

revi

sion

rule

s

2. A BVR with a PRECISE structure is static and has revisions hard-wired into it. Care has to be taken with static structures, because UG cannot show two different revs of same item.

Ignore Revision RuleSummary- Structures created in PSE- Revision rules can be used to configure revisions- Dynamic vs. Static structures


Rule handler invoked to validate form: if valid, workflow can proceed to next stage

Typical Teamcenter Workflow ProcessTypical Teamcenter Workflow Process

TASKS

ACTORS(R: Role,G: Group)

ACTIVITIES

TASK TYPE

Review to determine whether change required, prior to committing to the rest of the process

R = Designer

Decide what needs to be done to fix the problem:- Create 2D

markups- Compile

meeting notes

Review the proposed fix

R = DesignerR = Tooling Engineer

Implement the fix:- Save As- Create new item- Create datasets- Cancel old

Barrel, addNew Barrel

R = DesignerR = Technical

Support

Quorum = 1

NO

TIFY

R = Senior DesignerR = Manufacturing

EngineerR = Quality Manager

R = DesignerG = Marketing

DEC

ISIO

N

Quorum = ALL

VotingApprove = 1Reject = 0No Decision = 0

Create Solution

Do Route

Approve Solution

Design

Make Changes

Make Changes

Tooling

Do

Approval process to ensure the whole EC is satisfactory

R = SeniorDesigner

R = QualityManager

R = DesignerG = Marketing

DEC

ISIO

NA

CK

Quorum = ALL

Approve EC

Route

Company employee creates a change and attaches forms and targets

CR Approval

Review

Engineering changes go through a workflow process (sequence of actions and reviews) in order to get approval. This slide describes the important concepts associated with workflow.

1. An EC process starts with a user of TC Eng (company employee) identifying a problem, creating an EC and attaching the forms and targets. The subsequent process involves...

2. ... tasks (the stages in the process)...3. … Task types that define the types of activity undertaken within the task….4. … Activities that summarize what actions take place during execution of the tasks...5. … Actors: the people who undertake the activities required by each task...

WRITE ACCESS

PROMOTE/ DEMOTE

R = Checker

Check to ensure fix has been implemented correctly to the Models & Drawings

Quorum = ALL

Review

Approve Changes

Approve Changes

N/A

World = No Write

World = No Write

Approver Role= Senior Designer

World = No Write

Approver Role= Quality

ManagerN/A

Approver Role= Designer= Tooling Engineer

World = No Write

N/A

Approver Role= Designer

N/A

6. … Finally there are the privileges: a description of who can change data (write access) and who can move the process on to the next stage or back to a previous stage (promote/demote)

7. Once the EC has been created, the first task will typically be approval of the engineering change request (ECR). This is a review task in which assigned persons are asked for sign-off.

8. This particular review process is necessary to determine whether the problem is in fact real and the change is genuinely required, prior to committing resources in order to fix the problem.

9. The roles of people asked to approve the ECR review will be designer (the person assigned to fix the problem) and technical support (the person responsible for tracking the fix).

10. Although two people are asked to approve, this particular review task requires only one sign-off. The number of sign-offs required for a review task is called the Quorum.

11. The choices available to a reviewer are: ‘approve’, ‘reject’ or ‘no decision’. ‘Reject’ and ‘no decision’ are treated the same. It is necessary to press ‘approve’ in order to register acceptance.

12. At this stage of the process, data cannot be changed, i.e. World has no write access. With a quorum of 1, there is no need for anyone to promote/demote privileges.

13. The next task is ‘Create Solution’. This is a ‘Do’ task in which the fix is prepared prior to implementation.

14. During this task it is likely that a set of meetings will take place in order to decide how the problem will be fixed. Meeting notes and 2D markups will be compiled and attached to the EC.

15. Although the task will involve a number of people, the person responsible is the designer. It is his duty to compile the data collected and register the completion of the task.

16. During this stage, the designer will make changes to compile all the information gathered and therefore needs write access to do this.

17. The next task is a route task to approve the proposed fix. This is a special kind of review task in which persons other than those asked to provide sign-off can be involved in the review.

18. The actions required are to review the approach decided in the previous Do task.19. This is an important task, so as well as senior personnel being asked for sign-off, both a designer and someone from marketing will be notified and offered an opportunity to comment.

20. The quorum applies only to those asked to approve (not those on the notify list). In this case, sign-offs are required from all reviewers.

21. During the review stage, no data can be changed (no write access). In case not all reviewers approve, the senior designer can decide whether to promote or demote.

22. The next stage in the process is two Do tasks carried out in parallel. These are the implementation tasks carried out by the designer and by the tooling engineer.

23. It is during this task that the changes are implemented. This involves doing a ‘save-as’ to up-rev the item being changed as well as adds and cancels to the structure.

24. The roles of those required to implement the fix are Designer and Tooling Engineer.25. During this stage, both the designer and the tooling engineer need write access to make changes (promote/demote only applicable for review tasks).

26. The next stage in the process is two review tasks carried out by checkers. Separate reviews are needed for the design changes and the tooling changes. No write access during a review.

27. A second level of review is required to approve the whole EC. Because this is an important review, persons other than the approvers need to be involved. Hence Route task.

28. The objective of this review is to ensure the implementation has been carried out to the satisfaction of senior personnel.

29. A senior designer and quality manager are asked to approve the EC. A designer and a member of the marketing group also need to acknowledge that they have seen the fix.

30. Again, this is a review process, so no write access. In a stale-mate situation, the Quality Manager has the right to promote or demote.

31. The final two tasks are carried out automatically on approval of the previous task. This is when release statuses are added to the changes and relevant personnel are informed.

(Automatic)

Stamp affected items and solution items with release status and notify recipients on CC list that fix has been implemented. Production start date (Effectivity) may be set at this point.

Add Status Notify

Add Status Notify

N/A

32. During workflow, handlers can be implemented to carry out additional actions (action handlers) or to carry out sophisticated ‘go/no go’decision making (rule handlers)

SummaryWorkflow processes can be created to model tasks required to approve and implement a change and the required Role / Group to perform a task.


SummarySummary

Teamcenter is a collection of applications that are used to manage product data

The most important concept within Teamcenter is the item revision, representing a part and its data at a given point in its lifecycle

Product structure manager (PSM) is used to create and configure item-to-item relations (e.g. assemblies)

Revision rule configuration is used to determine item revisions and associated structure at a given point in the lifecycle of a product (e.g. latest released)

Within the Teamcenter representation of organization, a group member is a user assuming a particular role within a given group

Documents

01 Team Center Engineering Introduction