Use Case · Hyland OnBase

How a global enterprise put 28 OnBase servers under one watch — observed, assured, self-healed.

A business-critical, global Hyland OnBase environment retired its fragmented monitoring — two standalone tools, four-times-a-day manual checks, and PowerShell scripts — for a single Content Observability layer. The result: continuous 24/7/365 coverage and over $200,000 saved in three years.

  • 24/7/365 monitoring across every OnBase service
  • Automated self-healing before issues reach the queue
  • One dashboard for the whole 28-server estate
$200K+ saved / 3 yrs 28 servers, one view 24/7/365 coverage
ONBASE ENVIRONMENT · 28 SERVERS24/7 AVAILABILITYPROCESSINGWEB CLIENTSUNITY CLIENTSAT RISKReveille · Content Observabilityone watch over all 28 servers — services, drives, server health, clientsSELF-HEALrestart IIS · notify · ticket
Environment Snapshot Business-critical · global
Platform
Hyland OnBase — high-availability, global system
Scale
28 servers — processing, Web, and Unity clients
Availability requirement
24/7 — downtime is not an option
Observability layer
Reveille — one watch across the estate
The Challenge

A mission-critical system, watched by parts that didn’t add up to a whole

OnBase ran the enterprise’s content operations on 28 servers and could not be allowed to fail — yet visibility into it was assembled from disconnected pieces. Coverage existed, but it was manual, periodic, and scattered across tools that never spoke to each other.

Two separate programs checked services and server health. A managed-services routine ran manual system checks four times a day. PowerShell scripts kept an eye on the share drives. Each piece worked in isolation — but nothing produced a single, high-level picture of whether the environment was actually healthy. Between the manual checks, the system was effectively unobserved, and a stalled process or a failed client could run for hours before anyone noticed.

The Shift

From four manual checks a day to one continuous watch

Reveille consolidated every disconnected check into a single observability layer — replacing periodic, manual coverage with continuous, automated assurance across the whole estate.

Before Reveille
Two separate programs
Service health and server health checked in different tools
Manual checks, 4× a day
A managed-services routine, run by hand on a schedule
PowerShell scripts
Share-drive monitoring stitched together with scripts
No single high-level view
No one place that answered “is the environment healthy?”
Reveille
With Reveille
24/7/365 monitoring
Every service watched continuously, with stalled-process detection
Automated self-healing
Restarts IIS when issues are found — before a ticket is filed
Email + Teams + ServiceNow
Notifications routed and a ticket opened automatically for tracking
One dashboard, weekly KPIs
A single high-level view of all 28 servers, plus KPI emails
Technical Validation

What Reveille actually does in this OnBase environment

Not a status page. Reveille monitors, alerts, self-heals, and reports across the application and content layer the business runs on — the services, drives, servers, and clients that determine whether OnBase is genuinely working.

Monitoring

Continuous coverage

  • All OnBase services, with stalled-processing detection
  • Every shared drive, to keep process flow moving
  • Server statistics — processors, memory, IIS
  • Web and Unity client availability checks
Self-healing

Resolve, don’t just alert

  • Automatically restarts IIS when a fault is detected
  • Acts before issues reach the ticket queue
  • Cuts time-to-recovery on common failures
Alerting & workflow

Routed to where work happens

  • Notifications via email and Microsoft Teams
  • Opens a ServiceNow ticket for issue tracking
  • Feeds the tools the team already lives in
Visibility & reporting

One pane, proof on a cadence

  • Single dashboard for all monitoring
  • Weekly and monthly KPI emails
  • A high-level health view of the whole estate
Business Value

What the change was worth

The value didn’t show up as a line item — it showed up as reclaimed engineering hours, fewer outages, and faster resolution on a system that can’t go down.

$200K+
saved over three years
24/7/365
continuous coverage, replacing 4 manual checks a day
3→1
tools and manual routines consolidated into one layer
28 srv
servers under a single high-level view
Why The Team Landed On Reveille

A system this critical can’t be watched by hand, four times a day. Reveille made it one continuous watch.

Based on a real Reveille customer — a global enterprise running Hyland OnBase across 28 servers. Figures reflect the customer’s own reported results.

FAQ

Common questions

What did this OnBase environment look like before Reveille?
A high-availability, business-critical, global OnBase system running across 28 servers for processing, Web, and Unity clients — with a hard requirement for 24/7 availability. Coverage was assembled from two separate programs for service and server health, manual system checks run four times a day through a managed-services arrangement, and PowerShell scripts for share-drive monitoring. There was no single high-level view of the estate.
What does Reveille actually monitor and automate in OnBase?
Reveille delivers 24/7/365 Content Observability: it monitors all OnBase services and checks for stalled processing, watches every shared drive to keep process flow moving, tracks server statistics including processors, memory, and IIS, and verifies Web and Unity client availability. When it finds a problem it can self-heal — for example restarting IIS automatically — then notifies the team by email and Microsoft Teams and opens a ServiceNow ticket for tracking. Everything rolls up into one dashboard, with weekly and monthly KPI emails. In short, Reveille monitors, alerts, self-heals, and reports across the environment.
What was the measurable business value?
The environment moved from periodic manual checks to continuous 24/7/365 coverage with a single high-level view, retired two standalone tools and a manual managed-services routine, and gained automated self-healing and ticketing. The team reported savings of over $200,000 across three years — value that came from reclaimed engineering time, fewer outages, and faster resolution, rather than from a single cost line.

Your OnBase environment runs the business. Reveille makes sure it holds.

See what continuous Content Observability looks like across your own ECM, IDP, and automation platforms.