Sessió informativa licitació del SDA de solucions d’IA de suport a la contractació pública

Introduction to the Session

Language Preference and Recording Notice

• The session will be conducted in Spanish unless there is a preference for Catalan from attendees.

• A recording of the session is being made for those unable to attend live.

Overview of the Dynamic Acquisition System

Purpose of the Session

• The primary aim is to explain how the dynamic acquisition system works, particularly regarding offer submissions. Questions can be addressed during or after the presentation.

• Attendees are encouraged to submit questions in writing if they cannot be answered during the session. Responses will be published later on the contracting profile.

Key Features of the Dynamic Acquisition System

Application Process

• A 30-day initial period has been established for companies to submit applications for admission into the dynamic acquisition system. This allows for an initial selection of companies eligible for participation.

• Companies can apply at any time throughout the validity period of the system, which remains open continuously.

Contracting Invitations

• Municipalities will invite companies currently within the system whenever they issue specific contract tenders based on it. Applications submitted during this period must be resolved before any contracts can be called.

Categories and Technical Requirements

Structure of Categories

• The dynamic acquisition system is divided into four categories based on different stages: preparation, bidding, execution, and support services that may span multiple categories. Detailed explanations will follow regarding how offers should be presented according to these categories.

Solvency Criteria

• Specific technical and economic solvency requirements have been set lower than usual to facilitate access for small businesses and startups while ensuring minimum standards are met before application approval can occur. Each category requires independent solvency verification rather than cumulative totals across all categories (e.g., €100,000 per category).

Objectives and Requirements

Goals of Dynamic Acquisition System

• One key objective is not only to simplify municipal acquisitions but also to rationalize them by ensuring that AI systems used meet functional and security requirements before procurement processes begin (e.g., avoiding minor contracts or pilot tests).

Admission Requirements

• Companies seeking admission must demonstrate both their economic/technical capacity as well as compliance with specified functional requirements related to their AI solutions (including subscription proposals detailing duration and pricing). Although subscription prices won't affect evaluation criteria, they provide municipalities with necessary budgetary information when issuing specific contracts or tenders.

Indications for General Use AI Model in Solutions

Requirements for AI Solutions

• Clear indication of the type of general-use artificial intelligence model being offered, such as whether it utilizes GPT or cloud technology.

• This information must be provided to ensure transparency and compliance with technical requirements.

Documentation and Compliance

• Necessary documentation must be submitted to verify compliance with technical and security requirements, particularly if a medium-level compliance is requested.

• If the solution includes services from multiple categories, clarity on whether subscriptions can be made individually or collectively is required.

Subscription Details

• Information regarding subscription modalities and pricing should be included.

• Companies need to specify the maximum duration of their subscription, including any potential extensions.

Service Provision Operations

Implementation Timeline

• Details on when the municipality will have the solution implemented are necessary.

• Procedures for user onboarding and offboarding, as well as profile modifications, must also be outlined.

Access Requests

• All operational details related to service provision should be included in the system; however, these aspects will not be subject to evaluation.

• Applications lacking complete information will be rejected, preventing access to the dynamic acquisition system.

Reapplication Process for Access

Dynamic Acquisition System Access

• Companies whose applications are rejected may reapply for access as many times as needed until approval is granted.

Submission Guidelines Overview

Offer Presentation Instructions

• A quick overview of how companies should present their offers will follow; other questions will be addressed later during Q&A sessions.

Technical Specifications Document

Example Inclusion

• An example has been included in the technical specifications document detailing how access requests should be presented.

Categories of AI Solutions

Functionalities Offered by AI Solutions

• Various public procurement support solutions exist that provide multiple services categorized accordingly.

Specific Service Examples

• For instance, a solution might assist in drafting technical specifications (Category 1), while also supporting bid evaluations (Category 2).

Contracting Services Together or Separately

Joint vs Individual Contracting

• If an AI solution requires joint contracting for its functionalities (e.g., drafting specifications and evaluating bids), it cannot offer these separately.

Category Inclusion Criteria

• The company must include its offer under Category 4 if it provides services from two or more categories but can list them individually if they are available separately.

Categorization of Services Offered

Detailed Categorization

• Category 1: Drafting technical specifications support.

• Category 2: Bid evaluation support.

• Category 4: Solutions offering services across multiple categories.

Individualized Contracting Options

• If a company allows both individual and joint contracting options, each service must clearly fall within its respective category.

Implications of Service Offerings

Market Competition Dynamics

• Companies may label their offerings as individualized even if practical limitations prevent users from accessing only one service at a time.

Client Needs Consideration

• Municipalities may choose only specific services based on their needs without being forced into unnecessary contracts.

Overview of Technical and Administrative Specifications

Availability of Documentation

• The technical specifications and administrative clauses are available in both Catalan and Spanish versions.

• Participants are encouraged to refer to these documents for detailed information regarding the project.

Question and Answer Session

• A warning is issued that questions requiring clarification on the specifications will be addressed through formal channels, ensuring transparency.

• Responses published in the contractor profile are binding for the contracting authority, emphasizing their importance.

Clarification on Technical Solvency

Understanding Technical Solvency

• Ricard Ferrer from Anuncis raises a question about technical solvency requirements for multiple categories.

• It is clarified that if a company meets the solvency criteria exceeding €70,000, it can apply across all four categories without needing separate proofs for each category.

Economic vs Technical Solvency

• Both economic and technical solvencies are not cumulative; each category requires independent proof of financial capability based on specified thresholds (e.g., €100,000).

• Companies can reuse certifications across different lots as long as they meet individual lot requirements without summing them up.

Dynamic Acquisition System Features

Flexibility in Offerings

• The dynamic acquisition system allows companies to modify their offerings annually based on new functionalities introduced during the contract period.

• This flexibility ensures that businesses can adapt their portfolios according to evolving needs or technological advancements within five years of contract execution.

Modification Opportunities

• Contracting authorities also have the ability to adjust categories or introduce new functionalities as needed throughout the contract duration.

Submission Guidelines for Categories

Presenting Solutions Across Categories

• Companies may submit solutions that span multiple categories; however, they must ensure alignment with specific functional requirements outlined in each category's description.

Invitation Process Based on Functionalities

• If a solution includes functionalities from different categories, invitations will only be extended to companies qualified under those specific categories relevant to requested services.

Documentation Requirements and Validation Process

Technical Memory Limitations

• Questions arise regarding any limitations on the length or format of technical documentation submissions; it is suggested there should be no strict limits but rather common sense applied by participants when preparing submissions.

Information Sharing Post-validation

• The initial submission process primarily serves validation purposes; however, some information may later become accessible to municipalities seeking candidates for contracts based on validated data provided by companies.

Final Remarks

Anonymity in Queries

• All questions submitted via the contractor profile remain anonymous once responses are published, ensuring confidentiality for participants asking questions during this process.

• Emphasis is placed on timely responses being made available through official channels post-query submission.

Timeline Considerations

• Participants are reminded that while there’s an initial classification period of 30 days for companies entering the system, subsequent applications can occur without urgency after this period has concluded.