From monitoring data to operational intelligence

The problem - When everything looks equally urgent, nothing gets prioritised.

The result - The alert that matters, the one that means a clinical system or a payment platform is degrading, is invisible.

1. The Problem - Too Many alerts. Zero context.

Open the SCOM console on any given morning and you'll see something like this. Hundreds of alerts. Some critical. Some warnings. Even more informational which will never get looked at.

Which one matters? Which system is actually at risk? Which alert represents a genuine incident affecting the business — and which ones are noise from an untuned management pack?

The problem isn't that SCOM isn't monitoring. The problem is that this view offers no way to connect an alert to its business impact. Is this a performance blip on a test server? Or is this the application log filling up withe errors on the CVIS cardiology imaging system that clinicians are trying to use right now?

You can't tell. And that's the gap SquaredUp Dashboard Server is designed to close.

2. The solution - Visualise your application estate.

Rather than starting with alerts, SquaredUp Dashboard Server starts with your business services. Every clinical system, diagnostic platform, operational tool and piece of supporting infrastructure is mapped as a tile. The colour tells you everything at a glance.

When all tiles are green, everything is healthy. That's a dashboard the Service Manager can glance at every morning. It's a view the IT Director can share with the board. It's the live evidence that SCOM is working, your systems are up, and the business is running.

Notice what's on this dashboard. Not just the clinical systems — EPMA, EPR and PAS — but the full dependency chain.

Diagnostic systems: CVIS, PACS, RIS.

Operational: Beds, Outpatient, Theatre.

And underneath it all, the infrastructure: Active Directory, Hyper-V, SQL Server and ServiceNow.

This is the application estate mapped to business services. It's not a list of servers. It's a representation of what the business actually depends on — and SCOM's deep monitoring data is powering every tile.

Dashboard Server doesn't replace SCOM. It makes SCOM's data visible to everyone who needs it — not just the engineers who know where to look in the console.

3. Something changes: one tile turns red.

Then something happens. SCOM detects a problem. In the old world, it would fire an alert into a queue of hundreds of others and wait for someone to notice.

In Dashboard Server, it turns a tile red.

The power of this view isn't just that something is red. It's everything that's still green. The Service Manager can see in a single glance that this is an isolated issue in the Diagnostic Systems tier. EPR, EPMA and PAS are unaffected. The operational systems are fine. The infrastructure underneath is healthy.

That context — which is completely absent from the SCOM console — transforms the response. Instead of a major incident bridge call trying to work out scope, the team already knows: one diagnostic system, isolated problem, everything else operational.

This is the difference between monitoring data and operational intelligence. SCOM has the data. Dashboard Server turns it into a decision.

4. Follow the red: drill down to the alert.

Click the red CVIS tile. Dashboard Server opens the business service view — showing you exactly which component within CVIS has the problem, the alerts heatmap showing when it started, and the open alerts that are driving the red status.

This is where the story becomes specific. Not "CVIS is broken" — but "the App Log component within CVIS is generating a critical alert." The alert name is visible right there: File Age Count Threshold Exceeded. The other three components — OLE DB Checks, URLs and Windows Services — are all green. The application is running. The database connection is fine. It's a log file management issue and we know that starts to happen when the service stalls. It pre-empts a wider failure. Restart the service (yes, we need to fix this properly in our next release of CVIS).

Without Dashboard Server, finding this would mean knowing to look for CVIS in the SCOM console, filtering the alert view, understanding the management pack structure, and working out which of those hundreds of alerts was the relevant one.

With Dashboard Server, it's two clicks from the business services overview.

5. The alert detail: full context in one place.

Click the alert and Dashboard Server surfaces the full SCOM alert detail — but now enriched with business service context. You can see the description, the support details, the business service it belongs to, the team responsible, and the full context data SCOM captured at the time of the alert.

The resolution state panel lets you act immediately: assign to yourself, update the ticket ID, change state to Assigned to Engineering, add a comment. All without leaving Dashboard Server. All with the full SCOM data in context.

6. Verify: Back to Green.

The issue is resolved. SCOM detects the recovery. And the dashboard reflects it immediately — CVIS turns back to green, and the Service Manager has a complete picture of a healthy estate.

7. Result

1. Monitoring tells you something is wrong.
2. SquaredUp Operational Intelligence tells you what to do about it.