BMC TrueSight Operations Management Mean Time To Remediation
Has the solution helped to reduce your mean time to remediation? If yes, by how many hours or what percentage? Can be approximate.
It has improved our time to repair. From the time we get the incident logged to the time we get the customer back up and running, it has improved that by 33 percent or greater.View full review »
With a lot of the AIOps features and things like Service Impact Manager, my customers are able to reduce their mean time to repair (MTTR). MTTR is very important for companies who are reliant on their critical IT applications.View full review »
It's helped our meantime to remediation, and I'm being conservative here, by about 70 to 80 percent. That's an absolutely huge impact.View full review »
We have seen with a database out of disk space, because we can get to the root cause quicker, we know what the root cause is. It can be remediated faster, but we can also eliminate the number of people who have to be on outage calls. There is no need to have network people on a call if it's a database issue. We let them deal with other things, so our operation becomes more efficient. The database people know exactly what the problem is, and quickly.
The average length of time used to be 45 minutes before we had the right engineer on the line, fixing the problem. Now, it's probably three to five minutes.View full review »
Mean time to remediation is related to the Probable Cause Analysis and integration with some other components like orchestration or exectuing a remote action. It definitely helps in reducing the mean time to remediate, but it depends on the expertise of the administrator of TrueSight. In my current assignment we have implemented TrueSight for a large customer in the Middle East, and we have quantified how much we have reduced the meantime to remediate. For the top-priority incidents, we have reduced the MTTR from 12 hours to 1.5 hours.View full review »