# 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.

Source: https://app.assetlab.ca/docs/infrastructure

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

| Page | What it covers |
|---|---|
| [Networks & feature classes](/docs/infrastructure/networks-and-classes) | The structure - networks, classes, unit rates, attribute schemas |
| [Features](/docs/infrastructure/features) | The individual records - segments, points, inspections, costs |
| [Zones, routes & corridors](/docs/infrastructure/zones-routes-corridors) | Spatial and operational groupings |
| [Esri & GIS sync](/docs/infrastructure/esri-sync) | Keeping AssetLab aligned with your ArcGIS layers |
| [Map view](/docs/infrastructure/map) | The map as a working surface |
| [Level of service](/docs/infrastructure/level-of-service) | Measurable service commitments and their tracking |

A few surfaces live outside this list: the module's own **Import wizard** for GeoJSON, shapefiles, and CSV (covered under [Esri & GIS sync](/docs/infrastructure/esri-sync)); the **Routes** and **Corridors** pages (covered under [zones, routes & corridors](/docs/infrastructure/zones-routes-corridors)); and **Settings → Infrastructure**, the administrator home, split into three tabs: **Classes & networks**, **Replacement 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](/docs/infrastructure/features); risk and lifecycle math run exactly as they do for [vertical assets](/docs/asset-management/risk-and-fci).

## Built to coexist with your GIS

AssetLab doesn't replace ArcGIS - it [syncs from it](/docs/infrastructure/esri-sync). 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](/docs/start/municipal-quickstart) - networks → classes → GIS import → map check → level of service, in order.