Notifications

Make Sure What Matters Gets Heard.

Your operation generates thousands of signals every shift. OTSI mining notification software helps make sure critical operating events reach the right person, trigger the right response and escalate when action is missed.

The Performance Gap

Critical Signals Are Easy to Hear. Until Everything Is Critical.

Mining operations are constantly generating information about changing conditions, emerging risks and events that require attention.

The problem is rarely whether the information exists.

The problem is whether the signal that matters reaches the right person, at the right time, with a clear expectation for what happens next.

Without a structured response process, important events compete for attention, ownership can be unclear and unresolved issues can quietly become production loss.

Your operation can identify the problem. Notifications helps make sure somebody hears it, owns it and responds.

Important signals compete for attention

During a busy shift, critical operating conditions can disappear into the volume of information teams are already managing.

Response depends on who is working

Different supervisors, dispatchers or crews may respond differently to the same condition.

Ownership can become unclear

When responsibility is not explicitly assigned, issues can remain unresolved or depend on someone remembering to follow up.

Escalation happens inconsistently

A missed response does not always trigger the next level of attention soon enough.

What happened next can be lost

Without response history, recurring issues are difficult to review and lessons from previous events can disappear between shifts.

NOTIFICATIONS CAPABILITIES

Turn Important Operating Signals into Structured Response.

Notifications connects defined operating conditions with the people responsible for acting on them. When a condition reaches an operating threshold, the solution can notify the appropriate role, track acknowledgement, escalate missed responses and preserve what happened for future review.

Event-Based Notifications

Automatically trigger notifications when defined delays, bottlenecks, operating conditions or performance thresholds occur.

Configurable Operating Thresholds

Define when an operating condition becomes important enough to require attention based on the site’s performance standards and operating context.

Response Ownership

Direct the event to the role responsible for responding so accountability is established from the outset.

Escalation Logic

Escalate unresolved events when acknowledgement or action does not occur within the required timeframe.

Response Tracking

Capture acknowledgement, intervention and response activity so teams can see what happened after the signal was raised.

Notification History

Maintain a structured record of events, responses and escalation activity to support follow-up and review.

NOTIFICATIONS CAPABILITIES

Hearing the Signal Is Only the Beginning.

A delay exceeds its threshold.
A queue continues to grow.
A production condition moves outside the expected range.
A recurring issue appears again.

The operation has spoken.

What determines the outcome is what happens next.

Who sees it?
Who owns it?
How quickly do they respond?
What happens if they don’t?

Notifications help turn an operating signal into a clear expectation for action.

FROM SIGNAL TO FOLLOW-THROUGH

From Event to Action in Seconds

Notifications create a repeatable response process so important events do not depend solely on individual awareness or memory.

01 Threshold breached

When a defined operating condition occurs, the system detects it instantly. Example thresholds: queue time >2 min, crusher queue >3 min, empty stop >10 min, hang time over defined limit. Thresholds are site-configured and stay meaningful.

02 Alert delivered

The right person receives a notification via Microsoft Teams or email. No manual checking. No waiting for someone to spot it on a trends screen.

03 Response required — or escalated

The recipient must acknowledge and respond within a defined window. If no response is made in time, the event automatically escalates to the next level of supervision.

04 History captured

Every event, response time, escalation, and outcome is logged. Over time, this creates an operational learning record that reveals patterns traditional shift reports cannot surface.

BUILT AROUND THE PEOPLE WHO RESPOND

Clearer Priorities for Frontline Teams. Better Follow-Through for Leaders.

FOR OPERATIONS LEADERS

Greater Confidence in Response

Know that defined production-impacting events have a clear path from detection through acknowledgement and escalation.

Better Visibility Into Follow-Through

Understand where events are being resolved consistently and where response gaps remain.

More Consistent Operating Discipline

Apply common response expectations across crews, shifts and operating areas.

Better Insight Into Recurring Issues

Use event and response history to identify patterns requiring deeper operational improvement.

FOR FRONTLINE TEAMS

Know What Needs Attention

Receive relevant operating events without having to continuously monitor every source of information.

Understand What Is Expected

Give each notification clear context, priority and responsibility.

Reduce Manual Follow-Up

Use structured escalation rather than relying on phone calls, radio messages and individual memory.

Respond With Greater Confidence

Connect recurring operating conditions to established response expectations and guidance.

DON'T LET THE SIGNAL GET LOST

Make Every Important Operating Issue Easier to Hear, Own and Act On.

Connect critical operating conditions to clear ownership, structured escalation and traceable follow-through so the signals that matter have a better chance of changing the result.