Posts

Stop Turning Every BMS Alarm Into a Work Order

Image
The strongest objection to BMS-to-CMMS automation is that it can worsen maintenance. If every alarm creates a ticket, nuisance events become work, faults produce duplicate tasks, and technicians close symptoms instead of repairing causes. The integration may be technically successful while the operating model fails. Data moves faster, yet the maintenance backlog becomes less trustworthy across the portfolio and between maintenance teams. Alarms and work orders serve different purposes. An alarm asks for attention. A work order commits labor, parts, and accountability. A governed admission layer must decide when an operating signal deserves that commitment. A work order is a resource decision A BMS may generate events for safety limits, communication loss, comfort deviation, equipment state, sensor quality, or energy performance. These conditions do not require the same response. Low flow during startup may need no action. A failed pump can generate downstream alarms belonging to one in...

Predictive Maintenance Fails When Prediction Becomes the Product

Image
  The strongest case against predictive maintenance is that earlier warnings can create more cost. Every investigation consumes engineering time. Premature intervention can replace usable parts, interrupt stable equipment, and fill maintenance queues with uncertain work. Prediction is only one input to an asset decision. The outcome depends on an intervention policy combining technical evidence with consequence, confidence, redundancy, service windows, and the cost of error. For enterprise leaders, the goal should not be maximum anomaly detection. It should be fewer unplanned failures without creating uncontrolled maintenance demand. A forecast is not a maintenance decision A BMS alarm reports a condition. Fault detection tests abnormal behavior. A predictive model estimates future degradation. None of these outputs decides whether a technician should act today. Consider a pump drawing more current while producing the same flow. The pattern may indicate bearing resistance, an impel...

The BMS Does Not Need More Alerts. It Needs Better Decisions

Image
  Building management systems are good at reporting abnormal conditions. That does not mean they are good at explaining what happened or helping a technician decide what to do next. This is an executive issue. As portfolios add sensors, analytics, and AI, machine-generated findings can outgrow facility teams. Dashboards surface events while leaving diagnosis, priority, ownership, and verification unresolved, and forcing operators to reconstruct causes manually under time pressure across an entire portfolio. The better objective is decision quality. Enterprises should design a governed path from signal to diagnosis to action, using deterministic alarms for known conditions, fault detection and diagnostics for causal reasoning, and AI for context-rich assistance. Alarm volume is a weak performance metric A falling alarm count may indicate better engineering. It may also mean thresholds were widened, notifications were suppressed, or faults went unseen. Conversely, a high count may co...

Enterprise AI Needs Two Contracts Before It Can Scale

Image
  The strongest counterargument to enterprise AI standardization is that uniformity can destroy context. Buildings, workflows, and domain procedures differ. Forcing every source into one rigid structure may make the architecture clean but the system less truthful. The answer is not unrestricted flexibility. It is to standardize the interfaces that applications depend on while preserving valid differences behind them. This creates two contracts. The first defines what operational data means across assets and locations. The second defines how an agent interprets instructions, calls tools, and returns results. Governing only one may produce consistent data without reliable action, or controlled execution without dependable context. AI performance depends on the interfaces around the model Executives often evaluate AI through model accuracy, infrastructure cost, and application features. Yet failures frequently begin before or after inference. Before inference, the model may receive in...

Stop Choosing Building Metadata Standards Before Defining the Business Decision

Image
  The strongest argument against investing in building semantics is simple: a better data model cannot repair a drifting sensor, a broken control sequence, or missing trend history. That limitation defines its proper role. A semantic layer is not a cure for poor building data. It is a contract between operational systems and the applications consuming their data. For CEOs, CIOs, CTOs, and facilities leaders, the real decision is therefore not whether Brick Schema or Project Haystack is superior. It is what decisions the portfolio must support, what context each application requires, and how that context will remain accurate as buildings change. Schema selection is an operating-model decision Teams often compare tags, ontologies, query languages, and vendor support before defining ownership and maintenance. Who owns the model after commissioning? Who approves equipment changes? Can applications confirm that required points exist? Can another vendor reuse the mapped data? These quest...

The Business Case for AI in Buildings Starts With Control, Not Algorithms

Image
  Many buildings should not adopt AI yet. Faulty sensors, weak control sequences, inaccessible trend data, and neglected maintenance will undermine even a strong model. Adding intelligence can automate poor decisions and obscure their cause. The answer is to treat AI as a governed supervisory capability. The existing building management system, or BMS, should continue to run deterministic controls and safety functions. AI should operate above it, interpreting data and recommending bounded actions. This changes the investment case. The board is deciding where better decisions can produce measurable value, what authority software should receive, and what evidence is required before that authority expands. That is a governance and operating model decision before it becomes a software decision. Start with operational value, then choose the technology Energy savings attract attention, but value can also come from fewer comfort complaints, earlier fault detection, lower demand charges, a...

Why Enterprise AI Memory Fails Without Continuous Evaluation

Image
  Most enterprise AI initiatives struggle to transition from pilot demonstrations to mission-critical production. When autonomous systems fail in enterprise deployments, executive post-mortems typically blame stochastic hallucinations in the foundational language model. In reality, the primary failure mode stems from unmonitored degradation within enterprise AI memory architectures. The prevailing counterargument among technical leaders suggests that rapid advances in context window capacity eliminate the need for complex memory systems and specialized evaluation pipelines. If a frontier model can accept two million tokens in a single request, engineering layered episodic, semantic, and working memory caches appears to introduce unnecessary architectural friction. Empirical performance data refutes this assumption. As demonstrated in retrieval benchmarks such as Liu et al.'s "Lost in the Middle," transformer recall accuracy degrades as context density increases, especiall...