The Platform Analytics Hub Control System About Evidence Contact

Eight Years. Four Control Generations. One Grower. 98% Harvestable Yield.

In 2016 this facility ran on Sestos timers. EC and pH were measured manually once a day. Nutrient delivery was time-based and assumed linear crop uptake — an assumption that is physiologically incorrect. Eight years later the same facility runs on CultivaTECH, a proprietary control platform developed directly from the operational knowledge accumulated here, and achieves 98% harvestable yield across all production cycles. This is the documented progression between those two points.

Based on first-hand operational history. Verified system evolution. High confidence rating.

98%
Harvestable Yield
Current operational benchmark — all production cycles
4
Control Generations
Timers → Arduino → SCADA → CultivaTECH
8
Years of Partnership
Installer to strategic technical partner
1ha
Commercial Facility
Offenham — operating for four years

A System That Was Never Finished — Because It Was Always Improving

Most case studies document a defined project: a start date, a scope, an outcome. This one documents something different — eight years of continuous system development with a single commercial grower, from the first basic installation through to the current state of the art. It is included here because the progression itself is the evidence.

What the progression shows is how Saturn's role evolves over a long-term partnership, how the knowledge accumulated through operational experience is systematically incorporated back into the system, and how a commercial growing facility moves from functional-but-limited to consistently high-performing through iterative integration rather than wholesale replacement.

It also shows where CultivaTECH came from. The proprietary control platform that now sits at the centre of Saturn's growing system offering was not designed in isolation — it was developed from eight years of operational experience in this facility, addressing specific limitations that commercial third-party platforms could not resolve.

Long-term trust is built through shared system evolution — not vendor dependency. The grower in this case study has remained with Saturn for eight years because each phase of the relationship delivered visible, measurable improvement to the system they operate every day.

Each Generation Resolved the Limitations of the Last

1

Generation 1 — Sestos Timers (2016)

Baseline
Architecture

Sestos digital timers. Fully time-based control — no closed-loop feedback. EC and pH measured manually once per day. Dosing duration adjusted manually based on daily readings.

Limitation that drove progression

No real-time feedback. pH drifted freely with no acid or base correction. Nutrient delivery assumed linear uptake — physiologically incorrect for leafy crops. Functional at small scale but not scalable.

2

Generation 2 — Arduino-Based Controller (c. 2017)

Transitional
Architecture

Custom Arduino-based control platform. Centralised control logic replacing discrete timers. Greater flexibility in scheduling and output management.

Limitation that drove progression

Reliability insufficient for commercial crop production. Hardware and software robustness did not meet agricultural uptime requirements. Collaboration with the development team ended due to unresolved reliability constraints.

3

Generation 3 — Autogrow Multigrow SCADA (2017–2019)

Commercial scale achieved
Architecture

Commercial SCADA platform. Direct collaboration with the platform's core development team. Multi-block irrigation via valve control. Professionally built electrical control panel to agricultural standards. Inline filtration, stirring pumps, safe output interlocks introduced.

What it enabled

True commercial scalability and operational robustness for the first time. Parallel small-scale trial systems introduced at Warwickshire, UK (2019–2020) for R&D alongside the commercial operation. Custom irrigation logic required workarounds within the SCADA platform — the limitation that drove Generation 4.

4

Generation 4 — CultivaTECH Proprietary Control System

Current platform
Architecture

Proprietary control platform developed from the ground up around Saturn's irrigation logic, nutrition strategy, and crop management philosophy. Initial Raspberry Pi–based platform progressively evolved into the CultivaTECH system — now deployed across Saturn's commercial client portfolio.

Why proprietary was necessary

Specific irrigation logic, multi-block valve control, and integration of auxiliary R&D systems required workarounds in the SCADA platform rather than native implementation. CultivaTECH eliminates those constraints — designed for Saturn's crop management philosophy, not adapted from a general-purpose architecture.

From Fixed Schedules to Integrated Multi-Part Nutrition

Phase 1 — 2016

Time-Based Two-Part Nutrition

Basic A/B nutrient solution. No acid correction. pH drift unmanaged. EC and pH monitored but not actively controlled.

Limitation: Incorrect assumptions regarding nutrient uptake behaviour for leafy crops.
Phase 2 — 2017–2018

pH-Responsive Dosing

pH-responsive dosing with dedicated control unit and probe. Fixed pH targets implemented. Branded commercial dosing hardware adopted.

Outcome: Improved consistency, reduced operator intervention. Limited integration with irrigation logic.
Phase 3 — 2018–2020

Integrated Multi-Part Nutrition

Full integration of dosing into the main control system. Introduction of functional additives and silicon supplementation. Addition of Part C for high phosphorus and potassium uptake during crop maturity.

Outcome: Significant crop quality and shelf-life improvements. Successful entry into major supermarket supply chains.

98% Harvestable Yield. Herb Market Entry. Four-Year Commercial Operation.

The progression from the Warwickshire, UK trial site to the 1-hectare commercial facility at Offenham was possible because each phase of system development resolved the limitations of the previous one without disrupting the production operation. 98% harvestable yield across all production cycles is the current benchmark — not a peak result from a single optimised cycle, but a consistent operational standard achieved across the full range of seasonal and production variability.

Shelf-life improvement was a direct consequence of the dosing evolution — produce that exits the facility in better nutritional condition maintains quality in the supply chain for longer. This enabled the facility to enter major supermarket supply chains and compete directly with field-grown crops on quality metrics, not just on price or proximity.

Expansion into the herb market materially improved the facility's commercial resilience — a second revenue stream from the same growing infrastructure, adding stability against the pricing pressure of the salad category alone.

The facility continues to operate. The system continues to evolve. The 98% harvestable yield figure is the current state, not the ceiling.

CultivaTECH Was Built From This. Not the Other Way Around.

The most commercially relevant aspect of this case study for operators evaluating Saturn's integrated growing systems is the origin of CultivaTECH. The proprietary control platform was not designed theoretically and then deployed at a commercial site. It was developed from eight years of operational experience at a specific commercial facility, resolving specific limitations in commercial third-party platforms that could not be resolved within those platforms' existing architectures.

This means that the irrigation logic in CultivaTECH reflects what actually happens in a commercial leafy crop growing system — how crop uptake varies by growth stage and environmental condition, how multi-block valve control needs to behave when irrigation zones have different crop timing, how dosing and irrigation need to be integrated rather than run as parallel independent systems. These are not theoretical design choices. They are operational lessons incorporated into hardware.

For operators considering a long-term integration partnership, the question is not just what Saturn can deliver on day one of a new installation. It is what the system looks like after three years, five years, eight years of shared operational learning. This case study documents one answer to that question.

Long-Term Growing System Integration

Where Is Your System in Its Own Progression?

Whether you are starting from basic timer-based control or operating a system that has reached the limits of its current architecture, the conversation about what the next phase of integration looks like starts in the same place — an honest assessment of what your system is doing now and what it needs to do next.

Growing System Evolution — Technical Questions

No growing system is fully optimised at commissioning. The crop's behaviour in a specific environment, with a specific water source and nutrition programme, reveals information that no pre-installation specification can fully anticipate. Early production data shows where assumptions were wrong — where nutrient uptake doesn't follow the linear pattern the original dosing logic assumed, where irrigation frequency needs to change as the crop develops, where pH drift is occurring faster or slower than expected. A system that cannot incorporate this learning stagnates. The progression documented here — from basic timer logic in 2016 to integrated multi-part nutrition and proprietary control in 2024 — is the cumulative incorporation of eight years of operational learning into the system design.
Time-based dosing assumes that the crop takes up nutrients at a constant, predictable rate. This assumption is physiologically incorrect for leafy crops, which alter their uptake rates based on light intensity, temperature, growth stage, and time of day. The result is that time-based dosing creates nutrient environments that drift away from optimal — the grower compensates with manual adjustments based on daily EC and pH readings. Moving to closed-loop dosing removes the drift and the manual intervention simultaneously. The crop receives what it needs when it needs it, and the operator's time is freed from daily measurement-and-adjustment routines.
The commercial SCADA platform was a significant step forward in operational robustness. But as the system became more sophisticated, specific irrigation logic developed for leafy crop production required workarounds within the SCADA platform rather than native implementation. Multi-block irrigation, auxiliary R&D system integration, and specific interlocking logic pushed against the boundaries of what a general-purpose SCADA was designed for. CultivaTECH was developed to eliminate those constraints — a proprietary platform designed around Saturn's irrigation logic and crop management philosophy from the ground up, not adapted from a general architecture.
Harvestable yield is the proportion of planted crop that reaches harvest specification — commercially usable rather than discarded due to quality failures, disease, or production losses. At commercial volumes, the difference between 80% and 98% harvestable yield is not a marginal improvement. It is the difference between a facility that regularly discards significant production and one that consistently delivers almost all of what it grows into the supply chain. 98% across all production cycles means the near-elimination of production loss as a routine operational feature, not a peak result from a single optimised cycle.
The initial role in this partnership was system installation and basic technical support. What changed over eight years was the depth of involvement in the decisions that determine crop performance: irrigation logic design, nutrition strategy, control platform architecture, and the system philosophy connecting all three. This progression from installer to strategic technical partner happens when the grower is open to incorporating new understanding into how the system operates, and the technical partner is capable of delivering genuine improvement rather than just maintaining the existing system. Both conditions were met here. The result is a system that reflects eight years of shared operational learning rather than the assumptions of a single installation specification.

Further Case Studies

Saturn Bioponics

Integrated Performance for Plant Cultivation

15 years of integration experience. Eight years of documented system progression with a single commercial grower. CultivaTECH built from operational knowledge, not theoretical design. Tell us about your facility.