Step 7 · Evaluate Total Cost of Ownership

Most technology purchases are approved on the first-year number, because that is the number on the quote and the number the budget cycle asks for. It is also the smallest number the project will ever produce.

A five-year view changes decisions. It exposes the subscription that steps up in year three, the tags that have to be replaced in year four, the integration that carries its own annual fee, and the staff time that was never costed because it was absorbed by people already on the payroll.

Build the number in five parts. Acquisition and implementation happen once. Training happens more than once. Operations happen every year. Lifecycle costs arrive late, which is exactly why they get missed.

What it costs to get the thing. This is usually the only part on the quote.

What it costs to make it work in your department. Some of this is invoiced by the vendor. Some of it is your own people, and it is real money whether or not anyone writes it down.

Training is not a single event. It happens at go-live, again when the system changes, and again for every person hired afterward. In a department that runs shifts, the cost of training is often the cost of covering the shift.

What it costs every year to keep the system running. This is the number that has to survive a budget cycle, and the number most often missing from the original request.

What arrives after the first budget cycle and before the last one. These costs are predictable, they are rarely in the original request, and they tend to land in a year when nobody has planned for them.

Grant funding is one of the most useful tools a fire department has. It is also the most common way a department ends up owning something it cannot afford to keep.

Grant awards are generally built to buy things. The costs that follow are usually the department's to carry, and they begin the day the grant period ends.

If the department cannot identify the operating line that pays for the technology after grant funding ends, the project is not financially sustainable yet.

That is not an argument against applying. It is an argument for answering the sustainment question during the application, while there is still time to build the line into a future budget request and while the size of the request can still be adjusted to something the department can carry.

Work through this list before the application, not after the award.

Grant programs differ. Requirements vary by program, by award year, by funding source and by what is being purchased, and federal requirements sit alongside your state law, local ordinance and your own procurement policy rather than replacing them.

Do not assume that what was allowed under one award is allowed under another. For any grant-funded purchase, follow the requirements applicable to that specific grant, applicable state and local law, and your department's own procurement policies. Involve your purchasing and grant administration staff early enough that the answer can still change the plan.

FEMA's guidance for recipients and subrecipients is explicit on one point worth remembering: where federal, state, tribal and local procurement rules differ, follow the most restrictive rule.

A technically strong product can still create long-term risk if the company, ownership structure, support model, or pricing changes substantially.

This is not about guessing whether a company will survive. Your department is not in a position to assess anyone's balance sheet and should not try. What you can do is ask what your position would be under each of the changes that routinely occur in this market — an acquisition, a change of ownership, a discontinued product, a support model that moves, a price that resets at renewal — and get those answers into the contract rather than leaving them in a meeting.

None of these questions predict a company's future. They establish what your department's position would be if the future changes, which is the part you can actually control at contract time.

This is a risk-management framework, not a vendor-rating system. The Hub does not score companies on financial health, and a solicitation should not either. Treat the answers as terms to negotiate, not as a grade.

Someone will administer this system after implementation. That work has a cost even when it is absorbed by existing staff.

Absorbed cost is still cost. It shows up as a company officer doing user administration at the kitchen table, or an administrative assistant learning a reporting tool nobody budgeted to train them on. It is invisible in the business case and completely visible in that person's week.

Estimate the hours before you buy. Even a rough figure — two hours a week, a day a month — turns an invisible cost into something a budget can hold and a supervisor can plan around.

It also makes the argument for a named backup administrator while that is still a planning decision rather than an emergency. Step 8 covers who those people are and what has to be written down before go-live.