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 sit alongside existing platforms. It ingests telemetry and surfaces readiness signals without forcing a rip-and-replace. This is by design. Field IQ is an interpretive layer, not a control system.
Field IQ does not replace instructors, command systems, or human judgment. No pass/fail outcomes, no automated grading, no operational directives. It surfaces signals. Human authority remains final.
Field IQ is designed for training evaluation teams, operational experimentation programs, readiness reporting organizations, units operating high-volume telemetry environments, acquisition and capability transition programs.
Field IQ uses AI selectively and narrowly for pattern detection and signal classification. Core outputs remain deterministic, explainable, and doctrine-aligned, with no self-modifying behavior in operational use.
No. Field IQ operates as an interpretive layer during evaluation, training, and early operational use and does not function as a control or adjudication system. The system surfaces telemetry-derived signals such as drift, deviation, and dwell to support human review. Final judgment, scoring, and adjudication remain with instructors, evaluators, or command authorities at all times, and no Field IQ output is binding.
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 supports offline, disconnected, and air-gapped deployments. Core analysis and scoring run without external connectivity, subject to mission requirements and approved deployment architecture.
