In my recent post on Open Source Software, I received a comment about Linux and its impressive stability. My comment back was that while I agree that Linux is very stable, and that stability is an essential component of any manufacturing system, usability is the essential component which is missing from many solutions currently in the marketplace. Open Source, or not.
Earlier today, I was discussing usability with someone and we got to talking about the conflict that is often faced between making a system as easy and intuitive for the user as possible, and making it as standardized and easily maintainable as possible.
In manufacturing, practically all HMI/SCADA screens are custom made for the specific machine they are designed to control. An operator can typically look at the screen and immediately see the process for which they are working, and visually identify where things are running well, or poorly as the case may be. On the other hand, up at the business layer, ERP systems typically are forms based and utilize out-of-the-box software which is almost entirely standardized. Some customization is usually implemented, but in general, the users are expected to conform to the software, not the other way around.
MES is stuck somewhere in the middle. I have been to plants who have a completely standardized approch to MES, others which have developed completely custom user interfaces for their operators to interact in, and still others which have integrated MES functionality into their existing HMI/SCADA solution to create a single solution for their operators.
My personal favorite of the above is the latter. Some time back, Microsoft had a very impressive video demo of their, along with Invensys Wonderware's, vision of the future of manufacturing after Longhorn, the next version of Windows. While this demo is more of a vision statement than a real product at this point, it is a very impressive look at how collaboration, and the integration of data from a variety of sources into a single view is very impressive. Giving an operator a one-stop shop for all their computer interaction will not only simplify their lives, it will reduce mistakes and improve their efficiency. Unfortunately, the vision presented in this video, I suspect, is one based on custom developed, site specific solutions.
Why do we need to choose? Wouldn't it be great if we could have both? A system which is tailored to our users needs and skill level, and at the same time, simple to maintain and upgrade. Sounds like a dream come true! Unfortunately, the dream is just that... for now.
What do you think? Which is more important? Usability or Maintainability? Or should we all start pushing for the best of both worlds?
Earlier today, I was discussing usability with someone and we got to talking about the conflict that is often faced between making a system as easy and intuitive for the user as possible, and making it as standardized and easily maintainable as possible.
In manufacturing, practically all HMI/SCADA screens are custom made for the specific machine they are designed to control. An operator can typically look at the screen and immediately see the process for which they are working, and visually identify where things are running well, or poorly as the case may be. On the other hand, up at the business layer, ERP systems typically are forms based and utilize out-of-the-box software which is almost entirely standardized. Some customization is usually implemented, but in general, the users are expected to conform to the software, not the other way around.
MES is stuck somewhere in the middle. I have been to plants who have a completely standardized approch to MES, others which have developed completely custom user interfaces for their operators to interact in, and still others which have integrated MES functionality into their existing HMI/SCADA solution to create a single solution for their operators.
My personal favorite of the above is the latter. Some time back, Microsoft had a very impressive video demo of their, along with Invensys Wonderware's, vision of the future of manufacturing after Longhorn, the next version of Windows. While this demo is more of a vision statement than a real product at this point, it is a very impressive look at how collaboration, and the integration of data from a variety of sources into a single view is very impressive. Giving an operator a one-stop shop for all their computer interaction will not only simplify their lives, it will reduce mistakes and improve their efficiency. Unfortunately, the vision presented in this video, I suspect, is one based on custom developed, site specific solutions.
Why do we need to choose? Wouldn't it be great if we could have both? A system which is tailored to our users needs and skill level, and at the same time, simple to maintain and upgrade. Sounds like a dream come true! Unfortunately, the dream is just that... for now.
What do you think? Which is more important? Usability or Maintainability? Or should we all start pushing for the best of both worlds?
2 Comments:
I think you should use a cool buzz word called "Standardized Flexibility".
Standardized Flexibility... I like it. So what does Standardized Flexibility look like? How can we make a solution which is flexibile enough to make your user's life easier but yet won't give you a maintenance nightmare?
Post a Comment
<< Home