Commonly I come across a scenario with customers where they focus on implementing MOM/OpsMgr, yet do not think about process in relation to the tools. A prime example with Operations Manager or MOM is with Management Packs and Release Management - Plan, Build, Test, Review and Deploy (simply speaking). You can't just simply download a Management Pack, import it into your management group, and then expect it to go off and begin monitor your environment (Lets face it, there will be some level of inaccurate alerting that will occur even though the developers have tuned it to minimize "noise"). And why? Because everyone implements technology differently out of the box - customizations, tightening security, etc. Therefore, some level of tuning needs to occur before you "release" it into production.
From a Release Management perspective, you need to:
This may appear to be alot of unnecesary red-tape, but the point I am trying to make is do your due diligence in reviewing the MP and what it does, the requirements and caveats, and test it before you go ahead and implement in production. This is an enterprise monitoring product that should be controlled to ensure accurate notification of true health or reliability issues with services and applcations monitored in your datacenter. More importantly, the business will feel confident in IT meeting SLA's and the report data being reliable and that you are actually able to provide it.