# DroneSense A drone-operations management platform documented through Russellville PD's paired flight-session and coordinate-bearing exports, plus Policy 421.2's description of the records kept in the system. This page uses only what the produced records show and does not infer contract terms or pricing. ## Roles in this corpus - [[Russellville Police Department]] produced 724 flight-session rows. A later coordinate-bearing companion repeats the flight IDs and adds model, latitude, longitude, training status, and mission, yielding 719 dated takeoff joins across 715 exact coordinate strings ([[Russellville Drone Inventory Policy and Flight Coordinates]]). - Policy 421.2 says DroneSense stores hardware updates, maintenance schedules, member access, incident reporting, missions, training records, and Part 107 certifications, and directs the responsible pilot to log the correct training or real-world flight (`Drone data.pdf`, p. 10). ## Notes DroneSense is the drone-side counterpart to the corpus's camera-platform vendors: its records document operational tempo and takeoff locations, while full track geometry, procurement terms, and per-flight authorization records remain unproduced. No DroneSense contract, invoice, or agreement appears in the corpus. See [[Law-Enforcement Drone and UAS Programs]] for the cross-agency comparison.