Customer does not want to see that "All machines for your PI System" 219876543 down, if system 219876543 only consists of one PI Server. Customer would like if we could refine our System alerts if PI Agent is only down for a single machine.

Customer would like health tags to monitor PI Agent and PI Diagnostics Services in order to monitor and record their activity.

I'd like to customize the email alerts for my PI system so that alerts that appear do not show the site - as I don't want to mislead alert contacts as to where the issue exists.

I'd like help with being notified when my data is stale and help determining why it's stale.

Add capability to mPI to detect that services are no longer responsive or in a bad state - e.g. when an AF collective is out of sync and the service becomes not responsive, this is not detected by mPI and not flagged by the NOC

I'd like to be able to define a "line" related services that are monitored in the NOC, and then permit that line to be put into maintenance using a physical button or switch (something that is proximate to the line, and does not require computer interaction).

I'd like to be able to show my management an estimate of how much value the NOC delivers in dollars or FTE saved, so I can justify NOC coverage when renewing NOC services.

When you open the Services program (services.msc), the PI Diagnostics Service and the PI Diagnostics UI Service both do not have a description. Please provide one.

I'd like the infrastructure that supports NOC services to be FIPS compliant.