You’re standing in front of an air handler with a set of submittals in one hand and a parts list in the other. The equipment is different from the last job. The building automation system is from another manufacturer. The owner has a list of performance requirements, and the project schedule is already tight.

The first question that comes to mind is often, “Which controller do I need?”

It’s a logical place to start. But according to KMC Controls® Vice President of Business Development Jesse Shoemaker, it’s not the question that experienced integrators ask first. During a recent Stuck on a Bucket webinar, he pointed out that successful AFMS projects begin by understanding the application—not by selecting hardware.

That may seem like a subtle distinction.

In practice, it can make the difference between a smooth startup and a long day of troubleshooting.

The Hardware Isn’t the Starting Point

When a specification calls for an airflow measurement station (AFMS), it’s easy to jump straight to model numbers and controller options.

Should you use a BAC-5901 or a BAC-5971? Do you need Pressure Assist? Should the system communicate over BACnet IP or MS/TP?

Those are important decisions, but they come after you’ve answered a more fundamental question:

What is this system trying to accomplish?

Jesse explained that the application should drive every decision that follows.

Is this a retrofit or a new installation? Does the unit include a mixed-air chamber? Are you simply measuring airflow, or will it also provide unitary control? Will the AFMS operate as a standalone device, or will it integrate with an existing building automation system?

Each answer narrows the options until the right hardware becomes much more obvious.

Not Every Air Handler Has the Same Needs

One of the more interesting points from the discussion was that not every application should use the same solution.

KMC AFMS™ technology is specifically designed for equipment with a mixed-air chamber, where outside air and return air blend before entering the supply fan. In these applications, accurately determining outdoor airflow requires more than simply measuring fan performance. The controller develops a characterized airflow performance curve that relates damper position to the percentage of outside air entering the unit.

That’s a very different challenge from a dedicated outside air system.

As Jesse noted during the webinar, if you’re working with a 100 percent outside air unit, an AFMS may not be the appropriate tool. In those situations, a simpler airflow measurement approach often makes more sense because the application itself is different.

The lesson is broader than any single product.

Different applications deserve different solutions.

Startup Success Begins Long Before Startup

One of the themes that surfaced repeatedly throughout the webinar was that many commissioning problems don’t actually begin during commissioning.

They begin much earlier.

A sensor wasn’t specified correctly. The airflow measurement method didn’t fit the equipment. Someone assumed one rooftop unit behaved like another. By the time the technician arrives for startup, those decisions have already been made, and the commissioning process becomes an exercise in overcoming them.

That’s why experienced integrators spend so much time evaluating the equipment before they ever begin programming or calibration. Good startup isn’t just about following the right procedure. It’s about making the right decisions from the beginning.

Ask Better Questions

It’s easy to think of building automation as a collection of products.

Controllers.

Sensors.

Actuators.

Software.

Experienced integrators see something different. They see applications.

When the application comes first, product selection becomes much easier because every component has a clear purpose. The hardware supports the problem you’re solving instead of becoming the focus of the project.

It’s a simple shift in perspective.

And as anyone who’s spent time commissioning systems can tell you, it’s often the small decisions made at the beginning of a project that have the biggest impact when startup day finally arrives.

Watch the full Stuck on a Bucket episode!