How Buildings Remember: The Importance of Connected Knowledge
How Buildings Remember: The Importance of Connected Knowledge
Modern buildings generate an extraordinary amount of information throughout their lifecycle. Architects produce drawings, engineers develop sequences of operation, contractors submit equipment data, commissioning teams document testing, building automation systems record trends and alarms, and preventive maintenance programs generate thousands of work orders. Yet despite this abundance of information, many buildings suffer from the same problem: they forget. Not because the information disappears, but because it becomes fragmented across disconnected software platforms, document repositories, filing systems, and personal experience.
Information and knowledge are not the same thing. Information records events; knowledge provides context. A completed preventive maintenance work order may document that bearings were replaced on a chilled water pump, but by itself it says very little. When that same work order is connected to the pump’s startup documentation, vibration history, operating trends, commissioning records, engineering notes, photographs, and previous repairs, it becomes part of a much larger story. It explains not only what happened, but why it happened, whether it has happened before, what was learned, and what future engineers should watch for.
This principle extends well beyond preventive maintenance. Every engineering decision, sequence modification, operator observation, deficiency correction, and troubleshooting effort contributes another piece of operational knowledge. Individually, these records have limited value. Connected together around the equipment they describe, they become an accumulated history of how the building actually behaves rather than simply how it was designed to behave.
Unfortunately, organizations often lose this accumulated knowledge. Engineers retire, contractors move on, vendors change, software platforms are replaced, and personal notebooks disappear. Years later, someone asks why a control sequence was modified, why a valve is normally left partially open, or why an operating setpoint differs from the original design documents. The answers often existed at one time but were never preserved in a way that remained connected to the equipment and to the other information that gave those decisions meaning.
The objective, therefore, is not simply to store more information. It is to preserve the relationships among the information we already create. Instead, the goal is to establish meaningful relationships among existing sources of information. A preventive maintenance record should connect to the asset on which the work was performed. That asset should connect to its drawings, O&M manuals, commissioning reports, operating sequences, BAS trends, maintenance history, photographs, engineering notes, and lessons learned. Each connection contributes context, and context transforms isolated information into usable operational knowledge.
As these relationships mature, they become one of the building’s most valuable assets. New engineers inherit not only equipment, but also the experience accumulated by those who operated it before them. Troubleshooting becomes faster because historical decisions remain visible. Maintenance becomes more effective because recurring issues can be recognized instead of rediscovered. Most importantly, knowledge survives organizational change rather than leaving with the people who created it.
Every building accumulates knowledge throughout its life. Unfortunately, knowledge has a habit of walking out the door at retirement, changing employers with a contractor, or disappearing during the next software migration. The question is not whether a building creates knowledge, but whether that knowledge will still be available to the next engineer who needs it.