Time On Site

Created by Kenneth Abad, Modified on Tue, 26 Aug at 10:52 AM by Kenneth Abad

A higher score with the Time On Site metric shows that a vendor is able to resolve issues quickly, and are not spending more time onsite than the average work order.


A low score shows that a vendor spends more time making repairs onsite compared to other work orders with similar trades and priority.


Purpose / Metric Definition:

Measures how much time a vendor spends on-site compared to the expected average duration. The score reflects efficiency by comparing actual time against the standard time for similar Purchase Orders, using standard deviation as a benchmark.

Category:

Performance

Logic / Formula:

CASE
    WHEN POHoursOnSite IS NULL THEN NULL
    WHEN (POHoursOnSite - StandardHoursOnSite) >= 2 * STDEVHoursOnSite THEN 0
    WHEN (POHoursOnSite - StandardHoursOnSite) >= 1 * STDEVHoursOnSite THEN 0.2
    WHEN (POHoursOnSite - StandardHoursOnSite) >= 0.5 * STDEVHoursOnSite THEN 0.4
    WHEN (POHoursOnSite - StandardHoursOnSite) >= 0.25 * STDEVHoursOnSite THEN 0.6
    WHEN (POHoursOnSite - StandardHoursOnSite) >= 0 THEN 0.8
    WHEN (POHoursOnSite - StandardHoursOnSite) >= -0.075 * STDEVHoursOnSite THEN 0.8
    ELSE 1.0
END AS Performance_HoursOnSite

Scoring Rules:

  • 100% → Vendor time is well below expected duration (more efficient than -0.075 STDEV)

  • 80% → Vendor time is near expected duration (between -0.075 and 0 STDEV)

  • 60% → Minor overage (between 0.25 and 0.5 STDEV)

  • 40% → Noticeably over expected time (between 0.5 and 1 STDEV)

  • 20% → Substantially over expected time (between 1 and 2 STDEV)

  • 0% → Far past expected duration (≥ 2 STDEV)

  • Not Scored (NULL) → PO never entered 'On-Site' status

Notes / Exceptions (optional):

Uses Umbrava averages for Trade and Priority Category to determine expected time.


Links to Dashboards/Reports that use this metric:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article