Verdigris + Honeywell Forge: The Validated Layer

Key takeaways

You're a Honeywell Forge shop. Enterprise Buildings Integrator (EBI) handles BACnet, Modbus, and LonWorks; Forge runs analytics on top. Verdigris does not replace either.
Forge analyzes whatever EBI delivers. EBI polls field protocols at seconds-cadence by design. That is correct for HVAC, lighting, and life-safety, but the wrong regime for sub-cycle electrical waveform retention.
Verdigris is purpose-built for critical-power paths. EV2 sensors install directly on circuits and capture continuous 8 kHz waveforms. This is Verdigris's own sensor layer, not derived from EBI polling.
Intelligence flows outbound from Verdigris to Forge and to operator workflows via MQTT, REST API, Modbus, and BACnet emulation. EBI sees Verdigris as a native BACnet device on the network. Zero integration lift, no EBI config change required.
Verdigris is the system of record at the validated layer. It recovers stranded capacity on UPS, PDU, and busway paths that a building-wide platform cannot resolve by construction.

What Honeywell does well

Honeywell's stack in mission-critical buildings runs on two pieces working together. Enterprise Buildings Integrator (EBI) is the BMS, with native support for BACnet, Modbus, LonWorks, and OPC, often deployed alongside the Niagara framework for OT field integration. Honeywell Forge for Buildings (Forge Performance+ in current naming) is the analytics platform that sits on top of EBI and runs operational-optimization, energy, and alarm-management workflows across the estate.

That pairing covers HVAC, lighting, occupancy, life-safety, and BMS-tier electrical metering. EBI's alarm tooling and Forge's energy and operations workflows give facilities teams a unified control surface across thousands of points. For multi-site enterprises standardized on Honeywell building-automation, this is the system of record for HVAC and thermal performance, and Honeywell's services organization and brand reach in mission-critical facilities are genuine differentiators.

A note on electrical metering specifically: Honeywell's strength is BMS and analytics, not the meter itself. Most Honeywell sites use third-party electrical meters (Schneider, Eaton, Veris, and others) wired into EBI over BACnet or Modbus; Forge analyzes whatever EBI delivers. ControlEdge PLCs and HCE600-class controllers extend EBI into process-automation paths but are not native power-meter products.

Life-safety workflows are consistent with NFPA 72 fire-alarm signaling requirements. Those workflows continue unchanged when Verdigris is deployed. Verdigris does not replace any Forge or EBI capability.

Why not just configure Honeywell Forge for higher-frequency capture?

Operators standardized on Honeywell ask this directly: "If Forge is the analytics layer, can't we just turn up the sample rate?" The answer is that Forge does not own the sample rate. Forge analyzes whatever EBI delivers, and EBI's field-protocol stack is the ceiling.

EBI talks to the building over BACnet, Modbus, and LonWorks (ISO/IEC 14908), typically via Niagara for OT integration. Those protocols were designed for HVAC setpoints, lighting state, damper position, occupancy, and life-safety polling. Those phenomena move on the scale of seconds to minutes. Default poll cadence on BACnet and Modbus points sits in the seconds range; LonWorks is similar. That is correct engineering for the workloads BMS protocols were built for. It is the wrong regime for sub-cycle electrical-waveform retention. Rectifier-diode signatures, capacitor ESR drift, and harmonic shifts per IEEE 519 all live in the millisecond range, between BMS polling samples.

"Configure Forge for higher frequency" does not move that ceiling. Forge cannot analyze waveform content the EBI / Niagara layer never acquired. Tightening Forge's polling on EBI points only multiplies the same coarse samples; it does not synthesize the sub-cycle waveform.

Honeywell's own electrical-metering posture compounds the gap. Because most Honeywell sites rely on third-party power meters wired into EBI over BACnet or Modbus, the upstream meter itself is also a polling-cadence device. Even at the meter, sub-cycle waveform retention is not in the data path.

Verdigris's pretrained ML for rectifier degradation, capacitor ESR drift, and harmonic failure signatures does not exist in Forge or EBI analytics. Forge is building-wide. Verdigris is purpose-built for critical power.

Verdigris EV2 sensors are an independent acquisition layer that bypasses the EBI / Niagara polling ceiling. They install directly on critical-power circuits and capture continuous 8 kHz on the conductor. Forge keeps doing HVAC, lighting, life-safety, and BMS-tier electrical analytics on EBI polling. Verdigris adds continuous waveform intelligence at sampling rates the EBI architecture cannot deliver, then flows validated outputs back into Forge over MQTT, REST, Modbus, and BACnet emulation.

Where the architecture limits visibility

Forge plus EBI is building-wide by design. HVAC, lighting, life-safety, occupancy, and electrical are stitched together through EBI's field-protocol layer (BACnet, Modbus, LonWorks, often via Niagara). That breadth is the value proposition, and it sets the architectural cadence. Those protocols were built for HVAC setpoints, lighting schedules, damper position, and occupancy state. Those phenomena move on the scale of seconds to minutes. Default seconds-cadence polling is more than sufficient for them.

Electrical waveform content sits in a different regime. Rectifier diode degradation, capacitor ESR drift, harmonic distortion shifts per IEEE 519, and sub-cycle transients all live in the millisecond range. A seconds-cadence sample is one snapshot per polling interval; the waveform content between those snapshots is not recoverable downstream. No amount of Forge analytics on the polled stream can reconstruct what EBI never acquired.

Forge plus EBI is not built to acquire that waveform information. Verdigris is. Critical-power circuits get their own purpose-built sensor layer; the building-wide platform keeps doing what it does well.

Niagara polls field-protocol points at building-automation cadence and renders the trend with interpolation between samples. The line looks smooth because the renderer connects the dots, not because the underlying signal was sampled continuously. Verdigris runs a parallel 8 kHz waveform on the same conductor, where the actual sub-cycle shifts live.

Honeywell Niagara uses BMS-cadence polling. Verdigris captures 8,000 samples in that window

Why does BMS-tier monitoring produce thousands of alerts per day?

Industry studies of BMS alarm volumes in large data centers report an average of 4,484 alerts per day, with 67% ignored. That figure is not specific to Forge or EBI; it is what happens when threshold-based alarming runs on noisy electrical points at building-automation polling cadence. Every polling-based alarm management system inherits this pattern, Forge included, because Forge alarms on the EBI event stream.

Verdigris filters alerts by physics validation. An anomaly only escalates when its own 8 kHz waveform corroborates the threshold crossing as real degradation. Transient artifacts get suppressed. Measurement-noise spikes get suppressed. Misconfigured thresholds get suppressed. The result is a cleaner, ranked stream that Forge can consume alongside its native EBI alarms.

For operators running Forge alarm management today, Verdigris physics-validated alerts arrive through standard outbound surfaces (MQTT topics, REST webhooks, BACnet emulation) and slot into existing Forge alarm workflows. The thousands-per-day electrical-alert population shrinks to the dozens that physics actually corroborates. Operator attention shifts to events that map to real reliability risk and real recoverable capacity.

A T-Mobile Senior Director described the shift this way:

Verdigris Signals gives us visibility into degradation patterns that don't exist in standard monitoring, enabling us to maintain our reliability leadership position while optimizing capital allocation.

How does Verdigris integrate with Honeywell Forge?

Verdigris EV2 sensors install on critical-power circuits across greyspace (utility edge, main PDUs, switchgear, UPS, transformers), whitespace (row and rack level), and the server power path. Those sensors are Verdigris's own layer, capturing continuous 8 kHz directly off the conductor. They are not derived from BMS polling. Forge keeps running its analytics on HVAC, lighting, life-safety, and BMS electrical metering. Verdigris becomes the system of record at the validated layer.

Forge data is welcome as supplementary context: HVAC and thermal correlation makes electrical anomaly detection sharper, and Forge's alarm streams ride alongside Verdigris's validated feed. The two run on a clean integration surface.

Surface	Mechanism	Honeywell Estate Use
MQTT broker	Verdigris-hosted real-time pub/sub	Stream physics-validated alerts and validated operating limits into Forge ingestion
REST API	Programmatic access to electrical state	Backfill Forge dashboards and reports with electrical intelligence
Modbus	Production-validated OT field protocol	Native handshake with Honeywell controllers that already speak Modbus
BACnet emulation	Verdigris sensors appear as native BACnet devices	Zero integration lift. EBI sees Verdigris on the wire with no point-database change

Sibling integrations with Schneider EcoStruxure, Eaton Brightlayer, Vertiv, ABB, and Siemens Building X use the same outbound delivery shape. Mixed-vendor estates consolidate into a single electrical intelligence record.

The intelligence Verdigris adds

The capabilities Verdigris contributes to a Honeywell-equipped data center are the ones polling-based building monitoring was not built to deliver.

Sub-second waveform layer

Verdigris EV2 sensors at 8,000 samples per second per circuit. Captures rectifier-diode signatures, capacitor-ESR drift, and harmonic shifts. These live in the waveform window between BMS polling samples.

Physics-validated alert filtering

Alarms only escalate when 8 kHz waveform data corroborates the threshold crossing. Industry-typical BMS alarm volumes (thousands/day, 67% ignored) shrink to what physics supports.

Validated operating limits

Continuous measurement of safe headroom on UPS, PDU, busway, and rectifier paths. Building-wide polling architectures do not produce this. It is the foundation for recovering stranded capacity.

Vendor-neutral electrical depth

Verdigris reads any electrical panel regardless of manufacturer. Honeywell sites and non-Honeywell sites consolidate into a single electrical intelligence record.

This is the validated layer between Honeywell monitoring and downstream controls. Physics-based limits that polling-based monitoring cannot produce on its own. The guardrails autonomous control systems need as input.

How it deploys in a Honeywell shop

A multi-site enterprise runs Forge on top of EBI across 12 data centers. Verdigris EV2 sensors install on critical-power circuits during a standard maintenance window: non-invasive, no shutdowns, operational in days. BACnet emulation mode lets EBI see Verdigris as a native device on the network. No EBI point database changes, no Niagara station rework, no Forge configuration changes. Forge keeps running its analytics on HVAC, lighting, life-safety, and BMS-tier electrical metering. Verdigris streams physics-validated electrical alerts back via MQTT and webhook, cutting electrical alarm volume sharply, and flags three UPS rectifiers degrading via harmonic shifts visible only at 8 kHz.

This matches the pattern in Verdigris's T-Mobile rectifier case study. Verdigris detected equipment degradation in 4% of more than 800 monitored rectifiers. None of those rectifiers had triggered a Forge alarm. The waveform signature lived between BMS polling samples.

A second pattern shows up in technology-sector deployments. At Orange Silicon Valley's San Francisco innovation lab, Verdigris monitoring found more than $40,000 in annual energy savings below standard metering resolution. Infrastructure engineer Scott Dworkis put it plainly:

You're likely to learn surprising patterns once you start digging into the data, and this was certainly the case for us.

The mechanism generalizes. Continuous sub-second waveform data, captured on Verdigris's own sensor layer and flowed back through standard outbound surfaces, exposes signatures that polling-only systems cannot resolve.

Forge keeps the alarm-management workflow operators already trust. Verdigris contributes the early warning polling could not surface. Operators see the building and the electrical infrastructure clearly, each phenomenon measured at the resolution that fits it. Reliability risk and stranded-capacity recovery surface before they become outages.

Related vendors

Verdigris + Schneider Electric

Augment EcoStruxure with 8 kHz validation across the full power path.

Verdigris + Eaton

Keep Brightlayer and PredictPulse. Add 8 kHz validation across every vendor.

Verdigris + Vertiv

The validated layer above Environet and Liebert; 21-day early warning on rectifier degradation.

Verdigris + ABB

Proven Ekip Smart Fit and ABB Ability integration; 8 kHz validation across the path.

Verdigris + Siemens

Add 8 kHz validation to Building X, Desigo CC, and Sivacon panels.

Verdigris vs Packet Power

Consumption monitoring vs waveform-grade ML. How the two approaches compare.

Verdigris vs SkySpark

Rules on 1 Hz BMS data vs ML on 8 kHz waveforms. How the architectures differ.

Niagara interpolates between BMS-cadence polls Verdigris captures the real 8 kHz waveform