During a routine security audit at a private engineering university with seven academic blocks and three hostel wings, the campus IT team discovered that a student disciplinary case from the previous semester could not be closed. The access control log at the hostel entry showed a timestamp of 22:43:07. The corridor NVR camera recorded the same doorway event at 22:45:51. The warden's paper register rounded the time to 22:45. Three different records, three different versions of the same two minutes, and a disciplinary committee that spent three meetings debating which device was correct rather than what had happened.
The campus had never had a central time reference. Every IP camera was set manually during installation, every access control panel kept its own internal clock, and the IT network was pulling NTP from pool.ntp.org over a firewall exception that the security policy team did not know existed. We replaced the free-running configuration with a single PreciseSync-SMC-300 server mounted in the main campus server room. NTP was pushed to the core switch and propagated to every VLAN serving CCTV, access control, attendance and administrative systems. Within forty minutes of commissioning, every device on the network was reporting the same UTC-traceable time.
The first incident review conducted after the deployment produced a clean, matching timeline across the access log, the CCTV recording and the warden's digital register. The investigation closed in a single two-hour session. That is what disciplined campus timekeeping looks like in practice: records that agree with each other, and investigations that close on facts instead of clock discrepancies.