From the category archives:

Products

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

4 comments

beyond-plm-blogging-solidsmack-pic

Here is my personal story about blogging. I started to blog more than six years ago. The idea of blogging came to me from intensive meetings with customers that I had as Dassault SmarTeam CTO. I spent time discussing implementations and problems customers are experiencing with PLM solutions. These discussions inspired me to spend more time online. One thing I discovered immediately about PLM industry back in 2007 – the amount of online information about PLM implementations, products and technologies was very limited. Customers and vendors didn’t share much online. At the same time, outside of PLM domain, blogosphere was booming by large number of blogs sharing information about programming, web technologies and other topics.

My recent Cadalyst interview made me think again about the time I started to blog. Honestly, I almost shutdown the blog after I left Dassault in 2009. However, after speaking with some of my readers, I came to conclusion that I cannot stop it. I discovered and connected with many readers. I found how my readers are learning from my blog and I learned how to learn from them. The blog outgrew the original plan to share “one PLM topic to discuss” as Daily PLM Think Tank. I registered new domain beyondplm, which was a better reflection of what I’m writing about.

I’ve written about 1815 posts, which is probably equal to 10-15 full length books. During that time I learned a great deal about blogging and people (this is probably a topic for another blog post). What was amazing is how blogging helped me better understand customers, manufacturing and PLM business.

So, here are seven important things I learned about PLM after writing probably more than 1’000’000 words about PLM.

1. PLM is extremely conservative domain. You think engineers love new products and tech. Yes, engineers are loving to develop new products and technologies. But, it is a bit different when you speak to them about new product development tools. When it comes to adopting of new PLM tools, as a solution provider, you compete mostly with status quo – existing working processes, outdated implementations, legacy systems, Excel spreadsheets.

2. The adoption lifecycle of PLM products, ideas and technologies is much longer than you can imagine. Think about years or even decades. There are some great examples in the industry that can prove it. PLM industry first movers are competing with evolution of existing products.

3. The biggest PLM implementation challenge is customer learning process. Customer is discovering bad things about the way company is running business and managing product development processes. It is not easy for people to manage their own guilt. Somebody is actually responsible for the mess. From that point, all you need to do is to help company to understand their business and find ways PLM technologies and products can improve it.

4. Tables with data are boring. Visualization is absolutely important. Customers are asking about variety of data and processes management issues, but nothing can excite them more than  3D visualization of their own products – cars, airplane interior, engine, fashion collection, etc.

5. Cost is important. Everything customers will tell you about the fact price is not important and manufacturing companies have money to pay is a biggest illusion. Typically, you are talking to engineering IT and these people are interested how PLM technology and products can solve their problems. But, it will come down to price and must be prepared for tough cost related discussions. I think, one of the biggest reasons of PLM low adoption is high solution cost.

6- Data import and integration with other systems are two key technological challenges you need to solve to successfully accomplish PLM implementation. Customers rarely have an opportunity to start “from scratch”. Also, don’t think about import/export of Excel spreadsheets as you mainstream integration strategy. Most of PLM implementations are ending up with integration service providers hardwiring data exchange between applications.

7- You should think about ROI and how to connect to CIO. However, don’t forget to deliver one “extra feature” that will help engineers to feel proud of your PLM solution. You will become “engineering hero” and engineers will sell your PLM systems to rest of the company.

What is my conclusion? One of the best parts of blogging is that you can learn a lot. In many cases, I came back to topics I already discussed and shared what I learned to spark a conversation. Sharing knowledge is an amazing experience. PLM industry changed for the last 6 years. Companies are sharing more and it is easier to get information online. All together we can do industry better. Just my thoughts…

Best, Oleg

Share

12 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

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 →

MBOM collaboration and cost of change

October 9, 2014

The only thing that is constant is change. This is very much applies to everything we do around BOM. Engineering and manufacturing eco-system are full of jokes about engineering changes. You maybe heard about renaming “engineering change order” into “engineering mistake order” as well as the correlation between number of engineers and number of ECOs […]

Share
Read the full article →

Manufacturing BOM dilemma

October 8, 2014

Manufacturing process optimization is one of the biggest challenges in product development these days. Companies are looking how to low the cost, optimize manufacturing process for speed and to deliver large variety of product configurations. The demand for these improvements is very high. The time when engineering were throwing design”over the wall of engineering“ is over. […]

Share
Read the full article →

Part management is stuck between PLM and ERP

September 11, 2014

Few days ago, the discussion about PLM revenue model took me into part management route. This is not entirely related to revenue and business models, but my readers mentioned part cost reduction as one of the most visible ways to present PLM ROI. I have to agree, to manage parts is a critical element of […]

Share
Read the full article →

Why now is the right time to reinvent PDM?

August 15, 2014

Product Data Management (PDM) isn’t a new domain. The first PDM systems were invented 20-30 years ago with a simple objective – to manage product data. The scope of PDM was heavily debated and included design, engineering BOMs, ECO and even supply chain. However, the most widely accepted role of PDM is to manage CAD […]

Share
Read the full article →

Design Collaboration and Google+ Lessons

May 14, 2014

Recent management changes in Google+ attracted lots of conversations about social products experience as well as speculations about Google+ social future. It is also made a reflection on how “social theme” will be developed in enterprise companies. In the past few years we’ve seen few examples of social products for enterprise – eg. ExoPlatform, Jive, SAP […]

Share
Read the full article →

PLM Cloud Customization and Online Code Editors

May 7, 2014

One size doesn’t fit all. It very true especially when it comes down to PLM implementations. Once released as a toolkit, PDM / PLM systems did a long way from a system that requires special software compilation to be done for every customers to the current system with flexible data models and tools allowing to […]

Share
Read the full article →