Following the General Services Administration’s announcement last August of a OneGov agreement with Amazon Web Services, CMS Chief Information Officer Patrick Newbold is sharing details about the agency’s early experience using the program.
GSA said the agreement could provide federal civilian agencies with up to $1 billion in savings through December 31, 2028. The agreement includes credits for AWS cloud services, infrastructure and application modernization, and training and certification. It is intended to help agencies move aging systems to the cloud, reduce costs, and accelerate the adoption of artificial intelligence and other advanced technologies.
In a recent LinkedIn post, Newbold said CMS became the first agency to use the agreement. His post focused on a question he said he frequently hears from federal technology leaders: “The OneGov cloud deal looks great in year one, but what happens in year two?”
“It is a fair question. I had it too,” Newbold wrote.
According to Newbold, CMS needed to move a mission-critical contact center from a legacy data center to the cloud. After reviewing the OneGov agreement and conducting its due diligence, the agency decided to proceed.
“We needed to move a mission-critical contact center out of a legacy data center and into the cloud,” Newbold wrote. “GSA had negotiated the OneGov agreement. We did our due diligence, saw an opportunity to modernize while delivering better value, and moved forward.”
Newbold said CMS achieved 46% savings on that workload.
He also emphasized that the agency’s efforts did not end with the initial OneGov agreement. According to Newbold, agencies can negotiate additional cloud discounts through their resellers. CMS used that approach to pursue savings beyond the first year and create greater predictability in its long-term cloud spending.
Newbold advised agencies to engage GSA early, clearly communicate what they need to sustain their cloud operations, and treat the process as a partnership. He also said GSA is working toward longer-term agreements and that agencies may have more negotiating leverage than they realize.
CMS now has 16 OneGov cloud agreements supporting 11 mission areas, according to Newbold. Those areas include beneficiary customer relationship management, claims modernization, and payment integrity.
“Each represents more than a technology migration,” Newbold wrote. “It is another mission workload moving from costly, constrained legacy infrastructure to secure, scalable, modern cloud operations.”
Newbold encouraged other agencies considering OneGov to draw on CMS’s experience rather than begin the process without an existing model. He said CMS has already taken the step and that he is willing to share what the agency has learned.
His post provides an account of how CMS used the OneGov agreement for a specific mission workload, achieved reported savings, and pursued additional reseller discounts intended to support longer-term cost predictability.
