InnerWeb
Skip to main content

Automation rules: what manual dispatcher notifications cost

A dispatcher who calls or writes to interested people after every change of a work permit status loses, in a typical plant, more than an hour a day on a task that can be saved as a rule. Below we show what makes up this cost, how one rule with a notification action reduces it, and what assumptions stand behind the sample calculation.

72 min
a day taken over by automation, 80 percent scenario
Source: sample calculation
9
trigger types in the rules engine
Source: feature card
26.4 h
monthly saving over 22 working days
Source: sample calculation

What manual notification costs

Manual notification is a series of small actions: the dispatcher sees a change of permit status, works out who it concerns, chooses a channel and writes or calls. A single action takes a few minutes, but it is repeated several dozen times a day and takes time away from the coordination of the work itself.

The second cost is quality: a notification sent late or skipped when the schedule is overloaded. A rule sends the message every time and in the same way, so this cost disappears, although its value has to be assessed against the plant's process.

Which notifications are easiest to automate?

The easiest are those in which the recipient and the content follow from the event: a change of permit status, an alarm, inactivity, SOS or a change of report status. The rules engine has 9 trigger types, among them an external event, a schedule, the presence of an employee and a change of equipment location.

What one rule changes

A rule consists of a trigger, optional conditions on the event's attributes, and one or more actions. The actions are e-mail, push, a team notification, a webhook, and opening a permit from a template. One rule replaces a routine dispatcher task: a change of permit status starts the notification, without human involvement.

Matching a rule places the message in asynchronous processing, and the rule subscriber never raises an exception. A failure of the automation therefore does not block the approval of a permit or a change of report status. The worst effect is a return to manual notification until the fault is fixed.

Conditions reduce the noise

Several filters are combined with an AND condition, so a rule can notify only about permits in a chosen zone, or only about a change to a specific status. Fewer unnecessary notifications also means a smaller cost to the recipients' attention.

Conditions checked at the moment of matching

Some attributes, for example whether a person is online right now, come from the current state in the system rather than from the event. This makes it possible to write a rule such as: notify only if the supervisor is currently available.

Minutes a day on notifications about status changes

Minutes a day on notifications about status changesComparison: 90 minutes a day of manual notification against 18 minutes after the rules are deployed.020406080100minManual: Dispatcher: 90 min90 minManualWith rules: Dispatcher: 18 min18 minWith rules
Source: Sample calculation based on the assumptions in the Sample calculation section

Sample calculation: minutes a day

The sample calculation assumes 30 permit status changes a day that require a notification, and 3 minutes of manual notification per change. This gives 90 minutes a day of dispatcher work.

If the rules cover 80 percent of the changes, that is 24 out of 30, automation takes over 72 minutes a day. The dispatcher keeps 18 minutes for exceptions in which a conversation is needed rather than a standard message. The saving is 72 minutes a day, which over 22 working days is about 26.4 hours a month.

The 80 percent assumption is cautious: the remaining changes are unusual cases. At 60 percent the saving is 54 minutes a day, and at 90 percent it is 81 minutes a day.

Cost of deploying a rule

The rule wizard in the panel works with icon tiles in two steps: choosing the trigger, then the filters. Fields that point to system objects have selectors instead of identifier numbers. A person without programming knowledge builds a rule in a dozen or so minutes, and the cost of that work pays back on the first day of operation.

The recurring cost is a periodic review of the rules: a few times a year it is worth checking whether the conditions still match the current organisation of work. Without a review, rules age like any other procedure.

  • List the notifications the dispatcher sends by hand, with the number per day.
  • For each one, choose the trigger, the conditions and the action.
  • Switch on the rules starting with the most frequent one.
  • After two weeks, compare the number of manual notifications with the number before deployment.

What this calculation does not include

The calculation leaves out the value of faster information in emergencies and the cost of errors caused by a skipped notification. Both items are real, but they depend on the plant's process, and we do not price them without knowing how the work is organised.

The calculation also does not assume that all notifications can be automated. Messages that require a decision or a conversation stay with a person, and automation frees that person's time for exactly those matters.

Example calculation

Sample calculation: dispatcher notifications

Assumptions
ParameterValue
Status changes requiring a notification30 changes/day
Time of one manual notification3 min
Share of changes covered by rules80 %
Working days22 days/month

Result: Manual: 90 min/day; with rules 18 min/day; saving 72 min/day, about 26.4 h/month.

Note: Sample calculation. Measure your plant's own values over a week of observing dispatcher work.

Video

Frequently asked questions

Can a rule replace a conversation with the work supervisor?

No. The rule sends a standard message. The conversation stays where a decision or an agreement is needed.

What if the rule stops working?

An automation failure does not block the approval of a permit or a change of report status. The dispatcher goes back to manual notifications until the fault is fixed.

Can someone outside IT build a rule?

Yes. The wizard in the panel works with tiles in two steps, and system objects are chosen from selectors, without identifier numbers.

Automate the dispatcher's notifications

In a demo we will show how to build a first rule for a permit status change. Book a meeting with the InnerWeb team.

Let's talk