Fire Protection Data Model — Inspections | FieldCamp

How a fire protection and life safety business runs in FieldCamp — device registers, per-asset inspection history, deficiencies, and NFPA inspection agreements.

Fire protection and life safety is the classic asset-and-inspection trade, and FieldCamp models it on the same connected core records every business starts with — plus a purpose-built layer for the devices you inspect.

The transactional side of the business already runs on the core: a customer books an inspection, you schedule and dispatch a crew, you quote any repairs, and you bill.

What this trade adds on top is a way to track each extinguisher, alarm panel, sprinkler riser, and backflow as its own record — with its own compliance schedule, its own multi-year inspection history, and its own follow-up work when it fails.

FieldCamp works for any size, from a single-truck inspector to a multi-location life safety firm, residential or commercial — and everything on this page can be tailored to how your shop actually runs.

What the core already gives you

Most of a fire protection business is already covered by records that work on day one. You do not build these — they ship connected and ready.

The recurring inspection is a Job set to repeat on an NFPA cadence — monthly, quarterly, semi-annual, annual, or five-year. FieldCamp generates a Visit for each cycle automatically.
The on-site inspection checklist and readings are captured on a job form, the guided capture surface a tech fills in the field. Photo capture and a signature on completion are built in.
Quoting repairs and billing ride on Estimates and Invoices, including the Good / Better / Best multi-option quote and a deposit on larger work.
The customer book, billing-versus-service addresses, and crew assignment all live on core Customers, Jobs, Visits, and Team Members.

The core handles scheduling, dispatch, field capture, and billing. The fire protection layer adds the durable asset register, the per-device history, the deficiency follow-up, and the inspection agreement.

What fire protection and life safety adds

On top of the core records, this trade adds five custom objects — record types built on FieldCamp's customization engine, each with its own fields, links, workflow, and page layout.

Together they answer the questions the core cannot: which devices live at this building, when was each one last inspected and what did it pass, what failed and where does that repair stand, and what does the inspection agreement cover.

Site (Building / Property)

A Site is one physical building or property under a customer. Commercial customers are often a portfolio — one customer owns many buildings, each with its own device register and its own inspection schedule.

It carries the site name and address, a building type (office, warehouse, multi-family, healthcare, retail, or school), the authority having jurisdiction, access notes such as gate codes and the riser-room location, and a site contact.

It links to its customer, to the inspection agreement that covers it, and to its devices and inspection history.

Its page is assembled from a header, a link back to the customer, the address and a map, the access instructions, and tables of the devices and the inspection history at that building.

Device (the inspectable asset)

The Device is the heart of the model — one record per physical asset you inspect. A commercial building can hold dozens to thousands of them, each individually tracked.

Field	What it holds
Barcode / tag ID	The device's printed identifier, with a format check
Device type	Extinguisher, alarm panel, smoke detector, sprinkler head, riser, fire pump, backflow, kitchen hood, emergency light, or exit sign
NFPA standard	NFPA 10, 25, 72, 13, 80, or 96
Manufacturer, model, serial number	The make and unique identity of the unit
Location in building	Where it sits, such as "2nd floor, east stairwell"
Install date, manufacture date	When it was placed and made
Last and next hydrostatic test	The pressure-test dates that apply to the device
Inspection frequency	Monthly, quarterly, semi-annual, annual, or five-year
Last inspected, next due	The running compliance dates
Status	Where the device sits in its lifecycle
Warranty expiry	When the unit's warranty ends
Photo	A picture of the device

A Device belongs to its Site for commercial work, or links directly to the customer for a residential home. It owns its own inspection history and any deficiencies raised against it.

Its page leads with a header showing the live status, then a link to the building, the full device details, an asset card for serial and warranty, a service-history block, and a compliance block that counts down to the next due date — exactly the NFPA next-due use case.

Below that are tables of inspection records and deficiencies, a timeline, and files.

FieldCamp stores each device's barcode or tag ID and counts down its next-due date, but it does not include a built-in mobile tag scanner that opens a device when you scan it.

The identifier lives on the record so you can search and label by it.

Inspection Record (per-device result)

An Inspection Record is one row for each time a device was inspected. This is what makes per-asset history real: "when was this extinguisher last tagged, and what was the result each time" becomes a list you can read down.

It captures the inspection date, the result (pass, fail, or pass-with-deficiency), the technician, and a link to the actual Visit and Job it came from. It can hold readings such as pressure or weight, and the delivered report.

It belongs to its device and links to the visit, job, and team member involved. Its page shows the device it belongs to, the result details, the NFPA job form rendered inline, and files.

For richer guided capture in the field, the job form on the visit does the heavy lifting; the inspection record is the durable summary row that lives on the device.

Deficiency (failed item to repair revenue)

When a device fails, the trade raises a Deficiency — the tracked open problem that converts into repair work. It ties back to the exact device and the inspection that found it.

It carries a description, a severity (critical, major, or minor), a link to the inspection record that surfaced it, a photo, and the recommended fix. As it progresses it links to the Estimate it was quoted on and the Job that repairs it.

A Deficiency belongs to its device. When it moves to the quoted stage, an automation can convert it into an estimate, carrying the description and recommended fix onto a line item.

A critical deficiency can notify the account manager the moment it opens, and an open critical deficiency can flip its device to the failed status until it clears.

Its page shows the device it belongs to, the deficiency details, a status banner, convert-to-estimate and convert-to-job actions, files, and a timeline.

Inspection Agreement (recurring revenue)

An Inspection Agreement is the recurring inspection contract under a customer, and optionally a site. It is where the maintenance relationship lives.

It holds the agreement name, the coverage (which systems are included — extinguishers, alarm, sprinkler, suppression), the frequency, start and end dates, the contract value, an auto-renew toggle, and a link to the recurring Job that delivers it.

It belongs to its customer, links to the site and the recurring job, and covers a set of devices. Its page shows the contract details, terms, a table of covered devices, the recurring schedule, and the financial summary.

A compliance block counts down to renewal as the agreement nears its end date.

The inspection agreement does not run the schedule by itself — it points at a recurring Job. That Job, set to the NFPA cadence, is what generates each Visit, assigns the crew, and drives the on-site job form.

The custom objects add the asset register, the history, the deficiencies, and the contract; scheduling and dispatch stay in the core.

The inspection lifecycle

Each device moves through a compliance lifecycle as its due date approaches and as inspections pass or fail.

A failed device raises a deficiency, and that deficiency runs its own track from found to cleared — the path that turns a failed inspection into approved repair revenue.

When a deficiency reaches the quoted stage it can convert straight into an estimate, so the failed item the tech found in the field becomes a quote the customer can approve.

Residential vs commercial

The same model serves both. The difference is depth, hierarchy, and which guardrails you turn on.

Residential

A home usually skips the Site layer — a handful of devices hang directly off the customer, often an annual extinguisher service plus a monitored alarm test. Device counts are low, the paperwork is a tag and a receipt, and a signature on completion is optional. Billing is per job with a deposit on install.

Commercial

A property manager or facility owner owns many buildings, so the full customer-to-site-to-device chain is used, each building owning its own register and schedule. Device counts run into the hundreds or thousands, NFPA cadences layer per system, and the fire-marshal report and deficiency paper trail are the product. A signature and minimum photos are typically required on completion and on clearing a deficiency. Billing is a recurring inspection agreement plus separate repair quotes from deficiencies.

The model is built once. Residential simply leaves the Site layer empty and turns on fewer required steps; commercial uses the full hierarchy and stricter guardrails.

Built on the customization engine

Every object, field, workflow, and page above is built on the same engine you can reach yourself — there is no separate fire protection product, only the core records plus a tailored layer.

Add or rename objects and fields on any record, shape the device and deficiency stages and workflows to match how you track compliance, and arrange each page from the library of record layouts.

Start with what works on day one, then tailor as your routes and contracts grow.

Jobs

The recurring inspection work order that schedules each cycle and drives every visit.

Visits

The field appointments where devices are inspected, with signatures and on-site forms.

Estimates & Invoices

The repair quotes deficiencies convert into, and the invoices that follow.

Custom objects & fields

How the device, deficiency, and agreement records are built and tailored.

Coming from ServiceTrade

Most fire and life safety contractors on ServiceTrade can bring their structure into FieldCamp directly — the companies, the locations under them, the assets at each location, the recurring inspection services, the deficiencies, and the quotes and invoices all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your shop to a fixed one.

In ServiceTrade	In FieldCamp	Notes
Company	Customers	The party responsible for billing. FieldCamp keeps billing, service, and property addresses on one record.
Location	A Site or Building — as a custom object under the customer	ServiceTrade's one-company-to-many-locations split; model each building as its own record with its own device register and schedule.
Asset	Equipment, or a Device custom object	The inspectable unit — extinguisher, alarm panel, sprinkler riser, backflow — tracked with serial, tag ID, and full inspection history.
Service Request	Requests	The inbound inspection or repair call, with inspection-scheduled and quote stages already built in.
Job	Jobs	The work order — one-off, multi-day, or recurring.
Appointment	Visits	Each scheduled trip on a job, with dispatch, en-route, on-site, and sign-off.
Recurring Service	Service Agreements plus a recurring Job	The inspection contract carries coverage and renewal; the recurring Job runs the NFPA cadence and generates each Visit.
Inspection	A custom Inspection Record object plus Job Forms	The on-site checklist and readings ride on a job form; the durable per-device result lives on the inspection record.
Deficiency	A custom Deficiency object	The failed item tied to its asset and the inspection that found it, with severity and a recommended fix.
Quote	Estimates & Invoices	A deficiency converts straight into a repair quote, with Good / Better / Best and deposits.
Invoice	Estimates & Invoices	Partial and full payments, with overdue tracking.
Technician	Team Members	Carry certifications as skills and territory as service areas.
Inspection / deficiency report	Job form output and the delivered report on the inspection record	The completed form and its photos and signature produce the report attached to the record.

What you gain. In ServiceTrade the structure is fixed — the objects, their fields, and how they relate are set for you.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects and fields and your own stages and workflows.

One honest difference. ServiceTrade ships code-specific inspection forms, mobile barcode and QR scanning that opens an asset when you scan its tag, and inspection and deficiency reports in AHJ-ready formats out of the box.

FieldCamp stores each device's barcode or tag ID and counts down its next-due date, and its job forms and reports cover the on-site capture and the delivered paperwork — but the built-in tag scanner and the pre-built code-format report templates are not shipped by default.

If barcode scanning or a specific report format is central to how you work, plan that part of the move deliberately.