Purpose

The Data Entry Performance report can be used by supervisors to evaluate the accuracy of the data collection process by operators.

Three widgets are present at the top of the data entry report to display the total data entry score, unjustified major events, and total major events of the facility in the report period. The numbers displayed are collective of all selected assets in the report.

For each production line, a performance value for data entry is present at every point in the selected time period. The data is shown in a heat map as shown below. Cells in gray indicate that no downtimes have been recorded at that specific date/time. 

How to use it

From the Data Entry Performance page:

1. Select a facility and a date range

2. Click on "Generate"

3. Use additional filtering options to view the results for specific production lines

View unjustified events in specific period

For every cell that do not have a 100% performance value, the user can click on it to display all events that have not been justified by the user for an asset in that specific time period.   

How Data Entry Performance is calculated

Data entry performance is calculated as:

Data Entry Score = (Number of justified major downtime events) / (Total number of major downtime events)

As an example, let's consider the list of downtime events in the table below:

If we generate a data entry performance report in hourly resolution, then:

• The line experienced three events starting between 10 am and 11 am: two major events and a minor one. The minor event is ignored as justification is not required for this kind of event. Of the two major events, one was justified, while the other one does not have a cause. As a result, the data entry performance between 10 am and 11 am is 50% (1 justified major event / 2 major events)
• We have two major events starting between 11 am and 12 pm. They both have a cause, so during this time the data entry performance is 100%.

Note that in the table above, event 3 starts between 10 am and 11 am but last beyond 11 am. By convention, we'll consider that this event impacts the score between 10 am and 11 am, and not after. This is done to avoid double accounting, events are categorized by when they start.