---
title: "Use cases: from a need to a verifiable solution"
description: "IoT applications for buildings and agriculture: what to observe,
  how to intervene and how to check the value of an improvement."
author:
  name: Walter Jerusalinsky
  title: IoT Specialist
  url: https://www.linkedin.com/in/walter-jerusalinsky/
canonical: https://www.idoneos.com/en/use-cases/
image: resources/use-cases.png
source: use-cases/index.md
---

<p class="series-label">USE CASES · IOT</p>

# Use cases: from a need to a verifiable solution

<p class="article-byline">By Walter Jerusalinsky</p>

A machine stops, a tank empties or a home uses energy while it is unoccupied. These are different problems, but they share a question: what do we need to know in time to act?

The Internet of Things, or **IoT**, connects measurements from the physical world with systems that can record, interpret and use them. Its value appears when that information improves a specific task: preparing a repair, regulating equipment or notifying someone who can resolve a problem.

<figure class="editorial-figure chalkboard-figure">
  <img src="resources/use-cases.svg" width="800" height="800" loading="lazy" alt="The workflow connects an observation with an intervention and returns to the result to evaluate the improvement.">
  <figcaption>The workflow connects an observation with an intervention and returns to the result to evaluate the improvement. <a class="diagram-expand" href="resources/use-cases.svg">Enlarge diagram</a>.</figcaption>
</figure>

## Choose the problem before choosing the equipment

The English-language articles in this section explore [agriculture](agro-iot/) and [building management](property-managers-iot/). The [Spanish use-case collection](/use-cases/) also covers manufacturing, home automation and weekend properties.

These are design scenarios for understanding possibilities and conditions. Each explains what we want to achieve, which data is needed, how it relates to a decision and what should be measured before extending the solution. A possible application does not establish a completed implementation or a demonstrated saving.

We are interested in starting with a recognizable difficulty and completing the workflow: observe, decide, intervene and check what changed. That sequence makes it possible to compare technologies while keeping the work we want to improve in view.