Aquaculture Farm Operations Software Requirements

Define the production decision and biological boundary

Aquaculture software should help people observe and operate a specific production system without pretending that an algorithm can replace aquatic health, veterinary, environmental, food-safety, welfare, or regulatory authority. Begin with species, life stage, production method, water source, site structure, jurisdiction, market, environmental conditions, and the decisions the first release must improve. A pond farm, recirculating system, cage site, hatchery, and shellfish operation have materially different risks and records.

Trace representative stock from broodstock or seed source through receipt, quarantine where applicable, stocking, movement, feeding, sampling, treatment or intervention, mortality, harvest, packing, and sale. Include poor water quality, suspected disease, equipment failure, feed substitution, escaped or missing stock, weather disruption, connectivity loss, and a rejected harvest lot. The farm operations requirements checklist provides a broader foundation; aquatic production requires explicit population, water, and biosecurity relationships.

Model sites, production units, populations, and movements

Separate organization, site, water body or source, production unit, cohort or population, species, strain, life stage, batch, stocking event, movement, split, merge, sample, observation, mortality event, input, intervention, harvest, product lot, and shipment. Preserve source identifiers and effective dates. Avoid presenting an estimated population as a precise inventory when growth, mortality, escape, predation, measurement uncertainty, and partial movement affect the number.

Every split, merge, transfer, grading, and harvest should preserve parent-child lineage, quantities, units, method, time, source and destination, responsible person, and evidence. Define whether records apply to a physical individual, sampled subset, production unit, or estimated population. Corrections must retain the earlier report and explanation. A retrospective edit that makes feed conversion or survival appear cleaner undermines both operational learning and trust.

Capture environment and equipment with context

Record parameter, unit, method, instrument or sensor, calibration or verification context, production unit, depth or location, timestamp, operator, quality state, and environmental conditions. Water temperature, dissolved oxygen, salinity, pH, flow, turbidity, and other measures matter differently by system and species; qualified operators must define thresholds and response. Store raw or source observations where feasible and distinguish measured, entered, calculated, and imported values.

Sensor integrations need identity, clock handling, validation, missing-data behavior, drift detection, maintenance, calibration, and safe alerting. A plausible number can still come from the wrong probe or stale gateway. Show data age and uncertainty, preserve gaps, and avoid interpolating a smooth history as though it were observed. Test network loss, power interruption, duplicate readings, out-of-range values, changed units, replacement probes, and bulk reconnect after an outage.

Operate feed, inputs, work, and inventory as evidence

Model feed product, formulation or specification, supplier, lot, receipt, storage condition, expiration, allocation, planned ration, actual issue, delivery method, uneaten estimate where used, and correction. Keep recommendations separate from authorized plans and actual feeding. Connect chemicals, treatments, disinfectants, vaccines where relevant, and other inputs to approved authority, lot, quantity, purpose, production boundary, withholding or restriction, and responsible record.

Work records should identify task, unit or asset, instructions, assigned role, due window, execution, observation, exception, verification, and evidence. Support equipment inspection, cleaning, net or enclosure work, pump and aeration maintenance, predator controls, waste handling, sampling, and emergency action according to the operation. Offline users need stable identifiers and clear sync state so repeated taps or reconnects do not duplicate feed, mortality, treatment, or movement entries.

Support health monitoring and biosecurity plans

The FAO aquaculture biosecurity pathway frames biosecurity as risk-based management with shared responsibilities and includes surveillance, monitoring, diagnostics, management, and evaluation. Software can make approved plans operable by linking hazards, controls, zones, access, cleaning, introductions, movements, observations, thresholds, escalation, samples, laboratory results, actions, audits, and review dates.

The WOAH Aquatic Animals Commission maintains international aquatic animal health standards reflecting current scientific information. Applicability and response need competent authority. Configure qualified rules by species, disease concern, site, and jurisdiction; never infer diagnosis from mortality or sensor patterns alone. Preserve detection, assessment, recommendation, authorization, action, outcome, and notification as distinct records.

Connect harvest and traceability without false precision

Define harvest event, source populations, method, time, quantity and unit, grade, destination, handling condition, product lot, processor or buyer, transport, and acceptance. Preserve partial harvests and mixed lots explicitly. Reconcile expected stock, observed harvest, mortality, movements, and residual estimates, but do not automatically force the numbers to balance by editing history. Investigation should expose uncertainty and source evidence.

The GS1 Global Traceability Standard offers technology-neutral identify, capture, and share principles across supply chains. Apply standards where customer, certification, market, or partner requirements justify them. Trace backward and forward from harvest lot to production units, seed or stock sources, feed and relevant inputs, processing, and shipments within an agreed response time, while keeping regulated claims under qualified review.

Design analytics that respect biological uncertainty

Define survival, biomass, growth, feed conversion, stocking density, treatment outcome, yield, cost, environmental, and welfare-related calculations with input sources, units, exclusions, time boundary, and data-quality status. Display the underlying observations and assumptions. Comparisons across sites or cohorts can mislead when species, life stage, measurement method, weather, system design, stocking source, or missing data differ materially.

Use predictions as decision support with documented training boundary, validation, uncertainty, drift monitoring, and human authority. Do not automatically alter feeding, treatment, harvest, or stocking based on an unexplained recommendation. Measure whether a feature improves observation quality, response time, input use, survival understanding, traceability, and operator workload rather than advertising a universal optimization percentage unsupported by the actual farm.

Protect people, farm data, and operational continuity

Classify worker, supplier, customer, production, health, location, environmental, and commercial information. Apply purpose-based access, strong authentication, protected exports, audit trails, backup, restoration, and offboarding. Use the NIST Privacy Framework to structure privacy risk without mistaking it for a jurisdiction-specific legal answer. Limit precise site, infrastructure, and sensitive health visibility to legitimate roles.

Plan continuity for power, network, sensor, cloud, and device failures. Identify tasks that must continue locally, how records will be captured, which alerts have independent mechanisms, and how later reconciliation works. Restore backups and replay offline changes in a production-like exercise. An aquaculture platform that loses the day's observations during a storm or duplicates interventions after reconnection can create more risk than the paper process it replaced.

Migrate records and establish data stewardship

Inventory farm logs, spreadsheets, sensor platforms, feed records, laboratory results, stock and harvest systems, maintenance tools, invoices, and certification records. Map sites, production units, cohorts, materials, lots, units, timestamps, and authority before loading history. Decide what supports active production, traceability, claims, retention, or analysis and what should remain in a governed archive. Avoid inventing exact population lineage where source records only provide periodic estimates.

Rehearse with representative full-volume data and preserve source identifiers, transformation versions, and quality flags. Reconcile selected stock movements, feed issues, mortality, interventions, harvests, and product lots with operators and qualified reviewers. Assign ongoing owners for site masters, units, species terms, sensor identities, feed and input catalogs, health codes, integrations, and correction queues. Without stewardship, a polished dashboard will gradually combine incompatible units, duplicate cohorts, and stale thresholds.

Pilot one complete production cycle slice

Choose one site, species, and bounded cohort. Demonstrate stock receipt, production-unit assignment, environment observations, feed issue, task execution, movement or grading, health exception, qualified response, mortality, harvest, lot creation, trace back, offline capture, and restoration. Include an incorrect sensor, rejected laboratory sample, split cohort, missing feed lot, late sync, and corrected quantity. Reconcile the platform with physical and authoritative records.

Before commissioning development, provide site and production-unit maps, species and stages, operating procedures, biosecurity plan owners, observation methods, sensors, input and feed records, health and escalation boundaries, harvest and buyer requirements, integrations, connectivity conditions, migration samples, and acceptance scenarios. Submit them through the project questionnaire for a phased estimate, or use quick contact to compare configuration, integration, and custom software.

Authoritative references

• FAO Progressive Management Pathway for Aquaculture Biosecurity
• WOAH Aquatic Animal Health Standards Commission
• GS1 Global Traceability Standard
• NIST Privacy Framework

Related software planning guides

• Farm Management Software: Build, Buy, or Integrate?
• Farm Operations Platform Security and Resilience Guide
• Farm Operations Management Software Requirements Checklist