Spatial systems that close.

Field crews collect good data on clipboards and phones, and it dies in a spreadsheet the client never sees.

A phone form for the crew, a hosted layer as the record, an office app for QA and inspection scheduling, and a dashboard for the client.

• Field Maps form with required fields, pick lists, and photos
• Hosted asset layer with a related inspection table
• Office web app: filters, due list, CSV export, QA flag

Capital projects live in a PDF map and a spreadsheet, and the public, the council, and the PMs all have a different version.

One branded web map and list with phase, schedule, budget, documents, and contact, updated by the PM from a spreadsheet.

• Projects as points, lines, and polygons in one list
• Filter by category, phase, district, and fiscal year
• Project pages with milestones, documents, and a PM contact

Work orders, pressures, and breaks live in three systems, and the manager finds out about the bad week in the monthly report.

Assets, work orders, and sensor readings on one screen with KPIs, thresholds, and alerts, fed on a schedule from SCADA and the work-order system.

• Zones, mains, hydrants, valves, and work orders as layers
• Sensor layer with a readings table and alarm rules
• Scheduled feed from a historian export or an API

A constraint screening takes a GIS analyst two days in the desktop, and every analyst does it a little differently.

An interactive tool that encodes the firm's screening method: sketch, buffer, weights, overlap acres, parcels, score, and a printable memo.

• Constraint layers: floodplain, wetlands, slopes, soils, zoning, parcels, utilities
• Sketch a site or an alignment, or load a candidate
• Weighted score with editable weights and a stated formula