Skip to content
 
 
 
Manolin's Technology

How data becomes reliable intelligence

Manolin keeps the biological context intact across aquaculture data systems.
 
 
The data problem We Solve

Farm operations create data everywhere.

Production, feeding, health, environment, transport, and site operations all generate records. Each system captures a different part of the biological story.

Data systems hold different pieces of the same history.

As records leave their source systems, inconsistent identifiers, formats, and timestamps prevent them from arriving as one coherent history.

Reconstruction creates even more work.

Teams spend too much time matching fragments, identifying gaps, and determining which events belong to the same fish before analysis can even begin.

Structure turns fragments into an analytical foundation.

Manolin cleans and normalizes your data together so the historical context needed for comparison and analysis is now possible for your teams.

Now the data investigation can start.

The questions farms and suppliers need to answer for decisions become much clearer when they begin from one structured history rather than disconnected records.

manolin // continuity tracefish-production data system
site + pen wellboat operations feed records environment health + treatment
site_24 / cage_08
boat_transfer / time
feed_lot / dosage
oxygen / temp / current
evt_treatment / mech
same history // different records
normalized fish historyinvestigation-ready
ENTITYgroup_17 → site_24 → cage_08linked
EVENTSfeed + treatment + transfer + healthaligned
CONTEXTenvironment + operations + generation retainedready
For farms // operational investigation

Why did treatment performance diverge between two sites?

What changed this generation compared with the last?

Which conditions shaped the mortality event?

For suppliers // field evidence

Did the product drive the outcome, or were other variables involved?

Where does the signal remain consistent?

What should R&D investigate next?

The data problem // 01

Operations create data everywhere.

Production, feeding, health, environment, transport, and site operations all generate records. Each system captures a different part of the biological story.

fish-production data sources
site_24 / cage_08 boat_transfer / time feed_lot / dosage oxygen / current treatment / mech
The data problem // 02

Different systems hold different pieces of the same history.

As records leave their source systems, inconsistent identifiers, formats, and timestamps prevent them from arriving as one coherent history.

record fragmentation
site_24 / cage_08 boat_transfer / time feed_lot / dosage oxygen / current treatment / mech
same history // different records
The data problem // 03

Reconstruction becomes the work before the work.

Teams spend time matching fragments, resolving gaps, and determining which events belong to the same fish population before analysis can begin.

manual reconstruction
 
site_24 / cage_08 → group_17 ?
treatment_event → source timestamp ?
feed_lot → exposure window ?
mortality → generation context ?
The data problem // 04

Structure turns fragments into an analytical foundation.

When entity lineage and events are normalized together, the historical context needed for comparison and investigation becomes usable.

normalized continuity
normalized fish historyentity + event model
ENTITYgroup_17 → site_24 → cage_08linked
EVENTtransfer → feed → treatment → observationaligned
TIMEsource timestamps reconciledordered
CONTEXThealth + environment + operations retainedready
The data problem // 05

Then the investigation can actually start.

The questions farms and suppliers need to answer become much clearer when they begin from one structured history rather than disconnected records.

investigation-ready history
normalized fish historyready
ENTITYgroup_17 → site_24 → cage_08linked
EVENTSfeed + treatment + transfer + healthaligned
CONTEXTenvironment + operations + generation retainedready
For farms // operational investigation

Why did treatment performance diverge between two sites?

What changed this generation compared with the last?

Which conditions shaped the mortality event?

For suppliers // field evidence

Did the product drive the outcome, or were other variables involved?

Where does the signal remain consistent?

What should R&D investigate next?

Population Tracing

A continuous biological record for aquaculture analysis.

Manolin's population tracing algorithm gives our models and analysis a continuous biological record across production cycles throughout the Manolin network.

The preview environment could not stream the remote HubSpot MP4. The section is wired to the supplied HubSpot video URL.
The shared intelligence layer

Connecting historical data traces before any model runs.

Manolin’s differentiation starts underneath our software. The platform preserves the biological history behind the data, then applies aquaculture-specific analysis to questions that are otherwise difficult to answer reliably.

01 // Connect

Bring the systems together.

Integrate production, feeding, environmental, health, laboratory, and operational records without requiring a new hardware layer.

02 // Reconstruct

Preserve the fish history.

Link data to traceable populations rather than temporary cage locations as fish are split, merged, transferred, and moved.

03 // Contextualize

Compare the right baselines.

Evaluate performance with the conditions, interventions, and prior events that shaped the population outcome.

04 // Investigate

Move from signals to action.

Give farm and supplier teams a clearer path from a detected change to the next investigation, report, or decision.

Manolin Newsletter

Aquaculture intelligence, once a month.

Data insights, technical analysis, and industry developments from Manolin.

Technology FAQ

Questions about how Manolin works.

Technical answers for teams evaluating Manolin.

For farm teams, does Watershed replace our existing production systems or hardware?

No. Watershed works with the systems and data sources already used across your operation. Manolin sits across that existing environment, connecting and structuring the data for analysis rather than requiring a new hardware layer or replacement production system.

How does Manolin connect data from the different systems we already use?

Manolin brings records from production, feeding, fish health, environmental, laboratory, treatment, and operational systems into a common aquaculture-specific data structure so they can be analyzed together.

What is Population Tracing, and why does it matter?

Population Tracing is Manolin’s algorithm for maintaining a continuous biological record across production cycles. That record gives our models and analysis the population-level history needed to interpret health, performance, interventions, and outcomes in context.

Why would we use Manolin instead of our existing data warehouse or BI tools?

Data warehouses and BI platforms are designed to store, organize, and visualize data. Manolin is built specifically for aquaculture: structuring fragmented production data, preserving biological relationships, and preparing that information for population-level modeling and analysis.

What data can Manolin use for modeling and analysis?

Manolin can work across biological, environmental, operational, health, feeding, treatment, laboratory, and other relevant production data. The exact combination depends on the question being analyzed and the data available.

Can our data team access Manolin through an API?

Yes. Manolin can provide structured aquaculture data through API access for organizations that want to use it within their own analytics, applications, reporting, or internal workflows.

For Watershed farm users, can Manolin be used across different fish species?

Yes. Manolin’s platform is species agnostic and is designed to work across aquaculture species. We already work with production data from species including salmon, trout, king salmon, sea bream, and barramundi.