How Automated Conversion Can Help Fix the US Government's COBOL Problem
Recently, the US Government Accountability Office (GAO) released an eye-opening report which found that roughly 75% of the government’s $80 billion IT budget goes to keep aging technology running, and the increasing cost is shortchanging modernization. The report illustrates how kicking the legacy modernization can down the road costs significantly more every year, and has resulted in a $7.3 billion decline from 2010 to 2017 in development, modernization, and enhancement activities. While many of the findings in the report are astonishing, such as the revelation that the Defense Department’s Strategic Automated Command and Control System, which is used to send and receive emergency action messages to U.S. nuclear forces still uses 8-inch floppy disks for storage, the vast majority of the legacy upkeep falls into the COBOL realm.
Among the available mitigation options, we assert that automated conversion is the fastest, most cost-effective, and safest way to alleviate reliance on legacy infrastructure, databases, and the application code that supports them.
What You'll Discover In These Pages:
- The Trouble With Retaining Legacy Systems - The top three reasons keeping legacy systems on life support is a risky move
- Fixing the Legacy Problem - An overview of common modernization techniques, their pros, and their cons
- There's A Better Way: Automated Conversion - Why Automated COBOL Conversion is the answer
- Automated Conversion: Tools of the Trade - What makes Modern Systems' solution stand out
- Automated Conversion: The Process - What to expect when you're expecting an automated COBOL conversion