Show Notes
The Building’s Invisible Clock
Modern buildings do not operate from a single shared sense of time by default. Cameras, access control readers, building automation systems, occupancy and air-quality sensors, energy dashboards, and tenant Wi-Fi environments all record events with timestamps. Those timestamps are what allow teams to connect activity across systems and understand what happened, when it happened, and what should happen next.
In this episode of Built, Wired & Secured, the discussion focuses on time synchronization as a hidden infrastructure dependency. A building can appear to be operating normally while its systems quietly disagree about the time. The real consequences often emerge only after an incident, an operational dispute, a failed schedule, or a troubleshooting effort that cannot produce a trustworthy sequence of events.
When Systems Tell Different Versions of the Truth
The episode opens with a simple but serious scenario: access control, camera footage, and the building automation system each show a different time. That creates more than an administrative inconvenience. It means the building has multiple, conflicting versions of the truth.
On an ordinary day, a few minutes or seconds of drift may not draw attention. But when a team needs to reconstruct an incident, those differences can become a major obstacle. A camera may appear to show an event before a door reader recorded access, while the HVAC or building automation system may place related activity somewhere else in the timeline.
- Security investigations become difficult to reconstruct.
- Access events and video evidence may not line up.
- Building automation activity may be difficult to compare with other events.
- Technical teams lose confidence in the sequence of recorded information.
- Disputes can become harder to resolve because the evidence does not share a common timeline.
The core point is direct: timestamps are the thread tying building systems together. When that thread breaks, the records may still exist, but the building team can no longer reliably connect them.
Time Sync Is Not Only a Security Issue
Time synchronization matters in security, but the episode makes clear that the risk extends into operations and energy management. Building systems use time to organize schedules, trends, and automated decisions. If clocks drift, schedules can fire at the wrong time and analysis can be based on data that does not accurately align.
For example, teams may review sensor data to decide when HVAC should ramp up or down. If timestamps are inconsistent, the information used to make those decisions can be misleading. A team may believe a condition happened before or after another event when the data does not support that conclusion.
This is especially important because drift can compound. Some systems depend on a master clock. If that clock is wrong, the systems downstream from it can be wrong as well. Instead of one isolated device with an incorrect time, an entire group of connected systems can inherit the same flawed reference.
The Ownership Gap Between IT, Facilities, and Vendors
The episode identifies the biggest practical issue: ownership. Time synchronization commonly falls between IT, facilities, and system vendors. Access control may be considered a facilities responsibility. Facilities may believe the network team owns the issue. Vendors may set the time during installation and assume someone else will handle ongoing verification.
That does not necessarily mean people are ignoring the problem. The challenge is that no one has been explicitly assigned to keep the building’s clocks accurate. Responsibility falls between teams, and because nothing appears urgent until there is an incident, the gap can remain unnoticed for a long time.
- IT may manage network-connected infrastructure.
- Facilities may manage physical systems and day-to-day building operations.
- Vendors may install and maintain individual platforms.
- Without a designated owner, no one verifies that all platforms agree.
The recommended answer is not a committee. The building needs a designated owner with the authority to bring IT and facilities together, establish accountability, and answer one clear question: who keeps the clocks honest?
A Practical Time Health Check
The episode avoids overcomplicating the first step. If a building team does not know who owns time synchronization, that is the first problem to solve. Bring IT and facilities together and formally assign ownership.
Then perform a basic comparison across three representative systems: a camera, an access control reader, and the building automation system. Compare their timestamps. The episode identifies more than one second of difference as drift that should be addressed.
- Choose a camera and review its displayed timestamp.
- Check an access control reader or access-control record.
- Check the building automation system timestamp.
- Compare the three systems for alignment.
- Treat a difference greater than one second as drift.
- Repeat the check over time because drift can return.
This does not require an elaborate platform to begin. The team can document what it finds on paper: the systems checked, the observed time, the responsible owner, and the acceptable tolerance. That record becomes a baseline for future checks and makes the responsibility visible.
Make Time Verification Part of the Operating Routine
A corrected clock is not a permanent solution if no one checks it again. The episode emphasizes that time synchronization must become part of normal building operations rather than a one-time remediation project.
- Include time verification when commissioning new systems.
- Add time checks to vendor maintenance reviews.
- Document the agreed tolerance and responsible owner.
- Ask vendors when synchronization was last verified.
- Treat an inability to answer that question as a red flag.
For property owners, facilities leaders, and technology teams, the business outcome is clearer evidence, better troubleshooting, more dependable schedules, and more trustworthy operational data. A short time health check can protect the building’s ability to investigate the next incident before that incident occurs.
Listener Challenge
Run a time health check. Bring IT and facilities together, assign one accountable owner, compare clocks across key systems, document the result, and make verification routine. It is a small operational action that can prevent a major investigation and reliability problem later.
Time Synchronization Is Building Infrastructure, Not a Minor Setting
In a modern commercial building, time is not limited to wall clocks and meeting schedules. It is embedded in the systems that record, control, and explain what happens throughout the property. Cameras timestamp footage. Access control readers timestamp entry events. Building automation systems timestamp HVAC activity. Sensors tracking occupancy and air quality timestamp their readings. Energy analytics depend on data that is organized in time.
Those timestamps create the timeline that building teams rely on for operations, security, troubleshooting, and decision-making. When the clocks behind those systems disagree, the impact may be invisible at first. The systems can still appear to work. Doors may unlock, cameras may record, HVAC may run, and dashboards may display data. But when someone needs to understand an event across systems, the building may no longer have one reliable version of the truth.
That is why time synchronization deserves to be treated as real building infrastructure. It is a quiet dependency that supports the ability to investigate incidents, validate schedules, interpret trends, and coordinate the work of IT, facilities, and vendors.
Different Clocks Create Different Stories
Consider a situation in which an access control record, camera footage, and the building automation system each show a different time. Each system may contain useful information, but the information becomes difficult to connect. Did a person enter before or after the video event? Did a building condition change before or after the access event? Did an automated schedule operate as expected, or does the timestamp only make it look that way?
When clocks disagree, teams do not simply have a formatting problem. They have an evidence problem. The records cannot be confidently arranged into a single sequence.
This matters most during an incident investigation. A building team may need to reconstruct what occurred, compare a door-reader record with camera footage, and identify related activity in building automation data. If each platform reports a different time, the team has to guess which system is accurate and how much to adjust the others. That uncertainty can make a difficult investigation substantially harder.
- Camera footage may not align with door access records.
- Access activity may be difficult to compare with building automation events.
- Teams may disagree about the order in which events occurred.
- Incident reconstruction can become incomplete or unreliable.
- Troubleshooting can turn into guesswork instead of a disciplined review of evidence.
The problem is not limited to physical security. Any building process that depends on event history or coordinated automation can be affected by conflicting timestamps.
Bad Time Produces Bad Operational Data
Time drift also affects routine operations. Building teams use sensor data and trend information to make decisions about how systems should operate. That can include decisions about when to ramp HVAC up or down. When timestamps are drifting, the data may not accurately show how conditions, occupancy, and system activity relate to one another.
A team can have plenty of information and still make the wrong decision if the information does not share a consistent time reference. Data is only as useful as the ability to place it in context. If one system says an event happened before another system says a related condition occurred, the building team may draw conclusions from a sequence that never actually happened.
Automated schedules are another concern. When time is incorrect, schedules can fire at the wrong time. That may affect building operations in ways that appear isolated at first, but the underlying issue is shared time. Without a disciplined approach to synchronization, teams may chase individual symptoms instead of recognizing that the building’s sense of time is inaccurate.
There is also a compounding risk. Some systems synchronize to a master clock. If that master clock is wrong, systems downstream can become wrong as well. What begins as one incorrect source can become a wider problem across connected infrastructure.
The Ownership Problem Is Usually the Real Problem
In many properties, time synchronization falls into an ownership gap. IT may manage the network and connected technology. Facilities may manage building operations, access control, and automation platforms. Vendors may install individual systems, set the time during deployment, and leave ongoing verification to someone else.
Each party may have a reasonable view of its own role. The failure occurs when nobody is explicitly responsible for the common function that connects all those systems: keeping their clocks aligned.
This gap does not have to result from neglect. It often happens because the issue does not create an obvious emergency on a normal day. If doors work, cameras record, and HVAC operates, nobody may be prompted to compare timestamps across platforms. The absence of a visible failure can hide the absence of ownership.
The practical answer is accountability. A building should have one designated owner who can answer the question, “Who keeps our clocks honest?” That owner needs enough authority to bring IT and facilities together, coordinate with vendors, document expectations, and ensure that time verification continues after a system is installed.
A committee can discuss the issue, but a designated owner closes the gap. The difference matters because a shared dependency needs a clear person responsible for maintaining it.
Start With a Simple Time Health Check
The good news is that the first check does not need to be complicated. Start by comparing timestamps across three systems: a camera, an access control reader, and the building automation system. These systems represent core security and operations functions and provide a practical snapshot of the building’s time health.
Compare the timestamps directly. If they differ by more than one second, the episode identifies that as drift. That does not mean a team should only check once and declare the problem solved. Drift can return, so time health needs to be reviewed on an ongoing basis.
- Identify the accountable owner for synchronization.
- Bring IT and facilities together to confirm responsibility.
- Check a camera timestamp.
- Check an access control timestamp.
- Check the building automation system timestamp.
- Compare the results against an acceptable tolerance.
- Address differences greater than one second.
- Repeat the check because synchronization can drift over time.
The value of this exercise is not only technical. It forces the organization to establish a shared baseline. Teams move from assumptions about who owns the issue to documented knowledge about what was checked, what was found, and who is responsible for keeping the environment aligned.
Documentation Turns a Fix Into an Operating Practice
Documentation does not need to be elaborate to be useful. A basic record can include the systems reviewed, the observed timestamps, the owner responsible for time synchronization, and the acceptable tolerance. Even a simple written document creates a baseline that can be referenced during future reviews.
That baseline is important because it makes time health measurable. Without it, teams may know that they “fixed the clocks” at some point, but they cannot easily show what was verified or whether the condition has changed. With it, teams can identify drift, assign follow-up work, and keep the responsibility from disappearing between departments.
Time verification should also become part of commissioning. New systems should not merely be installed and left with whatever time configuration is present at deployment. Their synchronization should be included in the handoff process. The same principle applies to ongoing vendor maintenance reviews.
A useful question for any vendor is simple: when was synchronization last verified? If a vendor cannot answer, that should be treated as a warning sign. The question is not meant to create blame. It is meant to establish whether a critical operational dependency is being actively maintained.
Why This Matters to Owners and Operators
For owners, property operations leaders, facilities teams, and technology teams, time synchronization is ultimately about business resilience. Reliable timestamps support a building’s ability to investigate incidents, evaluate operational decisions, understand system behavior, and avoid unnecessary uncertainty.
The investment to begin is small. The episode’s challenge is to run a time health check, assign ownership, and compare clocks. That work can take about an hour, but it may preserve the ability to reconstruct the next significant event in the building.
Reliable building technology is not only about whether each individual system is functioning. It is also about whether systems can work together to tell a coherent story. Time synchronization is one of the quiet foundations of that story.
Listen to Built, Wired & Secured for the full discussion on why building clocks need clear ownership, routine verification, and a place in the operating discipline of every modern property.