Electricity and data budgets need the full equipment list and a clear distinction between continuous video and uploaded event images.
Estimate electricity from every powered component and network usage from the proposed data path. Cameras, illumination, processors, switches, modems and cabinet equipment all count; a dual-camera lane description is too broad to establish one monthly utility bill.
For communications, distinguish continuous video, event images and metadata. Storage, upload frequency and cellular allowances need their own assumptions, ideally checked against a representative trial before applying the site's electricity tariff or communications contract.
A camera-and-recorder design links network demand to the video being retained. Local recognition and event-led workflows introduced another path: processing near the camera and transmitting selected observations rather than treating every image as an uploaded stream.
Power planning still follows the complete electrical installation. Network planning follows where video is processed, stored and transmitted, which means local video traffic and externally uploaded events need separate treatment in the same equipment and communications budget.
Event images and metadata may be enough for an observation workflow if the intended task and retention requirements allow it. Another installation may need continuous video. Choose the data arrangement before estimating the required connection or remote power supply.
Measured consumption is particularly relevant when budgeting utilities or sizing a remote supply. The cameras alone do not describe the processor, illumination, networking equipment, other loads or backup losses that the proposed installation will need to support.
Illustrative loads, not device specifications: two 12 W cameras, a 30 W processor, 10 W switch, 6 W modem and 20 W illumination total 90 W. Continuous operation for 30 days uses 64.8 kWh, costing AUD 19.44 at an assumed AUD 0.30 per kWh before other loads and losses.
For a separate upload example, 1,000 daily events with two 200 kB images each generate roughly 12 decimal GB in 30 days before metadata and overhead. Continuous traffic at 1 Mbit/s is roughly 324 GB over the same period before overhead, showing why these are different budgeting assumptions.
RackLink processes supported RTSP streams on the local network, while other Aero Ranger paths connect structured events. The proposed deployment therefore needs a clear account of which data stays local and which records pass into the operational workflow.
Local processing still requires power and network resources. Compare the chosen data path with the actual observation task, using measured loads and traffic where possible rather than inferring the utility bill from the number of cameras.
Aero Ranger RackLink: local RTSP processing
Sources were reviewed on the publication date. Check the linked material for current details.
