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

• Identity - name/asset ID, its network, and through the network its feature class
• Geometry - the line or point that draws it on the map; for lines, geometry yields measured length
• Attributes - material, install date, diameter, streets, and the other physical fields, filled by sync, import, or hand
• Quantity & valuation - measured quantity × the resolved unit rate (feature override → material default → class rate) = replacement value
• Lifecycle - install date + service life (resolved the same way) → projected replacement year
• Zone - the zone containing it, where zones are in use

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, in three groups:

• Network - feature class, network, zone, and feature type (segment or node).
• Classification - material, risk level, condition band and status.
• Lifecycle - in the Lifecycle Filters tab on the right edge of the page, which slides a panel in: install year range, remaining service life, time since the last inspection, whether the feature is on a live project, and whether it has an open work order.

Remaining life uses the same service life as the rest of the module: the feature's own, else its material's, else its feature class's. "Not inspected in 3 years" includes features that have never been inspected. "On a live project" follows the project badge: a project that is complete, cancelled or archived does not count.

Search narrows the table only. Feature class and network take more than one value at a time - tick two networks and both draw on the same map, and the table lists the features of both. Picking one or more classes narrows the network picker to the networks carrying them; an explicit network pick takes over from the class.

A project badge beside a feature's name counts the projects currently working on it, as on the asset list. Live projects only: a project that is complete, cancelled or archived stops badging the features it named. The detail panel that opens from the table lists every project the feature is on, with finished ones greyed as history, and the feature page's Overview carries the same list.

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.

Exporting features

Export, beside Custom fields at the top of the features page, downloads every feature matching the current search and filters - not just the page on screen. Managers and administrators see it. Pick a format:

• CSV (Excel compatible) - one row per feature with the table's columns: network, asset type and status by name, condition score and band, risk score and level, material, length, diameter, cross streets, dates, remaining life, last inspection, positional accuracy, data source, and description, plus every custom field. Replacement value and depreciated replacement cost are included too, with your organization's currency in the column heading. The first column is each feature's AssetLab ID
• GeoJSON (GIS) - the same features with their geometry in WGS 84, ready to add as a layer in QGIS or ArcGIS Pro

To export a hand-picked set instead, use Export in the bulk action bar below.

Bulk work

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

• Set condition - one 0-100 score across the selection
• Change status and assign asset type
• Soft delete
• Export the selection as GeoJSON (geometry included - it opens in ArcGIS Pro or QGIS)
• Insights - an analysis panel over just the selected features
• Create work order or create a project from the selection - the selected features arrive pre-linked. A multi-feature selection makes one work order covering all of them, not one each
• Create PM schedule (Managers and Administrators) - opens the PM schedule form with the selected features already attached. Like a work order, it is one schedule covering all of them

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):

• Overview - the map, attributes, valuation, lifecycle, the description notes box (below), plus cards for the projects that include this feature and the zones containing it. Each project is labelled with where it stands, and one that is complete, cancelled or archived reads as history - greyed and dashed - rather than as work under way. Each card edits in place: Staff and above get a pencil on the cards they can change, and Save writes without leaving the page
• Inspections - the condition record (below)
• Work orders - corrective and PM work against this feature
• Costs - every dollar this feature has consumed
• Compliance - appears when the feature has PM schedules
• Parts - components associated with the feature
• Documents & comments - CCTV reports, specs, the running conversation
• Photos - every image attached to the feature's inspections, in one gallery
• History - the risk history trend plus split/merge lineage, so a segment's origin survives resegmentation

What each card edits

The card that shows a value is the card that edits it, so nothing is editable somewhere you cannot see it:

• Identity - name, asset ID, network (which carries the feature class), asset type, status, from/to street, model, serial number, description
• Financial - install date, service life, last maintenance
• Risk - condition score, consequence of failure, likelihood and risk factor with their override switches
• Physical - material, diameter, width, depth, lanes, road class, and the upstream and downstream inverts

Road class is the O. Reg. 239/02 class, 1 to 6. Classes 1-2 are arterial, 3-4 collector and 5-6 local, which is how O. Reg. 588/17 reports lane-kilometres. It can be set on the feature, over the API, or mapped in the import wizard or GIS sync, both of which accept values like 3 or Class 3 and leave anything else blank rather than rejecting the feature.

Some values read but never edit, because something else produces them: length comes from the geometry, slope is recomputed from the two inverts and that length every time you save, risk score is consequence times likelihood, and unit rate, units and replacement value resolve through your material and class rates - a Priced from row says which tier won, so you know whether editing a rate in Settings will move this feature's number. A feature priced per m² or m³ that lacks the dimension to multiply says so in its units field ("No width recorded") instead of showing a dash: that gap is fixed on the feature, not in the rate book. Purchase cost and purchase date read only as well, where an import supplies them: a purchase cost takes precedence over the whole rate chain, so a feature that has one is valued from its historical cost inflated to today rather than from your class rate, and that is a decision about how you account for infrastructure rather than a field to fill in. On a feature that syncs from Esri, every field the sync writes reads only.

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.

• Road segments: PCI from pavement condition surveys
• Sewers: structural grades from CCTV programs
• Water: break history and condition observations

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

Feature risk

A feature's risk is consequence × likelihood, the same model vertical assets use, computed for you from the condition score:

• Likelihood of failure (1-5) is banded from the feature's condition score - a segment at 30 scores 4, one at 90 scores 1
• Consequence of failure (1-5) is the feature's criticality. Where a feature arrives from GIS without one, AssetLab fills it from the feature class and marks where the value came from, so a rule's fallback never reads as an engineer's assessment
• Risk score is the product, out of 25, and the risk factor bands it: 20 or more is Critical, 15 or more High, 10 or more Medium, below that Low

A filled consequence says which tier produced it, because the tiers are not equally informative:

A value with no label is one somebody set, and it is left alone by everything above.

Likelihood and risk factor each carry an Override switch on the risk card of the feature page; typing a consequence by hand pins that one the same way. An override is judgment, so it survives whatever happens to the condition score afterwards - the derivation stops touching that field until you switch it back. Every change to condition, either score, the risk score or the risk factor is captured in the feature's risk history.

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 - divided evenly when one work order covered several - 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.