In short
Stable power on the cage and barge
Stable internet
Detailed requirements
These requirements define the optimal environment for Bluegrove CageEye systems. If any of the requirements are not met the Bluegrove CageEye service will be impacted as described in Impact of infrastructure loss at the end of this page.
Physical requirements
Minimum 15m deep nets.
Clear line of sight from barge roof to cages.
Power Requirements
1.1 Power at barge
The CageEye system requires 2 kW @ 230V 50hz at the barge.
The system complies with the international EMC standards:
IEC/EN 60950-1
IEC/EN 61000-3-3
IEC/EN 61000-6-1
IEC/EN 61000-6-3
In case of power source problems such as noise, spikes, brownouts and blackouts, an Online UPS system needs to be installed to accommodate continuous power stability and availability.
1.2 Power at cage
...
2. Network Requirements
...
2.1 Barge local network
Ethernet 802.3ab compatible connection available for all barge services.
Required network performance to provide optimal services:
...
Service
...
Bandwidth
...
Uptime
...
Latency
...
Packet Loss
...
Jitter
...
Network services on barge
...
1 Gbit
...
100%
...
2 ms
...
0
...
15%
2.2: Cage to barge network
Ethernet 802.3ab compatible connection available for all cage services. Required network performance to provide optimal services:
Service | Bandwidth | Uptime | Latency | Packet Loss | Jitter |
Network services on cage | 200 Mbit | 100% | 5 ms | 0 | 15% |
Bandwidth, uptime, latency, packet loss and jitter between devices on barge network and devices on cage.
2.3a: Internet
Services dependent on dedicated internet connection bandwidth with minimum requirements:
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Analytics and reports | 1 Mbps | 90% | 150 ms | 5% over 10 minutes | 15% |
Cloud data API | 1 Mbps | 90% | 150 ms | 5% over 10 minutes | 15% |
Feeding algorithms | 1 Mbps | 90% | 150ms | 5% over 10 minutes | 15% |
Upload bandwidth, uptime, latency, packet loss and jitter between devices on the barge network and Bluegrove Cloud.
If the internet subscription has a monthly limit for traffic we need 100 GB a Month.
Ports used by Bluegrove
...
Type
...
Port
...
Used for
...
Traffic
...
TCP
...
1194
...
VPN for access to Bluegrove cloud.
...
Incoming and outgoing
...
TCP
...
80
...
HTTP outgoing for connection to API. Eg environmental data.
HTTP incoming to be able to connect from the feed center.
...
Incoming and outgoing
...
TCP
...
443
...
HTTP outgoing for connection to API. Eg environmental data.
HTTP incoming to be able to connect from the feed center.
...
Incoming and outgoing
6b: Barge to Feeding Operations Center network
Services dependant on dedicated network connection bandwidth with minimum requirements:
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Feeding assistant (remote, without video) | 5 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
Feeding assistant (remote, with video) | 30 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
Upload bandwidth, uptime, latency, packet loss and jitter between devices on the barge network and the Feeding Operations Center.
Integration Requirements
The customer must to provide Bluegrove with an integration to his feeding system. Bluegrove maintains this list of compatible feeding-systems: Feeding-system integrations and compatibility with Bluegrove.
3.1 Operational feeding system integration
3.1.1 High level feeding system requirements
Feeding system requirements version 0.0.6. This section defines general requirements for controlling a feeding system for sea-based and land based aquaculture.
Intention
Enable the fish farmer to:
Maintain high uptime of its feeding processes.
Safely enable interaction between applications while minimizing risk of service outages.
Procure, replace or remove software from any vendor in a modular way.
Maintain high data and operational security
Get early warning about errors and the possibility of investigation through logging.
Enable access on an individual level, and integrate with the company's userdirectory.
Maintain robust local feeding operations with unreliable internet.
Enable remote control of feeding operations at different sites with full functionality without the use of VPN.
Enable control of feeding operations on one user interface, regardless of feeding system vendor.
Enable frequent and high-resolution data collection from feeding operations.
Safely control feeding operations remotely with no or unstable internet.
Enable scale in the data collection by using good practices like “Report by exception/change” and avoiding polling.
Definitions
...
Unit: The unit where feed is dispensed to the consumers. Example: Cage or tank used in aquaculture.
Feeding system: The machinery/installation which executes the feeding. Feeding barge at sea. Example: Land based feeding installation.
Feeding control system: The industrial control devices controlling the machinery in the feeding system. Example: The PLC controlling the feeding system. The server controlling the PLC.
Feeding Line: The feeding system internal feeding line. in the control system. Feedlines can sometimes be routed to different pipes by "changers". Example: Feeding line inside a barge connected to a blower and one or more feed silos.
Pipe The pipe or conveyor to transporting the feed from the feeding system to the place where it will be consumed. Example: The feed pipe from a barge to a cage.
Out of scope features
Feeding tables. A plan for dispensing feed over time. Often provided by the Feeding control system or feeding application.
Automatic feeding. A configurable plan for dispensing feed over time which is executed by the feeding system. Often provided by the feeding control system.
Biological data. Data on species, number of fish, weight, mortality etc. Often provided by the Feeding control system, ERP or planning tools.
Calibration of feeding dosers. Calibration of dosers to dispense the correct amount of feed. Often provided by the Feeding control system.
Line configuration. An operation that moves a pipe from one cage to another. The operator then updates it in one system, which then makes it available to other systems by API. Often provided by the Feeding control system.
Dosing of feed. The industrial control system achieves the desired intensity by operating the dosing machinery. Often provided by the feeding control system.
Silo management. Used for selecting type of feed. Often provided by the Feeding control system.
Required functionality:
Feeding Mode
Enables switching between manual and automatic feeding.
Set Intensity
Sets the feeding intensity for a pipe.
Alarm Warning Or Stop Message
Alarms, Warnings, or stop messages from the feeding control systems.
Feeding Lines Avaliable
Lists the available units(cages) avaliable to each feeding line, by changer or directly connected.
Enable And/Or Change Feed Line To Conveyor
Operates the changers to connect one line to the selected pipe.
Feedline Status
Describes which pipe(cage) the feedingline in the feedingsystem is connected to. Also gives the status of the feedline.
Feedline Blower Level
The set power of blowing in percent from maximum of 100%. 0 when off.
Feedline Pressure
The pressure inside a feedpipe.
Feedline temperature
The temperature inside a feedline.
Feedline airspeed
The airspeed inside a feedpipe.
4. Barge and feeding system
4.1. User terminal at barge (PC with UI)
PC with at least 1 display screen per 12 cages: Minimum 24”, 1920x1080 resolution
Mouse/Keyboard
Chrome Browser
4.2. User terminal remote (PC with UI)
Optional remote PC with at least 1 display screen per 12 cages: Minimum 24”, 1920x1080 resolution
Mouse/Keyboard
CageEye VPN Installed
Chrome Browser
4.3. Operational feeding system
The blowers, dosing, changers, piping, feed spreaders need to be in working condition.
4.4. Farm environmental sensors - Required for analytics and reporting
Sensors at farm:
Oxygen
Salinity
Temperature
Water-current
Weather
5. Machine vision for pellet detection and health indicators.
5.1. RTSP streams
RTSP streams from the camera available on the network we have access to.
Relation between RTSP stream and cage
6. Impact of infrastructure loss
Impact category | Example effect |
Emergency | Immediately stops service |
Severe | Critically impacts service/stops service within one day |
Moderate | Impacts service/partial loss of service |
Minor | Reduced convenience |
...
Requirement
...
Effect on service
...
Suggested Solution
...
Barge and feeding system
...
1.1 Power at barge
...
Emergency
...
2KW Online UPS
...
2.1. Barge local network
...
Emergency
...
Managed network service including ubiquiti router, network cables, installation and configuration.
...
3.1. Operational feeding system
...
Emergency
...
4.2. User terminal at barge (PC with UI)
...
Severe
...
4.1. Farm environmental sensors
...
Minor
...
Remote
...
2.3a. Internet
...
Severe
...
Primary and redundancy options:
Point-to-point ethernet backhaul
Satellite network
4G mobile network
...
4.3. User terminal remote (PC with UI)
...
each point.
Related documents:
Environmental parameter limitations: EN/NO/ES Environmental parameters limtiations / Grenseverdier for bruk / Límites de exposición ambiental
1 Physical requirements
1.1 Limitations in use/performance with other specific components
Main components
Component | Problem | Solution |
|---|---|---|
Cage type: | (2).png?version=1&modificationDate=1687513209497&cacheVersion=1&api=v2) Conflict between the top bracket fixture and the handrail post. | Use stainless ratchet straps or rope to tie the top part of the bracket to the pole. |
Extra equipment
Component | Problem | Solution / Løsning |
|---|---|---|
Aeration devices that makes airbubbles inside the cage. Sold under names like(Midt-Norsk ring, Turbolift etc) | The echosounder picks up the bubbles and it creates a noisy image of the fish. | Echosounders are not compatible with aeration devices. |
Aside from these components, the equipment is compatible with any other component that is not directly interfering with it. It is compatible with predator nets.
1.2 Cage requirements
Minimum 15m deep nets, which gives a 13m sensor head distance.
1.2.1 Coverage for different cage sizes:
| Expand | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Performance is mainly affected by how well the sensors cover the feeding zone.
1.5 Operational feeding system with integration.
CageEye is compatible with these feeding systems. The blowers, dosing, changers, piping, feed spreaders need to be in working condition.
| Info |
|---|
What happens if the requirement is not met: You will not get feeding data and you might not be able to feed. |
2 Power Requirements
2.1 Power at barge
The CageEye system requires 2kW @ 230V 50hz at the barge.
The system complies with the international EMC standards: IEC/EN 60950-1, IEC/EN 61000-3-3, IEC/EN 61000-6-1 and IEC/EN 61000-6-3.
A ground fault circuit interrupter must be used.
In case of power source problems such as noise, spikes, brownouts and blackouts, a UPS system needs to be installed to accommodate continuous power stability and availability.
| Info |
|---|
What happens if the requirement is not met: Service stops as soon as the power to the server and antenna is broken. This is mitigated by using a UPS(battery). |
2.2 Power at cage
Estimated continuous power requirements for all sensor devices in cage: 60 W.
The CageEye system requires 60 W @ 230V 50hz outlet at the cage. The power supply must have a C16A or a D16A circuit breaker. A ground fault circuit interrupter must be used.
| Info |
|---|
What happens if the requirement is not met: Service stops as soon as the power is interrupted. This is mitigated by using a UPS(battery). |
3 Network Requirements
CageEye uses two operating models. Customer managed network, and unmanged network.
3.1 Unmanaged networks
CageEye will install a server on the barge that needs to be on the same network as the feeding systems and the feeding cameras. Remote connections to operations centers can be set up in cooperation with the customers technical staff. CageEye needs to use radios to communicate with the sensors on the cages.
...
3.1.0 Ports used by the CageEye server
Type | Port | Used for | Traffic |
TCP | 1194 | Communication through OpenVPN with CageEye cloud servers; and remote servicing. | Incoming and outgoing |
| Info |
|---|
What happens if the requirement is not met: Dataflow and remote services are interrupted. Data is buffered for some time until recovery. |
3.2 Managed networks
For a detailed requirements for operating in customer managed networks see this page. [Private]https://bluegrove.atlassian.net/wiki/spaces/TRB/pages/1305903173/Bluegrove+Cybersecurity+practices#Operating-in-customer-managed-networks. Ask a CageEye representative to get access to this page.
3.3 Optional: Cage to barge network with radio.
If no cage to barge network is available, CageEye can set up a cage to barge network with radio. We typically use the 5GHz band. We use Ubiquity Rocket AC on the barge, and Ubiquity Bullet AC on the cage.
We configure the radio to use given frequencies between 5190-5940 GHz, alternatively the radio can be configured to automatically seek out new frequencies detects interference.