Field sensors reporting to a cloud dashboard with alarms, where the feasibility risk was not any single layer. It was whether the number at the metal would still be honest by the time it reached the chart a human acts on. The real exposure was capital: committing to a fleet before knowing the sensing, the link, and the data path were viable end to end.
The stated ask is build the monitoring product. The real problem is capital risk rather than a feature gap. A reading is only as good as its weakest hop, and owning a single hop means shipping a dashboard that is confidently wrong in ways nobody upstream can see. The question worth paying to answer first is whether the whole path holds, not whether any one layer can be built.
The reflex, and the fix.
Build the dashboard and buy the fleet
It is what was asked for, and the dashboard is the visible deliverable.
It commits the capital before anyone has established that the number surviving to the chart is the number at the sensor.
Prove the whole path before the fleet is bought
A feasibility engagement that spans firmware, link, ingestion, and alarms rather than delivering the visible layer first.
A rollout decision resting on a proven path instead of a hopeful one.
Prove the weakest hop before the capital commits, because a dashboard cannot report a problem it inherited.
Edge sampling and buffering
So a dropped link backfills on reconnect rather than leaving a hole that looks like a reading.
A defined transport and message schema
Because an undefined schema is a silent divergence waiting for the first firmware update.
Ingestion that marks gaps explicitly
A real zero and a missing value are different facts, and a pipeline that conflates them produces a chart that is wrong in the most expensive direction.
Alarms on sustained state
An alarm that fires on a single sample cries wolf on a momentary dropout, and an operator who has been woken twice stops trusting the third alert.
A single headline number hides where a system fails. This work was scored on the dimensions that actually decide whether it holds in production, measured on real, held-out cases rather than the demo path.
A polished dashboard, a purchased fleet, and a slow discovery that gaps read as zeros and alarms fire on noise, at which point the capital is already spent.
A validated end-to-end path where the reading at the metal survives the trip to the chart, gaps are visible rather than hidden, and alarms reflect sustained state, so the rollout decision rested on a proven path.
What it owns, and what it hands to a person.
Outcomes here are stated qualitatively. This was a feasibility engagement whose product was a decision, and the honest measure of it is that the decision rested on evidence rather than on hope.
When the risk is capital rather than capability, the deliverable is a decision, and the way to earn it is to prove the weakest hop rather than to build the most visible one.