EXPLAINER
RFC-1628 defines the standard UPS MIB: the common baseline that lets one monitoring tool read many UPS brands. That is exactly what a mixed fleet needs when it cannot rely on a single manufacturer utility.
MayaUPS decodes the standard RFC-1628 states that network-management cards expose. When the device offers those objects, that one layer covers status, battery charge, runtime remaining, load, input and output voltage, temperature and alarm state.
Profiles add readable detail when a card exposes more than the standard MIB. Available readings vary by UPS model, card and firmware, so confirm your exact combination before you deploy.
Raw codes become On battery, Replace battery, Overtemperature: states you can route and act on. A readable alarm can feed grouped email notices, escalation, return-to-normal messages, a daily summary and incident review, with no object identifiers to decipher.
The standard MIB is a baseline. A real fleet also needs vendor context, history and maintenance planning, so MayaUPS adds 24 h / 7 d / 30 d charts, CSV export, battery service-life forecasting, installation dates, preventive-maintenance dates and temperature-adjusted estimates on top.
RFC 1628 data can tell you a UPS is on battery or that runtime is getting low. Before that data is allowed to trigger a shutdown, review the policy and run the test that switches nothing off.
RFC 1628 loosens the grip of any one manufacturer’s software by giving everyone a common baseline. MayaUPS pairs that baseline with a bilingual interface, local data storage, history and battery planning.