Aero Intelli

18 · RAS Knowledge

Automation

Automation on a fish farm is a life-support system before it is a convenience. What matters most is not what it controls when working, but how it behaves when part of it fails.

AdvancedAutomationEngineeringOperations6 min read
Aero Intelli EngineeringPublished 19 April 2026Updated 7 September 2026Version 1.0

Quick understanding

Automation watches the system when nobody is in the building, and calls someone when something is wrong. The useful question is not what it does when everything works — it is what happens when a sensor lies, a signal drops, or the power goes out at three in the morning.

Definition

Automation covers the sensors that measure the system, the controllers that act on those measurements, the alarms that summon a person, and the records that make the whole history reviewable. In aquaculture it spans a range from simple standalone alarms to fully supervised control of every process in the loop.

Why it matters

  • Continuous monitoring detects fast-acting problems — oxygen, flow, level — in the interval between routine checks, which is when they mostly occur.
  • Alarms convert a detected problem into a human response, which is the only part that actually saves fish.
  • Logging turns operation into evidence, so trends are visible and post-event analysis is possible.
  • Control stabilises parameters more tightly than manual intervention can, improving both fish performance and energy use.
  • Automation reduces the number of routine tasks competing for operator attention, so attention goes to the things that need judgement.

How it works

  1. Sensing

    A sensor converts a physical property into a signal. Its accuracy depends on calibration, on its condition, and on whether it is located where the measurement is meaningful.

  2. Signal transmission

    The signal reaches a controller. In a wet, electrically noisy environment this path is a common failure point, and a failed signal must be distinguishable from a valid reading.

  3. Control logic

    The controller compares against a set point and acts. What it does when the input is implausible or missing is the most important part of its design.

  4. Actuation

    A valve, pump, feeder or dosing system responds. Actuation should be verified by an independent measurement rather than assumed from the command.

  5. Alarm and escalation

    Where a condition is outside limits, an alarm is raised and escalated until acknowledged by a person who can act.

  6. Logging

    Every measurement, alarm and control action is recorded with a timestamp, forming the record on which later analysis depends.

The monitoring and control chain

Engineering principles

  • Fail-safe by design. Every control loop must have a defined behaviour on sensor failure, signal loss and power loss, and that behaviour must be the safe one for the fish.
  • Independence of critical alarms. The oxygen alarm should not depend on the same controller, power supply or network as the oxygen control.
  • Redundant measurement for critical parameters, so a single drifting sensor cannot silently misrepresent the system.
  • Alarm escalation with acknowledgement. An unacknowledged alarm must escalate to another person rather than repeating into an empty building.
  • Plausibility checking. A reading that is physically impossible should raise a sensor fault, not drive a control action.
  • Manual override on every automated function, accessible without the control system.

Design considerations

  • Identify the critical parameters first — oxygen, flow, level, temperature, power — and design their monitoring, alarming and redundancy before anything else.
  • Provide alarm annunciation that reaches a person off site, with escalation and acknowledgement, and test the full path.
  • Provide uninterruptible power to the monitoring and alarm system, independent of the plant it monitors.
  • Place sensors where the measurement means something, and where they can be reached for cleaning and calibration.
  • Specify enclosures, cabling and materials for a wet, corrosive environment.
  • Keep the log locally as well as remotely, so a network failure does not create a gap in the record.
  • Document the control logic in a form the operators can read.

Operational considerations

  • Calibrate sensors on a written schedule and record every calibration.
  • Cross-check automated readings against a manual measurement regularly.
  • Test alarms functionally, including the escalation path and the out-of-hours route, rather than checking that they are enabled.
  • Review the alarm log for repeated nuisance alarms; alarm fatigue is the mechanism by which a real alarm gets ignored.
  • Keep manual operating procedures current, and practise running the plant without the control system.
  • Review trend data as a scheduled activity, because the value of logging is realised in review rather than in collection.

Common problems and troubleshooting

Automation symptoms and first checks
SymptomCheck firstCommon direction
Reading stable and plausible while fish show distressSensor calibration and fouling, against a manual measurementA fouled or drifted sensor reporting a value the water does not have
Control loop hunting or oscillatingTuning parameters, sensor response time, actuator lagControl tuned faster than the process it controls can respond
Frequent nuisance alarmsAlarm limits against normal operating variation, sensor noiseLimits set too tightly, producing fatigue that will mask a real alarm
An event occurred with no alarm raisedAlarm configuration, escalation path, notification delivery, power to the alarm systemThe alarm path broken somewhere between detection and the person
Gaps in the logged recordLocal logging, network reliability, storage capacityLogging dependent on a network or a service that was unavailable
Actuator commanded but process unchangedIndependent verification of the actual physical stateA failed actuator with the control system reporting its command rather than reality
Automation symptoms and first checks. A diagnostic ordering. Appropriate alarm limits and control settings depend on species, loading, temperature, water chemistry and system configuration.

Maintenance

  • Clean and calibrate sensors on schedule; fouling is continuous in culture water.
  • Test the alarm and escalation path functionally at a fixed interval, including out-of-hours delivery.
  • Verify uninterruptible supplies by loading them, not by checking their indicator lights.
  • Check backup and retention of the logged data.
  • Review and update control documentation whenever logic is changed, and keep a change record.
  • Inspect enclosures, glands and cabling for water ingress and corrosion.

Common mistakes

  • Automating control before establishing reliable, calibrated measurement.
  • Powering the alarm system from the same supply as the plant it monitors.
  • Setting alarm limits so tight that nuisance alarms train everyone to ignore them.
  • Trusting a single sensor for a critical parameter.
  • Assuming a control command was executed, without independent verification.
  • Testing that alarms are enabled rather than testing that they arrive.
  • Collecting logs that nobody ever reviews.
  • Leaving no documented manual procedure for running the plant without automation.

Advanced considerations

Predictive and model-based control uses the system's own history to anticipate load rather than react to it — for instance adjusting oxygenation ahead of a scheduled feeding rather than after the resulting demand appears. The benefit is tighter parameter stability and lower energy use; the requirement is a trustworthy measurement record long enough to characterise the system.

Connectivity introduces a security consideration that a purely local system does not have. Remote access is genuinely valuable for out-of-hours response, and it also creates a path into a control system that is holding a live biomass. Network segregation, authentication and controlled remote access belong in the design.

Summary

Automation in a recirculating system is life support. Design it around failure: defined fail-safe behaviour, independent critical alarms, redundant measurement, escalation until acknowledged, and manual override throughout. Calibrate relentlessly, test the alarm path rather than the alarm, and review the log — because the record is only worth what someone reads from it.

Key takeaways

  • Automation here is life support: design around failure behaviour, not normal behaviour.
  • Critical alarms must be independent of the control system and its power supply.
  • A sensor that fails plausibly is more dangerous than one that fails obviously.
  • Alarms only save fish if they escalate to a person who can act, and are acknowledged.
  • Nuisance alarms cause fatigue, which is how real alarms get ignored.
  • Every automated function needs a documented manual override and procedure.

Related knowledge

  • AI in Aquaculture

    What is deployed, what is in research, and the line between the two.

  • Oxygen Management

    Demand, transfer, supply, and the failure that kills fastest.

  • Electrical

    Supply, distribution, standby power, protection and wet-environment safety.

  • Operations

    Daily routine, records, staffing, procedures and the discipline that holds them.

Further reading

Explore RAS engineering

Thirty areas covering the science, engineering, operation and economics of recirculating aquaculture.

All knowledge areas

Build with Aero Intelli

Bring the constraints of your site — water, power, species and market — and we will work through what they imply.

Talk to Aero Intelli