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 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.
...
PC with at least 1 display screen per 12 cages: Minimum 24”, 1920x1080 resolution
Mouse/Keyboard
Chrome Browser
| Info |
|---|
What happens if the requirement is not met: You are unable to use the system locally on the barge. |
1.4 PC for remote access
Optional remote PC with at least 1 display screen per 12 cages: Minimum 24”, 1920x1080 resolution
Mouse/Keyboard
CageEye VPN Installed
Chrome Browser
| Info |
|---|
What happens if the requirement is not met: You are unable to use the system remotely. |
1.5 Operational feeding system
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 are unable to feed. |
1.6 Farm environmental sensors - Required for analytics and insights
Sensors at farm with API.
Oxygen
Salinity
Temperature
Water-current
Weather
| Info |
|---|
What happens if the requirement is not met: You do not get access to this data in the Bluegrove systemwill not get feeding data and you might not be able to feed. |
2 Power Requirements
2.1 Power at barge
The CageEye system requires 2 kW 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, an Online 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 10A or 16A fuse.
Estimated continuous power requirements for all sensor devices in cage: 60 W
Estimated maximum power consumption in the future 500 WC16A 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
...
3.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%
| Info |
|---|
What happens if the requirement is not met: Remote services are interrupted. Data is buffered for some time until recovery. |
3.2 Cage to barge network
Clear line of sight from barge roof to cages. 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.
| Info |
|---|
What happens if the requirement is not met: Services are interrupted. Data is buffered for some time until recovery. |
3.3 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.
...
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 |
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 centerCommunication through OpenVPN with CageEye cloud servers; and remote servicing. | Incoming and outgoing |
443
HTTP outgoing for connection to API. Eg environmental data.
HTTP incoming to be able to connect from the feed center.
Incoming and outgoing
| Info |
|---|
What happens if the requirement is not met: Remote Dataflow and remote services are interrupted. Data is buffered for some time until recovery. |
3.
...
Services dependent on dedicated network connection bandwidth with minimum requirements:
...
Service
...
Upload
...
Uptime
...
Latency
...
Packet Loss
...
Jitter
...
Feeding (remote, without video)
...
5 Mbps
...
100%
...
150 ms
...
1% over 10 minutes
...
15%
...
Feeding (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.
| Info |
|---|
What happens if the requirement is not met: Remote services are interrupted. Data(not video) is buffered for some time until recovery. |
4 Integration Requirements
4.1 Operational feeding system integration
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
| Info |
|---|
What happens if the requirement is not met: Feeding service is interrupted. Data collection on feeding is interrupted. |
4.1.1 For developers: General feeding system integration requirements
| Expand | ||
|---|---|---|
| ||
Feeding system requirements version 0.0.6. This section defines general requirements for controlling a feeding system for sea-based and land based aquaculture. IntentionEnable the fish farmer to:
Definitions.png?version=1&modificationDate=1687597310821&cacheVersion=1&api=v2)
Out of scope features
Required functionality:
|
6 Machine vision for pellet detection and health indicators.
6.1 Video streams in the RTSP protocol
RTSP streams from the camera is available on the network we have access to.
Information on the which stream belongs to which cage.
...
What happens if the requirement is not met:
...
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.