Role 5 / 5 · time horizon: days–weeks

Strategic Commander

"Set priorities. Allocate watch resources. Brief leadership."

Persona

Komentaja Mirka Lahtinen

Maritime Operations Command · Suomenlinna HQ · 17 years in service

Mirka runs the joint maritime watch cell. Her job is not to read every AIS track — she has a watch room for that — but to decide where the watch room's attention should be next Tuesday. She lives in a Power BI executive workspace with three composite-score timecharts, a map of detector coverage, and a Data Agent prompt box. Her morning ritual is the overnight digest; her weekly ritual is the posture brief to the Border Guard director.

She is allergic to dashboards that need explaining. If a chart needs three paragraphs to interpret, she will ask the Intelligence Analyst to bake the interpretation into a written narrative and just send her the deltas.

⚠ synthetic persona

Daily workflow

06:00Pulls the overnight incident digest in Power BI — a single tile per active scenario family with composite-score and any threshold breaches.
08:15Stand-up with Watch Operator leads. Reviews any tickets escalated overnight and any rules that fired more than three times.
10:00Asks the Data Agent: "Which infrastructure corridors had the most loitering events this month, and where is sensor coverage thinnest?"
13:30Reviews Intelligence Analyst's proposed rule-weight changes. Approves or returns with questions before they ship to production Activator.
16:00Drafts the weekly posture brief slide — Power BI export to PPTX — for the director. Sensor allocation map + composite trend deltas.
21:30Phone push from Activator on any threshold-breach incident that the duty watch has not closed within 30 min. Decides whether to wake the on-call deputy.

Key data products

Data product	Source scenario(s)	Fabric tool	Refresh cadence
Daily situation brief Composite scores per active scenario family, threshold breaches, top 5 incidents	S6 (flagship)	`Power BI` executive workspace	hourly
Trend deltas (week-over-week) Loitering events, dark-window minutes, novel-MAC rate	S3 + S6 historical	`Lakehouse` SQL endpoint + PBI	daily
Sensor & watch-team allocation map Where coverage is densest vs where incidents are clustering	all	`Power BI` map visual	daily
Strategic Q&A (free-form) Natural-language questions against the full fused store	all	`Fabric Data Agent`	on-demand
Director's weekly brief pack PPTX bundle + Loop page link	S6 + cross-scenario	`Power BI export` + Loop	weekly (Fri 14:00 EET)

Linked scenarios

S6 — Multi-Stage Combo The flagship five-stage incident What this role sees: a single composite score tile that broke the 0.70 threshold at 09:42 UTC — drill-through opens the staged narrative. S3 — Loitering Over Critical Infrastructure Two-hour figure-eight over BalticConnector What this role sees: a loitering-events-per-corridor monthly trend — S3 dominates the BalticConnector slice this quarter. S1 — AIS Dark Near Cable 33-min silence over the Estlink alignment What this role sees: dark-window minutes per cable per week — used to argue for two more coastal MAC sensors east of Porvoo.

Fabric tools used

Power BI executive workspace Fabric Data Agent Lakehouse SQL endpoint Microsoft Loop (brief pack) Activator (push alerts)

Example Data Agent prompts

Which infrastructure corridors had the most loitering events this month, and where is sensor coverage thinnest?
Compare this week's composite-score distribution against the previous four weeks — what changed?
Summarise the three incidents in S6 that contributed most to last month's threshold breaches.

Dashboard mockup

Commander · Daily situation brief · 2025-10-15 06:00 EET