L. Stephen Wolfe, P.E. (contributing analyst with Jon Peddie Research), recently posted some great questions regarding Creo. Here’s his 8 questions with our answers, and where possible, we’ve also included video answers from Mike Campbell, DVP of Creo product development at PTC, offering a more in-depth explanation. I’ve summarized his answers in words (for you skimmers), but you’ll want to view the complete videos for full details.
1. What will be the upgrade paths from the Creo Elements (a.k.a. Wildfire 5 M080) packages to Creo application suites?
Every Creo Elements product, package, and extension has an upgrade path to Creo, for example, a customer with Creo Elements/Pro on maintenance has the option to upgrade to Creo Parametric, a customer with the Creo Elements/Pro Foundation will have an upgrade path to a package of the corresponding Creo Parametric capabilities, and so on. At a minimum, the upgrade to Creo offers the same product capabilities as the customer has today, and in many cases, adds new capabilities.
As part of the release of Creo 1.0, we’ll publish a ‘product mapper’ to detail every product, package, and extension and how it maps to Creo. Mike discusses the approach to protecting a customer’s existing investment in the second part of this video FAQ.
2. How much will it cost (in both initial charges and annual maintenance fees) to upgrade each Pro/Engineer or CoCreate user?
There is a no cost upgrade for existing maintenance customers to each target Creo app, extension, or package. There are no increases in annual maintenance fees when the customer selects the no cost upgrade.
3. When will the Creo apps have all the equivalent capabilities of Pro/Engineer Wildfire 5?
PTC is committed to protecting the investment customers have already made, and all data, working methods, and capabilities in Creo Parametric are equivalent to or deliver more than the capabilities found in Creo Elements/Pro 5 (Pro/ENGINEER Wildfire 5) today.
4. How consistent are the user interfaces across all the Creo apps?
While the Creo apps are standalone programs, they have a common look and feel for key areas. The Ribbon presentation is common across all Creo apps, and when commands are common (like File Open, and Close, for example) they are presented in the same way and in the same place.
5. Will all changes made using direct-modeling techniques be represented as dimension-driven features in Creo Parametric? Or will changes made with direct modeling have to be recreated in the parametric program?
Changes made in the direct modeling approach do not have to recreated in the parametric approach; all changes made in the Direct Modeling app are simply represented as additional changes (features) in the model when it is viewed in the parametric modelling app. The user of the parametric app can choose to either accept, and incorporate these changes permanently in the model (by persisting the new features in the model), or review them and reject them entirely.
6. Are there direct edits that will cause parametric features previously created to fail?
No. All changes made via a direct modeling approach can be captured within the parametric model without a failure.
7. What changes to the company’s Windchill PDM or Intralink software will be required to support Creo?
Creo 1.0 apps are compatible with Windchill 9.1 M062 and 10.0.
8. How much retraining will be required to use Creo?
For existing users of Creo Elements/Pro (formerly Pro/ENGINEER), they should think of this upgrade as they would have a significant release of Pro/ENGINEER in the past. Many companies are planning ½ to 1 day training.