Autodesk 2014: How Will the Cloud Affect PLM?

Today, Autodesk presented a look at their 2014 portfolio along with a preview of their offerings for building, plant, product, and factory design. If you missed any of the information, you can check out the CIMdata write-up: Autodesk 2014 Design and Creation Suites Give Flexibility to Innovate More. Or you can look at more information on the Autodesk website.

Autodesk has also introduced a re-branding for all of their suites. You can see the new logo above. Don't be confused, it's not the logo for Google Drive; that wouldn't be right. Along with this new logo comes new capabilities that seek to leverage the advantages of the cloud, and tie these suites together in a way that will benefit customers. How this works in the future and in practice is still an open question. Autodesk said there are already millions of people taking advantage of their 2014 solutions.

This started me thinking about PLM in the cloud and how Autodesk might leverage this technology to make PLM more robust and ubiquitous throughout major corporations. I think Autodesk is taking the lead in this area as they roll out solutions that feature a cloud model, without making the cloud a big deal. Subscriptions to these kinds of tools are not new; Aras PLM and Arena Solutions have been PLM pioneers in this area. But, with Autodesk there is a considerable user base and a large breadth of solutions that makes this an interesting experiment to watch.

I want to see how large corporations will adopt PLM cloud technology to support their global organizations. Larger companies will likely already have some type of private cloud that they use for many activities. However, having the ability to use PLM applications that are designed to take advantage of the cloud could be a real payoff for PLM. These new tools would be smart enough to know when to use the cloud and when to use local resources. The user should never have to tell the application that they want to use "the cloud"; the applications should be smart enough to know about the available resources, and use them efficiently.

I am looking forward to seeing smarter PLM solutions that will take advantage of the could and any other available resources automatically. But, I think we shouldn't be continually talking about the cloud. That's like talking about what types of disk drives are used by IT, and where they are located. The bottom line is: we don't care! IT cares, but the PLM user doesn't care. Just give us all the resources we need and get us what we want when we want it. To PLM solutions providers: give us intelligent tools that anticipate what we will do, and make sure we have as much resource as we need to get our jobs done. I don't want to worry about the cloud, or federations, or multi-tenants, or anybody else living in my cloud.

I think the less we talk about the cloud the better. The cloud is often nothing more than a Red Herring. We get hung up on what it's all about, when all we really want is efficient, easy to use PLM. I hope the cloud is part of that equation, but let's move on.

What do you think?

Jim

Cultural Change Management or How I Saved PLM!

It was dark; too dark. The rain pelted my hat and left crusty pools of congealed slush around my feet. The wind blew hard against my back and produced a rhythmic swaying like that of a tall tree that is being cut down, just before it falls: gracefully tracing an invisible arc in the sky. The only light was a sharp point at the other end of the room, barely visible in the harsh conditions. After considerable effort, I reached out my hand to push the puny button and the neon lights above my head sprang to life.

I stood under the harsh lights of the server room. With the door closed, I was able to breathe freely  for the first time in several hours. It had taken me some time to traverse the many hallways and cubicles, undetected, to finally come to this place. Several rows of servers stood motionless, gleaming in the glow of halogen warmth, their lights blinking and flashing in a symphony of digital magic. Somewhere in the distance, a low beeping sound brought me out of my stupor; I had to act fast.

Quickly, I ran between the rows of digital sentinels looking for the one that held the key to my visit. They all looked the same, standing there with those unfeeling eyes; judging me; taunting me; profiling me. But, I would have the last laugh, not them. I pulled a crumpled piece of paper from my pocket to see the barely legible scrawls that would identified my target.

At last, I saw the one I was looking for. I stood before my prey and wondered what the thousands of users would think when many of their favorite applications would no longer be available. I imagined they would stare at the screen, bite their lips, and profane silently. Maybe now they would be forced to log into the new PLM system we had just rolled out. Maybe now they would make an effort to learn how easy it was to search for information, collaborate with their colleagues, and find the latest version of any file.

With one decisive stroke I pushed the glowing green button, and with a low whine, the fans stopped running, and legacy applications were no more. The digital crutches that so many had used for so long were gone. No longer would they be able to submit an Excel spreadsheet, and call it "current"; no more guessing about where the latest version resided. It was deceptively easy. It took only a small amount of effort, and PLM was saved. I had saved PLM!

It was than that I heard a low rumble. The moaning and whining of thousands of users, and the groaning of managers all over the company; it would be a long night...

But, I had saved PLM. Instead of being able to ignore the new PLM tools, the users would be forced to use these new tools and learn better ways to do their jobs. There would be no way to get around our corporate workflows to support engineering change activities. Now our many pages of configuration management rules would need to be followed, or no work would be accepted. I knew this was not the recommended way to manage cultural change during a PLM implementation, but I had no choice.

If I had done this properly, I would have created a Cultural Change Management Plan, long before we ever rolled out one piece of new software. The plan would have included advanced education for our super users in every organization. They would have been a key part of our roll-out plan, and they would have helped us educate their users. We would have had some excellent user group meetings with free pizza, to let everyone know what was happening. We would have communicated frequently to make sure everyone felt good about the new system before we ever rolled it out. We didn't do any of that, and that's what brings me to this server room to do this dirty deed.

Please, learn from my mistakes. Make cultural change management an important part of any PLM planning activity. If you don't know what to do, there are people who can help. Do it right the first time, and you won't be the bad guy...like me.

What do you think?

-Jim