ptc-windchill

Classify and gate PTC Windchill PLM operations across parts, CAD documents, BOMs, and change workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working in PTC Windchill (PDMLink) is risky because a Released revision is a controlled baseline that manufacturing, procurement, and service all build against. This Skill gives an AI agent the operator judgment to classify every Windchill action as read, reversible write, committing write, or destructive, so consequential actions like releasing a change, altering effectivity, or obsoleting a part pause for human approval instead of silently re-pointing the plant. ## Core Features & Use Cases - Operation classification and gating: Maps Windchill operation families (check-in, Revise, promotion, Change Notice completion, effectivity changes, Obsolete, delete, ESI publish) to read / write / destructive classes with matching approval gates. - Configuration reasoning: Explains config specs (Latest / Released / Baseline / Effectivity / As-Stored), iteration vs revision versioning, EBOM vs MBOM views via MPMLink, baselines, and Options & Variants so the agent acts on the correct structure. - Change lifecycle guidance: Covers the PR -> CR -> CN -> Change Task flow, promotion requests, workflow voting, checkout locking, contexts / domains / OIRs, and IP / ITAR export-control boundaries. - Use Case: A field failure on bracket BRK-1000 requires a design change. The Skill walks the agent through where-used analysis, raising a PR and CR, revising to a new In Work revision, applying serial effectivity from unit 5000, transforming the EBOM change into the MBOM, and completing the Change Notice that publishes to ERP. ## Quick Start Ask the agent to walk you through safely revising and releasing a released Windchill part under a Change Notice, including where-used analysis and effectivity.

Frequently Asked Questions about ptc-windchill

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

FAQPage Schema
How do I change a released part in PTC Windchill?

Released content is frozen by lifecycle policy, so the controlled path is to Revise the part to a new In Work revision inside a Change Notice. Completing the Change Notice is the release event that drives the new revision to Released and triggers downstream ERP updates.

What is the difference between iteration and revision in Windchill?

A version is revision.iteration, such as A.1 or B.2. An iteration bumps automatically on every check-in and is uncontrolled, while a revision bumps only via Revise and starts a new controlled In Work revision. A check-in is not a release.

Does an EBOM change automatically update the MBOM in Windchill?

No. The Design view (EBOM) and Manufacturing view (MBOM) have separate version streams and releases. An EBOM change must be transformed via MPMLink and the Manufacturing view re-released and published before the plant sees it.

Why is changing effectivity on a released configuration dangerous?

Effectivity re-points which revision production consumes without editing any BOM line, so changing it on a released configuration can retroactively supersede parts on already-built or shipped units. It should be gated like a supersede with the affected fleet identified first.

Can a deleted Windchill object be recovered?

Windchill has no recycle bin by default, so deleting an iteration, revision, or entire version history is permanent and recoverable only from backup. Deletion is also blocked while the object is referenced by a baseline, released structure, or change.

When should I use a Promotion Request instead of a Change Notice?

A Promotion Request only moves lifecycle state and carries no revision or change audit, so it suits governed state changes that are not formal engineering changes. Releasing changed content requires a Change Notice to preserve the audit trail.