---
title: "Asset Management"
url: "https://fieldcamp.ai/hvac-software/commercial/asset-management/"
date: "2026-07-27T09:22:53+00:00"
modified: "2026-08-07T11:21:49+00:00"
type: "Article"
resource: "https://fieldcamp.ai/hvac-software/commercial/asset-management/"
timestamp: "2026-08-07T11:21:49+00:00"
author:
  name: "Jeel Patel"
categories:
  - "Uncategorized"
word_count: 2186
reading_time: "11 min read"
summary: "Home›HVAC Software›Commercial›Asset Management"
description: "Track every HVAC unit by site, model and serial, with full service history attached — so quotes, PMs and warranty calls run off the equipment record, not m..."
keywords: "Uncategorized"
language: "en"
schema_type: "Article"
related_posts:
  - title: "Free Construction Estimate Template"
    url: "https://fieldcamp.ai/construction-software/estimate-template/"
  - title: "Field Service Software With Xero Integration Singapore 2026"
    url: "https://fieldcamp.ai/sg/blog/field-service-software-xero-integration/"
  - title: "Free Cleaning Estimate Template"
    url: "https://fieldcamp.ai/cleaning-business-software/estimate-template/"
---

# Asset Management

_Published: July 27, 2026_  
_Author: Jeel Patel_  

[Home](/)›[HVAC Software](/hvac-software/)›[Commercial](/hvac-software/commercial/)›Asset Management
Commercial · Asset Management

# HVAC asset management software that knows every unit on every roof — before the truck leaves the shop.
A record of every unit you service — make, model, serial, warranty, and full service history — attached to the site and client it belongs to. Part of FieldCamp’s [commercial HVAC software](/hvac-software/commercial/), which itself sits inside FieldCamp’s [HVAC software](/hvac-software/) platform.

[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)Bring one building’s equipment list — we’ll model it live.

Nameplate

as typed, queryable fields

Two warranties

parts and labour, tracked apart

Unit-level

history, not job-level

Beacon Property Group›Sites›Beacon Tower Downtown12 units on site<svg aria-hidden="true" fill="none" height="14" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="14"><rect height="18" rx="1.5" width="16" x="4" y="3"></rect><path d="M8 7h2M14 7h2M8 11h2M14 11h2M8 15h2M14 15h2M10
  21v-3h4v3"></path></svg>Site equipmentsite_equipment<svg aria-hidden="true" fill="none" height="14" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="14"><rect height="18" rx="1.5" width="16" x="4" y="3"></rect><path d="M8 7h2M14 7h2M8 11h2M14 11h2M8
  15h2M14 15h2M10 21v-3h4v3"></path></svg>Beacon Tower Downtown

Client · Beacon Property Group

12 unitsRoof access: NE stairwellContact: chief engineer<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12 9.8c0-3.2 1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6 5.8 3.6 0 1.6-1.4
  2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8 0-2 2.2-3 6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3
  6z"></path></svg>RTU-1Rooftop package unitGood<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12 9.8c0-3.2 1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6 5.8 3.6 0 1.6-1.4
  2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8 0-2 2.2-3 6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3
  6z"></path></svg>Chiller 1 · Trane RTAC-150Chiller · central plantDue soon<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0
  0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12
  9.8c0-3.2 1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6 5.8 3.6 0 1.6-1.4 2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8
  0-2 2.2-3 6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3 6z"></path></svg>Chiller 2Chiller · basementGood<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0
  0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12
  9.8c0-3.2 1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6 5.8 3.6 0 1.6-1.4 2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8
  0-2 2.2-3 6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3 6z"></path></svg>Compressor 2Central plantOverdue<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12 9.8c0-3.2 1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6
  5.8 3.6 0 1.6-1.4 2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8 0-2 2.2-3 6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3
  6z"></path></svg>Asset recordequipment_history<svg aria-hidden="true" fill="none" height="13" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="13"><circle cx="12" cy="12" r="2.2"></circle><path d="M12 9.8c0-3.2
  1.6-5.8 3.6-5.8 1.6 0 2.4 1.4 2.4 2.8 0 2-2.2 3-6 3zM14.2 12c3.2 0 5.8 1.6 5.8 3.6 0 1.6-1.4 2.4-2.8 2.4-2 0-3-2.2-3-6zM12 14.2c0 3.2-1.6 5.8-3.6 5.8-1.6 0-2.4-1.4-2.4-2.8 0-2 2.2-3
  6-3zM9.8 12c-3.2 0-5.8-1.6-5.8-3.6 0-1.6 1.4-2.4 2.8-2.4 2 0 3 2.2 3 6z"></path></svg>Chiller 1

Central plant · Beacon Tower Downtown

Due soonOverviewService historyFilesNameplate & specsManufacturerSelectTraneModelTextRTAC-150Serial numberTextBT-CH1-4471Install dateDateMar 14, 2019Service history · on this unitApr 12, 2026

Condenser coil clean · water treatment check · Marcus T.
<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" style="display:inline-block;vertical-align:-1px" viewbox="0 0 24 24" width="10"><path d="M23 19a2 2 0 0 1-2 2H3a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h4l2-3h6l2 3h4a2 2 0 0 1 2 2z"></path><circle cx="12" cy="13" r="4"></circle></svg> 4Nov 03, 2025

Quarterly PM visit · readings logged · Dana R.
<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" style="display:inline-block;vertical-align:-1px" viewbox="0 0 24 24" width="10"><path d="M23 19a2 2 0 0 1-2 2H3a2 2 0 0
  1-2-2V8a2 2 0 0 1 2-2h4l2-3h6l2 3h4a2 2 0 0 1 2 2z"></path><circle cx="12" cy="13" r="4"></circle></svg> 2<svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2
  1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg>“When did we last touch Chiller 1?” Answered from the unit record: Apr 12 — condenser coil clean, Marcus T., 4 photos. One click, not an archaeology dig through closed jobs.

<svg aria-hidden="true" class="flex-shrink-0" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5
  9l5.2-1.6L12 2z"></path></svg> History lives on the unit, not the job**Contractor-side, not owner-side.** This tracks *your customers’* equipment — see the disambiguation below.

Rooftop units Chillers Split systems Portfolios
01 What it is

## What is HVAC asset *management software?*

HVAC asset management software gives contractors a record of every unit they service — make, model, serial number, install date, warranty, and full service history — attached to the site and client it belongs to. It tracks the lifecycle of your customers’ equipment, from install date to replacement, so every estimate, visit, and invoice lands on the same unit record instead of scattering across jobs.

FieldCamp models it directly: [each client holds its sites, each site holds its equipment](https://docs.fieldcamp.ai/data-model/commercial-hvac), and each unit carries its own nameplate data, warranty dates, and service history. Generic equipment tracking stops at a list of assets with tags; contractor-grade tracking ties each unit to the service relationship around it — the agreements that cover it, the visits that touched it, the invoices it generated. That’s the difference this page is about.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Assets vs inventory — the boundary that matters.**</mark> This page covers equipment *installed at a customer site*: it has a serial number, a warranty, and a service history. Parts and materials *you* own, sitting in the warehouse or on a van before they’re fitted, belong to [HVAC inventory](/hvac-software/inventory/). Mixing the two is how a warehouse count ends up including units already bolted to somebody’s roof.

02 How it works

## How commercial contractors track customer equipment — *the four-step loop.*

Asset management isn’t a module you fill in later. It’s a loop that runs on every job: capture the nameplate, attach the unit, point the work at it, answer from it.

1

Capture

### Nameplate data, as structured fields

Make, model, serial number, tonnage, refrigerant type, filter size, install date — entered once on the unit as typed fields, not buried in a job note. However the data gets captured, what matters is where it lands: as structured, queryable fields the whole system can use.

2

Attach

### To the site and client it belongs to

The unit lives under its site, the site under the client — a hierarchy, not a flat list. When the portfolio is forty buildings, that structure is the only thing keeping hundreds of units straight, and it’s why the office can pull one building’s full asset list in a click.

3

Point

### Everything at the unit record

The equipment isn’t a note in a job — it’s an object the whole system points at. [Estimates](/hvac-software/estimating/), visits, and invoices all reference the unit, so every job closed against a chiller adds to that chiller’s history: line items, technician notes, photos.

4

Answer

### From the record, not from memory

The tech opens the work order already knowing what’s on the roof. The office answers “when did we last touch that chiller?” in one click. Renewal and replacement conversations start from install dates and warranty status instead of guesswork.

03 The asset record

## What should an equipment record contain? *Everything on the nameplate — and everything since.*

A complete asset record holds three layers: identity (make, model, serial number, location), specifications (tonnage, refrigerant type, filter size, install date, parts and labour warranty expiry), and history (every visit, what was done, line items, technician notes, photos). Together they make a searchable equipment database of every unit you service.

01

Identity

make · model · serial · where it physically sits

02

Specifications

tonnage · refrigerant · filter size · install date · warranty expiries

03

History

every visit, line items, notes and photos — on the unit

04 Key capabilities

## What to look for in equipment tracking software — *the checklist.*

A list of assets is the starting point, not the product. These six capabilities decide whether the record actually saves truck rolls — each one native in FieldCamp rather than an add-on module.

### The complete asset record

Every unit carries make, model, serial number, tonnage, refrigerant type, filter size, install date, and location as typed fields. And because FieldCamp runs on a [customizable data model](/customizable-data-model/), the record isn’t fixed — add belt sizes, economizer details, BAS points, or whatever your shop actually tracks, without a developer.

### Parts warranty vs labour warranty

The two expiries are different dates with different money attached, so they’re tracked as separate fields on the unit. Before the office quotes a repair it can see whether the part, the labour, both, or neither is still covered — and quote accordingly instead of eating a covered part or billing one.

### Unit-level service history

Every visit rolls up to the equipment it touched: the date, what was done, the line items billed, the technician’s notes, and the photos taken. History attaches to the unit, not just the job — so five years of work on Chiller 1 reads as one timeline instead of fragments across closed work orders.

### Equipment details in the field

The scheduled visit carries the unit record with it, so the tech sees model, serial, filter size, warranty status, and the last technician’s notes before leaving the shop — and brings the right parts the first time. Scheduling and the asset list share one system: see [HVAC scheduling](/hvac-software/scheduling/).

### Site access notes and contacts

A tech sent to a commercial site without the access code, the roof entry, or the right on-site contact is the classic wasted trip. Those details live on the site record — with separate contacts for building access and payments — so configured work records present the relevant site context to the technician.

### An asset list built for portfolios

A dozen units on one roof, hundreds across a client’s forty buildings — the hierarchy holds it without workarounds. No fake customers per building, no address-line hacks. One client, its sites, their equipment: the structure a property-management portfolio actually has. See [the commercial service lifecycle](/hvac-software/commercial/lifecycle/).

05 The disambiguation

## Asset management software vs CMMS — *which side of the roof are you on?*

They track the same equipment from opposite sides of the service contract. Contractor-side asset management tracks your customers’ equipment; a CMMS is the building owner’s system for maintaining their own assets. Most search results for “HVAC asset management” are owner-side facility platforms — this page, and FieldCamp, are the contractor side.

| Dimension | <svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg> Contractor-side (FieldCamp) | Owner-side (CMMS / CAFM) |
|---|---|---|
| Who runs it | The HVAC contractor — office, dispatch, and techs | The building owner’s in-house facility team |
| Whose equipment | Your customers’ units, across every client and site you serve | The owner’s own buildings and assets |
| What it connects to | Estimates, visits, invoices, service agreements, projects | Internal work orders, asset registries, facility budgets |
| Typical products | Field service management platforms | CMMS and CAFM platforms sold to facility teams |
| The question it answers | “What’s on that roof, and when did we last touch it?” | “What maintenance does our own portfolio need this quarter?” |

If you service other people’s buildings, you want the left column. If you *own* the buildings, you want the right — and this isn’t the page for it.

06 One record

## The asset sits inside one connected record — *not its own silo.*

Equipment tracking pays off when the rest of the operation points at it. The unit record sits in the middle of the client → sites → equipment → agreements → projects chain — one record from the first service call to the retrofit that eventually replaces the unit.

01

Client

1 account

02

Sites

3 sites, with access notes

03

Equipment

47 units — the layer everything points at

04

Agreements

PM scope · renewal date

05

Projects

retrofit · phases · billing

Which is why a [PM agreement](/hvac-software/commercial/preventive-maintenance/) can scope specific units rather than a vague building, why a [retrofit project](/hvac-software/commercial/project-management/) knows exactly which units it replaces, and why the [dispatcher](/hvac-software/dispatch/) can see what the visit is actually for.

07 Any size

## Model installed equipment around *the client portfolio.*

FieldCamp ships a commercial HVAC template out of the box — client, sites, equipment, agreements, projects, pre-structured. Because that [data model is customizable](/customizable-data-model/), teams add the fields and statuses their equipment programme requires rather than working around a fixed form.

Track the one nameplate field your manufacturer cares about. Add a lifecycle stage between active and retired. [Attach a warranty-claim object to the unit](https://docs.fieldcamp.ai/data-model/custom-objects-and-fields). None of it needs a developer, and none of it means a different product tier.

08 Why it matters

## Never climb a roof blind. *Never answer from memory.*

01

### Fewer second trips

Filter size, refrigerant type, and the last tech’s notes travel with the visit — so the van carries the right part the first time.

02

### Warranty money stops leaking

Parts and labour expiries are separate fields, so the office knows what’s covered before it quotes — instead of eating a covered part or billing one and losing the account.

03

### Replacement conversations get evidence

Install date plus [five years of visit history on the unit](https://docs.fieldcamp.ai/job-management/tracking-job-logs) turns “it might be time” into a case a facilities director can take to their board.

04

### The knowledge outlasts the technician

When access notes and equipment quirks live on records instead of in a senior tech’s head, turnover stops costing you the account’s history.

09 FAQ

## HVAC asset management, *answered.*

**What is HVAC asset management software?**

Software that gives a contractor a record of every unit they service — make, model, serial number, install date, warranty, and full service history — attached to the site and client it belongs to, so every estimate, visit, and invoice lands on the same unit record.

**How is this different from inventory?**

Inventory tracks parts and materials *you* own before they’re fitted — warehouse, van, job site. Asset management tracks equipment already installed at a customer site, with its serial number, warranty, and service history. Keeping them separate is what stops fitted units inflating your stock count. See [HVAC inventory](/hvac-software/inventory/).

**What should an equipment record contain?**

Three layers: identity (make, model, serial, location), specifications (tonnage, refrigerant, filter size, install date, parts and labour warranty expiry), and history (every visit with its line items, notes, and photos).

**Why track parts and labour warranty separately?**

Because they’re different dates with different money attached. A part can still be covered while the labour isn’t — and quoting without knowing which is how a shop either eats a covered part or bills for one.

**Does the technician see the equipment record in the field?**

Yes. The scheduled visit carries the unit record, so model, serial, filter size, warranty status, and the previous technician’s notes are available before leaving the shop.

**How does it handle a client with dozens of buildings?**

Through the hierarchy: one client, its sites, and each site’s equipment. Hundreds of units stay organised without creating a fake customer per building.

**Is this a CMMS?**

No. A CMMS is the building owner’s system for maintaining their own assets. This is the contractor’s system for tracking the equipment they service for customers. Same machines, opposite sides of the contract.

**Can I add my own fields to a unit?**

Yes — belt sizes, economizer details, BAS points, a warranty-claim object. The equipment record sits on a customizable data model, so it adapts without a developer.

**Do PM agreements know which units they cover?**

Yes — an agreement scopes specific equipment rather than a vague building, which is what lets a recurring workflow create the right visits for the right units.

**How much does it cost?**

Pricing depends on portfolio size, equipment volume, the fields your programme requires, and implementation scope. Bring one building’s equipment list to a demo and we’ll model it.

Related

## The rest of the commercial operation.

[Commercial HVAC Software The platform view — every module the asset record feeds.](/hvac-software/commercial/)[Commercial Service Lifecycle How the whole account is structured, layer by layer.](/hvac-software/commercial/lifecycle/)[Commercial Preventive Maintenance PM agreements scoped to the units this record holds.](/hvac-software/commercial/preventive-maintenance/)[HVAC Project Management The retrofit that eventually replaces the unit.](/hvac-software/commercial/project-management/)[HVAC Inventory The other side of the boundary — parts you own, before they’re fitted.](/hvac-software/inventory/)[HVAC Software The whole platform this record sits inside.](/hvac-software/)[Maintenance Agreements Agreements that renew against covered equipment.](/hvac-software/maintenance-agreements/)[HVAC Scheduling Where the visit that carries the unit record gets booked.](/hvac-software/scheduling/)[HVAC CRM The client and site records equipment hangs from.](/hvac-software/crm/)

Get started

## Want every unit on every roof *on the record?*

Fifteen minutes. Bring one building’s equipment list — we’ll build the site, the units, the warranty dates, and show what the technician sees before the van leaves.

[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)


---

_View the original post at: [https://fieldcamp.ai/hvac-software/commercial/asset-management/](https://fieldcamp.ai/hvac-software/commercial/asset-management/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_  
_Generated: 2026-08-07 11:21:50 UTC_  
