Home / Cities and public spaces / Tender specification

Smart city video analytics tender specification for agencies and integrators.

This smart city video analytics tender specification gives vendor-neutral clauses to copy into a bid.

Smart city video analytics tender specification test: a stopped vehicle detected in a junction keep-clear box

Functional requirements

ClauseRequirementSpecification
R1Camera inputWorks with existing IP cameras over RTSP and ONVIF, directly or through the agency's VMS or NVR, with no camera replacement.
R2Use casesDetects the use cases listed in Annex A, each switched on per camera and per time of day.
R3AlertsAlerts named roles by mobile app, SMS, Microsoft Teams, email, dashboard and API, with the clip and camera. At the 95th percentile, an alert arrives within seconds of the event.
R4EscalationEscalates unacknowledged alerts on a schedule the agency sets per case type.
R5Case routingCreates a case for each event and routes it to the team or contractor that owns the place and issue, by API into the work-order system.

Closure and record requirements

ClauseRequirementSpecification
R6Case closureRe-checks the same camera view and closes the case only when it shows the issue resolved, storing the closing photo.
R7PrivacyPerforms no biometric identification and stores no face templates. Exports blur faces and plates by default; only an authorised role can export unblurred, with the purpose logged under R9.
R8ReportingProduces weekly reports per contractor with cases raised, closed on camera and days to close, approved by an officer.
R9AuditLogs every view, search and export with user, time and purpose.
R10ResilienceDetection, recording and on-site alerts continue through a network outage, and remote alerts send when the link returns.

Deployment options

Bidders price all three options.

OptionWhere processing runsFits
On premisesServers in the agency's data centreSovereign data, large camera counts
EdgeSmall servers near camera clustersLimited network links, remote sites
In-country cloudA partner's government-approved cloudFast start, opex budgets

Data handling

TopicClause
Data locationVideo and case data stay in-country, on infrastructure the agency approves.
RetentionThe agency sets retention per data type; case clips are deleted when it expires.
AccessRole-based by area and camera; contractors see their own cases only.
EncryptionEncrypted in transit (TLS 1.2 or higher) and at rest (AES-256).
LawThe bidder complies with the agency's data law, such as Singapore's PSGA or Saudi Arabia's PDPL.

Acceptance tests

Every test runs on the agency's own cameras or footage. The agency sets each value marked before the tender is issued.

TestNameMethodPass condition
T1Detection on agency footageBidder runs on 20 hours of agency footage with events pre-counted by the agency.For each Annex A use case, recall of at least % and at most false alerts per camera per day
T2Alert time staged events on three live cameras.At the 95th percentile, the named role receives the alert within seconds of the staged event
T3Case closureStaged event cleared on camera.Case closes with the photo from the same camera
T4Offline operationLink to the dashboard cut for 2 hours.Behaves as clause R10, with no events lost and the alert backlog delivered within minutes of the link returning
T5PrivacyFive clips with people and vehicles exported by a standard user and the authorised role.Standard exports blurred; only the authorised role exports unblurred; every export logged with its purpose

Annex A use cases

The agency sets each marked value and deletes unused rows.

Use caseEvent definitionConditionsClosure condition
Traffic incidentsVehicle stopped in a live lane or keep-clear box over seconds, or debris in a laneDay and nightLane clear
Illegal parkingVehicle in a no-parking zone, bus lane or loading bay over minutesHours set per zoneZone clear
Crowd densityOver people per m² in a marked area for minutesNo identificationDensity below the level
Public safetyPerson on the ground over seconds, or entry to a closed areaHours set per zoneOfficer closes with a note
Illegal dumpingWaste of m² or more outside a bin point over minutesHotspots drawn per cameraArea clear

Annex A use cases, continued

Use caseEvent definitionConditionsClosure condition
Overflowing binsWaste above the rim or beside a bin point over minutesBin points drawn per cameraBin point clear
Drains and floodingStanding water over % of a marked area for minutesDay, night and rainWater gone
Road damagePothole or crack cm or more across, or a works barrier downDaylightRepair shown
Visual pollutionGraffiti, fly-posting or abandoned items over m²DaylightItem removed
ParksClosed area entered after hours, litter or a damaged fixtureHours set per areaArea clear or fixture repaired

Revisions

VersionDateChange
1.07 Nov 2026First issue.
1.18 Nov 2026Pass values in R3, T1, T2 and T4; export blur in R7 and T5.
1.28 Nov 2026Annex A definitions; Annex B background.

Annex B background for the agency

The agency removes this sourced context before the tender is issued.

  • Saudi government tenders can weight local content in the financial evaluation, and supply and support through an in-Kingdom integrator count toward it.

    Source: Saudipedia, May 2023
  • Under Singapore's January 2026 Public Sector (Governance) Act amendments, external partners receiving shared government data take on duties equivalent to agencies.

    Source: Hogan Lovells
  • Saudi Arabia's Personal Data Protection Law has been enforceable since September 2024, with SDAIA as regulator.

    Source: Clyde & Co

Bid support for agencies and integrators

Partners get the architecture diagram, data sheet and a footage review for each bid.