Teamcenter Automation: Developer Overview

Proven recipes for driving Teamcenter programmatically over the JSON REST SOA surface: the same interface Active Workspace itself uses, so one client works against any Teamcenter web tier from TC 11 through 2506/2606 with no Siemens client libraries.

Everything here has been run against a live Teamcenter and read back, or is explicitly marked as documented-but-unproven. That distinction is the point: a recipe you have not executed is a hypothesis.

The three house rules

1. Never state a Teamcenter item id, uid, dataset name or status that a tool call did not return.
2. Re-verify every create with a live getProperties on the returned uid before reporting it.
3. A fault code is a hint, never proof a capability is impossible. If the Active Workspace UI can do it, the call exists. Capture it rather than concluding it cannot be done.

Skills

• Cameo Connector Config Configure and switch the HCL Cameo Connector for Teamcenter between environments and releases. Covers the fact that an "environment" is 14 (file, key) writes over 11 key names across TWO files that nothing keeps in step (a half-switch logs in fine and sends files to the wrong tier), the Java .properties escaping bug that presents as a missing folder, replace-never-overlay when swapping connector releases, the Cameo profile that must move with it, and the catalogue of errors on this stack that name the wrong cause. Use for any Cameo/Teamcenter connector setup, environment switch, release upgrade, or "it logged in but something is wrong" investigation.
• Cameo Headless Automation Run scripts inside Cameo / MagicDraw without touching the GUI - a custom CommandLineAction plugin driven by CommandLineActionLauncher, or a persistent worker that serves HTTP so calls cost 0.4s instead of 40s. Covers the three things that make an unattended run fail while looking healthy - batch mode still needs a desktop, the FL_* licence properties suppress the FlexNet dialog in BATCH but not in GUI, and a batch process discards an unsaved edit while the create still reports success. Use for any headless/batch/unattended Cameo work, macro automation without clicking Tools > Macros, or a "the action ran and nothing happened" investigation.
• Cameo Model Build Discipline Build a large Cameo/MagicDraw SysML model programmatically without producing a model that passes its own audit and is still wrong. Covers the decision that must be made BEFORE the first element (organize by function or by phase, and what each costs at export time), the Jython authoring traps that report success and change nothing (getOwnedElement under-enumerating, relation re-homing defeating idempotency, a batch save that throws while the audit prints clean), and the audit discipline that catches a self-graded model - three-valued outcomes, negative controls, and the meta-failures where a check that was never written reads exactly like a pass. Ships mdzip_audit.py, a zero-dependency offline checker that runs on any .mdzip with no Cameo and no licence. Use before starting any generated Cameo model, when an audit reports all-green, or for any "the build said it worked" investigation.
• Cameo TC Diagram Images Get Cameo/MagicDraw diagram images into Teamcenter and make Active Workspace preview them. Covers what the connector actually produces (a JPEG picture plus an SVG that is NOT a picture), the AWC_defaultViewerConfig.VIEWERCONFIG entry that decides which one the viewer serves, the diagram-type filter that silently skips most diagrams, and the site-preference write mechanics including a payload that faults on a null member and a write that returns HTTP 200 and changes nothing. Use for "SVGs from Cameo to Teamcenter", any Seg0Diagram preview problem, blurry diagram previews, or any Teamcenter site-preference write.
• Cameo TC Element Authoring Author SysML in Cameo so it actually lands in Teamcenter through the HCL connector. Covers the element-type landing matrix (what each Cameo type becomes in TC), the three gates that decide whether something exports at all (a port needs a part-property occurrence, a connector needs factory ends plus propertyPath, an object flow needs CallBehaviorAction endpoints), the direction rules that make Allocate and Verify work or silently fail, the "set only at creation" class of traps where editing an existing element is ignored with no error, the two relations that never export despite 330 declared rules each, and the verification discipline (server-side reads only, because the headless Check-In never stamps TC ids back into the model). Use for any Cameo model that must reach Teamcenter, any "the export succeeded but nothing is there" investigation, and before writing modeling guidance for other people.
• Capella Headless Authoring Create and modify Eclipse Capella 6.0 models from Python with no GUI, using Python4Capella over EASE inside Innexis Architect Explorer - installing it with the p2 director, the workspace bootstrap that makes projects visible, the exact element-creation idioms for PhysicalComponent/PhysicalFunction/ComponentPort/allocation, and the two silent-success traps in the API that write nothing or the wrong name while reporting success. Use for any Teamcenter-to-Capella import, bulk Capella edit, or Capella scripting.
• Capital Topology Design Association Associate functional (logical) designs with a Capital topology design, so a topology stops reporting zero conductors and becomes routable. Covers the one command that does it (Associate Logical Designs, on Automate > Wiring, reachable by pressing the space bar), its two modes (individual design revisions, or a whole build list), the numbers that prove it worked, and the five plausible wrong doors that cost a session: the Working Set picker that offers designs or a build list and changes nothing, Set Active on a build list, Manage Designs & Effectivity whose OK never enables, the Build button that is really the Report Builder, and Query and Generate Design which cannot target an existing topology. Use for any Capital topology that gathers no wires, "0 inline(s) with connectivity", getAssociatedFunctionalDesigns returning zero, Capital Wiring Integrator or Systems Integrator design association, or before concluding that a topology ships without functional designs.
• Diagnose Silent Failure Diagnose a call that reports success and does nothing, or a reading that looks like a fact about the world and is an artefact of how it was read. Gives the capture-first procedure, the five shapes a wrong reading takes, and the control discipline that kills a hypothesis in one run instead of six. Use when an API returns ok but the effect is absent, when a flag reads false and you are about to explain why, when a count looks wrong, or any time you are about to write "the tool does not support X" - and especially when you have already tried two explanations.
• Eggplant AWC Testing Drive Active Workspace (or any web app on a Windows SUT) with Eggplant Functional 26.2.2 headlessly - the runscript CLI, the RDP connection recipe, OCR/text matching that lets a suite be authored with no GUI and no pre-captured image assets, and the seven failure modes that make a run report success while proving nothing. Covers the credential handling that keeps a password out of the logs (Eggplant writes TypeText content to LogFile.txt by default), the blank-framebuffer race after Connect, SSO sessions that silently drop mid-test, and why OCR flakiness must be designed around rather than retried. Use for any Eggplant Functional work, any "my UI test is flaky" investigation, and before writing UI tests against Teamcenter.
• Graphstudio Hyperv Keycloak Build a Rocky Linux Hyper-V VM via unattended kickstart (no Windows admin elevation, no RHEL subscription) and install Siemens Rapidminer Graph Studio (rebrand of Altair Graph Studio, née Cambridge Semantics Anzo - internal code/paths still say "anzo" everywhere) with SSO wired to a shared Keycloak realm. Covers the OEMDRV-ISO-via-Docker recipe (COM/IMAPI2FS from PowerShell is not worth fighting), three separate kickstart traps that each look like a different failure, the install4j console-mode driver pattern with tail-anchored prompt matching, and the multi-stage Keycloak SSO debugging chain: a discoveryURI:null red herring, a redirect-uri port+slash mismatch, a "Trust All" checkbox that only covers one of two TLS code paths, and Graph Studio's own SEPARATE certificate trust store (distinct from the JVM cacerts) that is the actual fix for the second path. Also covers Altair Units Licensing machine-slot exhaustion and its Auth Token fix, deploying a Graph Lakehouse (AnzoGraph) backend via Docker instead of a second VM (including the gRPC ports a graphmart deploy needs that the web UI alone doesn't expose), and a Hyper-V Default Switch IP change that silently breaks the browser URL, the Keycloak redirect URI, and the VM's own hosts-file entry all at once. Also covers what a locked-out sysadmin account actually requires (a full reinstall - no offline reset exists anywhere in the product) and the install4j memory-prompt trap that validates against live Hyper-V dynamic memory rather than the stated minimum. Also covers three independently-reproducible backend bugs blocking every no-code path to get real data into a graphmart (HttpSource auto-browse NPE, a missing OSGi commons-net bundle that makes FTP File Connections unusable, and a shared file-mapping-preview crash on any source type), a working vsftpd staging-server recipe including the pam_shells//etc/shells FTP-login trap, the sticky per-graphmart File Staging Area binding, and why the one working ingestion path (a hand-written SPARQL/GDI CONSTRUCT query) is virtualization-only, not onboarding, in this build. Use for any Hyper-V unattended Linux install, any Graph Studio/Anzo deployment, any Graph Lakehouse/AnzoGraph connection, a locked-out admin account, connecting Graph Studio to an external REST/HTTP data source, or any "OIDC login redirects but throws an internal SSL error" investigation.
• Innexis Ae Headless Drive Innexis Architect Explorer 2026.1 headless from the command line - the AE_Engine CLI contract, the working-directory trap that silently deletes your project, the schema-resolution rule that makes a valid model report "syntax is invalid", and what each stage {validate, compile, build, run, analyze, all} actually needs. Use for any Innexis AE automation, batch validation, or "AE says my model is invalid" investigation.
• Innexis Ae Model Xml Author the Innexis Architect Explorer analysis model (the AR-PACKAGE XML the AE engine consumes) - its AUTOSAR-shaped schema, the HW-SW-MAPPING element that actually answers "can this electronics carry this software", the hard architecture limits, and the mapping from Teamcenter/Cameo system elements. Use when generating or hand-editing an AE .xml, sizing an AE architecture, or planning a TC-to-AE transform.
• Nx Schematic Diagramming Author NX Diagramming / Schematic Designer content (P&ID, hydraulic, wiring schematics) from NXOpen Python - placing reuse-library symbols, wiring connections, tagging and plotting. Covers the one thing that blocks every attempt: this cannot run in run_journal.exe, and why the failure is silent. Use for any NX schematic, P&ID, or diagramming automation.
• Polarion Authentication Configure Polarion 2606 authentication - the authentication.xml contract, SSO via Teamcenter Security Services (tcss) or OIDC (oauth2), and the traps that make a wrong config look right. Covers the built-in editor being the only supported edit surface, the schema-vs-runtime contradiction that makes password and tcss mutually exclusive, the JVM truststore Polarion needs before it can call TcSS at all, and the TcSS Application Registry check that fires on the return leg only so a clean outbound redirect proves nothing. Use for any Polarion SSO, LDAP, OIDC or "my authentication config will not save" work.
• Polarion Https And Rest Put Polarion 2606 on HTTPS, move base.url, run the index rebuild it forces, redirect HTTP, and enable the REST API. Covers serving TLS on a non-standard port when 443 is taken, the JDK truststore Polarion needs to call its own base URL, the reindex script whose real behaviour differs from the documentation so a correct rebuild reads as "never ran", the Apache rewrite rule whose guard silently stops guarding when you add a second rule, and the REST API status code that means success. Use for Polarion SSL, base.url or repo changes, "do I need a reindex", HTTP to HTTPS redirects, enabling the REST API or Swagger UI, and any Polarion change that has to be coordinated with a Teamcenter SSO Application Registry entry.
• Polarion Salt Licensing Make Polarion 2606 obtain a SALT licence, and diagnose it when it will not. Covers the three configuration surfaces and which one actually wins, the rule that SALT validates the COMBINATION of licence sources so one bad entry invalidates a good one, the vendor-daemon mismatch (features issued to ugslmd while Polarion's client wants saltd) that produces two completely different error messages from one cause, the consolidated-vendor-daemon reading that makes "no features are served" look true when it is false, and the instrument ladder that answers the question in one call instead of six. Use for any Polarion licensing failure, "License cannot be obtained", "missing server_id feature", "Invalid (inconsistent) license key", a SALT server that appears to serve nothing, or before asking Siemens to reissue a licence.
• TC AWC Custom Tab Add a whole TAB (an XRT ) to the summary panel of one Teamcenter business object type in Active Workspace - the top-level inject pattern OOTB uses for Weight and Balance / Cost / Parameters, how tab order and the overflow chevron decide whether anyone ever sees it, why type scoping belongs in the REGISTRATION rather than in visibleWhen (an occurrence sheet is not what renders for a block), gating a tab on a site preference, and the verification traps where a screenshot lies in both directions. Use for "put a custom tab on this object type", scoping a tab that appears on too many objects, a per-type dashboard or report tab, or a "my tab does not appear" investigation.
• TC AWC Stylesheets Author, register and verify Active Workspace style sheets (XRT / XML Rendering Templates) on Teamcenter - putting custom content on an Overview or Details tab, working out which style sheet a surface actually resolves, carrying real markup via an SWF module htmlPanel, and the traps where a write returns 200 and changes nothing. Use for any AWC style sheet, XRT, summary panel, custom dashboard, declarative view, or "my panel does not appear" investigation.
• TC Bmide Project Validation Make a hand-authored BMIDE template project that BOTH the packaging utility and the BMIDE client accept. Covers the requirements neither tool documents, the two that contradict each other, the one that cannot live in the project at all, what breaks when you split a template, and the error messages that name the stage that noticed rather than the thing that is wrong. Ships verify-bmide-project.ps1, which checks all of them against any project. Use before running bmide_generate_package.bat, before loading a project into the BMIDE client, and for any "failed to load correctly" or "Unable to update the manifest file" investigation.
• TC BOM Structure Read and build Teamcenter product structure over SOA. The working three-call sequence for BOM windows and occurrence trees (createOrReConfigureBOMWindows, expandPSAllLevels, connector endpoint properties), the proven occurrence child-add write, and why an empty 200 here means wrong request shape before it means deprecation. Use for BOM, occurrence, connectivity or structure work.
• TC Capture AWC Calls Crack an undocumented Teamcenter capability by capturing Active Workspace's own network calls instead of guessing SOA operation names. The fetch/XHR interceptor recipe, when to reach for it, and the two wrong conclusions this method overturned. Use when an operation is not in the WSDL kit, or after two or three failed blind attempts to guess a service name or version.
• TC Classification Bulkload Bulk-load any domain into Teamcenter Classification. The four-stage reconcile / resolve / generate-plmxml / idempotent-rerun pipeline proven end to end, why the plmxml plus CLI route beats direct SOA writes, the search-index caveat that makes REST-write success reports unreliable, and the real documented SOA op for creating hierarchy nodes (not just placements). Use for classifying items at scale (notes, functions, logical elements, signals, parts) or building the class tree itself.
• TC Classification Hierarchy Build the Teamcenter Classification TREE ITSELF - the class/hierarchy nodes, not the placements into them. Three ways in (the documented SOA op, Classification Manager's Add Class panel, its JSON/PLMXML Import), which one works when, the account trap whose error message reads like a wrong-data-model conclusion, the four HierarchyNodeDetails fields whose XSD prose is misleading, and why there is no safe undo. Use before any classification bulk-load when the target branch does not exist yet, and for designing a new taxonomy.
• TC Datasets Files Attach real file content to Teamcenter objects over SOA. The three-step dataset recipe (createDatasets, getDatasetWriteTickets, FMS multipart upload, commitDatasetFiles), the two settings that silently return nothing if wrong, verified named references including NX UGMASTER, and why "FMS is blocked" is usually a missing session cookie. Use when checking a file into TC.
• TC Decision Management Author decision management (ISO/IEC/IEEE 15288:2023 clause 6.3.3) in Teamcenter - trade studies, measurable selection criteria frozen before the alternatives exist, alternative evaluation, and a decision record carrying resolution, rationale and assumptions. Covers building criteria on Parameter Management's OOTB registry, the difference between a type being absent from a TIER and absent from the RELEASE and which call answers which, authoring a decision on stock types before the typed template is deployed, and the nine silent-200 traps hit while proving it (createRelations reporting no created uid on relations it created, deleteObjects hiding partialErrors from a non-DBA account, setProperties silently writing nothing because it takes info/vecNameVal and not objects/attributes, a parallel-array file-ticket lane, and a workflow template that holds its name while being unlistable). Use for trade studies, decision records, criteria registries, weighted alternative evaluation, rationale and assumption capture, or deploying the Decision Management module.
• TC Deployable Package Ship a custom Teamcenter BMIDE template as a Deployment Center package whose PAYLOAD actually installs, and prove that it did. Covers the four rendering preferences a type needs and why registering one does not cover the others, the Deployment Center localization bundle's real format (wrong shape renders the raw key as the application's name), the generated-file trap that silently reverts edits at the next build, a build gate that fails when a style sheet is installed but nothing can reach it, staging into the repository, and the verification chain where the packager, the exit code and the installer log each report success on a failure. Use when building or deploying a custom template package, when a deployed capability is missing a surface, or before claiming a package installs anything.
• TC Deployment Center Teamcenter Deployment Center - the centralized web app that models environments, holds the software repository, and generates the deployment scripts that actually install or update Teamcenter on target machines. Covers the concept model (Environment / Software / Applications / Components), the repository rules that silently hide kits, quick deploy and its utilities, and how custom DC-compatible packages get built. Use for installing or updating Teamcenter modules, and for authoring Deployment Center packages.
• TC Dispatcher Cicd Pipeline Set up a Teamcenter Dispatcher translator end to end and use it as a CI/CD-style pipeline engine — a workflow-fired job runner with stages, gates, pass/fail routing and fan-out/fan-in. Full setup guide (translator registration, handler binding, site preferences, the Windows-service classpath trap) plus the router/config pattern for running many "pipeline stages" off one script. Use when standing up a new Dispatcher-triggered workflow integration, or explaining the pattern to someone else.
• TC Dispatcher Requests Trigger and monitor Teamcenter Dispatcher translations. The undocumented SOA operation createDispatcherRequest, the OOTB workflow handler the Dispatcher guide says does not exist, how to read a request's state when getProperties returns nothing, the two independent preference families, and direct vs indirect translators. Use for any Dispatcher, translation, or long-running out-of-band job against TC data.
• TC Help Server Authoring Author, publish, package, and distribute custom manuals on a local Siemens Support Center Documentation Server (the "Teamcenter Help Server") so they serve, search, and deep-link exactly like an out-of-the-box collection. Covers the real content and Elasticsearch index formats (reverse-engineered from a live install AND from taking apart two real Siemens installer .exe files, no public admin guide exists), the reindex command found in the installer's own log, real bugs hit building this and root-caused with an A/B test (a PowerShell ConvertTo-Json read that silently mangled the schema; an "[ids] failed to parse field [values]" importer error that looked like a nondeterministic vendor bug but was actually caused by launching help-server-win.exe with the wrong process working directory -- 4/4 failures with the wrong directory, 9/9 clean with it pinned via Start-Process -WorkingDirectory, confirmed causal by reproducing the failure on demand; and a Copy-Item -Recurse destination-exists gotcha that doubled a folder segment), and a PowerShell toolkit -- author, publish, package, install-elsewhere, verify -- that automates and has proven the complete pipeline end to end. Use for "add a custom manual to the help server", "install documentation like Teamcenter's own", "package documentation for another server", or any Documentation Portal / help-server-win.exe investigation.
• TC Mission Engineering Build business or mission analysis (ISO/IEC/IEEE 15288:2023 clause 6.4.1) and DoD Mission Engineering (MEG 2.0, Mission Architecture Style Guide, UAF) in Teamcenter - the problem/opportunity space, solution classes, preliminary operational concepts, mission threads and the traceability into stakeholder and system requirements. Covers the Seg0 operational-analysis layer that ships in the systemsengineering template and is absent from the documentation set, which OOTB types carry which 6.4.1 concept, the two concepts that have no carrier, and the relation-verification path that works when the usual one silently returns nothing. Use for mission analysis, concept definition, capability gap analysis, trade-space framing, operational concepts, mission threads, mission engineering threads, METs, MOE/MOP measures, baseline versus alternative mission architectures, or finding which Teamcenter capability serves the front of the life cycle.
• TC Object Authoring Create real Teamcenter business objects over SOA. The createAttachAndSubmitObjects compound-create pattern (works where generic createItems faults), when to use createItems instead, and the verified type names for requirements, functions, logical blocks, signals, verification, reliability, electrical and simulation objects. Use when authoring any TC item, revision, spec, or domain object.
• TC Parameters Units Author Teamcenter parameters, parameter definitions and units. The three-tier model (definition, parameter, measure value), the AttributeTargetManagementService API that beats hand-rolled creates, the unit-of-measure system (UMS) and its CSV loader, and the traps around att0Uom, the unit picker and the current_project blocker. Use for MBSE parameters, engineering characteristics, KPIs or units of measure in TC.
• TC Parent Child Rollup Standing rule for authoring in Teamcenter - every object rolls up to a parent, and it must roll up through the carrier the DOCUMENTATION reads, not only the one the Relations tab reads. Covers which carrier each family needs, the two-carrier trap where having one looks like success, and how to verify rollup so a demo does not open on a flat list. Use before authoring any requirement, logical block, function, simulation request or verification request, and for any "why is the Content tab empty" or "why will Configurator not filter this" investigation.
• TC Query Discovery Read Teamcenter over SOA. getProperties as the universal traversal primitive, the OOTB saved-query chain (Item Name / Item ID / General... / Dataset Name) with its parallel-array trap, type discovery, and the types that return zero from a saved query for reasons that are not absence. Use for any TC read, search, or "does this type exist here" question.
• TC Relations Traceability Create and verify Teamcenter relations (GRM) over SOA. createRelations shapes, the revision-uid rule, direction enforcement, the verified relation-type atlas for architecture/allocation/verification/reliability, and the one-call reference-property read that beats GRM traversal. Use when linking TC objects or proving a traceability claim.
• TC Report Definitions Author, import, verify and delete Teamcenter ReportDefinitions - the classic Report Builder kind and the Active Workspace "active summary/item report" kind that carries charts and feeds the Reports dashboard tile. Covers the export-then-mutate recipe, the report-id length cap that fails completely silently, the chart-type vocabulary actually available (pie/column/line, no donut), why a saved query reports zero definitions on a tier that has 162, and the empty-string criteria that crashes a tcserver. Use for any TC report, dashboard card, Reports tile, or "my report did not import" investigation.
• TC Requirement Spec Content Put requirements INSIDE a Teamcenter specification so Active Workspace, the Content tab, exports and Product Configurator can all see them. Covers the two different things "in a spec" can mean and why having only one of them looks like success, the two undocumented Active Workspace calls that actually place content (getOccurrences4 then addObject5), the five payload members whose absence returns a fault naming nothing, and the verification mistake that makes an unpersisted structure report as built. Use whenever authoring requirements, verification requirements or any spec content, and before any trace link matrix or variant work.
• TC Schedule Program Planning Author Teamcenter Schedule Manager schedules and IPP&E program structure over SOA. The createSchedule path and the single site preference that silently blocks it site-wide, the root-task lazy-creation gotcha, the coordinator-membership gap, and the Psi0WorkElement precedence-network alternative. Use for schedules, tasks, milestones, WBS, IMP or program-planning work in TC.
• TC SOA Docs Navigation Find the truth about a Teamcenter SOA operation in the local Help Server documentation set (WSDL/XSD schemas, Services Reference javadoc, SDK samples, help server at localhost:51000). The WSDLs are the ground truth the javadoc and the samples are not. Use when you need the real service name, version, required members, or deprecation status of an operation.
• TC SOA Payload Shapes Build a Teamcenter SOA request that actually works. The full-struct rule, the NULLTAG sentinel, what each fault code (214022, 214085, 214086, 38015, 38041, 101019, 515110) really means, and the single most expensive failure mode in TC automation: a deprecated operation that returns 200 OK with an empty result and no error, forever. Use when a call faults, or returns success with nothing in it.
• TC SOA Session Connect to any Teamcenter web tier over the JSON REST SOA surface (the same one Active Workspace uses). Covers the XSRF bootstrap handshake, the login envelope, the fact that TC returns HTTP 200 on faults, and how to tell a bad credential from a down server-manager pool. Use this before any other Teamcenter automation skill.
• TC Sso Keycloak Stand up Keycloak as a shared OIDC identity provider and configure Teamcenter to authenticate against it. Covers where the IdP must live and why the two obvious placements are wrong, the issuer-hostname rule that silently breaks token validation while returning 200, the fact that Teamcenter speaks OIDC only through Security Services in federation mode, the THREE separate truststores one login crosses, and the user-id matching constraint that decides whether the job takes a day or a week. Use for any Teamcenter SSO, Keycloak, OIDC or federated-login work, and before onboarding any further application to shared identity.
• TC Subscriptions Set up and troubleshoot Teamcenter subscriptions (subscribe/notify/unsubscribe) over SOA, and keep the delivery daemons running. Covers the notification pipeline (event -> queue -> subscriptionmgrd -> email/news feed), the "Event Table renders blank until you press Find" trap that looks exactly like a broken daemon, making subscriptionmgrd/actionmgrd survive a reboot with a scheduled task, and the verified SOA operation set including the real unsubscribe call. Use for any "why didn't I get notified" investigation, or for authoring/reading subscriptions programmatically.
• TC Traceability Matrix Generate and COUNT a Teamcenter Trace Link Matrix, in Active Workspace and headlessly over SOA, including RFP Section 4 verification matrices. Covers the two ways to get an empty matrix with no error (direction is enforced, and the trace link type filter silently matches nothing), the undeclared response shape, the fact that a generated matrix is a transient view that is lost unless saved, and how a Product Configurator context makes the same matrix configurable per product variant. Use for any traceability or verification matrix, coverage figure, or "the matrix looks empty" investigation.
• TC Type Discovery And Census Discover what business object types are deployed on ANY Teamcenter tier at runtime, what attributes they carry, and how many instances of each actually exist - without a BMIDE export and without hardcoding anything per deployment. Covers the two SOA operations that enumerate the live type model, the delta-protocol trap that makes getTypeDescriptions2 return less every time you call it (and eventually nothing, which reads as "type not deployed"), the false-zero trap where a populated type reports nFound 0 because it has no object_name, the static predictor that separates a trustworthy zero from a meaningless one, proof that Teamcenter has no 500-row ceiling (that clamp lives in tc-mcp's client), and the property-tier signal that cuts 190 attributes down to the handful worth reporting on. Use for any "what types exist here", "how many of X are there", data-model discovery, BI/analytics feed, or type-picker work.
• TC Verify And Cleanup The grounding discipline for Teamcenter automation: never report an object a tool call did not return, re-verify every create, find test litter by name rather than by a uid ledger, and the retry pattern for "the instance is referenced" delete failures. Use at the end of any TC authoring session, and any time you are about to state a TC item id or status.
• TC Vm Operations Operate and maintain the local Hyper-V Teamcenter 2606 demo VM (TC2606 / guest SIEMENSDC at 192.168.222.100) - snapshots, WinRM into the guest, service and port state, credential handling, and the release-matched 2606 documentation set. Use for anything about starting, stopping, checkpointing, reaching, diagnosing or connecting to the VM, and before any install or config change inside it.
• TC Workflow Authoring Author Teamcenter workflow templates and task handlers - over SOA (createOrUpdateTemplate, createOrUpdateHandler, getRegisteredHandlers, getSupportedHandlerArguments) and in Active Workspace Workflow Designer. Covers action vs rule handlers, trigger placement, the EPM-hold pattern that makes a workflow wait on an external job, and the access-level preference that silently blinds handlers. Use for any EPM/workflow template, handler, or process-instantiation work.
• Xcelerator Desktop Ui Build a PySide6 desktop app that looks and behaves like Active Workspace, using Teamcenter's real palette rather than an approximation of it. Covers capturing the six AW themes out of a live web tier, the shell structure that makes an app read as a Teamcenter sibling, and a catalogue of ~30 Qt failures that are silent by construction: the mechanism runs, nothing is drawn, and no exception is raised. Use for any Qt/PySide6 tool that sits beside Teamcenter, for "my stylesheet does nothing" investigations, and before writing any test that claims a widget renders correctly.

Reference

• Local Teamcenter 2506 documentation sources
• Teamcenter fault and error code reference
• MCP servers behind this workspace
• Verified Teamcenter relation (GRM) atlas
• Verified Teamcenter business-object type atlas

Where to start

If you are	Read
Connecting for the first time	TC SOA Session
Getting a fault, or a 200 with nothing in it	TC SOA Payload Shapes, then the fault-code reference
Looking for the real operation name	TC SOA Docs Navigation
About to report what you built	TC Verify And Cleanup

Source

These pages are generated from the tc-automation-skills library, which is the canonical copy and is also mounted as the agent skill set for Teamcenter work. Edit the skill, then re-run scripts/publish_to_kb.py.