PDM was long time a step child for many CAD systems. To deal with CAD files, their relationships and dependencies including multiple revisions of document was complex and painful. So, many customers just gave up and stored files on shared drives. It was okay until the our life was disrupted by a new way to get work done – online, connected, collaborative.
The initial intent of collaborative cloud systems was to solve the problem of collaboration and data sharing. The idea to provide a value on top of existing CAD desktop file systems was interested. So, specialized cloud CAD file sharing and collaboration systems got focus and attention.
At the same time, CAD vendors got to think about longer term solutions. CATIA was one of the first systems that announced the disconnect from a traditional file systems. I posted about that few years ago – The future of CAD without files.
These days, the race towards cloud CAD is accelerating development of data management and CAD collaboration technologies for the cloud. Few weeks ago, I shared some of my thoughts about importance of PDM technologies for cloud CAD. Cloud CAD vendors are clear about their intent to make PDM part of their core product technology.
My attention caught Autodesk Fusion360 article – Fusion System Architecture Changes Coming in the Next Release – Why and What. Read it, because it contains some very interesting pieces of information about how files are going to disappear into future cloud infrastructure. Here is the passage I captured:
With the coming release of Fusion, we will be introducing significant changes to Fusion Cloud Service architecture that lays a strong foundation on which we can build an environment that is rich in WIP DM. As part of this change, we are introducing the Autodesk Work In Progress Cloud Service which is designed to model and manage complex relationships that are associated with a design. The service is highly scalable, highly available and optimized for performance. Another important change in the February release is significant improvements to the Fusion Object Storage Service. Taken together, these changes will result in immediate benefits in the way of performance gains and high reliability in the Fusion upload and download data pipeline, and allow the Fusion team to deliver rich DM workflows in subsequent releases.
Another article from Fusion360 blog brings an excellent explanation what these date services mean for end user. These are functions that belonging to PDM system in a traditional file based CAD / PDM setup.
…it solves so many common design problems that we’ve heard from the community, both in Fusion 360 and other programs, and improves workflows for both teams and single designers. Branching and merging lets you easily:Work in parallel with other members of your team. Explore changes or alternatives to a project and keep changes that make sense while leaving behind changes that don’t. Understand how your project evolved over time and what decisions were made (and why). Restore or reuse any design(s) in your project from any point in your project. Use any point in your project as a starting point for a different project.
What is my conclusion? It is hard to bring a value of cloud design collaboration without re-thinking the way CAD-PDM bundle is operating. For new type of cloud CAD systems it means to embed core PDM collaborative function and make it part of CAD system. It sounds like a very exciting time- many collaboration and data management problems are going to be solved by that. However, here is a question. What will happen when two cloud CAD systems will have to collaborate together? Looks like a topic for another blog. Just my thoughts…