The Future Of CoCreate

In order to shed more light on my post titled “The Creo Product Strategy“, Mike Campbell, PTC’s DVP of Creo Product Development, sent me an email containing the following clarification.

==== x ====

What about CoCreate (or Creo elements/direct)?

Click image for larger view

In the attached second slide, you will notice that we are planning another release, next summer of the Creo elements/direct (CoCreate) products. (To be clear, there will NOT be another release of Creo elements/pro or Creo elements/view. Those products are being replaced by Creo immediately.)

The reason for this is that the Creo elements/direct product capabilities are quite broad, and it will take us a while to completely map all of those capabilities, and the associated data, to the new Creo Common Data Model. Not only does Creo elements/direct provide Direct Modeling, including parts, Assemblies and Sheetmetal parts, but there is support for FEA, Moldbase design, routed systems, and so on.

In order to continue to improve those products, and incorporate the changes needed to accommodate that data compatibility, we will continue providing new releases of Creo elements/direct. These new releases of Creo elements/direct will include the new top-level Ribbon UI, consistent with the rest of Creo, as well as improvements around Windchill PDMLink integration and other functional enhancements to the products. We will also be focusing quite heavily on supporting the 100% compatibility of data and working methods that we have committed to for Creo elements/direct customers. On the slide, you will notice orange arrows, indicating the ability to move some data seamlessly (initially, geometry, and geometric meta-data, such as thread definitions, for example), and then broader arrows in the future (at 18.1) indicating more and more application-specific meta data will be compatible with Creo.

The details of exactly what Creo elements/direct capabilities and meta-data will be seamlessly accommodated in Creo are yet to be determined, but this will likely be a multi-release process. We expect that some customers will find the capabilities acceptable to them, and will be able to move to Creo in the first and second Creo releases, while others, with more sophisticated use of Creo elements/direct may want to wait until that “bridge” is wider, and more of their data can seamless move to the new platform. We have no plans to sunset Creo elements/direct at this time, and expect a 19.0 and 20.0 release and so on.

==== x ====

Mike also asked me to note that these are the plans for CoCreate as of today. He wrote to me, “They reflect our current plans, but these plans are of course subject to change“.

  • Neil

    My brain is fogging and my eyes are glazing reading this.
    Couldnt they have just called it Procreate or something…

    • stirring the pot a little

      It seems like the CREO benefits for cocreate users aren’t going to be realized for a number of years. …And, if one stays with “elements direct” for the next few years, is PTC truly doing to continue to improve the product, considering that the product will go away eventually? Yes, they will change the GUI somewhat, but what about all of the other shortcomings of the cocreate product line?

      • I don’t think PTC will be doing anything significantly different with CoCreate for the next few releases. And I don’t think they should either since the plan is to merge paths with Creo. Having said that I think you will see significant changes in terms of adding capabilities to CoCreate which will aid in the merging of the two paths. That, in itself, can have a lot of value. My point here is if CoCreate users have a little patience, some really good things may be in store for them in the future.

        • foo


          “…if CoCreate users can have a little patience…”

          the problem is that cocreate users have been patient for a number of years pre and post aquisition…CREO has been unveiled and CoCreate customers are in line behind the Pro/e customer base. And why not? Creo was the hope for cocreate customers that they would be rapidly getting on the same platform as the bulk of PTC customers….but it turns out that is not the case.

          • To be fair, I think its much easier to add direct modeling to Pro/ENGINEER than to add history based parametric modeling to CoCreate. So it makes sense for PTC to keep Pro/ENGINEER as the base platform on which to grow other stuff. I know that may sound a bit off to CoCreate users, but if you look at the long term, if PTC pulls this off, I think its all good.

          • foo

            I completely agree with your point that pro/e should be the core that is retained, but with explicit modeling added.

            I simply point out that asking cocreate customers to wait a few more years on top of the last few of underwhelming improvement is too much to ask.

            CoCreate mgmt prior to PTC underspent in R&D in the last few years, PTC underinvested as well. To make up for this, PTC should have spent the necessary $$ so that CoCreate Customers would be guaranteed to have the functionality they need in CREO 1 or 2 at the latest.

            They have not done this, so in the end cocreate customers continue to pay the price of underinvestment.

          • Being part of CoCreate and PTC for the last 10 years, I’ve seen first hand the increased investment PTC has made into CoCreate (now Creo Elements/Direct) and it’s tight integration into PTC’s other product families. This has served many customers well, from using MECHANICA technology for advanced structural analysis, to tight integrations into Windchill, and many other PTC solutions CoCreate customers can now enjoy and take advantage of.

            Let’s also not forget our major release (17.0) delivered a new wave in user productivity this year, with independent testing showing a factor 2 increase in design productivity.

            I’m sure some customers will see the opportunity to move to Creo 1.0 or Creo 2.0. But we also want to make sure all designs, however rich, can be smoothly migrated to Creo from Creo Elements/Direct, and I know many of our customers expect that – and PTC is committed to it.

          • What does a “factor 2 increase in design productivity” mean? Is it meant to imply that users are twice as productive with the newest release?

          • charlie

            Sorry, I ‘m not aware of any “tight integration to Windchill”? There is no WGM for CoCreate Modeling available until Autumn of next year. Are you referring to the “gateway”? You consider that tight? Or maybe you are referring to wgm for cocreate drafting? Of what benefit is that to most customers, who are on 3D? PTC made that product because it was extremely easy to develop, thus making it of little development cost of effort.

          • Greg

            As a long time CoCreate user I have little desire to get on the same platform as the bulk of PTC customers. They’d be welcome to get on the same platform as us. . .

  • Pingback: The Creo Apps |

  • Poor CoCreate… i mean Solid Designer… i mean One Space Modeling… i mean Creo Elements/Direct. This many name changes is not good for a product, imo!

  • Pingback: Creo Explained – Part 6 |

  • Anonymous

    Now, the WGM for CoCreate Modeling is out……… now CoCreate Modeling can connect to Windchill by WGM or by Gateway….

  • Pingback: The Dassault Systemes And PTC Modeling Kernel Problem |

  • Brandon Lackey

    As a user of the software I can tell you there is no productivity improvement in version 17. I am open minded and liked the concepts and used them on a regular basis for a while. The new commands seem extremely glitchy to me. After loosing no telling how many hours of work i finally resorted to using the classic commands and have not had any issues since switching back.