Every decision makes the next one better
Nidus Core keeps the district's record and then works on it. What came of each decision shapes where the district looks next, so effort narrows onto the ground that is actually producing mosquitoes. The aim matches yours: fewer mosquitoes and less pesticide, season after season.
Signals in, verified outcomes back
A resident report, a trap count, or a satellite detection enters as a signal. A planner turns signals into a lead. A crew confirms what is actually there. What they find attaches back to the signals that prompted the visit, so the next decision starts from ground truth the district confirmed itself.
Find
Intelligence from the systems the district already runs, together with resident reports, enters the system and becomes a worklist the district can act on.
Dispatch
Work reaches the technician responsible for it, with that site's history attached before arrival.
Record
Findings are captured in the field and attached to the site permanently, in the technician's own hand.
Review
Supervisors see completed work, find anomalies, and correct the process rather than the history.
Learn
Every observation sharpens the next decision, so the district's knowledge accumulates rather than walking out the door with staff.
Prove
The record shows what was found, what was done, and what changed, which is what a board and a compliance file need.
Nothing enters the record on a machine's say-so
A detection, a report, or a pattern can suggest that a site is producing mosquitoes. Only a technician's field observation can confirm it, and a site is only called a source after an inspection finds larvae or pupae. Every recommendation in Nidus traces back to an observation the district recorded, on ground the district walked. Corrections are added as new entries, so the trail behind an enforcement action holds up.
Data that gets more useful every season
Storing the work is the starting point. Nidus holds what happened after each decision so the next one is better informed, and the district's effort keeps getting more precise.
It keeps what happened after each decision
Every inspection, notice, and treatment attaches to that site permanently, so the system holds what was done there and what came of it. That is what makes the next decision informed.
Nothing is deleted, so history compounds
A site that was treated keeps its full history. The district accumulates what works in its own conditions rather than starting each season from scratch.
Effort narrows onto real production
Sites that keep relapsing rise on the work list, and sites that stay clean stop consuming visits. Crews spend their time on water that is actually producing mosquitoes.
Everything you already know comes with you
FieldSeeker and MapVision data come in as they are, alongside the records your district already keeps. Nothing is re-entered, and every week's findings sharpen the next decision.
Field capture runs without a signal
Nidus Notes records findings with no connection and syncs when the crew is back in range, so dead zones and rural routes do not put the work on hold.
Corrections build the record
A revisited finding becomes a new entry. The trail behind a compliance action holds up because it was never editable in the first place.
The workbenches a district runs on
Resident reports arrive by web, phone, and text, and owner letters go out from the same record. Planners turn signals into work, supervisors dispatch it, technicians capture what they find in the field, and Review keeps the process honest.
Intake and communication
Resident reports by web, phone, and text, owner letters, and the Communications workbench for reading and answering correspondence.
Planning, field, and review
Planning and Operations turn signals into dispatched work, Nidus Notes captures it in the field, Review checks it, and Insights sits above the day to day.
Works with your systems
FieldSeeker and MapVision come in as they are, and the intelligence your district already holds stays live in Nidus instead of being re-entered.
Weekly coverage of the ground nobody has visited
Core works from the data your district already has. Reveal adds satellite coverage of the whole district each week, and every finding enters the same record as everything else, arriving as a site with the visit, the notice, and the treatment attached to it.
| Workbench | What it does |
|---|---|
| RMO | Resident reports arriving by web, phone, and text |
| Communications | Reading and answering resident and landowner correspondence |
| Nidus Notes | Field capture on a phone or tablet, offline, with site history on screen |
| Planning | Turning signals into the work that needs to happen |
| Operations | Assigning work to technicians and building routes |
| Compliance notices | First notice, second notice, and warrant escalation |
| Review | Checking completed work, catching anomalies, correcting process |
| Insights | Operational reporting above the day-to-day |
Bring your district onto Nidus
We start from the data your district already has, bring the existing record in, and set the workbenches up around how your crews actually work.