Teamcenter and Windchill, upgraded without breaking the BOM.
We upgrade and support Siemens Teamcenter and PTC Windchill, untangle years of customization, connect PLM to CAD, ERP and MES, and help teams weigh a move to Teamcenter X or Windchill+.
Cohash upgrades and supports Siemens Teamcenter and PTC Windchill.
We plan upgrades to current releases such as Teamcenter 2606 and Windchill 13.1, review customizations before they block the next version, build BOM and change integrations to SAP and other ERPs, and assess moves to Teamcenter X or Windchill+ SaaS. Engineers work onsite in the US, nearshore or offshore, on contract, contract-to-hire or permanent terms.
you probably need this if
The PLM upgrade has been pushed back twice because nobody knows what the custom code does.
Planners rebuild BOMs in ERP by hand because the transfer fails silently.
Designers can't check in after a CAD upgrade because the connector lags behind.
terms on this pageERPdefinitionEnterprise resource planning. It's the system finance and operations staff live in: the ledger, purchasing, sales orders, stock and often production, all in one database.explained in a field note →
01 Dec 2025Teamcenter X Standard and Advanced tiers Siemens added Standard and Advanced tiers to Teamcenter X, between Essentials and Premium. Check which one a quote assumes before you compare prices.
16 Dec 2025Teamcenter 2512 This one came before 2606. Check your upgrade path from it against the support matrix before you plan the jump.
12 Jun 2026Teamcenter 2606 AI inside PLM is one of the clearest themes here. Expect Teamcenter Copilot and the first Teamcenter agent. Collaboration and visibility got updates as well, and so did control.
today · Nov 09, 2026
no date yetWindchill 13.1.2The 13.1.2 update adds a Next Gen home page behind a New Home toggle. Its Apache configuration isn't applied automatically, so put that step in the upgrade plan. Windchill+ is the SaaS edition.
the story · siemens teamcenter & ptc windchill estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your Siemens Teamcenter & PTC Windchill estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · siemens teamcenter & ptc…3 open
openThe PLM upgrade has been pushed back twice because nobody knows what the custom code does.
recurringPlanners rebuild BOMs in ERP by hand because the transfer fails silently.
blockedDesigners can't check in after a CAD upgrade because the connector lags behind.
exposure
Teamcenter and Windchill upgradesCustomization review and clean-upCAD integrationsERP and MES integrationSaaS assessmentsPLM staffing
S/4ERP
startrehearsehandover
Inventory
Clean-up plan
Rehearsal
Cut-over and handover
we are here
ready to hand over
Most of the old code is gone from the upgrade.
Leadership decides on Teamcenter X with a clear list of what changes, what stays custom…
Every customization listed and marked keep, replace or retire, so nobody argues about it…
Upgrade runbook with rehearsal timings on a copy of production
chapter 01 · where it hurts
Why teams reach out
The PLM upgrade has been pushed back twice because nobody knows what the custom code does.
Planners rebuild BOMs in ERP by hand because the transfer fails silently.
Designers can't check in after a CAD upgrade because the connector lags behind.
chapter 02 · what we change
How we solve it
Teamcenter and Windchill upgrades
Customization review and clean-up
CAD integrations
ERP and MES integration
SaaS assessments
PLM staffing
chapter 03 · how it runs
Our approach
Inventory
Clean-up plan
Rehearsal
Cut-over and handover
chapter 04 · where you end up
What changes
Most of the old code is gone from the upgrade.
Leadership decides on Teamcenter X with a clear list of what changes, what stays custom and which programs can't move yet.
Every customization listed and marked keep, replace or retire, so nobody argues about it mid-upgrade
Upgrade runbook with rehearsal timings on a copy of production
what we do
Our Siemens Teamcenter & PTC Windchill work
6 kinds of Siemens Teamcenter & PTC Windchill work, each run by engineers who have done it on live tenants.
Version-to-version upgrades planned from an inventory of customizations, integrations and CAD versions, with a full rehearsal on a copy of production vault and database.
Server extensions, workflow handlers, listeners and UI changes sorted into keep, replace with standard or retire, so each upgrade carries less code than the last.
NX, Creo, SolidWorks and other CAD connectors kept in step with PLM and CAD versions, so designers don't lose work during the upgrade window.
EBOM to MBOM transfer, change release to SAP S/4HANA and other ERPs, and process plans to MES, with error queues someone actually watches.
A fit check for Teamcenter X or Windchill+ against your customizations, integrations, export controls and validation needs, before the vendor proposal arrives.
Teamcenter and Windchill administrators, developers and integration engineers, onsite, nearshore or offshore, on contract, contract-to-hire or permanent terms.
capability 01 / 06in production
S/4ERP
Teamcenter and Windchill upgrades
Version-to-version upgrades planned from an inventory of customizations, integrations and CAD versions, with a full rehearsal on a copy of production vault and database.
Server extensions, workflow handlers, listeners and UI changes sorted into keep, replace with standard or retire, so each upgrade carries less code than the last.
A fit check for Teamcenter X or Windchill+ against your customizations, integrations, export controls and validation needs, before the vendor proposal arrives.
Teamcenter and Windchill administrators, developers and integration engineers, onsite, nearshore or offshore, on contract, contract-to-hire or permanent terms.
Siemens Teamcenter & PTC Windchill situations we walk into
We pieced these together from Siemens Teamcenter & PTC Windchill situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Windchill several releases behind with 300 custom listeners
composite · not a client story
Beforethe situation
A machinery maker runs an older Windchill release with about 300 custom listeners and workflow expressions. Two upgrade attempts stopped in testing, and the ERP transfer to SAP fails every few days.
What we dothe work
We trace every listener to the business rule behind it and mark which ones current Windchill handles natively. The SAP transfer gets an error queue and a reprocessing job first. Then a production copy is upgraded and retested with the reduced code set.
Afterwhere you end up
Most of the old code is gone from the upgrade. Failed transfers land in a queue where planners can see them, and nobody finds out from a bad BOM anymore.
case file 02
Teamcenter on-premises and a Teamcenter X proposal on the table
composite · not a client story
Beforethe situation
An automotive supplier runs Teamcenter on-premises with NX, a custom SAP integration and export-controlled programs. Siemens has proposed Teamcenter X, and IT wants an independent view.
What we dothe work
We score every customization, integration and data control against what SaaS supports, run a pilot with one program's data, and check export control handling with legal. Then the costs of both options go side by side.
Afterwhere you end up
Leadership decides on Teamcenter X with a clear list of what changes, what stays custom and which programs can't move yet.
approach
How a Siemens Teamcenter & PTC Windchill engagement runs
We don't start a step until the last one has produced something you can check.
step 01
Inventory
We list customizations, workflows, integrations, CAD versions and data volumes, then mark what blocks the target Teamcenter or Windchill release.
step 02
Clean-up plan
Every customization ends up in one pile or another, keep it, replace it with standard, or retire it. That way the upgrade carries less before anyone touches a server.
step 03
Rehearsal
A full rehearsal on a copy of the production database and vault, start to finish. We record the timings, the CAD check-in tests and the ERP transfer tests.
step 04
Cut-over and handover
We run the production upgrade during the engineering freeze you agreed to, then stay for hypercare and leave admin runbooks with your team.
ai on siemens teamcenter & ptc windchill
Where AI fits on Siemens Teamcenter & PTC Windchill, and where it needs guardrails.
Both PLM vendors now ship AI. Teamcenter 2606 came out in June 2026, centered on Teamcenter Copilot and the Teamcenter AI BOM agent. PTC's Windchill AI has AI Parts Intelligence, AI assistants and an agentic digital thread. Results depend on clean BOMs, classification and access rules, which is where most of the engineering work goes.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
Siemens Teamcenter & PTC Windchilldoes the work
Siemens and PTC don't currently publish an official MCP server, so agents go through the Teamcenter or Windchill REST APIs as a dedicated user whose access matches the data it needs. Export-control rules apply. We log every call, and an engineer signs off on BOM or change-object updates.
Teamcenter Copilot and AI BOM agent
Teamcenter Copilot finds information and shows its context across the lifecycle. The AI BOM agent does more: it reads BOM context, proposes changes, and runs multi-step workflows while a person oversees. We check both are available in your deployment and agree who signs off the agent's changes.
Windchill AI
In Windchill, AI Parts Intelligence looks for duplicate or similar parts. AI assistants answer natural-language questions and summarize documents within access controls, and the agentic digital thread automates steps between engineering and manufacturing. Part matching is only as good as the classification data, so we clean that before switching it on.
Export control and access
Before rollout we review access rules, export-controlled programs first. An AI assistant reads whatever its user can read. If the ACLs are loose, the data is exposed.
AI around PLM upgrades
We use AI to explain old customizations (listeners and workflow expressions included) and to draft test cases for upgrades. A developer checks every single one.
architecture
Where PLM sits between design and manufacturing
Designers check CAD data into Teamcenter or Windchill, where parts, BOMs and changes are managed. Released BOMs and changes flow on to ERP and MES. Supplier packages go out from PLM, not from shared drives.
What a Siemens Teamcenter & PTC Windchill engagement leaves behind
These are working documents, written against your configuration, so your team can run them without us.
document01
Every customization listed and marked keep, replace or retire, so nobody argues about it mid-upgrade
yours to keep
runbook02
Upgrade runbook with rehearsal timings on a copy of production
yours to keep
document03
CAD and PLM version compatibility matrix
yours to keep
document04
ERP transfer spec with error queues. When a transfer fails, someone can follow the steps and reprocess it.
yours to keep
report05
A SaaS fit assessment for Teamcenter X or Windchill+, so you know what can't move before you sign
yours to keep
runbook06
Admin runbooks for the run team
yours to keep
talent and delivery · siemens teamcenter & ptc windchill
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
00:0006:0012:0018:0000:00
roles we staff
Teamcenter administrator
Teamcenter developer (ITK, BMIDE)
Windchill administrator
Windchill developer (Java customization)
PLM to ERP integration engineer
CAD integration engineer (NX, Creo)
due diligence · siemens teamcenter & ptc windchill
Questions to ask any partner, including us.
Put these to anyone bidding on your Siemens Teamcenter & PTC Windchill work. The ones who've done it answer differently from the ones who've read about it.
Q1
Our custom code is barely documented. How will you find out what each piece actually does?
PLM upgrades stall on undocumented server code. Tracing each extension to its business rule is the only way to decide what to keep.
Q2
Which CAD versions does the target PLM release support with our connectors?
CAD and PLM versions have to line up. A mismatch locks designers out after go-live.
Q3
Who finds out when an ERP transfer fails, and how do we reprocess it?
Silent BOM transfer failures cause wrong builds. Error queues and reprocessing are part of the integration, not an afterthought.
Q4
What can't move to Teamcenter X or Windchill+ in our estate?
SaaS limits on customization, integration and data residency decide the real cost. Get that list in writing before you sign the contract.
Q5
How long is the engineering freeze for cut-over, and how did you measure it?
Engineering can't stop for long. A rehearsal on a production copy is the only honest basis for the freeze length.
01How often do Teamcenter and Windchill release?
Siemens names Teamcenter releases by year and month, so 2512 came out in December 2025 and 2606 in June 2026. On the PTC side, Windchill 13.1 has maintenance releases through 13.1.4.0. Don't plan around those numbers alone. Check each vendor's support matrix for your exact path first.
02How long does a PLM upgrade take?
It depends on the number of versions you cross, the amount of custom code, CAD versions in use and how many integrations need retesting. We inventory those first and time a full rehearsal on a copy of production before committing to a date.
03Should we move to Teamcenter X or Windchill+?
Sometimes. SaaS removes upgrade work, but heavy customization, on-premises integrations, export control rules and validated processes can make it hard. We score each customization and integration for fit before you decide.
04Can you integrate PLM with SAP S/4HANA?
Yes. We build EBOM to MBOM transfer and change release to S/4HANA, using the vendor's standard connectors where they fit and custom integration where they don't. Error handling and reprocessing get as much design time as the happy path.
05Do you work on both Teamcenter and Windchill?
Yes. Many manufacturers run both after acquisitions. We can support each on its own or plan a consolidation, costed by data volume, customizations and CAD tools.
06Can you staff PLM people?
Yes. Tell us which role is open, whether that's a Teamcenter admin, a Windchill developer or someone for the integrations. We'll place them onsite in the US, nearshore or offshore, in whatever time zone your team works.
services
Related services
Projects on Siemens Teamcenter & PTC Windchill usually end up touching one of these, so they're worth a look.
Reviewed by the Cohash teamSiemens Teamcenter & PTC Windchill is a trademark of its owner, used here to identify the platform.how we handle facts and data →
next step
Tell us what you're running. We'll tell you what we'd do first.
A 30-minute working session with a senior engineer. No slides.
