Getting Started

Capture and normalize

Field telemetry, image frames, weather feeds, and site metadata are normalized into one event fabric.

Score and enrich

MosqAI enriches the event with model outputs, thresholds, contextual overlays, and governance metadata.

Publish operational action

Dashboards, alerts, maps, and exports update so analysts and field crews can act from the same signal.

Before you deploy anything

A successful MosqAI rollout starts with operational intent, not hardware shopping. Decide whether the first deployment is meant to prove surveillance coverage, improve treatment timing, support a research study, or build a cross-agency operating picture. That choice determines where traps go, who needs access first, and how success is measured.

• Name the decision you want the system to improve first
• Choose one geography small enough to learn from quickly
• Identify the analysts, field operators, and executives who need visibility

Design your first coverage zones

Coverage should reflect ecological logic and operational usefulness at the same time. MosqAI zones are not just polygons on a map. They are the units that alerts, reports, and interventions will be discussed in, so they should align with how the team actually responds.

• Separate flood-prone, tourist, residential, and infrastructure-heavy areas
• Use zones that match field routing and internal reporting language
• Avoid making the first deployment too large to interpret

Pick the first alerts carefully

Teams usually over-alert in the first week. Start with a narrow set of events that matter operationally, then widen the signal surface after people trust what they see. MosqAI is most useful when every early alert feels explainable and worth opening.

• Use simple pressure bands at first
• Treat unexpected movement, not just high counts, as a meaningful signal
• Add disease-risk and intervention logic after baseline behavior is understood

Plan for the human rollout

A surveillance platform succeeds when it fits team habits. Decide who reviews the dashboard, who owns escalation, who records interventions, and how summaries move upward. Technical deployment without operational ownership quickly becomes a dormant map.

• Assign one operator to own weekly signal review
• Define what qualifies as a field escalation
• Create a short narrative template for leadership updates

What should the first pilot prove?

The strongest pilot proves that MosqAI improves a real operational decision. That could be crew routing, hotspot detection after storms, or better reporting across departments. Start with one clear outcome and build from there.

How many traps are needed to begin?

Enough to create a meaningful comparison across zones, but not so many that the team cannot interpret the data. The goal of the first rollout is to learn the local pattern, not blanket the map.

Who should own the launch?

One accountable operator should own the first rollout, even if multiple departments are involved. Shared interest is useful; shared accountability usually is not.