SPM Scheduling Technician Utilization
SPM Scheduling Technician Utilization records are created from Scheduling Event Summary records associated with the selected / latest Schedule Optimization job(s).
One SPM Scheduling Technician Utilization record is created per technician per day for a specific job run, with JobId, Technician, and Horizon Date fields as the composite primary key, and the mapping is done as follows:
Target Field
Value Derived From
Available Time
Holds the available time of the technician, which is calculated based on the metric configuration, as explained in Settings section.
Break Minutes
Technician’s break time as configured in Technician > Break Hours. If technician Break Hours are not present, this sequence is considered.
Dispatch Process Id
JobId > SVMX Process > Process Number
Dispatch Process Name
JobId > SVMX Process > Name
Drive Time
Sum of technicians’ drive time including the before and after drive time.
Idle Time
Available Time - (Productive + Non-Productive Time)
Job Execution Start Time
ServiceMax Job > Start Time
Non Productive Time Value
Sum of durations of events which are not configured as Productive Hours event types.
Non Work Order Events Time
Sum of non-work order events duration, per job per technician for a horizon date.
Overhead Time
Holds the overhead time of the technician, which is the duration of the event before and after the service duration.
Productive Time
Holds the productive time of the technician, which is calculated based on the metric configuration, as explained in Settings section.
Service Team
Technician > Service Team
Service Time
Sum of work order events service duration, per job per technician for a horizon date.
SPM Schedule Tech Utilization Constraints
SPM Schedule Tech Utilization Constraints > Name
Territory
JobId > Territory > Name
Utilization %
(Productive Time / Available Time) * 100
Working Minutes
Technician’s working time as configured in Technician > Working Hours.
If technician Working Hours are not present, this sequence is considered.
After a target record is created, there are no overrides and no re-examination. This means that if a target record exists for a job already, it is not updated and that job is not processed again.
See Also:
Was this helpful?