Start with ownership, not with interfaces
Before any mapping, we agree who owns each piece of product data: where a part is born, which system holds the released BOM, where cost and plant data live. A one-page ownership map settles most integration arguments before they reach the code.
Patterns we use
- Events on release. When a change is released in Windchill, an event carries parts, BOMs and documents to ERP. Nothing is pushed half-finished.
- Lookups on demand. Portals and apps read live Windchill data through web services instead of keeping their own copies.
- Nightly reconciliation. A scheduled job compares both sides and reports any difference before a planner finds it.
Built to be operated
Every message is safe to repeat and easy to trace. Failures are retried automatically, set aside in a queue when they cannot succeed, and shown on a dashboard your support team can read. Nobody has to search log files to learn why a part did not reach ERP.
Common integrations
- ERP systems, through PTC’s standard connectors or an integration layer
- MES systems for work instructions and as-built data
- ALM tools for requirements and software configuration
- CAD tools, so designers save and release straight from their own environment
- Supplier and customer portals with controlled, read-only access