Situational Awareness System

FAQ #

• What types of operational data can the system read?

  Fleet GPS positions, IoT sensor feeds, PostgreSQL/MySQL tables, REST APIs, WebSocket streams, CSV/JSON files. We design the data ingestion layer in the Diagnostic Architecture Audit to match your sources. Live data (sub-second) uses WebSocket or SSE; batch data (minutes) polls.
• What map rendering framework do you use?

  Kepler.gl (Deck.gl/WebGL) — handles 100K+ points, heatmap, hexbin, arc, cluster, and point layers, smooth viewport navigation. Non-geospatial operations can integrate Grafana or custom chart layers. Framing is scoped in the Diagnostic Architecture Audit.
• How does the NL interface prevent wrong commands?

  The AI produces typed JSON commands ({type: "filter_fleet", params: {zone: "northeast"}}) against a fixed schema of 12–20 types. Invalid types are dropped by the parse pipeline — the AI can’t invent a command that doesn’t exist in the schema.
• What data volumes does the system handle?

  Kepler.gl renders 100K+ points client-side via WebGL. The Rust backend handles concurrent connections and real-time data pushes. We profile your data volume in the Diagnostic Architecture Audit and right-size the backend accordingly.
• Can multiple operators use the system simultaneously?

  Yes. The backend supports concurrent sessions. Each operator has an isolated chat history; the map state can be shared (shared awareness) or per-session (individual views). We scope the multi-operator model in the Diagnostic Architecture Audit.
• What does deployment look like?

  We deploy to your infrastructure — Kubernetes, Docker Compose, or bare server (Hetzner, AWS, GCP, Azure). We deliver Dockerfile, k8s manifests, and a documented redeploy process. Database is PostgreSQL. Two services: Rust backend + static frontend.
• Do you build the data integrations or do we provide the APIs?

  We build the integration layer. If your sources have REST APIs or direct database access, we wire them. Proprietary protocols or legacy systems are scoped in the Diagnostic Architecture Audit and factored into the build timeline.
• How long does it take to build a full system?

  The five-day Diagnostic Architecture Audit delivers the architecture and command schema. A first live data source on the map follows in 10–15 days; the full system timeline depends on your data sources.
• What happens after delivery?

  You own the system — full source code, database schema, deployment configuration, and runbook. Ongoing support, feature expansion, and team onboarding are available as separate engagements.
• Do you sign NDAs and formal contracts?

  Yes. NDA before project start. Signed contracts with fixed scope per phase. Wyoming LLC — you’re contracting with a registered entity, not an individual.