The figure shows the Australian Government buy profiles for the SSA sellers and key digital marketplaces for 2019 to 2024 as per Contract Notices to indicate approximate values covering the total of Standing Offer Number and Contract Notices.
In relation to the SSA sellers, the buy profiles of four SSA sellers (AWS, Oracle, Rimini Street, and SAP) are less than $2 billion each, and the buy profiles of two SSA sellers (IBM and Microsoft) are between $2 to $4 billion each.
In relation to other established digital marketplaces and panels, Digital Marketplace Panel 1 is between $18 to $20 billion; the Hardware Marketplace Panel and the Software and ERP Marketplace Panel are between $2 to $4 billion each; the Telecommunications Marketplace, Cloud Marketplace, and Data Centre Facilities Supplies Panel are less than $2 billion each, and the other panels are less than $2 billion in total.
Off1.39 The figures above show that buyers across the Australian Government do not solely rely upon SSA sellers, with approximately 76% of the spend profile going through the other digital marketplaces and panels.
1.40 In respect of these figures, the review noted the values published on AusTender do not align to the actual spend under the SSAs for the following key reasons:
1.41 Further, some sellers expressly constrain the DTA from publishing information, including SSA spends, unless it is already in the public domain. Noting this, however, engagement with the SSA sellers through the review indicates willingness from the SSA sellers to support transparency common in government procurement globally.
1.42 To address the constraints above and to enhance the transparency of the Australian Government's spending on the SSA sellers, the DTA should, in collaboration with the SSA sellers, publish the full value of expenditure under the SSAs for each respective SSA seller.
The figure shows the high-level process for how DTA manages SSAs, as follows:
1.46 The following briefly outlines each of these steps:
1.47 Details on the operational costs of this work for DTA are outlined in Costs section.
1.48 The DTA is funded to establish and maintain the SSAs through two means:
1.49 Separately, in certain circumstances, buyers must pay a savings fee which is calculated based on the total contract value. Monies collected in the form of savings fees are temporarily stored in a special account and returned to the Consolidated Revenue Fund (CRF) in the following financial year. (The CRF savings fee is extended to additional arrangements as agreed by the Finance Minister.) These monies cannot be used to fund activities of the DTA.
1.50 Of note, buyers pay either the CAF or the savings fee, not both.
1.51 The CAF and CRF savings fee are paid to the ICT Coordinated Procurement Special Account 2017 which is limited appropriation that allocates funds for specific purposes. The balance of the special account determines the amount available for expenditure, subject to strict rules around the use of the funds. (Appropriate expenditure includes: Administration of the SSAs, pass-through costs, compliance and reporting, development of procurement technology and tools, user research, technical advisory, and staffing costs.) The Australian National Audit Office audits this account annually.
1.52 The following graphic illustrates the interaction between the amount paid to a seller, the CAF or CRF savings fee paid by the buyer and the discount realised.
1.53 The table below summarises the CAF and CRF fees payable.
Arrangement | Fee type | Amount |
|---|---|---|
AWS | Either CAF or CRF fee | |
IBM | CRF fee (and one non-Commonwealth entity pays a CAF) | 1.25% to 2.5% of agency spend |
Microsoft | CAF only | $3.00 per E3 licence |
Oracle | CRF fee only | 2.5% of agency spend |
Rimini Street | CAF fee only | 2.5% of agency spend |
SAP | CRF fee only | 0.5% to 5% of agency spend |
1.54 Further details can be found in the Funding model complexity section of this report.
The figure depicts how the savings and fees payable by agencies are allocated, from a whole of Australian Government perspective, to the DTA and/or the Consolidated Revenue Fund, as follows:
Agency:
DTA:
Consolidated Revenue Fund:
The financial flow for the CAF fee paid by buyer is to move from the Agency to the DTA.
The financial flow for the CRF fee paid by buyer is to move from the Agency to the DTA and then to the Consolidated Revenue fund.
OffThe figure shows the procurement lifecycle and how buyers typically engage with the SSA, as follows:
Measure against the Data and Digital Government Strategy: Ensure your service meets the Data and Digital Government Strategy. Consider how information you collect and report could improve your service in line with the Strategy’s implementation plan.
Apply benefits management: All digital and ICT-enabled investment proposals must define their purpose, outcomes and methods for measuring, monitoring and optimising them. Find out more in the Benefits Management Policy.
Off1.57 NCEs must use the SSA contracting framework when buying from an SSA seller. For any other entity, the SSAs are not mandatory.
1.58 The selection of sellers (SSA sellers and non-SSA sellers) to include on the market approach is made by the buyer. The review noted that buyers can utilise Limited Tender provisions in accordance with the CPRs, and this is further discussed in the Procurement and contracts section of this report. In this regard, buyers may approach a limited number of sellers or direct source from an SSA seller. Critically, the review noted the CPRs enable this, as buyers can utilise the Limited Tender provisions irrespective of an SSA being in place.
1.59 The above is distinct from the process the DTA follow to establish an SSA, which is discussed in previous sections.
The figure shows a summary of benefits delivered through existing SSA model, grouped by primary benefits and secondary benefits.
Primary benefits:
Secondary benefits:
The review also considered the costs and key risks associated with the SSAs. Establishing an SSA costs the DTA $1.6m, and managing the SSA ongoing costs $1m annually. Key risks of the SSAs were assessed overall to be low to medium, including risks associated with buyers being locked into technologies and other sellers being locked out of government.
From a cost-benefit and risk perspective, the review concluded that the benefits of the SSAs far exceed the costs and are well worth the associated risks.
The use of SSAs should continue.
The figure shows the continuum of nations from 'Most decentralised' to 'Most centralised': United States of America, United Kingdom, Australia, New Zealand, and Canada.
Off4.8 The figure below further outlines the comparison between the respective nations.
| NATIONS | FACTS | FEATURES | COMMONALITIES |
![]() USA |
|
| Common benefits sought:
Common challenges:
|
![]() UK |
|
| |
![]() NZ |
|
| |
![]() CAN |
|
|
This decision-making framework helps you determine how to consolidate your access points.
Consolidate generally means to combine or unite things. For example, through migrating an existing service from one place to another or incorporating a new service into an existing access point.
First, think about your users. Make the most of existing access points by understanding where users already go to access your services. Start here if your service is for individuals (but not suitable for myGov), businesses or providers.
Next, look at the current digital landscape. Assess and consider where you can consolidate your new service with an existing access point. If this is not an option, investigate how you can migrate existing services into a new access point with the new service.
Then, check for limitations. Consider if there are any challenges making the new services available through an existing access point or with consolidating platforms, portals or services. Could there be technical issues interfacing with legacy systems or legal barriers such as data sharing?
Finally, assess the investment. Determine if consolidating access points is affordable and that the cost is outweighed by the benefits. For example, cost to consolidate services is outweighed by a significantly better experience for users.
Note: this content is a decision tree. The first step has one question. If you answer yes, you progress to the next step. If you answer no, your service may be out of scope, or the myGov decision-making framework should be applied. The second and third steps have two questions. If you answer yes to either question, you progress to the next step. If you answer no to both questions, you may be eligible for an exemption. The fourth step is a yes or no question.
The first step is ‘Know your user’. Is the service for individuals (not suitable for myGov), business or providers? If yes, continue to the next step. If no, your service may be out of scope, or the myGov decision-making framework should be applied. Process ends here.
The second step is ‘Evaluate existing access points’. Is there an existing access point your services can consolidate with? If yes, continue to the next step. If no, can you create a new access point and migrate other existing access points into it? If yes, continue to the next step. If no, you may be eligible for an exemption. Please refer to the Compliance, reporting and exemption guide for more information.
The third step is ‘Limitations’. Is your service free from any limitations to consolidate? If yes, continue to the next step. If no, can these limitations be overcome? If yes, continue to the next step. If no, you may be eligible for an exemption. Please refer to the Compliance, reporting and exemption guide for more information.
The fourth and final step is ‘Assess the investment’. Would consolidating your access points be cost effective? If yes, your intention to consolidate and/or migrate your service must be clearly articulated within your new policy proposal or business case. If no, you may be eligible for an exemption. Please refer to the Compliance, reporting and exemption guide for more information.
Off