Industries

Controlled Environment Agriculture

Water, climate and energy monitoring for greenhouses and indoor growing operations, where the environment is the product.

In a controlled environment, the utilities are not overhead — they are the growing recipe. Irrigation volume, lighting load, heating and dehumidification all move together, and a monthly total hides every one of the interactions between them. Continuous metering makes the recipe measurable, and makes a fault at 2 a.m. something you find out about at 2 a.m.

Climate is the first thing we meter, because it is the thing with the shortest fuse. A zone that spends three hours under setpoint on a January night has cost a week of growth, and the loss is already banked by the time anyone walks the range in the morning. Temperature and humidity sensors on the zone, an alert threshold either side of the setpoint, and a text message — that is the whole intervention, and it is usually the reason the system gets bought.

Irrigation is the second. Recipes are set per zone and then trusted, and a solenoid that does not quite close will follow the recipe on paper while delivering something else entirely. Flow metering per zone gives you litres delivered against litres intended, every day, per zone — which is a water number, a fertigation number and an early warning about a valve, all from one meter.

Energy sits underneath both. Lighting and dehumidification are the two largest loads in most operations and they are strongly scheduled, which makes them the easiest place in any facility to see a demand peak and move it. Gas for heating behaves the same way: baseload creep in a boiler is invisible on a monthly bill and obvious on a sixty-second trace.

Photo slot · industry-agriculture — pending the photography cull (§K.3 #27).

What the data looks like.

Representative operational data, not a client result — the shapes are real, the plant is not.

Zone 3 climate · last 24 h
NIGHT SETPOINTLights onLights offZone 3 at 16.1 °CVent actuator stuck open — 3 h below setpoint
LAST 24 H · 30-MIN BUCKETS · DASHED = NIGHT SETPOINT
Chart data
IntervalZone 3 air (°C)
00:0021.5
00:3021.3
01:0021.4
01:3021.3
02:0021.3
02:3021.3
03:0021.3
03:3018.8
04:0016.8
04:3016.1
05:0016.8
05:3018.7
06:0021.4
06:3021.6
07:0021.6
07:3021.8
08:0022.3
08:3022.9
09:0023.3
09:3023.8
10:0024.2
10:3024.7
11:0025.0
11:3025.2
12:0025.1
12:3025.1
13:0025.2
13:3025.1
14:0025.0
14:3025.2
15:0025.0
15:3025.2
16:0025.1
16:3025.0
17:0025.2
17:3024.6
18:0024.3
18:3023.7
19:0023.4
19:3023.0
20:0022.5
20:3022.1
21:0021.6
21:3021.4
22:0021.4
22:3021.5
23:0021.6
23:3021.5
A vent actuator stuck open at 03:00 and the zone spent three hours 5 °C under setpoint. The heating system did what it was told; nobody was there to be told anything.
Irrigation volume by zone
RECIPELIMITZone 1: 4,050 LZone 2: 4,180 LZone 3: 3,960 LZone 4: 6,740 LZone 5: 4,110 LZone 6: 3,760 L4,0504,1803,9606,7404,1103,760
YESTERDAY · LITRES · DASHED = RECIPE · RED = LIMIT
Chart data
IntervalValue (L)
Zone 14,050
Zone 24,180
Zone 33,960
Zone 46,740
Zone 54,110
Zone 63,760
The irrigation recipe is a number somebody chose. A zone quietly running 60 % over it is both a water bill and an agronomy problem, and only one of the two shows up on the invoice.

Representative sets are flagged provenance: representative in src/data/widgets/ and are hot-swappable for the real sets (G6) with no markup change — §K.3 #28.

What it found in plants like yours.

All 3 case studies in this sector

G4 — every industry slug must resolve to at least two case studies; the build gate asserts it (J.9.4). R2 — a study marked Illustrative scenario is representative of common industrial IoT applications: no client is named, no logo is shown and no figure on it was measured at any site.

Book a site walk.

Half a day on your floor, no charge and no obligation. At the end of it we tell you what we saw, what we would meter first, and what the return looks like.

How we work

or call 1-833-QUANTFY (1-833-782-6839)