How to Manage ECO without paying $1’500 per seat?

I had chance to read Buzz message thread about ECO management, initiated by Josh Mings. I found it worth reading. One of the questions stick in my memory, and I decided to put it in the title of my blog post today. How to manage ECO without paying $1’500 per seat? I think the point was made in a very clear way. Changes is a real life of engineering and manufacturing company. However, cost/value seems to be problematic for solutions we have available today.

Please, take a look on Microshare definition in Wikipedia.

To microshare is to offer access to a select piece or set of digital content by a specific group of invited or otherwise privileged guests in a controlled and secure manner. In contrast to public sharing of content, microsharing enables a more private or intimate level of making content accessible by others. Microsharing access can be secured via uniquely encoded urls or by password protection.

Let me take an example from Josh’s stream and translate it in microshare-like ECO-message-burst.

–>ECR#123 is submitted from customer services @servicecounter;
–>@servicecounter Looking on this ECR#123… Seems like a problem. Hold shipments;
–>Moved ECR#123 to engineering @engineeringhero;
–>@engineeringhero ECR#123 requires analyzes by #allengineeringgeeks;
–>@topgeek solution for ECR#123 is to disable radio switch off function;
–>@servicecounter hold shipments until ECR#123 fixed by @engineeringhero;

I hope you should get my hint now. In the end, I see collaboration as a message sharing in the organization. In before-computers-era, papers functioned as a message transferring mechanism. Then we invented databases, PDM, PLM…

PLM View on ECO Management
When all you have is a hammer, everything looks like a nail. When all you have is a database and SQL, you just need to translate all your problems in database and SQL forms. This is the way we have been working for the last 15-20 years. If we got a problem, we need to create a model, keep data in a database, retrieve it, save it, manipulate and, in the end, yikes! — we have a solution. What is the problem here? This is a long way that creates lots of complexities — manage a database, agree about model, implement, agree about how maintain changes, create a user interface, teach everybody how to use it and, finally also to fix bugs. This is a way we are doing PDM/PLM today.

Should Be A Simpler Way?
What if? What if we invented enough technologies that can help us to the same job in a much simpler way? If all we are interesting is related to a particular ECO#123, I can keep reference to these messages without inventing SQL Table Grandiose? I can just record it and want to be alerted, when something happens to this particular ECO. If you are doing something related to this ECO, you can put a message into microshare storage about that. Somebody, who is responsible for shipment need to see if there are any of messages or info that prevents shipment. You can subscribe to messages via something like RSS and get a single channel of messages coming to your mobile device. I know it sounds crazy to any straightforward database and/or IT guy. But, in my view it may work and simplify the life of many engineers in the organization. The infrastructure for microshare and RSS is much cheaper, compared to the development of data models, tables, UIs etc.

What is my conclusion? I think, we came to the point where everybody in the organization is looking how to work differently. It is not only about how much to spend on the particular software package. It is about how to organize work better and simpler. I’m taking “microshare” as an option. Yesterday, on Enterprise 2.0 conference, one of the presenters asked a question — How many user guides did you read in the last year? The answer was ZERO. This is a time to think about a simpler way. I want to credit Evan Yares blog for the picture, I put in this blog post. I think it is very valid these days.

Just my thoughts…
Best, Oleg



Share This Post