Let's connect
Articles
Digital Infrastructure

Smart city infrastructure starts with the workload

Smart city projects often start by buying servers. They should start by describing the work those servers will do. Cameras, analytics, access events and applications each place a different load on the infrastructure underneath.

Start with what the system will carry

Before choosing hardware, write down the workload:

  • How many cameras, at what resolution, and for how many days video must be kept
  • Which analytics run, and on how many streams at once
  • Access control events, alarms and sensor data
  • The applications and databases that sit alongside them
  • Who needs to see what, from where, and how quickly

That description, not a product catalogue, decides the design.

Put compute at the edge where decisions must be fast

Roadside cabinets, campus buildings and remote sites benefit from local compute that runs analytics close to the cameras. Decisions happen on site, only events and selected video travel upstream, and the site keeps working if the network link drops. Rugged edge servers such as Dell PowerEdge XR are built for these locations.

Keep the core for retention, search and command

The data centre holds what must be kept and searched: video archives, evidence, databases and the command platform itself. Storage is sized from retention rules, not guesses, and is designed so investigators can search months of footage quickly.

Design the network and resilience together

Video and access systems are only as reliable as the network between them. Plan bandwidth from the edge, redundant links for critical sites, and failover for the servers that run the command platform. Decide in advance what keeps working when a component fails.

Run it as a single system

Infrastructure is not finished at handover. Monitoring, patching, firmware, capacity planning and vendor support need an owner. LaQuest designs, deploys and operates Dell infrastructure in an integrated environment with the video, access and application platforms above it, with clear ownership from the data hall to the roadside.

Five questions to ask before you buy

  1. What is the workload today, and in three years?
  2. What must run at the edge, and what can run centrally?
  3. How long must data be kept, and who needs to search it?
  4. What happens when a link, server or site fails?
  5. Who operates the system once it is live?
Keep reading

More from the practices.

Want a briefing for your team?