Teamcenter Knowledge Base
One home for Teamcenter's
program & engineering modules.
A human-readable knowledge base covering Siemens Teamcenter, module by module. Live now: Program Planning, Schedule Manager (Rich Client & Active Workspace), IPP&E, Requirements Management (Systems Engineering), MBSE, Weight and Balance Management, (in progress) Structure Manager / BOM Management, and TC Administration (system/application administration, command-line utilities, environment variables, Dispatcher job setup) — distilled from Siemens Support Center's documentation for Teamcenter 2606 — with Change Management, Quality Management, Classification, and Manufacturing Process Planning coming next. Plus a Developer section of automation recipes proven against live Teamcenter instances.
Program & Schedule Management
Requirements & Systems Engineering
Structure & Mass Properties
TC Administration
Developer — Teamcenter Automation
Read the overview →Proven recipes for driving Teamcenter programmatically over the JSON REST SOA surface, the same interface Active Workspace itself uses. Session and authentication, payload shapes and fault decoding, object and relation authoring, datasets and FMS, BOM structure, schedules, parameters and units. Every recipe has been run against a live Teamcenter and read back, or is explicitly marked as documented-but-unproven.
Dispatcher — Translation Management
Read the overview →Teamcenter’s queued, distributed job runner: architecture and request lifecycle, the translator.xml registry, the four genuinely different things people call a “custom handler”, and the zero-Java route that Siemens ships as a sample readme rather than a chapter. Read out of the shipped Dispatcher SDK and the 2506 admin guide; config contracts are taken from the files themselves, runtime claims are marked as documented-but-unproven.
SSO Setup: SSL/TLS on Teamcenter
Read the overview →Teamcenter has no direct OIDC support: its SSO path runs through Teamcenter Security Services in federation mode, which requires SSL in place first. This is the operations record of putting a live 2606 tier on TLS, end to end. The certificate authority and its SAN list, the four trust stores that had to be satisfied on both client and server side, the Active Workspace and Deployment Center changes, every file created with why and how to reverse it, and the verification battery. Each claim came back from a tool call against the running tier, and what was not proven says so.