- Energy
OQ8
Infrastructure monitoring across plant and corporate networks, with alert thresholds tuned to how the operations team actually works.

Monitoring existed before we arrived, and that was the problem: enough alerts arrived each morning that the team had stopped reading them. An alert nobody reads is worse than no alert, because it looks like coverage.
Tuning before extending
The first phase added no new coverage at all. We reviewed every existing threshold against what the team would genuinely act on at three in the morning, and removed or raised the rest.
Then the gaps
With the noise down, the real gaps were visible. Plant network devices and several application tiers had no coverage, and their failures had been surfacing as user complaints rather than alerts.
Where they are now
Alert volume is a fraction of what it was and each one has an owner and a runbook entry. Coverage extends across both networks, and escalation reaches our engineers in Muscat when it needs to.

Layla Al Balushi
Principal consultant, ITSMPrincipal consultant for service management at DWITS. Layla has led ManageEngine assessments and implementations across government, banking and higher education in Oman, and writes about the operational side of platform decisions.
Ask Layla a questionRelated customer stories
Banking
National Bank of Oman
Three branch support queues and no shared asset record. Fourteen weeks later, one governed service desk covering every branch and the head office.
Read Telecommunications
Ooredoo
Recurring internal IT requests were handled by hand at every step. Automating the mechanical ones took the queue back to work that needs a decision.
Read Logistics
Sohar Port
Endpoint management and patch discipline across terminal and administrative sites, on a schedule that does not interrupt vessel operations.
Read
