Skip to content

Cities don't fail from lack of data.
They fail from systems that can't act on it.

Every department has a dashboard. No department has the full picture.

4hr

Water main broke Tuesday. Public works found out from Twitter.

Infrastructure failures are discovered by citizens, not by the system that manages the infrastructure. The gap between event and response is measured in hours, not seconds.

5 silos

5 departments. 5 budgets. Zero shared view of infrastructure.

Water, fleet, facilities, streets, and waste each operate their own systems, their own budgets, their own reporting. Nobody has a cross-department view of what is failing, what is overdue, or where resources overlap.

$4.2B

IIJA grant requires measurable outcomes. You have spreadsheets.

Federal grants demand auditable evidence of infrastructure improvement — spending per milestone, outcome measurement, equity tracking. Your proof is assembled manually, months after the fact.

6wk

Pothole reported 6 weeks ago. Citizen called the mayor.

A citizen request enters the system and disappears into a department queue with no SLA tracking, no status visibility, and no automated follow-up. The next touchpoint is a complaint to elected officials.

The gap is not another smart city dashboard. It is that your infrastructure — pipes, vehicles, buildings, signals — was never digitally alive enough to report its own condition, trigger its own repair, or prove to a federal auditor that the money worked.

Warehouse 7 — Aisle 4
Cold Unit A3
Temp36.2°F
Humidity42%
CompressorNormal
Dock 7 Inbound
ETA2.4 hrs
Load94%
Pallets18
Aisle 12-B
SKUs1,847
Picks23/min
Errors0.1%
Pallet CC-09
Weight1,240 lb
ZoneBay 4-C
Dwell12m
Freezer Unit 2
Temp-8.1°F
DoorSealed
AlertNone
Forklift 14
StatusActive
Battery67%
ZoneC-North
RFID Gate 3
Reads412/hr
Miss Rate0.3%
Uptime99.8%
Rack G-22
Capacity83%
Last Scan4m ago
Items246
Vision Bay 6
Defects0.02%
Throughput148/min
Accuracy99.7%
0 / 9 tracked
Signal Lost
All Connected
Ask ArgusAI Assistant
ArgusIQ

HOW WE DO IT

One Operating System. Built for the complexity of city operations across every department you actually manage.

Not another dashboard feeding another department. A complete operational foundation — connectivity, identity, workflows, and AI — that makes every city asset digitally alive and every condition change, dispatch, maintenance event, and citizen response a governed, automatically recorded transaction.

Step 1

Locate & Sense

Every water main, pump station, pressure zone, and meter — tracked by flow, pressure, and condition. Every streetlight, traffic signal cabinet, and electrical panel — tracked by circuit status, power draw, and fault state. Every fleet vehicle across police, fire, public works, parks, and solid waste — tracked by location, utilization, and maintenance condition. Every waste bin, recycling container, and collection route — tracked by fill level and service state. Every city building, HVAC system, and energy meter — tracked by environmental condition and consumption pattern. IoT SimpleLink® deploys city-wide LoRaWAN infrastructure once — then enables every use case on the same network.

CITY ASSET NETWORK
Water meters (Zone 4–7)1,247 online
Streetlights (all circuits)3,840 monitored
Fleet vehicles142 tracked
Waste bins (fill sensors)340 active
Buildings (BMS linked)47 connected

Network: IoT SimpleLink® LoRaWAN — city-wide

Step 2

Normalize

Existing SCADA outputs, fleet GPS feeds, BMS data, meter readings, citizen 311 inputs, GIS layers, ERP records, and data from any sensor or system already deployed — we ingest it all into one consistent operational model. No rip-and-replace. No vendor lock-in. Every existing investment becomes part of the unified view instead of another silo.

DATA NORMALIZATION
SCADA (water/sewer)Mapped
Fleet GPS (4 vendors)Mapped
BMS (3 platforms)Mapped
311 / Citizen PortalIntegrated
GIS / ERPLinked

Vendor protocols: 18 | Unified: ✅

Step 3

Digitalize

Once connected, every asset gains a digital identity — a governed record of what it is, where it has been, every condition reading, every maintenance event, every work order, every inspection, every citizen interaction, every compliance record, and every exception. The asset’s digital twin is not a visualization. It is the operational truth layer that every workflow, every dispatch, and every report is built on.

DIGITAL IDENTITY — Pump Station 7
Runtime (month)+22% above avg
Pump B vibrationTrending ↑
Last PM2026-01-18
Next PM (condition)Due now
WO-PM-0771Auto-created

Bearing replacement scheduled — low-demand window

Step 4

Run Operations on ArgusIQ™

ArgusIQ™ is the hub. Multi-tenant architecture gives each department — water, fleet, facilities, public works, waste, parks, public safety — its own dashboards, its own workflows, its own role-based access. City-wide rollup gives leadership one view across all departments. Built-in CMMS manages maintenance end-to-end. Ticketing and workflows orchestrate dispatches, citizen responses, compliance events, and cross-departmental coordination. ArgusOps provides the multi-department command dashboard for operations leadership.

ArgusIQ™ — CITY OPS HUB
Open WOs (city-wide)47 (12 auto-created)
Overdue7
Avg response time2.6h
Departments online6 of 6

Grant KPI: response time ↓ 34% vs. prior quarter

Step 5

Automate With AI and Orchestration

Ask Argus queries live operational data in plain language across every department: “Which pump stations exceeded runtime thresholds this month?” “What’s the average streetlight repair time this quarter vs last?” ArgusForge extends to new workflows — citizen reporting apps, seasonal operations programs, cross-departmental coordination processes — without new vendors or new silos. ArgusAI brings full AI on-premises for water treatment, power distribution, and emergency management environments where data cannot leave the network.

ASK ARGUS
Q: “Which assets have recurring faults across all departments?”
A: Pump Station 7 — 3 vibration anomalies (Water)
Circuit C-44 — 2 voltage events (Streetlights)
Capital replacement candidates: 2 | PM adjustments: 2

REAL OUTCOMES

You’ll recognise your city in these.

These are not hypothetical scenarios. They are the exact dispatch delays, unverified repairs, departmental coordination failures, and compliance gaps your teams navigate every day.

Play 1

Zone 4 pressure drops at 2am. In most cities, nobody dispatches until 9am. In yours, the crew is on-site by 3:10.

The Scene

Zone 4 pressure drops 12 PSI at 02:17 Tuesday morning. The anomaly is not a slow decline — it’s a step change consistent with a main break. In most cities, this alarm sits in SCADA until the morning shift reviews overnight logs at 07:00. By then, citizens in three neighborhoods have called about low water pressure. A crew is dispatched at 08:30. They arrive at 09:15 to find a condition that has been actively wasting water and eroding the road base for seven hours.

With Viaanix

ArgusIQ™ correlates the pressure drop with flow data from adjacent meters within 90 seconds. The system identifies the likely location — Zone 4, Sector C, between meters M-0447 and M-0451. A priority work order is created at 02:19 with the location, the severity classification, and the nearest crew availability. The on-call crew is dispatched at 02:35. They arrive at 03:10. The repair is complete by 05:45. The zone pressure recovers to normal by 06:15 — before the first citizen wakes up.

What Does Not Happen

Seven hours of active water loss. Road base erosion. Three neighborhoods calling about low pressure. The 9am dispatch to a problem visible since 2am. The citizen complaints and political exposure.

5 hours earlier detection → dispatch

WATER DISTRIBUTION — Zone 4
Zone 4 MainPressure −12 PSI
M-0447Flow normal
M-0451Flow +18%
WO-4471Created 02:19

Crew: Water Team B — ETA 35 min | Status: DISPATCHED

Play 2

The meter flagged its own tamper at 11:40pm. Revenue recovery started before the customer knew anyone noticed.

The Scene

Residential meter M-1247 reports a consumption pattern at 23:40 that is inconsistent with its historical baseline — sustained flow at a rate that exceeds the property’s typical peak by 340%. The pattern does not match a leak. It matches a bypass event — someone has interfered with the meter.

With Viaanix

ArgusIQ™ flags the anomaly as a tamper event. A security work order is created with the meter location, the anomaly signature, and photographic evidence from the last inspection. The field investigation is dispatched the following morning. Confirmed bypass. Revenue recovery initiated.

What Does Not Happen

Six months of undetected revenue loss. The meter that “seemed fine” because nobody was looking at consumption patterns at the individual meter level.

Tamper detection within hours, not months

Play 3

Pump Station 7 didn’t wait for failure. The bearing was replaced during a planned window — and the $23,000 emergency was avoided.

The Scene

Pump Station 7 has been running 22% above its historical average runtime this month. The vibration signature on Pump B has shifted — not catastrophically, but consistently, showing a pattern that precedes bearing failure by 2–4 weeks based on the asset’s maintenance history. In a calendar-based maintenance program, the next scheduled service is 6 weeks away.

With Viaanix

ArgusIQ™ identifies the runtime exceedance and the vibration trend. A predictive maintenance work order is created: WO-PM-0771, priority elevated, parts pre-ordered based on the likely failure mode. The technician replaces the bearing assembly during a scheduled low-demand window. Total downtime: 3 hours planned. Avoided downtime: 18–36 hours unplanned.

What Does Not Happen

The emergency pump replacement. The boil-water advisory risk. The citizen impact across three service zones. The emergency overtime. The $12,000–$25,000 unplanned repair vs. $1,800 bearing replacement.

$23K saved per prevented failure

Play 4

Seven streetlights went dark. Three separate crews were dispatched. One upstream repair would have fixed all seven.

The Scene

Seven streetlights on Commerce Avenue go dark within 72 hours of each other. Citizens report each one separately to 311. In a conventional system, each report generates a separate work order, and three separate crews are dispatched to three separate poles before anyone notices the pattern.

With Viaanix

ArgusIQ™ correlates the outages against circuit topology. All seven lights share a common upstream feed point — Panel CP-22. The system identifies a likely feed fault, creates a single work order targeting CP-22, and cancels the three individual pole dispatches. One crew. One repair. All seven lights restored overnight. The citizens who reported are notified automatically.

What Does Not Happen

Three unnecessary truck rolls. Extended dark corridor safety risk. Citizen complaint escalation to council. The pattern that nobody noticed because each outage was treated independently.

3 truck rolls eliminated, 1 repair

STREETLIGHTS — Commerce Ave
Pole SL-0881Dark 72h
Pole SL-0882Dark 48h
Pole SL-0887Dark 24h
Root causePanel CP-22

1 repair resolves all 7 — WO-SL-0221 dispatched

Play 5

The traffic signal cabinet was 14°F too hot. The intersection never went dark.

The Scene

Traffic Signal Cabinet TSC-0091 at the intersection of Main and 21st reports an internal temperature 14°F above normal at 14:30 in July. The temperature rise is consistent with a cooling fan failure — not an immediate hazard, but a condition that will cause controller board failure within 48–72 hours if the ambient temperature holds.

With Viaanix

ArgusIQ™ creates a maintenance work order with the cabinet ID, the temperature trend, the probable cause (fan failure), and a 48-hour resolution window. The technician replaces the fan during a scheduled maintenance window. The cabinet temperature returns to normal. The intersection never goes dark.

What Does Not Happen

Controller board replacement ($3,000–$5,000). Intersection failure requiring police traffic control. Accident liability during signal outage. Emergency overtime dispatch.

$5K+ avoided per signal save

Play 6

The waste bin was at 92% on Tuesday. The overflow that would have ruined the weekend event never happened.

The Scene

Waste bin B-0441 at City Park reaches 92% capacity on Tuesday — two days before the scheduled Thursday collection. The park is hosting a weekend event that will generate additional waste. In a route-based system, the Thursday truck arrives to find an overflowing bin that has been a public eyesore for 48 hours.

With Viaanix

ArgusIQ™ flags B-0441 at 92% fill. The collection route is updated to add a priority pickup. The bin is emptied Wednesday morning. For the weekend event, a temporary second bin is pre-positioned based on historical event waste data. No overflow. No citizen complaints. No council inquiry about park maintenance standards.

What Does Not Happen

The 48-hour overflow. The citizen complaints. The health and pest attraction risk. The council inquiry about park maintenance standards.

Overflow prevented, route optimized

WASTE COLLECTION — City Park
B-044192% ⚠ PRIORITY
B-044234% — Skip cycle
B-044361% — Scheduled

Route updated: priority pickup added | Weekend: +1 bin staged

Play 7

The truck was 147 engine hours past due. It got serviced before needing a tow.

The Scene

Public Works truck V-114 has logged 4,847 engine hours — 147 hours past the manufacturer’s recommended oil change interval. The engine oil pressure sensor shows a slight but consistent downward trend over the last 200 hours. In a mileage-based maintenance program, the next service is 1,200 miles away. The truck is dispatched daily to water main repair sites.

With Viaanix

ArgusIQ™ flags the engine hour exceedance and the oil pressure trend. WO-PM-0092 is created with the vehicle ID, the condition data, and confirmed parts availability from the fleet maintenance yard. The truck is serviced during the next scheduled non-dispatch day. No downtime. No tow. No emergency rental.

What Does Not Happen

Engine damage from deferred maintenance ($8,000–$15,000). Tow cost ($350–$800). Emergency rental ($250/day). Crew downtime during vehicle unavailability.

$15K avoided per engine save

FLEET — Public Works
V-1144,847 hrs ⚠ PM
Oil pressure↓ trend −3%/200hr
Next serviceOverdue 147h
PartsConfirmed in stock

WO-PM-0092 — Scheduled: next non-dispatch day

Play 8

The compactor sat idle for 14 days. Another crew rented one because they couldn’t find it. That stops now.

The Scene

GPS/RTLS-tagged compactor C-019 has not moved from the maintenance yard for 14 days. It was signed out to a road repair crew two weeks ago. The crew finished the job and returned the compactor — but nobody updated the assignment. Meanwhile, another crew rented a compactor because they couldn’t locate one available in the fleet.

With Viaanix

ArgusIQ™ flags C-019 as idle for 14 days with an active assignment record. The assignment is cleared. The rental is cancelled for the second crew, which is now assigned C-019. The rental savings alone pay for the tracking system for the quarter.

What Does Not Happen

The unnecessary equipment rental ($400/day × 5 days = $2,000). Crew time spent locating equipment. Duplicate procurement for assets the city already owns.

$2K+ saved per prevented rental

Play 9

The citizen reported a pothole at 8:14am. They got a photo of the completed repair at 1:20pm. With proof.

The Scene

A citizen reports a pothole at 08:14 via the city’s online portal. Request WO-3301 is created. In most cities, the citizen receives an acknowledgment and then hears nothing until they call back to ask about the status — at which point a staff member manually checks with the responsible department.

With Viaanix

ArgusIQ™ creates WO-3301 with the location, the citizen contact, and the SLA clock (24 hours for pothole repair). The work order is routed to the street maintenance crew. The crew completes the repair at 13:20. The technician captures photo evidence via the mobile app. ArgusIQ™ updates the citizen notification automatically: “Your request WO-3301 has been completed. Repair verified with photo evidence. Total response time: 5h 06m.” The SLA record is closed with a complete, auditable trail.

What Does Not Happen

The citizen callback. The manual status check. The council inquiry about response times. The inability to document SLA performance for grant reporting.

SLA met and documented: 5h 06m

CITIZEN SERVICES — WO-3301
RequestPothole | 5th & Main
Received08:14 | Online portal
Completed13:20 | Photo verified
SLA (24h)Met: 5h 06m

Citizen notification: SENT | Evidence: 📸 before/after

Play 10

Water main break at a hospital intersection. Six departments responded in 4 minutes — coordinated by the system, not by phone.

The Scene

A water main break at the intersection of Douglas and Hydraulic at 16:45 on a Wednesday. Water is flooding the roadway. Traffic is backing up. The affected water zone serves a hospital and two schools. In a conventional response, police are called for traffic control, water is called for the break, streets is called for barricades, and communications is called for the public notification — four departments responding independently, coordinated by phone.

With Viaanix

ArgusIQ™ detects the pressure loss and flow anomaly. The system creates a multi-department incident response: water dispatch for the break, police notification for traffic control, streets dispatch for barricades, communications trigger for the public notification, and a hospital/school notification protocol. All five actions are initiated within 4 minutes of detection. The incident timeline, resource allocation, response times, and resolution verification are recorded automatically.

What Does Not Happen

The 30–60 minutes of phone-based multi-department coordination. Extended citizen impact. Hospital service disruption risk. Liability exposure from delayed road closure. The 4–8 staff hours assembling the after-action report.

4 minutes to full multi-department response

Play 11

The HVAC fault happened at 3am Saturday. The building opened on schedule at 8am. Nobody noticed.

The Scene

Air handler AH-07 in Community Centre Building 3 throws a high-static-pressure alarm at 03:14 Saturday morning. The building opens at 08:00 for a youth sports programme. In a conventional system, the alarm is logged in the BMS. Nobody sees it until Monday morning. The building opens Saturday with a failed HVAC zone.

With Viaanix

ArgusIQ™ receives the BMS alarm, correlates it with the building occupancy schedule (youth sports, 08:00 open), and escalates the priority. WO-2201 is created at 03:15 with the fault code, the building schedule context, and the on-call technician assignment. The technician arrives at 06:45, replaces the fan belt, and verifies normal operation by 07:30. The building opens on schedule.

What Does Not Happen

The emergency overtime dispatch during programme hours ($800–$1,200 vs. $200 planned on-call). Programme disruption and citizen complaints. Equipment damage from extended operation in fault condition.

Fixed 75 min before building opened

FACILITIES — Community Centre 3
AH-07High static ⚠ FAULT
Alarm time03:14 Saturday
Building open08:00 | Youth sports
Repair complete07:30 ✅

Building opened on schedule: YES

Play 12

The 90-minute weekly coordination meeting became a 15-minute exception review. Ask Argus answered in 12 seconds.

The Scene

Every Monday at 08:00, department heads from Water, Fleet, Facilities, Streets, and Waste meet for 90 minutes to share status updates, coordinate resources, and resolve scheduling conflicts. Each department brings a printed report from their own system. The meeting is the coordination mechanism because no shared system exists.

With Viaanix

The City Manager opens Ask Argus: “Show me all overdue work orders across water, fleet, and facilities. Which departments have resource conflicts this week? What was the average response time by department last month vs. this month?” The answer appears in 12 seconds. Grounded in live data. Cross-departmental. No report assembly required. The 90-minute meeting becomes a 15-minute exception review.

What Does Not Happen

The 90-minute meeting. The 2–4 hours of preparation time across departments. The printed reports that were already 3–5 days old when they were printed.

90-min meeting → 15-min review

THE PLATFORM IN ACTION

This is what your city operations look like when every asset is digitally alive.

Live telemetry, governed workflows, and AI — running across water, fleet, facilities, streets, and citizen services. One Operating System, every department.

Water Pressure — Main 7
40 PSIPSI
Fleet Bus 44RTLS
TypePublic Transit
LocationCentral Depot
StateMaintenance
Battery142K mi
Last seen< 1 min ago
Citizen SLA Response

District 1

4min

District 2

8min

District 3

18min

District 4

32min

District 5

6min

District 6

24min

NormalSlowBottleneck
Work Order Lifecycle
TriggerWater pressure anomaly — Main 7
WO CreatedWO-WM7-PRESS
AssignedWater Crew Alpha
ResolvedLeak repair dispatched
CROSS-DEPARTMENT STATUS
Public Works12 open | SLA 91%
Fleet8 open | SLA 96%
Facilities11 open | SLA 82%
Water14 open | SLA 88%

City-wide SLA: 89% | Grant KPI target: 90%

IIJA Grant Accountability62%
Outcome measurementpass
Spending documentationpass
Milestone reportingpass
Equity trackingwarning
Environmental reviewpending
Audit readinesspending
Recent Activity
Water pressure alert — Main 7 dropped below 50 PSI threshold. WO-WM7-PRESS created.
09:14
Fleet PM completed — Bus 44 oil change and brake inspection at Central Depot.
09:08
Citizen request resolved — District 3 pothole repair verified with photo evidence. SLA: 4h 22m.
08:52
HVAC efficiency alert — City Hall compressor efficiency down 22%. WO-HVAC-CH-09 created.
08:41
Ask ArgusAI Assistant

BUILT FOR WHAT COMES NEXT

Autonomous inspection drones, AI-optimized dispatch routing, predictive infrastructure replacement, and self-executing seasonal operations are entering city management at scale. Is your Operating System the foundation they need to run?

Every autonomy capability entering city operations — from autonomous infrastructure inspection to AI-driven dispatch optimization to predictive capital replacement — requires the same foundation: a unified operational identity layer where every asset has a known state, a complete history, and a governed lifecycle that AI can reason about. ArgusIQ™ is that foundation.

Autonomous Infrastructure Inspection

Drone and robotic inspection of water mains, sewer lines, bridges, and road surfaces — feeding findings directly into ArgusIQ™ as work orders with severity classifications, location data, and photo evidence. The inspection that currently requires a crew, a truck, and a day of lane closures runs overnight, unattended.

AI-Optimized Dispatch & Route Planning

Every dispatch decision — which crew, which vehicle, which route, which priority — optimized in real time based on crew location, skill match, parts availability, traffic conditions, and SLA urgency. The dispatcher’s judgment is augmented, not replaced. The truck roll that would have been wasted is eliminated before it starts.

Predictive Infrastructure Replacement

Capital replacement planning driven by actual asset condition data, failure probability models, and cost-of-failure analysis — not by age-based assumptions. The water main that would have been replaced in 2030 based on installation date is replaced in 2027 based on what its condition data shows. The one scheduled for 2025 based on age is deferred to 2029 because it’s performing fine.

Self-Executing Seasonal Operations

Winter storm prep, spring flood response, summer heat protocols, fall leaf collection surge — each seasonal operation defined as a workflow in ArgusIQ™ that triggers automatically based on weather integration, calendar triggers, and historical patterns. No phone tree. No “did anyone check the salt inventory?”

The autonomy capabilities that will define city operations over the next decade are not replacements for the platform. They are extensions of it. ArgusIQ™ is the foundation. The rest follows.

WHAT THIS COSTS NOT TO HAVE

City operational waste is not a catastrophic event. It is a thousand daily inefficiencies that compound across every department, every shift, every dispatch, every month.

0%

Citizen SLA Compliance

0x

Cross-Dept Coordination

0%

Infrastructure Uptime

0%

Grant Audit Readiness

WHY VIAANIX

Not another vendor. A different foundation.

One OS Across Every Department

Not integration middleware. Not a unified dashboard that aggregates reports. One Operating System where water, fleet, facilities, streets, waste, parks, and citizen services share a single operational truth layer — with department-level views and city-wide rollup.

Vendor-Agnostic — Bring What You Have

Existing SCADA, GPS, BMS, meters, sensors, ERP — we ingest them all. No rip-and-replace. No vendor lock-in. Every existing investment becomes part of the unified view.

City-Scale Governance

Multi-tenant architecture with department-level access control, role-based permissions, audit trails, and compliance documentation that meets federal grant accountability requirements.

AI Grounded in Your City's Data

Ask Argus queries your city's operational data — your assets, your maintenance history, your response times, your compliance records. ArgusAI runs on-premises for water treatment, power distribution, and emergency management environments where data cannot leave the network.

Deployment Options

Cloud

Full platform on Viaanix-managed cloud infrastructure. Fastest deployment. Automatic updates. Ideal for cities starting with water metering, fleet, waste, or facilities use cases.

Private Cloud

Dedicated instance on your city's preferred cloud provider (AWS GovCloud, Azure Government). Full data isolation. Meets municipal data residency requirements.

On-Premises

Full platform deployed inside your city's data centre. Complete data sovereignty. Ideal for cities with strict data governance policies.

Air-Gapped (ArgusAI)

Full platform with embedded AI running inside isolated networks with no external connectivity. Water treatment SCADA, power distribution, emergency management.

Multi-tenant department isolationRole-based access controlFederal grant audit trailsIIJA accountability workflowsData residency complianceCritical infrastructure network isolation

You don’t have a sensor problem. You don’t have a data problem. You have an execution problem. And it has a solution.

Start with water or fleet. Add facilities, waste, streets, and citizen services on the same platform. One Operating System. Every department. Every asset. Every workflow.