Will public clouds help enterprises to crunch engineering data?

August 6, 2014

google-data-center-crunches-engineering-data

The scale and complexity of the data is growing tremendously these days. If you go back 20 years, the challenge for PDM / PLM companies was how to manage revisions CAD files. Now we have much more data coming into engineering department. Data about simulations and analysis, information about supply chain, online catalog parts and lot of other things. Product requirements are transformed from simple word file into complex data with information about customers and their needs. Companies are starting to capture information about how customers are using products. Sensors and other monitoring systems are everywhere. The ability to monitor products in real life creates additional opportunities – how to fix problems and optimize design and manufacturing.

Here is the problem… Despite strong trend towards cheaper computing resources, when it comes to the need to apply brute computing force, it still doesn’t come for free. Services like Amazon S3 are relatively cheap. However, if we you want to crunch and make analysis and/or processing of large sets of data, you will need to pay. Another aspect is related to performance. People are expecting software to work at a speed of user thinking process. Imagine, you want to produce design alternatives for your future product. In many situations, to wait few hours won’t be acceptable. It will be destructing users and they won’t use such system after all.

Manufacturing leadership article Google’s Big Data IoT Play For Manufacturing speaks exactly about that. What if the power of web giants like Google can be used to process engineering and manufacturing data. I found explanation provided by Tom Howe, Google’s senior enterprise consultant for manufacturing quite interesting. Here is the passage explaining Google’s approach.

Google’s approach, said Howe, is to focus on three key enabling platforms for the future: 1/ Cloud networks that are global, scalable and pervasive; 2/ Analytics and collection tools that allow companies to get answers to big data questions in 10 minutes, not 10 days; 3/ And a team of experts that understands what questions to ask and how to extract meaningful results from a deluge of data. At Google, he explained, there are analytics teams assigned to every functional area of the company. “There’s no such thing as a gut decision at Google,” said Howe.

It sounds to me like viable approach. However, it made me think about what will make Google and similar computing power holders to sell it to enterprise companies. Google ‘s biggest value is not to selling computing resources. Google business is selling ads… based on data. My hunch there are two potential reasons for Google to support manufacturing data inititatives – potential to develop Google platform for manufacturing apps and value of data. The first one is straightforward – Google wants more companies in their eco-system. I found the second one more interesting. What if manufacturing companies and Google will find a way to get an insight from engineering data useful for their business? Or even more – improving their core business.

What is my conclusion? I’m sure in the future data will become the next oil. The value of getting access to the data can be huge. The challenge to get that access is significant. Companies won’t allow Google as well as PLM companies simply use the data. Companies are very concerned about IP protection and security. To balance between accessing data, providing value proposition and gleaning insight and additional information from data can be an interesting play. For all parties involved… Just my thoughts..

Best, Oleg

Photo courtesy of Google Inc.


Here is why CAD in the cloud is more than mainframe terminal

August 1, 2014

CAD-IBM-mainframe-term

Cloud is one of the topics that I’m following on my blog for a long time. I can see lots of changes that happened in CAD / PLM world for the last few years with everything that related to cloud. I’m sure you remember very turbulent announcement about SolidWorks future in the cloud made during SWW 2010. Since then, I was looking how CAD/PLM vendors were taking different cloud approaches based on their customer base, long term vision and strategy. Here are some of my previous posts speaking about vendors and different cloud strategies – Dassault is going to support all PLM cloud options by 2015; PLM cloud switch and PTC final click; Siemens PLM analyst event PLM public cloud strategies; Cloud and IaaS options; PLM/PDM Why Cloud? Wrong question…

I read Siemens PLM blog post – Is it time to revisit CAD in the cloud? by Matt Lombard. The article raised many question and concerns in my head. So, I decided to share them with you to compare our notes about cloud strategies. My attention was caught by the following two statements: 1/ Cloud has nothing to do with CAD. It is IT; 2/ Cloud in the cloud will send us back to manufacturing/terminal arrangement. Here is the passage from the post about that:

The cloud has nothing to do with CAD, really. The cloud is all about how you deliver the software, and/or about how you store the data. It’s IT. There was a time when all CAD software was delivered across a network to individual terminals, and the data was stored centrally. People about my age who remember this sort of thing generally refer to that as the “bad old days”. Working on terminals that had to log in to a mainframe was inconvenient. If the mainframe was down, no one could do anything.

The personal computer (PC) revolution was such a big hit because it gave you more flexibility. Everyone had their own computer. It took us out of the collective, and made us individuals again. In the mid 90s, along with Windows NT, this meant that we could start using our technical engineering applications on PCs, which were far less expensive and restrictive when compared to mainframe setups.

“CAD in The Cloud” promises to send us back to the mainframe/terminal arrangement. Whether it’s a local cloud, on your company’s LAN or a public cloud on Amazon or IBM, or a private cloud you access over the internet, it’s the same idea as the mainframe/terminal. But is it a good thing, or a bad thing?

These two statements made me think again about completely different approach companies can take in terms of cloud adoption. You can consider cloud as "yet another server" located elsewhere and managed by somebody else (not by the IT of your company). From a very narrow point of view, it is true. However, think for the moment about potential elastic computing power. You might rethink your position. The ability to bring brute computing force will allow you to speed up design and analysis. You can compare variants, visualize your design and re-use early projects in a completely different way. It can change design and decision process completely.

Another aspect is related to collaboration and data access. By moving your PDM server into cloud can gain some benefits. It mostly around IT cost and global access. However, you can achieve much more by allowing people to communicate across departments and extended value chain. It opens many opportunities in communication, business optimization and analytics services.

Another interesting point made by Matt is related to desktop tools. Matt comes with the explanation about relationships between SolidEdge and cloud. Here is the passage from the blog:

For all of these reasons, I like the approach that Siemens PLM has when it comes to the cloud. Solid Edge does not appear to have any cloud aspirations at this time, but there are versions of enterprise software that will allow for local cloud set up. Giving the customer the choice and the control without coercing them is the right thing to do.

I like the way Matt put the connection between SolidEdge as a desktop software and so called "enterprise software that will allow for local cloud set up". I reminded me TechCrunch article – The Return Of The Desktop Productivity App. What I like is the role desktop applications play in the triad of desktop-web-mobile. All together, these applications become part of connected cloud platform. Think about Evernote for a moment. You can use desktop version of Evernote and transparently switch to mobile and web version depends on the situation and need. Your notes remain captured and available to view, edit and collaborate. This is a big deal. This is how we will use software tomorrow. Desktop CAD applications will be seamlessly connected to cloud platforms providing backbone for communication, collaboration and storage.

What is my conclusion? Think about web and cloud as a new platform. It will bring a completely new paradigm of design and engineering. As a first step you can think about it as an old "mainframe/terminal" or "yet another server located elsewhere". However, cloud trajectory will take us much further. It will bring new connected platforms that will change the way we communicate and collaborate. Elastic computing platforms will help us to find optimal design solution and intelligently use customer data for analysis. Just my thoughts…

Best, Oleg

The photo courtesy of computerhistory.org


Cloud PDM can make file check-in and check-out obsolete

July 21, 2014

cloud-pdm-checkin-out-need-1

Management of CAD files (PDM) is heavily associated with desktop workflows. Lots of CAD files live on engineering desktops and shared company network drives. Originally, one of the main PDM functionality was to vault CAD data and manage CAD files revisions. One of the most widely used scenario to support this functionality is so-called Check-in / Check-out process. CAD files are checked-in from working folders (working space) into secured File vaults located on PDM servers. In case engineers want to make a change, you need to check-out file. The same mechanism can insure released CAD files won’t be changed without approval and prior check-out. The implementation of PDM check-in/check-out process is not simple because of CAD data complexity. File relationships and dependencies need to be taken into account if you want to make an update CAD 3D design and drawings.

Cloud is changing existing working habits. For long time, engineers were tightly connected to their desks. CAD, engineering analysis, Excel spreadsheets… this is only a short list of tools that live on engineering desks. Not anymore. These days our workflows are heavily impacted by cloud software. Web email, cloud file sharing, cloud and mobile applications. We don’t need to be at our desk to do a job in many situations. Cloud is providing new complementary workflows. However, in some cases, we can see a total replacement of existing workflows.

I’ve been discussing how cloud technologies are changing CAD file sharing, CAD data management and PDM. Navigate to my previous post – What makes cloud a good alternative for PDM system?. One of the most widely debated questions is related to the ability of cloud system to handle large size of CAD files. The capacity of public cloud systems to handle large data scale is well known. Cloud storage cost is getting down. The speed of changes is significant and the numbers from my 2 years old post – Cloud PDM and 10GB emails can make me smile today.

At the same time, a very important and critical aspect of cloud technologies is synchronization of data between cloud and desktop / local networks. Web giants like Google, Amazon, Microsoft and others are working to improve sync technologies. In few of my posts, I covered some specific examples about how companies like Box, Dropbox are providing specific techniques to improve data and file sync. But CAD data is different. Not like photos, office files and even videos. To solve the same problem for highly dependent and intertwined CAD data can be a big deal. When it done, it can be a significant leapfrog for any company in the market of cloud PDM solution.

Future CAD file management trajectories can take us from the original idea to check-in/check-out files between secured PDM vault and local working folders towards different workflows. Cloud file systems can support a new way to manage CAD files and provide access to them for design tools and other services. Long term goal can be a future without CAD files. The potential file storage transformation can raise lots of question about how CAD systems will operate without local storage? All these questions are relevant for both private and public cloud solutions.

What is my conclusion? Cloud will change PDM. I can see a potential transformation in fundamental CAD/PDM scenarios – check-in/check-out. Modern cloud PDM can take an approach of seamless and transparent data synchronization and simplify PDM. New workflows can potentially exclude engineers from time consuming and complicated file retrieval between desktops and servers. New way of work will be more simple and focus on design release and approval only. I can see this approach well aligned with future cloud design systems eliminating local file storage completely. So, future cloud PDM without check-in/check-out? What do you think? These are just my thoughts…

Best, Oleg


Why Siemens PLM can develop PaaS option

July 16, 2014

cloud-paas

PaaS is a category of cloud computing service providing platform and solution stack. This service model is including not only computing infrastructure (IaaS), but also application design, development, testing, team collaboration, integration features, database integration, scalability, security and others. In addition to that, it might provide service management capabilities such as monitoring, workflow management, etc.

As cloud market becomes mature, IT, customers and application development are looking into complete solutions. All PLM vendors are in full swing into IaaS cloud PLM option. Cloud PLM experience brings the need to dig more into nuts and bolts of cloud business. It includes understanding of cost, scale, service maintenance, application development, partnership. So, fundamental question many vendors and customers have is what is the best way to make cloud PLM efficient? Understanding of PaaS option is an important step. I shared some of my thoughts about PaaS and PLM before- Cloud PLM and PaaS dilemma, Will cloud PLM develop PaaS options?

My blogging buddy and well known PLM analyst Chad Jackson tweetstormed what he learned at Siemens PLM about furure TeamCenter platform development. While I’m still waiting for full blog post on Chad’s Lifecycle Insight, the following filtered tweetstorm can give some idea about Siemens PLM platform strategy:

chad-jackson-siemens-plm-tweetstorm

It resonated with my previous thoughts about cloud PLM and PaaS and made me think why Siemens PLM as well as any other PLM vendor can consider PaaS as a right option for their cloud PLM strategy. Here are my 3 reasons to develop PLM PaaS:

1- Agile development.

Vendors should be able to go fast in the development of applications, ability to customize existing features and supporting new opportunities. Businesses are much more dynamic these days. Everyone wants to be agile. PLM vendors too. So, to get up to speed with business, PLM vendors need to have a stable platform to build on. PLM PaaS can be one.

2- Better upgrade strategies

Let’s take marketing gloves off. Regardless on deployment options (on premise; private cloud; public cloud), you need to deal with upgrades. Databases, services, data model changes- this is only a very short list. PaaS can hide upgrades from customer and application developers by providing a stable platform layer. This layer requires less frequent upgrades.

3- Scaling factor and cost.

Cost is important. Cloud is not cheap as many of us thoughts from the beginning. Customers are demanding new business models and optimized cost. The development and customization cost is another problem. Scaling and keeping cost low is also huge challenge. Utilization of enterprise servers is still relatively low. PaaS can answer on the question how to share resources and scale with low cost.

What is my conclusion? Most of PLM vendors took IaaS option as a starting point to develop cloud business. It is okay and will provide important experience from different perspective – technologies, business, user interface. However, IaaS won’t remove fundamental enterprise PLM issues – implementation complexity, upgrade challenges, high diversity of requirements and business changes. PaaS option can become the next logical step to optimize platform and application for agile delivery. It looks like Siemens is making steps towards this direction. Just my thoughts…

Best, Oleg


Why cloud engineering collaboration tools are slow to ramp up

July 15, 2014

cloud-engineering-collaboration-user-adoption

Few weeks ago I attended Boston Tech Jam and learn new buzzword – YAPSA. Which stands for Yet Another Photo Sharing Application. The amount of cloud files and data sharing applications is skyrocketing these days. It inspired many developers to re-think how to share and collaborate with engineering data. Cloud technologies made people to bring back lots of web-collaboration initiatives from earlier 2000s. Web collaboration was hard 10 years ago. IaaS initial cost and availability made deployment and hosting of collaboration tools simple. 10 years of web 2.0 and photo sharing application experience provided good foundation of open source technologies to implement basic set of features. The straightforward set of every engineering collaboration is down to 5 basic functions: upload CAD files, web/mobile viewing, versions, project organization, comments and reviews.

So, you can ask me – what is wrong here? The challenge of all cloud based tools is user adoption. The obvious dream of every vendor in this space is to make tools to scale within organizations. Here are few widely used associations and buzzwords – Dropbox for CAD, Facebook for engineers, Google Drive for collaboration. However, to make engineering organization to use these tools is not a simple task. I want to bring 3 main roadblocks. In my view, most of cloud collaboration tools ignored them in their initial and sometimes even second incarnation.

1- The ease of data upload.

What is good for photo, doesn’t work well for engineers and CAD tools. Photo is all about how to upload a single file or a folder with bunch of photos from your last vacation. CAD design contains multiple files often located in several folders with references on standard parts, etc. File/Upload function doesn’t fit here.

2- Organizational security and data access.

Every organization, even small engineering firm is taking care about file access. Integration with directory service such as LDAP is probably "must have". However, very often, access rules can go even future and integrate with security access of existing applications – PDM/PLM, ERP, CRM, etc.

3- Integration with desktop tools.

Integration inside CAD (and other desktop tools) can help people to start sharing data easier. As soon as you come close to basic PDM function of revision management, integration with desktop tool is must. To integrated with desktop tool is not simple. Many cloud collaboration tools are ignoring it from the beginning.

What is my conclusion? Cloud collaboration tools are going through the difficult time of maturity. The time when website allowed to everyone to upload CAD file(s) for free and watch it on iPad is over. To remove organizational roadblocks preventing engineers to use tool broadly in an organization as well as to provide interesting capabilities to collaborate efficiently is more important. Just my thoughts…

Best, Oleg


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

July 10, 2014

cloud-options

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 to cover all four cloud PLM options here during Siemens PLM analyst event. One of the most challenging decisions for PLM vendors remains the "duality" of PLM cloud options – public vs. private. After few years of slow ramp up, all PLM vendors today are placing "cloud options" on their roadmap. So, the question "How to implement PLM cloud?" is the the one that you need to focus on when thinking about what is right PLM option for you.

I’ve been following Dassault #3DXforum for the last few days via twitter. The following slide caught my attention, since it presents clearly the spectrum of PLM deployment options Dassault is going to support – public cloud, private cloud, on premise cloud and on premise. It also gives you some idea about timeline. On premise, public and private cloud by 2014 and on premise cloud for 2015+.

ds-dfl-all-clouds

It looks like Dassault doesn’t want to miss the cloud movement and makes public and private cloud a priority. It would be interesting to see more about architecture specific, data centers, supported IaaS and PaaS options. The only information I can get from the Develop3D tweet is 6 global locations. Which sounds like a very impressive achievement. It is not clear what is behind on premise cloud option. I can guess about some combination of data storage location or mix of application deployed from multiple clouds. This is just a guess -not much you can see online.

What is my conclusion? Cloud is here to stay. However, cloud architecture and deployment options will evolve and morph actively for the next few years. It is hard to run on all options. Therefore, to focus on right match between customer interests and operation maturity looks like to direction PLM companies are trying to follow.Just my thoughts…

Best, Oleg

Disclaimer: Dassault didn’t sponsor and didn’t not influence the content of this post.


PDM weakest link

July 8, 2014

cad-file-transfer

You’re only as strong as your weakest link. The article Are You Still Using FTP for CAD File Transfer? on Engineering.com by Scott Wertel caught my attention few days ago. The article compares FTP, cloud file sharing and cloud based PDM. Read the article and draw your opinion. I found something common between all these approaches – you need to transfer files between desktop or LAN server and some other (usually remote) locations – FTP, virtual cloud drive or similar storage used by cloud PDM. Here is my favorite passage:

Let’s look at a product development scenario. A designer has finished the preliminary design of a brand new widget. He is in a small design shop, so he keeps the files on his personal computer. He wants a rapid prototype of the design made so he emails the file to a service bureau. As the bureau is working up a quote for the prototype, the designer notices a few things and makes some tweaks. The file size is too big now, so he uploads it to his company’s FTP site and emails a notification to the bureau. But, because the project is still in development and no files have been released, the designer doesn’t change the revision on the file. It’s the same filename on the FTP site as was emailed previously to the service bureau. Now the bureau has two files downloaded to their system. Both with the same filename and both contain relatively the same time stamp caused by saving the email attachment at about the same time they downloaded the file from the FTP site. Rather than being able to quickly quote the part and begin shooting laser beams, they have to spend the time to reconcile the files, also taking up the designer’s time.

So, in my view, the need to send files between local computer and remote location is the weakest link to make that work efficient. Both PDM and any other file sharing service will face this challenge. And, forget the cloud and internet for a minute) it was the same challenge back in every PDM system developed in the past. PDM developers used different techniques to optimize file transfer, but the problem remains the same – slow connection and large files.

The move to the cloud, actually, doesn’t change much. The connection is still slow (relatively) and files are still big (or even getting bigger). As I discussed few days ago in my How to move CAD files to the cloud post, a special technology needed that will break CAD files synchronization process and make the process transparent. At the same time, user should be able to work on the same file to satisfy the scenario described in the beginning of this post. Whoever will be able to accomplish so, will take a huge advantage of knowledge about CAD files and improved user experience. Read more here – CAD companies and cloud storage strategy.

What is my conclusion? The weakest link of PDM is the ability to sync large multi-file design between local discs and cloud (server) storage. It was the problem back to PDM development in 1990s and it remains the problem today. Until now, cloud doesn’t change much, since most of cloud PDM and file-share vendors are taking CAD files with existing boundaries. To break these boundaries and develop technology to move file efficiently while allowing to user to work on the same files at the same time, can be a deal breaker and huge step to fix the weakest link. Just my thoughts…

Best, Oleg


Follow

Get every new post delivered to your Inbox.

Join 250 other followers