Average and Percentage Run Time Difference for Microsoft Dynamics 365 Business Central
Knowing that an operation runs long is not enough to fix a routing; an engineer needs to know by how much per unit, and whether the gap is large compared with the standard. Routing Analysis reports the average actual run time per unit for each operation in Business Central, then its difference from the routing's run time, in hours and as a percentage.
An explanation of how the difference was calculated is available for the selected line.
How Average and percentage run time difference works in Routing Analysis
- Open Routing Analysis and choose the routing and date range.
- Choose Generate.
- Read the average actual time per unit, the average actual difference, and the percentage difference for each operation.
- Open the explanation for a line to see how its difference was calculated.
- Decide whether the standard needs correcting or the operation needs attention on the floor.
Key capabilities
Per unit, in hours
The average actual time is expressed in hours per unit of base quantity, so operations recorded in different time units compare on the same footing.
The size of the gap
Avg. Actual Difference shows the gap between the average actual run time per unit and the routing's run time per unit, as an absolute value.
The gap in proportion
% Difference expresses the gap as a percentage of the routing's run time, so a small gap on a short operation is not overlooked.
Explained on request
A message for the selected line walks through how the average actual difference was calculated from the total recorded run time and the total finished quantity.
Feeds the filters
Variance Threshold Filters use the average variance to hide operations whose gap is too small to act on.
See Average and percentage run time difference on screen
Real screens from Routing Analysis, shown with demo data.
Details that matter on the floor
The calculation is visible
Because the steps are shown for each line, an engineer can check the inputs, recorded run time and finished quantity, before changing a standard.
A percentage puts gaps in context
A tenth of an hour matters more on an operation that should take a quarter of an hour than on one that should take twenty hours. The percentage column makes that visible at a glance.
Who uses Average and percentage run time difference
Manufacturing engineers
Size the gap between recorded and expected times before deciding on a correction.
Cost accountants
See how far run times sit from the standards that costing uses.
Production managers
Identify operations that consistently take longer or shorter than planned.
Questions about Average and percentage run time difference
How does Routing Analysis measure the gap between actual and expected run time?
Routing Analysis calculates the average actual run time per unit for each operation, then reports the difference from the routing's run time in hours and as a percentage of it.
Can I see how a difference was calculated?
Yes. Routing Analysis shows a message for the selected line that explains the calculation, from the total recorded run time and the total finished quantity.
Why show a percentage as well as the time difference?
The percentage relates the gap to the size of the standard, which helps you compare short and long operations fairly.
Related Routing Analysis features
All Routing Analysis features →Part of Routing Analysis
Optimize production with routing analysis to reduce variability and enhance costing accuracy.
Have a question about Average and percentage run time difference?
Send us a note and the Routing Analysis team will reply by email. Ready to plan a rollout? Contact your Microsoft Partner.
