For Engineering & Operations
Your command center for every building.
Noda analyzes every asset continuously, then hands engineers scoped work with savings attached.
From fault to accepted Project
Noda finds faults, traces them back to their causes, and estimates what fixing each one would save before the work reaches engineers.
Every asset analyzed, continuously.
Fault detection runs on chillers, air handlers and terminal units around the clock, so coverage no longer hinges on staff on-site.
- Chiller Delta T LowCH-2
- Chilled water valve open, no coolingAHU-2
- Zone Temp above setpointVAV-12
Projects arrive ready to accept.
Each Project carries its root cause, the change to make and its estimated annual savings.
Tasks reach technicians as work orders.
Noda's AI agents write each Project's Tasks, naming the equipment and the change to make. Sync a Task to your CMMS, and the work order carries those instructions to the technician.
Noda catches degradation while it is still a maintenance item.
Customers report 5 to 15 percent lower reactive repair and replacement costs.
CH-1 is drawing more power than predicted at its current load, and the gap has widened over six weeks.
Condenser approach temperature has risen alongside it, which points to fouled condenser tubes.
Skip the investigation. Start on the fix.
A bad day in a commercial building can produce a flood of alarms and faults. Noda gets to the true root cause and synthesizes the stream into scoped, actionable Projects.
CH-2's Delta T collapses, AHU-2 can't hold its discharge air setpoint, and the zones it serves run warm. 20 Insights fire, and none of them points to the cause.
Works with the systems you already use.
Noda connects to leading building management systems and to anything supporting BACnet/IP, Modbus, or MQTT, through the Noda LaunchPad, a secure on‑premises gateway.
Results with real impact
$166,000 in annual savings by rerouting tenant loads off a 24/7 chiller plant.
What Noda DiagnosedA landmark DC office tower ran two chillers 24/7 to serve tenant supplemental loads, even though overnight activity was minimal. Migrating those tenant systems to the retail condenser loop let the main chiller shut down 9 PM–6 AM, cutting ~20,000 kWh weekly year-round.
Related reading
Frequently asked questions
Does this replace my engineers?
No. Noda performs the continuous analysis that is impractical to do manually and produces scoped work for engineers to review and execute. Engineering time shifts from diagnosis to review and execution.
What does it need from my BMS?
Noda needs read access to the data your BMS already trends, connected through the Noda LaunchPad, a gateway installed on site. Enabling Automated Demand Management or setpoint changes from Noda also requires write access, limited to the specific BMS points enabled during setup. Deployment requires no BMS reprogramming and no custom integration work.
How much of my team's time does this take?
Your team reviews and accepts the Projects Noda proposes. Noda runs the diagnostic work behind each Project: fault triage, root cause analysis and the savings estimate.
We have fault detection already. How is this different?
Noda turns the faults your FDD system detects into a short list of Projects with the savings estimated. Fault detection rules frequently produce more faults than any team can triage: a Lawrence Berkeley National Laboratory study of 317 buildings found an average of 245 faults per building per month. Noda groups related faults by common cause through root cause analysis and turns each cause into one Project. After the work is done, Noda monitors the equipment to confirm the fix held and measures the savings against a baseline.
How are savings measured?
Noda measures each completed Project against a counterfactual baseline normalized for weather and occupancy, and reports the measured result as the Project's savings.
Is our data clean enough for this?
Operational data in commercial buildings is notoriously messy, and Noda normalizes it as part of every deployment. Noda's Independent Data Layer reconciles the points each BMS exposes into one normalized schema, then models the equipment, spaces and relationships behind those points in each building: which air handler serves which zones, which pump serves which loop.