How PLM can avoid cloud integration spaghetti?

June 18, 2015

21-centure-spaghetti-integration

Enterprise integration is a messy space. It is always complex – applications, databases, new and legacy systems, complexity of requirements. People usually need to run at least dozen of applications to run things smoothly. It is never done out-of-the-box and it is always requires circles of implementations and professional services.

I caught the following picture tweeted yesterday by Stan Przybylinski of CIMdata. It provides an excellent view of integration complexity. Unfortunately, in many situations, integration is a major challenge in PLM adoption. To get full value of PLM, company should spend a fortune integrating data and processes – CAD, Bill of materials, ECO, etc.

data-silos

Cloud is coming to enterprise these days. In many ways it creates a new way to think about data, software, services and maybe integrations too. The new technologies and eco-system of services can make a difference. It also creates a significant demand for openness and interoperability. This is a main reason why PLM need to learn web APIs. Web services and REST APIs are changing the way integration can be done.

Technology can make a difference. However, integrations are still hard. Few months ago, I shared my thoughts how to prevent cloud PLM integration mistakes. It comes down to three main things – 1/ lost data semantics; 2/ limitation of data transfers; 3/ transaction management in distributed and cross site environment.

Unfortunately, cloud is not a silver bullet to solve integration challenges. The demand for holistic integration continuum is still in the future. In practice, cloud applications today are replicating bad siloed behaviors of on premise applications. I captured the following picture earlier this week at Boston New Technology meetup.

cloud-silos-apps

This picture is the great demonstration of how bad aspects of siloed on premise applications are moving to cloud environment. Migration of applications on cloud infrastructure such as IaaS can simplify IT’s life. However, it won’t make life of users simpler. From end user standpoint, applications will still run in a silo.

What is my conclusion? The danger is to move established on premise PLM paradigms to the cloud. Technologically new cloud systems can give an advantages in terms of integrations. REST API is one example – it is much easier to code integration scenarios using REST APIs and modern web based tools. At the same time, closed data paradigms and data duplication between silos can bring well-know data spaghetti from on-premise applications to the cloud. Just my thoughts…

Best, Oleg


PLM Vendors: Cloud Service Comparison

June 15, 2015

plm-cloud-compare

Cloud is taking PLM vendors by storm. Just few years ago, the question if manufacturing companies will adopt cloud raised lot of debates. You probably remember my posts – PLM competition and true cloud solution and PLM cloud: differentiation and anti-cloud rant. Fast forward into 2015 – I can see almost all PLM vendors are actively engaging into industry discussion about cloud solutions. Public cloud is getting more traction and I stated it in my earlier post – Is public cloud reshaping PLM landscape? Time to recheck…

Earlier today, the PTC article – Demystifying Cloud Services by Christa Prokos caught my attention. The article provides a good insight on different aspects of providing cloud services such as IaaS, PaaS, SaaS. The article is also connecting it to the notion of public, private, hybrid and virtual private clouds.

It made me think about summarizing what I know about PLM vendors strategies and cloud capabilities. I admit that I don’t have full information and can rely only on public sources of information. So, I created the following draft table. If it makes sense to you, let me know. If you have some information and think I missed something, please comment as well. I will maintain updates to this post.

plm-vendors-cloud-services

What is my conclusion? In 2015, cloud is probably not a marketing differentiation for PLM sales people. However, the devil is in details. You need to get your hands dirty to figure out what “cloud” vendors are talking about. Earlier this year, at COFES 2015, I gave a briefing about PLM and cloud. You can take a look here to learn more. There are few questions that left not answered and, in my view, will require a heavy focus by PLM vendors – cloud adoption trajectory by manufacturing, economic of cloud offering and how cloud PLM can change an existing PLM implementation paradigm. It seems to me PLM vendors made a first shot to fill a spreadsheet with cloud check boxes. But jury is out to check what and how PLM cloud cloud can deliver. Just my thoughts.

PS. The PLM cloud services comparison table is a draft. I’m looking forward for your comments – I’m sure missed some company specific points and I need your help to finalize it.

Best, Oleg

Image courtesy of cuteimage at FreeDigitalPhotos.net


Cloud CAD and Offline Internet

May 29, 2015

online-offline-cad

I had a chance to attend Google I/O extended 2015 event in Cambridge, Mass yesterday. If you follow up Google I/O, you might be already up to the speed with all Google announcements around Android, Wear, Internet of Things, Photo, etc. If not, check Google I/O 2015. What caught my special attention is Google’s focus on offline. Offline is starting to be important, since Google is thinking about future internet expansion. Think about questions like – how to search on mobile when Internet connection is weak? or How to navigate using Google Maps with no internet connection?

Offline is an interesting topic. We want to have our life connected and collaborative. But at the same time, we are trying to think how cloud applications will work with absence of internet connection or in the situation when internet connection is very weak. TechCrunch article Google Quest to bring the internet to 7 billion people can give you some brief about what Google plan to do. The following Gizmodo article specifically talks about YouTube offline and Maps offline.

offline-google-maps

Another thing that Google did is optimized download time for bad network connections. I’ve seen a demo and it really makes a difference.

optimized-download

It made me think again about offline topic in the connection of cloud CAD. The “offline” topic is one of those things Autodesk Fusion360 and Onshape are different these days. Read my earlier post – Autodesk and Onshape disagree about cloud technology and focus. For the moment Fusion360 is an app that requires installation and it works connected with Autodesk 360 cloud platform. It can remind you Evernote – you can install it and it will sync data instantly and keep your records so you can access it from any device. Onshape is taking a different route – full cloud CAD application and it works completely in the browser. You can think about it as Google Apps and Gmail-like approach.

Al Dean of Develop3D shared his opinion on strategy and technology of both Onshape and Fusion360 in his article The cloud – a bright future ahead. Here is the passage addressing the “offline” topic.

Eventually, Fusion will be available via the browser (I’d put a fiver on that being before the end of the year). DS’ next generation SolidWorks products will get better and more accessible. Though strangely, this is the unknown in the calculations as DS is reluctant to talk about the whole thing, presumably to protect its dominance with SolidWorks.

And hopefully, OnShape will have a way of working when you’re offline, as well as internet connected. Finally, I’d hope that DS is much more open about getting its customer’s access to the tools it is developing . The excuse that “They’re using our resources so they should pay” simply won’t cut it as these tools need to be played with, discovered and explored. At the moment, they’re not getting the exposure that they deserve — leaving a whole new market open to Autodesk and Onshape.

What is my conclusion? Will CAD vendors take Google way to make cloud CAD offline? This is an interesting place to watch. Google made several attempts for offline work in Google Apps. It didn’t work in the past, but these days I can save my work offline in Google Drive and it is magically getting in sync when my computer connects back to the internet. Google Maps is a great example how to address specific offline needs. I guess cloud CAD vendors can learn a lesson from Google. It seems to me Autodesk and Onshape will be coming to offline mode from two separate directions. However, focus on customers can be a good guidance to see what is important and when. Just my thoughts…

Best, Oleg

Google I/O pictures credit Gizmodo.

Image courtesy of Stuart Miles at FreeDigitalPhotos.net


Cloud PLM and SaaS sales mindset

May 22, 2015

cloud-plm-sales

I want to talk about PLM sales today. If you want to succeed in sales, a mindset is a right starting point. But, enterprise sales needs a special mindset. PLM sales is very special case. These days SaaS / cloud software is setting new rules for enterprise software. How does it influence and change PLM sales? What advantages cloud PLM can get compared to a traditional PLM products and sales model?

Few days ago, I posted about how to stop blaming engineers for PLM sales problems? In my view, engineers are on average bad sales people. Therefore, to put engineers in the spot of selling PLM and blame them for wrong articulation of PLM value is a bad idea. There are thousands of books and article on the topic of how to sell to enterprise organizations. It is a good reading for coming Memorial Day long weekend. Today, I want to talk about cloud PLM sales – a new category that has a chance to change the way we sell PLM.

I can see two aspects of cloud PLM sales. First is related to a new reality of our world – internet, online connectivity, social networks, virality. How does it help to sell PLM? It certainly helps to create a new level of awareness about what your product does. If you didn’t setup your product twitter account, blog and other social channel, do it now! But, it doesn’t change a fundamentals. Despite all social channels, selling to enterprise is still very much old-schoolers game. In my view, there is no PLM vendors that discovered a new way to sell PLM until now. You can read more in my earlier post – PLM, Viral Sales and Enterprise Old Schoolers.

Second aspect is related to the fact how PLM companies are managing enterprise sales process and new business models. My attention caught the A16Z blog post – If SaaS products sell themselves, why do we need sales? The article gives you an excellent perspective on the details of sales process. I like the comparison of enterprise sales to the process of getting a bill passed in Congress. Certainly true. Although PLM is not a new category in the market, I would consider PLM sales challenge to create a unique value for every customer as something real PLM vendors are facing every day. PLM sales are competing with many other activities in manufacturing companies and it is literally hard to take it through the all three steps of decision process – why to buy PLM, why to buy PLM from a specific vendor and why to buy PLM now.

SaaS sales are facing the same level of sales difficulties. At the same time I’ve been thinking how cloud PLM can get some advantages over a traditional PLM product sales. And the point of "customer facing activity" form A16Z blog is clearly resonating here. This is a passage to pay attention in my view:

SaaS is a winner-take-all market involving a “land-and-expand” sales strategy. However, landing doesn’t necessarily mean expanding and winning. Staffing your startup with customer-facing resources — professional services, customer support, etc. — at this stage is an investment that will pay off not only in expanding your footprint inside that account, but in building the most powerful sales tool there is: a good reference. And while new clients are great, the best place to sell something is where you’ve already sold something.

You may ask me how is that related? Here is the thing… Landing should be an easy process in SaaS PLM compared to a traditional PLM sales process. And this is where cloud PLM can provide a clear differentiation. A traditional PLM approach is to sell on a premise of changing the way customer is doing business and manage product development processes. When it is done, you can setup PLM system and prove it. But it is a very lengthy process. Opposite to that, you can think about cloud PLM first sale as a "land" process. Do it for the most painful problem customer has. This is why PLM sales should be more technical. Land it to the customer for a cost of zero dollars. After all, you can leverage elasticity of the cloud as a biggest advantage. After you done, work on expand option. New subscription business models will help you to provide a new way for customer – pay per use.

What is my conclusion? Moving to the cloud, doesn’t mean PLM can sell itself. After earlier attempts, it looks like wrong sales strategy. At the same time, landing small feature to solve the most painful problem for a customer can be a right step to start. The challenge is to have enough customer facing resources that can help to discover it and land an initial solution with very low cost and super fast ROI. In my view, it is a completely different mindset from what we had before in PLM and enterprise. It is a time for PLM vendors to retool sales teams with new skills. Just my thoughts…

Best, Oleg

Image courtesy of Kittisak at FreeDigitalPhotos.net


Onshape quietly developed “Google Drive for CAD”

May 11, 2015

onshape-vision

Cloud storage and CAD files. This topic always created lot of controversy and questions. File sizes, speed, security, CAD formats and viewing. At the same time, the need to collaborate and share files is obvious. In my early blog – PLM Cloud Concerns and Dropbox Reality for Engineers 3 years ago, you can find some interesting statistics about how engineers are using Dropbox services. I don’t have updated numbers, but my hunch that usage of public cloud storage services is not decreasing.

GrabCAD was probably the first widely adopted CAD storage and share service. I debated usage of specialized CAD storage and collaboration service – 3 pros and cons to have a special CAD file sharing tool. You can find some more comments in my chat with Hardi Meybaum of GrabCAD.

Onshape cloud storage and collaboration

I’ve been watching recording of . It is a bit long, but if you have time, watch it. Here is a skimmed version with my comments .

Onshape developed a platform that allows users to store, view and collaborate with CAD files. It allows to export and import files, manage revisions, view and edit models and drawings. The list of export and import file formats is not comprehensive yet, but in my view can easy cover the needs of many small and mid size manufacturing shops.

There are 4 main scenarios explained in the webinar – 1/ use Onshape as cloud storage tool; 2/ vendor collaboration; 3/ design review; 4/ access for people with no CAD (viewer). Slides below can be give you some additional explanations.

1-cloud-storage-tool2-collaborate-with-vendors3-design-review-tool4-increase-access-nocad

There are few interesting things that are not obvious in my view if you think about Onshape as CAD tool only.

You can upload and store any type of files to Onshape. Embedded browser viewer is available and you can see them online (you need to convert file into Onshape geometry for viewing). The ability to share and comment on files inside of browser brings “social element” into collaboration. Revisions will help you to keep baselines of files shared with subcontractors.

Onshape’s pricing model can support collaboration. I guess, as soon as somebody with paid Onshape license will share file with you (via email), it will give a free access after registration steps.

What products Onshape is competing with?

Onshape is clearly not the only vendor to support collaboration and storage of CAD files. I just want to mention few of them. I mostly focus on public cloud tools. I’m sure missed few tools, so please feel free to add them in the comments to the blog post.

[Update: 11-May 2015] As expected, I’m getting comments about tools I forgot to mention in this section. So, I’m re-arranging the list. It is alphabetical and will be expanded. Watch for updates…

Autodesk A360 is a cloud project collaboration tool that can support different CAD formats, viewing and collaboration. Navigate here to learn more.

GrabCAD (even after acquisition by Stratasys) is around and after GrabCAD announced Workbench is free, it can be an attractive option too.

Kenesto is an outfit that recently announced the availability of “Kenesto Drive” – cloud tool that can help you to collaborate on CAD files instead of using shared network drive. I’ve been sharing my thoughts about Kenesto here. You can get more info here.

TeamPlatform is a tool that was acquired by 3DSystem. More info is here. It can give you a set of viewing and collaboration capabilities with CAD files.

What is my conclusion? The think I like the most with Onshape is simplicity. The ability to follow Google Drive or Dropbox scenario of File download, Save As, Translate and browser (URL) based model is something you can appreciate if you are doing a lot of work online. Onshape feature set is limited and it is not clear how fast it will grow. It can be a good opportunity to discover what Onshape can give you, but you should consider Onshape beta status. Just my thoughts…

Best, Oleg


Cloud PLM provider check list

April 30, 2015

cloud-plm-checklist

Cloud is everywhere these days. Despite high popularity of cloud solution, I still can see some confusion on the side of a customer trying to make a decision about moving towards specific cloud services. The discussion I had at COFES 2015 earlier this month made me think about key questions you want to ask your potential cloud PLM provider before signing your SLA.

A server, which is connected to the internet is not automatically cloud (SaaS) application. The devil is in details and by understanding specific cloud characteristics you will save time and money for your organization.

Here is a check list you might consider for your cloud provider due-diligence process. .

1- Infrastructure

Most of cloud PLM vendors are not running their own infrastructure layer to bring cloud solutions to you. This is so-called IaaS (infrastructure as a service) layer is pretty important for the architecture of your solution.

Professional cloud provider and partners used for IaaS should be responsible for maintenance of infrastructure layers. Then this partner is also responsible for the entire maintenance of the infrastructure (servers, operating systems, databases, backups, etc.). Patches are published on a weekly basis (usually for good reasons) and this is alone is a valuable service which reduce a pressure on your IT department. The level of availability guaranteed usually lies close to 99.99%; a level which the market leaders in the cloud segment also actually achieve.

2- Maintenance and upgrades

From the perspective of cloud vendor, the maintenance of cloud based apps is much simpler than on-premise solution. User can see it as a clear advantage. However, you should validate how is that aligned with customization and test environment. It can take an interesting turn on your own IT upgrades to leverage the same time frames and also identify the impact you your own company maintenance schedule.

3- Multi-tenancy

This is one of the key things, in my view. Compatibility to multi-tenancy has nothing to compare with the ability to set an environment for many customers. This is about how application architecture was developed in the way to be used by multiple clients. I touched few years ago in my post, which can give you more details.

Essentially, it is separated into two topics – application multi-tenancy and data multi-tenancy. The first will insure all customers are running the same version of the application. It simplifies maintenance for vendor, but bring an additional level of complexity for application and service providers. To insure your environment and data are compliant with a new version takes time and you want it to be very efficient. Data multi-tenancy is a next level. In some cases, you can consider it as non-important. However, after more thoughts, it might be wise to check how multi-tenant application is working with multiple customer databases. It might be too complex to maintain and it might make an upgrade more complicated.

Be aware, multi-tenancy is a key thing in cloud architecture and it require major re-architecture if you speak about existing on premise software. An on-premise solution cannot be made compatible to cloud overnight. Therefore, anyone who is trying to convince you that technology developed back in 1990s runs on both cloud and premise locations might have a great sales skills, but not much technological competency.

4- Security

One of the most often asked question is about security. For the last 3-5 years, cloud providers developed a set of security procedures. Good vendors have them available online in a very transparent way. Ask for a link. If you cannot get one, this is a red no go flag to work with this vendor.

What is my conclusion? Cloud technologies can be very different. But, as a customer, you shouldn’t take blind decision about what are you buying. The most important to understand – you are not buying product anymore. You are buying “service”. SLA is your marriage contract if you will. Whatever is in that contract will define how your PLM system will perform. So, check contracts upfront and look for technological and business differentiations. Just my thoughts…

Best, Oleg

Image courtesy of arztsamui at FreeDigitalPhotos.net

 


Onshape, API and cloud architectures

April 23, 2015

cloud-API

I assume you are aware about Onshape, the new CAD software outfit founded by Jon Hirschtick and part of his old SolidWorks founding team. The software is in public beta for the moment. You can reference to my previous posts – PLM thoughts after Onshape public beta and Develop3D live set a stage for cloud CAD competition. I also recommend you Develop3D article – Onshape Beta goes live – start your engines. Navigate to the following link to discover more Onshape resources.

Integration is a very important thing in engineering application domain. Engineers and manufacturing companies are using multiple applications for design, simulation, product data and lifecycle management. Therefore, system architecture and availability of APIs is absolutely important in order to develop integrations and more specific and complex engineering data flows.

Earlier today, my attention was caught by Onshape blog by Steve Lewin-Berlin, which gives you some perspective on Onshape APIs. Onshape is using own APIs to create first integration with Graebert Drawings. Here is the passage from the blog explaining that:

I’ve been leading the development of the Onshape API for the past year. COFES was our team’s coming out party, marking the first public discussion of the API. The introduction of Onshape Drawings and our partnership with Graebert GmbH is an important part of the story.

We decided to build Onshape Drawings on top of the same API that will be available to partners. In a classic case of “eating our own dog food,” we believe that using the API for a significant internal component validates the capability and performance of the API. This also provided a clean interface between Onshape and Graebert technology, allowing us to leverage the extensive technology available in Graebert’s core drawing engine.

As you can see in the screenshot below, Onshape Drawings run in a tab just like Parts and Assemblies, and use a native Onshape style toolbar and command structure.

onshape-drawings

Last week at COFES 2015 I spent some time learning about what Onshape is doing with APIs and integrations. You will be able to integrate Onshape using three different approaches – file exchange, live link using REST API and by creating more complex integrated cloud workflows. Few pictures below can give you some idea about Onshape integrations (apologies for the quality of pictures. I’ve made them in standing room only during Onshape presentation at COFES).

onshape1

onshape-file-exchange

onshape2

onshape3

Onshape is promising to make APIs and documentation available to broader audience later in May.

What is my conclusion? Hybrid architecture and APIs. For the next decade we will live in the world of new cloud apps and existing desktop tools. I can see people starting to use new cloud services in parallel with existing design applications. Openness will be even more important than before. It is critical to follow open integration architecture and REST APIs to support a mix of required integrations. Just my thoughts…

Best, Oleg

Image courtesy of Danilo Rizzuti at FreeDigitalPhotos.net

 


Follow

Get every new post delivered to your Inbox.

Join 285 other followers