Input Requested: Defining the Logic Threshold for "Normal" vs. "Reduced" Power

[Rennhack]

I am currently finalizing the code for the new Rx Power Status tool on the site, and I want to ensure the status labels reflect operational reality rather than just raw data.

The baseline is easy: I am hard-coding anything reporting 0% power as "Offline/Tripped/Outage."

The challenge lies in where to technically draw the line for "Reduced Power." I know that "Normal Operations" rarely means pinning the needle at exactly 100% for the entire cycle. Operations will often lower power by a certain margin to maintain a safety buffer, ensuring that minor transients or specific work scopes don't cause a spike that jumps the unit over 100% (or triggers a license limit violation).

My question to the Ops and Engineering folks here is: At what point does that buffer stop being "Standard Operating Procedure" and start being a notable "Reduced Power" event?

I am trying to solve for X in the following logic:

    Offline: 0%

    Reduced Power / Power Ascension: 0% to X%

    Normal Operation: X% to 100%

If a unit is holding steady at 96% or 98% for margin control, should the tracker flag that as "Reduced," or is that effectively "Normal" in your view? I'm looking for a consensus percentage (e.g., is the cutoff 90%? 95%?) that separates a standard operational buffer from a genuine power reduction issue that the community would want highlighted.