What is the Union added value criterion in CADA procurement?

As proposed, Article 32 of the Cloud and AI Development Act (CADA) — headed "Union added value" — would require contracting authorities to include, as part

Summary As proposed, Article 32 of the Cloud and AI Development Act (CADA) — headed "Union added value" — would require contracting authorities to include, as part of the quality evaluation, a non-price award criterion in procurement of innovative cloud computing services and AI systems. Under Article 32(1) it evaluates a tenderer's contribution to the development of a European cloud and AI ecosystem: strengthening the Union digital supply chain, integrating Union technologies and Union-funded R&D, supporting security of supply, and using critical hardware designed or manufactured in the Union (Article 32(3)). The criterion must be linked to the subject matter and, critically, be ancillary and not decisive (Article 32(2)).

Detail

Article 32 is CADA's demand-side lever: a way for public buyers to steer procurement toward a stronger European cloud and AI ecosystem without abandoning competitive, non-discriminatory procurement.

The obligation (Article 32(1))

Article 32(1) provides that "in public procurement procedures for innovative cloud computing services and AI systems, contracting authorities shall include, as part of the quality evaluation of the tender, non-price award criteria that allow them to evaluate the tenderer's contribution to the development of a European cloud and AI ecosystem." Two features stand out: the obligation is mandatory ("shall include") for the procurements in scope, and it is confined to innovative cloud computing services and AI systems — not all cloud purchases.

The four conditions (Article 32(2))

To keep the criterion compatible with procurement-law principles and the EU's international commitments, Article 32(2) requires the non-price criteria to be:

(a) linked to the subject matter of the contract;
(b) not conferring unrestricted freedom of choice on the contracting authority;
(c) expressly set out in the procurement documents or in the contract notice; and
(d) ancillary and not decisive in the award of the contract.

Condition (d) is the central safeguard: Union added value may inform the score but may not, on its own, decide the award. It must remain subordinate to the core technical and financial criteria.

What "Union added value" covers (Article 32(3))

Without affecting authorities' discretion to apply additional criteria, Article 32(3) lists what the criteria must enable authorities to evaluate — the extent to which:

(a) the tenderer contributes to strengthening the Union's digital technology supply chain, including using software or hardware designed or manufactured in the Union;
(b) the tenderer has integrated Union-developed technologies, including R&D results from Union-funded programmes, and uses Union-developed tools such as standards, specifications, software or models;
(c) the innovation required to deliver the service strengthens security of supply and the development of a European cloud and AI ecosystem; and
(d) the service is delivered, to the greatest extent feasible given market availability and technical requirements, through critical computing, storage and networking hardware components designed and/or manufactured in the Union — or, where that is not feasible, through third-country hardware that contributes to security of supply and the European ecosystem.

Weighting and proportionality

Article 32 itself fixes no numerical weight. Recital 67 of the proposal provides the guidance: the European added value criterion "should not be decisive for award of the contract" and should preserve "the primacy of technical and financial criteria directly connected to the performance requirements"; for this purpose authorities "could consider a maximum weighting of 15 out of 120 points" (12.5%) to keep it proportionate and subordinate. ("European added value" in Recital 67 and "Union added value" in the Article 32 heading refer to the same concept.)

Why this criterion exists

Recital 66 explains the logic: public procurement "frequently serves as a primary signal of market direction," and requirements imposed by public authorities tend to be mirrored by private-sector entities in regulated industries, producing spillover effects that realign the broader market over time. Article 32 turns that signalling power toward a stronger European cloud and AI ecosystem. It is a demand-side measure that complements CADA's supply-side measures — such as data-centre acceleration zones and support for cloud and AI capabilities — by using public purchasing to stimulate demand for European technology, components and R&D outputs.

How it relates to innovation procurement (Article 33)

Article 32 does not stand alone. It sits alongside Article 33, which would have Member States monitor and report on their procurement of innovation in cloud computing services and AI systems, and pursue the objective that at least 25% of such procurement be awarded to innovative SMEs (Article 33(4)), with plans set out in the national strategies under Article 7. Article 33 also asks Union entities and contracting authorities to promote preliminary market consultations, matchmaking with European SMEs and start-ups, and SME-friendly contract clauses. Together, Article 32 (the added-value award criterion) and Article 33 (innovation-procurement monitoring and SME uptake) form CADA's procurement-side toolkit for strengthening the European ecosystem. Article 32 governs how you score innovative tenders; Article 33 governs how the system tracks and encourages innovation procurement and SME participation over time.

What this means for you

For public-sector procurement teams, Article 32 changes how you evaluate tenders for innovative cloud and AI solutions.

When drafting procurement documents for in-scope innovative solutions, you would need to:

Confirm scope. The duty applies to innovative cloud computing services and AI systems, not standard off-the-shelf purchases.
Define clear, verifiable metrics drawn from Article 32(3) — for example, EU-origin hardware components or integration of Union-funded R&D — rather than vague preferences.
Publish the criteria in the contract notice or procurement documents, as Article 32(2)(c) requires.
Keep the weighting modest so the criterion stays ancillary and not decisive; the 15/120 figure in Recital 67 is the indicative ceiling, not a legal minimum.

For tenderers, this means preparing verifiable evidence of supply-chain origin, hardware/software design and manufacturing locations, and any Union-funded R&D integrated into the offering.

Common misconceptions

"It is a quota for European companies." No. It rewards contribution to the European ecosystem (EU-designed hardware/software, Union-funded R&D, security of supply), not the nationality of the bidder. A non-EU bidder can score well on these elements.

"It overrides price and technical quality." No. Article 32(2)(d) makes the criterion ancillary and not decisive; a stronger technical-and-financial bid can still win despite a lower added-value score.

"It applies to all procurement." No. Article 32(1) is limited to innovative cloud computing services and AI systems.

"It violates WTO/GPA rules." The proposal is structured to operate within the EU's international commitments — linking the criterion to the subject matter and keeping it ancillary and not decisive. Whether any particular application complies would turn on how an authority applies it.

This is general information about a draft EU regulation, not legal advice.