Code is the last tool we reach for
Most requests can be met with the standard model: types, attributes, numbering rules, lifecycles and workflow templates. We always check that route first, because every line of custom code is a line someone has to carry through the next upgrade.
When code is the right answer, it is a small, focused module with one job, a named owner and a reason written down next to it.
How a customization is built
- Under version control, in a repository you own, with every change reviewed by a second engineer.
- By a pipeline, never compiled on a server or copied in by hand.
- With tests that run against a disposable Windchill instance before anything is promoted.
- Into an inventory that records what it does, which parts of the product it touches and who maintains it.
Typical work
- Numbering and naming rules that go beyond what the standard settings can express
- Change workflows with parallel reviews, delegation and escalation timers
- Release checks that validate a BOM before it can move to the next state
- Reports and dashboards built on Windchill data
- Administrator tools: bulk loaders, mass updates and clean-up jobs
Upgrade-safe by design
We build on supported extension points, never edit PTC’s own files, and register every override in the inventory. When the next release arrives, upgrading the customizations is a rebuild and a test run, not an investigation.