BENSYS: Four Systems in One Dashboard
Server maintenance was documented without a common structure, and the information needed sat in four systems, each with its own interface and its own authentication method.
Services Used
The situation
BENSYS looks after the IT infrastructure of several clients. Until then, server maintenance was documented without a common structure. Before every maintenance window the same research started from scratch: what happened last time, which event log had already occurred, how it was resolved back then. The answers were spread across four systems for device monitoring, tickets, client management and billing, each with its own interface and its own authentication method.
The solution
I built a dashboard that brings these sources together and puts the maintenance documentation on top of them. Every external system gets its own package that encapsulates its quirks and offers one consistent model to the outside. Access tokens are cached and renewed deliberately when a request is refused; rate limits lead to retries with growing intervals rather than to failures. Sign-in runs over Microsoft Entra ID in the authorization code flow with OpenID Connect, and access to sensitive areas is checked server side rather than only in the interface. Every synchronisation with an external system is logged, with errors and record counts.
The result
Maintenance is comparable over time per client and per server. A recurring event log shows the previously documented solution directly instead of being researched again. If a source fails, that becomes visible instead of quietly leading to stale data. As of July 2026 the system covers 24 database tables, 14 interface areas and 18 screens.