0% found this document useful (0 votes)
287 views8 pages

Teamcenter Developer Guide

The Teamcenter Developer Complete Guide outlines eight essential steps for becoming a proficient Teamcenter developer, covering prerequisites, PLM basics, data modeling, server-side automation, workflow customization, UI customization, integration, and daily developer workflows. It emphasizes hands-on exercises and real-world applications, including item creation, change management, and integration with ERP and CAD systems. The guide serves as a comprehensive roadmap from beginner to advanced practices in Teamcenter development.

Uploaded by

hiihello9974
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
287 views8 pages

Teamcenter Developer Guide

The Teamcenter Developer Complete Guide outlines eight essential steps for becoming a proficient Teamcenter developer, covering prerequisites, PLM basics, data modeling, server-side automation, workflow customization, UI customization, integration, and daily developer workflows. It emphasizes hands-on exercises and real-world applications, including item creation, change management, and integration with ERP and CAD systems. The guide serves as a comprehensive roadmap from beginner to advanced practices in Teamcenter development.

Uploaded by

hiihello9974
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Teamcenter Developer Complete Guide (Steps 1–8)

Step 1: Getting Started / Pre-Requisites


• Knowledge Needed Before You Start:
• Basic C/C++ and Java programming
• Understanding of databases (Oracle, SQL)
• Basic CAD experience (optional but helpful)
• Understanding of software version control
• Setup:
• Install Teamcenter server (sandbox)
• Install Rich Client (RAC) and Active Workspace (AWC)
• Install Eclipse for BMIDE
• Access credentials for sandbox server

Step 2: PLM and Teamcenter Basics


1) Core PLM Ideas

Concept What it means Teamcenter Objects

Product Thing a company sells Item (master)

Version of a
Specific state in time Item Revision (A, B, C…)
product

Files for a version CAD, PDFs, images, code Dataset (JT, NX, SolidWorks, PDF…)

Relations How things are linked IMAN_specification, IMAN_reference

BOM (BOMView, BOMView Revision,


Structure Parts inside assemblies
BOMLine)

Lifecycle Draft to Released to Obsolete Release Status, Lifecycle rules

Request, analyze, implement Problem Report, Change Request, Change


Change control
change Notice

Access control Who can see or edit Group, Role, Project, Privileges

Mental Model:

Item (master record)


└─ Item Revision (versioned record)

1
├─ Datasets (files)
└─ Relations to other objects

2) EBOM vs MBOM

• EBOM: Engineering view; focuses on design intent


• MBOM: Manufacturing view; focuses on assembly sequence

Example:

EBOM:
Phone Assy
├─ PCB Assy (1)
├─ Battery Pack (1)
└─ Back Cover (1)

MBOM:
Line 3
├─ Operation 10: Sub-assemble PCB
├─ Operation 20: Install Battery Pack
└─ Operation 30: Close Back Cover

3) Lifecycle & Workflows

• Release Status: Preliminary → Released → Obsolete


• Workflow: Automates tasks, approvals, and release steps
• Handlers: Validate data, auto-set properties, send emails

4) BOM Structure

BOMView
└─ BOMView Revision
└─ BOMLine

5) Example End-to-End Story

1. Create Item: PR-000200 "Battery Pack"


2. System creates Item Revision A
3. Attach datasets (CAD, JT)
4. Add properties: Weight, Voltage, Supplier
5. Insert into EBOM
6. Run workflow: Designer submits → Reviewer approves → Released
7. Assembly available downstream

2
6) Change Management

Problem Report → Change Request → Impact Analysis → Change Notice → Implement


Revision → Release

7) Hands-On Mini Exercises

• Create Item, Item Revision, attach Dataset


• Build EBOM
• Revise and release
• Sketch a Change Request process

Step 3: BMIDE – Data Modeling & Customization


1) BMIDE Overview

• Eclipse-based modeling tool


• Define Item Types, properties, relations, lifecycles
• Create Forms for RAC and Tiles for AWC

2) Object Definitions

Object Definition Example

Item Type Template for objects Part, Document

Property Attribute of Item Weight, Material

Relation Link between items IMAN_specification, BOMLine

Lifecycle State progression Draft → Released → Obsolete

3) Forms & UI Binding

• Forms: define RAC property layout


• Tiles: define AWC dashboard views
• Event Handlers: execute ITK or Java SOA logic on actions

4) Hands-On Exercises

• Create new Item Type "Battery Pack" with properties and relations
• Design RAC form for fields and tabs
• Create AWC tile to display Item and BOM
• Test lifecycle and release workflow

3
Step 4: ITK – Server-Side Automation
1) ITK Overview

• C-based API for server-side operations


• Automates object creation, modification, validation

2) Core Concepts

Concept Definition

Session Connection to server (tc_init, tc_connect)

TC Object Item, Item Revision, Dataset

Property / Attribute Field of object

Relations Link objects

Handlers Triggered by workflow or events

Error Handling Check ITK return codes

3) Basic Flow

tc_initialize();
tc_connect("user", "pass");
...perform operations...
tc_commit();
tc_disconnect();
tc_terminate();

4) Common ITK Functions

• ITEM_create, ITEM_find, ITEM_set_properties, DATASET_create, RELATE_create, WORKFLOW_start

5) Mini Exercises

• Create Item & Item Revision


• Attach Dataset
• Build BOM line via ITK
• Workflow validation (Weight > 0)

4
Step 5: Java SOA & Workflow Customization
1) Overview

• Java-based services for workflows and integration


• Accessible via RAC, AWC, or custom apps

2) Core Concepts

Concept Definition

SOA Service Java operation exposed by Teamcenter

Workflow Handler Executed during workflow step

Business Rule Logic enforcing policies

Session TCSession object for authentication

Event Listener Responds to server events

3) Example Java SOA Flow

TCSession session = new TCSession("user", "pass", "http://server/tc");


ItemService itemService = new ItemService(session);
Item item = itemService.createItem("BatteryPack", "Part");
WorkflowService workflow = new WorkflowService(session);
workflow.start("ReleaseWorkflow", itemRevisionId);
session.close();

4) Mini Exercises

• Create Item and Revision via Java SOA


• Trigger workflow approval handler
• Validate business rule (Weight > 0)
• ERP integration simulation

Step 6: UI Customization (RAC + AWC)


1) RAC Customization

• Eclipse RCP desktop client


• Forms (.form), Dialogs (.dlg), Commands (.xml)
• Example: Add "Export BOM" button, Supplier Info tab

5
2) AWC Customization

• Web client, HTML5-based


• Tiles, pages, dashboards
• Bind to Java SOA services for data retrieval and updates

3) Developer Tasks

• Edit forms, dialogs, toolbar buttons


• Create AWC tiles for BOM, Item details
• Bind event handlers to save/open/change events

4) Mini Exercises

• Customize RAC form for Battery Pack


• Add Export BOM button and bind ITK/Java handler
• Create AWC tile displaying BOM and suppliers
• Event handler validation simulation

Step 7: Integration (ERP, CAD, External Systems)


1) Core Concepts

Integration Purpose

CAD Auto-manage CAD files, revisions, datasets

ERP Sync BOM, parts, and orders

SOA / REST Programmatic access to Teamcenter data

ITK Handlers Backend automation for integration

Event / Batch Integration Real-time or scheduled sync

2) Example CAD Integration Flow

Designer saves 3D model → Teamcenter plugin creates Dataset → Item Revision


updated → BOM updated

3) ERP Integration Flow

Item released → Java SOA handler pushes BOM → ERP confirms → Update Teamcenter
status

6
4) Mini Exercises

• CAD integration simulation: attach dataset


• ERP BOM export simulation
• Event-based release trigger
• Batch export simulation

Step 8: Real-World Developer Workflow


1) Daily Role

Area Task

BMIDE Create Item Types, properties, forms

ITK Backend automation, validation

Java SOA Workflow handlers, ERP/CAD integration

UI RAC forms, dialogs, AWC tiles

Integration CAD, ERP sync, batch/event jobs

Testing Sandbox verification, deployment

2) Daily Workflow Diagram

Morning: Check tickets, review BMIDE/ITK/Java code


Midday: Implement backend logic, test workflows
Afternoon: UI customization, integration tests
Evening: Deploy changes, document, monitor

3) End-to-End Example

1. BMIDE: Item Type Battery Pack, properties, relations


2. RAC Form: Supplier Info tab
3. ITK: Validate Weight > 0
4. Java SOA: Workflow handler for approval
5. Attach CAD Dataset
6. EBOM placement
7. ERP integration simulation
8. Release workflow, verify downstream

7
4) Object Flow Diagram

BMIDE → Item/Revision → ITK Validation → Workflow/Java SOA → UI (RAC/AWC) →


Integration (CAD/ERP/External)

5) Mini Exercises

• Create Battery Pack end-to-end with workflow, UI, ITK, SOA, and ERP simulation
• Simulate event-based workflow trigger
• Test RAC/AWC UI updates

6) Key Takeaways

• BMIDE: foundation of objects and properties


• ITK: backend automation
• Java SOA: workflows, integration, approvals
• UI: efficient user interaction
• Integration: data synchronization
• Testing & deployment: critical for production stability
• Documentation and version control: essential for maintainability

7) Cheat Sheet

BMIDE → ITK → Java SOA → RAC/AWC → CAD → ERP → Test → Deploy → Document

8) Pro Tips

• Always test in sandbox


• Use consistent naming conventions
• Automate repetitive tasks with ITK/Java SOA
• Sync UI with backend logic
• Collaborate with CAD, manufacturing, ERP teams

This complete guide (Steps 1–8) gives you a full roadmap from beginner to real-world Teamcenter
developer, including data modeling, automation, workflow, UI, integration, and daily workflow
practices.

You might also like