1. Windchill depth, not PLM breadth
Ask how many Windchill implementations the firm has delivered, on which versions, and in which modules — PDMLink, MPMLink, ProjectLink, Windchill+. Then ask which of those the people who'll be on your project delivered. A firm with a deep bench on Teamcenter and two Windchill projects is a Teamcenter firm.
How Element fits: Windchill is nearly all of what we do. 100+ implementations since 2003, PTC Certified Windchill Implementation Practitioners on the team, and the same people who configured the last system configure the next one.
2. Real implementation experience, not configuration experience
There is a difference between a consultant who has configured Windchill and one who has lived with the consequences. Ask for an example of a decision they made in configuration that turned out to be wrong, and what they changed. A firm that can't answer that has never stayed long enough to find out.
3. Industry depth in your industry
Aerospace and defense, medical devices, automotive and industrial equipment each impose different requirements on Windchill — ITAR data controls, FDA design-history-file traceability, PPAP documentation, engineer-to-order configuration. A partner should be able to describe the specific Windchill configuration decisions your industry forces, before you tell them.
How Element fits: Aerospace & defense and medical devices are the majority of our work. We deliver in ITAR-controlled and government-cloud environments, and the Windchill configuration for AS9100 and 21 CFR 820 traceability is work we've done repeatedly, not work we'd be learning on you.
4. Integration treated as part of the implementation
Windchill does not run alone. It connects to ERP — SAP, Oracle, Dynamics — to MES, to CAD, and often to QMS. A partner who quotes the Windchill implementation and treats integration as a later phase has quoted half a project. Ask which ERP integrations they have delivered and how — PTC's ESI framework, middleware, or custom — and what went wrong on the last one.
How Element fits: ERP–PLM integration is a core service, not a partner referral. We have delivered Windchill to SAP, Oracle and Dynamics 365, and the failure points on each are documented on this site because we've hit them.
5. A data migration methodology they can describe
Migration is where implementations go over budget and past deadline. Ask how they handle legacy CAD relationships, duplicate part numbers, revision history, and what "clean" means for your data before it goes in. The right answer includes a pilot, validation scripts, and a stated position on how much history to migrate versus archive.
6. An explicit adoption plan with a name on it
Most Windchill implementations are technically complete and practically unused. Engineers keep working in Excel; manufacturing doesn't trust the BOM; "phase two" never happens. Ask the partner what adoption looked like at their last three go-lives, six months later. Ask who on their team owns organizational change management — not training, change management — and what that person does.
How Element fits: Process and people first, technology second. It's the order we've used on every implementation, because a Windchill system nobody works in is a very expensive document repository. We have OCM leads on staff, not a training deck.
7. Independence and knowledge transfer
When the partner leaves, you should own the configuration, the documentation, and enough internal capability to run the system without calling them. Ask what the handoff looks like. A firm that's vague about this is planning to be your permanent administrator.
How Element fits: We train your champions, document everything, and aim for you not to need us. That's also why clients come back for the next project — because the first one worked.