CEFAS26-115 ITT for a Small Autonomous Underwater Vehicle

Overview

Cefas currently uses hand deployable multi-parameter sondes (CTDs) for collecting water column data. With the advent of easy-to-use small AUVs we wish to supplement these programs with more autonomous data collection. We envision a platform which will collect data comparable with our current instruments, which can also operate fully autonomously for a period of hours while our staff conduct other activities. 3. Technical Requirement Cefas require one small autonomous underwater vehicle equipped with biogeochemical sensors to supplement our water quality monitoring efforts. 3.1 The vehicle will be capable of collecting marine biogeochemical observations to a depth of 250 m. 3.2 It will weigh no more than 20 kg in air and will be deployable by a single person by hand, from shore or small vessels. 3.3 It will be fitted with sensors meeting the following specifications. 3.3.1 Temperature: Range: 0°C to 35°C Initial accuracy: ±0.01° Resolution: 0.0005°C Time constant: ~1s Typical stability: < 0.002°C per year 3.3.2 Conductivity Range: 0–85 mS/cm Initial accuracy: ±0.003 mS/cm Resolution: 0.001 mS/cm Typical stability: < 0.02 mS/cm per year 3.3.3 Oxygen concentration Range: 0–500 µM Initial accuracy: ±2 µM Resolution: 0.1 µM Time constant: < 8 s Typical stability: < 0.5 % per year 3.3.4 Chlorophyll-a fluorescence 3.3.5 Optical backscatter / turbidity 3.3.6 The following optional sensors are of value: • fDOM • Photosynthetically active radiation (Cosine) 3.4 It will be capable of maintaining a fixed depth from the seabed. 3.5 It will be capable of repeatedly navigating a saw-tooth transect mission plan in the presence of horizontal currents up to 2 knots, while maintaining navigation performance. 3.6 It will have an endurance of no less than 5 hours under the stated conditions in this Specification. 3.7 Mission planning will be possible via software graphical user interface. 3.8 Surface communications will be provided; VHF or Iridium SBD are acceptable. 3.9 The vehicle will be fitted with high-visibility markings and means of surface location and recovery. 3.10 The vehicle’s software will have safeguards to prevent the operation of a dangerous mission plan. e.g. a maximum depth specified beyond the capabilities of the vehicle. 3.11 The vehicle will have an abort-mission procedure to safely return the vehicle to the surface when it encounters an issue with its navigation, internal monitors or sensors. 3.12 Data should be easily downloadable from the vehicle, and the process take no more than a few minutes. 4 Environmental Considerations 4.1 The system should have a low power consumption. 4.2 The system should be designed for reuse/remanufacture and of regenerative nature to eliminate waste where possible. 4.3 Consideration of how packaging will be managed. Ideally at the time of delivery and/or installation the Supplier will remove packaging and dispose of by ethical and environmentally friendly methods. Where possible packaging is to be re-used or recycled. 4.4 Consideration of life cycle assessment for the equipment. 5 Hardware, Software, PC, Licenses, operating systems 5.1 Any software required to operate the vehicle will be compatible with Windows 11 operating system, built in line with NCSC guidance and updates available for the lifetime of the machine. 5.2 Any software licences required for the operation of the vehicle will be a one-off purchase only and not be as a subscription service. Please confirm this in your response and include all one-off costs in Appendix 6 – Pricing Schedule. 5.3 If a cloud-based service is required to operate the vehicle or manage its data, demonstrate how our data would be kept secure. Any cloud servers must be located within UK or Northern Europe. 5.4 Details of the proposed data transfer method(s) between the vehicle, operating software and user are required, including any internet connection or remote access needed. 5.5 It will operate without an internet connection. At a minimum, the vehicle mus