Options for Resource Schedule Location Profile used in Work Assignment Logic
In 24C, a new Location Profile was added to the Resource Schedule and Resource Schedule Instance where the starting and ending locations can happen at any location in the profile without creating a leg segment back to the single location that was available in the previous version.
In 25A, new options were added to provide rules to more specifically define how those location profiles may be used. Most common is to get the driver back to the starting location where presumably the personal transportation is parked.
Start and End Options by Resource Schedule
Enter a START NFR LOCATION OPTION and an END NFR LOCATION OPTION. The START NFR LOCATION OPTION has three values.
- Start Location: If first location on the first shipment is not in the location profile then the start location from RS is used as NFR by default unless the start location from RSI is the same location as first location on first shipment.
- Nearest Profile Location: If the first location on the first shipment is not in the location profile then choose the nearest location from the location profile from the RSI.
- Do Not Add NFR: Do not add an NFR stop even when first location on first shipment is not in the location profile.
Similarly, you can choose any of four values from END NFR LOCATION OPTION.
- End Location: If last location on last shipment is not in the location profile then the end location from Resource Schedule Instance is used as NFR by default unless the end location from RSI is the same location as last location on last shipment.
- Nearest Profile Location: If the last location on the last shipment is not in the location profile then choose nearest location from the location profile from the RSI.
- Same As First Shipment Start: Use the start location from the first shipment (could be an NFR that was just added with above logic) as the NFR location for the end of the last shipment.
- Do Not Add NFR: Do not add an NFR stop even when the last location on last shipment is not in the location profile.
Resource Schedule Instance showing Options
Typically, the Location Profile is added when modeling a carrier that might be a house carrier for a shipper and that can work out of multiple locations. On the other hand, a casual carrier with no affiliation might not have the Location Profile and just have start and end locations to model a domicile.
Orders for Example
Resource Schedule Options for Testing
This scenario returns to the End Location, Aurora, because it is not end at a facility in the profile. Likewise, it started at Holland because that facility was in the profile. This option represents "current behavior".
Scenario 1
Scenario 2
Scenario 3
Scenario 4
This enhancement allows the clients to utilize the Location Profiles on the Resource Schedule and Instance in new ways. Originally the Location Profiles were added to allow Work Assignment to begin and end at any company location in the location profile if there was a profile. If no profile, the beginning at end was at the singular locations. The new options allow greater ability to model driver behavior for different types of carriers. or. For example, the driver may leave an auto at the start of a Work Assignment and would desire to return there at the end. Carriers may have a garage or yard nearby where their drivers start and end and these would opt to not have a profile. Contract carriers, used to fill out shipments that the house carrier will not get may prefer to simply end at the destination where their other work will start. Finally, a company may prefer that their driver return to the closest company location. All of these options can be modeled by the individual resource so that a plan may be run with different types of carriers.
Steps to Enable
The Resource Schedule Must be configured, else the default option will be used.
Tips And Considerations
Company carriers or "house carriers" will likely have profiles. Outside or "contract carriers" will most likely NOT have profiles. One needs to be careful about this and not assume that all carriers are modeled the same.