Federal civilian agency redesigns RISE to comply with sovereign cloud requirements.

A sovereign cloud reset of the RISE conversation.

The agency operated a long established SAP estate supporting financial management, acquisition workflow, grants administration, and human capital management. The on premise environment had been running for more than a decade, with consistent SAP support contracts and a small set of internal SAP support staff. The SAP federal team had been positioning a RISE migration since 2024, with the proposal in question arriving in late 2025.

The proposal contemplated a standard RISE Cloud Private Edition deployment on a hyperscaler infrastructure provider, with multi tenant architecture, US region data residency, and standard SAP managed operations. The agency CIO had communicated, in the prior six months, a sovereign cloud commitment for systems handling the relevant data classification. The sovereign cloud commitment required dedicated single tenant infrastructure, in country operations by US persons holding appropriate clearances, FedRAMP High aligned controls, and contractual transparency on subcontractor chain.

The engagement was scoped at twenty two weeks to accommodate the federal procurement timeline, the FedRAMP control review, and the inter agency consultation that the agency contracting officer required before final award. The work split into five streams. Commercial modelling. Contract review against federal acquisition regulations. FedRAMP High control mapping. Sovereign cloud architecture assessment. Subcontractor disclosure verification.

Four phase negotiation sequence.

What the architecture review surfaced.

The proposed RISE configuration relied on multi tenant infrastructure with shared compute and storage isolation provided by virtualisation layers. The sovereign cloud commitment required dedicated single tenant infrastructure with physical separation from non sovereign workloads. The proposed configuration could not meet the commitment without architecture redesign.

The proposed operations model contemplated SAP managed operations from offshore service centres, with US based escalation paths but no commitment to US person operations for routine activity. The sovereign cloud commitment required in country operations by US persons holding appropriate clearances for the data classification. The proposed operations model could not meet the commitment without operational redesign.

The proposed subcontractor disclosure committed to disclosure of named subcontractors at the time of contract signature, with no operational personnel disclosure and no ongoing notification obligation. The sovereign cloud commitment required transparency on the operational personnel, including clearance status, location, and citizenship. The proposed disclosure could not support the commitment.

The commercial proposal was built against the multi tenant architecture. Moving to a sovereign single tenant architecture changes the underlying cost structure. The negotiation needed to reset the commercial baseline at the same time as the architecture redesign, because the original discount stack assumed multi tenant economics that did not apply to the sovereign configuration.

The sovereign cloud commitment was not a contract clause that could be added at the end. It was an architecture requirement that changed the shape of the deal. The negotiation had to reset the commercial baseline and the architecture together.

What changed at award.

The redesigned RISE configuration deploys on a sovereign single tenant infrastructure operated from in country facilities by US persons holding the required clearances. The infrastructure provider is a named sovereign cloud operator with FedRAMP High authorisation and a documented separation from the operator commercial cloud business. The architecture supports the agency authorisation to operate process with traceable control mapping.

The contract includes named subcontractor disclosure covering the operational personnel for routine activity, the named escalation contacts for incident response, and the clearance verification process. Subcontractor changes require prior notice with a defined approval mechanism that supports the agency security review process. The disclosure obligation extends across the full contract term.

The commercial reduction from $58M to $19.1M reflects the rescoping of the deal against actual agency user populations rather than original SAP estimates, the unbundling of services that the agency could source through existing federal acquisition contracts at lower rates, the removal of premium services that the agency did not require, and the standard discount stack rebuild applied to the redesigned architecture. The sovereign single tenant infrastructure carries higher unit cost than multi tenant, but the redesigned scope and the negotiated discount more than offset the unit cost increase.

Exit credits worth $4.2M are tied to defined regulatory or policy exit triggers, including direction from the agency oversight body, formal change in federal cloud policy, and failure of the sovereign operator to maintain required authorisations. The exit credit is paid in cash on a defined schedule rather than applied against future SAP commitments, consistent with federal acquisition regulation preferences for cash recovery rather than future obligation.