Ascend Updates

Agencies across government continue to struggle with buying and adopting cloud technologies. GSA repeatedly hears customers say that they want and need an acquisition vehicle that addresses cloud-specific technologies and requirements, offers a less complicated way to buy them, and provides standardized security and data management features.

The Ascend Blanket Purchase Agreement (BPA), to complement GSA’s Multiple Award Schedule Cloud SIN 518210C, will meet the government’s demand for more comprehensive, secure and compliant cloud-based solutions. It allows GSA to develop a solution for federal, state, local, tribal and territorial governments that will make buying cloud less complicated.

With Ascend, GSA delivers what agencies are looking for:

  • Security requirements: Cybersecurity and interoperability requirements, regulations and standards are extremely challenging to navigate. Ascend will include recently updated standards on supply chain risk management (SCRM) and cyber SCRM (C-SCRM). It will provide access only to FedRAMP– or Department of Defense Cloud Authorization Services (DCAS)– authorized cloud solutions. Ascend will make it easier for agencies to comply with cybersecurity mandates.
  • Data ownership and portability: Ascend establishes the requirement that agencies own their accounts and data, and cloud service providers (CSPs) have to make the data portable in case the agency wants to move it.
  • Standardized reporting: Customers require visibility into financial information for contract administration, cost control, chargeback and budget management/forecasting (i.e., FinOps). Ascend offers standardized reporting of this information.
  • Subject matter expertise: Leaders need to ensure that contracted technical personnel have knowledge, skills, abilities, taskings and mindsets for cloud services, not just general IT skills. Ascend is built on the Cloud SIN 518210C, which accounts for specific cloud technologies and cloud-related IT professional services.
  • Compliance: Federal agencies must comply with constantly updating executive orders, OMB memos, acquisition laws and policy targets. Ascend has these complex requirements built in upfront to reduce agencies’ risks and ensure compliance.
  • Ease of ordering: Customers across government need access to a catalog of cloud services under a single acquisition solution to promote flexibility, agility and continuous injection of emerging technologies. Catalogs are standardized at the BPA level to make it easier for customers to compare services and associated prices.

Industry input, implemented

We’re closer to releasing a final solicitation of Ascend Pool 1, which covers the basic BPA requirements and Infrastructure as a Service/Platform as a Service requirements through three subpools. We recognize how important your invaluable feedback is through your responses to our requests for information, draft performance work statement and the draft solicitation. We heard you! We carefully balanced your feedback against agencies’ needs to be able to buy and manage cloud effectively.

As a result of your feedback, we’ve changed some of the BPA requirements:

Order catalogs: At first, we required contractors to provide catalogs at the ordering level.

  • Now the requirement is to deliver and maintain catalogs at the BPA level following a specific format to standardize Ascend BPA catalogs.

Cybersecurity logs: At first, the contractor had to provide cybersecurity logs.

  • Now the requirement is to enable the feature for eligible users upon request.

Authorized cloud services: The BPA includes only what is in the BPA catalog. At first, we required the contractor to restrict cloud services usage.

  • Now contractors must provide the capability for eligible users to restrict the usage of cloud services through configuration files and policies, which in turn, gives eligible users more control over what cloud services are being used.

Cybersecurity incident reporting and incident response timelines: Aside from following timelines established by current law, we required incidents to be reported to the administrative agency.

  • Now the requirement is less complex and no longer requires reporting to the administrative agency. Reports are further defined at the task order level for reporting to eligible users.

Carbon Pollution-Free Electricity (CFE): At first, GSA specified required sources of CFE.

  • Now the requirement is to offer cloud services that comply with current environment and sustainability legislation, regulation and policies at any given time.

FinOps: At first, contractors were required to monitor and automatically suspend cloud services when consumption reached certain thresholds.

  • Now the requirements are to enable metering options and allow for eligible users to set metering thresholds and automate suspending specific cloud services once metering thresholds are at a certain level. The contractor must also notify the eligible users.

Next steps

We are still working through minor adjustments. We plan to send out another draft solicitation and hold another industry day before issuing the final solicitation. Again, we appreciate the feedback we have received throughout the market research process.

Resources

For questions about the Ascend BPA, please reach out via email to cloudenterprisewide@gsa.gov.

Our cloud subject matter experts are here to provide guidance, and support agencies and vendors navigating our contract vehicles. Reach them at cloudinfo@gsa.gov.

Follow our Cloud and Software community on GSA Interact to learn the latest Ascend updates, or use our IT Solutions Navigator to find the vehicle that’s right for you.

Follow us on LinkedIn to join our ongoing conversations about government IT.

To get updates for this blog, please sign up on the right-hand side of the page where it says Sign up for Blog Updates.

Moving Up(front) with Upfront SaaS Payments

As agencies continue transitioning to cloud solutions that make government services more efficient and accessible, simplifying how they pay for these solutions may seem like a minor detail, but it is critical and it’s a big deal. 

Due to the expertise, influence, and progressive-thinking of GSA’s Information Technology Category (ITC), we’ve worked to find a new approach to give agencies better solutions while ensuring cost-effectiveness and compliance with regulations.

Effective May 2024, GSA changed its rules about upfront payment for software licenses delivered as Software as a Service (SaaS). 

The change affects Multiple Award Schedule (MAS) Special Item Numbers (SINs), most significantly SIN 518210C Cloud Computing and Cloud Related IT Professional Services.

The change is another step toward delivering lower costs by aligning federal IT purchasing with commercial practices.

Background

We know that the software service delivery model has changed rapidly in recent years and to better serve our customer agencies and industry partners, we’re adapting, too.

Last year, we asked for industry feedback on the SaaS payment model and ways to align with industry best practices and the commercial marketplace. 

Based on their feedback and our research, we published a significant update in the recent MAS refresh, which should allow for increased competition and lower-risk entrance of small businesses into the SaaS marketplace. 

Good for agencies, good for cloud service providers

Traditionally, software was provided via a CD-ROM that needed installation and updates. However, with rapidly changing technology, most of it is now offered via the SaaS model. These services were billed in arrears on a month-to-month basis for a long time. 

With our recent update, we are providing the option to allow for payment up front, that is, paid at time of delivery for software delivered as SaaS that meet specific criteria, while keeping the option for month-to-month billing.

This change provides agencies with more flexibility and control to align task orders to SaaS license needs. Using the upfront payment model allows agencies to negotiate with vendors and resellers to realize more potential savings. 

Next steps for vendors  

To offer the upfront payment option, vendors must submit a modification adding it to their schedule contract. We encourage vendors to offer SaaS through the Cloud SIN 518210C so customers can easily discover it. And along with that, adding the upfront payment pricing and month-to-month pricing options to give agencies more flexibility. 

Aligned with commercial best practices, upfront payments can significantly reduce not only the cost of SaaS licenses, but also the administrative burden through one task order and one invoice to process. 

Best practices and resources

GSA has developed several resources to assist agencies in navigating cloud payments and IT procurement:

  • Acquisition Resource Guides: These guides provide detailed advice on managing costs, ensuring data protection, and selecting the right vendors.
  • Data Dashboards: Tools like the searchable data dashboard help track AI-related contract actions and spending, providing valuable insights for decision-making.
  • Cloud SME Support: Our cloud subject matter experts are here to support agencies and vendors navigating our systems. They can be reached by email through cloudinfo@gsa.gov.

By following these best practices and utilizing available resources, federal agencies can effectively manage their cloud payments and enhance their IT infrastructure.

Visit our website to learn more about the MAS Refresh, or follow the Cloud and Software community on Interact.

Follow ITC on LinkedIn and subscribe for blog updates.