Today we do not have something like that. However…
I normally don’t talk publicly about futures but since this is already in the oven and actively baking (so close to delivery) I’ll share our thinking/plan.
I wanted to be able to focus on work cycles from a source to a destination location - especially real time monitoring see daily/weekly summaries.
Another focus is what I call “bunchups”. I wanted to know 1) how often trucks are bunched together waiting to be loaded or waiting a turn to dump. This could be construction-focused like a single excavator(s) or frontend loader(s) with trucks waiting and you need more load capacity. You set your concurrent load/dump capacity and we monitor when that’s not enough. Occasionally is good but long/constant waits is bad.
So we are creating “Work cycle” definitions for you to monitor a given cycle and see it now, see it by day or see it by week-over-week should it be a long project.
Below is the first internal effort to verify our process/concept. With that confidence, the we created a development spec for all the enhancements which are now actively being developed (I think next month is realistic).
To give you a taste, page 1 is our first draft, page 2 is a developer mockup for the Weekly overview and page 3 is daily view (and if the day is “Today” is has real time truck positioning at/between the locations).
To be frank, no one has asked for this but we think it is very useful for many source/destination “work cycle” tasks - especially time critical tasks where the destination is wondering if they have any loads coming, any awaiting around the corner or too many incoming and need to throttle back loading.
I would really value your feedback and where we’ve hit the mark or have gaps!
