IVA Activity & Response Report
Security performance dashboard built from TrackTik report IDs, DSG/TrackTik exports, Get It Done data, and incident / emergency / maintenance reports.
Executive Signal
- Peak perimeter activity: Feb-26 with 1,448 people cleared.
- Peak Get It Done load: Feb-26 with 214 tickets.
- Peak incident / ER / maintenance month: Feb-26 with 164 reports.
- Top incident category: Maintenance Report (637 reports).
Evidence Model
Figures are backed by downloadable source exports and a TrackTik report ID evidence index. The API confirms report metadata; answer-level fields come from the DSG/TrackTik workbook exports.
Ownership Question: Why Don’t Some People Move Immediately?
Strong answer: the current export proves volume, timing, and outcomes, but it does not reliably code motive. We should not pretend it does. The original TrackTik narratives show repeat patterns worth adding to the operating story.
1. Resident / guest ambiguity
Some contacts involve people who state they are residents or guests. That creates hesitation because guards need to avoid over-enforcement while still clearing restricted perimeter areas.
2. Short-delay compliance
Several reports show people leave after a second prompt, after waiting for a ride, or after the guard remains present. The issue is often delay, not refusal.
3. True non-compliance / impairment
Incident samples include intoxication, noise, fighting, police/fire response, and other behavior where a normal verbal request may not work. These should be separated from basic loitering clears.
Recommended dashboard improvement: add a new “First Contact Outcome” chart once the RGT form captures one extra dropdown: Moved immediately / delayed compliance / claimed resident or guest / refused / escalated to onsite or PD / unknown. That will answer ownership’s question directly instead of guessing from narrative text.
Loitering Removals by Month
Loitering by Day
Ordered Monday → Sunday. Values are people cleared, not report count.
Get It Done Tickets by Month
Top GID Types
| Type | Count |
|---|---|
| Encampment | 866 |
Incident / ER / Maintenance Reports
Top Categories
| Category | Count |
|---|---|
| Maintenance Report | 637 |
| Trespass / Transient or Homeless Individual Onsite | 270 |
| Emergency / Medical | 253 |
| Alarms / Police or Ambulance Response | 250 |
| Disturbance / Other | 186 |
| Access Control / Other | 103 |
| Disturbance / Fighting | 88 |
| Noise Complaint | 76 |
| Disturbance / Loitering | 61 |
| Disturbance / Damage to Property or Vandalism | 58 |
| Disturbance / Suspicious Activity | 55 |
| Alarms / Fire Alarm or Fire Department Call out | 39 |
How the Figures Are Backed Up
Numbering audit note: Ian flagged the 6,103 figure. Re-check confirmed it is the source workbook count of unique loitering report entries, while the operational evidence package should stay manageable: 12 original TrackTik PDFs plus full exports.
The dashboard is no longer just pasted screenshots. Each KPI maps to a source export below. The source pack includes CSVs, original workbooks, and a PDF summary similar to the C14 evidence model.
Original TrackTik Report Samples
Authenticated TrackTik app route /patrol/default/viewreportprintable/idreport/<id> was used to pull 12 representative original printable PDFs. Full evidence is represented by the source workbooks/CSVs; we are not treating all 6,103 loitering entries as PDFs that need to be downloaded individually.
Integrated Source Graphs
The additional graphs Deen supplied are incorporated as styled evidence panels, not dumped at the bottom.
