- AtlasIED
- Advanced Network Devices
- Algo
- Valcom
- Singlewire
We aren't tied to any brand. If your drawings call for something else, we'll install to the specification.
What a network based mass notification system is
Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. We design and install network based mass notification under that classification for offices and tenant improvements, public agency buildings, schools and community colleges, clinics, warehouses and campuses across California.
A network based mass notification system sends one alert to every endpoint on the data network at the same time. The endpoints are IP speakers on PoE switch ports, IP beacons and strobes, LED message displays in corridors and lobbies, full screen messages pushed to computers, and text and push notifications sent to a phone list. The head end is a server or a hosted service that holds the zones, the message templates and the user permissions.
It reaches people who aren’t looking at a screen or carrying a radio, in the same areas a page would already reach, and it puts the same words in text for anyone who can’t hear the announcement. The next section covers where our package starts and stops.
| Endpoint | What it delivers | Where it fits |
|---|---|---|
| IP speaker | Live voice, recorded message, tone | Corridors, classrooms, offices, lobbies |
| IP horn or array | Higher output voice and tone outdoors | Parking areas, yards, athletic fields |
| Beacon or strobe | Visual alert with no audio content | Shops, plant floors, quiet areas |
| LED message display | Scrolling or fixed text | Lobbies, corridors, gymnasiums |
| Desktop alerting | Full screen message on computers | Offices, labs, agency floors |
| Mobile alerting | Text, push and email to a list | Staff off site, night shift, drivers |
AtlasIED, Advanced Network Devices, Algo, Valcom and Singlewire are among the platforms commonly specified for this scope on California commercial and institutional projects, and we install to the spec. If there’s no specification, we’ll write one with the owner based on the zones, the endpoint mix and the systems already in the building.
Where our package starts and stops on a California project
This needs to be settled before anyone budgets the scope.
Our package is the network based system: IP speakers, beacons and message displays on the data network, the head end, the Cat6A drops, the zones, the templates and the commissioning. When the endpoints are separate devices on the network, all of it is ours on a Division 27 submittal.
Some specifications call for the notification system to share speakers with, override, or be combined with another building emergency system. That portion isn’t ours. It’s carried by the licensed contractor the fire code official requires, on its own submittal, and we’ll say so at bid time instead of at rough in.
Bring the fire code official into that conversation early. During design, get two answers in writing: the permit and plan review path, and which licensed contractor the jurisdiction expects to carry each part of the system.
How an alert gets initiated
An alert can only go out as fast as someone can start it. Four paths cover most projects, and most sites use more than one.
From a phone. A dial code on a desk phone or a softphone opens a live announcement to a zone or to everyone. Staff can use this path with little or no training. It depends on the phone system and the notification head end sharing a connection that’s been tested from the handsets people sit at.
From a panic input. A duress button under a counter, a lockdown switch in a front office, or a dry contact from another system fires a recorded message to a defined zone. Contact closures still work when nobody has a console open and nobody is able to talk.
From a console. A desktop or mobile application shows the zones and the templates. The operator picks a template, picks the zones, confirms, and the alert goes out. Rights are set per user. The confirmation step is there so a mis-click doesn’t put a lockdown message on a campus.
From another system. An interface or an API call from access control, a weather service, a dispatch feed or a building system sends a message with no person involved. Large sites get a lot of value from this path. It’s also where testing has to be most careful, because an automated trigger can fire at three in the morning with nobody standing next to it.
Every path logs the initiator, the time, the zones and the template, and that log is the record the owner produces afterward.
Zoning, paging and school bell integration
Zoning is the design decision that outlives the equipment. If it’s wrong, the operator can end up sending everything everywhere because the zone list is too hard to use under pressure.
We build zones three ways. Geographic zones follow building, floor, wing and outdoor area. Functional zones follow who needs the message: front office, shop floor, dining, athletics. Escalation groups combine them, so an all call, a building call and a floor call are each a single selection. Outdoor areas get their own zones, because an outdoor message carries past the property line and the endpoints are different hardware.
How the system fits with everyday systems matters as much as the emergency case. Overhead paging uses the same speakers for routine work, like a page to the dock, a shift tone or a background announcement. At a school or community college, the bell and intercom system carries the schedule, classroom call-in and all call, and mass notification is the emergency layer on top of it. When they’re bought together, the endpoints, zones and amplifier capacity are designed once. When they’re bought separately, the building can end up with two speaker systems in the same ceiling and two zone maps that don’t agree. On K-12 and higher education projects, we ask for the bell schedule and the paging zone list before we lay out a single speaker.
Intelligibility, ambient noise and speaker placement
The real design challenge on this scope is whether people can understand the words where they’re standing, and coverage alone doesn’t answer that.
Two things work against you. Ambient noise sets the level the message has to rise above, so it’s measured on site with the equipment running instead of estimated from a floor plan. Reverberation blurs speech in the very spaces that need it most: gymnasiums, atria, stairwells, parking structures and warehouses with hard surfaces and long sight lines. In a reverberant space, turning up the volume makes the message louder and harder to understand at the same time.
The fix is more speakers at lower levels, rather than fewer speakers turned up. They’re placed so no listener is far from one, and so sound from two distant speakers doesn’t reach the same ear out of step. Outdoors, where the throw is long, horn arrays are aimed and delayed, and messages are kept short and paced slowly because echo eats the ends of words. Recorded messages hold up better than live announcements under stress, since the pacing is already right.
Text covers what audio can’t. Message displays and desktop alerts reach people who are hard of hearing, people wearing hearing protection, and people behind a closed door, so we build every template in both forms.
Network, PoE and head end requirements
Once the endpoints are on the network, the network becomes part of the notification system. That changes what your IT group has to provide.
Count the PoE budget per switch, not per port. A closet full of speakers and beacons can exceed a switch power supply that looked adequate on paper, and you may find the shortfall the first time everything sounds at once. Put the endpoints on their own VLAN with the multicast configuration the platform needs, and get the firewall rules for a hosted console written before commissioning week. Address the endpoints from a reserved range and label them to the same scheme as the rest of the structured cabling.
Power is one of the items that gets missed most often. A system running on PoE stops when the switch stops. If the site expects notification during an outage, the switches, the uplinks and the head end all belong on the UPS and generator path. That requirement has to reach the electrical scope during design, so we show it on the submittal and put the load on the panel schedule request.
Each endpoint gets a Cat6A run, terminated and certified like a data drop, with exterior pathway sized and sealed for the environment. Endpoints don’t go on Wi-Fi.
Templates, drills and the records you keep
Messages get written before the emergency, reviewed by the people who’ll send them, and stored as templates with the zones already attached.
A workable template set is small: lockdown, lockdown lift, an evacuation message reviewed with the fire code official, shelter in place, severe weather, all clear, and a test message. Each one tells people what to do instead of naming the hazard, because in the first five seconds the action is what they need.
Drills are how you show the system works. The system logs the initiator, the time, the zones, and which endpoints reported back, and that report is what the owner files. At handover, we set the drill schedule and walk the operator through running one. We also leave a zone map, an endpoint schedule by room, the head end configuration, the user accounts and rights, and a commissioning test log. Endpoint counts and firmware change over time, so periodic testing belongs under a service and maintenance agreement.
Next step
Send us the floor plans, the zone list you want, and the phone and paging systems already in the building. Upload drawings through request a bid, and we’ll send back a zoned endpoint count that shows where our work meets the electrical and network scopes. General contractors can start at for general contractors for our prequalification packet and Division 27 scope letter.