# Deployment and Location Activity Notifications Series **32 variants** across three related auto-notification subject lines documenting Flock's platform-side **installation, maintenance, and location-activity announcements** for the Conway PD deployment. Each notification is a routine prompt — upcoming installation work, completed deployment activity, or planned location changes on specific Conway cameras. The series spans the operational lifetime of the deployment and supports cross-referencing with [[Conway PD Project Update - ARDOT Permits Series]] for the installation timeline anchor. ## What's inside **Three subject patterns, 32 total .msg files:** | Pattern | Count | Purpose (per filename + sender pattern) | |---|---:|---| | `Upcoming Deployment Activity for AR - Conway PD` | 17 variants | Advance notice of planned work at specific Conway camera locations | | `Flock Safety Location Activity for AR - Conway PD` | 8 variants | Confirmation of completed activity at specific locations | | `Flock Safety Upcoming Location Activity for AR - Conway PD` | 7 variants | Variant subject line for the same advance-notice notifications | All automated emails from Flock's platform notification system (no-reply or hello@ addresses), addressed to Burningham. The 32-variant volume across ~12 operational months works out to **roughly 2-3 location-activity notifications per month**. The notification frequency tracks the deployment timeline: - **2025-Q2-Q3** — Higher frequency during initial 8-of-20 installs (per [[LPR Report First Half 2025]]). - **2025-Q4** — Quieter as deployment paused awaiting ARDOT permits. - **2026-Q1** — Spike during the Feb-Mar 2026 final installation wave (per [[Conway PD Project Update - ARDOT Permits Series]]). ## Key takeaways - **Each install / maintenance event generates a notification pair** (upcoming + completion). The redundancy means the deployment timeline is doubly anchored. - **The notifications cite specific device IDs** (F#NNN format) and intersection names — consistent with the device-level identifiers used elsewhere in the corpus. - **These notifications are the operational analog of the [[Conway PD Project Update - ARDOT Permits Series]]** — the project-update emails are human-authored summaries from Garrett Yosenick (Flock PM); these auto-notifications are platform-generated for each individual location event. Combined they give complete visibility into the deployment timeline at both summary and per-event levels. - **The notifications imply Conway PD's deployment is operationally typical** for a Flock customer: regular maintenance, occasional location adjustments, no signal of operational dysfunction. The documented anomalies (vandalism — see [[MSA via Cameras Thread]] — and past-due invoices — see [[Flock Safety Past Due Balance INV-81961]]) are not reflected in this notification stream, which suggests those events are tracked through different Flock workflows (support tickets, billing systems) rather than the location-activity notification channel. ## People and orgs mentioned - [[Lt. Andrew Burningham]] — sole recipient (the named Conway Flock admin). - [[Flock Safety, Inc.]] — automated sender. ## Concepts invoked - [[Flock Camera-as-a-Service Procurement Model]] — operational notifications are part of the bundled service. ## Cross-references - [[Conway PD Project Update - ARDOT Permits Series]] — human-authored counterpart for the same install events. - [[Flock Devices 2 (admin screenshot)]] — the eventual deployed inventory. - [[LPR Report First Half 2025]] — H1 2025 status (8 of 20 installed). ## Open questions / follow-ups 1. **Sample one notification per quarter to confirm device-ID and intersection-naming consistency.** A low-priority validation step. 2. **Cross-reference notification dates against the [[Conway PD Audit Logs Series]] activation dates** for each device to confirm the install-to-active-query timeline.