By correcting a Spot’s status history, you can fix an incorrect event time or reason, insert a missing status change and delete an incorrect intermediate event. Together with the usage schedule, status history provides the source data for usage rate calculations. A correction may therefore also change the calculated hours in use and usage rates for earlier periods.
Before making corrections
Make corrections in the browser service. You need access to the Spot and permission to edit it. Permission to view its history alone is not enough to save or delete events.
Establish the device’s actual status and the time of the change before saving. Also check the events immediately before and after the change. If necessary, note down the original details so you can compare them with the corrected history.
The browser statuses are Active, Inactive, Faulty and Disabled. On Android and iOS, Active is called In Use. Switching between Inactive and Faulty does not automatically add an event to this status history. A missing row alone therefore does not mean that the current status has not been updated.
Open the history you want to correct
- In the browser menu, open Assets and content → Assets, devices, tools → Usability monitoring.
- Select the Event logs tab and find the Spot.
- Open the Full history events link on the Spot’s row.
By default, the Event logs overview shows the Spot’s latest event. If a date range filter hides the Spot you are looking for, clear the filter before opening its full history.
The Spot’s history opens with the latest event first. The Status on a row indicates the status after that event: it starts at the time shown on the row and continues until the next status change. It is not necessarily the Spot’s current status. Also check User and Reason for status change.
Correct an event’s time or reason
- Select the pencil icon at the right end of the history row you want to correct.
- In the Update the selected event history window, change Status begin time or Reason for status change.
- Compare the time with the previous and next events shown on the form, then select Save.
The time must be later than the previous event and earlier than the next event, if those neighbouring events exist. You cannot move an event past other events. Two events at exactly the same time are not accepted for the same Spot. If the Spot’s usability monitoring has been reset, you cannot move the event time earlier than the recorded reset time.
The Status of an existing row is locked. You cannot use the pencil icon to change the status after the event. You can delete an incorrect intermediate event and, if necessary, replace it by inserting a missing status change. An incorrect status in the first or last event cannot be corrected using these deletion functions; contact support to resolve such a correction.
Saving changes the row’s user to the person making the correction. The user shown afterwards is therefore not necessarily the person who recorded the original status change. You can leave the reason blank, but it is a good idea to describe why the correction was made.
Insert a missing status change
- Find the two events between which the change belongs. Select the plus icon at the left end of the older event’s row. The latest row does not have this icon.
- In the Insert a missing status-change event window, select Status to insert between.
- Enter Begin time for the inserted status and, if necessary, Reason for status change.
- Check the previous and next statuses, then select Save.
Status and begin time are required. The time must fall strictly between the two events and must not precede any usage rate reset time. The inserted status must differ from the status after either neighbouring event; these statuses are also excluded from the selection list. This function fills gaps between existing events and cannot add a new event after the latest one.
Inserting an event records you as its user. The new event’s starting status is taken from the preceding event, and the next event’s starting status is corrected to match the status you inserted. The status after the next event remains unchanged.
Delete an incorrect intermediate event
- Select the trash icon at the right end of the row you want to delete.
- Confirm the deletion by selecting Yes in the confirmation window.
You cannot delete the first or last event directly; their rows do not show a trash icon. If the history contains only one or two events, there are no intermediate events to delete.
Deleting an event changes the status sequence. If the statuses after the preceding and following events differ, the following event’s starting status is updated to match the preceding event’s status. If the statuses after those events are the same, the following event is also deleted as redundant. This automatic deletion can also affect the latest event.
For example, in the sequence Active → Faulty → Active, deleting the Faulty event also deletes the Active event that follows it. Always check the entire surrounding status sequence.
What does a correction affect?
A history correction changes the recorded status events. It does not itself change the Spot’s current status, the physical operating hour meter reading or the statuses of the Spot’s tasks. Inserting a historical Disabled status does not remove the Spot from the asset register either.
Update status at the top of the history is a separate function: it opens the current status update. Spot status updates on Android and iOS also change the current status. Use the history row functions when you want to correct past events.
When the time of a saved or deleted event is at or before the start of today, the correction triggers background recalculation of usage rate data. Even correcting only the reason can trigger it. When editing the time, the newly saved time determines whether recalculation starts. An event timed later than the start of today does not trigger this recalculation.
The process recalculates the Spot’s existing daily records in the service’s time zone, followed by the existing weekly, monthly and yearly results based on those records. It can change Hours in use, Desired in use and usage rate percentages. The effect is not necessarily limited to the corrected day.
This process does not create missing daily records or new summary rows. Deleting a single history row does not reset usability monitoring or clear all usage rate data. Changes to daily records affect the statistics and reports that use them. An Excel file downloaded earlier will not update; generate a new export if necessary.
Which schedule does recalculation use?
For each day, a schedule valid on that day is selected in the following order:
- A schedule assigned directly to the Spot.
- The schedule of the Spot’s own folder. The search does not extend to parent folders.
- An applicable schedule linked to the Spot’s schedule history.
- The service-wide schedule.
The start and end dates are included in the validity period. If there are several historical options, the one with the latest start date takes priority; ties are resolved by the more recent creation time and finally by the schedule identifier. If no applicable schedule is found, the existing daily record is left unprocessed.
A directly assigned schedule is therefore not required for recalculation. However, schedule history is not an unchanging copy of the original calculation settings: current assignments, validity periods, calculation modes, usage times and exceptions can affect results for past days. The current schedule name shown in the statistics alone does not prove which schedule was used to calculate a past day.
For instructions on setting a schedule, see How do I define a Spot’s usage schedule?
How does status history change the calculated hours?
The day’s starting status
In both calculation modes, the day’s starting status is primarily taken from the status after the latest event before that day. This also applies to days with no status changes.
If there is no preceding event but the day has events, the starting status is assumed to be Active. If the day has no events and there is no preceding event, the starting status of the first event in the entire history is used. Only if that is also unavailable is the Spot’s current status used. The day’s events then change the status used in the calculation from their respective times onwards.
Time-based schedule
The day’s target hours come from the usage periods for that weekday after exceptions have been applied. If the schedule is divided into weeks, the calculation uses the week definition for the calendar week and its own exceptions. All exception periods applicable to the day are removed from the usage periods; overlapping time is not deducted twice.
The calculation treats each period spent in Inactive or Faulty status as an absence. Consecutive changes between these statuses are also processed. Only the overlap between an absence and a scheduled usage period is deducted from the target hours, up to the number of hours in that usage period. Absences outside the schedule do not reduce hours in use.
Disabled is not an absence status deducted by this calculation mode. Time spent in this status within the schedule may therefore remain in the calculated hours in use. A historical disabling does not automatically reduce the result to zero.
Example: on a normal day, the usage schedule is 08:00–16:00 with no exceptions. The Spot is Inactive from 06:00 to 10:00 and Active after that. Only 08:00–10:00, or 2 hours, is deducted as an absence. Hours in use is 6, Desired in use is 8, and the usage rate is 6 ÷ 8 × 100 = 75%.
Daily hours schedule
The day’s target is the number of hours defined for that weekday. The number of hours between the start and end times of the first applicable exception is deducted from the target, down to a minimum of zero. Multiple applicable exceptions are not added together.
When the target is positive, hours in use accrue only from time spent in Active status over the entire day, up to 24 hours. Inactive, Faulty and Disabled statuses do not accrue these hours. The exception’s times change the target, not the period over which active time is counted. If the target is zero, the day’s hours in use and usage rate are also saved as zero.
Daily percentage and period summary
The daily usage rate is hours in use ÷ target hours × 100. With a zero target, the result is 0%. In the Daily hours schedule model, the daily percentage is capped at 100%, but active hours can exceed the target.
The weekly, monthly and yearly summaries are calculated from the existing daily records for the calendar period: total hours in use ÷ total target hours × 100. This is not an average of the daily percentages. These summaries have no 100% cap; with a zero target, the result is 0%. For example, if the only day in a week with a positive target has a target of 8 hours and 20 hours of active time, the daily percentage is 100%, but the weekly summary is 250%.
The selected date range in the Statistics table is a different view from a calendar period summary. The table’s percentage is calculated from the totals of the daily hours within the selected date range. When the Spot’s current directly assigned schedule uses the Daily hours schedule model, the table’s usage rate is capped at 100%. This table cap does not apply when the daily hours schedule is only inherited. The daily percentage, calendar summary and table percentage based on the same data may therefore differ.
This article covers Usage-%. For an explanation of the separate Uptime % metric and the table’s other values, see How do I view a Spot’s usage rate?
Check the saved result
- Close the Spot’s history and reopen Full history events. Check the time, status, reason and user, as well as both neighbouring events. After a deletion, also check whether another row was deleted.
- Check the Spot’s details to ensure that its current status is still correct. A history correction does not update it.
- If the correction triggers usage rate recalculation, allow time for background processing and reopen the Statistics tab in the same Usability monitoring view.
- Open Full history of usage rates from the Spot’s row. Check that a daily record exists for the day being corrected, and compare its Hours in use, Desired in use and Usage-% values with the corrected status history and the schedule selected for that day.
- Compare statistics and reports for the same date range and, if necessary, the summaries for the corresponding completed calendar week, month or year. Generate a new export by following How do I check usability monitoring history and export the data to Excel?
Active periods, as well as period hours and absence deductions in time-based calculations, are rounded to four decimal places. Calculated daily and summary percentages are also rounded to four decimal places. Hour and percentage values in daily records are displayed to two decimal places; hover over a cell to see the more precise value. A small change may therefore be hidden by display rounding.
A saved history row confirms the history correction, but does not by itself confirm that background recalculation has finished. If the results remain inconsistent, work with support to check the Spot’s schedule, the corrected status sequence, the existing daily records and the comparison period before using the results in reporting.