11/22/2024 10:51:44 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum for off topic and general discussion. View the code of conduct for posting guidelines.
|
|
|
|
Technician Dispatch
Posted: 10 Jan 07 2:54 PM
|
fiogf49gjkf0d Is anyone aware of an application that manages dispatch and scheduling for service technicians? (and integrates with SLX, of course) We service machines all over the world, and we currently use ticket activities to alert technicians of pending service calls. While this does do the job, I can't help but feel there might be a better way to do this. It could be that I'm serching for a solution to a problem that doesn't exist, but if anyone would be willing to share their methods for assigning, scheduling and tracking techinician service calls in SLX - it would be greatly appreciated. We are gearing up for v7, and there may be added functionality in there that could fit the bill.
Thanks! |
|
|
|
Re: Technician Dispatch
Posted: 10 Jan 07 4:38 PM
|
fiogf49gjkf0d I would think such a thing exists already but perhaps it doesn't for a reason.
How would you go about alerting technicians of their dispatches? Do they login to view tickets? Are tickets assigned to managers that print them out, email them, or whatever? The biggest peice of the puzzle in my mind is getting the information to the tech and it seems wasteful to give them a full SLX license when they use probably 10% (or less) of the overall application. The rest of it really is just data and how you manage it. Tickets are a nice fit and should be used for the general support information. As far as the actual dispatching goes, that could be a custom table off tickets or a completely separate entity but ticket activities can also work.
There are also different levels of dispatch. For instance, my friend worked for an auto glass repair shop and he'd get work orders at the beginning of the day then plan his route before starting. He'd then turn in the work he did at night but I have no clue how the backend works from that point. You may have a service that works primarily in-house so that dispatches are actual dispatches, where the technician comes in and leaves multiple times during the day. Obviously the latter is easier to track since the technician actually comes to the office (in a perfect world of course, some people don't keep up with paper work but that's another topic).
From my limited knowledge of the subject, it does appear that you can automate a lot of it. Since most of SLX is manual, that is probably where a lot of the customization will come in. |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|