Platform

Capabilities in depth

What each capability does, who uses it, how the workflow runs, and exactly what data it shows today.

Traffic intelligence

Trends, congestion and forecast planning

What it does

  • Hourly vehicle counts per camera with a 90-day history chart and CSV export.
  • Week-over-week comparison computed directly from stored counts.
  • Statistical 7-day forecast with 80% / 95% intervals, a seasonal baseline and a rolling backtest — not AI guesswork.
  • Reports “insufficient data” instead of guessing when history has gaps.

Who uses it

Traffic & mobility teams, analysts, executives

Traffic intelligence
Illustrative demo

Workflow

  1. Open Traffic and pick a camera or the whole network.
  2. Read the 90-day chart and week-over-week change.
  3. Check the forecast and its intervals before planning a closure or event.
  4. Export CSV for your own analysis.

Data, freshness & integration status

Freshness: hourly buckets. Gaps are shown as gaps, never filled in. Integration status: counts in the demo are synthetic; live counting requires connected cameras (planned).

Weather awareness

Connect weather data with street observations

What it does

  • Optional forecast provider per municipality (Open-Meteo supported, no API key required).
  • Forecasts, measured sensor readings and camera-visual indications are kept in separate, clearly labelled sections.
  • Shows “Not connected” until a provider is configured — nothing is invented.
  • Hourly refresh by the background job queue, with source and last-updated time on screen.

Who uses it

Command center, public works, executives

Weather awareness
Illustrative demo

Workflow

  1. A municipal admin selects the provider and approximate coordinates.
  2. The platform fetches the hourly forecast on schedule.
  3. Operators compare forecast rain with standing-water indications seen on camera.
  4. Daily briefings record which weather sources were used.

Data, freshness & integration status

Freshness: hourly forecast. Measured sensors: not connected (no supported sensors yet). Camera-visual indications: demo data in this build.

Road conditions

Track hazards, repairs and work orders

What it does

  • Hazard candidates are reviewed by a person before any work order is created.
  • One work order per hazard, with crew, due date and a timestamped update log.
  • A work order can only be closed with photo evidence attached (file type verified on upload).
  • Outstanding work appears in every daily briefing. Detections never certify a road as safe.

Who uses it

Roads & public works, command center

Road conditions
Illustrative demo

Workflow

  1. A hazard candidate appears from a reviewed event or a manual report.
  2. Public works confirms or dismisses it.
  3. Confirmed hazards become a work order with a crew and due date.
  4. The crew posts updates and closes the order with evidence.

Data, freshness & integration status

Freshness: immediate (records update when saved). Every step is written to the audit log.

Reviewed safety alerts

Evidence-linked events with human review

What it does

  • Each event links to the exact moment in the camera replay.
  • Operators confirm or dismiss with a note; an event can only be reviewed once.
  • Filters by status, type, camera and date range.
  • Event types are operational (stopped vehicle, queue build-up, standing water) — never about who a person is.

Who uses it

Command center operators, municipal admins

Reviewed safety alerts
Illustrative demo

Workflow

  1. New events land in the pending review queue.
  2. The operator opens the replay at the event moment.
  3. They confirm or dismiss with a note.
  4. Confirmed road events can become hazard candidates.

Data, freshness & integration status

Integration status: event detection on live feeds is planned; this build reviews events derived from synthetic demo footage.

Daily briefings

Bilingual reports, charts and history

What it does

  • Generated automatically at 06:00 local time; weekly on Mondays and monthly on the 1st.
  • Traffic, weather sources, reviewed events, road work and tower health — each figure cites its source table and time window.
  • PDF and CSV export, full history, retry and audited rerun; duplicates are prevented.
  • Delivered in-app with a notification — nothing is emailed or sent outside the platform.

Who uses it

Mayors & executives, analysts, auditors

Daily briefings
Illustrative demo

Workflow

  1. At 06:00 the scheduler queues yesterday’s report.
  2. The background job builds it from stored records.
  3. Readers get an in-app notification.
  4. Open, export PDF/CSV, or rerun if late data arrives.

Data, freshness & integration status

Missing data is listed explicitly in every report (for example, “Live camera feeds: not connected”).

Controlled livestreams

Approved views for offices and the public

What it does

  • Camera wall that loads only visible tiles, with reconnect and fullscreen.
  • Office viewers see only the cameras assigned to them.
  • Public views require an explicit publish action, masking confirmation, audio removed and a 30–600 s delay.
  • Revoke per stream, a municipality-wide kill switch, and fail-closed behaviour.

Who uses it

Command center, office viewers, municipal admins, the public

Controlled livestreams
Illustrative demo

Workflow

  1. An admin chooses an approved view.
  2. They confirm masking, audio removal and authorization, and set a delay.
  3. The public page shows the view only after the delay has passed.
  4. Revoke it, or hit the kill switch, at any time.

Data, freshness & integration status

Integration status: live camera feeds require the media gateway (planned). This build streams synthetic demo footage only.

Module tour

All modules

Towers & health

Map of tower sites with daily health status (online / degraded / offline) and uptime. Power, battery and solar telemetry are shown as “not connected” until a supported controller is installed.

Camera wall

Grid and single-camera views with a replay timeline and seek-to-event buttons. Muted autoplay, lazy loading and automatic reconnect.

Search

Search permitted cameras by time window (max 31 days), vehicle type, colour, direction and scene. No person, face or plate attributes exist to search. Every search is audited.

Work orders

Hazard review, crews, due dates, updates and evidence-required closure.

Missing-person case workspace

For authorized case reviewers only: case number, purpose, time window, area and non-biometric descriptors. Returns candidate clips for human review. Biometric terms are rejected.

Reports

Daily, weekly and monthly reports plus custom TrakAI reports, with PDF/CSV export and full history.

Public portal

Anonymous page with approved, delayed, audio-free views; kill switch and revoke; fails closed.

Roles & permissions

Eleven roles, explicit permissions

Roles and permissions
RoleOverviewAll camerasAssigned camerasTowersTrafficWeatherEvent reviewWork ordersSearchCasesReportsPublish publicAudit logUsersPlatform settings
Platform Super Admin●●·●●●●●●·●●●●●
Municipal/Tenant Admin●●·●●●●●●·●●●●·
Mayor/Executive●●·●●●····●····
Command Center Operator●●·●·●●·●······
Traffic/Mobility●●··●●·········
Roads/Public Works●●···●·●·······
Authorized Missing-Person Case Reviewer·●·······●·····
Analyst●···●●··●·●····
Auditor··········●·●··
Restricted Office Viewer··●············
Public Portal Demo Viewer···············
Client manager●●·●·●····●····
Client user●●·●·●·········
Monitoring team●●·●·●●·●······
Partner admin●●·●·●··●·●····
Partner technician●●·●·●··●······

Generated from the platform’s live permission table. Case access is limited to authorized case reviewers — not even platform super admins have it. Everyone can view approved public streams.