Engineering and manufacturing software is full of interesting TLAs that companies continuing to invent even these days. Only yesterday GrabCAD introduced Workbench enhancement under somewhat that can be considered as a very traditional name – Collaborative Product Development (CPD) Platform.
Chad Jackson, my long time blogging buddy published an article with fascinating title – ENOVIA Data Management: Less PDM-ish, More PLM-ish. Chad made a review of Enovia data management capabilities from Dassault System briefing. Read the article with multiple embedded tweet-quotes. Besides playing PDM vs. PLM naming game, article brings an important perspective of where Enovia data management architecture is going. Here is an interesting passage I captured:
CAD models have never been simple files. Lots of stuff have been, and continue to be, jammed into them. They contain far more than just geometry. They contain part numbers, so drawing BOMs populate automatically. They contain material properties, such that mass properties can be calculated. Over time, as more and more enterprise considerations needed to be taken into account, more non-geometry stuff has been jammed into CAD files. The problem with all this stuff in CAD files was that, unlike many other types of files, operating systems couldn’t understand the structure of information in CAD files.
So, what Enovia is doing differently? According to Chad’s comments –
Dassault Systèmes are trying to liberate all that stuff jammed into the CAD file. Here are some notes from my briefing with them. In short, they are taking non-geometric items in CAD files an turning them into meta-data that lives in ENOVIA. They are being turned into individual pieces of information that can be modified separately and independently from every other piece of information and the geometry. Of course, this meta-data is related and will live as a database item right alongside the file that contains the geometry.
It made me think about future trajectories of CAD/PDM/PLM integrations. I’ve been describing possible options in one of the posts last year – Multi-CAD PDM integrations: yesterday, today and tomorrow. The idea of CAD/PDM bundle I expressed there is in my view a reflection of what CATIA/Enovia is doing in data management. As I mentioned there, it solves the problem of version compatibility as well as provide a significant advantages in terms of functional richness. This is exactly what Chad demonstrated with CATIA/Enovia examples.
What is my conclusion? Integration remains a place where lots of innovation is happening. CAD, PDM and PLM integrations is a very challenging space. Customers have a huge demand to have vertically integrated product providing sufficient amount of features and what is mostly important a completely new level of user experience. It sounds like we can see more investment in this space coming from traditional vendors. CAD/PLM companies will try to integrate existing products into vertical suites connecting data and providing support for integrated product scenarios. Just my thoughts…