↓
Intelligent Software, New User Vision & Integrated Systems

Compete 2030 — Technical FAQ

1. Validation and Technical Strategy
#

What makes a software or R&D project eligible for Compete 2030?
#

The project must solve a scientific or technical uncertainty that cannot be resolved by an experienced engineer using common tools. It is assessed using the Frascati Manual criteria: novelty, creativity, uncertainty, systematic approach, and reproducibility. A standard CRM or e-commerce project is not eligible.

What is the difference between “Productive Innovation” and “Business R&D”?
#

Productive Innovation supports the purchase of existing technology to increase company capacity (e.g., servers, ERP licenses). Business R&D supports the creation of new technology or knowledge that does not yet exist on the market, covering mainly internal engineering and research hours.

How do I validate alignment with Compete 2030 objectives?
#

Check whether the project contributes to strategic priorities such as digitalisation, decarbonisation, circular economy, or SME competitiveness. Review the specific call notice and eligibility criteria, and ensure the project delivers measurable impact (e.g., productivity gains, emission reductions, innovation in product/process).

2. Architecture and Technical Specification
#

What level of detail is required in the technical specification?
#

The specification must be detailed enough to allow assessment of innovation and feasibility. It should include:

  • System architecture and module mapping (e.g., UML, microservices)
  • Technology stack and security/scalability justifications
  • Functional and non-functional requirements (performance, interoperability)
  • Integration plan with existing systems (ERP, CRM, IoT)
  • Test and validation plan

Are Cloud (AWS, Azure) or DevOps licensing costs eligible?
#

Yes, if they are directly allocated to the development, testing, and prototyping environment during the project execution period. Production environment costs are considered operational and are not eligible.

Which technical standards are commonly required?
#

Depending on the sector: ISO/IEC 27001 (information security), ISO 9001 (quality), ISO 50001 (energy management), ISO 14001 (environmental), CE marking for equipment, and sector-specific regulations.

3. Technical Implementation (Development)
#

How should engineering timesheets be controlled?
#

Each team member allocated to the project must record monthly timesheets specifying the technical task performed (e.g., AI algorithm refactoring, REST API development). Tasks must match the approved project milestones and work packages.

Are Low-Code / No-Code platforms accepted?
#

Rarely in pure R&D projects, because low-code reduces technical uncertainty. They may be eligible in Productive Innovation or Digital Transition projects focused on speed of implementation and productivity gains.

What technical reports are mandatory during execution?
#

Progress reports must demonstrate physical and financial execution, including:

  • State of advancement against the schedule
  • Compliance with achievement indicators
  • Justification of deviations and corrective actions

4. Monitoring and Regulatory Defence
#

How do I manage technical deviations or stack changes?
#

Any structural change requires a Change Request (PA) submitted through the Balcão dos Fundos. The change must be technically justified, proving that the final objective and innovation level are maintained or improved.

What happens if a technical milestone fails or is delayed?
#

The delay must be reported in the progress report. If the company proves the failure was due to an unpredictable technical uncertainty inherent to R&D and documents resolution attempts, the project is not cancelled, but the payment schedule may be adjusted.

How do I prepare for an audit or regulatory defence?
#

Keep all technical and financial documentation organised and accessible from the start. Maintain the original technical annex, approved change requests, invoices with technical specifications, progress reports, and evidence of communication rules compliance.

5. Technology Audit Dossier
#

What constitutes a Technology Audit Dossier?
#

The dossier is the set of evidence proving project execution. It should include:

  • Invoices and payment receipts for all investments
  • Technical manuals and source-code repositories (dated commits)
  • Test and validation reports (load, security, QA)
  • Patents or prototypes, if applicable
  • Evidence of compliance with communication rules (logos, mentions, publications)

How do auditors cross-check financial and technical audits?
#

Auditors verify that paid invoices match technical deliveries. For example, if there is an invoice from a senior security consultant, the technical dossier must contain the vulnerability report or encryption code signed by that consultant on the corresponding dates.

Official Sources
#

isnuvis
© 2026