Contact
Chat or call
We are available Sunday 8 a.m. - Friday 8:30 p.m. Central time. Average wait times are under a minute.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock
(
)
or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
On this page: Cloud buying considerations | Order through MAS | Acquisition resources | Related policy and documents
This guidance walks agencies through the essential phases of cloud procurement — from early planning and market research to long-term operations — ensuring compliance with standards and review of the general cloud acquisition process. It details the essential phases of the solicitation cycle and provides tips for ensuring long-term success.
Before using the Cloud SIN, agencies should should define their mission need, business outcome, technical requirements, security requirements, data requirements, and expected operating model. Early planning can help agencies select the appropriate service model, identify whether professional services are needed, and develop clearer requirements for vendors.
Consider:
| Topic | Tips |
|---|---|
| Application rationalization | Retire redundant systems first. Avoid “copy-pasting” inefficient legacy applications into expensive cloud environments. |
| Avoid vendor lock-in | Evaluate solutions based on data portability and the use of open standards to ensure the mission can transition between providers or hybrid environments without prohibitive egress costs. This may be difficult to realize since many CSP tools are required to be baked into agency cloud applications in order to run properly, or at all. |
| Cloud-native expertise | Prioritize labor categories specific to cloud architecture (Cloud DevSecOps, Cloud Engineers, etc.) over general IT support to ensure the labor skill set matches the cloud environment. |
Cloud security and compliance | Cloud security requirements should be considered early in the acquisition process. Agencies should identify applicable federal and agency-specific security, privacy, data, and compliance requirements before issuing a solicitation or placing an order. When FedRAMP applies, agencies should verify the cloud service offering’s FedRAMP status and ensure the solicitation and order clearly describe applicable security requirements. Agencies are responsible for determining their own authorization, risk management, and compliance needs. Before award, verify that the service is not just “FedRAMP Ready” but maintains an Active FedRAMP Authorization at the required impact level (Low, Moderate, or High) for the specific data being hosted. The FedRAMP Marketplace is the final authority on whether a cloud offering is FedRAMP authorized. “NIST compliance” describes the architecture, but “FedRAMP” confirms the legally required security authorization to operate. |
| Comprehensive exit strategy | A resilient acquisition includes a predefined “exit plan” to mitigate concentration risk—the danger of relying too heavily on a single vendor and/or Cloud Service Provider. This strategy should detail criteria for execution, identified alternative solutions, and data recovery/exit procedures methodology in the RFQ. This prevents egress fee surprises and ensures your data is returned in a non-proprietary format, making the “exit plan” financially, operationally, and technically actionable. Require a “Data Exit Price” (e.g., order closeout data migration costs) and predefined data file formats and protocols. |
| Cybersecurity Supply Chain Risk Management | Agencies must evaluate the entire cloud supply chain, including the provenance of sub-components and the Foreign Ownership, Control, or Influence of subcontractors. Ensure your C-SCRM plan addresses risks from hardware origins to software dependencies (e.g., third-party, open source). Require Cryptographic, Hardware, and/or Software Bill of Materials (CBOM, HBOM, SBOM) deliverables in your RFQ and post award. The Bill of Materials provide visibility into the components (e.g., cryptographic, hardware, software) of your cloud environment supporting asset management, configuration management, and cybersecurity activities. |
| Embedded governance and governance support | Integrate Zero Trust and FedRAMP compliance at the design phase to protect High-Value Assets. Determine if the vendor will provide managed services for cost optimization/control and security monitoring, or if the agency will retain those tasks internally. |
| Enforceable service level agreements | To ensure cloud accountability, agencies should review and replace generic uptime metrics with enforceable, mission-aligned SLAs, that include automated penalties and refunds for performance failures. Shift from “uptime” to “mission availability” SLAs. Tie service penalties and refunds to specific mission impacts—like API responsiveness or security patch timelines—rather than just server pings. This ensures the vendor is financially accountable for the functional performance of the infrastructure, platform, and software being provided “as-a-Service”. |
| FinOps transition | Shift from CapEx to OpEx models using data-driven analysis to prevent budget overruns and ensure long-term value. |
| Mandatory direct access | Ensure the OA RFQ prohibits “middleware” restrictions. The agency should maintain access to native CSP consoles, including usage reports, audit logs, and security tools, regardless of whether a reseller is involved. |
| Mission-first architecture | Align every technical requirement with specific agency priorities rather than treating the cloud as a mere storage utility. |
| Multi-cloud readiness | Prioritize solutions that use open standards and allow for seamless integration with other cloud platforms. This preserves the agency’s ability to adopt a hybrid or multi-cloud approach as mission needs evolve. Consider mandating Open API compliance and containerization (e.g., Kubernetes) in your RFQ to ensure workloads can migrate between providers without expensive code rewrites. |
| Multi-cloud & hybrid strategy | Agencies can utilize a BPA approach to consolidate access to multiple cloud service provider catalogs through a single reseller, resulting in a single contracting action rather than several. Use a “Brand Name or Equivalent” approach for your primary environment while mandating access to secondary CSPs; this secures current mission stability while providing a pre-competed pathway for future hybrid-cloud scalability. |
| OLM flexibility | Include the OLM SIN in your cloud RFQ to capture incidental, unforeseen items — like specialized training or utility tools — not pre-priced on the vendor’s Schedule. This streamlines procurement by keeping supporting items under the same FAR-compliant terms as your primary cloud services, avoiding the need for separate open-market actions. Use the OLM SIN to handle variable egress fees or unexpected data migration tools; just ensure the OLM portion stays incidental and is evaluated for price reasonableness via at least three competitive quotes at the order level. Expenses must be unknown at the time of award and be capped at 33% of the total award. |
| Period of Performance | Cloud buying requires the balancing of tradeoffs between Periods of Performance length (e.g., 1 year, multi-year)/type of appropriations (e.g., 1 year, no year) and consumption-based ordering (e.g., pay-as-you-go)/term-based ordering (e.g., reserved instances, annual subscriptions). Use Prospective Price Redetermination for IaaS/PaaS to adjust budgets every 12 months based on actual consumption, preventing “use-it-or-lose-it” waste while maintaining fixed-price contract discipline. |
| Policy alignment | Cloud acquisitions must strictly adhere to FITARA for investment oversight and FISMA for risk management, ensuring that every dollar spent is architecturally sound and security-compliant from day one. |
| Real-time cost transparency | Require vendors to provide granular billing data (tagging/metadata) that supports automated “showback” or “chargeback” to internal agency departments. |
| Shared responsibility model | Clearly define which security controls are managed by the CSP and which must be covered by agency labor or Order-Level Materials to avoid security gaps. |
| Total solution Multi-SIN approach | When mission requirements exceed the NIST cloud definition, agencies should utilize a multi-SIN approach. While SIN 518210C remains the primary vehicle, the RFQ can encourage vendors to include complementary SINs — such as 54151S (IT Professional Services) or 54151HEAL (Health IT) — to deliver a seamless, comprehensive solution. In eBuy, always list SIN 518210C as the primary SIN to ensure your requirement hits the specialized cloud vendor pool, while explicitly stating in the SOW that cross-SIN solutions are permitted for non-cloud incidental tasks. |
| Transactional data transparency | Transactional Data Reporting provides agencies with granular data on actual government prices paid (i.e., costs), moving market research beyond commercial list-price comparisons to real-world benchmarks. Review TDR prices paid (i.e., cost) during market research and compare quoted prices to TDR prices paid to secure competitive prices in respect to historical prices paid and the specific requirements (e.g., volume). |
| Upfront payment structures | Upfront payment structures may provide additional discounts but may not align with your actual consumption patterns and cycles leading to the oversubscribing of cloud services resulting in higher overall costs. Review and understand the applicable appropriation legislation, regulations, and policies and historical consumption patters and cycles prior to releasing an RFQ. Align your order with your actual consumption and avoid paying for unutilized cloud services (e.g., IaaS, PaaS, SaaS). |
| Workforce readiness | Identify cloud-native Specialized Labor gaps early to support cloud automation and governance patterns. |
Proactive planning ensures workloads are deployed where cost, performance, and compliance intersect. Engage your CIO and IT Portfolio Management leads early to ensure the solution fits the agency’s enterprise roadmap; early collaboration is critical to prevent bottlenecks during the Risk Management Framework and Authority to Operate approval processes.
Common cloud acquisition risks include treating cloud as a one-time purchase rather than an ongoing service and not planning for post-award monitoring, optimization, and governance. By prioritizing these areas, agencies reduce the risk of “cloud sprawl” and maximize the returns on investment.
To maximize return on investments for cloud buying, agencies should transition from traditional procurement to a dynamic cloud-as-a-utility model. Consider how elasticity and rapid provisioning can reduce operational bottlenecks and allow for automated, “pay-as-you-go” up/down scaling cost savings. Mitigate risk by requiring vendors to define protocols for automated scaling, cost-attribution tagging, and unrestricted administrative access. These requirements ensure fiscal transparency and maintain direct government oversight of cloud performance and security.
The right cloud service model depends on the agency’s business need, technical environment, security requirements, and desired level of control.
Many cloud requirements include more than one service model. Agencies should define the business outcome first, then identify the cloud services and professional support needed to achieve that outcome.
When mission requirements exceed the NIST cloud definition, agencies can utilize a multi-SIN approach. The RFQ should list SIN 518210C as the primary vehicle, but may include complementary SINs to deliver a seamless and comprehensive solution.
Before placing an order, agencies should conduct market research to understand available Cloud SIN vendors, cloud service models, commercial pricing approaches, security considerations, and implementation options. Market research may include:
Agencies must define scope around utility-based consumption and precise service-level agreements.
Assess quotes using your stated evaluation criteria, such as:
Document your best‑value determination and fair‑and‑reasonable price decision in the order file, consistent with FAR 8.4 and your agency’s procedures.
We are available Sunday 8 a.m. - Friday 8:30 p.m. Central time. Average wait times are under a minute.
Error, The Per Diem API is not responding. Please try again later.
No results could be found for the location you've entered.
Rates for Alaska, Hawaii, and U.S. territories and possessions are set by the Department of Defense.
Rates for foreign countries are set by the Department of State.
Rates are available between 10/1/2024 and 09/30/2027.
The End Date of your trip can not occur before the Start Date.
Traveler reimbursement is based on the location of the work activities and not the accommodations, unless lodging is not available at the work activity, then the agency may authorize the rate where lodging is obtained.
Unless otherwise specified, the per diem locality is defined as "all locations within, or entirely surrounded by, the corporate limits of the key city, including independent entities located within those boundaries."
Per diem localities with county definitions shall include"all locations within, or entirely surrounded by, the corporate limits of the key city as well as the boundaries of the listed counties, including independent entities located within the boundaries of the key city and the listed counties (unless otherwise listed separately)."
When a military installation or Government - related facility(whether or not specifically named) is located partially within more than one city or county boundary, the applicable per diem rate for the entire installation or facility is the higher of the rates which apply to the cities and / or counties, even though part(s) of such activities may be located outside the defined per diem locality.