PLM and Global Product Development Strategy

December 13, 2011

Manufacturing business become global even for very small companies these days. It is not unusual to see a company of 100-150 employees having multiple locations using suppliers world wide. How these businesses can survive globally and what systems they need to use? What solutions are available today to support global product development? I decided to put some thoughts about that as well as share some articles related to this topic I had a chance to read earlier this week.

Global PLM system deployment

To support global product development is one imperative objectives for every PLM software provider. Obviously, PLM mindshare vendors are thinking about that. Navigate your browser to the article in Cadalyst few days ago – Break Down the barrier to Global Product Development written by Brian Shepherdof PTC. Brian’s view on global product development and role of PLM can be summarized in the following passage from the article:

Product lifecycle management (PLM) is a key component of GPD. PLM enables geographically dispersed individuals and groups to work collaboratively on products and product development processes through a seamless, integrated information flow.

I found the notion of "integrated information flow" interesting. Later in the article Brian is talking about 5 challenges to achieve global product development – distributed design, collaboration across the enterprise, share data securely, manage complex programs, manage change and achieve scalable performance. The approach PLM mindshare vendors are proposing (and PTC is clearly one of them) is to organize a single environment for people to work collaboratively.

The question I wanted to raise and discuss is how to drive global deployment of such a complicated system as PLM across multiple locations, divisions and departments. This is can be a multi-year complicated and expensive project. None of the challenges mentioned in Cadalyst article are covering this topic, and it surprised me a bit. One of the main problems I see is related to a nature of heterogeneous environment in every global organization.

The Reality of Heterogeneous environments

The global organization is normally heterogeneous. The reason for that is related to the fact how most of global organizations were created. I can see two typical cases – establishment of remote manufacturing facility or acquisition of another company, which includes both engineering and manufacturing functions. In both situations, the biggest problem is to integrate multiple heterogeneous systems into a single one. Alternative is to keep working systems for some time and establish a new system gradually. This process can be complicated and expensive. In many situations, companies are leaving with existing systems for a very long period of time.

Global Part Numbers and Global Development Strategy

Thinking about how organization can shift successfully to a global model, I’m coming with my 3 elements of potential global development strategy:

1 – share data across locations;
2 – establish global identification for items and documents
3 – integrated engineering and manufacturing environments

Steve Amman of Zero-Wait State wrote about why use of intelligent part numbers is a wrong way to think about when you want to establish a global environment. Here is an interesting passage from Steve’s post – What is so difficult about product development strategy? Let’s start from Part Numbers…

The old way is to try to create or use an existing divisions “intelligent” part numbering scheme that was set up before we had modern PDM, PLM and ERP systems. Part numbers can be coded with prefixes and suffixes to represent different part types, product lines, and commodity codes and a whole bunch of other translations for the numbers so they can be organized mostly on a spreadsheet. The more information you are trying to code into the part numbers, the more you trap yourself into this old methodology.

As an alternative, Steve is proposing to use the power of PLM meta data to classify information instead of intelligent part numbers. This is can be a complicated goal if your global PLM environment is not established yet. An alternative to this approach can be the establishment of sharing network with the information resided into existing systems.

What is my conclusion? I think, global product development startegy is hard. I can see companies are working years to achieve that. Even very well organized companies are crashing to deliver the results in a short period of time. Taking steps into sharing data, create an overall identification and integrate two most complicated systems – engineering and manufacturing can take a company in the right direction. Just my thoughts…

Best, Oleg


PLM Think Tank November top 5

December 11, 2011

I’m a bit late with my top 5 review for November. It was a tough month for me because of travels. I made double-Vegas. What does it mean you can ask? It means that Vegas this year became a top PLM destination. Back in June, PTC organized their annual conference in Vegas. However, in November, both Dassault System and Autodesk managed to have their annual customer events (DSCC 2011 and AU 2011) in Las Vegas.

I wasn’t surprised by the results of November’s top 5. Clearly, Autodesk with the announcement about Nexus PLM made a hit. Top two most viewable topics on my blog are related to Autodesk. So, with this short intro, let me take you to the list.

Autodesk Enters PLM: Everything Changes… for Autodesk

Autodesk is taking a huge step forward to deliver a different PLM. This is a significant step for the company that was focused on design tools for many years, starting from early AutoCAD days back 1980s. I liked cloud-based strategy and how it was presented by Autodesk. I can see it very promising. The analyzes presented by Autodesk people in PLM spaces shows that Autodesk is definitely learning from mistakes made by “big 3″ mind-share PLM providers. Focusing on processes is an interesting approach. However, it is important not to loose “data” grounds – it happened to many companies in the space of “business process management” (you can read more about this in my post – PLM controversy about process vs. data management). I want to learn more about Vault/ Nexus bundle. In my view, it contains a potential danger (similar to what happened with SolidWorks n!Fuze). Overall, I can see Autodesk is in the beginning of PLM learning curve. It is a very interesting time, and I’m looking forward to many fruitful PLM discussions.

Autodesk PLM Nexus – First Hands On Demo

Nexus PLM has nice and slick web user experience. Without practicall hands-on it is hard to say something about ease of navigation and the estimate the number of clicks you need to do to perform an action (click-per-action). These two things normally drive crazy users in data-oriented web environment. I found very positive the fact Autodesk is thinking about “insane customization”. However, it will be interested to see and experiment with how the complexity of customization will co-exist with cloud-based multi-tenant deployment. It reminds me one of my old posts – Is PLM customization a Data Management Titanic? Another critical aspect that wasn’t covered is data import or integration with existing systems (i.e. Files, Archives, Content Management, PDM, PLM, ERP, etc.). The answer Autodesk provided pointed to some internal development with Autodesk Vault as well as a future work with partners. That would be very interesting to see in the future. Overall, Nexus has a potential to disrupt. I’m looking forward to seeing how Autodesk will realize this potential.

PLM: Controversy About Process vs. Data Management

I think the failure to design data access in organizations, was a recipe for disaster for many PLM implementations. PLM programs were focused on “how to improve processes” and forgot about how to put a solid data foundation to support cross-departmental process implementations. So, I’d like to put a quote from Bell Helicopter’s presentation during DSCC 2011 as something PLM vendors and customers need to remember – “to get the core data right first”. Just my opinion, of course. YMMV.

Autodesk: CAD is done. Now PLM. The moment before AU…

You can see how Carl Bass, Autodesk CEO re-defines ‘business casual’. In addition, I’m trying to make my conclusion about what I’ve heard in the connection with PLM. Autodesk is definitely recognizing PLM as a future opportunity. After what was done in PLM by Dassault, Siemens PLM and PTC, to democratize PLM will be probably a biggest challenge for Autodesk. Just my thoughts…

DSCC 2011: How Dassault Blends PLM and Search Based Applications?

Dassault is clearly innovating by adding Exalead technology to their portfolio. As Laurent mentioned during our conversation, everybody these days understood that the ability to handle information becomes very important. Search technology is an interesting competitive advantage Dassault is having. Compare it other CAD/PLM players (Siemens, PTC and Autodesk) – they need to outsource these capabilities to companies acquired by Oracle, Microsoft and HP. I believe Exalead will be used by Enovia to improve their search capabilities. I haven’t seen a demo of this, but assume Dassault will replace Autonomy OEM by Exalead. Delivery of EXA-like applications sounds like an interesting trend. However, speaking about Enovia vs. Exalead platform it is still hard to see how they are blending together. Which, of course, can be played nicely by saying – it is all part of DS V6… voilà. Just my thoughts, of course.

Best, Oleg

Picture credit to Shaan Hurley blog


Crowd-sourcing in CAD / PLM software development

December 11, 2011

The topic of crowd-sourcing is fascinating these days. Community based development is interesting topic, and I’m continuing to follow different aspects of crowd-sourcing and finding new examples. I had a chance to write about Local Motors few weeks ago – it was a perfect example of crowd-sourcing and community-based development. Earlier today, I had a chance to read about interesting examples of how Autodesk is using crowd-sourcing to improve localization of their products. Localization is a complicated topic. Even if you’re hiring the best bi-lingual people, your software won’t be perfect.

Autodesk is proposing for users of Inventor 2012 to participate in the project to improve Autodesk Inventor translation. Navigate to the following link (in Russian) and you can see how you can propose a new translation for a specific term and / or command.

I found another interesting example in crowd-sourcing in PLM software – Aras Community roadmap. Navigate to following link and see how you can actually "vote" for specific features and functionality.

This story is specifically ineresting in my view. The ability of software vendor to manage in a very precisely way what features and functionality need to be implemented is a complicated product management objective. To use crowd-sourcing principles in this project is a very interesting and innovative approach, in my view.

What is my conclusion? Crowd-sourcing is fascinating and inspiring. I think it opens additional opportunities in the way nobody thoughts before. It is promising, and I’m expecting more in the future.

Best, Oleg


How to streamline PLM?

December 10, 2011

One of the biggest problem I can see in all PDM / PLM tools is a high level of the complexity. I’ve been thinking about it many times. After observing this industry for quite some time, I started to come to conclusion that solutions are becoming more complicated without becoming more functional. I’ve been reading the article The case for stripped-down enterprise 2.0 tools on by Moly Bernhart Walker. He was quoting Tim Young of Socialcast. Here is my favorite passage:

"Simple tools are incredibly powerful," said Young Nov. 15, during a keynote at the Enterprise 2.0 Conference in Santa Clara, Calif. It’s very difficult to solve a complex problem with a complex tool, he added. What we’ve been doing with customers is actually moving away, stripping away functionality and making it very, very simple by just focusing on one or two activity screens. And we’ve actually begun to see the value in this," said Young.

I decided to pull few old pictures of EDM and PDM tools and take a look on them from the angle of PLM 2012.

How to strip-down PLM?


I think, we’ve been obsessed by the power of computer, higher screen resolution and interest to push additional functionality in the PLM software. It is a time to stop and think. Here is the slide from last presentation I’ve made during Autodesk University 2011.

PLM software is bloody complicated. To find a right strip-down option will be an appropriate way to think about the next PLM solution.

What is my conclusion? PLM was born many years to solve the problem of product development in complex defense and aerospace companies. Since that time, software vendors passed a long way developing new functionality. However, I don’t think it made solutions better. It is very hard to remove functionality for existing software. At the same time, I don’t see any alternative to that in the future. Just my thoughts…

Best, Oleg


PLM Highway and New Dassault Waltham Campus

December 9, 2011

I’m sure, you are familiar with highway 101 crossing Silicon Valley. However, you probably never heard about PLM Highway in Boston. After last week Autodesk PLM announcement and Dassault System move to a new campus in Waltham, I think we can officially suggest to rename Massachusetts Route 128 (also known as Yankee Division Highway) to PLM Highway. The map below prove it. PTC, Dassault, Autodesk, Siemens, SAP, Oracle. These are top six providers of PLM software with offices located along Rt 128.

As a blogger, I was invited by DS to visit their new office and to attend ribbon cut ceremony. Bernard Charles, DS President and CEO and Al Bunshaft hosted this event for media and journalists. After short briefing and visiting virtual reality presentation room, we’ve been taken to the campus tour. I’ve honored by having Jeff Ray walking together with our group and providing explanations about the building. Below you can see few pictures I made during this event.

You can find more pictures on DS Campus Tumblr page.

Best, Oleg

Freebie. Dassault didn’t pay me to post about Ribbon cut ceremony.


Autodesk, Aras and Integrated PDM / PLM story

December 7, 2011

Back to the beginning of this year, I came with the post – Integrating PLM and PDM. Wrong question? My initial thoughts about integrating PDM and PLM was driven by growing interest to integrate existing software assets in the companies. However, thinking more I can see some additional aspects of PDM / PLM integration in a longer-term perspective. Few weeks ago, I postedFrom PDM to PLM: Unify vs. Integrate. I can see some examples of "integrate trend" happens now. I wanted to discuss two examples. Both Aras and Autodesk, in my view, are trying to integrate existing PDM systems with agile and flexible PLM environments.

Aras Enterprise PLM

If you haven’t had a chance to review it, Aras EPLM is a new packaged offering coming from Aras and expanding SolidWorks Enterprise PDM horizons by providing additional process oriented applications in Aras PLM. I recommend you to take a look on Aras EPLM on-demand webcast. Based on the information I found on the website, the functional scope of Aras EPLM related to Item and BOM Management, Product costing, Supply Chain processes, Project management and Change Management.

The clear strategy of Aras is to provide a complementary solution to SolidWorks and EPDM. I believe SolidWorks customers are looking for this solution as the opportunity to keep SolidWorks EPDM, to have an additional functionality and eliminate probably more expensive and unclear migration towards future Enovia V6 solutions DS is planning to deliver in the future.

Autodesk Nexus PLM

Another interesting example that just came last week – Autodesk made the announcement of Nexus PLM. Thre is little information and hands-on experience available about Autodesk PLM. You can navigate to my earlier posts aboutAutodesk Nexus PLM and Autodesk PLM strategies. At the same time, from the top slide presented by Steve Bodnar, Autodesk VP of PLM, we can learn that Autodesk is building their PLM strategy as a combination of two products – on-premise PDM (Autodesk Vault) and cloud based future product (Nexus PLM).

Looking on the scope of solutions Autodesk is promising to deliver as part of Nexus PLM, you can see some similarity with Aras EPLM Solution.

PDM / PLM Integration: pros and cons

If I think about possible advantages of combined solutions PDM+PLM, the one that stands clear to me is the interest to leverage existing software assets and re-use implementations cost already made by customers. When I think about the way Aras and Autodesk articulate what they do, I can see lots of similarities.

In that context, the cost of integration between PDM and PLM becomes one of the most important elements. Mindshare PLM vendors like Siemens PLM and Dassault are driving customers towards unified solution. They are trying to convince customers that unification will reduce the total cost of ownership and optimize the implementation. At the same time, if cost of integration is low, the type of solution proposed by Autodesk and Aras can have some grounds.

What is my conclusion? PDM / PLM integration looks like an interesting trend. We are going to see to see more examples, in my view. What is the fundamental reason behind it? I think many companies are having trouble to drive their IT infrastructure towards unification. It requires longer projects and expanded budgets. If PLM companies find an efficient way to integrate and access data between systems, it can definitely provide a competitive advantage on the market. Last one cannot be guaranteed, but it sounds as an interesting opportunity. Just my thoughts…

Best, Oleg

Image: dan / FreeDigitalPhotos.net


PLM and The Future of Appification

December 6, 2011

Mobile is very important nowadays. More and more people these days discovering opportunities to use "mobile version of something". It is interesting to see how the market of devices is affecting the development of products. To leverage the power of the device becomes absolutely important. I was reading TNW blog yesterday – Google Just Used Search Application to Sneak the major part of Chrome onto the iPad. I made a try and find it useful – take a look.

Last week, during AU 2011, I’ve seen how significantly Autodesk is investing in the business of mobile applications. One of the applications caught my special attention – Autodesk ForceEffect. Having my engineering background, I almost forgot about how tough it was to deal with force diagrams and calculations 25 years ago. So, I found the following video specially enjoyable – you can capture diagrams, use photo and cameras.

What is my conclusion? Introducing tools that can use new devices is a very powerful trend. CAD/PLM software companies won’t be able to avoid it. These two great examples are just scratching the surface of the level of importance mobile devices will have in today’s business. You can ask me how it related to Product Lifecycle Management. Two aspects: 1/ the power of the device; and 2/ granularity. CAD /PLM companies have the opportunity to delivery applications, they want to end users via cool mobile devices. Granularity is another important aspect. PLM is going to be fragmented into a large set of applications used by many people in the organization. One size doesn’t fit all – you cannot deliver a single application for PLM. Just my thoughts…

Best, Oleg

[tag Mobile, iPad, Apps, Appification, PLM]


Manufacturing Crowd-Sourcing and Cloud PLM Opportunity

December 5, 2011

Crowd-sourcing is a popular trend these days. For those of you out of sync, in a nutshell, crowd-sourcing is a way for a community of people to build, create, print, etc. anything. Here is the classic definition of crowd-source from Wikipedia:

Crowdsourcing is a distributed problem-solving and production model. In the classic use of the term, problems are broadcast to an unknown group of solvers in the form of an open call for solutions. Users—also known as the crowd—typically form into online communities, and the crowd submits solutions. The crowd also sorts through the solutions, finding the best ones. These best solutions are then owned by the entity that broadcast the problem in the first place—the crowdsourcer—and the winning individuals in the crowd are sometimes rewarded. In some cases, this labor is well compensated, either monetarily, with prizes, or with recognition. In other cases, the only rewards may be kudosor intellectual satisfaction. Crowdsourcing may produce solutions from amateurs or volunteers working in their spare time, or from experts or small businesses which were unknown to the initiating organization.

I had a chance to write about crowd-sourcing before. Navigate to one of my previous posts – Marketplaces and Engineering Software or NoPLM and Quirky Social Product Development. Earlier last month, I’ve been reading recent announcements related to Local Motors and SolidEdge Design1. I can see it as a big deal.

Navigate to the following article in Develop3D by Al Dean to read his commentary on this. Also, you might be interested to read Evan Yares’ take on this same topic in his post – Siemens PLM and Local Motors. Here is my favorite passage from Evan’s post.

While I think the Local Motors deal is interesting, what I find more interesting is the potential Design1 might have in Siemens’ (and its competitors’) major accounts, as a low-cost interstitial CAD tool for use by engineers and others who are not full-time CAD users, or who simply don’t need history-based CAD. I could imagine some companies (particularly large automotive companies) signing up for literally thousands of copies. It could make things pretty interesting in the CAD business.

I found another source of ideas looking for GrabCAD presentation during AU2011 last week (Unfortunately, I wasn’t able to attend Hardi’s presentation and ended up to catch it via slideshare version).

The connection of GrabCAD to crowd-sourcing services can be interesting because it will require additional tools that can help people to communicate and re-use data.

All this, made me think about a potential impact crowdsourcing models can make on PLM software development. Here is the idea, in a nutshell. Design1 is a good start. Local Motors needed a cheap CAD tool that can be used by the community of people. The community of people is obviously using the internet as a way to communicate. So, by doing that, one of the biggest concerns of cloud PLM (cloud security) will be dissolved. It means data will flow online anyway. Obviously, the community can be interested in having PLM tools to support data management, communication and processes across the community.

What is my conclusion? The power of community is fascinating. It can impact many aspects of software development. Will community be using Google tools or special PLM software dedicate to online usage? It is a good question. What is your take? Speak your mind.

Best, Oleg


Autodesk PLM Nexus – First Hands On Demo

December 4, 2011

I’d like to continue Autodesk PLM story I started in my previous post and share some of my thoughts based on hands-on experience with Nexus PLM. The demo was provided by Brian Roepke, Autodesk Product Director responsible for Nexus PLM.

Nexus PLM Architecture

Not much been said about Nexus PLM architecture, except of saying it is on the cloud. I haven’t seen Nexus PLM architecture charts during AU. From the conversation with Autodesk people, I can drive the following conclusion about how Nexus PLM is built. Nexus cloud is running on Amazon (AWS). The storage is SQL-compliant database (I can guess it is MySQL or Oracle) via Amazon RDS. As it was explained Nexus separates databases per customers in the cloud, so customer data is separated. It indeed provides some advantages related to the perceptions of the security. However, in my view, it creates some disadvantages when it comes to cross company usage of data. The last one can be a very interesting use case of global collaboration organization.

Applications

Autodesk is planning to release lots of applications using Nexus PLM platform. Initial focus is on the following five applications: new-product development, Program and process management, Quality and compliance, Supplier and partner management, Maintenance and services. The total amount of applications available on Nexus now is about 140 (this number probably includes Buzzsaw apps).

User Experience

Below you can see few screenshots of Nexus PLM. You can see the main user dashboard appearance and how Nexus gives you the access to object information (i.e. project).

The following pictures will give you a glimpse of how Nexus Project and Program management app works. It includes also scheduling module as well as elements of reporting and navigation.

Customization

Autodesk claims Nexus PLM to be "insanely configurable". What does it mean? According to the what I’ve heard everything can be customized. Well, this is probably too broad. From what I’ve seen user interface appearance, names and many other elements can be changed. During the demo, the flexibility of workflow was presented. It was related to the ability of flowchart and logic changes. It also includes the example of Java scripting.

Autodesk claims "everything can be customized" in Nexus PLM. The examlpes they presented related to workflow, rules and user interface appearance is great. However, I’d love to have a deeper look on these abilities when software will be available.

What is my conclusion? Nexus PLM has nice and slick web user experience. Without practicall hands-on it is hard to say something about ease of navigation and the estimate the number of clicks you need to do to perform an action (click-per-action). These two things normally drive crazy users in data-oriented web environment. I found very positive the fact Autodesk is thinking about "insane customization". However, it will be interested to see and experiment with how the complexity of customization will co-exist with cloud-based multi-tenant deployment. It reminds me one of my old posts -Is PLM customization a Data Management Titanic? Another critical aspect that wasn’t covered is data import or integration with existing systems (i.e. Files, Archives, Content Management, PDM, PLM, ERP, etc.). The answer Autodesk provided pointed to some internal development with Autodesk Vault as well as a future work with partners. That would be very interesting to see in the future. Overall, Nexus has a potential to disrupt. I’m looking forward to seeing how Autodesk will realize this potential.

Best, Oleg

[categories Daily PLM Think Tank]


Autodesk Enters PLM: Everything Changes… for Autodesk

December 2, 2011

It finally happened. Autodesk enters PLM business. After talks, speculations, discussions and guesses, Autodesk presented their Autodesk Nexus PLM product earlier this week during AU2011. I had a chance to read initial press and blog reviews related to Autodesk Nexus PLM. Here are few examples. Navigate your browser to the following link to read the official Autodesk press -Autodesk Introduces Cloud-based Product Lifecycle Management. You can read CBR - Autodesk unveils new cloud-based PLM tool. Blogosphere also provided coverage of what PLM was announced. You can read well-prepared post Autodesk and PLM: Strap Your Boots. It is coming by Al Dean (the author of my favoritePLM definition). Below is my favorite passage from Al’s post. This is, actually, one of the most interesting and, from my view,  controversial elements of Autodesk PLM strategy.

What Autodesk has effectively done is keep the server-based solution (Vault) where it needs to be. CAD data is too heavy for internet-based communications just yet. But then around this and intelligently linked to it is a set of cloud-based applications that can both provide input and are resultant as output from that data source and provide access to them in a lightweight manner. That means that whoever needs to use it can.

Few additional blog posts I notices: AU 2011: Autodesk’s 180 Turn with 360 by Kenneth Wong; AU hot topics by Monica Schnitger; Autodesk Enters PLM Arena by Managing Automation; Autodesk 360 for PLM by JTBWorld; Autodesk introduced cloud-based product lifecycle management solution by Enterprise Communication; Autodesk 360 by Cloud Tool Box.

In addition to all news and blog publications, you might be interested to read analytical review related to Autodesk and PLM written by Gartner - Autodesk Extends Benefits of PLM to Everyone at Any time from Anywhere.

PLM, Definition, History and anti-PLM rap

It is important to understand how Autodesk defines PLM. In a nutshell, Autodesk is taking an approach to focus on “M” in the definition of PLM. You can listen to “what is PLM?” definition provided by Autodesk VP of PLM Steve Bodnar.

Autodesk provided an interesting historical retrospective on PLM industry. Take a look on the follow picture. What is specially interesting is that Autodesk emphasized Arena as a first cloud-based PLM on this picture.

One more thing related to the history of PLM and Autodesk. Autodesk CEO, Carl Bass was famous by his anti-PLM rapback in 2007. Back, that days, he said PLM problem doesn’t exist. Carl touched this point in his AU2011 keynote.

Here is the 2011 version. Autodesk waited for technology to be ready for PLM. Autodesk waited for the time technology will allow to make PLM successful and available for a broad range of manufacturing companies.

Autodesk PLM: Conceptual view and package

The view on PLM presented by Autodesk was very straitforward and not unique. I’d call it PDM+. You can see a slide presenting this view below. Practically, it defines PLM as an expansion of “engineering PDM” by modules supporting multiple organizational processes. Historically, you can track similar definitions coming from other vendors (i.e.SolidWorks PDM first white paper)

As from packaging standpoint Autodesk Nexus PLM is part of a new bundle called Autodesk 360, which contains Autodesk 360 Vault and Autodesk 360 Buzzsaw.

Cloud Disruption and No Software

The fundamental element of Autodesk PLM strategy is about the cloud. In the early presentation for media, Autodesk Labs director Brian Mattews defined cloud as one of the 5 technology disruptions these days.

The strong message to support cloud strategy was provided by Carl Bass by making an association between Autodesk cloud strategy and what was done in the same space by Salesforce.com. Historical record – salesforce.com was pioneering SaaS applications and “No Software” slogan back in early 2000s.

What is my conclusion? Autodesk is taking a huge step forward to deliver a different PLM. This is a significant step for the company that was focused on design tools for many years, starting from early AutoCAD days back 1980s. I liked cloud-based strategy and how it was presented by Autodesk. I can see it very promising. The analyzes presented by Autodesk people in PLM spaces shows that Autodesk is definitely learning from mistakes made by “big 3″ mind-share PLM providers. Focusing on processes is an interesting approach. However, it is important not to loose “data” grounds – it happened to many companies in the space of “business process management” (you can read more about this in my post - PLM controversy about process vs. data management). I want to learn more about Vault/ Nexus bundle. In my view, it contains a potential danger (similar to what happened with SolidWorks n!Fuze). Overall, I can see Autodesk is in the beginning of PLM learning curve. It is a very interesting time, and I’m looking forward to many fruitful PLM discussions.

Best, Oleg

Disclosure: Autodesk sponsored my travel and attendance AU 2011, did not in any way influence the content of this post.


Follow

Get every new post delivered to your Inbox.

Join 237 other followers