- American Time
- Primex
- Sapling
- Valcom
- Bogen
We aren't tied to any brand. If your drawings call for something else, we'll install to the specification.
Where synchronized time changes how a building runs
Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. Synchronized time, bell and tone systems fall within that classification, and we install them for schools and community colleges, hospitals and clinics, senior housing, and public agency buildings across California.
In a building that runs on a schedule, the clocks are part of the infrastructure. A class period ends when the bell rings. If the bell in the gymnasium is 40 seconds behind the one in the main building, the passing period is off for half the campus. A shift change is timed by the clock on the wall and recorded at the time clock. Medication rounds are charted against a wall clock, and a court calendar runs on the clock in the corridor. In each case someone is being held to a time, so the times have to agree.
Records are the other reason. Access control events, camera video, phone system logs and badge readers all stamp time onto data that gets compared later. Say an incident review puts a camera clip next to a door event and the two are 90 seconds apart. The review then gets stuck on which one is right. When every system takes its time from the same source, that argument is much less likely to come up.
Our scope is the master clock or time server, the clocks, the bell and tone hardware, the schedules, the cabling or wireless infrastructure, programming, testing room by room, staff training, and the closeout documentation. American Time, Primex, Sapling, Valcom and Bogen are among the platforms commonly specified on California school, healthcare and agency projects, and we install to the spec.
Wired, wireless and PoE clock distribution
The right distribution method depends on the building.
| Consideration | Wired | Wireless | PoE and IP |
|---|---|---|---|
| Fits | New construction, accessible ceilings | Occupied retrofits, hard lid ceilings | Buildings with a managed network at the wall |
| Cabling | Correction circuit to every clock | None to the clock | Existing or new Cat6 or Cat6A drop |
| Power | From the circuit | Batteries in each clock | From the switch port |
| Time source | Master clock | Master clock and transmitter | NTP over the network |
| Ongoing work | None once cabled | Battery replacement cycle | Switch port and PoE budget |
| Status reporting | Limited | Varies by platform | Per clock, from the network |
| Watch out for | Pathway cost in existing buildings | Signal into concrete, steel, elevator lobbies | PoE budget, VLAN, switch uptime |
Wired systems are still the simple choice in new construction, where the pathway is going in anyway. Wireless has made occupied retrofits practical. A clock and its receiver go up in one visit per room with no wall opening, and that matters in an occupied hospital corridor or a school that’s in session. The tradeoff is a battery schedule and a coverage survey, because concrete stairwells, elevator lobbies and metal shop buildings absorb signal in ways a floor plan won’t show. We run that survey with the real hardware before we commit to coverage.
Specifiers are asking more and more for PoE and IP clocks on projects where a data drop already reaches the wall. Each clock is a network device with an address. It takes time over NTP and reports its own condition, so a facilities team can spot a clock that’s dropped off without walking the building. These clocks also use a switch port and PoE budget, and they stop when the switch does, so plan UPS coverage for them the same way you would for the rest of the network gear.
The master clock, the time server and NTP
Every synchronized system has one reference. The design question is where that reference gets its time.
A traditional master clock holds the time and drives the clocks over its own distribution. A network time server does the same job on the data network, serving NTP to IP clocks and often to the rest of the building’s systems too. Either way, the reference gets set from one of three sources: an NTP source on the organization’s network, an internet time source, or a GPS antenna mounted with a clear view of the sky. The GPS option is for sites that want a reference that doesn’t depend on the wide area network.
Two coordination points come up on most projects. The first is deciding which device is authoritative for the whole site. If the district or agency already runs an NTP source, the clock system follows it instead of becoming a second source of truth. The second is the network path. IP clocks need a VLAN, addressing, and firewall rules that let them reach the time source, and we write those down during design so they’re settled before commissioning.
Make a deliberate call on redundancy. A time server with a second reference and a battery backed real time clock keeps the site on time through a network outage. Without that, clocks hold their last known time and start to drift.
Dedicated circuits for the master clock or time server and for the amplifier racks are electrical scope. We put the load, the location and the circuit count on our submittal early enough for the electrician to carry them in the panel schedule instead of adding them later by change order.
Bell schedules, tones and special day calendars
The schedule is where the clock system has to match the way the organization runs day to day.
A school year has a regular bell schedule, a minimum day schedule, an assembly schedule, a testing schedule, and a rotating block on some campuses. A community college runs different period lengths by term. A hospital uses tones for shift change and codes rather than a bell. An agency building may want nothing more than a chime at opening and closing. The system stores each of these as a named schedule, with a calendar that says which one runs on which day and a holiday calendar that suppresses everything.
A few practical points from the field:
- Use different tones for different events. People should be able to tell a passing bell, a warning bell, an emergency drill tone and a shift tone apart, and staff should be able to name each one.
- Zone the bells. Athletic fields, shops and portables often need a different level or a different tone than a classroom wing.
- Give one person the calendar. Someone in the front office loads the year, and we set up their access before turnover instead of after the first schedule change.
- Load the whole year at commissioning. Building the schedule with the person who owns it doubles as their training session.
- Confirm the manual override. Staff need a way to ring, silence or hold a bell without making a support call.
Bells and announcements from the same zones
A bell and an announcement should come out of the same speakers, in the same zones, at levels that were set together. That’s as much a paging design question as a clock one, and our audio visual and paging page goes into it in more depth.
If a school or campus already has an intercom and paging system, the clock and bell system either drives those zones through an interface or shares the amplifiers directly. When both are in the same package, we lay out speaker zones once and map the bell schedule onto them. On K-12 and higher education projects, the classroom call-in function usually lives on the same system. That means the intercom, the bell and the clock in a classroom are one submittal and one test.
Batteries, drift and what fails over time
Clock systems fail quietly. Nothing sets off an alarm, and one clock in a back corridor can stay wrong for a whole year.
Quartz movements drift, and that’s why synchronization exists in the first place. A wireless clock that misses its correction signal keeps running on its own movement and drifts away from the rest of the building at its own rate. Batteries in wireless clocks wear out on a cycle the maintenance program has to track, and they don’t all die in the same month. A PoE clock on a switch that gets rebooted comes back and re-syncs, unless the VLAN changed underneath it.
Two things cut down the maintenance load. First, specify clocks that report status to the master, so the facilities team can read a list instead of walking corridors. Second, write the battery cycle and the schedule review into a service and maintenance agreement. That way the year gets loaded and any drifted clocks get found before the term starts.
DSA, HCAI review and the documentation you receive
K-12 and community college projects are subject to Division of the State Architect review. Hospital and skilled nursing projects are subject to HCAI review. We coordinate deferred submittals to match. Product data, mounting and anchorage details and cut sheets go in on the schedule the design team sets, in the form the reviewer expects. On healthcare work, the anchorage detail is usually what draws a comment, so we submit it early.
At closeout, you get a clock schedule by room with the type and address of each device, a wireless coverage map with transmitter and repeater locations where wireless is used, the master clock or time server configuration and time source, every named bell schedule and the calendar that drives it, the user accounts and rights for whoever manages schedules, a battery replacement schedule, a room by room test log, and the manufacturer’s operation and maintenance manuals. The test log shows that each clock followed a correction and each zone sounded on a scheduled bell, with the technician’s initials next to it.
Next step
Send us the floor plans, the room list, the bell schedules you run, whether the building stays occupied during the work, and any existing paging or intercom system we should tie into. Upload drawings through request a bid, and we’ll send back a clock and zone count that shows where our work connects with the electrical, network and plan review pieces. General contractors can start at for general contractors for our prequalification packet and Division 27 scope letter.