Features

The individual infrastructure record - geometry, attributes, valuation, inspections, costs, and work history for one real segment or point.

A feature is one real piece of infrastructure: this 240 m watermain segment on Elm Street, this hydrant, this culvert. Features are to the Infrastructure module what assets are to the registry - and they carry the same kind of record.

Anatomy of a feature

Most of this arrives automatically when features sync from Esri; manually created features fill the same fields.

The list

The table carries 17 reorderable columns - condition, risk, replacement value, depreciated replacement cost, material, length, install date, remaining lifetime, last inspection, and more. Two data-quality columns (positional accuracy class and data source) are hidden by default; GIS analysts toggle them on from the column manager during data-quality audits. Any custom fields defined for infrastructure - including ones created during a file import - appear as additional columns, and their values show in the feature detail panel and on the feature page.

Filters scope both the table and the map: search, feature class, network, zone, material, feature type (segment or node), condition band, and risk level.

On large portfolios the result total is an estimate. Counting every matching feature exactly on each page turn costs far more than fetching the page itself, so past a few thousand rows the total comes from table statistics instead - close enough to size the result and turn the pages, typically within a fraction of a percent. Smaller result sets are still counted exactly.

Bulk work

Turn on Select mode and a bulk action bar appears for the checked features:

The feature detail page

The page opens on a summary header - condition, risk, service life, replacement value, and last inspection at a glance - with every dimension one click away in the section list (each section shows how many records it holds):

Quick notes

The feature's description is an always-open notes box, on the Overview tab and in the detail panel that opens from the table or the map. It shows on every feature, empty ones included - type the observation and Save appears; Cmd/Ctrl+Enter saves without reaching for it. Staff and above can write; Requesters see the text read-only. Use it for the running note that has no field of its own ("temporary patch at the north joint, revisit in spring") - a dated condition record belongs in an inspection instead.

Inspections

Feature inspections are the linear-asset condition record - dated, sourced ratings with notes, equivalent to condition assessments. The entry form offers a fixed method list - visual, CCTV, PCI survey, core sample, gauge reading - the Inspector dropdown lists your active team (Administrators, Managers and Staff; Requesters never appear), and each inspection stores the raw score you entered plus the scale it was entered in; the network's condition scale governs the conversion to the internal 0-100 score.

Inspections drive the condition shown on the map, the risk score, and where the segment lands in the replacement planner. Inspection forms can standardize field capture (subject_type: infrastructure_asset).

Work and costs against features

Work orders target features exactly as they target assets - a watermain break is a work order on that segment. Completion posts costs to the feature, and a segment's accumulating break-and-repair history is precisely what justifies its replacement priority.

Where feature money goes

Each network projects into the Capital Brief and the lifecycle forecast as its own class, so infrastructure replacement value, FCI, and funding gap sit alongside your facility system classes in one forward view. Infrastructure O&M spend rolls into the dashboard cost views and the Budget tab, so the operating and capital pictures both include the linear network.