Summary As proposed in the Cloud and AI Development Act (CADA), the duration of a "strategic project" designation is not arbitrary; it is strictly derived from the project's predicted operational lifetime. Article 14(3) mandates that applicants must include specific information in their proposal to substantiate this predicted lifetime. The Commission will determine the designation period based solely on this evidence. Failure to provide robust, verifiable data on the project's longevity may result in a shorter designation period or rejection, while providing incorrect information risks withdrawal of the status under Article 14(4).

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, establishes a mechanism for the European Commission to designate specific data centre projects as "strategic projects." This status is designed to accelerate the deployment of computing capacity across the Union by streamlining permitting and enabling access to support measures. However, the temporal scope of this designation is a critical variable that applicants must carefully engineer into their proposals.

The Legal Mechanism: Article 14(3)

The core requirement for substantiating the predicted lifetime is explicitly defined in Article 14(3) of the CADA proposal. This paragraph establishes a direct causal link between the technical and economic lifespan of the infrastructure and the period during which the project enjoys strategic privileges.

The text of Article 14(3) states:

"The duration of the designation as a strategic project shall be based on the predicted lifetime of the project. The applicant shall include in the proposal the information necessary to substantiate the predicted lifetime of the project, on the basis of which the duration of the designation as strategic project shall be determined."

This provision creates a "evidence-based" duration model. The Commission does not assign a standard fixed term (e.g., 10 or 15 years) to all applicants. Instead, the designation period is a function of the applicant's substantiated claim. If an applicant claims a 20-year operational life but fails to provide the necessary information to prove it, the Commission cannot legally base the designation duration on that claim.

What Constitutes "Necessary Information"?

While Article 14 does not provide an exhaustive, itemized checklist of documents, the legal obligation to "substantiate" implies a requirement for verifiable, objective, and engineering-grade evidence. For technical leaders and project developers, this means moving beyond high-level marketing estimates or optimistic financial projections. The proposal must demonstrate that the infrastructure is physically and economically viable for the claimed duration.

To meet the requirements of Article 14(3), a robust proposal should likely include the following categories of evidence:

  1. Technical Durability and Structural Assessments: Evidence must demonstrate that the physical assets selected for the project are rated for the claimed operational period. This includes:

    • Manufacturer Specifications: Data sheets for servers, cooling systems, power distribution units, and battery backup systems indicating their expected useful life and reliability metrics (e.g., MTBF).
    • Structural Integrity Reports: Engineering assessments of the building's design life, foundation stability, and resilience to environmental factors over the predicted period.
    • Redundancy and Resilience Plans: Documentation showing how the facility will maintain operational viability and competitiveness as components age, including plans for component replacement and system refreshes.

  2. Economic Viability and Financial Modelling: A predicted lifetime is not just a technical figure; it must be economically sustainable. The proposal should include financial models demonstrating that the project will remain viable for the claimed duration. Key elements include:

    • Cost Projections: Detailed estimates of energy costs, maintenance expenditures, and operational expenditures (OPEX) over the full lifecycle.
    • Revenue Streams: Evidence of long-term demand or contractual commitments (e.g., Power Purchase Agreements, long-term leases) that support the project's financial health.
    • Obsolescence Analysis: A demonstration that the project will not become financially unviable or technologically obsolete before the end of the predicted lifetime.

  3. Maintenance, Upgrade, and Evolution Roadmaps: Data centres are dynamic environments. A static facility cannot operate for decades without adaptation. The substantiation must show a clear plan for how the facility will evolve to remain relevant. This includes:

    • Technology Refresh Cycles: A schedule for hardware upgrades, software updates, and efficiency improvements.
    • Adaptability: Evidence that the infrastructure design allows for the integration of future technologies (e.g., quantum computing, advanced cooling) without requiring a complete rebuild.
    • Lifecycle Management: A documented strategy for managing the end-of-life of components and their replacement.

  4. Environmental and Regulatory Compliance Trajectories: As the EU tightens sustainability standards, a data centre must demonstrate long-term compliance. The proposal should evidence that the project will meet evolving EU environmental standards (such as those in the Energy Efficiency Directive and Delegated Regulation (EU) 2024/1364) for the entire predicted lifetime.

    • Sustainability Strategies: Long-term plans for waste heat recovery, renewable energy integration, and water efficiency.
    • Regulatory Alignment: Analysis of how the project aligns with future regulatory expectations, ensuring it does not face forced closure due to non-compliance.

The Commission's Discretion and the Risk of Withdrawal

The Commission determines the final duration of the designation based on the submitted evidence. This means the applicant bears the burden of proof. If the Commission finds the substantiation insufficient, unrealistic, or unsupported by the provided information, it may adjust the duration downward or reject the application entirely.

Crucially, Article 14(4) provides a safeguard for the Union against inaccurate claims. It states:

"Where the Commission finds that a project designated as a strategic project no longer fulfils the relevant criteria, or where its designation was based on an application containing incorrect information affecting compliance with those criteria, it may withdraw the designation of that project by means of a decision."

This clause underscores the importance of accuracy. Overstating the predicted lifetime to secure a longer period of strategic benefits (such as accelerated permitting or access to funding) constitutes "incorrect information affecting compliance." If the actual performance or lifespan of the project falls short of the substantiated claims, the Commission has the power to revoke the strategic status. This creates a significant compliance risk for applicants who inflate their projections.

Strategic Implications for the Application

When drafting the proposal under Article 14(2), which requires providing "all the necessary and relevant information to demonstrate that the project fulfils the relevant criteria," the predicted lifetime section is a foundational element. It defines the window of opportunity for the project to deliver on its strategic promises, such as addressing capacity shortages, integrating Union-designed hardware, or supporting public sector functions.

The substantiation must be robust enough to withstand scrutiny during the open call for expressions of interest. The Commission is looking for projects that offer long-term value to the Union's digital infrastructure. A short, speculative lifetime may suggest a lack of commitment or stability, whereas a well-substantiated, long-term plan demonstrates reliability and strategic alignment with the EU's goals for technological sovereignty and resilience.

What this means for you

For CTOs, architects, project managers, and SMEs evaluating the practical impact of CADA, this requirement shifts the burden of proof entirely onto the applicant. You cannot simply state a desired duration for strategic status; you must engineer your business case and technical design to support it.

Actionable Steps:

  1. Integrate Lifetime Analysis Early: Begin the substantiation process during the initial feasibility study, not just when drafting the final proposal. Engage financial analysts, structural engineers, and technical architects to align on a realistic, defensible operational lifespan.
  2. Document Everything: Maintain detailed records of equipment specifications, supplier warranties, maintenance contracts, and structural engineering reports. These documents serve as primary evidence for your predicted lifetime claims.
  3. Plan for Evolution: Ensure your upgrade roadmap is detailed and funded. Show how the data centre will adapt to technological changes without requiring a complete rebuild, thereby supporting a longer predicted lifetime.
  4. Align with Strategic Criteria: Ensure that the activities planned for each year of the predicted lifetime continue to meet the strategic criteria (e.g., supporting public sector functions, using innovative features, or addressing capacity shortages). A project that loses its strategic relevance halfway through its lifetime may face scrutiny.
  5. Prepare for Commission Review: Anticipate questions from the Commission regarding the realism of your projections. Be ready to provide third-party validations, expert opinions, or independent audits if necessary to bolster your case.
  6. Avoid Overstatement: Do not inflate the predicted lifetime to gain a longer designation period. The risk of withdrawal under Article 14(4) for providing "incorrect information" is a severe penalty that could negate all benefits of the designation.

Common misconceptions

Misconception 1: The Commission assigns a fixed duration to all strategic projects. No. Article 14(3) clearly states the duration is based on the predicted lifetime you provide. You propose the lifetime; the Commission validates it and sets the duration accordingly. There is no standard "10-year" or "20-year" rule.

Misconception 2: Predicted lifetime is the same as the construction timeline. No. The predicted lifetime refers to the operational lifespan of the data centre after it is built and commissioned. Construction timelines are separate and do not determine the duration of the strategic designation.

Misconception 3: Once designated, the status is permanent for the claimed period. No. Article 14(4) allows the Commission to withdraw the designation if the project no longer meets the criteria or if the initial application contained incorrect information. This includes inaccuracies regarding the predicted lifetime. If the project fails to operate for the substantiated period, the status can be revoked.

Misconception 4: Substantiation is optional if the project is technically high-quality. No. The requirement to include information necessary to substantiate the predicted lifetime is mandatory for all applicants under Article 14(3). High technical quality does not exempt you from providing evidence of long-term viability.

Related

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