siemens-teamcenter

Classifies Siemens Teamcenter PLM operations by risk to gate product structure and change actions.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill siemens-teamcenter-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: siemens-teamcenter
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/plm/siemens-teamcenter
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill siemens-teamcenter-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working in Siemens Teamcenter without operational judgment risks corrupting the controlled product baseline: editing released revisions in place, releasing an item revision while its BOM View Revision stays uncontrolled, changing effectivity that silently re-points which revision production builds, or obsoleting a part without knowing its where-used blast radius. This Skill gives an AI agent the operator judgment to classify every Teamcenter action as read, reversible write, committing write, or destructive, and to gate consequential ones for human approval. ## Core Features & Use Cases - Operation risk classification: Maps Teamcenter action families (revise, release, workflow sign-off, effectivity change, supersede/obsolete, publish to ERP/MES) to read / write / destructive classes with gating rules. - Configuration reasoning: Covers revision rules, precise vs imprecise occurrences, EBOM vs MBOM divergence, date/unit/serial effectivity, and variant-configured structures so the agent reads the correct structure before acting. - Change lifecycle guidance: Walks the PR → ECR → ECN/ECO flow with a worked end-to-end example, 25 real gotchas, edge states, and recovery patterns for mistakes like wrong effectivity or aborted workflows. - Use Case: A field failure requires thickening bracket BRK-100 rev A. The Skill guides raising a PR and ECR, running where-used, revising to rev B under an ECN, releasing both the revision and its BVR with unit effectivity from serial 5000, and publishing the change to ERP. ## Quick Start Ask the agent to walk through releasing a new revision of a Teamcenter part under an engineering change, including which steps need human approval.

Frequently Asked Questions about siemens-teamcenter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change a released part in Siemens Teamcenter?

Released revisions are frozen and cannot be edited in place. The controlled path is to raise a change (PR, then ECR, then ECN/ECO), use Revise to create a new working revision under that change, and let the change approval act as the release event.

What is the difference between an item and an item revision in Teamcenter?

The item is the identity of a part or document, while the item revision carries the actual structure, datasets, attributes, and release status. Almost all operations target a specific revision, not the bare item.

Why does a released Teamcenter revision still have an uncontrolled BOM?

The structure lives in a BOM View Revision (BVR) which carries its own release status, separate from the item revision. Releasing the revision does not release the BVR, so both statuses must be checked and released as a pair.

When should Teamcenter operations require human approval?

Committing writes like releasing a revision, approving a workflow, setting effectivity, or publishing to ERP need human approval. Destructive actions like obsoleting a part, changing effectivity on a released configuration, or aborting a workflow mid-approval need a named approver.

Does changing effectivity in Teamcenter edit the BOM?

No. Effectivity re-points which revision production consumes for given dates or unit serial numbers without touching any BOM line. On a released configuration this is a high-blast change treated like a supersede and gated as destructive.

What happens if a Teamcenter workflow is aborted mid-approval?

Aborting a workflow returns the object to Working state and permanently loses all accumulated sign-offs. The workflow must be restarted from the beginning, so it should never be aborted just to fix one field.