Is your current system at risk?
It should be accepted that computer related problems will affect your company in one form or another at some time. Being prepared for this would minimise the impact to the business.
A typical IT system with a million lines of code can be assumed to have a failure rate of .05% per bug. Using three methods of remediation, with both high (your own IT staff) and low (outsourced) levels of system knowledge, the impact would be as follows:
For a manual fix with high knowledge, 80% estimated accuracy with 20% date routines the MTBF (mean time between failure) is 0.60 hours and the system is down for a long time. For the same fix using low system knowledge, the MTBF is 0.34 hours and the system is crashed.
Using automated tools with high knowledge, the MTBF gets down to one every 2+ hours. Now it might take two hours to fix that bug and it might take all day, but after it is up and running again, another bug will show up two hours later, and that one will also take time to fix. At this level, the system is working but just barely. At any level below this the system is crashed.
The normal failure rate for large transactional processing is less than 1/10 of 1%. For
distributed processing systems it is 1%. Even if it is assumed 99% remediation and
95% testing, the failure rates will be over 5% which is 5 to 50 times higher than
a modern purpose-