Infrastructure

Linear and networked assets - roads, water, sewer, sidewalks - with GIS geometry, Esri sync, and the same condition-risk-cost engine as the rest of AssetLab.

The Infrastructure module extends AssetLab to the assets that don't live in buildings: road segments, watermains, sewers, hydrants, streetlights, sidewalks. They get geometry and map presence - and the same lifecycle machinery (condition, risk, costs, work history) that vertical assets have, so the whole portfolio plans as one.

What lives here

A few surfaces live outside this list: the module's own Import wizard for GeoJSON, shapefiles, and CSV (covered under Esri & GIS sync); the Routes and Corridors pages (covered under zones, routes & corridors); the Strategy page, where lifecycle strategies are set; and the Settings → Infrastructure group, the administrator home, with its own entries for Classes & networks, Material rates, and GIS & basemaps.

The model in one paragraph

Feature classes (Watermain, Road Segment, Hydrant…) are a tenant-level catalog carrying unit replacement rates and service lives; each network (Roads, Water Distribution, Sanitary…) is filed under exactly one class. A feature is one real thing - a specific pipe segment with its length, material, install year, and geometry. Replacement value uses the feature's purchase cost inflated from its base year when one is recorded; otherwise it's measured quantity × a unit rate resolved feature override → material default → class rate. Condition comes from inspections; risk and lifecycle math run exactly as they do for vertical assets.

On the dashboard

The Infrastructure tab carries FCI forecasts by network, by category and by feature class. Each one draws a dashed Planner line beside the estate curve showing where FCI goes once the replacements you have scheduled are carried out - it appears only where something is scheduled, so a curve with no plans behind it stays a single line. The first of the three also carries an Industry average line when you have benchmarking switched on: the average infrastructure FCI of organizations in your own category, over their linear assets rather than their buildings. Below the forecasts sit the condition and age distributions and Features Requiring Replacement - every feature the forecast retires inside the horizon, with its network, feature class, in-service year, replacement year, original cost and estimated replacement cost. Anything already past its replacement year is flagged Past Due. The horizon is the one set on the Lifecycle tab, so this list and the Assets tab's replacement list cover the same window.

Members assigned to the Infrastructure workspace get the whole dashboard keyed to linear assets: the Work distribution card on the Work orders tab buckets work by feature, network, feature class or work category, rather than by the site, building and system dimensions a feature does not have.

Built to coexist with your GIS

AssetLab doesn't replace ArcGIS - it syncs from it. Esri stays the authority on geometry and mapped attributes; AssetLab owns what GIS is bad at: condition history, work orders, costs, inspections, and capital planning. One-way sync keeps the boundary clean.

Where to start

Municipal teams should walk the municipal quickstart - networks → classes → GIS import → map check → level of service, in order.