Monitoring to ensure critical objects (schedules, etc) stay active?

Discussion created by daryl.brown_ACI on Oct 16, 2015
Latest reply on Dec 1, 2015 by RichieTurman602610
We had an incident the other day where someone in our Operations team inadvertently canceled one of our client's schedule objects (in AEv9).  We did not realize this until later when the client called to ask why their job hadn't run.  Umm...

Here are the ideas we're toying with so far:
1) Remove the rights to cancel Schedule objects (and possibly other object types) from our Operators.
2) Build a variable listing all of the critical processes that need to be active all the time, and then build a recurring job to loop through the list, throwing an alert whenever it finds something on the list that isn't actively running or sleeping.  (Will need to account for schedules being restarted at turnaround so that we don't throw false alerts at those times.)

Has anyone in the community come up with and/or implemented any other strategies to deal with this danger?
Bonus points if they're particularly clever solutions...