Spot utilization on report pages shows a percentage based on the usage schedule and the Spot's status history. Machine Hours shows the recorded total reading from the device's hour meter. Neither represents a person's working time entries. A calculated utilization rate also does not prove that the device's physical meter has advanced.
Requirements and opening the report
From the browser's main menu, open Dashboard → Report pages and select a report page using the selector at the top of the page. The report data is limited to Spots for which you have read access. The same report can therefore show different results to different users.
Adding reports and permanently saving settings requires administrator rights. To add a report, select Add new report at the top of the page, find Spot utilization or Machine Hours, and drag the report onto the page. Configure the required options and save the new report using Save the page. If needed, see adding and arranging a report.
Utilization requires a valid usage schedule and calculated historical data. The Spot selector in the Machine Hours report offers devices for which Hourly maintenance in use is selected. Enabling the feature alone does not guarantee that readings have been recorded for the selected period.
Select the time period and items
Above the chart, Tme period for the data selects the period covered by the data. Time grouping for data selects the period for each point: Per day, Per week, or Per month. Both reports default to monthly grouping and the current and previous calendar years.
Year view does not allow daily grouping. If you need daily results, first change the period to a date range, for example. For utilization, grouping changes which precomputed percentage is used; for machine hours, it changes the period from which the last reading is retrieved. The report's time filter uses the user's time zone, which defaults to Helsinki. Daily utilization calculations use the service's time zone. For more details on time selections, see report time periods and filters.
Open Settings from the report's title bar. All filters in the panel that opens on the right contains the item filters. You can filter utilization by folder, Spot, customer, and Spot attributes. The folder filter also includes Spots in subfolders. For machine hours, the Spot selection is mandatory: select the devices to compare before viewing the result.
An administrator can save changes to an existing report using Save Settings in the title bar, which appears while the settings are open. Other users can change the view but cannot save the report settings permanently. Reload the report page and check that the desired filters have been retained. Saving retains the report configuration, not the current figures as fixed values.
How is utilization calculated?
The daily calculation uses the schedule valid on that day in this order: the Spot's own schedule, its direct folder's schedule, and finally the service-wide schedule. The search does not continue to schedules in higher-level folders. If there is no applicable schedule, no utilization data is produced for that day.
The schedule's validity, the day of the week, any division into even and odd calendar weeks, and exception times affect the target. When weeks are divided this way, the selected week's own exceptions are used. For instructions on configuring the settings, see setting a usage schedule.
Daily hours
The daily target is the number of hours set for the day of the week, minus the hours between the start and end times of the first exception that applies to that day, down to a minimum of zero. Multiple applicable exceptions are not added together. An exception can apply to a given day or date range, or recur monthly or annually. The exception's times reduce the target; they do not limit the calculation of active time.
Used hours accumulate from time spent in the Active status throughout the day, up to 24 hours. On Android and iOS, the same status is called In Use. The Inactive, Faulty, and Disabled statuses do not accumulate active hours under this calculation method.
The daily percentage is active hours ÷ target hours × 100, capped at 100%. If the target is 8 hours and 12 active hours accumulate, the daily record has 12 used hours but a daily percentage of 100%. When the target is zero, the day's used hours and percentage are recorded as zero.
Time-based schedule
Target hours are based on the time intervals in the schedule. Exception times that apply to the day are removed from the operating intervals: they can shorten or split an interval, or remove it entirely. The time range of a multi-day exception is handled separately for each day it covers. Recurring exceptions are also taken into account. Overlapping time is counted only once.
The calculation subtracts time spent in the Inactive and Faulty statuses from target hours only where it falls within the remaining operating intervals. Consecutive periods in these statuses are also handled. Time outside the schedule in these statuses does not reduce used hours.
For example, an operating interval from 8:00 to 16:00 gives a target of 8 hours. If the Spot is Faulty from 7:00 to 10:00, the time from 8:00 to 10:00, or 2 hours, is subtracted from the operating interval. This leaves 6 used hours and a utilization rate of 6 ÷ 8 × 100 = 75%.
The percentage is remaining used hours ÷ target hours × 100. A zero target gives 0%. Disabled is not a status that is subtracted under this calculation method: time spent in it can remain as calculated operating time. Therefore, do not interpret this status as equivalent to Inactive or infer the device's actual meter usage from the percentage.
Time-based hours are calculated using actual elapsed time in the service's time zone. Daylight saving time changes can alter the number of hours in an interval. In spring, a nonexistent clock time is moved forward by the amount of the clock change; in autumn, the first occurrence of a repeated start time and the second occurrence of a repeated end time are used. If the end is still not later than the start, the interval's duration is zero. An interval ending at 23:59 is treated as extending to the end of the day. By contrast, the Daily hours model's target is a specified number of hours that is not lengthened or shortened by the clock change.
Where does the day's starting status come from?
In both calculation methods, the day's starting status is primarily taken from the status after the last status event before the day. This also applies to a day with no status changes.
If there is no earlier event but the day has events, the calculation assumes a starting status of Active. If there are no events on the day and no earlier event, the starting status of the first event in the history is used. Only if that is also unavailable is the Spot's current status used. The current status alone therefore generally does not indicate the status used to calculate a past day.
When are daily, weekly, and monthly results available?
The utilization report uses data calculated in advance in the background. Daily processing calculates the previous day according to the service's time zone. Weekly data covers Monday through Sunday and is created only when Sunday's data is processed. Monthly data is created when the last day of the month is processed. There is therefore no real-time percentage for an incomplete week or month using the corresponding grouping. Switch to daily grouping to view days that have already been calculated.
The weekly and monthly percentage is calculated as the sum of used hours in existing daily records ÷ the sum of target hours × 100. It is not a simple average of daily percentages. In the daily hours calculation method, active hours can exceed the target even though the daily percentage is capped at 100%. Weekly and monthly percentages are not capped in the same way, so they can exceed 100%. If the sum of target hours in the aggregate is zero, the percentage is 0.
The calculated percentage is rounded to four decimal places, and the value shown in the report to two decimal places. In the time-based daily calculation, the target and absence hours for an operating interval are also rounded to four decimal places.
The report's time filter applies to the date recorded for the utilization data: a daily record is marked with that day, and an aggregate record with the last day of the week or month. A partial date range does not recalculate a precomputed aggregate percentage for only the selected days.
Missing data is not the same as a calculated 0%. Normal daily processing does not automatically fill in earlier missing days. Saving a schedule does not by itself recalculate old results or create missing daily records either.
What does folder utilization mean?
In the settings panel, select By folder in the Grouping section. The report calculates the arithmetic mean of the included percentage records for the selected period type: the sum of the percentages is divided by the number of existing percentage records. Missing records do not increase the denominator, but a recorded 0% is included in the average. A new folder utilization rate is not calculated from the combined hour totals of all devices.
For example, utilization rates of 100% and 50% for two Spots in the same period give the folder 75.00%, even if the devices have different target hours.
The group is determined by the Spot's current direct folder. Including subfolders in the folder filter does not combine all results into one parent-folder group. Moving a Spot to another folder can therefore also change the folder grouping of historical data.
Without item filters or grouping, the utilization report shows a maximum of 50 Spots. These are not ordered by highest utilization. Applying a filter or grouping by folder removes this default limit.
What does Machine Hours show?
For each Spot, Machine Hours retrieves the last recorded reading for the selected day, week, or month based on the time it was recorded, and rounds it to two decimal places. It does not show the sum of readings, the highest reading, or usage accumulated during the period.
If 1,250 hours are recorded first and 1,268 hours later in the month, the report value is 1,268.00. It is not 18 hours. If there is no new history entry for a period, the previous period's reading is not copied into it. A missing point does not mean the meter reads zero hours.
Report settings → Chart type in the settings panel offers Bar, Line, and Spline. The display type does not change the rule for selecting readings. A line does not indicate that readings were recorded for the times between points. The Machine Hours report displays a quantity warning at 20 Spots; this warning threshold does not itself limit the data to 20 devices.
In both reports, Report settings → Show average value adds the average of the series values at each time point to the chart, rounded to two decimal places. The denominator is the number of numeric series values returned for that point; if the data contains an empty null value, it is included as zero. A series value that is entirely missing is not included. This differs from utilization for the whole period calculated from hour totals. For machine hours, it is the average of total readings, not average usage during the period. The option is off by default.
Why can history and reports change?
A changed meter reading adds an entry to the machine hours history when the hourly maintenance feature is enabled. Recording the same latest reading does not add a new history entry. A reading entered on a task affects the Spot's reading history when the task is completed only if it exceeds the Spot's current reading.
On Android and iOS, updating a Spot's Machine Hours saves to the same data and accepts only a value greater than the current one. In this guide, the report is viewed in a browser. For instructions on recording a normal reading, see updating an hour meter reading.
Resetting machine hours retains earlier reading history and can add a new, lower reading. If it is the last entry in the period, the report shows the corrected reading rather than the earlier highest reading for the period. Resetting can also remove incomplete hour-based maintenance tasks. Check the effects in the hourly maintenance feature and correcting a reading.
Correcting status history
When the time of a saved or deleted status event is at or before the start of today in the service's time zone, the change triggers a background recalculation of utilization data. Processing can change the calculated used hours, target hours, and percentages for existing days, as well as existing weekly, monthly, and yearly aggregates. The time groupings available on the report page are still day, week, and month. This correction does not create missing days or aggregates.
Recalculation does not require the Spot to have its own schedule. For each day, a valid schedule is sought in this order: the Spot's current direct schedule link, the current direct folder's schedule link, the Spot's schedule history, and finally the service-wide schedule. Among historical options, the one with the latest start date takes precedence. You cannot therefore assume that the schedule used in the original calculation will be retained. If no applicable schedule is found for a day, its previous daily record is left unchanged.
Correcting status history does not change the separate machine hours reading history. The correction steps are described in correcting a Spot's status history. After the correction, check the report result using the same filters.
Resetting usability monitoring
Resetting usability monitoring is different from correcting an individual status history event or resetting machine hours. It permanently deletes the Spot's earlier status history, schedule history, and saved utilization results. The current status and current schedule selections are retained. Machine hours reading history is not deleted.
Monitoring starts from the time of the reset, and new utilization results are not calculated for earlier days. On the reset day, only the portion of a time-based schedule after the reset is taken into account. The Daily hours model's target is reduced in proportion to the remainder of the day, and active time accumulates only after the reset. Removing old results also changes the report's folder averages. Resetting is not a way to correct a single incorrect percentage.
Verify the result
Check the report's time period, time grouping, time zone, and selected Spots. For utilization, open Assets and content → Assets, devices, tools → Usability monitoring from the main menu. Select the Statistics tab and then Full history of usage rates on the relevant Spot's row. Check that data has been created for the days you are viewing, and compare used hours and target hours with the schedule.
Check status events on the Event logs tab in the same view. The daily percentage, the period percentage calculated from hour totals, and the report's folder average are different metrics. The period utilization rate in the Statistics table is calculated from daily hour totals and capped at 100% only if the Spot's current directly linked schedule uses the Daily hours calculation method. If the schedule comes from a folder or the service-wide schedule, for example, the Statistics table result can exceed 100%. The report's weekly and monthly aggregates can also exceed 100%. For more background, see interpreting usability monitoring.
For machine hours, open the Assets, devices, tools page from the same menu and select its Datatable tab. Open the Spot using its name link. On the Basic info tab, find Running machine hours. Of the two icons to the right of the field label, the left one opens the reading history and the right one opens the chart. Find the last entry for the report period in the history.
If a result is missing, first check the recording time, read access, and, for utilization, whether a daily record exists. After a history correction, wait for background processing and reload the report page with the same time and item filters. A corrected status event alone does not yet show that the report's background data has been updated.