Integration first, customization second
Most requests for “customization” are really integration gaps: engineering data that needs to reach ERP, or ERP data that engineers need to see. We solve those with governed, monitored integrations before considering changes to Windchill itself.
What we build
- ERP synchronisation with explicit attribute ownership, error queues that someone actually watches, and reconciliation reports.
- Windchill REST Services and OData endpoints for downstream tools, dashboards and internal apps.
- Workflow and UI extensions built on supported extension points, packaged so they survive upgrades.
- Software and firmware links so a hardware revision knows which software versions are compatible.
How we keep it maintainable
Every customization is a versioned artefact with automated tests, a runbook and an owner, and it reaches production through the same CI/CD pipeline as PTC releases. We review the customization inventory with you once a year and retire what standard Windchill now does better.
Where we have done this
Custom workflows, integrations and data-model extensions for engineering teams at Thales, Airbus, BMW and Benteler, in environments ranging from a few hundred to several thousand users.