The SSA's ITSSC Recompete - A Prime Example of Unintended Federal Acquisition Malpractice

Federal IT procurements are often treated as technical paperwork. In reality, they are long-term strategic decisions. They shape how systems are built, who can compete, how risk is shared, and how innovation shows up in real services.


The Social Security Administration ITSSC recompete is one such decision. This is a ten-year, multi-billion-dollar opportunity. It will shape how SSA designs and operates its technology well into the 2030s.

At this scale, procurement is architecture.

The documents released as RFI do more than ask vendors what they can do. They define who can realistically compete, what solutions are viable, and whether innovation is built into the foundation or added later. That is why the early artifacts matter.

What they reveal is not just poor wording. They point to deeper problems that risk locking old assumptions into the next decade of SSA modernization.

The Request for Information addresses modernization, data, and artificial intelligence, but it does not provide a clear design.

There is no clear enterprise data architecture. The document lists platforms and tools but does not explain how data should flow, where analytics should reside, or how modern AI systems should integrate with legacy systems.

There is no shared modernization target state. Instead of describing where SSA wants to be, the RFI blends past contracts and current operations with future goals. Modernization is defined by outcomes but scoped around legacy infrastructure.

As a result, procurement ends up defining the architecture by committee. Advanced AI use cases appear next to requirements that all new development rely on traditional relational databases. Modern analytics are tied directly to mainframe-style administration.

The outcome is a predictable muddle. Risk is pushed onto vendors. Innovation is treated as an add-on rather than a foundation. AI and analytics are layered on top of existing systems rather than shaping their design.

This raises a fundamental question that the acquisition does not answer.

Do we really want future AI systems that support disability decisions to be built on the same relational database assumptions that defined earlier generations of SSA systems? With the same for other SSA systems?

Isn't treating AI as just another database workload risk carrying old limits into new mission-critical decisions?

These issues are not unique to SSA. They reflect a broader pattern in federal acquisition. Agencies often speak about modernization while relying on dated procurement language shaped by legacy systems. Senior leadership is more focused on short-term wins, meeting KPI's, and optionality to change.

Modernization does not fail because of a lack of technology. It fails when old assumptions are allowed to define the future. This is why the taxpayer continues to pay billions annually, with little to show for it.



Comments

Popular posts from this blog

Breaking the Bottlenecks: Information, Access, and the Fight for Time ACRD 2026 Annual Conference Keynote: Kissimmee, Florida

The McDonaldization of the Social Security Administration

Obfuscation Is Not Security