MULTILARM // SOLUTIONS

Factory Break Bell & Shift Siren Systems: A Practical Guide

Shift changes, break buzzers, multi-zone paging and drills · 10 min read

Last updated 2026-09-23

A factory break bell marks shift starts, breaks and shift changes across a noisy building. A shift siren does the same job louder. Both are trivial until the shift pattern rotates, the building has zones, or someone needs to make an announcement over the top — which is where most installed systems quietly stop helping.

What does a shop-floor bell system have to survive?

A factory bell system has to be audible over machinery, survive dust, heat and vibration, keep running when the site loses network, follow shift patterns that rotate rather than repeat weekly, and reach different parts of a building selectively. Factories break bell systems in ways schools do not:

• Shifts rotate. A three-shift or continental pattern is not a weekly timetable; it repeats on a cycle that does not line up with the calendar week.
• Noise is the enemy. A tone that carries over a press shop is not the tone you want in the offices twenty metres away.
• Zones are not optional. Goods-in does not need the assembly-line break buzzer.
• Announcements matter more than bells. "Line 2 is down", "the forklift in bay 4 is blocking the aisle", "drill, this is a drill".
• Somebody will need it at 05:40 on a Sunday, from a phone, without driving in.
• Drills must be provable. If a system rings an evacuation tone, somebody will eventually ask for the log.

What are the options for a factory bell system?

There are three routes: a mechanical timer or bell panel, an industrial IP paging system, or scheduling software driving the amplifier already on site. They differ mostly in what happens when the shift pattern changes and in how much of the cost is cabling. The table compares them.

If your site is being rewired anyway, or you need per-speaker addressability and intercom across a large campus, industrial IP paging is the right product and this guide will not talk you out of it. If the amplifiers and horn speakers are fine and the problem is the schedule and the announcements, the software route is far cheaper and far more flexible.

How do you schedule a factory's shift patterns?

Most rotas repeat on a calendar rule — a weekday, a date, a week number — and those can be expressed directly as schedule entries. Patterns that do not repeat on any calendar rule should be driven from outside instead, through the trigger API, rather than encoded as a fiction. A day-shift factory is the easy case, the same times every weekday:

<DateAndTimeData>*mon|06:00|10:00|10:15|12:30|13:00|14:00*tue|06:00|10:00|10:15|12:30|13:00|14:00*wed|06:00|10:00|10:15|12:30|13:00|14:00*thu|06:00|10:00|10:15|12:30|13:00|14:00*fri|06:00|10:00|10:15|12:30|13:00|14:00</DateAndTimeData>
<AlarmPath>D:\Tones\ShiftStart|D:\Tones\BreakStart|D:\Tones\BreakEnd|D:\Tones\ShiftEnd</AlarmPath>
<AlarmIndexData>1|2|3|2|3|4</AlarmIndexData>

Start of shift gets the long tone, break start and break end get distinct short tones so nobody has to count, and the end of shift gets its own. Different tones for different meanings is the single cheapest improvement to a shop-floor bell system — one tone for everything trains people to ignore it.

Three-shift running is the same file with more slots: 06:00, 14:00 and 22:00 starts and their associated breaks, all in one day's entry, because the schedule is a list of times rather than a concept of "shift".

Continental and rotating patterns — where the crew on days this week is on nights next week — are handled with rules rather than by writing out the calendar. The rule overlays match on weekday, date-of-month, month, last-day-of-month, or slot number, and the first match wins. A pattern that alternates on odd and even weeks is expressed as two rules, not fourteen entries.

Where a pattern genuinely does not repeat on any calendar rule — a bespoke rota out of a workforce system — the better answer is not to encode it at all. Use the trigger API below and let the rota system fire the bell.

How do you page one part of a shop floor and not the rest?

Zoning means muting the parts of the distribution that should not hear a given announcement. A USB relay board provides that: four channels covers two zones plus a bell and an emergency lamp; eight channels covers four zones.

ZoneRules tags an announcement with its zone, and the mute relay of every other in-use zone opens for the duration and is always released afterwards. The realistic setup for a mid-sized plant is: zone A assembly, zone B goods-in and warehouse, zone C offices and canteen. Break buzzers go to A and B; "your taxi is here" goes to C only.

The same board can drive a real siren or bell circuit on its own schedule, with no audio involved:

<BellScheduleRules>06:00,dur=4000;14:00,dur=4000;22:00,dur=4000;10:00,dur=1500;12:30,dur=1500</BellScheduleRules>

Long pulse for shift change, short for breaks. If you already have a siren you trust, keep it — and use the audio side purely for speech.

How do announcements, drills and emergencies share one system?

The reason to put bells and announcements on one system is that they compete for the same speakers, and priority has to be decided somewhere.

• Live push-to-talk streams a microphone straight to the speakers and pre-empts whatever is playing. The person holding the microphone owns the building.
• Voice Broadcast records a message, plays it back to you first, and only transmits after you confirm — which is what you want for a message going out across a plant.
• Text announcements are spoken by an on-device neural voice, so a scheduled "line changeover in ten minutes" needs no recording at all and runs with no internet.
• A physical emergency button on a GPIO pin loops a designated file at top priority and suppresses every scheduled bell until reset, so a shift buzzer cannot fire in the middle of an evacuation.

Everything that fires is written to a playlist log and an audit log on disk, and dispatched as an outbound webhook — bell.fired, emergency.triggered, emergency.reset. When somebody asks whether the 14:00 drill actually sounded, there is a file that says so.

How does it integrate with the systems you already run?

The External Trigger API accepts the same set of actions — play a specific file, play from a folder, stop, set volume, transmit an uploaded clip — over three transports:

• LAN HTTP — POST /api/trigger on the device, bearer-token authenticated. The simplest thing for a PLC gateway, an Ignition script, or a line-side button box.
• MQTT — subscribes to a topic on your broker, so a plant that already runs MQTT needs no new infrastructure and can apply its existing per-client ACLs.
• Cloud HTTP — the same call over the internet for systems that live off site.

That is usually the honest answer to "can it follow our rota": rather than modelling the rota twice, let the system that owns it fire the bell.

What does it cost?

Licences are one-off and perpetual for the device count they cover. A single-building plant with a siren and three zones is typically £250–£450 all in.

Which bell tones actually work in a noisy building?

Tone choice is where most of the perceived quality of a factory bell system lives, and it is usually an afterthought. A tone has to cut through broadband machine noise without being painful, be distinguishable from every alarm already on site, and stay recognisable through a horn speaker. The practical rules:

• Use distinct tones for distinct meanings. Break start and break end should be immediately distinguishable at fifty metres.
• Longer, not louder. A three-second tone at a sensible level carries better through machinery noise than a one-second blast turned up.
• Put speech and tones at different levels. A volume profile can hold announcements at a different level from bells, and drop both after the last shift so a night-shift skeleton crew is not blasted.
• Randomise within a folder. Several variants of the same bell prevents the sound becoming wallpaper.

Try the live demo — a working dashboard in your browser, nothing to install.

FAQ

Multilarm is scheduled-audio, announcement and emergency-alert software for factories, schools, mosques and other facilities. Free for personal use; one-off licences for commercial deployment. See pricing or try the demo.