Remaining Stability Budget (RSB) Add-Back and Excursion Resolution

Last updated: May 13, 2026

Overview

When a completed temperature excursion is resolved in Product Release, the platform recalculates shipment stability metrics as if that excursion no longer counts against the shipment’s temperature limits.

This process effectively:

  • Adds back Remaining Stability Budget (RSB)

  • Reduces the shipment’s calculated Time Out of Range (TOR)

  • Updates downstream product stability calculations

If the excursion is later un-resolved, the system reverses those changes and the excursion once again contributes to the shipment’s TOR and stability consumption.

Why This Matters

Not every excursion represents a true product quality risk.

In some cases, excursions may be reviewed and determined acceptable based on:

  • Product stability data

  • Packaging performance

  • Operational context

  • Quality review outcomes

Excursion resolution allows approved events to be excluded from stability calculations while maintaining a complete audit trail of the decision.

Eligibility Requirements

Completed Excursions Only

Only completed excursions can be resolved.

Excursions that are still in progress are not eligible for resolution.

Upload Method Considerations

Resolution behavior may vary depending on how temperature data was uploaded.

In many deployments, full excursion resolution and RSB recalculation behavior is primarily supported for:

  • PDF uploads

  • Temperature data uploads

Your organization’s configuration and product rules determine which uploads support full recalculation behavior.

Who Can Resolve or Un-Resolve Excursions

Users with the appropriate shipment access permissions can resolve or un-resolve excursions.

This typically includes:

  • Members

  • Admins

Permissions may vary depending on your organization’s access model and configuration.

How Excursion Resolution Works

Resolving an Excursion

For a device with a completed excursion:

  1. The user initiates excursion resolution from the shipment or device details view.

  2. The user provides a justification or resolution note.

  3. The justification is stored as part of the audit trail and device resolution history.

  4. The excursion status updates to resolved.

  5. Device temperature status and related shipment metrics refresh automatically.

Once resolved, the excursion no longer contributes to adjusted TOR calculations used for stability evaluation.

Un-Resolving an Excursion

If a resolved excursion needs to be reversed:

  1. The user initiates the un-resolve workflow.

  2. The system restores the excursion into active calculations.

  3. TOR totals increase accordingly.

  4. Remaining Stability Budget decreases to reflect the excursion again.

This returns the shipment closer to its original stability picture prior to resolution.

Understanding TOR and RSB Add-Back

Original TOR

Time Out of Range (TOR) is calculated as the total duration spent outside approved temperature limits.

For each excursion event:

TOR = End Time − Start Time

The shipment’s original TOR is the sum of all applicable excursion durations.

Adjusted TOR After Resolution

When an excursion is resolved:

  • Its TOR contribution is removed from adjusted totals

  • The shipment’s effective TOR decreases

  • Stability calculations refresh using the adjusted TOR value

Only unresolved excursions continue contributing to adjusted TOR totals.

Remaining Stability Budget (RSB)

Remaining Stability Budget reflects how much allowable product stability margin remains for the shipment.

When excursions are resolved:

  • Adjusted TOR decreases

  • Stability consumption decreases

  • Remaining Stability Budget increases

This increase is commonly referred to as the RSB add-back.

When excursions are un-resolved:

  • Adjusted TOR increases again

  • Stability consumption returns

  • Remaining Stability Budget decreases accordingly

Product Stability Calculations

Exact RSB percentages and stability indicators depend on your configured:

  • Product profiles

  • Lane settings

  • Shipment configuration

  • Stability thresholds

  • Cumulative batch rules (if enabled)

Because stability rules may vary by organization and product type, the recalculated values will follow your configured product stability model.

Audit Trail and Notifications

Excursion resolution actions are fully recorded for traceability and compliance purposes.

Recorded Information

For both resolve and un-resolve actions, the system captures at minimum:

  • Action timestamp

  • User who performed the action

  • Resolution note or justification

  • Excursion start time

  • Excursion end time

  • Original TOR

  • Adjusted TOR

Resolution notes are commonly stored as part of the device thread or resolution history and may not be editable after submission depending on your organization’s configuration.

Notifications and Comments

The platform may generate:

  • Device-level system comments

  • Excursion resolved notifications

  • Excursion unresolved notifications

Notification behavior depends on your organization’s configured notification and comment settings.

Example Scenario

A shipment contains a completed 2-hour excursion.

Initially:

  • The 2 hours contribute to total TOR

  • Remaining Stability Budget decreases accordingly

After quality review, the excursion is resolved:

  • The 2-hour TOR contribution is excluded from adjusted totals

  • Remaining Stability Budget increases

  • Stability indicators refresh automatically

If the excursion is later un-resolved:

  • The 2-hour TOR contribution returns

  • Remaining Stability Budget decreases again

  • Stability calculations revert accordingly