Skip to main content

We would like to use PSO Depots with FSM 6 to have technicians pick up parts for calls but don't know how or if this is even possible.

In the PSO Scheduling Concepts - Parts Functional Guide, there is the following blurb which says "Depots are a special type of Activity (with activity_class_id=DEPOT)" but it looks like the activity_class_id for Activities (aka: Tasks) is hard coded to "CALL" in the Metrix.Threesity.Integration dll. From what we see, when GenerateActiviyExportXml is called, it internally calls AddActivtyToXDoc which has the following line, hard coding the activity_class_id to “CALL”:

this.AddNodeAndValue(xDocIn, element, "activity_class_id", "CALL");)
 

If PSO Depots are truly Activities with an activity_class_id equalling “DEPOT”, can we use PSO Depots with FSM 6 or is there another way to have technicians directed to pick up parts by the system to be dynamically scheduled for a call?

 

PSO Scheduling Concepts - Parts Functional Guide - Page 6

Depots
Where there are lots of pick-up activities, or repeated ones, it is best to use a Depot. Depots allow parts to be collected as needed in order to perform later activities in the route. The Dynamic Scheduling Engine will collect just the number of parts required. Depots are a special type of Activity (with activity_class_id=DEPOT) and they can generate many visits: for*
*instance, there may be just one depot activity, but it may be used by several resources, and each of those may use it more than once.

 

Hi @ssabo 

The short answer is that you must customise FSM to use PSO depot functionality.

Cheers!


Hi @ssabo 

The short answer is that you must customise FSM to use PSO depot functionality.

Cheers!

Is there any documentation available for how it was intended to be used?


@ssabo 

Not sure what you mean.

This was never developed for FSM6, don’t think there was ever an intention for this to work with FSM6.

Cheers!


Reply