When you first create a job in the Skedulo web app, you can apply time constraints to it–so they become tied to that job. They indicate to the scheduler that the job must (or should if possible) be scheduled within the dates and times set.
Definitions of Time Constraints
In its rawest form, a time constraint is just metadata in a record, connected to a job that specifies either a single time, or multiple times in which a job can, and should be (preferably) scheduled. It always contains three fields: start before, start after, and end before. You could use any, or all three fields to create a time constraint.
An SLA is different. It's a very rigorous form of time constraint. In business terms, and from a terminology point of view, it is as the acronym suggests–a service level agreement. It usually references a starting time for the job and has a specific interval in which it must be completed, i.e., from the time you hear about the job, it needs to be scheduled within one, five, or ten hours to fulfill your contractual obligations, and meet your customers' expectations.
A timeslot is a variation of a time constraint. It has nothing to do with an SLA, or your ability to respond to a customer. It is more about constraining the time in which an appointment can be scheduled based on a booking window or time slot, e.g., a booking grid with several windows of time, showing you can book an appointment many times over within a specific window. Unlike an SLA, it has a certain elasticity to it, i.e., a one-hour assignment can be completed at any point within any four-hour block of time, it doesn't have to be completed at a specified time.
Types of Time Constraint
In Skedulo, there are two types of job time constraints:
- SLA–this is a hard constraint, i.e., it must be done on this date/time. It is detailed and not flexible. The "Vehicle Route Planning (VRP)" and "Suggest" features must meet these criteria.
- Timeslot–this is a soft constraint, i.e., it would be nice to meet these criteria. It has some flexibility–a time window of sorts.
Salesforce Object Manager: Job > Related Details > Job Time Constraints
Applied Time Constraints
Time Constraints in Job Details View
Once time constraints have been specified and saved, they cannot be changed. They become read-only, viewable in the job details view.
Note: Even though a time constraint cannot be changed ("VRP" and "Suggest" honor this hard constraint), once the job has been placed in the swimlane it can be manipulated by the scheduler.
In the swimlanes, the time constraint is represented in the following way:
- Diagonal hashed lines represent blocks of resource availability that should not be used to schedule the constrained job.
- Start after time is a single thin black vertical line.
- Start before is a single thin black line with arrows indicating the job should start before the line. Note: When a start time conflicts with a constraint, this line will turn red (see Figure 1).
- End before time is a single black vertical line.
Figure 1. A job in job details view, with time constraints set. Note there is a start time conflict indicated by a red line with arrows in the swimlane.
Figure 2. A job with time constraints, ready to be scheduled in job details view. Note the swimlane scheduling restriction indicators.
Time Constraints in the Scheduling Console
To identify whether a job has a time constraint applied, in the scheduling console, look at the job cards in the job list panel. If a job card has underlined times, hover over them using your mouse to see the SLA details.
Figure 3. A job in the scheduling console, with time constraints, highlighted.