You know how everything experiences loss in the universe? (The 2nd Law of Thermodynamics!!!) When you use energy, something is lost. Well, in legacy rules-driven event display systems, you see the same thing.

In rules-based systems such as Netcool, SMARTS, Monolith, etc., loss is experienced in translation (data normalization). And then again when data is enriched.  And because it was translated again in Impact. And because it gets delayed more and more, it loses time relevance. Or you have agents that only forward a filtered message.

Then when you experience load, the common practice is to glean out or discard things that are seemingly irrelevant. (Another loss.)

As humans, our perception is naturally filtered already. This is not always a good thing. We skip over relevant things and recognize things that lack relevance. Driving while texting comes to mind! (Or selective hearing!)

In science, entropy is the opposite of information. Like Noise to signal in radio communication. And the natural order of things is to go from order to chaos.

Incident.MOOG takes a transformative approach to entropy. With Incident.MOOG, we can measure entropy so that we can see INFORMATION.  We can recognize it, sort it, group it, and present it in context. And it does it in a forward-chained manner.  As things develop. You don’t have to wait until you’ve experienced a few samples to figure out a rule. There is no delay and there’s no dependence on rules!

So, do you want to keep losing with legacy rules-driven event display platforms

OR

gain awareness of the SITUATIONS you have and put the INFORMATION to work?

Richard Whitehead will be talking about Situations during this week’s Moogsoft webinar.

PS – The guys doing the rules ought to be working on the instrumentation first. (Coming from Mr. Rules himself!!) Ironic. When you get Incident.MOOG installed and running, it really illuminates bad instrumentation.