Controls

Why BAS Trend Data Is Evidence—Not Proof by Itself

Trend logs can reveal schedules, resets, staging, cycling, and control instability, but their meaning depends on point accuracy, timestamps, intervals, and operating context.

A field-oriented framework for collecting and interpreting building automation system trends without mistaking available data for verified performance.

Technical overview

Using BAS Trend Data Well: field logic map

01Trends are a record of reported values
02Build the trend around the question
03Validate before interpreting
04Use trends with functional testing
Follow the subject from its engineering basis through field verification and documented acceptance.
01

Trends are a record of reported values

A BAS trend shows what selected points reported at selected times. It does not automatically establish that the sensor was accurate, the point was mapped correctly, the command reached the device, or the physical system responded as indicated.

That distinction matters when a command, status, and feedback point all originate from the same controller logic. Three lines on a graph may look like independent confirmation while representing variations of one internal software state.

02

Build the trend around the question

Start with a specific question: Does static pressure reset as terminal demand changes? Does a valve close before an outdoor-air damper opens? Does a chiller stage only after available capacity is exhausted? The required points, interval, duration, and operating conditions follow from that question.

  • Commands, physical feedback, and independent process variables
  • Setpoints, calculated setpoints, limits, enable conditions, and overrides
  • Equipment status, speed, load, alarms, and safeties
  • Outdoor conditions, occupancy, schedules, and representative demand
  • A sampling interval capable of showing the transition or cycling rate
03

Validate before interpreting

Check point names, units, scaling, timestamp alignment, sensor location, calibration evidence, and missing data. Compare critical points with an independent field reference. A five-minute timestamp error can completely change the apparent cause-and-effect relationship during a short control sequence.

Also look for compression, change-of-value logging, smoothing, and overwritten history. These features can be appropriate for storage management but can hide short cycling, overshoot, or alarm delays.

04

Use trends with functional testing

Trends are especially valuable when they extend a witnessed functional test across nights, weekends, changing weather, and different loads. The field test establishes point credibility and physical response; the longer trend shows whether that behavior persists.

When the data suggests a problem, return to the system. Observe the device, verify the sensor, review overrides, and reproduce the condition safely. Trend analysis should direct investigation rather than replace it.

Field application

A practical review checklist

  1. 01

    Write the performance question before selecting trend points.

  2. 02

    Include commands, feedback, process variables, setpoints, and enable conditions.

  3. 03

    Confirm point units, scaling, location, timestamps, and sampling behavior.

  4. 04

    Compare critical BAS values with independent field measurements.

  5. 05

    Preserve the raw export and document exclusions or data cleaning.

Authoritative orientation

References and further reading

Use the current adopted or licensed edition applicable to the project. These links provide public orientation and do not reproduce protected standards.