The single-brand problem
OEM tools are typically strongest inside their own brand ecosystem. In a mixed site, operators can end up reconciling several consoles, different alarm wording, separate reporting habits, and inconsistent visibility into battery replacement timing.
The MayaUPS approach
MayaUPS monitors major brands through SNMP v1/v2c/v3 and RFC-1628 where the network-management card exposes the required data. Vendor-specific profiles add more readable decoding when available, while the baseline monitoring workflow stays consistent across the fleet.
Battery and alerting depth
MayaUPS tracks more than online and offline state. It records battery install date, nominal life, preventive-maintenance date, temperature-adjusted estimates, and due alarms roughly 30 days ahead. SMTP alerts support grouping, return-to-normal notices, escalation, and an optional daily digest.
Shutdown in the current release
The current release includes controlled shutdown without feature gating. The safety model is Observe → Dry-run → Armed, with proof before arming, SNMP-SET for UPS shutdown, and an mTLS host agent for ordered host shutdown. Live-action paths still require final real-hardware bench approval before general release.
A fair fit statement
If a site is genuinely all one brand and the OEM tool covers the required workflow, that tool may be enough. MayaUPS is for the mixed-brand reality: one local bilingual console, one set of alerts, one battery-planning view, and one safety-gated shutdown workflow.