EXPLAINER
RFC-1628 defines the standard UPS MIB. It gives monitoring tools a common baseline across UPS brands, which is why it matters for mixed fleets that cannot rely on one manufacturer utility.
MayaUPS uses universal RFC-1628 decoding for standard UPS states exposed by network-management cards. That common layer can cover essential readings such as status, battery charge, runtime remaining, load, input/output voltage, temperature, and alarm state when the device exposes those objects.
Vendor-specific bitmask and flag decoding adds readable detail where manufacturers expose more than the standard MIB. MayaUPS includes profiles for known devices, but the current vendor-specific profiles remain pending hardware verification. The standard RFC 1628 profile is the verified baseline.
Raw codes become states such as On battery, Replace battery, and Overtemperature, which are easier to route and act on. A readable alarm can feed grouped SMTP notices, escalation, return-to-normal messages, daily digest summaries, and incident review without requiring the recipient to interpret object identifiers.
The standard MIB gives a baseline, but real fleets often need vendor context, history, and maintenance planning. MayaUPS adds 24 h / 7 d / 30 d charts, CSV export, battery service-life forecasting, install dates, preventive-maintenance dates, and temperature-adjusted estimates on top of the raw monitoring layer.
RFC-1628 monitoring can help determine when a UPS is on battery or runtime is low, but shutdown should still be gated. MayaUPS separates Observe, Dry-run proof, and Armed states, then uses SNMP-SET for UPS shutdown and an mTLS host agent for ordered host sequences where configured.
For public-sector and Quebec buyers, RFC-1628 support is also a procurement signal: it shows that the software is not limited to one vendor ecosystem. MayaUPS pairs that technical baseline with EN-CA / FR-CA language support, local data residency, accessibility evidence, and security artifacts.