Bring the right participants
Include security, operations, communications or IT, engineering and people who understand the site's aviation or transport constraints. Procurement can join early, but the technical problem should not be framed around a preselected product.
Prepare a safe information set
The first discussion needs the site type, operating pattern, existing observation and notification systems, continuity constraints and decision process. Exact vulnerable-zone coordinates can wait for an agreed channel.
Describe normal activity
Document routine air and ground traffic, authorized flights, peak periods and seasonal changes. Without a baseline, a pilot may measure background activity rather than the ability to distinguish a meaningful event.
Agree pilot criteria in advance
Define scenarios, starting conditions, records, responsible roles and stop rules before testing. Criteria should cover the complete path from observation and notification to confirmation and operator action.
Keep assessment separate from authorization
A technical assessment informs architecture and testing. It does not replace any authorization, coordination or legal determination required for the selected capabilities and operating scenario.