If any CAD company could be diagnosed with ADHD, it would be PTC.
A company has to grow. This can be done by acquisition. I get that. But PTC's acquisitions have been... how should I say? ...varied. At its core, a CAD company, PTC has sought to grow with such diverse applications as Arbortext (desktop publishing), MathCAD, others... but most recently Altego (MBSE) and ThingWorx (IoT)
If you are wondering what those last two acronyms mean, I have proved my point.
Expansion from its core users of CAD by PTC has been explained by a very loose interpretation of "adjacent" technologies.
As expected, PTC CEO James Heppelmann, touted his recent acquisitions with an evangelical zeal to the 2,000 plus assembled at PTC Live Global. Engineers, as a rule, are not the jump-up-and-down types.
They were waiting.
Day 2, Creo 3.0
On day 2, PTC rolled out Creo 3.0. The salad plate, barely touched, is removed. Here was the meat and potatoes. Thousands of Creo users are paying attention. Veteran Brain Thompson, VP of product management, reveals what they could expect in the next release of Creo (due mid July).
Chief among the enhancements as Unite, which lets Creo read native files from major MCAD products. If you wondering "can't they all do that?" then I should have emphasized read -- versus import.
"Importing a file means making a copy of the geometry," says Brian. "We leave the file in its native format."
PTC acknowleges the need to read and write to rival CAD formats in Creo 3.0
Truly, most CAD programs will import a rival's CAD file. Nobody reads in a model in someone else's format. Until Creo 3.0.
Creo can also save as other file formats. But it is a one way street. CAD programs have typically never acknowledged a need to go back -- something users see as a trap, an arrogant assertion that if you are now where you should be all along. Why would you want to go back?
But for what may be the first time, PTC takes on a coexistence approach to other CAD systems, in effect saying that you may choose to use Creo to whatever advantage it affords, but you are free to retreat to your comfort zone, even if it is another CAD program.
Although you can read can read a file from another CAD program without translation, once it is changed (as was a Siemens NX part in a Creo assembly), the part is translated. Any design intent imparted during the change (parameters or relationship) will not be preserved when the part is saved back in its former format.
Only SOLIDWORKS, Siemens, CATIA (V5?) will be read without translation. Inventor and Solid Edge will be imported via data translation.
Not all read and write as features will be available at Creo 3.0's initial release in July, but may roll out by the end of the year.