In a previous post, I gave an overview of the upcoming MOMi (Manufacturing Operations Management Institute) guide plus gave the first example, of configuration. Now, learn about Typology.
In the Last Post: MOMi Guide – Configuration
The link to the first post in this series will probably show up at the bottom of the post page. However, just to make extra-certain, here is the first post, again: The MOMi Guide – Overview and Configuration.
The MOMi Guide Typology
Where configuration is about “how” you implement a system, the typology gives you information about “where” to implement it. It gives an idea what types of labs this brand and type of software might run in.
The other purpose to this example is that you can see that MOMi has given limited responses. The scale is from 1 to 5. No-one can accidentally put a 0 or a 10, for example. Nor can anyone say 2.5 to indicate that it’s “about halfway there.”
Here is my reason for showing you this type of example. It is to help those of you who will eventually read The Guide to understand how responses have been elicited.
For example, some areas as for check boxes. Others have sliders, such as this. One of the purposes is just to make the responses easy to understand. Another purpose is to help enable visualization. Where you have a discrete 1 to 5 scale, you can more easily create a pie chart with some of the graphing tools than if you let people type numbers.
Typologies – More Thought
So, back to the actual typologies, themselves. What is the MOMI Guide Typology section really about? Let’s think about the variety of different situations out there.
First of all, I think we all know and actually do say that there is no product out there that is suitable for every situation. What we don’t specifically think about, though, is how suitable or unsuitable a product really is for a particular situation. Often, we think of it as an either/or situation. Then, we start looking at features.
Suppose that we knew that a software vendor believed their product to be best for the industry we are in. And suppose we also knew they felt it was not as good a fit as for some other industries. That sounds like an honest assessment to us. Hopefully, it is both honest and correct. But it might mean that we would give a little higher focus to the product, in that case.
Of course, let’s suppose someone claims they’re at a 5 for a “Commercial/QC” lab. Then, we see that they don’t have features that relate to manufactured batches. In that case, we still might not consider the product in our final list. Still, the fact that it helped us narrow our list down, at all, is still of value.
The Guide – Various Response Types
In any case, I just want to get across to the reader that different types of information require different response types. Some questions are more along the lines of “yes or no” or “true or false” while others might have some gradient to them, such as this one.
If you go back to last week’s example, you’ll see that the software vendors were asked to give their responses as percentages, where the responses in a section were required to add to 100%.
The next time I write about The MOMi Guide, I will have another example to give. My goal is to get readers who have an interest in The Guide to understand the methodology behind its compilation somewhat better. In addition, to give them an understanding of the types of information it will provide.