Posts tagged as:

Dassault

ds-solidworks-cloud

The race towards CAD in the cloud is getting more interesting every day. I’ve been watching SOLIDWORKS World 2015 live streaming this morning. Overall SOLIDWORKS show was very impressive, as usual. I look forward to keep watching it following days.

However, what caught my special attention today is a presentation of a new cloud product – SOLIDWORKS Industrial Design. Couple of interesting facts about new product  - works on top of Dassault 3DEXPERIENCE platform (in many aspects, think about it as ENOVIA V6); focus on free design with no traditional CAD constraints; leveraging cloud approach for social connection between users and collaboration. And… it is complimentary for SolidWorks users. Demo of product presented few scenarios in which design flow went between new cloud product and old SolidWorks connected by 3DEXPERIENCE platform. Sounds like a big deal.

The story about new SOLIDWORKS/3DEXPERIENCE product took me back to my comparison of Onshape and Autodesk Fusion360 visions few days ago – Carl Bass and Jon Hirschtick are in agreement about future of CAD. In my view, changes in design world towards distributed teams and ability to work effortlessly on any device without installation and manual upgrades are two main driving factors behind new cloud solutions. The story about Autodesk Fusion360, Onshape and SOLIDWORKS made me think about interesting priorities all creators of cloud CAD are thinking about. It was well articulated during SolidWorks World 2015 first day keynote –  supporting any device, information is up to date all the time, users are connected (see picture above).

It makes a perfect sense to me, since it is a great reflection of modern cloud paradigm you can see well developed in products such as Google Apps, Office 365 and others. However, this is a place where complexity of CAD data requires from cloud products to be more sophisticated. Traditionally, CAD project is combined of multiple files – assemblies, parts, drawings, etc. As you start making changes you very quickly end up with a complexity of many-to-many relationships between different versions of parts, assemblies and drawings. Move it to the cloud – the complexity won’t disapear.  Therefore, you can see both Autodesk Fusion360 and SolidWorks Industrial Design are trying to solve. I had no chance to see Onshape product yet, but my hunch Onshape will try to solve this problem too.

Autodesk Fusion360: revision control, branching and collaboration

autodesk-fusion360-rev-branchescarl-bass-fusion-360-au2014-2

SolidWorks Industrial design: 3DEXPERIENCE collaboration, branches, revision merging

solidworks-industrial-design-1solidworks-industrial-design-2

What is my conclusion? In a traditional CAD world, the problem of file revisions, collaboration and data control was part of PDM solution. Historically, CAD vendors were reluctant to solve PDM problems unless it became absolutely necessarily. PDM was complex, required services, special pre-sale process, etc. However, cloud is creating a new demand and constraints for new CAD in the cloud paradigm. With the absence of file system exposed to end user, cloud CAD system will have to solve a PDM problem first. Just my thoughts…

Best, Oleg

Share

0 comments

cloud-pdm-paradigm

Integration of CAD and PDM is a field with long history of battles, innovation and failures for the last 15-20 years. You can hardly undervalue the importance of integration between CAD and data management tools. For some time in the past CAD and PDM were separate systems. Engineers had to switch from CAD to PDM to perform specific tasks related to data management functions. To integrate PDM tools inside CAD was one of the greatest ideas of 1990s, which improved significantly what we call today “user experience”.

However, the complexity of data management interfaces was always something that made engineers uncomfortable. Another innovative approach that was introduced in the field of integration between CAD and PDM was to embed PDM tools into File Explorer user interface. One of the companies that did it back in 2000s was Conisio (later SolidWorks Enterprise PDM). The idea got lot of traction and allowed to engineers to work with a familiar file based interface while in fact using PDM tools.

People are hard. Especially, when it comes to adopting of new paradigms. Dassault System blog SOLIDWORKS and PLM: No Fear Required brings an interesting perspective on integration between ENOVIA PLM and SolidWorks.

3DEXPERIENCE platform offers a fresh approach to this problem. Recognizing that our existing Enterprise PDM solution has been greatly accepted by the design community, the same R&D group has designed a new product that offers the usability of EPDM but actually stores the data in a broader and more capable PLM solution. The result is the SOLIDWORKS Collaborative Innovation Connector, a product that works and acts much like a workgroup solution would but gives the designer just enough access to the PLM functionality to innovate their processes beyond what they can do today in a PDM environment.

The following video is one of the confirmation for that. You can see how ENOVIA PLM traditional web interface is morphing to provide File-Explorer user experience for SolidWorks users. What I found specifically interesting is that you can hardly distinguish between ENOVIA PLM and SolidWorks EPDM, which has very similar user experience for both file explorer and SolidWorks UI.

 

The video about ENOVIA SolidWorks integration made me think about what can be a new PDM paradigm as we move forward into cloud future. I’d like to bring few references to new products and companies in that space – GrabCAD, Autodesk Fusion360 and Onshape.

Fusion360

At recent Autodesk University in Las Vegas, Autodesk CEO Carl Bass presented the evolution of Fusion360 and its connection with cloud services such as Autodesk A360. According to Carl Bass, you can think about Fusion is a GitHub for engineers. Combined with A360, Fusion is a full digital re-imagination of how designers and engineers will collaborate – online and social. What is important to understand is that A360 provides data and collaboration backbone for Fusion360, so engineers are not facing file-based operations like in traditional desktop CAD tools.

carl-bass-fusion-360-au2014-2

Onshape

Onshape is a new company re-imagining CAD for Google era. Large group of Onshape founding team is coming from SolidWorks. Last week, Onshape started to blog. One of the things I captured from Onshape blog is their claim to rethink PDM role and appearance for cloud CAD. You can read some of my thoughts here – Future CAD won’t require PDM. Here is quote from Onshape blog:

on-shape-world-changed

We tried with traditional PDM, but fundamentally the architecture of copying files around, to and from servers and desktops, is just not a good basis for solving version control and collaboration problems. We think we have a better way to solve the problems, and no PDM system is needed.” Mac, Windows, phone or tablet. No PDM system needed. The files stay in one place. Different UI look. Now those sound like interesting and wonderful things. We’ll continue to anxiously anticipate what they have planned and what you have to say about it.

GrabCAD

GrabCAD workbench is another system that introducing a different experience by merging cloud and file-based data management operations. GrabCAD didn’t develop CAD system as it was predicted by some CAD industry insiders. However, GrabCAD Workbench is a PDM system on the cloud that can remind you some elements of Dropbox combined with CAD viewer and ability to control file revisions.

grabcad-workbench

What is my conclusion? Existing paradigms are hard to change. In my view, engineers are one of the most innovative groups of people. However, when it comes to their own tools, engineers are very conservative. You can easy expect the following vision for data management from an engineer – “I want to work with my designs (files), please leave me alone and stop selling me PDM tools”. However, here is the thing – collaboration can make a difference. The integration of data management and collaboration can provide a significant advantage to engineers in a modern mobile and distributed environment. This is a key thing, in my view. Cloud and mobile collaboration will change CAD /PDM integration paradigm in the future. Just my thoughts…

Best, Oleg

 

Share

6 comments

When BOM is not BOM

by Oleg on December 17, 2014 · 0 comments

walks-like-BOM-quacks-like-BOM

Bill of Materials (BOM) is a central part of everything in product development. Sometimes, people call it product structure. Manufacturers are using BOM to define list of raw materials, parts and sub-assemblies with corresponded quantities need to manufacture a product. This is over simplistic definition. As usual, devil is details and BOM story is getting quite complex. Depends to whom are you talking, people see a different aspects of bill of materials – sales options, design hierarchy, product configurations, manufacturing process, service parts. Many systems are defining BOM differently. It depends on their roles and functions in overall product lifecycle.

In one of my recent articles – Thoughts about BOM ownership, I discussed some ideas about how BOM can be shared among organizations and enterprise software tools. That was my attempt to think about how to resolve a conflict between two major BOM stakeholder – Product Lifecycle Management and ERP systems. The BOM management landscape in the organization is complex. In my view, companies are not ready for a single BOM management tools - it was my observation 2 years ago.

At the time a major BOM master ownership dispute is between PLM and ERP vendors, I can see an interesting trend which can put some lights on how PLM companies are articulating their BOM strategies.

Dassault Systems ENOVIA is coming with their “zero BOM error” strategy. I posted about it earlier – PLM and Zero BOM errors: the devil is in details. In a nutshell, ENOVIA is trying to improve process of Bill of Material generation by direct connection between CATIA design and product structure. In my view, it might lead to potential formal elimination of EBOM, which will be replaced by a bundle of design and engineering information. Practically, product structure in CATIA/ENOVIA will represent everything that happens on engineering level. According to ENOVIA strategy, it will eliminate errors between design and engineering.

In parallel, I’m observing the way BOM is positioned by Siemens PLM. Teamcenter blog – Introducing BOM management speaks about BOM information as a vital part of many processes supported by PLM. I found interesting how “BOM management” term was replaced by “Product definition”. Here is the passage:

I just noticed that as I am writing this I am using the words “bill of materials” less and “product definition” more. I would go back and correct – I wanted to keep it a surprise!  But I think it’s ok – it helps me get to this next part. To us, it has become abundantly clear that one of the problems that come up when you talk about bill of materials (BOM) management is that the scope of what people might mean is so broad. To call all those things listed above “BOM Management” is not sufficient.  We’ve collected these capabilities into an umbrella we call the Integrated Product Definition. This is an area where we have been leaders, and it continues as a high priority for us – we have the breadth and depth to address these issues like nobody else can.

In both situations, I can see a strategy by PLM vendors to redefine BOM and bring up the extended value PLM environment for customers. This is a very important transformation in my view, since it helps to streamline processes. The problem of synchronization between design and engineering environment is well-known and not solved in many companies. Teamcenter is connecting BOM management into varietly of topics such as part management, master data management, configuration management, coordinate change and variability and others. It helps to create a solid platform to manage product data.

However, the biggest fight over the BOM is between PLM and ERP environments. Engineering.com outlined it in their article – The next big boom in PLM is a battle over MBOM ownership. Muris Capital Advisors outlined the sam conflict in the blog post – The Battle for BOM Control. According to Bruce Boes of Muris Capital, service integrators will play a leading role in making alignment between PLM and ERP and forming BOM master model. Here is an interesting passage:

We predict that System Integrators have a unique opportunity and from our recent experience, the desire to bridge the gap and add value during integration with the BOM as a key point of integration.  In doing so they open the market for process consulting and integration services surrounding the master model concept. 

The last one make sense. In many PLM implementation projects, SI teams are actually leading development of PLM-ERP integration on site or using different middleware or integration toolkits. Unfortunately, the cost of these implementation is high and overall process is very complex.

What is my conclusion? PLM vendors redefining BOM by tight integrating of product information into development processes. From what I can see, both Teamcenter and ENOVIA are trying to redefine Bill of Material (BOM) as a wider topic. This is an interesting strategy to fight over MBOM ownership. Integrated “product definition” can help to streamline processes between engineering and manufacturing. However, the end game should be total BOM experience including all manufacturing aspects – manufacturing process planning, cost and orders. The last one brings PLM-ERP integration topic back on the table. Just my thoughts…

Best, Oleg

Share

0 comments

PLM software lifecycle and social development roadmaps

December 16, 2014

My post few days about PLM software replacement cycle turned into discussion about the way companies are implementing and maintaining PLM software, upgrades, new versions and planning investments into infrastructure and enterprise software. My attention caught Technia on demand webinar – The future of SmarTeam. It is an example of long software development cycle, maintenance, support […]

Share
Read the full article →

Social PLM: How to pull a trigger?

November 19, 2014

In my yesterday blog, I shared some of my thoughts about “Facebook at Work” and potential impact on engineering and manufacturing software. It made me think again about all discussions and stories related to social software trend and social PLM. Social was trending topic 3-4 years ago. Many new companies were founded back those days to […]

Share
Read the full article →

PLM Vendors and Tunnel Vision

November 11, 2014

I’ve been following Dassault Systems 3DXforum this morning. Thanks for technology improvements these days you can be almost present at the events by combination of live streaming and social media communication. The first presentation by Bill Taylor, Fast Company editor struck me by mentioning of the idea of Tunnel Vision. I took a trip to […]

Share
Read the full article →

Multiple dimensions of BOM complexity

October 15, 2014

Bill of Material topic is getting more attention these days. No surprise. BOM is a center of universe in manufacturing (and not only) world. People can disagree about terminology applied to BOM management. Depends on a specific domain people can call it part list, specification, formula. But at the same time, everybody speak about the […]

Share
Read the full article →

What cloud PLM cannot do for you?

September 19, 2014

It has been already few years since I started to discuss cloud PLM opportunities on my blog. I found one of my early blogs about PLM and cloud – PLM and cloud: hold the promise? So, what changed since then? Actually, quite a lot… We’ve seen massive adoption of cloud and mobile by businesses in […]

Share
Read the full article →

PLM and Zero BOM errors: the devil is in details

September 10, 2014

To manage Bill of Materials (BOM) is not a simple job. Often you can hear a simple definition of bill of material as a “list of component needed to build a product”. However, in reality, BOM is much more complex and contains information about product structure, the ways product is manufactured, maintained and even disposed. […]

Share
Read the full article →

Dassault is going to support all PLM cloud options by 2015+

July 10, 2014

For the last few years, I’m following cloud strategies of main PLM vendors – Aras, Arena, Autodesk, Dassault, Siemens PLM, PTC and few others. You can find some of my early notes here – PLM vendors, IT and cloud strategies. The variety of cloud options made statement “Cloud PLM” practically useless. I had a chance […]

Share
Read the full article →