Summary Under the proposed Cloud and AI Development Act (CADA), public procurement for cloud and AI services includes specific "Union added value" award criteria. To score points under Article 32, providers must explicitly evidence the integration of technologies developed in the Union. This requires a traceable evidence pack that directly links EU-funded R&D results, EU standards/specifications, and EU-developed software or models to the specific subject matter of the contract. Mere presence in the EU is insufficient; the bid must demonstrate how these specific Union assets enhance the service being tendered.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a strategic shift in how public contracts for cloud computing and AI systems are awarded. Beyond price and core technical performance, Article 32 mandates that contracting authorities include non-price award criteria to evaluate a tenderer's contribution to the European digital ecosystem. These criteria are designed to reinforce the Union's technological sovereignty and supply chain resilience.

While Article 32(2) clarifies that these criteria must be "ancillary and not decisive in the award of the contract," they serve as a critical differentiator in competitive tenders where technical and financial scores are closely matched. The core of this evaluation lies in Article 32(3), which outlines the specific dimensions of Union added value.

The Specific Requirement: Article 32(3)(b)

The most relevant provision for providers integrating research and development is Article 32(3)(b). This clause requires contracting authorities to evaluate the extent to which the tenderer:

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

To successfully satisfy this criterion, a provider cannot rely on vague assertions of "European innovation." The proposal demands a rigorous, auditable trail that connects the proposed service directly to specific Union-developed assets. The evidence must be granular, verifiable, and strictly relevant to the contract at hand.

1. Identifying Qualifying EU R&D and Technology

Providers must first conduct a comprehensive audit of their cloud stack, AI models, and service delivery mechanisms to identify components that qualify under Article 32(3)(b). The scope includes:

  • EU-Funded R&D Results: Technologies that originated from or were significantly advanced by Union-funded programmes. This includes outputs from Horizon Europe, the Digital Europe Programme, or the European Competitiveness Fund (ECF). Examples include specific algorithms, open-source libraries, hardware architectures, or middleware developed through these grants.
  • EU Standards and Specifications: The implementation of standards developed by European standardisation bodies (such as CEN, CENELEC, or ETSI) or specifications defined in EU legislation (e.g., the Interoperable Europe Act). The bid must show active use of these tools, not just awareness of them.
  • EU-Developed Software and Models: Proprietary or open-source software, AI models, or data sets where the primary development activity, intellectual property creation, or significant modification occurred within the Union. This includes "models" explicitly mentioned in the text of Article 32(3)(b).

2. Creating a Traceable Evidence Pack

The success of a bid under CADA hinges on the quality of the evidence pack. Providers should prepare a dedicated annex titled "Union Added Value" that serves as a verifiable audit trail. This pack must be structured to allow evaluators to instantly verify claims. Key elements include:

  • Grant Agreement References: For R&D results, cite the specific Grant Agreement Number, the project acronym (e.g., from Horizon Europe), and the specific work package or deliverable that produced the technology. Attach the final project report or a summary of the R&D outcome to prove the origin.
  • Standard Compliance Documentation: Provide certificates of conformity, test reports, or declarations of performance demonstrating adherence to relevant European standards (e.g., EN standards for cybersecurity, data centre efficiency, or interoperability).
  • Development Provenance Records: For software and AI models, provide documentation showing the "development in the Union" claim. This could include:
    • Repository logs showing commit history from Union-based developers.
    • Intellectual property registration documents (e.g., EU trademarks or patents) filed within the Union.
    • Training logs for AI models indicating that the training data and compute resources were located in the Union.
  • Integration Maps: A technical diagram or narrative that explicitly maps how these EU-developed components are integrated into the final service. This visual or narrative link is crucial to proving that the technology is not merely "available" but is actually "integrated" into the solution.

3. Linking Evidence to the Contract Subject Matter

A critical constraint in Article 32(2) is that non-price award criteria must be "linked to the subject matter of the contract." This is a strict admissibility filter.

Providers cannot simply list every EU-funded project their company has ever participated in. The evidence must be directly relevant to the specific cloud or AI service being procured.

  • Relevant Example: If the contract is for a sovereign cloud infrastructure for healthcare data, evidence of EU R&D in secure data handling, health-specific AI models, or EU standards for medical data interoperability is highly relevant.
  • Irrelevant Example: Evidence of EU R&D in automotive AI or agricultural drones would likely be disregarded if the contract is for healthcare infrastructure, as it does not link to the subject matter.

The bid must explicitly articulate the connection between the EU-developed technology and the performance, security, resilience, or efficiency of the specific service being tendered. The evaluator must be able to see how the Union asset directly benefits the public sector body's specific needs.

4. The Role of Union-Funded Programmes

The proposal explicitly highlights the importance of leveraging results from Union-funded research and development programmes. Providers should actively map their existing technology portfolio against outputs from the Digital Europe Programme and Horizon Europe.

If a component of your cloud stack was co-developed with an EU consortium, this is a prime example of "technologies developed in the Union" that should be highlighted. The bid should detail how these specific R&D outcomes enhance the service's resilience, security, or performance. For instance, if a specific encryption module was developed under a Horizon Europe grant to address quantum threats, and that module is now part of the proposed cloud service, this is a direct, high-value link under Article 32(3)(b).

What this means for you

For cloud service providers, data centre operators, and AI model developers, CADA transforms the procurement landscape. It moves the competition from a purely commercial assessment to one that also values strategic autonomy and European innovation capacity.

Immediate Actions for Providers:

  1. Audit Your Stack: Conduct a full review of your cloud and AI service offerings. Identify every component that originated from EU R&D, complies with EU standards, or was developed within the Union.
  2. Build the Evidence Repository: Start collecting grant agreements, standard certificates, development logs, and IP records immediately. Do not wait for the Request for Proposal (RFP). Create a centralized, searchable database of these assets to ensure rapid retrieval during bid preparation.
  3. Train Your Bid Teams: Ensure your proposal writers understand the distinction between general "EU presence" (e.g., having an office in Brussels) and specific "integration of EU-developed technology" as defined in Article 32(3)(b). They must know how to draw the precise line between the technology and the contract subject matter.
  4. Collaborate with Research Partners: If you have partnerships with universities or research institutes funded by the EU, formalize the link between their outputs and your commercial products. Secure written confirmation or data sheets that trace the technology from the research project to your commercial offering.

Common misconceptions

"Having EU offices is enough."

  • Correction: No. Article 32(3)(b) specifically requires the integration of technologies developed in the Union. Mere employment of staff in the EU or having a registered office does not constitute R&D integration. You must prove the technology itself was developed, significantly enhanced, or standardized within the Union jurisdiction.

"Any EU standard counts."

  • Correction: While using EU standards is a positive factor, the criterion emphasizes integration. You must show how the use of these standards or specifications actively contributes to the service's quality, security, or interoperability in the context of the specific contract. Simply listing a standard without explaining its application to the service will likely yield no points.

"We can list all our EU-funded projects."

  • Correction: As noted, the evidence must be linked to the subject matter of the contract (Article 32(2)). Irrelevant R&D outcomes will not score points and may clutter the bid, making it harder for evaluators to find the relevant evidence. Quality and relevance trump quantity.

"This is the main award criterion."

  • Correction: Article 32(2)(d) states that these criteria are "ancillary and not decisive in the award of the contract." You must still win on core technical and financial merits. However, in a competitive field where technical scores are tied, these ancillary points can be the deciding factor.

Related

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