Municipal Infrastructure Operations

The investment gap between current infrastructure spending and what is needed has grown to $3.7 trillion.

ASCE, 2025

Infrastructure doesn't manage itself on spreadsheets

Work orders that live in someone's inbox. Inspections recorded on paper and re-typed into a spreadsheet. FOIA requests that take a week to answer because the data sits in five different systems. The cost compounds in staff hours, audit exposure, and infrastructure risk.

Ithil replaces the patchwork of spreadsheets, legacy systems, and tribal knowledge with a single operations platform built for municipal public works.

The Problem Everyone Knows

About a third of the water and public works workforce is eligible for retirement in the next decade. Senior operators are leaving and taking decades of institutional knowledge with them. Ithil records every action as a structured event so the operational history outlasts the people who built it, and so council reports come out of the system in a single click.

Most municipal operations still rely on what ICMA calls “a patchwork of disconnected systems, each performing its designated function adequately but creating data silos that prevent integrated service delivery.” The operations platform has to produce audit-ready documentation as a byproduct of daily operations, not as a separate workstream.

Assets in one place, on a real map

Curb ramps, catch basins, signals, streetlights, parks, bridges, sober-living facilities. Hierarchy from systems down to individual components, with condition tracking, lifecycle cost, and replacement forecasting based on real operational data.

  • Schema-per-tenant Postgres with PostGIS
  • Cluster-aware map view at any scale
  • Asset metadata configured per type
  • Replacement forecasting from condition data
Ithil asset map zoomed in on a dense municipal asset cluster, light theme

Compliance is the substrate, not a bolt-on

Every workflow maps to NIST 800-53, ADA Title II, NPDES MS4, SB 1, SB 1383, Caltrans NBI, and the local code provisions specific to each jurisdiction. The audit comes out of the work, not after the fact.

  • ADA Title II curb ramp Transition Plan tracking
  • NPDES MS4 catch basin and outfall reporting
  • SB 1 pavement condition + project list submittal
  • Local code workflows configurable per jurisdiction
ADA Title II curb-ramp compliance dashboard showing compliant, non-compliant, and pending counts, light theme

Work orders with real history

Event-sourced work orders capture who requested it, who was assigned, what was done, what parts were used, and what it cost. Immutable. Linked to inspections, requirements, and the assets they touch.

  • Append-only event store
  • Inspection-finding-to-remediation pipeline
  • Material usage with cost per job
  • Mobile field capture with offline mode
Work orders list with status, assignee, and asset for a municipal public-works backlog, light theme

Inspections that become reports

Configurable inspection templates for any asset type. Mobile field capture with photos, GPS, and structured findings. Compliance documentation generated from the same records the inspector saw on the truck.

  • Templates per inspection type
  • Photo + GPS attached to each finding
  • Findings drive work orders automatically
  • Annual reports compiled from the source data
Inspections table with template, asset, inspector, and completion status, light theme

Built for Government

Data Isolation

Each tenant operates in a fully isolated database schema. Tenant data is never commingled with another agency's.

Compliance Mapped

Aligned with NIST SP 800-53 Rev 5 controls across access management, audit logging, and data protection. SOC 2 Type I Ready. FedRAMP Moderate on the roadmap.

FOIA & Audit Trail

Every action is logged with attribution and time. Soft deletes preserve records for legal holds. FOIA exports pull directly from the audit log with automatic PII redaction.

Accessible

WCAG 2.1 AA compliant. Section 508 accessibility requirements met.

Ithil deploys with industry-specific templates built from real municipal workflows. Asset hierarchies, inspection programs, permit types, and compliance frameworks come configured for how public works actually operates, not a generic CMMS bent to fit.