Define operational scenarios
Describe the observable event, the environment in which it matters and the decision that must be supported. A headline range can represent different modes, probabilities and test conditions.
Request the conditions behind each figure
For important claims, ask for the mode, target type, altitude, speed, background, weather, detection probability, false-alarm context, update behavior and evidence method. A number without a method is difficult to compare.
Test the complete information path
Evaluate interfaces, time synchronization, records, access control, communications status and failure behavior. The system must move information from observation to an authorized user without losing meaning.
Include the lifecycle
Installation, training, updates, spares, support, diagnostics, cybersecurity and retesting after changes belong in the evaluation. A low purchase price does not automatically mean a low ownership cost.
Separate supplier documents from acceptance evidence
A datasheet is a supplier claim, not an acceptance result. Link certificates, reports and demonstrations to the exact model, version, mode and agreed scenario. Record missing data as a question rather than filling the gap with an assumption.
Run a separate regulatory review
A commodity code or marketing name alone does not determine import, control or use requirements. The selected configuration needs evidence-backed specifications and any applicable official determination or authorization.