Engineering Research
Help ARS engineer the right capabilities, not just any capabilities
ARS is conducting structured engineering interviews with public safety professionals to better understand real-world UAS missions, operator workload, communications challenges, sensor needs, software limitations, reliability requirements, and desired future capabilities.
Why We're Talking With Agencies
Engineering priorities driven by field experience, not assumptions
ARS wants the people who fly missions, run programs, and make command decisions to shape what gets built next. These conversations are engineering research and requirements discovery — they are not a sales campaign.
ARS is not currently using this outreach as a sales campaign.
Interviews are intended to understand real operational workflows and unmet needs.
ARS wants engineering priorities to be driven by experienced end users rather than assumptions.
Who We Want to Hear From
Public safety and aviation professionals across every response role
What Gets Discussed
Typical interview subjects
Interviews are typically 20 to 30 minutes and cover the operational realities of your mission — not a product pitch.
About 20–30 minutes
Typical interviews run 20 to 30 minutes, in person, by phone, or by video — whatever works for your schedule.
Voluntary participation
Participation is voluntary and does not create a purchase commitment, endorsement, or procurement discussion of any kind.
No sensitive information
Please do not share law-enforcement-sensitive, protected, classified, or otherwise operationally sensitive information.
What We Are Not Asking For
This is not a product evaluation or a procurement conversation
- Procurement plans or budget information
- A purchasing decision or commitment
- An endorsement of ARS or its technology
- Evaluation of a finished product
- Law-enforcement-sensitive or protected operational information
How Information Is Used
Turning field experience into engineering requirements
The information gathered will be used to identify recurring engineering requirements and help prioritize future system development. It is not sold, and it is not used for a sales follow-up campaign.
ARS can avoid publicly attributing comments to an individual or agency when requested. Beyond that, ARS has not adopted a formal confidentiality policy, so please do not share information that must be handled under a specific confidentiality or classification requirement.
Comments may be summarized anonymously across interviews to identify common patterns, unless another arrangement is explicitly made with you in advance.
Ready to share your operational experience?
Schedule a conversation with the ARS engineering team. No sales presentation, no purchasing commitment.
Engineered in Idaho