The network equipment hero: active units, capital value, maintenance, aging
The Equipment hero is the top band of HQ's Equipment page, the first thing leadership sees before scrolling into any per-location detail. It is one giant number, a pill beside it, a plain-language…
On this page
- What this is
- Where to find it
- The headline: active equipment
- Status mix: in service, in storage, retired
- Ownership mix: owned, leased, financed
- Weighted average age
- The three secondary tiles
- 1. Capital value
- 2. Maintenance overdue
- 3. Equipment >5yr
- How the network figures are built
- National comparison deltas: demo accounts only
- Anonymization and the small-network guard
- How to use it
- Best-practice example
- Related reading
- Data sources
What this is
The Equipment hero is the top band of HQ's Equipment page, the first thing leadership sees before scrolling into any per-location detail. It is one giant number, a pill beside it, a plain-language sentence underneath, and three smaller figures to the right: capital value, maintenance overdue, and equipment over five years. Together they answer the question a franchisor or PE-backed ops lead actually asks first: how much drying and extraction equipment does the network have in the field, what is it worth, is anyone falling behind on upkeep, and how much of the fleet needs to be replaced soon.
Every number on this hero is built entirely from a network-wide rollup. HQ never reads a single location's individual equipment record, its service history, or which specific unit it owns. It reads a nightly summary table that each location's own Verinode IQ account feeds into, and sums, averages, and counts across it. See Equipment (Assets): what HQ sees across the network for the full page (the hero plus the Maintenance & Calibration Risk, Refresh Cycle, and Equipment by Franchisee rows underneath it) and What HQ sees: the network privacy boundary for how that boundary is enforced everywhere on the platform, not just here.
Where to find it
Open Assets from the HQ sidebar, then the Equipment pill (alongside Facilities and Fleet), at hq.verinode.ai/equipment. The hero is the first thing on the page, above the three tile rows. It loads from a nightly aggregation cron rather than a live query, so it reflects the most recent overnight rollup of every location's equipment records, not the current instant.
The headline: active equipment
Eyebrow: "Network equipment."
The giant number is the count of active equipment across the whole network: every piece currently marked in service or in storage. Retired equipment is deliberately excluded from this headline, it counts the fleet you can actually put to work today, not everything a location has ever owned. The number counts up from zero when the page loads.
The pill beside the headline reads one of two things:
- "N franchisees" (or "1 franchisee" for exactly one), the count of member locations that have at least one piece of equipment on file, of any status.
- "No data yet", when no location in the network has registered any equipment at all.
The pill's color follows the same maintenance-health tone as the Maintenance Overdue tile described below: green when nothing is overdue network-wide, yellow at a modest combined overdue count, red once overdue maintenance and calibration together climb higher. Read the pill's color as a one-glance summary of the network's upkeep posture before you even look at the numbers beside it.
The sub-line beneath the headline spells out the mix in plain language, for example:
312 total · 260 in service · 40 in storage · 12 retired · 3.4yr avg age.
Each clause is conditional:
- The total count (every piece of equipment on file, active and retired combined) always shows.
- In service and in storage always show, these are the two states that make up "active."
- Retired only appears when the retired count is above zero, there is no "0 retired" clause cluttering the line.
- The average age clause only appears once Verinode can compute a weighted average across the network (see below), it is omitted entirely while the network is still cold-starting on age data.
If your network's entity model is set to independent operators (the default, safer posture for a franchise or association network of separately owned businesses), the sub-line adds one more sentence: "Franchisee rows are anonymized (independent-operator network)." That is a plain heads-up that every per-location row further down the page will show as a stable label like "Franchisee #A1B2" rather than a real business name. Same-entity networks (a single enterprise or PE-backed roll-up operating every location under one legal business) do not see this sentence, since there is no anonymization question when every location is the same business.
Empty state. When no equipment has rolled up from any location yet, the sub-line reads exactly:
"Restoration equipment will appear as operators register their dehumidifiers, air movers, truck mounts and other field assets."
Status mix: in service, in storage, retired
"Status mix" is the network-wide total of every location's equipment broken into three buckets: in service (deployed or ready to deploy on a job), in storage (owned but not currently in active rotation), and retired (taken out of service permanently). Verinode sums each location's own status counts into these three network totals; there is no separate "status mix" panel on the hero, the sub-line sentence above is where it surfaces. The headline's active-equipment count is simply in-service plus in-storage, retired is tracked separately and only surfaces in the sub-line when it is non-zero.
Ownership mix: owned, leased, financed
Ownership mix works the same way, an aggregate across the network of how much equipment each location owns outright versus leases versus finances. It is not printed on the hero band itself, it feeds the network's equipment posture behind the scenes and is available for future drill-down and benchmark work, so don't expect to see an "owned / leased / financed" split on this page today. If your network runs a mix of ownership structures across locations (common where a franchise agreement finances startup equipment packages differently from a veteran location that has since bought its fleet outright), that mix is already flowing into the rollup even though the hero doesn't surface it as a standalone number yet.
Weighted average age
The avg age clause in the headline sub-line, and the underlying figure that feeds the Equipment >5yr tile's tone, is a weighted average, not a simple average of each location's own average age. Here is why that distinction matters: a location running 40 pieces of equipment with an average age of 2 years should count for more in the network figure than a location running 3 pieces averaging 8 years. Verinode computes this by weighting each location's average age by how many active pieces of equipment it has, then dividing the sum by the total active count across the network. A location with no equipment, or with an unknown average age, simply doesn't contribute to the weighted sum, it doesn't get treated as a zero that would drag the network average down artificially.
The result is the single "N.Nyr avg age" figure in the sub-line, and it's read the same way at the per-location level throughout the rest of the page (the Refresh Cycle row and the Equipment by Franchisee row both show each location's own average age using the same math, just unweighted per that one location).
The three secondary tiles
To the right of the headline sit three smaller figures, each with its own label and a supporting line underneath.
1. Capital value
Label: "Capital value."
This is the sum of every location's recorded equipment purchase prices across the entire active network, shown as a rounded dollar figure ($1.4M, $82k, $340, whatever the total comes to). It is a floor, not a true replacement-cost estimate: it only counts equipment where a location has actually entered what it paid. A location running equipment it never logged a purchase price for contributes nothing to this total for that equipment, so the real capital tied up in the network's fleet is very likely higher than what this tile shows.
The sub-line reads:
- "Sum of recorded purchase prices", once any location has entered at least one purchase price.
- "Awaiting purchase data", when no location in the network has entered a purchase price for any equipment yet.
2. Maintenance overdue
Label: "Maintenance overdue."
The network-wide count of equipment currently past its maintenance due date, summed across every location. This tile's tone (color) tracks the network's overall upkeep health: green when the combined count of overdue maintenance and overdue calibration is zero, yellow at a modest combined total, and red once that combined total climbs into a range worth a leadership look. The headline pill's color follows this same tone, so a red pill is your cue to open this tile before anything else on the page.
The sub-line shows whichever of these is most useful, in priority order:
- "+N due inside 90d", the count of additional equipment coming due for maintenance in the next 90 days, when that count is above zero. This is a look-ahead figure, it's not overdue yet, but it tells you what's about to become overdue if nothing changes.
- "N calibration overdue", when there's no near-term maintenance coming due but calibration is overdue somewhere in the network. Calibration overdue (equipment like moisture meters and thermo-hygrometers that need periodic recalibration to stay trustworthy for documentation and billing) is tracked as its own separate count from maintenance overdue; this clause is how it surfaces on the hero when it's the more pressing of the two.
- "Across active equipment", the default line when neither of the above applies, that is, when nothing is overdue and nothing is due inside 90 days.
Note
Maintenance overdue and calibration overdue are counted separately in the underlying data (a location can have overdue maintenance with no calibration issue, or the reverse), but this one tile only has room for one line, so the sub-line surfaces whichever is most actionable given what's actually happening in the network right now. The full split by location, maintenance count and calibration count side by side, is in the Maintenance & Calibration Risk row underneath the hero.
3. Equipment >5yr
Label: "Equipment >5yr."
The count of active equipment older than five years, network-wide, the population that's due for refresh-cycle planning (budgeting to replace aging dehumidifiers, air movers, and truck mounts before they start failing mid-job or driving up repair spend).
The sub-line reads:
- "Refresh-cycle candidates", when the count is above zero.
- "All equipment under 5 years", when it's zero, the whole active fleet is younger than the five-year mark.
This tile's tone follows its own scale rather than the maintenance tone: green when the count is zero, a neutral tone when the aged share is a modest fraction of the active fleet, and yellow once older equipment makes up a larger share of what's active. Read it as: a small aged tail is a normal, ongoing refresh cadence; a large aged share is a capital-planning conversation for the network's next budget cycle.
How the network figures are built
Every hero number is an aggregation across every location's own rollup row, computed fresh from the nightly summary:
- Totals (total equipment, active equipment, status mix, ownership mix, maintenance overdue, maintenance due in 90 days, calibration overdue, calibration due in 90 days, equipment over 5 years) are straight sums across every location.
- Capital value is a sum of each location's total purchase-value figure, but only where at least one location has a non-null figure; if no location has entered any purchase price, the tile shows the "Awaiting purchase data" empty state rather than a misleading $0.
- Average age is the weighted average described above, weighted by each location's active-equipment count.
- "N franchisees" (franchisees with equipment) counts locations with at least one piece of equipment of any status on file, active or retired.
National comparison deltas: demo accounts only
You may occasionally see a small added fragment on the secondary tiles' sub-lines, an extra clause comparing the network's figure against a national reference. This only ever appears on Verinode demo accounts. Real, live networks never see a demo-derived national comparison spliced into their own numbers, that comparison is null for every production group until a genuine cross-network equipment benchmark ships. If you are looking at a live account and don't see any such comparison fragment, that is expected, not a missing feature.
Anonymization and the small-network guard
The hero's own numbers (the headline, the pill, and all three secondary tiles) are always network aggregates and are never gated by anonymization, they show in full regardless of how many locations your network has or how your entity model is configured. What the entity model changes is only whether the hero's sub-line adds the "Franchisee rows are anonymized" sentence, a heads-up for what you'll see once you scroll down into the per-location rows.
Those per-location rows underneath the hero (Maintenance & Calibration Risk, Refresh Cycle, Equipment by Franchisee) carry their own additional guard: in independent-operators networks with very few active locations, a single tile's numbers could identify a location by elimination even under an anonymized label. When your network falls under that floor, the hero still shows in full, but the rows below it are replaced with an aggregate-only disclosure instead of per-location tiles. That mechanic, and the exact banner copy, is covered in Equipment (Assets): what HQ sees across the network.
How to use it
- 1Check the pill's color first. Green means the network's maintenance and calibration posture is clean; yellow or red means something needs attention before you scroll further.
- 2Read the sub-line for the mix: how much of the fleet is in service versus sitting in storage, and whether any meaningful share has been retired.
- 3Scan the three secondary tiles left to right: capital value tells you what's at stake financially, maintenance overdue tells you what's falling behind right now (and what's about to, via the "+N due inside 90d" clause), equipment over 5 years tells you what's coming up for replacement planning.
- 4If maintenance overdue is red or equipment >5yr is yellow, scroll down into the Maintenance & Calibration Risk row or the Refresh Cycle row to see which specific locations are driving the network figure.
Heads up
Capital value is a floor built only from purchase prices locations have actually entered, not a true replacement-cost estimate for the network's fleet. Don't read a low Capital value figure as "the network doesn't own much equipment", it may just mean purchase prices haven't been logged everywhere yet. Check the sub-line: "Awaiting purchase data" is a data-completeness signal, not a small-fleet signal.
Best-practice example
Say the hero reads 312 active equipment, pill "18 franchisees" in yellow, sub-line "354 total · 260 in service · 40 in storage · 14 retired · 4.1yr avg age." Capital value reads $1.4M ("Sum of recorded purchase prices"), Maintenance overdue reads 6 in yellow ("+3 due inside 90d"), Equipment >5yr reads 58 in yellow ("Refresh-cycle candidates"). The yellow pill already told you this is a "watch," not a "clean" network. The maintenance tile's "+3 due inside 90d" is the near-term signal: three more items are about to tip overdue on top of the six already there, worth flagging before the next maintenance cycle rather than after. Scroll into the Maintenance & Calibration Risk row to see which of the 18 locations is carrying most of that count, and into Refresh Cycle to see whether the 58 aged units concentrate in a few older locations (a targeted refresh conversation) or spread evenly across the network (a broader capital-budget conversation for next year).
Related reading
- Equipment (Assets): what HQ sees across the network, the full Equipment page: this hero plus the Maintenance & Calibration Risk, Refresh Cycle, and Equipment by Franchisee rows, and the small-network aggregate-only guard.
- What HQ sees: the network privacy boundary, how HQ's aggregate-only posture is enforced across every section, not just Equipment.
- Network health, HQ's command home and the entity-model concept (independent operators vs. same entity) that governs anonymization everywhere, including here.
- HQ overview, the sidebar, page shell, and Assets cluster (Facilities, Fleet, Equipment) every HQ section shares.
Data sources
Data sources
- 1.Locations' own equipment records (purchase price, status, ownership, maintenance and calibration due dates). Your network's franchisee locations, via nightly rollup.
- 2.Network-wide equipment aggregation. the network data, refreshed nightly by the HQ aggregate-refresh cron.