In 2025, the Digital Transformation Agency (DTA) engaged SolsticeIT to conduct an independent strategic review of the Australian Government’s Single Seller Arrangements (SSAs).
The objective of the review was to assess whether SSAs remain fit-for-purpose, continue to deliver value, and support the Australian Government's digital transformation agenda.
The review collected insights from government agencies, SSA sellers, industry bodies, and both domestic and international representatives through interviews, written submissions and surveys.
An outline of the purpose of this report and background on the SSAs.
1.8 The Australian Government has progressively developed coordinated ICT procurement since the early 1990s to streamline procurement processes, reduce duplication, and secure better value for money in technology engagements.
1.9 The introduction of the General Information Technology Conditions in the 1990s established standardised contractual terms for technology procurement across government agencies. These conditions reduced legal complexity and supported more consistent supplier relationships, but procurement processes remained largely decentralised. In addition, until its abolishment in 1997, the Department of Administrative Services established a series of arrangements similar to those currently in place on BuyICT.
1.10 During the early 2000s, agencies commonly negotiated individual contracts with major sellers, often resulting in inconsistent pricing and fragmented contract terms. The Australian Government recognised the inefficiencies of this approach and began pursuing a more coordinated procurement strategy.
1.11 In 2008, the Gershon Review called for the Australian Government to improve coordination of ICT procurement and manage suppliers more strategically. The review recommended the Australian Government adopt whole-of-government approaches to reduce duplication and improve cost-effectiveness. In 2009, the Australian Government implemented this by establishing the first whole-of-government technology contract with Microsoft. This was the first SSA, known as ‘Volume Sourcing Agreement 1’ or VSA1 for short.
1.12 At this time, commercialised cloud storage and computing services emerged, transitioning the traditional on-premises, perpetual license model to the ‘as-a-service’, subscription-based licensing model that is now common across the modern technology landscape.
1.13 The Australian Government updated its engagement model with Microsoft by signing its second SSA in 2013, VSA2, reflecting lessons learned from the first iteration and creating a unified contracting framework for all Commonwealth agencies. The Australian Government then expanded the SSAs to other major sellers (SAP, IBM, AWS, Oracle and Rimini Street), supported by growing institutional capability in digital procurement policy.
1.14 The November 2013 audit of technology procurement by the Australian National Audit Office further highlighted the importance of coordination. The audit identified shortcomings in fragmented contracting practices and supported stronger central oversight and consolidated procurement models.
1.15 The establishment of central agencies to lead digital transformation further shaped the SSA environment:
1.16 The figure below summarises this history.
A figure showing the high level structure of the SSAs. At the top is the Head Agreement with attachments, annexures and modules, covering: Commercials, including pricing and discounts; Products and services terms and conditions; Policy compliance; and Templates and forms. Below the Head Agreement, are the contracts executed under the SSA by eligible buyers / entities.
Off
Use existing standards as your baseline: Comply with legislation and standards to ensure your service uses best practice and meets the expectations for government services. Consider any specific legislation or policies relevant to your service as well as the Disability Discrimination Act (1992), the latest version of the Web Content Accessibility Guidelines (WCAG) and should consider the government’s Style Manual.
Offer content in alternate formats: Offer content in different mediums (such as text, images and audio) and segment long documents or tutorials into chunks. Provide human-validated multilingual support for critical information. Evaluate your service with users who depend on assistive technology, integrate their feedback and resolve pain-points through design.
Consider different platforms: Prior to launch, comprehensively test your service across devices and platforms your users will access it through. Anticipate how content will appear on different devices in your designs and assess whether platform-specific interfaces either support or fail to meet accessibility standards.
Design for affordability and connectivity: Design and develop your service to use as little bandwidth and data as possible. Where it suits the service, make it cache for offline access or offer downloadable, print-friendly versions of critical content.
Use accessible language: Use plain language in both your content and user interface to ensure your service is usable by all. Replace niche terminology or jargon with widely understood terms. Always adhere to the government’s Style Manual and plain language guidance.
Off1.20 Each SSA includes the following core components:
1.21 There are significant differences in how these components are incorporated into each SSA, reflecting the distinct evolution paths each SSA has undertaken. More recently, the DTA has been working with the SSA sellers to more consistently align the terms and conditions across the SSAs. This has required some of the arrangements to transition from terms and conditions which were initially based on the sellers’ terms and conditions, to a format that better meets Commonwealth needs. Consequently, each SSA exhibits key differences in:
1.22 A summary of the key establishment dates for the SSAs are outlined in brief below.
1.23 The AWS SSA was first established on 1 May 2019, and is now in its third iteration, which commenced on 1 April 2025 for a three-year term that expires 31 March 2028.
1.24 The IBM SSA was first established in June 2018, and is now in its second iteration, which commenced 15 December 2022 and will expire 15 December 2027.
1.25 The first SSA with Microsoft was established in July 2009 (this agreement was signed in February 2009, however, began operating from July 2009). This SSA is now in its fifth iteration which was signed on 1 July 2022 has been extended through to 30 June 2026. The current iteration of the SSA provided for an initial term of 3 years, to which there was a subsequent contract renegotiation to extend the contract further for one year.
1.26 Products and services are procured from Microsoft’s incumbent Licensed Solution Provider, Data#3, through a reseller arrangement under the Software and ERP Marketplace Panel (SON3490955).
1.27 The Oracle SSA was established on 25 November 2020 for an initial period of three years. Options have been exercised, and the SSA now expires 24 November 2025.
1.28 The Rimini Street SSA was established on 28 January 2020 for an initial period of four years, with options having been exercised under the contract such that the SSA now expires 28 January 2026.
1.29 The SAP SSA was first established on 29 June 2017 and is now in its second iteration, which commenced on 29 June 2024 for a three-year term that expires 28 June 2027.
1.30 The table below provides a high-level overview of the products and services offered under the existing arrangements.
Seller | Standing Order Number (SON) | Products and services |
|---|---|---|
AWS | SON4124095 |
|
IBM | SON3933978 |
|
Microsoft | SON3615953 | All Microsoft products and services, including:
|
Oracle | SON3726074 | All Oracle products and services, including:
|
Rimini Street | SON3660909 |
|
SAP | SON4059115 |
|
1.31 Further information about the sellers can be found in Appendix A: Overview of SSA sellers and Appendix E: Commercially sensitive analysis.
1.32 The timeframes relevant to each of the existing SSAs is provided below. (Where option periods exist, these are not included on the below timeframes as this information is commercially sensitive. Microsoft’s VSA dates reflect the end dates.)
The figure shows the timeframes of the SSAs as follows, noting the date of this report is 2025:
AWS:
AWS1.0 was 1 May 2019 to 30 Apr 2022.
AWS2.0 was 1 May 2022 to 30 Apr 2025.
AWS3.0 is 1 Apr 2025 to 31 Mar 2028.
IBM:
IBM1.0 was 28 Jun 2018 to 30 Jun 2023.
IBM2.0 is 15 Dec 2022 to 15 Dec 2027.
Microsoft:
WoAG agreement, now known as the Volume Sourcing Agreement (VSA) 1 was 1 Jul 2009 to 30 Jun 2013.
VSA2 was 1 Jul 2013 to 30 Jun 2016.
VSA3 was 1 Jul 2015 to 30 Jun 2019.
VSA4 was 1 Jul 2019 to 30 Jun 2022.
VSA5 is 1 Jul 2022 to 30 Jun 2026.
Oracle:
25 Nov 2020 to 24 Nov 2025.
Rimini Street:
28 Jan 2020 to 28 Jan 2026.
SAP:
SAP1.0 was 29 Sep 2017 to 28 Jun 2024.
SAP2.0 is 29 Jun 2024 to 28 Jun 2027.
1.33 Appendix B: SSAs representation on the DTA panels provides further information on the representation of the SSAs on BuyICT with respect to the DTA's marketplaces and panels.
1.34 SSAs primarily support the requirements of non-corporate Commonwealth entities (NCEs), and their use as head agreements is mandatory for these agencies. (Whilst their use as head agreements is mandatory, this does not compel the selection of any particular products or services from the SSA seller.) However, they can also be utilised in other contexts (in some instances, the SSA seller or DTA must approve this), which are:
1.35 Appendix E: Commercially sensitive analysis outlines the availability for use of these arrangements across these entities.
1.36 The amount the Australian Government spends on the SSAs is reported on AusTender (the reporting portal for all Australian Government contracts over $10,000).
1.37 The figures below provide an overview of the total value of the reported spend on AusTender for each of the SSA sellers for the period 2019-2024. (Data sourced from AusTender. The total spend for Microsoft includes values reported through Data#3 for Microsoft products and services.) In respect of these figures, the full value of a contract is included where the start date fell between 1 July 2019 and 30 June 2024, and are split out in to:
1.43 The DTA has internal guidance for assessing whether an SSA be established.
1.44 When a potential new SSA has been identified, the DTA seeks approval from the relevant portfolio and Australian Government for policy authority to establish the new mandated arrangements and to resource negotiations, which are conducted directly with the seller on behalf of the Australian Government. The DTA then continues to manage the arrangements, including renegotiation of renewals. (Finance Minister approval is not obtained to renegotiate renewals of the SSAs.)
1.45 The below figure outlines the process the DTA follows:
1.55 The review noted the SSAs are only one of several contracting mechanisms used by the Australian Government. The list and table below provide a high-level comparison:
Element | Seller standard T&Cs | Standard contract | Piggy-back contract | Model contracts | Panel and marketplace | SSA |
|---|---|---|---|---|---|---|
Pricing | As per proposal or quote, or as otherwise negotiated by the agency | As per proposal or quote, or as otherwise negotiated by the agency | As agreed between head agency and seller, with any discounts negotiated into contracts | As agreed between the buyer and seller | Standard panel rates, with any discounts negotiated into contracts | Negotiated discount pricing |
Terms and conditions (T&Cs) | Sellers T&Cs, subject to any amendments negotiated by the agency | Australian Government common T&Cs, subject to any amendments negotiated by the Seller | Australian Government T&Cs, subject to any amendments negotiated by the Seller | Australian Government T&Cs, with some model contracts allowing for amendments | Australian Government T&Cs, with tailorable clauses | Negotiated T&Cs, with the ability to specify additional options or terms in the contract |
Typical engagement model | Seller contract | Australian Government contract | Australian Government contract | Australian Government head agreement, with contracts / work orders | Australian Government head agreement, with contracts / work orders | Australian Government head agreement, with contracts / work orders |
Scope and timeframes | Agreed between seller and Australian Government agency | Agreed between seller and Australian Government agency | Agreed between seller and lead Australian Government agency, and separately with any subsequent agency | Head agency agree with seller common scope or timeframes, with contracts / work orders containing deliverable specifics | Head agency agree with seller common scope or timeframes, with contracts / work orders containing deliverable specifics | Head agency agree with seller common scope or timeframes, with contracts / work orders containing deliverable specifics |
1.56 Undertaking a competitive and compliant procurement process prior to purchasing any new technology products and services is critical to ensuring value for money is achieved and that the procurement aligns with Commonwealth policy requirements. For this reason, the SSAs are designed to fit into the standard procurement lifecycle undertaken by buyers, which is depicted in the figure below.