We've been using Busingess Process Monitoring for a while and actually have some business teams relying on the reports (yay! small victories with Solman!!). Unfortunately it's not as robust as we need it to be. With system restarts, the BP monitors often stay off, as if they've been deactivated and then we need to go back and reactivate, usually when a business client notices they haven't received any alerts in a while. Not a good scenario.
Is this something that is unique to our installation? (wouldn't be the first time, we seem to be good at "hmm you'r the only one doing that" responses from SAP).
Case in point - few weeks back something mysteriously took out 1 application server from several of our SAP systems. Solman, ECC, two other systems each lost one app server. We run multiple app servers, so it appeared that the systems were functioning , but Solman lost all technical monitors and the agents would NOT report any system availability stats, and the bpm monitors stopped as well.
We restarted all the systems and TechMonitoring came back online, but the BP Monitors did not restart. And we've had that happen in the past as well. You would think/hope that a system restart would reactivate any running monitors, but apparently this isn't always the case.
Anyone noticed this behaviour? Or am I in a class of 1, again? 
Almost seems like I need a way to automate a global reactivation of all BPM processes once a month or so.
Solman 7.1, sp12, Solaris
Thanks.
Bernie