Farms are simple. A farm, a building or two, maybe a barn. Done. You’d wish.
Monitoring farms and barns is a tedious task. No farm looks like the other and water distribution, next to other elements, has grown generically. A little bit like the good old legacy systems we all love. With the additional complication of keeping track of topology changes, typical building automation systems are out of the scope.
See how clevabit integrated neo4j, PostgreSQL and TimescaleDB to bring observability to farms and what I learned along the way. And there were a lot of “this time it works” moments.
63. https://www.brickschema.org/
Brick Schema
The subject is upstream of the object and
some media is passed between them.
The subject is composed in part of the
entity given by the object.
The subject has a source of telemetry
identi
fi
ed by the object.
feeds:
hasPart:
hasPoint:
64. https://www.brickschema.org/
Brick Schema
The subject is upstream of the object and
some media is passed between them.
The subject is composed in part of the
entity given by the object.
The subject has a source of telemetry
identi
fi
ed by the object.
feeds:
hasPart:
hasPoint:
65. https://www.brickschema.org/
Brick Schema
The subject is upstream of the object and
some media is passed between them.
The subject is composed in part of the
entity given by the object.
The subject has a source of telemetry
identi
fi
ed by the object.
feeds:
hasPart:
hasPoint:
MATCH (e:Equipment)-[:feeds]->(l:Location)
WHERE EXISTS {
MATCH (l)<-[:has*]-(c:Customer {id: “…”})
}