Home/ User Guide/ Operator guide/ Field operations & registries

06 — Field operations & registries

The Operazioni di campo menu holds the master data behind everything else: your field assets (hardware) and their maintenance, the operational registry of agencies and responders (the firekeeper/agency data the dispatch simulator uses), the incident registry of real fires, and the historical intervention record.

Access note. Most operators have read access here; creating and editing records (incidents, field assets, maintenance) is generally admin-only. CBA cases are an exception — operators can build them, only approval is admin-only (see 07).


Field assets — /field-asset/index

The unified registry of every piece of owned hardware in one place — IoT sensors, LoRaWAN gateways, drones, thermal cameras, telecom radios, vehicles and generic equipment. It's the successor to the older technology/equipment registries.

What you read here

  • A grid of all assets: Type (taxonomy icon, filterable), alias, serial, latitude/longitude, Owner (the operational agency), deployment state (active / test / decommissioned) and a photo count. Type shortcuts (Drones, Thermal cameras…) appear under the menu entry.
  • Open a row for Details / Photos / Maintenance tabs.

Two kinds of row — important. Some assets are backed by a dedicated module: IoT sensors, gateways and legacy technology are shown here but edited on their own page ("Open in original module" / Edit jumps there). The satellite-less types (drones, thermal cameras, radios, vehicles, generic) are edited here. This preserves the single-source-of-truth contract.

Creating/editing (admin): pick the type, alias and serial, set the location on a map (click/drag a marker — altitude auto-fills from the terrain model), choose the owner agency and deployment state. Soft-deleting keeps the asset's maintenance history and assignments.


Asset maintenance — /field-asset-maintenance-event/index

Maintenance events for any field asset (the richer replacement for the old maintenance module).

What you read here

  • A grid of events: Asset, event type, severity (info / warning / critical), start/end, next due, State (closed / OVERDUE / in progress), downtime hours and parts cost. An "Overdue only" toggle helps you find what's slipping.

Logging an event (admin): choose the asset and event type (preventive, corrective, inspection, calibration, firmware update, part swap, decommission), set severity, fill the timeline (leave end empty while in progress), and work through a checklist seeded from the asset type's template. You can attach images/PDFs (≤ 8 MB). Complete an event to stamp its end time.

Plan ahead

  • Calendar (/field-asset-maintenance-event/calendar) — a month/week/list view colour-coded by severity, with overdue events in bold.
  • Suggest plan — proposes the next preventive dates from each asset type's interval, stepped from the last completed preventive; tick the ones you want and Create selected (it de-duplicates near-identical dates).

Operational registry — /operational-registry/index

The master data of responders — agencies, their sites, vehicles, teams and contacts. This is the data the firekeeper/agency dispatch simulator ranks and routes (05 — Interventions ⭐). Keeping it accurate and geocoded is what makes the dispatch flow trustworthy.

It's one screen with an entity tab picker; create/edit/delete within each:

EntityWhat it isKey fields
AgenciesThe organisation itselfname, country (IT/SI), region, agency type (civil protection, regional civil protection, municipality, volunteer/professional fire brigade, forest service, firefighters' union, other), contacts, logo, HQ photo
SitesAn agency's physical locations (the points on the map)site name, site type (regional HQ, municipal CP, fire station, forest station, depot, command room, water point…), address, latitude/longitude, geocode status, operational status (active/inactive/seasonal), visibility
AssetsVehicles & equipmentcategory (vehicle, pump, generator, water tank, drone, radio…), quantity, wildfire-capable, off-road (4×4), water capacity, pump rate, crew capacity, width/length/height, min road width, status
TeamsCrews (incl. firekeeper squads)team name, team type (municipal PC, AIB forest-fire squad, fire volunteer/professional, forest service, civil-protection staff, first aid, technical rescue, hazmat…), volunteer & operative counts
ContactsPeople to reachwith a privacy class and an "emergency use" flag
SourcesProvenance of each recordthe dataset/source a row came from
Quality issuesA data-quality audit workflowopen / in-review / closed / waived, by severity
Social profiles (new)An agency's official social pagesplatform, page URL, verified official (a human decision), monitoring on/off — see below

Why this matters for dispatch. A responder only appears in the intervention ranking if it has an agency and an active, geocoded site (with coordinates). Its vehicles' wildfire/off-road flags, water and width, and its teams' crew counts, drive the score, the vehicle picker and the forest-road width caution. The AIB team type is how "firekeeper squads" are represented. The quality-issues workflow (plus the created/updated timestamps and source on every row) is the persistent audit of your responder data — the live dispatch panel itself is not saved.

Agency detail shows the logo, type, region/country, official URL, HQ photo, direct contacts, referents/volunteers, a map of the agency's sites and — where registered — its official social profiles.

Official social profiles (new, August 2026)

An agency's official pages can be registered so the cockpit can watch them for incident posts. Two switches govern each page, and both are deliberate human acts:

  • Verified official — you confirm the page really belongs to this agency. Unverified pages are never read.
  • Monitoring — turn the hourly check on for that page.

When both are on, new incident-related posts are proposed into the media review queue as social references — the link and its metadata only, never the file. Only official pages of registry agencies are ever read, only through the platform's approved interface, and there is no scraping fallback: a deployment without approved access simply reports the platform as unconfigured. Reviewing and attaching those proposals is covered in 11 — Media & sources ⭐.

If you cannot see the tab, the feature's table is not installed on this deployment (administrator task).

Not the same as the admin Organisations or Locations lists in 08 — Administration — those are general partner/geo reference data; this is the operational responder model.


Incidents — /incident/index

The wildfire incident registry — the canonical record of each fire event: where, when, the cause, vegetation, weather, burned-area damage, and the response (personnel and equipment). It's the foundation for statistics, historical replay and authority reporting.

The list opens with three statistics widgets (wildfires by year, burned area by country, current-year vs historical) above a grid filterable by status, country and location. Operators can read incidents and the charts; creating and editing is admin.

Last updated (new, September 2026) — a sortable column between Area (ha) and Location. It is the most recent of six things that can happen to a fire: the record was edited · a media item (photo, video, article, satellite product) was linked · the narrative / enrichment was written or reviewed · a model run was attached · a hazard event (satellite detection, warning) was linked · a dispatch was recorded. The cell shows a relative time ("2 days ago") with a small icon for the kind of change; hover for the exact instant and the source that won ("media added", "narrative / enrichment updated", …). Click the header to sort newest first — the quickest way to see which fires gained new information since you last looked — or again for the oldest, which surfaces incidents nobody has touched.

The incident form adapts to your country (Italy or Slovenia variants) and is organised into tabs: Overview · Location · Timeline · Fire characteristics · Damage & area · Cause & legal · Personnel & equipment.

  • The Overview tab is a useful dashboard: burned-ha and duration KPIs, a hazard-zone flag, a missing-required checklist (year, fire start, code, cause, country, municipality) and a six-event timeline (fire start → report → intervention start → extinguishing → fire end → intervention end) with duration KPIs.
  • Location has a map — click/drag the marker to set coordinates (reverse-geocoded), with municipality autocomplete for IT/SI.
  • Damage & area captures burned area split by forest/non-forest/pasture, estimated damage, destroyed wood mass, etc.; Personnel & equipment records who and what responded (down to vehicle/aircraft/retardant breakdowns).
  • A "Show enrichment fields" toggle reveals the fuller Slovenian taxonomy (forest-management units, land cover, terrain, burned-forest composition, fire-type percentages) for cross-border completeness.

Export the incident to Excel in four variants (IT/SLO × default/enriched).

Media & sources (new, August 2026) — the incident list now carries a Media column (chips per class: video, images, audio, publications, satellite products, social) and a Models badge with the number of simulation runs linked to that fire. Clicking the chips opens the Media & sources workspace (/incident/media?id=…) where photos, videos, articles and official posts are reviewed and attached. Media are filed against a fire episode, so one article covers every municipality incident of the same fire — the full workflow is 11 — Media & sources ⭐.

Incident-report assistant (admin): from an incident, Incident report opens a country-templated wizard that autofills fields from the incident (tracking each value's source as portal/manual/AI), runs pre-export validation (missing-required and consistency checks like "fire end before fire start"), supports optional human-approved AI assist (draft narrative, cause description, species summary, consistency check), and exports PDF / DOCX / HTML / CSV. From an incident you can also Create a CBA case (see 07 — Analysis → Cost-benefit analysis).


Historical intervention record — /intervention/index

This is the post-fire record, not the live dispatch simulator. For simulating who responds to a simulated fire, see 05 — Interventions ⭐.

The historical intervention is the persisted record of a real suppression effort attached to an incident: start/end of the intervention, suppression method, number of sitreps, bonification, water usage and durations. It is filled as part of the incident workflow and is the durable, auditable account of what actually happened on the ground — the counterpart to the ephemeral planning simulation.