On-call staff cannot function if every trivial alert wakes them at three in the morning, but they must be woken for anything genuinely urgent. Quiet hours resolve this tension by scheduling when low-priority notifications are held back while critical ones always break through. This guide explains what quiet hours and do-not-disturb windows are, how the critical-alarm override keeps them safe, and how this notification-policy idea differs from shelving or suppressing the alarm itself, which is a completely separate action.
Notification quiet hours in one line: Notification quiet hours, also called a do-not-disturb window, are configured periods, typically overnight, during which low-priority notifications are held or deferred rather than delivered, so on-call staff are not disturbed by nuisance alerts. Critical alarms are configured to override the quiet hours and are delivered anyway, so genuine emergencies still get through. Quiet hours act on the delivery schedule of notifications, not on the alarm itself, which continues to be recorded and handled normally.
Quiet hours are a rule about timing: they define a window on the clock during which the notification system changes how it delivers alerts. Outside the window, notifications flow normally. Inside it, typically overnight or during other agreed off periods, low-priority notifications are held back rather than pushed to the recipient, so that alerts that can reasonably wait until morning do not intrude in the middle of the night. The alarm still occurs, is still recorded, and can still be seen; what quiet hours change is whether the recipient is actively disturbed by it at that hour.
The purpose is to protect the people who carry the alarms. On-call staff are a finite resource, and their effectiveness depends on rest and on trusting that a notification at an unsocial hour means something. If they are woken repeatedly for low-consequence events that could have waited, two things go wrong: they become exhausted, and they start to disregard notifications, which is far more dangerous than any single missed nuisance. Quiet hours preserve both the responder's rest and their responsiveness by ensuring that being disturbed at night is reserved for events that warrant it.
Quiet hours are usually defined as part of a notification policy that can vary by recipient, by role, and by day. A weekday daytime pattern differs from nights and weekends, and different responders may have different windows. The held notifications are typically not lost; they are deferred, so they surface when the quiet window ends or can be reviewed on demand, which means nothing is discarded, only rescheduled. The policy captures the judgement about which times are protected and, crucially, which alarms are important enough to ignore that protection.
Quiet hours would be reckless without an override, and the override is what makes them safe. The essential rule is that a quiet window applies only to notifications that can genuinely wait, and that critical alarms are exempt. A high-priority alarm, one whose consequence is serious and whose response cannot be delayed until morning, is configured to break through the quiet hours and reach the responder immediately, at any hour. The quiet window silences the nuisances; it must never silence the emergencies.
This is where the priority scheme and the notification policy meet and why an honest priority scheme underneath is so important. The override keys off priority: low-priority notifications are held during quiet hours, high-priority notifications override them. That only works if priorities are assigned truthfully, so that critical really means critical. If priorities are inflated, too much overrides the quiet hours and the protection is worthless; if a genuinely critical alarm is mis-rated as low, it could be wrongly held. The value of quiet hours therefore depends directly on the discipline of the underlying prioritisation.
The override also interacts with channel and escalation behaviour to stay robust. A critical alarm that overrides quiet hours should still cascade across channels and still escalate if it is not acknowledged, because breaking through the quiet window is only the first step; the alarm must still actually reach and engage someone. Well-designed quiet hours therefore do not weaken the reliability of critical notifications at all. They simply add a schedule that filters out the low-priority noise at unsocial hours, leaving the full force of the notification system available for the alarms that matter whenever they occur.
It is important to see that quiet hours act on delivery, not on the alarm. Shelving and suppression operate on the alarm itself: they stop it from annunciating or hold it back at the source, changing whether the alarm is presented at all. Quiet hours leave the alarm entirely intact, active, recorded, and visible on the operating displays, and change only whether and when a notification about it is pushed to a person's phone. The same alarm that is silently held from a sleeping responder overnight is still fully present in the system for anyone watching the screens.
This distinction has real consequences. Because quiet hours are a delivery-schedule policy rather than an alarm action, they do not risk hiding a condition from the process record or from an on-shift operator; they only govern the personal notification. Shelving, by contrast, can genuinely conceal an alarm and carries the well-known hazard of being forgotten. Quiet hours cannot make an alarm disappear from the system, which makes them a safer tool for managing after-hours interruptions specifically, without touching the integrity of the alarm system underneath.
On a cloud SCADA platform such as Merobix, quiet hours fit naturally because notification is already a distinct, centrally managed layer over the alarms coming from remote wells and facilities. The platform can hold low-priority notifications to an on-call responder during their configured quiet window while continuing to record every alarm normally, and let critical alarms override to reach them at once. Because a single platform sees the priority, the recipient, the schedule, and the delivery channels together, it can enforce quiet hours consistently across a whole distributed operation, so that responders spread across sites and time zones are shielded from nuisance alerts at night while remaining fully reachable for the emergencies that justify the disturbance.
No. Quiet hours are configured to hold only low-priority notifications during the window, while critical alarms override and are delivered immediately at any hour. The whole design depends on this override, so that on-call staff are protected from nuisance alerts at night but never shielded from genuine emergencies. It relies on priorities being assigned honestly so that critical really means critical.
Quiet hours act on notification delivery, changing whether and when an alert is pushed to a person, while the alarm itself stays active, recorded, and visible on the displays. Shelving acts on the alarm, stopping it from annunciating at the source. Quiet hours cannot hide a condition from the system or an on-shift operator, which makes them a safer tool for managing after-hours interruptions specifically.
Usually not. Held notifications are typically deferred rather than discarded, so they surface when the quiet window ends or can be reviewed on demand. The alarm itself is always recorded and remains visible in the system throughout. Quiet hours reschedule the personal notification for low-priority events rather than erasing any record of them.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.