The final MTTR process step impact is Remediation. Once we know the problem, we must connect to the asset and perform the Remediation. While that may seem trivial, it often is not. With ConsoleWorks we are either already connected to the asset or simply click on the device’s name and are automatically connected to the asset, ready to perform our remediation. That leads us to an MTTR of Detect = 0, Isolate = 0, Analyze = 0 to (norm – x), and Remediate = (norm – y)?
Additionally, ConsoleWorks can capture remediation activity and assign it to an event as a best practice. Now when a problem occurs there is a distinct possibility that the remediation activity is already there, associated with the event. Because the best practice can include keystroke-by-keystroke instructions for remediation, the actual remediation step is reduced to a simple paste-execute.
For cases where best practices are in place, the MTTR process moves to an effective result of Detect = 0, Isolate = 0, Analyze = 0 to (norm –x) and Remediate = paste-execute to (norm –y).
Basically, for events that an IEM can pick up (and yes – you can change, add, delete, and build your own embedded content in an IEM) the process is intensely streamlined and simplified.
ConsoleWorks Detects the event, notifies you of it, tells you its severity, describes what the event means, has the data you need at your fingertips to troubleshoot the problem and pops you into the asset you need to remediate with one click, and may even give you the perfect set of instructions to remediate the issue almost instantly.
In short, ConsoleWorks will slash MTTR down to a fraction of what we usually experience.
Read the first three parts – ConsoleWorks Reduces Mean Time To Repair (MTTR): Part 1 – DETECT, Part 2 – ISOLATE, Part 3 – ANALYZE