Can PLM turn notifications into a process and vice versa?

June 10, 2014


Notifications are fascinating. We are all love to get notified. Alarms, emails, meetings… Later came social notifications such as likes, discussion comments and others. Enterprise systems are sending notifications about process states and many others.

Recent Apple WWDC presentation provided a snapshot about next evolution point of OS/X notifications. When iOS 8 hits, the notification center can easy become a center of universe for your iPhone. The same happens on Android device- notification screen is pretty much in focus of everything.


Wired article Why Notifications Are About to Rule the Smartphone Interface? provides an interesting insight on how notification functionality will developed and what is means for end users. Here is my favorite passage:

Interactive notifications will spur all sorts of new behaviors. (And yes, Android already has interactive notifications, but the ones in iOS 8 look to go beyond what KitKat can do.) Some of these will be simple, like the ability to reply to an email or text message. But they’re powerful in that you can do this without quitting whatever you’re already doing. And this interactivity is not just limited to system apps. Third-party developers can take advantage of this new capability as well, so you could comment on something on Facebook, respond to a tweet, or even check in on Foursquare. But others are going to be radical, stuff we haven’t imagined yet. Once developers begin to really harness what interactive notifications can do in iOS 8—and they will—it’s going to cause one of the most radical changes since third-party apps. With the advent of iOS 8, notifications are the new interface frontier.

It made me think, there is an opportunity for process management tools to leverage notification center ideas as well as use this spot for better experience PLM systems can provide. In most of the implementation, I’ve been involved, PLM systems are using email to get people involved into the communication about changes and process notification. Recently, instant messengers (IM) and live chats came to that place as well. New type of notification system can come to combine all aspects of communication into single interconnected experience. There is one more aspect. The ability of process management tools to capture existing notifications. It can be an interesting opportunity to simplify process planning for organizations.

What is my conclusion? Communication brings a lot of noise and inefficiency. This is a problem we have everywhere. On the other side, process is all about how to get people to perform in the most possible efficient way. It seems to me the new notion of notification can provide some alternative to old email exchange and buzzzzzes of alerts. UX architects and PLM technologiests should take a note. Just my thoughts…

Best, Oleg

PLM: Data vs Process – Wrong Dilemma?

August 7, 2013

Recent debate on Tech4PD brought back one of my favorite topics in PLM – data vs. process. The topic isn’t new, but it is not diminishing the importance. I found first appearance of my debates with Jim going to back in 2009. Navigate to the following link and read my old blog – PDM vs. PLM: Is it about the process? Another perspective on data vs. process in PLM was presented in my blog post – PLM: controversy about process vs. data managemen. The last one was inspired by Bell Helicopter presentation made during Dassault Customer Conference back in 2011.

Take a moment of time and watch the debate. I gave my vote to Jim. I like his broad perspective on setting organization on the right path with their working procedures. Jim also "packaged" his process opinion together with "file management", which made me assume that engineers will be able to identify right versions of a specific file/design. What made me feel sad a bit with regards to Chad’s position is his wiliness to focus on how to control all data in PLM – something I have hard time to believe as needed and even possible. To me PLM cannot control all data, but should rely on technologies to make data available for decision (and not only) processes.

The debate made me think about why Data vs. Process is probably a wrong dilemma in the context of PLM. In my view, the right focus should be on "lifecycle" as a core value proposition of PLM and ability of PLM to support product development. In a nutshell, product development is about how to move product definition (in a broad sense of this word) from initial requirements and design to engineering and manufacturing. If I go future, next stages of product definition will be related to maintenance and disposal. To define what represent product on every stage together with what is required to move product from one stage to another is a core value of product lifecycle and PLM.

What is my conclusion? After many years of debates about data vs. processes, I think time came to get to the next mature level of understanding how to get PLM work for companies. The focus on product definition for every stage of product lifecycle bundled together with procedures or requirements needed in order to move between stages can be a new way to define what PLM is about. Just my thoughts…

Best, Oleg

PLM and Engineering Task (Process) Management

December 13, 2012

PLM is all about process management. This statement comes to the play when people explain the value of PLM in the organization. Usually, when you think about process management, your mind is switching to some kind of "workflow thinking" mode, which assumes you need to follow the process from state to state by accomplishing tasks and activities. In every PLM implementation, this is a moment of time, people ask – how do we manage engineering processes? What toolset we need to have to make it happen?

I can see, engineering people, are bad organized. In many situations to run processes among engineers is similar to herding cats. To manage process in an engineering organization is a challenge. This is a place where PLM vendors usually fails to provide a reliable and simple solution. Engineers are asking for additional flexibility and vendors have a tendencies to provide a complicated solutions. Many PLM tools are providing sort of Workflow designer to create a process model. Later on, you can discover that engineers tend to abandon these processes. Main reason – these processes are not reflecting the reality. I wanted to come with some ideas how to fix that. I came up with the three definitions – tasks, engagement and information context. Take a look on the picture below.

The overall engineering process is described as list of tasks (above). This is the simplest way to present what needs to be done. It easy to digest and follow up. At the same time, the activity around this task list is not linear. In order to accomplish the task, an engineer needs to engage with additional people. This a typical situation when a person who leads the process needs to communicate with other people and comes with the result. Often, it is ad-hoc communication that cannot be formalized resides in people’s mind. Another situation happens when an engineer needs to bring an additional set of information to accomplish the task or make a decision. To combine these activities together is not a simple thing. Workflow is a wrong tool to solve this problem. To support a simplified task management tools with the ability to manage external engagement and connect to information context can be a potential solution to the problem.

What is my conclusion? The simplification is a key word to summarize my thoughts. In many situations, engineers will prefer a simple task list to get things done. However, tools need to provide a collaborative capabilities to connect the engineer’s activity to other people and additional sources of information. Just my thoughts. I’m interesting to learn how you manage engineering tasks in your organizations.

Best, Oleg

[categories Daily PLM Think Tank]

Kenesto vs PLM 360: Apples to Apples?

June 9, 2012

Earlier this week, Kenesto – new outfit of Mike Payne announced about general availability of their cloud based business process automation services. If you missed the announcement, navigate your browser to the following link. I blogged about Kenesto before – PLM, Kenesto and Process experience. Released version brings some additional features such as a cloud viewer from TechSoft3D, enhanced reporting and few more. According to Mike Payne:

We have built a product which works the way people want it to without forcing them to change how they work and which delivers technology in precisely the way people want to access it. With Kenesto 2012 we have reached an objective no PLM system has achieved before: practically zero implementation costs for deployment or training.

Autodesk PLM360 vs. Kenesto. Data management is a difference.

Randal Newton of GraphicSpeak coined an interesting term – unPLM. Navigate to the article to read more. Randal is driving some parallels between Autodesk PLM 360 and Kenesto. He is speaking about the amount of processes / solutions as one of the differences, but not only. Here is an interesting passage from the article:

The first product that comes to mind when looking at Kenesto is Autodesk 360 PLM, the cloud-based product lifecycle management system introduced earlier this year. Look past the cloud deployment, the openness about pricing, and the browser-based work environment and there are many differences. Autodesk 360 is aimed at the traditional PLM market, engineering departments; Kenesto is looking at wider deployment in the enterprise.

The comparison between "traditional PLM market, engineering department" and "wider enterprise deployment" is something that caught my attention. I navigated to the previous GraphicSpeak article – Autodesk launches cloud-based PLM. Here is a quote with examples of PLM 360 apps:

Autodesk says 360 is made up of more than 140 apps so far, which can either be used as-is or modified by users. The apps so far fall into ten categories: Quality, Supplier Management, Engineering, Program Management, Service and Support, Operations, Sales and Marketing, Manufacturing, Executives, IT professionals.

It looks like PLM 360 is clearly focused on how to cover all organizational activity and not stopping on the level of PLM for engineering department. When Kenesto is focusing on business automation, PLM 360 provides much more by allowing to manage data and processes beyond engineering. In my view, flexible and adaptable process managament is probably a differentitation. Kenesto can provide it on top of Autodesk PM 360 in order to serve broader set of end users in organization focusing on processes rather than on data management. For the moment, PLM 360 cannot support such a level of flexibility, and it creates an opportunity Kenesto can use. The right question to ask – for how long?

What is my conclusion? Process automation is an important function of many systems and applications. It can be part of PLM, CRM, ERP and other solutions. From that standpoint, Kenesto can potentially serve a much broader audience. However, PLM 360 is managing data. Kenesto is not doing so (at least, for the moment). So, Kenesto can come to the play when data-management problems already solved (or less important). Just my thoughts…

Best, Oleg

PLM, Kenesto and Process Experience

February 17, 2012

Kenesto just did the first appearance at SolidWorks World 2012 in San Diego. It was a good opportunity, to see Kenesto product in public. So, I did. I’ve been posting about Kenesto before. Navigate to the following link to read my previous post – PLM and Process Tools: Opportunity or Complication? So, I sat down with Kenesto team for the demonstration (disclosure – I’m serving as an adviser to Kenesto).

The big idea – flexible processes

The idea of Kensto is to move away from rigidity of process management and workflows – it called routes. You can push process flow to any person you want. It is fundamentally different from many BPM and PLM process tools that require you to define process flowchart before actually you are going to use it. From that standpoint, Kenesto just helping you "to document processes". This is about flexibility and ease of use. Here is the process that was built during the presentation:

Kenesto and Cloud

Cloud is another differentiation of Kensto. You don’t need to have to installed and configure the system. The only thing you need is to access it via browser. Kenesto runs on AWS. You can see the following picture of Kenesto architecture (taken from Kenesto whitepaper)

What is interesting to notice is the diagram on the bottom – three information objects (processes, documents, structures). I can see them as potential data models for PDM or PLM system. However, nothing was mentioned about these plans.

Kenesto Challenges

The idea of Kenesto is simple and I like it. I can see some challenges related to the way Kenesto communicates with ‘on-premises’ solutions. What I’ve seen during the demo, was only related to uploading of files. However, I’d be interested to see how customers will use Kenesto in a real life. Currently, in a beta version, Kenesto definitely is going to learn more about it.

Kenesto People

To make the story social, here are few pictures of people behind the Kenesto team. Sorry for not capturing all of you, guys – will do it next time.

What is my conclusion? All components of Kenesto are not unique. But here is the deal. Similar to iPod assembled by Apple from components available to everybody, Kenesto uniqueness is in experience it provides to a user. This is in my view, a secret sauce behind what company is doing. Experience is important. Bernard Charles, CEO of Dassault Systems was talking about "3D experience" during SWW 2012. Will Kenesto invent new "process experience"? Time will show. It has a potential. Just my thoughts…

Best, Oleg

Disclosure: I’m serving as an external adviser to Kenesto.

PLM and Process Tools: Opportunity or Complication?

January 18, 2012

I’d like to talk about BPM again. I was writing about BPM in the past. Navigate to this link to take a look on few pasts topics related to Business Process Management. Almost four years ago, I asked a question – Should PLM develop its own process tools? I think, the question is still not answered. Here is a quote from my historical article about what is the place PLM can take in the BPM game:

So where does PLM play into this game? I see two possible options: (1) PLM providers will focus on the development of process management tools; (2) PLM providers will allow the integration of PLM information and IP (Intellectual Property) into existing process tools provided by platforms. I believe that option (1) will be very helpful in integrating PLM systems into the enterprise software already available within the vast zoo of software within the organization, option (2) can simplify deployment and and keep the implementation of PLM simple.

I was reading Beth Stackpole Design News article PLM startup targets efficiency. It is a short article. Have a read and make your opinion. Don’t miss also comments to the article too. Based on what Kenesto is saying, manufacturing companies are still looking for good process management solutions. I found the following passage interesting:

…PLM’s tight ties to CAD still limit its use beyond engineering — a fact Kenesto is hoping to avoid with its process-automation-for-anyone approach…. traditional PLM is basically a process automation tool that is too complex to use effectively, prompting many users to circumvent it, using spreadsheets or email to share critical product data….Kenesto isn’t a replacement for PLM systems, but rather a different approach for solving the process automation piece of facilitating engineering workflows. Kenesto, which is cloud-based software, employs conventions that most users understand, like sending and receiving attachments, so it feels in many ways like a familiar email system…

The idea seems to me simple and interesting. Kenesto will be on the cloud, disconnected from CAD, providing graphical DIY tools to engineers to route documents and messages.

BPM and PLM: Integration Complexity

One of the biggest problems of BPM in the past was a problem of integration. Tools like SharePoint, WebSphere, and many others provided quite powerful solution to support processes in your organization. However, when companies tried to implement it, organization faced significant complexity to integrate existing “content oriented” systems (i.e. ERP, CRM, PLM) with process management tools (BPM). Most of BPM tools ended up acquired by large platform tools, and you can find them as part of larger platforms.

What is my conclusion? It seems to me “cloud” is a game changer in Kenesto play. By introducing solution in the cloud, Kenesto will try to simplify the process of integration with existing CAD, PLM and other enterprise tools. DIY approach can simplify IT life in organizing engineering processes. At the same time, it can introduce a challenge for IT trying to rule application and business processes and not interested to give it up to end users. The simplicity claimed by Kenesto can be another game changer. Kenesto is searching for beta customers. You can read more here. You can watch Kenesto in action to prove it right. Just my thoughts…

Best, Oleg

Disclosure: I’m serving as an external advisor to Kenesto

Process Simplification – the next goal for PLM companies?

January 6, 2012

It was a long time I didn’t talk about process management. The importance of process management is obvious. One of the main questions, companies are asking for is how to make process management more efficient and less complex. For the last 5-6 years, PLM companies put a lot of emphasizes behind the process improvement. Almost two years ago, I wrote – PDM vs. PLM: A process perspective. The ugly truth I discovered is that PLM vendors took "process orientation" as the next "sales tool". It is much easier to explain what system does for organization using "process language". At the same time, it is very complicated to provide a solution for efficient process management.

Most of PLM "process implementation" were about workflow and process tasks orchestration. One of the biggest challenges vendors are facing related to the level of process diversification in every company. Main element of process customization is actually the tool (process designer) you have at your disposal to define and manage processes. Some time ago, I posted -PLM processes: flowchart vs. rule-based. Take a look on this article, please. I’m bringing few examples how existing PLM solutions are solving "process and workflow" management challenges. Definition of a process in more traditional (flowchart way) can create multiple problems that preventing process management to be simplified. On the opposite side, rule based processes can get very complicated to understand and requires almost programming skils.

Lately, I found two examples of companies that working toward trying to simplify process management. One of them is PLM solution from Autodesk (Nexus PLM) introduced during AU 2011 last month. Second solution is related to a new company Kenesto.

Disclosure. I had a chance to speak with both Autodesk development team and Kenesto team about their solutions. Some of the information I have about these products cannot be disclosed in this blog because of NDA. I also advising Kenesto on PLM related topics.

Nexus PLM – simple, but insanely flexible

Slowly, but surely vendors are starting the understand the importance of the simplicity. However, in practice, it is very hard to understand how vendors plan to make it happen. About a month ago, I was watching a preview presentation about Autodesk Nexus PLM at AU 2011. Here is a screen shot of the future Autodesk cloud PLM solution. Autodesk is focusing on simplification. It is still hard to make a conclusion about the level of tool simplicity. Nevertheless, you can make your prediction.

Kenesto – new kid in the block

This is a new company on the PLM horizon. Actually, Kenesto is not brand new. Back-roots of Kenesto take you to another "simple PLM" solution announced about two years ago PLM+. I had a chance to post about them – PLM plus user experience minus complexity on demand. When Kenesto website is still under construction, you can download and read Kenesto white paper. Here is what you can read in Kenesto white paper:

Kenesto starts with a design tool that anyone can use. Kenesto’s powerful process designer uses a universal (and simple) set of graphics to allow a user to rapidly tell the system what he or she wants it to do. The screen snippet below shows how easy it is for people across the enterprise to create and participate in very sophisticated processes.

It is hard to say from only seeing this picture what is the efficiency of Kenesto process designer. On the surface, you can think about some similarity with other process management tools. However, it is user experience that matters in such cases.

What is my conclusion? Process management simplification becomes a very important imperative for PLM vendors. If it is done right, it can provide a clear differentiation. Most of PLM systems have a decent process management foundation. However, the real question is how to combine it with an efficient user experience and right level of flexibility. Just my thoughts…

Best, Oleg

Freebie. Kenesto and Autodesk didn’t pay me to write this post.

Picture by vichie81 /


Get every new post delivered to your Inbox.

Join 250 other followers