AssetLab Canada: Latest News, Updates & Industry Insights

Until now the map in AssetLab belonged to the Infrastructure module. It does not any more. Give a building a latitude and longitude - type the coordinates, or click Pick on map to drop a pin and drag it onto the roof - and three map views open up on every plan. Position lives on the building rather than the site, so each building on a campus gets its own pin instead of six stacking on one address, and the Buildings tab gains a list/map switch plotting every placed building coloured by criticality. The asset register gains a Map view where each building is one pin, coloured by its Facility Condition Index, sized by the replacement value of the assets inside it and labelled with how many there are; click it for the rollup, with FCI and both figures behind it, replacement value, value per square foot, the building's condition mix and the four system classes carrying the most value. Every figure is computed from the assets your filters return, so filtering to HVAC gives you HVAC value per building, and a building whose assets carry no purchase cost draws grey and says so - missing data, not a clean bill of health. The work order queue's Map view is no longer infrastructure-only either: on the Facilities workspace a work order draws at the building it resolves to, with the same clustering, filters, summary panel and technician day plans the infrastructure side has. All three use the same map as the rest of AssetLab, so basemaps, aerial imagery and the 3D-buildings view work in them, and building coordinates are available over the REST API and to AI assistants.

Straight-line decline assumes you do nothing until an asset dies. Real programs intervene, and AssetLab can now model it. A lifecycle strategy captures the interventions between buying an asset and replacing it - a roof recoat at condition 70-85 that adds five years, a boiler retube at 40-60 that resets condition to 100, crack sealing at 80-90 that adds two years to a road - each with its own cost, cost source and condition trigger window. Set them once per asset type or type group on the facilities side, or per feature class, material or diameter band on the infrastructure side, and every matching asset projects its own sawtooth curve anchored at its own assessed condition. The strategy-aware renewal year then flows through everything downstream: the lifecycle chart, the replacement planner (which now ranks by extended life rather than raw design life and filters on Due intervention and Missed window), the map's renewal forecast layer and corridor dig-once bundling. The dashboard prices the whole program - year-by-year cash flow against the run-to-replacement line, years of life added, replacement value deferred, and every strategy ranked by cost per added year of life, including what an already-missed window would have cost. A Due interventions panel turns an asset or feature sitting inside a trigger window into a work order or a project in one click, and the strategy never writes a condition score itself: completing the work offers the modelled condition as a pre-filled assessment for a person to confirm.

August was the busiest release month in AssetLab's history. The work order queue gained a Map view for infrastructure organizations: every open work order bound to a road, pipe or node is a pin, and a technician's day is a numbered route you build by clicking pins - drag to reorder or let AssetLab suggest the shortest order, then hand each stop to your phone's maps app. Routes and corridors are now tiers of the Infrastructure page with the map working at every tier, and you can turn the routes and corridors you select into a capital project scoped to a renewal-year window. Every organization now gets dedicated intake addresses so anyone can raise a work request by email - no account, no portal. The report builder was rebuilt around 30 data sources with grouped AND/OR filters and CSV or Excel export, Settings > Import ships an onboarding Excel workbook you fill in and upload, and finished projects can be archived. Rounding it out: a 3D buildings basemap, secured ArcGIS basemaps, custom fields created straight from your GIS columns, private file storage everywhere, and a documentation site with an interactive API reference.

July brought forms and inspections to AssetLab: build inspection forms with pass/fail checks, readings, text and photos, with conditional items that appear only when an earlier answer warrants them, attach them to work orders and PM schedules, and get the answers back as data you can filter and report on. Shared work order links let you send a contractor a secure link to one job - view-only or with completion allowed - and two-way conversations on work requests keep requesters and staff in one thread that follows the request onto the work order. Enterprise administrators can now configure Okta, Entra, Google or a custom SAML/OIDC connection themselves under Settings > SSO, Esri layers can be overlaid on the infrastructure map and bound to AssetLab records, and platform availability now lives on a public status page with 90 days of history.

AssetLab's biggest release yet brings linear and spatial assets into the platform as first-class citizens. The new Infrastructure module organizes roads, watermains, sewers, streetlights, and other buried assets into networks of segments and nodes - on a fast vector-tile map, in your work orders, in your preventive maintenance program, and in your capital plan. Import GIS data through a guided wizard that handles GeoJSON, Shapefiles, and CSV with WKT geometry, or overlay your ArcGIS FeatureServer layers directly. Every feature carries a 0-100 condition score that rolls up into a length-weighted Network Condition Index, so your buildings and your buried assets finally tell one story. Available today on the Enterprise plan.

Q1 2026 has been our biggest quarter yet. We shipped a full REST API, opening AssetLab to custom integrations and automation workflows. Organizations can now connect AssetLab with their existing ERP, accounting, and building automation systems through our new integrations framework. The highlight of the quarter is our Claude AI integration through the Model Context Protocol (MCP) - facility managers and asset planners can now query their asset data, create work orders, analyze FCI scores, and generate maintenance insights using natural language directly through Claude. Whether you're pulling replacement forecasts or auditing compliance records, AI-assisted asset management is here. These releases reflect our commitment to building the most connected and intelligent CMMS platform in Canada.