SPM Schedule Technician Utilization Constraints

Analytics > Schedule Optimization Metrics > Technician Utilization > Metrics Calculation > SPM Schedule Technician Utilization Constraints

SPM Schedule Tech Utilization Constraints records are created from Scheduling Job Summary records associated with the selected / latest Schedule Optimization job(s).

One SPM Schedule Tech Utilization Constraints record is created per source record, with JobId field as the primary key, and the mapping is done as follows:

Target Field	Value Derived From
Dispatch Process Name	JobId > SVMX Process > Name Horizon End
Horizon End Date	Calculated based on JobId > SVMX Process > Planning Time Horizon configuration, as processed by the Schedule Optimization engine
Horizon Start Date	Calculated based on JobId > SVMX Process > Planning Time Horizon configuration, as processed by the Schedule Optimization engine
Overall Drive Time	Total drive time in all the schedules returned for the job by the Schedule Optimization engine
Overhead Time	Total overhead time in all the schedules returned for the job by the Schedule Optimization engine
Preferred Technician	Weight of selecting the preferred technician, as per JobId > SVMX Process configuration (Dispatch Process configuration)
Priority1	Description of P1 rule in JobId > SVMX Process (Dispatch Process configuration)
Priority2	Description of P2 Rule in JobId > SVMX Process (Dispatch Process configuration)
Priority3	Description of P3 Rule in JobId > SVMX Process (Dispatch Process configuration)
Priority4	Description of P4 Rule in JobId > SVMX Process (Dispatch Process configuration)
Processed Work Orders Count	Number of work orders that were scheduled by Schedule Optimization engine for the specific Schedule Optimization job run
Product Specialization	Weight of technician meeting required product specialization, as per JobId > SVMX Process configuration (Dispatch Process configuration).
Qualified Technician	Weight of finding the Qualified Technician for the service.
Skill Match	Weight of technician meeting the desired skill set, as per JobId > SVMX Process configuration (Dispatch Process configuration)
SLA (Weights)	Weight of technician meeting work order SLA, as per JobId > SVMX Process configuration (Dispatch Process configuration)
Submitted Work Orders Count	The number of work orders sent for scheduling to Schedule Optimization engine for a job run
Technician Eligibility	Weight of finding eligible technician for the service
Technicians Count	The number of technicians identified for scheduling and sent to Schedule Optimization engine for a job run
Total Events Count	The number of existing technician events sent to Schedule Optimization engine for a job run
Travel Cost	Weight of total travel cost incurred by the technician, as per JobId > SVMX Process configuration (Dispatch Process configuration)
Utilization %	(Utilization Sum / Utilization Count)
Utilization Count	Count of (roll up) of the SPM Scheduling Technician Utilization, per Schedule Optimization job.
Utilization Sum	Sum of (roll up) of the SPM Scheduling Technician Utilization > Utilization %, per Schedule Optimization job

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.