Just FYI, being in information systems myself.
Please don't take this post as any attempt to be rude, it's not.
But the thought that the SSA core infrastructure of 1960's era COBOL mainframes can be replaced in 2-3 years isn't realistic. It would take probably a couple of billion dollars over the course of a decade to replace. Verizon has the contract up upgrade and modernize the FAA system and this multiple billions of dollars over the course of 15 years. (Actually I think the couple of Billion is just the starting phase.)
- First you have to define what the critical infrastructure is supposed to look like in terms of size, scope, locations, and network from a Technology standpoint. Then you have to define the size, scope, record volumn, and functionality from a software standpoint. That would take the SSA a year or two.
- Then you have to put it out for RFP (Request for Proposal) to vendors and the big players in that field are Oracle, SAS, and Microsoft. And this can take multiple rounds as vendors will have questions that need answer before they can cost it out. This could take another year or two.
- You have to get Congress onboard to - you know - actually fund the project in the budget. Who knows how long that would take.
- Once the vendor is selected and and actual design work can start, now you have to build a database system from the ground up that meets the operational requirements in terms of functionality and scope but that also provides for historical tracking, record maintenance, determination of benefits, and payment of those benefits in such a manner as to comply with existing laws and regulations. That alone would take a couple of years.
- Because this is critical infrastructure you are going to have to go through various testing phases:
- Functional Testing of subsystems to check performance and compliance.
- Beta Testing of the entire system for all planned scenarios
- Alpha Testing under real world conditions to see if performs properly and is in compliance now that real situations are being tested.
- Parallels Testing - As critical infrastructure you would never, NEVER just turn off the old system and turn on the new system. You would run the old system for actual production and then run the same processing through the new system in a "Safe" environment to identify issues for correction. Here alone it would probably be recommended that parallels run for at least one entire tax year.
- Oh and don't forget you don't get to start with a clean, empty system. You have to be able to convert and correct existing data in the COBOL system to this new infrastructure.
- Finally, you then get to "Go Live" with the new system.
This is critical infrastructure and CANNOT FAIL, so it has to be designed with care, constructed comply with laws and regulation, and be tested properly.
This is NOT Rocket Science. In rocket science is an interrative process, you design, you build, you launch, and you gather data about what went wrong. You repeat the process over and over again - build, test to failure, build test to failure. That can't happen with such things as replacement FAA and SSA systems.
This isn't ordering a DELL desktop.
Just my thoughts.
WW