Friday, August 20, 2010

EMI or BI - what are those anyways?

Lately I have had inquiries from a couple of customers about providing “intelligence”, as in manufacturing intelligence, well I believe that is a good topic I said… (Hint, see my blog’s title).

In most cases their curiosity came from either seeing or working with an EMI or Enterprise Manufacturing Intelligence system. However when I asked about how they would like to use the intelligence I found out that they where asking about BI – Business Intelligence behavior, yet they wanted manufacturing metrics like the EMI system’s demo. That is an interesting discussion that I have mentioned a few times in this blog. I believe that what they really want are timely and sometimes real-time intelligence about their manufacturing operations provided in KPI lists, metrics and charts but also analytics capabilities such as “slicing and dicing” and “drill downs”.

Unfortunately I have found that such solutions are rare if they exist at all. It seems that EMI is a separate animal than BI and the problems that they are trying to address are more complicated than they generally convey in their sales and marketing information. Most EMIs do not provide an effective way to aggregate and correlate information to support BI style analytics, while the BI vendors’ understanding of 'real-time' and timeliness leave much to be desired for application in the manufacturing operations world.


Rich Santoriello said...

We are using an application called Qlikview and are currently building our own BI datasets/data cubes to help with the What If's. These efforts take longer than expected but once completed are a great asset to the organization.

glanger said...

I am somewhat familiar with Qlikview... Its great that you are venturing into this. I would love to hear all about it next time we meet.

jaganwgl said...

Ahaa, its nice conversation about this piece of writing at this place at this blog, I have read all that, so at this time me also commenting at this place.relational databases are good for data entry and update, but they obscure information stored in the database from the user. QlikView's associative database is specially designed to allow users to get maximum benefit from all of the information stored in their databases Thanks. qlikview training

sai venkat said...

Nice blog has been shared by you. it will be really helpful to many peoples who are all working under the technology.thank you for sharing this blog.

R Programming Online Training|

Tableau Online Training|

SAS Online Training |