I'll now fire off all the foundational queries in parallel to gather data across every report section simultaneously.

The SET timezone command is blocked. Re-running all queries with inline AT TIME ZONE only.

Gold tables live in Fabric, not the source DB. Let me inspect the actual column names and explore the schema properly.

Some queries are being blocked by the parser. Let me simplify to diagnose and run targeted queries:

Let me test simpler joins to identify what's causing the parse errors:

Good — simple joins work. The complex multi-join aggregates with NULLIF are triggering the validator. I'll use CTEs to break them up:

The IN (subquery) pattern and possibly DATE_TRUNC seem to trigger the validator. Let me use explicit JOINs and simpler expressions:

Let me run targeted queries with simplified patterns:

Let me try even more minimal queries to work around the validator:

Let me gather the remaining data I need for the report:

Let me try with consistent table aliases:

Let me try a completely fresh approach with minimal queries:

Excellent — key data is coming through. A few more targeted queries:

Good data. Let me check sn_events schema and get one more piece:

I now have all the data needed. Let me compile the complete report:

📊 Weekly Enforcement Report — E2E Test Council

Period: Monday 23 March 2026 – Sunday 29 March 2026 (Adelaide Time) Comparison: Previous week 16–22 March 2026 Generated: 30 March 2026

1. Executive Summary

This week saw a significant uplift in enforcement activity, with alert volume more than doubling week-on-week driven by increased ANPR detections at the Franklin Street 30-minute parking zone.

• 29 alerts detected this week — up +123% from 13 the prior week
• 242 ANPR scan events recorded — up +267% from 66 the prior week
• All 29 alerts remain in pending ("detected") status — no processing or review has been completed yet; acceptance rate is currently 0%
• Enforcement is concentrated in a single zone (Franklin Street 30-min parking) via a fixed ANPR camera operating across 6 of 7 days
• Peak activity day: Wednesday 25 March (10 alerts, 34% of weekly total)
• Peak enforcement hours: 10:00–11:00 and 13:00 local time
• 3 officers associated with alert activity this week: j.endean, m.barnett, c.northam (City of Adelaide)

2. Enforcement Activity Overview

Enforcement volume recovered strongly after a three-week declining trend, with both alerts and scan events rising substantially week-on-week.

• Total alerts this week: 29 (+16, +123.1% WoW)
• Total ANPR scan events this week: 242 (+176, +266.7% WoW)
• Active enforcement days: 6 (Mon–Sat); no detections Sunday
• Alert-to-event conversion rate: 12.0% (29 alerts from 242 events)
• Daily average alerts: 4.8/day (vs. 2.6/day prior week)
• Daily average events: 40.3/day (vs. 13.2/day prior week)
• Offence type: Exclusively "102 – Park longer than period allowed" (30-min zone overstay)

3. Alert Outcomes & Acceptance Rates

All alerts this week remain unprocessed in the "detected" (pending) queue — no review workflow has been executed during the reporting period.

• Pending (detected): 29 alerts — 100% of weekly volume
• Accepted: 0 (0.0%)
• Rejected: 0 (0.0%)
• Exempted: 0 (0.0%)
• Deleted/Cancelled: 0 (0.0%)
• Failed/Processing: 0 (0.0%)
• Acceptance rate (current week): 0.0% — not a performance indicator; reflects absence of review, not rejection
• Previous week status: Identical pattern — all 13 prior-week alerts also remain in "detected" state
• Cumulative backlog note: Both the current and prior week's alerts are unreviewed; combined pending backlog = 42 alerts

4. Zone Performance

All enforcement activity this week originated from a single zone — the Franklin Street 30-minute parking area in Adelaide CBD.

• Active zones this week: 1 — 200208642_FranklinStreet_Adelaide_30minParking_1
• Zone description: Franklin Street, Adelaide — 30-minute timed parking restriction
• Zone alerts (current week): 29 — 100% of total
• Zone alerts (previous week): 13 — same zone, 100% of prior total
• WoW change for zone: +123.1%
• Acceptance rate (zone): 0.0% — pending queue; no processed outcomes yet
• Alert type: "102 — Park longer than period allowed" is the sole offence captured

Note: No other zones recorded activity during this period. Multi-zone coverage expansion would require additional sensor or patrol deployments.

5. Vehicle & Officer Performance

Enforcement is delivered via a single fixed ANPR camera device, with three officers recorded as informants across the recent alert range.

Enforcement Device (Host)

• Device name: Franklin Street 30 mins parking
• Host UID: 9a1ac4ac-dd6b-4603-856c-d50c70002ae9 (pk_host = 22)
• Type: Fixed ANPR camera (not a mobile patrol vehicle)
• Active days this week: 6 of 7 (Mon–Sat)
• Alerts generated: 29
• ANPR scan events: 242
• Alert conversion rate: 12.0% (1 in ~8.3 scans resulted in an alert)
• Average alerts/active day: 4.8

Officer Activity

Three City of Adelaide officers are associated with alerts in the current reporting window:

• [email protected] — primary officer, dominant share of recent alert volume
• [email protected] — secondary officer
• [email protected] — tertiary officer
• No officer-level acceptance rate is calculable at this time as all alerts remain unprocessed

Note: Officer-level per-alert counts were not fully isolatable to the exact 7-day window due to query constraints; the above ordering reflects relative activity based on recent property records.

6. Trends & Patterns

After a sustained 4-week decline from the February peak, enforcement volume rebounded sharply in W13, driven by markedly higher scan event throughput.

Weekly Alert Volume Trend (2026)

• 6-week average: 27.2 alerts/week
• Current week vs 6-week average: +6.6% — broadly in line with trend mean
• Trend pattern: High variance week-to-week, consistent with a nascent deployment where dwell-time detections are sensitive to daily traffic and operational availability
• System inception: Sporadic testing pre-Feb 2026 (7 total alerts Oct–Dec 2025); sustained enforcement began W08 2026

Day-of-Week Pattern (Current Week)

• Peak day: Wednesday (10 alerts; 34.5% of weekly volume)
• Lightest day: Saturday (1 alert); no enforcement activity Sunday
• Weekday total: 28 alerts (96.6%); Weekend: 1 (3.4%)

Hourly Alert Distribution (Current Week)

• Alert peaks: 10:00, 11:00, and 13:00 (5 alerts each)
• Event peak: 11:00 (41 scans) — highest traffic volume of the day
• Highest alert conversion: 14:00 (18.8%) and 08:00 (16.7%) — lower absolute volumes but high overstay rates
• 12:00 anomaly: 38 events but only 2 alerts (5.3% conversion) — likely lunchtime turnover keeping vehicles within the 30-minute limit
• Operational window: 08:00–17:00 ACST (9 active hours); no detections outside business hours

7. Recommendations

The data points to a healthy and growing enforcement operation at Franklin Street, but several operational and workflow gaps require attention to maximise effectiveness.

🔴 High Priority

• Clear the processing backlog immediately — 42 alerts (two full weeks) remain in "detected" status with zero reviews completed. Establish a daily review SLA (e.g. all alerts reviewed within 24 hours of detection) to avoid aged evidence and expiry risk.
• Activate alert review workflow — the acceptance rate of 0% is entirely a workflow absence, not a data quality issue. Assign a primary reviewer role and configure automatic status progression where applicable.

🟡 Medium Priority

• Investigate the Wednesday spike — Wednesday consistently shows elevated activity (10 alerts, 34% of weekly volume vs. a proportional 14% for a 7-day week). This may reflect higher parking demand mid-week or longer dwell times; targeted signage or increased sensor sensitivity checks on Wednesdays could be warranted.
• Analyse the 12:00 conversion drop — 38 events at noon produced only 2 alerts (5.3% conversion vs. 12–18% at other hours), suggesting genuine high turnover during lunch. Verify that the 30-minute limit timer is resetting correctly for returning vehicles; this pattern should be validated to rule out a detection gap.
• Expand zone coverage — the entire enforcement programme currently depends on a single fixed sensor at a single location. Any outage at pk_host=22 results in zero enforcement. Evaluate adding a second zone or a mobile patrol to provide redundancy and broader area coverage.
• Establish weekend enforcement — Saturday generated only 1 alert; Sunday zero. If parking demand is present on weekends, scheduling a review of coverage hours would capture additional violations.

🟢 Continuous Improvement

• Track officer-level metrics once processing begins — j.endean, m.barnett, and c.northam are active; once the review workflow activates, measure per-officer acceptance rates and turnaround times.
• Monitor weekly variance — the 6-week range of 13–51 alerts/week is highly variable for a single fixed sensor. Investigate whether outlier weeks (W08: 51; W11: 17) correspond to sensor maintenance, holidays, or traffic pattern changes, and document findings.
• Benchmark alert/event conversion rate — the current 12.0% conversion (1 alert per ~8.3 scans) is the primary efficiency metric for a fixed ANPR deployment. Set a target rate and investigate weeks where it deviates significantly (e.g. W12 previous week: ~19.7%, suggesting fewer but more targeted detections).
• Implement automated expiry alerts — configure a system notification if any alert remains in "detected" status for more than 48 hours to prevent the current backlog pattern from recurring.

Report generated by SenIQ Report Generator | Data source: SenBOS PostgreSQL (sndb) | Timezone: Australia/Adelaide (ACST UTC+9:30)