A monthly average does not show an event at the tail. When reviewing duration per run, keep the limit definition, logging interval and measurement gaps in the same table.
Estimating duration from records
Mark consecutive readings outside the limit; the logging interval between them informs the duration estimate. Use the span from first to last reading, and do not treat one row as proof of a full duration.
Limits of the logging interval. For example, hypothetically, two consecutive out-of-limit readings on a ten-minute interval show at least one interval between them; exact start and end times remain unknown. Check the device setting and timestamps.
Separate missing rows
A data gap means no measurement; it proves neither normal temperature nor a continuous excursion. Mark gaps in the archive and check the export range.
Which duration to report
Total duration summarizes the month's accumulation, while the longest event summarizes one continuous measured sequence. Show them in separate columns using the same limit definition.
Verify the limit
Use product requirements, validated route conditions and the authorized quality process. If several products are involved, confirm the assessment method with the quality role and record it.
A peak is a moment; duration summarizes the measured sequence.
Monthly total and longest event
Hypothetically, two months can have the same total duration while one has a single long event and the other has short events. Present event count and longest estimated duration alongside the average.
Follow-up review
If the longest event appears on a particular route or shift, compare timestamps with loading and stop records. Co-occurrence alone does not establish a cause.
Tie the decision to records
State the limit source, logging interval, gaps and calculation method in the report. Leave product decisions to the authorized quality process.
