Summary Under the proposed Cloud and AI Development Act (CADA), Article 32 requires contracting authorities to include "Union added value" as a non-price award criterion in public procurement for innovative cloud computing services and AI systems. Crucially, Article 32(2)(d) mandates that these criteria be "ancillary and not decisive in the award of the contract." This means Union added value must sit alongside price and core technical quality criteria without overriding them. While authorities must evaluate a tenderer's contribution to the European ecosystem (e.g., Union-designed hardware or R&D), the criterion cannot be the primary driver of the award decision. The proposal suggests a practical weighting cap of 15 out of 120 points to ensure compliance with this ancillary constraint, preserving the primacy of technical and financial performance under the Most Economically Advantageous Tender (MEAT) framework.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a targeted mechanism to steer public procurement toward strengthening the European cloud and AI ecosystem. Unlike broader procurement directives that focus on general market access, CADA specifically targets "innovative cloud computing services and AI systems" to foster technological sovereignty. This is achieved through Article 32, which integrates "Union added value" directly into the award criteria of the Most Economically Advantageous Tender (MEAT) procedure.

The Legal Framework: Article 32 and MEAT

In EU public procurement, the MEAT principle (Directive 2014/24/EU) requires contracts to be awarded based on the best price-quality ratio. CADA does not replace this principle but inserts a specific, mandatory quality component into it.

Article 32(1) states:

"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."

This provision transforms "Union added value" from a voluntary consideration into a mandatory quality criterion for the specified scope. It sits within the quality matrix alongside other factors such as technical merit, security compliance, or service levels, and is distinct from the price criterion.

The "Ancillary and Not Decisive" Constraint

The most critical operational constraint in CADA's procurement framework is found in Article 32(2)(d). When applying these non-price award criteria, contracting authorities must ensure they are:

"(d) ancillary and not decisive in the award of the contract."

This phrasing imposes a strict hierarchy on the evaluation process:

  1. Ancillary Nature: The criterion is supplementary. It supports the evaluation of the tender's overall quality but cannot form the primary basis for the award. The core decision must remain rooted in the technical and financial merits directly connected to the performance requirements of the service or system.
  2. Non-Decisive Status: The Union added value criterion cannot act as a tie-breaker that determines the winner if other criteria are equal, nor can it override a superior technical or financial offer. If a tenderer offers a technically superior solution at a competitive price but scores lower on Union added value than a less capable competitor, the technically superior tender must still win, provided the Union added value criterion is properly applied as ancillary.

This constraint is designed to prevent the criterion from becoming a de facto protectionist measure that distorts competition by allowing inferior products to win solely based on their European origin or supply chain composition. It ensures compliance with the fundamental EU procurement principles of equal treatment, non-discrimination, and transparency.

Cumulative Conditions for Drafting Criteria

To fit correctly within the MEAT evaluation, Article 32(2) imposes four cumulative conditions on how these criteria are structured. Failure to meet any one of these renders the criterion non-compliant:

  • Linked to the subject matter (Article 32(2)(a)): The Union added value criterion must be directly relevant to the cloud or AI service being procured. It cannot be a generic corporate social responsibility metric unrelated to the contract's execution.
  • No unrestricted freedom of choice (Article 32(2)(b)): The criterion must be objective and measurable. Contracting authorities cannot use it to arbitrarily select a preferred bidder. The evaluation methodology must be clear, allowing tenderers to understand exactly how they will be scored.
  • Expressly set out (Article 32(2)(c)): The criteria must be clearly defined in the procurement documents or the contract notice. They cannot be introduced ex post facto during the evaluation phase. This ensures legal certainty and allows all economic operators to tailor their bids accordingly.
  • Ancillary and not decisive (Article 32(2)(d)): As detailed above, this preserves the primacy of technical and financial criteria.

Defining "Union Added Value"

Article 32(3) provides a non-exhaustive list of factors that contracting authorities may evaluate to determine Union added value. These factors allow authorities to assess the extent to which a tenderer:

  • (a) Contributes to strengthening the digital technology supply chain in the Union, including the use of software or hardware designed or manufactured in the Union.
  • (b) Has integrated technologies developed in the Union, including research and development results stemming from Union-funded research and development programmes and makes use of tools, such as standards, specification, software, models or other technology developed in the Union.
  • (c) The innovation required to deliver the service contributes to strengthening the security of supply and the development of a European cloud and AI ecosystem.
  • (d) The service is delivered, to the greatest extent feasible with regard to market availability and technical requirements, through critical computing, storage and networking hardware components designed and/or manufactured in the Union, or, where this is not feasible, through hardware components from a third country that contributes to strengthening the security of supply and the development of a European cloud and AI ecosystem.

These factors allow authorities to quantify "European-ness" in terms of supply chain resilience, technological integration, and hardware origin, fitting them into a scored quality matrix.

Weighting and Practical Application

While Article 32 does not prescribe a specific numerical weight, the Explanatory Memorandum and Recital 67 provide a crucial practical guideline to ensure the "ancillary" constraint is respected. Recital 67 states:

"For this purpose, contracting authorities could consider a maximum weighting of 15 out of 120 points to be allocated to European added value within the overall evaluation methodology, ensuring that it remains proportionate and subordinate to the core contract award criteria."

This suggests a cap of approximately 12.5% of the total score. In a typical MEAT matrix where Price might carry 40% and Technical Quality 60%, Union added value would likely be a sub-component of the Technical Quality score. Assigning it a weight that exceeds core technical or financial criteria risks violating the "not decisive" requirement of Article 32(2)(d).

What this means for you

For in-house counsel, procurement officers, and compliance teams, the integration of Union added value into MEAT requires immediate attention to procurement documentation and evaluation methodologies.

  1. Mandatory Inclusion: Ensure that all tenders for "innovative cloud computing services and AI systems" explicitly include a Union added value criterion as defined in Article 32. This must be stated in the contract notice and procurement documents. Failure to include this criterion may constitute a procedural error if CADA is adopted.
  2. Calibrate Weighting Strictly: When designing the MEAT matrix, ensure the Union added value criterion is scored as "ancillary." Avoid assigning it a weight that exceeds core technical or financial criteria. A safe harbor, as suggested by the Commission's impact assessment, is keeping it below 15 out of 120 points (approx. 12.5%).
  3. Objective Scoring Rubrics: Develop clear, objective metrics for assessing the four factors in Article 32(3). For example, define precisely what constitutes "hardware designed in the Union" and how points are awarded for using Union-funded R&D results. Avoid subjective language that could be challenged as granting "unrestricted freedom of choice" under Article 32(2)(b).
  4. Feasibility Checks: When evaluating Article 32(3)(d), remember the feasibility constraint. If Union hardware is not technically feasible, tenderers can use third-country hardware that contributes to security of supply. The evaluation must be nuanced, not binary.
  5. Documentation of Compliance: Keep detailed records of how the Union added value criterion was applied. If a tenderer challenges the award, you must be able to demonstrate that the criterion was ancillary, linked to the subject matter, and did not override a technically superior bid.

Common misconceptions

"Union added value is a separate award criterion outside MEAT."

  • Reality: It is an integral part of the MEAT quality evaluation. It is not a separate "sovereignty" award but a quality factor within the standard price-quality ratio assessment.

"'Ancillary and not decisive' means the criterion is optional or negligible."

  • Reality: It must be applied as a mandatory criterion, but it cannot be the deciding factor. It influences the score but cannot override the core technical and financial merits of the tender.

"Any use of European hardware automatically qualifies for maximum points."

  • Reality: Article 32(3)(d) requires that the use of Union hardware be "to the greatest extent feasible with regard to market availability and technical requirements." If Union hardware is not technically feasible, tenderers can use third-country hardware that contributes to security of supply. The evaluation must be nuanced, not binary.

"This applies to all public procurement."

  • Reality: Article 32 specifically applies to "innovative cloud computing services and AI systems." It does not automatically apply to standard IT hardware procurement or non-digital services unless they fall within this specific scope.

Related

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