These questions address common considerations around deployment, integration, security, and use. If you don’t see your question here, contact us to discuss your environment.
No. Field IQ is designed to integrate with existing mission, training, and reporting workflows. It works alongside current systems as a post-mission evaluation support layer rather than replacing them.
Field IQ does not replace instructors, evaluators, or command judgment. It does not issue operational directives, automate grading, or generate pass/fail outcomes. It provides post-mission evaluation support and evidence-backed findings for human review.
Field IQ is designed for Observer Controllers, evaluators, AAR and debrief workflows, training and certification exercises, test and evaluation environments, and experimentation settings.
Field IQ’s core evaluation outputs are deterministic and explainable. Any bounded AI use, where enabled, supports assistive detection or classification and does not alter core evaluation logic, thresholds, or decision authority.
No. Field IQ supports evaluator judgment and mission command in post-mission review. Final judgment, scoring, and adjudication remain with instructors, evaluators, or command authorities.
Yes. Every signal is traceable to observable behavior, timing, and thresholds. Outputs are designed to support review, audit, and instruction. For details on how determinism, traceability, and auditability are enforced across deployments, see the Assurance & Control Model
Yes. Thresholds and flags are defined in doctrine and configuration files so they can align with training objectives and organizational standards. Core signal logic is fixed and not modified at runtime by AI or UI.
Field IQ integrates with GPS telemetry, training systems, mission planning tools, and downstream analytics platforms via structured movement data, timestamps, and mission metadata.
Deployment models support standalone Python modules, containerized services, API-based integrations, and air-gapped configurations. Deployment choice affects hosting and connectivity only. Signal logic and thresholds remain consistent across deployment models.
Most deployments can be stood up in days, not months, depending on data readiness, security constraints, and integration scope. We start with a scoped evaluation and expand only after outputs are validated in your environment.
You do. Field IQ does not retain, reuse, or externalize customer data. All telemetry, derived signals, and outputs remain fully within your deployment boundary and under your control. No telemetry or outputs leave your environment unless you explicitly configure an outbound path.
No. Field IQ does not require external API calls or cloud services by default. Any external connectivity is optional and explicitly configured by the customer.
Yes. Field IQ can be deployed in customer-controlled environments, including secure and contested / DDIL environments, subject to deployment architecture and mission requirements.
