When a company’s revenue vaults into the hundreds of millions of dollars, even a day of downtime can result in a staggering loss. When extended downtime occurs due to a solvable IT problem, stress levels run high. Jobs may even be at risk.
For companies that earn significant revenue, expectations are that every process throughout the organization runs as smoothly as possible. For Mesilla Valley Transportation (MVT), a dry-freight trucking company that serves the continental U.S., Mexico, and Canada, downtime simply isn’t an option. When they experience downtime, they stand to lose three very important facets of their business: revenue, customer goodwill—they pride themselves on a customer-first mentality—and truck drivers.
The Challenge: Upgrading Business-Critical Software
When MVT’s Director of Information Technology Mike Kelley contacted us about a pending upgrade to one of their most critical systems, we knew the Kubisys Platform was up to the challenge.
Kelley challenged us, “If you can help us capture this environment and let us test it, then we can run our upgrade and learn from it. Then when we perform this upgrade in production, we should experience exactly what we went through in Kubisys, if your system does work …”
Kubisys: Too Good to Be True?
Due to the current state of development testing, his doubts were well founded. When Kelley first learned about the Kubisys Platform at the MidMarket CIO Forum conference and told his development team about our Platform, they called it “too good to be true.” After all, a test environment that was capable of accurately replicating production within a matter of hours seemed like an illusory dream. If it worked, they all believed it would be fantastic.
Pegasus Transflo, the content management system that needed to be upgraded, involved four interconnected applications and was responsible for tracking driver and customer documentation, billing clients and driver payroll. In other words, this software was heavily integrated into their core TMS (Transportation Management System) and thus fundamental to their business. A failed upgrade would mean unbilled customers, angry drivers and angry managers—any IT Manager’s perfect storm.
The Kubisys Platform helped Kelley successfully overcome the situation before it ever had the chance to come to fruition.
How Kubisys Prevented “a Major Impact on Our Organization”
When testing the upgrade of this business-critical software in Kubisys:
“We made a critical decision and didn’t realize it at that point but continued moving forward. We realized later that had we continued it would have caused major problems with the system overall, which would have forced us to recover the system from backups. The recovery would have been done during business hours. It would have been very painful, but we realized this mistake while working with the Kubisys environment. We scrapped everything, started again, changed that critical choice, and had a successful upgrade. We then re-tested the upgrade to be certain and ran the drill one more time. Everything went flawlessly each time. That one successful upgrade, because it saved us the downtime, that was proof to not only my team, but also to the CFO, that Kubisys was a worthwhile investment.”
Since one Kubisys test environment replaced their need for three traditional test environments that could each run eight virtual machines at a cost of $2,500 per VM, MVT saved $60,000 in hardware costs.
Since MVT typically needs at least three test environments to test approximately 36 refreshes per year, with an average of 20 days needed per test, MVT shortened their overall development timeframe from 585 days to just 39 days, resulting in a substantial productivity savings of $786,240.