Site readiness for edge processing: power, network and mounting

Edge processing moves video analysis out of a distant data centre and onto equipment installed at the site. Video is analysed close to where it is captured, and the operator experience works from structured events rather than continuous streams. On-site processing can reduce dependence on the uplink; document what remains available during an outage and how queued events recover. What else leaves the site, if anything, is agreed with each customer.

It also means the site has to host that equipment well. A compute unit in a hot cabinet with no surge protection and a shared network port will cause more trouble than any software setting. This guide covers the physical questions facilities and IT teams should answer before installation day. None of it is exotic: it is the discipline you would apply to a camera system or gate controller, written down so nothing is left to the morning of the install.

What edge processing means on the ground

Physically, an edge deployment has three parts:

• Cameras, existing or new, positioned to see the zones that matter. Coverage is its own subject; see planning camera coverage for vehicle lots.
• On-site compute that receives camera streams over the local network and turns them into structured events: a vehicle entered a zone, a row is full, movement in a closed area.
• An uplink from the site to the operator experience, carrying events, device health and remote management traffic.

The compute can live in one of three kinds of place, each with its own trade-off:

Comms room

Easiest to cool, power and secure. Long cable runs to distant poles add cost and points of failure.

Service-building cabinet

Closer to the lot, usually with power nearby. Check ventilation and who else has a key.

Pole enclosure

Shortest runs to the cameras it serves. Takes on heat, weather and harder maintenance access.

Many sites use a mix. Decide early, because power, network and mounting all follow from where the equipment lives.

Power

Edge equipment needs clean, continuous power, often in places that were never designed with electronics in mind.

Circuits

Identify the circuit that will feed each equipment location and confirm it has capacity for the new load. A dedicated circuit for network and compute equipment is cleanest. At minimum, avoid sharing with gate motors, vehicle lifts, wash bays or lighting contactors, which switch heavy loads and introduce electrical noise. Pole power often follows lighting circuits that a timer or photocell switches off during the day; confirm the feed is live around the clock, or plan a separate one.

Surge protection and grounding

Tall poles and long outdoor runs invite surges from lightning and utility switching. Plan protection at the panel, at each enclosure and on network cabling that runs between buildings or up poles, with proper grounding and bonding throughout. Your electrician will know the local code; the point is to put it in scope rather than add it after the first storm.

Backup power

A UPS carries compute and network gear through brief interruptions and lets it shut down cleanly in a longer outage, which protects storage and avoids a messy restart. Decide what it must cover: the compute alone, or also the switch, the uplink router and any cameras powered from that switch. If cameras draw power over the network cable, that switch is a single point of failure for every camera on it, so give it headroom and include it in the backup plan. Batteries age, so put replacement on the maintenance calendar and connect the UPS status to monitoring. Outdoors, choose backup equipment rated for the temperatures it will see.

Network

The edge unit talks to cameras on the local network and to the outside world for events, health and management. Give both paths the care you would give a building management system.

Segmentation

Put cameras and edge equipment on their own segment, typically a dedicated VLAN, separated from guest Wi-Fi, office workstations and point-of-sale systems. Cameras should reach the edge unit and nothing else; the edge unit should reach the cameras and its approved outbound destinations, and nothing else. Segmentation limits the damage if one device is compromised and makes troubleshooting far easier.

Outbound-only where possible

Prefer designs where the site opens every connection outward and no inbound firewall ports are needed. Events, health reports and remote management can all travel over connections the edge unit initiates. If your policy requires a proxy, an allow-list of destinations or a VPN, agree on it during planning so the install does not stall on a change request.

Remote management

Most issues can be handled remotely: an update, a restart, a configuration change, a look at device health. Agree on who may do that, how access is authenticated and logged, and how your IT team is kept informed. Remote access should be visible and revocable, never a standing back door.

Failover

Decide what happens when the uplink drops. Because analysis happens on site, the design can keep working locally and hold events for delivery; agree how long, and test recovery before launch. Where continuous visibility matters, consider a secondary uplink, such as cellular, and decide which traffic it carries. Test failover once, deliberately, during installation rather than learning how it behaves in the first real outage.

Mounting, conduit and enclosures

Where cameras and equipment are fixed decides what they can see and how long they last.

Poles

Existing light poles are convenient but can sway in wind, which degrades camera views, and may not suit added weight or cabling. Confirm suitability with the pole owner and whether a landlord or lighting contractor must approve changes. Dedicated poles cost more but go exactly where coverage needs them.

Building faces

Walls and parapets give stable mounting and easier access to power and network. Check what is behind the wall before drilling, how cables will enter the building and whether roof penetrations need approval.

Conduit

Run outdoor cabling in conduit suited to the environment, with pull strings left for future runs, and seal every entry so conduit never becomes a water channel. Trenching is expensive to repeat: if the ground is open for another project, add spare conduit.

Enclosures

Choose enclosures rated for the weather and dust they will face, with room for equipment, cable management and airflow. Mount them high enough to deter tampering but where a technician can safely reach them, and label each one on the outside.

Heat, dust and rain

Electronics fail early when they run hot, wet or dirty. Judge each location by the worst week of the year, not the day of the survey.

• Heat. A dark enclosure in full sun gets far hotter inside than the surrounding air. Prefer shade, sun shields or light-coloured enclosures, and ventilation or active cooling where needed. Small comms closets with no air movement overheat too.
• Cold and condensation. Temperature swings cause condensation inside sealed boxes. Breathable vents or a small heater may be needed in cold or humid climates.
• Dust. Lots near roads, construction or unpaved ground coat lenses, filters and fans. Filtered ventilation and a cleaning schedule keep views clear and equipment cool.
• Rain and irrigation. Check drainage below enclosures and the reach of sprinkler heads. Bring cables in from below with drip loops so water runs off rather than in.
• Coastal and industrial air. Salt and chemicals corrode fixings and connectors; specify corrosion-resistant hardware where it applies.

Physical security of the equipment

The equipment that watches a lot should not be the easiest thing on it to tamper with.

• Lock enclosures and cabinets, and keep a record of who holds keys.
• Mount cameras and enclosures out of easy reach, and protect exposed cabling with conduit or armoured covers.
• Keep compute in a locked indoor room where possible, or place outdoor enclosures within view of another camera.
• Treat a camera going offline or an enclosure door opening as an event worth reviewing.
• Disable unused switch ports on the camera segment, so plugging into an exposed jack grants nothing.

Access for maintenance

Everything installed will need attention eventually: a lens cleaned, a fan replaced, a cable reseated. Plan for it now.

• Note whether each location needs a ladder, a lift or a bucket truck, and whether vehicles must be moved to reach it.
• Agree on maintenance windows that avoid busy periods, and on how technicians check in on site.
• Keep spares of anything whose failure would take a zone out of view for long.
• Decide who on site can perform simple tasks, such as a power cycle under remote guidance, so a minor fault does not wait for a site visit.

Documentation and labelling

Good documentation turns a future fault from a hunt into a quick fix. Before sign-off, the site should have:

• A site plan showing every camera, pole, enclosure and compute location, with the zones each camera covers.
• A network diagram showing segments, switch ports, uplinks and allowed outbound destinations.
• A power map showing the circuit and breaker for each location and what the UPS covers.
• Labels on both ends of every cable and on every enclosure, matching the drawings.
• A contact sheet naming the owners of facilities, IT and operations decisions, the key holders, and who to call for each kind of fault.
• A record of what was agreed for this site on data retention, access and remote management.

Store it where both the site team and support can reach it, and update it whenever anything moves. Out-of-date drawings are worse than none, because people trust them.

Readiness checklist by owner

Use this as a starting point for a joint walk-through. An item is ready when its “done when” condition is met, not when someone believes it probably is.

Bring this checklist to a ParkSense site discussion, where camera coverage, network approach, retention and access are worked through for your site. The technology overview explains how edge processing and structured events fit together, and you can get in touch when you are ready to talk through your own site.