ENOVIA V6 Multi-CAD: Do Everything!

April 1, 2012

Note, this is NOT 1st April post :). Multi-CAD and PLM. Endless story… Few weeks ago, I published my post The Anatomy of MultiCAD-PDM integrations. I recommend you to have a read before you continue with this article. Another blog, you probably want to review is the story about Autodesk Vault and Multi-CAD. This blog is also continuation of the discussion I started in the following posts – Immersive CAD management: is it the CAD/PDM future?, CAD Strategies: Unified or Diversified and CAD, PDM and PLM diversity.

So, this week, I’d like to make a next step and talk about Dassault Enovia and multi-CAD. Again, as before when I talk about Autodesk Vault, my focus is on the integration between PDM/PLM platform and CAD. I’m not focusing on CAD data translation, visualization. Don’t take me wrong- data translation is important. However, I’d like to keep my focus on how data-management platform interact with CAD applications.

A week ago, I sat down with David Segal of Dassault Systemes to talk about Dassault Enovia and MultiCAD. This blog gives you some ideas about how Enovia presents their Multi-CAD integration and openness. He kindly provided me with some slides about Enovia V6 multi-CAD and gave me explanations about how Dassault Enovia supporting different design applications.

In my view, the usual complexity, every CAD/PLM vendor has is about how to separate their own CAD solutions from "other vendor CAD" solutions. Dassault is calling it "authoring applications". So, on the following slide, you can see how ENOVIA V6 chart pictures about data-management strategy. I had hard time to go and understand the difference between "comprehensive collaborative solution" and "collaborative data-management solutions" for MCAD and ECAD. What was important to understand is that Enovia is not limiting their offer to Dassault CAD applications only. In addition, interesting to see that CATIA V6 and SolidWorks are positioned on this slide in the same box.

ENOVIA multiCAD data management

Another aspect is related to mechanical and electronic design applications (so-called MCAD and ECAD). The complexity of products is growing. You can hardly limit yourself to only mechanical aspects of the design. In that context, Enovia V6 supports both MCAD and ECAD spaces. You can see a chart below explaining MCAD solution offering.

MCAD Data Management

Another one related to ECAD options.

ECAD Data Management

I’ve got mixed feeling about these slides. The simple message is clear. Whatever CAD you do have – Enovia supports it. At the same time, what I learned the user experience and functionality of the integration are very important. The level of diversification in design scenarios and practices is very high. So, to see what is supported is something that important to understand. It is always interesting to see some performance in action. Take a look on few videos below for more examples.

NX Collaboration

ProE Collaboration

ProE ECO Implementation

MCAD-ECAD with Cadence

What is my conclusion? I made my short conclusion in the title of the post – Do Everything! I can hardly find the name of design system / CAD not covered by the slides. It is a good sign, since it allows the flexibility for user to choose tools and don’t lock customer on DS tools only. However, don’t take it blind and compare functional details in case you decide to go to one of them. Blog post is a wrong place to make functional comparison, but details are important. Remember that. Moreover, to support different versions of CAD applications is as well important. I can see how Dassault is doing a lot to make ENOVIA capable to be connected to any design applications and looking forward to learning about your experience. Speak your mind…

Best, Oleg

Disclosure: This post was reviewed by David Segal (DS) before publishing.

Aras, SolidWorks and Disruptive PLM Strategies

October 27, 2011

BAM! Aras just announced Enterprise PLM for SolidWorks. Here is the new article –Enterprise PLM for Enterprise PDM. Navigate to the following article to read more – Open Source Aras Releases Commercial PLM Solution for SolidWorks. Here is the short conclusion made by Randall Newton: Our assessment: Aras just plugged a huge hole in the SolidWorks marketplace, one as big as the product name is long.

Fast rewind back in 2010. SolidWorks World 2010. Anaheim, CA. SolidWorks is announcing about their future products on top of Enovia V6 platform. During that event SolidWorks made multiple mentioning of Enovia V6 to be used as a platform for future enhancements of SolidWorks. Here is the passage from razorleaf’s blog summarizing SolidWorks World 2010:

SolidWorks has a new product line, SolidWorks PLM. This line will include a number of offerings, thefirst of which is cloud-based data management named SolidWorks Product Data Sharing (PDS). This software was demonstrated on the last day of the show, operating right inside of SolidWorks. For those paying close attention, the PDS plug-in showed a label, “powered by ENOVIA V6.”

Now rewind seven month ago. SolidWorks 2011. I posted – Integrated PDM and PLM: Wrong Question? This blog was a follow up on the conversation and presentation made by Jonathan Scott of Razorleaf about SolidWorks Enterprise PDM and ENOVIA V6 integration. Slides are still here.

The interesting comment to this post was made by Marc Lind of Aras:

My sense is that the future will be about leveraging existing systems / data, like legacy PDMs, with more modern technologies to enable global processes, cross-functional collaboration and new ways of doing business. Our “view” at Aras is: Use the latest PLM technology to automate what makes economic sense, gets results quickly and gives you control over your own destiny.

I had a chance to meet Aras booth during SWW 2011. Aras presented a co-existance between Open Source Enterprise PLM and EPDM (see photo in the beginning of the post)

Another rewind. April 2011. ACE 2011 (Aras Community Event). After digesting all ACE 2011 materials and presentations, my clear conclusion was – Aras PLM lines up against Windchill, Enovia and TeamCenter. Navigate to my earlier blog to see slides presented Aras. The integration capabilities of Aras were clearly outlined and existing PLMs were presented as “PLM Legacy”.

Here is the quote from my blog post:

Integration is an important element of every PLM strategy and implementation. There are multiple aspects of integrations – desktops, CADs, PLM systems and ERP systems. Aras presented a very broad scope of integrations and integration technologies. (note: I was a bit surprised to see existing PLM systems defined as “legacy”)..

Aras Enterprise PLM vs. Enovia V6

The Enterprise PLM offering by Aras is pretty straightforward. Aras is going after 3 key areas – Engineering Bill of Material management, Change Management and Project/Portfolio Management.

All these modules are available in Enovia V6 portfolio – Enovia Engineering Central and Enovia Program Central. Now, customer can make a decision.

What is my conclusion? Aras is clearly playing a role of a disrupter on PLM market. Back in 2007, Aras disrupted PLM first time by introducing Open Source PLM. It looks like Aras is on the way to make a second disruption among large companies using SolidWorks and taking a role of Enovia V6 in a bundle EPDM / EPLM. Enovia clearly has a technological advantage of having unified development forces in their new Dassault facilities in Waltham, MA to develop “best in class” Enovia V6 / SolidWorks EPDM integration. The speed of customer adoption will be a key factor for Aras. Just my thoughts…

Best, Oleg

Integrate PDM and PLM: Wrong Question?

February 9, 2011

Two weeks ago, during SolidWorks World 2011, I had a chance to talk with Jonathan Scott of Razorleafabout different aspects of integration between SolidWorks Enterprise PDM and Enovia V6. Navigate to the following link to see Jonathan’s presentation online. These slides as well our conversation made me think about trajectories of different product data management systems and environments in the context of the overall software lifecycle in manufacturing organization.

PDM as a PLM Foundation

Few years ago, I had a chance to read SolidWorks White Paper about PLM. You can navigate to the following link to retrieve this document. The concept of "PLM: It starts from PDM" was crafted very well in this paper. Thinking more about this concept I can see a very interesting approach of PLM implementation- to start from existing PDM solution. The potential advantages of this approach can be to prevent unnecessarily migrations between systems and shorten implementation cycle. PLM system connected to PDM system can re-use data foundation to manage CAD files lifecycle, Bill of Materials, change management.

CAD Files and BOMs

These are two entities that always raises lots of discussion during PLM implementations. Multiple CAD systems create significant difficulties for PLM implementation and making ROI much longer than expected. Management of multiple Bill of Materials, tracking changes between different BOM views can be an additional complication in front of PLM. What if product data management system, which already in place (from CAD vendors, homegrown or any other) can provide this solution? The starting point of PLM implementation will not be anymore to start managing CAD files.

Collaboration and Process Foundation

A significant portion of a product lifecycle is to support people in their way to run product development, exchange information and making decision. Most of this work today relies on IT infrastructure available in the organization – mail, shared workspaces, instant messenger and more. Business process management software (if any in place) rarely covers product development processes. Companies thinking about product development process improvements have a very long way to go until PLM implementation actually coming to the stage of quality management, cost management, compliance, regulatory and more. A new approach in PLM implementations can be to start from this stage and leveraging existing PDM infrastructure.

What is my conclusion? Software has a long lifecycle in manufacturing companies. I found the lifecycle of PDM/PLM software systems is very complicated. Actually, it is as complicated as the product lifecycle they are managing. To change existing systems in a company can be a very costly decision. To re-use existing systems can be a complicated from the technical standpoint, but can lead to a faster ROI. It makes sense to me. The cost of integration can be a key in this story. So, a potentially "wrong question" can lead to the right answer. Just my thoughts…

Best, Oleg

Technia and PLM Implementation Secret Sauce

November 16, 2010

The following announcement came to my attention yesterday. Technia annouces Technia Value Components Release 2010-3 future increase the value of ENOVIA. I found it interesting. Technia is a Sweden outfit with a deep and diverse set of skills of PLM implementations. Technia came to my attention first time as a reseller of MatrixOne (acquired by Dassault in 2006). Technia relations with MatrixOne have a long history of customer implementation and development.

I specially liked the following passage from the announcement:

With the experience from +50 larger PLM implementations, Technia seized on the fact that many organizations request similar customizations of their ENOVIA/MatrixOne systems. Technia developed the TVCs to componentize these common changes and streamline implementations. TVCs not only close the gap between requested and out-of-the-box functionality, but also reduce the time and cost required to investigate the impact of each change. This leads to faster implementations with lower risk, as well as reduced Total Cost of Ownership.

Implementation Toolkit?

Navigate your browser to the following link to see the overal portfolio of TVC and look on the list of TVC components: Structure Browser, Graphic Report, Grid, Personal Browser. You can request demo or AVI of a specific component.

Thinking about the component list, my hunch is that this is a toolkit that can be used to handle various types of implementation use cases. There is no visual resources on the website. Grid and structure browsers, XBOM, Office, Report generator, etc. – all these components demonstrate a toolkit approach. I believe Technia engineers utilized a deep knowledge and experience of almost a decade of implementations.

PLM Portfolio and Implementation Toolkit

In the early beginning, a typical PDM / PLM product was a toolkit based implementation. Going back to Metaphase or MatrixOne, most of the implementations were done this way. However, for the last decade PLM mindshare leaders developed a significant set of PLM portfolios. The combination of out of the box products and toolkit approaches is the most critical element of successful implementations. To have a right balance can be very helpful, especially if you think about future product upgrades. Too much toolkit approach and your future PLM upgrade becomes a bloody mess. It looks like Technia engineers invented something special in their way to implement TVC together with ENOVIA V6. I hope to learn more about this in the future.

What is my conclusion? To combine a "toolkit approach" and major product portfolio of mindshare PLM vendor is a very interesting problem to solve. Based on what I learned from the press release and by combining this information with TVC list on Technia website, Technia engineers invented some "secret sauce" of combined implementation. These two approaches are orthogonal and requires intelligent methods to be applied to solve them. My hunch TVC is used to expand ENOVIA portfolio in the spaces where customization is required. Just my thoughts…

Best, Oleg


Get every new post delivered to your Inbox.

Join 290 other followers