Information checklist for site installation and documentation.
- Martin Munkeby
- Gøran Pedersen Krangsås
- Ivan Brissiuk
уove needs to collect this information for each site before installation.
Export this page to Word or PDF. You can also Copy this table to fill out the information in an email.
1. Site information
Checklist | Value |
|---|---|
Company | Collected by CageEye. |
Site name | Collected by CageEye. |
Site ID | Collected by CageEye. |
Shipping Adress | Collected by CageEye |
Travel Route | Plane: [Airport] |
Site coordinates | Collected by CageEye. |
Contact information to project owner for the customer. | Collected by CageEye. |
Number of cages: | Â |
Cage type | Ex. |
Net depht and type | Important to know what the wanted depth of our bottom sensor is, so we can prepare the sensor distance already in our production. |
Cage handrail vertical post type and diameter: | Ex. 120mm. Rectangular Steel, plastic. Ideally a picture and/or measurements. |
Power connector type at the cage | This is info that we use to produce the power cables, so we know we are able to power our equipment through your power cabinet on cage. |
Power cable length needed from power supply cabinet to CageEye cabinet. | Our standard solution is 25m. We strongly recommend reading this document to get a better understanding of the limitations. |
Cage-fuse for our equipment | We require a fuse (6-16A). Usually the fuses are directly connected to the power outlet of the power distribution cabinet on cage. |
For wired network to Akva CAP: | More details on AkvaCAP/CageEye-network cable: Here. |
Antenna mount on barge roof | We want pictures of the roof, showing where we can physically mount the antenna. We also want a picture showing the cage-view from this position to identify and solve potential issues. Document with specific details. |
Antenna-to-inside-barge cable | We have to pull a outdoor network cable from the antenna to inside the barge (where our network equipment will be). To do this effectively, we need to know the route. The best way to give us information is by providing pictures showing the route, and what cable length we need to bring. |
Contact information to personnel at the site and shift information. | Barge control room: [Phone] [email] Used to reach the person siting in the control room at any given time. Site manager: [Name] Â Â Â Â Shift 1 Even week number.
Shift 2 Odd week number.
 In case of outage event outside working days, who do we call:
|
Feeding center address and contact info: | Â |
Contact information to IT department responsible for the site | IT:Â [Name], [role] [phone] [email] |
Contact information to operational technology(OT) department responsible for the site | OT:Â [Name], [role] [phone] [email] |
Population data | Cage 1 number of fish: Cage 2 number of fish: |
Pipe lengths to cages: | Cage 1: |
Fish group id | Cage 1: |
Farm server | Model: Ex Advantec. Mic 770 v2. |
Â
2. Network information
Checklist | Value |
Should we use CageEye VPN or the customer VPN to access the network? | Â |
Any special company policy or network security restrictions we should adhere to? | Â |
Is there DHCP or static IP adresses? | Â |
Which subnet/VLAN is the feeding system on? | Â |
Internet traffic or speed limited? | Â |
Tested network upload speed | Â |
Tested network download speed | Â |
Packet loss % tested. | Â |
3. Feeding system information
Checklist | Document |
|---|---|
Feeding system supplier | Â |
Contact information to the feeding system supplier | Â |
Collected by CageEye from feeding system supplier: Configuration parameters for integration | Â |
The version of the feeding system software | Collected by CageEye. |
Cage 1 unique ID in feeding system: | Collected by CageEye |
ID | Collected by CageEye and stored securely. |
Token | Collected by CageEye and stored securely. |
Password | Collected by CageEye and stored securely. |
URL | Collected by CageEye. |
Ports to use | Collected by CageEye. |
IP-addresses | Collected by CageEye. |
API endpoint | Collected by CageEye. |
Â
Â