BACnet trend logs and any other CSV

The canonical shape

Whatever the system, Energy Agent wants a wide table: one timestamp column, then one column per point, with the unit in the header. This is what a BACnet trend-log export, a Niagara history table, a data logger download and a hand-built spreadsheet all reduce to.

One timestamp column, then one column per point. Put the unit in the header, for example "AHU-1 Supply Air Temp (F)" or "CHW-VLV (0-100)". Name each column with the equipment tag first so points from the same unit group together.

• Timestamps in ISO form ("2025-03-01 00:15:00") or any unambiguous local format. Tell us the timezone if the file does not carry one.
• Status points as 0/1, On/Off or True/False.
• Commands in percent ("(%)" or "(0-100)"), temperatures in F or C, pressure in inWC or Pa, flow in cfm or gpm. Say which if the header cannot.
• Blank cells for missing samples, not zeros.

Naming convention

Name each column "<equipment tag> <point name> (<unit>)": "AHU-1 Supply Air Temp (F)", "VAV-12 Damper (%)", "Chiller-2 Status". The equipment tag lets Energy Agent group points into units; the point name maps to the sensor role; the unit removes guesswork. Common vendor abbreviations (SAT, MAT, RAT, DSP, CHWST, OAD) are also recognised.

BACnet trend logs specifically

Trend Log objects on BACnet controllers can be read with the vendor tool or a generic BACnet explorer and exported to CSV. Each log usually comes out as its own file with a timestamp and a value column. Send them all; files that share a timestamp basis are joined. Name the files after the point if the export does not.

You do not need to clean the file. Energy Agent checks timezone, gaps, duplicate timestamps, frozen channels and unit mismatches before any rule runs, and tells you what it found.

Common questions