PLM One Big Silo

June 9, 2014


Silos is an interesting topic in enterprise software. And it is a very important topic for product lifecycle management. Why so? Because, PLM is heavily relies on the ability to work and communicated across the organization and extended value chain. Accessing information in multiple departments, functional domains and application is part of this story. Silos is clearly one of the biggest PLM challenges. At the same time, silos can be also a good thing. They are reflection of org structure and sort of order we can use to navigate inside of organization. posted PLM/ERP article – “Demolish the silos in PLM”: Why Dassault’s Bernard Charles believes in the 3D Experience. Read the article and draw your opinion. My understanding – Dassault System is combine multiple technologies and product belonging to different organizational domains to improve communication and information access across silos in organization.

Dassault System is not alone in the try to crush silos. Article is referencing other PLM companies’ effort to interconnect people and products. I liked the following passage:

The main idea behind DS’ 3DExperience is to provide the IT tools needed to break down the silos and connect the development work not only to software, electronics and manufacturing, but also to the end-customers. No doubt there are similarities and touch points between what this solution aims to do and Siemens PLM’s Industry 4.0 concept as well as PTC’s broader ALM, MES and SLM/IoT scope. The difference is that Siemens PLM places a higher priority on the engineering side of product realization, whereas PTC presently zooms in on the aftermarket and product-as-a-service concept.

Interesting enough, web is also got infected with the problem of silos. Large web 2.0 platforms are very similar to enterprise software silos, which put a lot of questions about availability of information across the web. There are quite lot of debates these days around the topic of web openness and information access. I’ve been reading Aral Balkan’s article – How Web 2.0 killed the Internet. The article contains a lot of controversial opinions about development of Web 2.0 and the way Open API used to support the development of huge centralized systems such as Facebook, Google, LinkedIn, Twitter and some others.

The thing that made me think the most was the question about Openness and Open APIs. Here is the passage from the article.

An Open API is simply a limited, revokable license to access and consume a certain subset of data and/or functionality that belongs to a closed silo. It is a visitor’s pass. The terms of the pass grant you limited access for a specific time. The terms can be altered — and routinely are altered — at the whim of the API owner. This is a painful lesson that many developers learned, for example, while working to add value to the Twitter platform by building Twitter clients. They were unceremoniously dumped after expending their energies to help Twitter build up its closed silo.

These two articles made me think about demolishing organizational silos, enterprise software, and future trajectories of PLM development. The term silos is misleading. There are organizational silos and application silos. The first (organizational silos) is something that needs to be demolished to improve communication and process transparency. However, the second one (applications) is something that will be built-up to connect people, applications and data. So, there is a high probability to have PLM One Big Silo built to solve the problem of communication and streamlining of product development.

The thing that raises my concern are related to open API. Enterprise software companies might have different reasons to product data compared to Google, Facebook and Twitter. However, fundamentally these APIs are controllable by vendors that can turn them off and on depends on the strategy, competition and many other reasons.

What is my conclusion? To build an open system is a very complicated task. I can see a shift towards creating of huge monolithic vertical silos. So, PLM One Big Silo is a very possible future for customers looking for smoothly integrated systems and aligned experience. However, my belief is that future will belong to open systems, which will bring an additional level of innovation and flexibility. Long term commitment of vendors for Open API is an important indication of software trajectory. Just my thoughts…

Best, Oleg

PLM Implementations Challenges and 3 Organizational Lenses

June 4, 2014


It is not unusual to hear people speaking about PLM implementation and changes that need to be done in the organization. Very often, PLM vendors or implementers are calling this process business transformation, which is literally supposed to make a change in everything that related to product design, engineering, manufacturing, support and services.

So, to implement PLM is hard. I can admire the power of some PLM technologies. At the same time, to make customer implementing and using them takes time and energy. PLM vendors understand that. PLM service companies aimed to make implementation successful by understanding organizational specifics, adapting business processes and configuring PLM software.

It made me think about how PLM implementation challenges can be mapped on some fundamental organizational behaviors. Organizations are often inspected with 3 fundamental lenses: (1) strategic (2) political, and (3) cultural.

PLM and Strategic Lens

The strategic lens is the most often applied perspective. Under this lens, managers are looking how to optimize work and meet corporate goals. This lens is responsible for processes and procedures. This is a place where all benefits of PLM can shine. However, very often, the application of PLM strategic transformation is triggering significant organizational turbulence in everything that related to processes and procedures. People dislike the change as well as tend to spend lot of time discussing how to make an optimal strategic process alignment. It drives lots of confusion and can derails PLM implementation.

To map existing organizational processes can be a good starting point to overcome challenges that PLM implementation can face with changes of processes and procedures. A good approach can be to apply changes in the specific processes without changing whole organization in a single shot.

PLM and Political Lens

The political lens looks at the distribution of power and influence. This is one of the most complicated part. This is a part where organization is distributing power and authority. The major challenge for PLM is related to the need to cross organization silos. Organizational silos are distributing power by separating data, people and responsibility. It is also separating IT stack and data ownership.

To bridge organizational silos can be a good way to optimize organizational behaviors and establish "political contracts". PLM can be a factor that consolidate people and help them to turn organizational silos into "cylinders of excellence".

PLM and Cultural Lens

This is probably the most unclear thing. It reflects underlying attitudes and beliefs. In many situation it reflects how culture and history of the company can affect their decisions. This is where you can expect lots of historical "PLM pitfalls" to happen. You need to understand the motives of people in power in order to be able to understand and predict their decisions. It will help you to influence them and increase PLM adoption.

What is my conclusion? Don’t ignore fundamental organizational structure and mechanisms. Strategic, Political and Cultural lenses can give you a good model to survive PLM implementation and make it successful for organization in all aspects. Just my thoughts…

Best, Oleg

PLM Implementations and PLM Egoism

November 13, 2012

PLM implementation requires the change. I’m sure you had a chance to hear about it more than one times. The idea behind that is somewhat simple – PLM implementation eventually going to change the way you are doing business, your product development processes, intercommunication between people, systems and, of course, the way you are making decisions. The theme of "change" during PLM implementation is reflected online quite well in PLM blogosphere. Jos Voksuil, my long time blogging buddy, is probably one of the most prominent supporters of "change" during PLM implementation. Navigate to the following blog – The state of PLM – after 4 years of blogging to read more about how Jos sees PLM technologies and implementations these days. Here is my favorite passage about PLM implementation and change.

I believe PLM requires a change in an organization not only from the IT perspective but more important from the way people will work in an organization and the new processes they require. The change is in sharing information, making it visible and useful for others in order to be more efficient and better informed to make the right decisions much faster.

During my long flight from Boston to Europe yesterday, I read “Ending the Cults of Personality in Free Software.” This write up resonated well with my thoughts about PLM implementation and change, because personality reflected significantly in everything related in design, engineering and product development. If you are long enough in CAD business, you probably remember that very often the decision about what CAD system to use was almost religious among some engineers and designers. You can see lots of similarity these days related to the decision about Integrated vs. best of breed PLMs. Another place where discussion is heating up is related to the conversation about open vs. close PLM platforms. It takes literally years for some large organizations to decide about what PLM platform to use. One of the best way to observe it is to attend customer presentations during PLM vendor forums. You can learn many stories about organization, history of product development decisions and endless PLM roadmaps.

What is my conclusion? I found PLM implementation discussion very similar to some technological disputes. The potential danger is the ego factor. When it comes, ego factor is going one way – up! Sometimes ego may lead to a something very positive and sometimes ego can be a significant destructive factor. Time is a good validation for many egocentric decisions. This is why ERP and PLM implementations are often cyclic with 5-7 years of people’s lifecycle in an organization. When PLM implementation fails, ego might provide a bad guidance. My recommendation to PLM people is to develop "ego-detectors" :). Another piece of technology to decide about on a long transatlantic flight. Just my thoughts…

Best, Oleg

PLM and freedom in business

April 11, 2012

business-networks-300x199.jpgIf you think about PDM and PLM, you will discover a lot of “controlling” functions. Examples are easy. You need to control documents, revisions, bill of materials, changes. Later, you need to manage and control processes. We’ve been living this type of environments for many years. Today I want to talk about something that I can consider opposite to ‘control’ – I want to talk about ‘freedom’. Wait… Bear with me for a moment and don’t kill me :).

I was reading Bryony Cole blog – The change toward human freedom in business. The blog pointed to a lecture of Thomas Malone (author of The Future of Word book) and his MIT lecture. I put a small fragment of Malone speaking below in my post

The interesting aspect mentioned in the same article is related to decentralized organization. Here is my favorite quote:

Malone’s ‘future’ describes an organisation built on decentralised decision-making. Leadership has moved beyond ‘command and control’ to ‘coordinate and cultivate.’ Technology is a key driver. These concepts are very much coming to bear in the organisation in 2012. He shows an awesome video at around 35 minutes about an audience of people ‘co-piloting’ a simulated plane through a set number of targets. The point being ‘it may be possible to have much more decentralised control than we usually assume is possible. If we do that, we may be able to take advantage of much more of the true energy and potential of the people in our organizations, than today.’

The idea of decentralized organization made me think about what role the future PLM systems will play in supporting of such a type of teams. The technology of controlling and process organization needs to change. The immediate requirement that come to my mind is related to the higher level of flexibility. The current function of PLM will be more focused on how people communicate around product rather than how people control the information about the product. The collaboration between people based on the usage of the online system will cause a change. In a “previous version of PDM”, we have been thinking how to protect people from making changes in the data controlled by somebody else. These days, the importance will be shifting towards “informing people” that somebody else is working on data collaboratively. The level of granularity will go beyond the level of “controlled documents” as a result of increased technological potential.

Another interesting quote to mention: Malone’s prediction that ‘technology will impact communications so much that employees will make sensible decisions for themselves instead of just following orders from someone above them, who supposedly knows more than they do, in a management hierarchy‘ is here already.

What is my conclusion? The technology matters. What we considered as futuristic projects 4-5 years ago, now becomes a reality. The scale of systems like Google and Facebook, makes us reconsider some fundamental behaviors of the systems we built for the last 10-15 years. PDM and PLM are an example of these technologies. A different level of flexibility in communication and information will become very important element of this change. Just my thoughts…

Best, Oleg

krishnan /


PLM, Organization and Information Silos: Good, Bad and Ugly

October 2, 2011

Earlier this month, I posted What is the biggest PLM challenge? Since then I had multiple conversations on twitter, blog and LinkedIn groups. Discussing a potential level of changes in the organization, I came to the topic of “information silos”. I found this topic interesting. Information silos – is it good or bad? Is it a problem at all? What PLM vision need to be applied to handle it? I wanted to quote one of my readers:

…It is about maintaining a trade-off between what is local and what is global in a company. The problem in my view is one of terminology. If we say “silos” we immediately think “bad”. This in turn promotes actions to minimize silos, which is harmful if driven too far. We need to conceptualize the organization in a different way. My take is “work practice” or similar constructs. An organization would be seen as a constellation of workpractices, each contributing to the overall goal of the organization. This would provide a perspective where trade-off, silos, business processes, etc., could be discussed from a more productive point of view.

I followed up the same topic on the round table during Autodesk Forum in Moscow. During the discussion, we found some interesting facts. Few participants mentioned that one of the challenges during PLM implementation is that PLM improve the transparency of processes and corresponded information in an organization. You can say – this is a really good thing. However, I’ve heard people faced organizational resistance. Information and process control is a power in every organization. So, people responsible for it don’t want to lose it. At the same time PLM streamlines processes it reduces the power of “gate keepers”. This is the ugly truth.

What is my conclusion? PLM is not only about technology. It can (actually does) change the way organization works top-down and bottom up. To manage this change is an important part of every implementation. However, PLM technologies nee to allow to make this change more transparent and less painful. Just my thoughts… I’d be interested to hear more about your experience. Speak your mind.

Best, Oleg

Collaboration Trends or Why I Stopped Using Google Wave?

January 11, 2010

We tend to use word “collaboration” very often in Product Lifecycle Management and related fields. Collaborative Design, Collaboration Product Data Management, Collaborative… I want to discuss how I see the world of collaboration can probably change in the future. The following four trends are my take on what will happen in the area of collaboration.

1. Infrastructure maturing.
This is obvious and not. In my view, the biggest collaborative infrastructure move for the last few years was introducing of “Unified Collaboration”. However, I think, this trend will continue and Cisco, Microsoft and others will provide more and more infrastructure solutions for the market.

2. Device-less. Collaboration will need to lose religious connection to the specific device. Growing cloud computing and improvements in the multiple device will disconnect collaboration from the “collaborative device”. We will collaborate using mobile phone, PDA, Tablet, via Internet, on multiple devices in your office.

3. Going beyond applications. The context will become The King Of Collaboration. However, you need to have rich set of information in your hands in order to set up context for collaboration. Such set of information in PLM can come only from multiple applications – requirements, analyzes, design, manufacturing planning, etc. Collaborative tools will need to go beyond a specific application to be really useful in the future.

4. Collaboration – not social. I think the name for “social” inside of organization is “collaboration”. It will take some time to understand it, but this is really true. In place of social networks, friends, connections, etc. will come organizational structures and collaborative work. However, lots of social nets practices will be adopted for new collaborative organizations.

5. Growth in enterprise search. I think, enterprise search will need to learn from success of web search. Today is still not happening. However, as much as organizations produce more and more data, search will become an important function. Today search is the commodity and very primitive in organization and new collaborative application will have to change it.

Now, how it related to Google Wave? The Alpha preview of Google Wave was announced last year on I/O conference and got a lot of visibility, discussions and speculation. It was the fist time, after introducing of Google Mail, people have tried to get Google Wave invitation even for money. Few month later after initial I/O demo, Google released about 100’000+ invitation and, in my view, satisfied the need of researching communities. Now, the ugly truth is that despite huge expectations related to how Google Wave can improve and change people collaboration, for the moment, it doesn’t happen.

What are top failures of Google Wave, for the moment?

1. Isolation. Google Wave is terrible connected to the outside world. The technological promise is in place, but practically it still not happened in beta/alpha versions. It will take time to develop all connections that allow GW to become part of your day-to-day work.

2. Another application to run. This is related to previous point. But, today, you need to run it, follow this application, etc. This is like another mail. Somewhat you need to spend more time to work on…

3. Documents and other Google App integration. This is a place where Google needs to learn from Microsoft, in my view. Microsoft’s folks did a great job integrating SharePoint and Office Apps. Google Wave need to do the same with Google Apps. This will be part of their mutual success.

4. Inbox management. This is similar to mail inbox. And need to be improved. I still don’t know how, but feels like we cannot drag old email inbox problems into new collaborative world :).. This is a place to innovate.

So, what is my conclusion today? I think we will see growing interest in collaborative platforms and application in coming couple of years. However, organization will hardly accept “yet another application to collaborate”. The platform trend will be very strong and will require certain integration and “collaboration” inside of organization. The ideas of social networks, enterprise 2.0 will be proliferating in the organization and mature in the way of open collaborative platforms.

Just my thoughts.
Best, Oleg

Can we scale PLM down?

September 1, 2009

Picture 1Originally, PLM was born to provide solution for big enterprise customers. Aerospace, Defense, Automotive… these are original roots of today PLM kings. But, since we are moving forward many companies started to investigate in possibility to take PLM ideas to different domains, industries as well as apply it to be used for smaller customers and not only to industrial behemoths like  aerospace and automotive OEMs. In your comments, I got few requests to raise this topic on blog and discuss, so here we go. I don’t expect to finish this topic in one post, so today I want to talk about fundamental grounds behind topic of PLM for different company sizes. I’d like to put few buckets to make our discussion more structured.

Marketing. Just to make things clear. We live in dynamic world that creates multiple opportunity for product marketing. I believe marketing around PLM is very strong and interesting. One day we discuss it too, but not today. I think customer’s demands are similar if we talk to them about their needs such as product cost, regulation needs and distributed development and manufacturing. PLM marketing is focusing on explaining how PLM can solve these problems, but won’t be the only solution for these problems and needs solving. I raised these issues multiple times before discussing how different product and technologies can be positioned to solve the same (or similar needs).  

Company IT. When I think about PLM of different scales and different organizations, the first thing come to my mind is what IT organization company have. Obviously IT of big enterprise won’t be equivalent of small business IT combined from very few people. So, ability of IT to handle operational and technological issues are crucial to understand what type of PLM technology we need to come with.

Technology. So, we agreed – we need different PLM technologies. In my view, these days we are facing a very significant wave or technology and business/technology combination. Microsoft is coming up to enterprise very actively. Traditional big-IT focused companies like IBM, Oracle and others are trying to establish their strategic position. On opposite side, SaaS and Cloud technologies becomes more mature and attractive for enterprises. I think, companies of different sizes will be deciding also based on technological choice. So, PLM companies need to be prepared to multiple offering or understand niches of technological marketplaces

Company Processes and Organization. When IT abilities and Technological preferences are fundamental things companies will analyze, issue such as company processes are definitely need to be taken into account when you come with PLM-bag to organization. What is good for big companies won’t fit way smaller customers are doing their business. Smaller organization are always will be more agile, connected and open compared to bigger enterprise and therefore, will be focusing on different priorities and needs.  So, don’t develop very complex ECO for the company of 100 people and 5 engineers.

So, what is my conclusion today? Different companies are doing business in different way. There is strong influence of IT, Technologies and Organization processes on the way product development and manufacturing systems need to be established, implemented in supported. I’d be thinking about next discussion with more specific themes and looking forward for your comments.

Best, Oleg.

How many Lifecycles do we need?

August 25, 2009

how-many-lifecyclesYesterday, two separate article got my attention and brought me to think about Lifecycle. Alternatively, even more, about number of systems claims different lifecycle support. Jim’s Brown thought about QLM Quality Lifecycle Management and TEC article What keeps EAM/CMMS away from PLM“. Why I choose these two is because they are presenting a complimentary story, in my view.

Jim claims Quality is a complimentary process to Product Lifecycle. Manufacturers these days cannot take risks and afford quality issues rising up, so QLM processes need to be adjusted and/or work together with Product Lifecycle. At the same time, Jim mentioned that many of today’s PLM systems doesn’t have QLM capabilities and some hybrid PLM/QLM would be probably interesting combination, we can offer to customers. I’d agree with Jim - with PLM system capable of manage overall product lifecycle, we’d better had Quality related processes connected and working together.

If I read correctly TEC, Kurt Chen presents in his article need to tie PLM and EAM systems together and analyze possible ways to do so. These processes represent both sides of product-related activities. First- from a product development side, second- from side of purchasing. What I liked is presenting of “two-sides of the story” of the same lifecycle.

I thought, these two stories is excellent examples to stop considering product-related processes as a something separate. Today’s organizational goals can be achieved only if we will be able to establish single lifecycle to manage all product-related activities in organization across department, divisions and cross-organizational boundaries. The siloed approach won’t work anymore. And I think demand on customers today is to establish such approach.

So, that’s what I thought about “lifecycles”. What do you think? What is your opinion? Do you have similar discussions and/or thoughts coming from your organizational experience?

Best, Oleg

Why I haven’t bought PLM yet.

June 26, 2009

Well, Product Lifecycle Management sounds like a very profound concept. I can see organizational benefits, values, etc… etc… But I’m not buying yet! You are probably familiar with such behavior – it all sounds good, but people are keeping their positions and not moving. So, I tried to analyze and talk with a few of our customers.

Here is my list of “why I’m not buying yet”?

1. Complexity. This is key. I mentioned it yesterday in a separate blog post called “Complexity Kills…”. It’s too complex to be true. I’m afraid that when I start following all the processes, recommendations, models, and user interfaces…. I see too much. So, in this situation, my reaction is – you guys are too smart and too complex for me.

2. Need to change the way I work. PLM comes with a state of mind “We know how to change it — believe me!” My user’s position here is that I want be able first to see how PLM handles my environment. So, from this standpoint, I want the company to be able to implement PLM, see how it works in not optimized way and then optimize everything.

3. Additional hassle to handle. Unfortunately, this is another system on the table. I need to learn it, handle it separately, ultimately work on this system separately. So, I don’t like this idea :) …

4. Want LEGO approach. This is want I want. I want my PLM LEGOLAND. I want to add blocks as easily as possible – to play with them, allow to users to play with them, and only after we’ll see how it flies in the organization – by moving it to the user’s daily work. And… one more thing: Users need to be part of this process. They need to provide inputs interactively– not only to see it.

So, what is my bottom line? I want to go with the Toyota approach – “test before design”.  So, afterwards, we will make the system simple — the main approach will be to see how the system can work in the organization AS IS, use it, and improve it with small steps. All this will help people want to buy PLM to improve their daily work within their organizations.

What do you think?

How PLM can re-use SharePoint Social Network Capabilities?

February 16, 2009

How can we improve user adoption of PLM in the organization? What technologies can we use?? How can we reuse what we already have? I’ve found that many companies are using Microsoft SharePoint. It’s interesting that although SharePoint provides a lot of capabilities, not all of them are used by organizations. When capabilities, such document and content management are widely used, capabilities relating to organizations and supporting social networking are really undervalued. I think that these social networking capabilities can be adopted and merged with PLM/PDM system capabilities that are already available. These will create significant additional value and will let you distribute product related content (i.e. product design, specification etc.) in the organization.

 So, how can we make this happen? The following SharePoint components allow you to create social environment:

User profile

These are foundational components that collect and store information about user in SharePoint. The information is collected from multiple sources such as Active Directory, Human Resource Information System, and Business Data Catalog of external systems. SharePoint allows you to aggregate all these multiple sources in a single representation of the user profile;

My sites

Individual sites are created for each user profile. My Site is a view for a user profile containing personal and public information, as well as an aggregated view of all related information – content libraries, lists etc. My Sites allows to user to present information about their role in the organization.

Colleague web part

Colleague web parts let you present your mined and sorted colleagues to visitors by a colleague list. These colleague lists are compiled to represent organizational structure and people relations in the organization.

Colleague tracker web part

The colleague tracker web part allows a member of the organization to view privately his or her list of compiled content. For example, users can modify the colleague tracker to present their list in context of the products for which they are responsible to develop in context of other roles in the organization.

SharePoint sites, links and membership web parts

These web parts let users view their own SharePoint site, group and mailing list memberships and links.

In common Web Part

This provides a summary of information relating to membership, organizational managers and colleagues that visitors have in common with the owner of My Site.

The following standard tools in SharePoint can be used to discover and search for the appropriate people with whom to collaborate:

People search

This is a standard web part for discovering people profiles by using user profile attributes.

People search by user profile

Search capabilities are based automatically on the same properties of the user profile. For example, individuals with specific skills can find people with the same skills in the organization based on their user profile information.

So, now, when we establish a social environment the purpose of PLM here is to work to provide content and/or information that can be accessible by people in the organization. There are a lot of ways to do this:

 Publishing document libraries

Generate documents and put them into SharePoint libraries. This can be done automatically and/or manually.

Using excel services and reports

This is similar to document libraries, but uses MS Excel-based content

Using business data catalog services

This is a more complicated way of accessing as it requires programming and developing of the access data from the external system.

So, SharePoint provides a set of social tools to organize your communities in the organization. By linking these social communities and PLM content, you can deliver product information to the appropriate people in the organization. In many cases you can leverage existing PDM/PLM products MS SharePoint. 



Get every new post delivered to your Inbox.

Join 244 other followers