Configuring Radar as an administrator

What it does

This page covers the technical Radar configuration tasks that only your Futuh instance administrator performs: active sources, scoring, cron, and notification distribution.

Before you start

• Role: Futuh instance administrator.
• Access to Settings → Technical and to the Radar menus in developer mode.
• Estimated time: 20–30 min for the full initial configuration.

Activating tracking sources

Radar v0.1 works with BDNS as its primary source. The integration with Funding & Tenders (EU) is provisioned but deferred.

1. Open Radar → Configuration → Connectors.
2. Verify that the BDNS connector is marked as active. Its nivel1 filter must include the values ESTADO, ESTATAL and AUTONOMICA (the API returns all three and omitting any one leaves calls out).
3. Check the F&T (EU) connector: by default it appears in being enabled status. Do not activate it until the SEDIA credential has been renewed in production. [VERIFY: cierre credencial SEDIA]

Deferred European programmes

While F&T is not operational, Horizon Europe, CERV, Erasmus+, FEDER, ESF+ and LIFE are not tracked. This is by design in phase 1: any attempt to act on these programmes must wait for phase 2.

Configuring the IATI and ODS vocabularies

Radar uses two canonical vocabularies that are synchronised from the Federación Futuh: the IATI catalogue (sectors and cooperation purposes) and the Sustainable Development Goals.

1. Open Radar → Configuration → Vocabularies.
2. Verify that the IATI sectors and ODS tables have entries (several hundred in the first, 17 in the second).
3. If they are empty, manually run the cron Futuh Federation: Daily canon hub pull from Settings → Technical → Scheduled Actions.
4. Return to the vocabularies screen and refresh to verify the load.

Adjusting scoring weights

The fit score combines two dimensions with default weights 60/40. If your organization wants to give more weight to evaluation criteria than to formal requirements, you can change them.

1. Open Settings → Radar → Fit Score.
2. Change the Requirements weight and Evaluation weight fields. The sum must equal 1.00.
3. Save and run a manual recalculation from the Recalculate fit score button so that the changes apply to the existing history.

Recalculation affects the full history

The recalculation processes all open calls (several hundred). On large instances it may take several minutes. Run it during low-load hours.

Configuring the daily cron

Radar tracks sources via two separate crons: a secondary one that enriches already-known calls, and a daily one that checks official publications.

1. Open Settings → Technical → Scheduled Actions.
2. Locate the cron Radar BDNS · Hourly enrichment (_cron_enrichment_bdns). Verify interval Every hour and Active.
3. Locate the cron Radar BDNS · Publication check (_cron_publication_check). Verify interval Every day and Active.
4. If you modify the intervals, do so during low-load hours: the hourly cron makes several hundred HTTP requests to BDNS and it is best to avoid clashes with backups.

Configuring the alert watcher

The watcher is the engine that checks which new calls match each alert configured in your organization. It relies on three models: radar.alerta (definition), radar.alerta.match (each match) and radar.alerta.template (registration templates).

1. Open Radar → My watchers (or My alerts, depending on UI version).
2. Verify that at least one active alert exists. If not, create one from a template.
3. Check the cron Radar Alerts · Hourly matching and Radar Alerts · Digest sending in Settings → Technical → Scheduled Actions.
4. Digest frequency is configured per alert (daily or weekly).

Configuring the email digest for operators

Each operator can choose whether to receive the digest only by email, only by internal notification (Discuss bell → Inbox), or through both channels.

1. Open Settings → Users & Companies → Users.
2. Select an operator.
3. In the Preferences tab, locate the Radar alerts delivery field. Options are Email, Odoo (internal bell) or Both (default value).
4. Save.

The field is per-user: each operator controls their preference without affecting the rest of the team.

Next steps

• Use Radar as an operator to understand what your users will see with this configuration.
• Send a call to Gestión de ayudas to review the cross-module flow.
• Configure the AI model if you want Silvio to understand questions about Radar.