Aquaculture harvest management software
AquaOS is aquaculture harvest management software that records fish leaving a growing unit on purpose, by destination, and checks what leaving implies before it is allowed. Harvest is where the production record either closes cleanly or stops being trustworthy.
- Recorded by destination
- Checked before the fish leave
- Reconciled against the source
How a harvest is recorded
By destination, not as one event type
Fish leaving for an order, leaving for another buyer, moving internally, or being culled are different events with different consequences.
Recording them the same way is how a stock figure and a sales figure drift apart.
The gates run before the fish move
A harvest to an order or to another buyer is refused while the batch is quarantined, and refused while a withdrawal period is open, because both are exits to food.
Internal moves and culls are treated differently, because the fish are not being sold. The checks run at the operation, in order, before anything is written.
See health and treatmentGrades on the way out
A harvest records which size grades left and in what quantity, so what was shipped is described in the same terms the farm sells in rather than as an undifferentiated count.
The sale output of a grading session
Where a sort ends in fish going out rather than back to a unit, that output is the same harvest path, not a parallel one.
One write path means one set of rules, and the reconciliation at close still has to balance against the source.
See sorting and gradingA cull that is counted as mortality
Culled fish are written as mortality in the same transaction that closes the session.
If any part of it fails, the whole thing rolls back together, so a close cannot half-happen and leave the count wrong.
Preview before committing
A harvest can be previewed against current stock before it is recorded, so the effect on the unit is visible at the point of decision rather than after the lorry has left.
What changes when harvest is part of the record
Stock is right the morning after
Because the harvest wrote the movement, the counts, and any cull together, the next day starts from a figure nobody has to reconstruct.
The compliance question is already answered
Whether the fish that shipped were clear of treatment is not a question asked after the fact. The shipment could not have been recorded otherwise.
Harvest data feeds the plan
What actually shipped, by grade and by month, is what the annual plan is measured against and what the next harvest forecast starts from.
Related capabilities
Health and treatment
Treatments, withdrawal periods, quarantine, vaccinations and mortality by cause.
Production planning
Annual plan against actual, harvest forecast by size band, capacity and period locks.
Sorting and grading
Sorting stations, live sessions, size classes and reconciliation against the source.
Frequently asked questions
Does AquaOS stop a harvest that would breach a withdrawal period?
Yes, for any destination that is an exit to food: an order, another buyer, a transfer or a hand-off. The check runs at the operation before anything is written. An internal move or a cull is not blocked by a withdrawal, because the fish are not being sold. Where an override is used it is stamped on the operation.
Can a quarantined batch be harvested?
Not to an order or to another buyer. Internal moves and culls remain possible, because they are not sales. Quarantine has no override path, so releasing the batch first is the only way, and the release is logged.
How are culled fish accounted for?
As mortality, written in the same transaction as the session close. If any part of the close fails the whole operation rolls back, so the cull, the movement and the counts cannot end up disagreeing with one another.
Does harvest feed back into planning?
Yes. What shipped, by grade and by period, is what plan against actual compares to, and the harvest forecast reads the remaining stock forward from the same record.
See AquaOS on your operation
Bring a real production scenario. AquaOS is walked through on your operation, not a canned dataset.