Culvert & Storm Inlet Inventory and Inspection System

The township maintains about 180 culverts and 320 storm inlets on local roads and has no current record of where they are, what condition they are in, or when they were last looked at.

Field technicians capture each asset once on a phone with a required-field form and photos, then re-inspect on a 36-month cycle (12 months for poor or failed assets); the office reviews new captures and programs the next year's inspections.

The outcome is an inventory the township engineer can open in a browser, a defensible inspection program for the MS4 permit, and a renewal list ranked by condition and age.

1. Everything above the office app is standard Esri configuration (the Starter tier).
2. The office web app reads the same layers through the web map; swapping the demo's static data for the hosted layer is a one-line change in configuration.
3. No custom server: the app is static files on Vercel; the data lives in the client's ArcGIS Online org.

These tables are generated from the same schema file the demo app and the data generator use, so the sheet cannot drift from the data. Computed fields are derived in the office, not collected.

• All layers are shared to the township's ArcGIS Online organization only; nothing is public unless the township asks for a public view.
• A public view, if requested, is a separate read-only layer view with photos and inspector names removed.
• Field technicians can add and edit their own features; only the QA reviewer and the consultant can delete.
• The office app's basemap key is scoped to basemaps only and restricted to the township's domain.
• At handover the consultant's admin role is converted to a named support account or removed, per the township's policy.

• Esri US list prices as of 2026-10-08; confirm at purchase. Licenses are bought in the township's name.
• The consultant's own Creator seat is separate and not billed to the client.
• Worked total for the roles above: $1,875 per year to Esri.

The demo on this site is the Standard tier.

The client signs this list at Issued for Use. The final 20% is invoiced on signature.

1. 1The Field Maps form rejects a submission with any required field empty and requires at least one photo.
2. 2A feature submitted from a phone in coverage appears in the office app within 5 minutes with office_reviewed = false.
3. 3Every field in the data model is populated or explicitly null on 100% of loaded features.
4. 4Filters, list, map, counts, and charts always show the same set (checked on five filter combinations).
5. 5The due list export has the agreed columns and one row per asset due in the next 12 months.
6. 6The three core workflows (capture, QA, programming) run end to end by township staff without the consultant present.
7. 7The app loads and is usable on the township's phones over cellular.
8. 8The record set is delivered.

• Township: field technicians capture and inspect; the QA reviewer clears new captures weekly; the engineer runs the monthly due list.
• Monthly (consultant, under retainer): usage and credit check, broken-link check, sync error review.
• Quarterly: SDK and dependency updates to the office app, backup export of the hosted layers to GeoPackage, health report.
• Annually: ArcGIS Online renewal reminder, review of the inspection-cycle rules and the condition domain, photo-storage check.
• Retainer covers 2 hours of small changes per month; beyond that at the hourly rate with a not-to-exceed.

Demo data is synthetic. Ridgeline County does not exist. The county roads, river, and downtown are generated; the data model, the SDK, and the workflows are real.

What to tap

1. Filter Condition to Poor and Failed, then Material to CMP
2. Tap any red circle to open its record and history
3. Open Insights and export the 12-month due list

Generator seed 101 · demo clock 2026-10-01 · culverts 180 · inlets 320 · storm_mains 140 · outfalls 24 · inspections 1191 · overdue culverts 32 · overdue inlets 48