This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
android:truck:truck_stories [2014/12/17 02:06] mikeclapp |
android:truck:truck_stories [2014/12/19 20:43] (current) mikeclapp [Story 1] |
||
---|---|---|---|
Line 15: | Line 15: | ||
- | Story 1 | + | ===== Story 1 ===== |
+ | |||
+ | |||
+ | * The Foreman hands out trackers (in mag boxes or otherwise) to each truck at the beginning of the day and work begins. | ||
+ | * The trucks begin running. An excavator loads them and they leave the site and take the material away to be dumped. (It could be being brought in for paving or base material too). | ||
+ | * The Foreman sees that the line of trucks is diminishing and brings up our app that shows the list of trackers and the distance they are from the job site. The distance and average speed creates an ETA. (Note: We can provide a lot more information if the Foreman creates a load zone polygon. Trucks within the load zone should not display ETA) A map of truck locations might make a lot of sense here too as well as a dashboard of efficiency. | ||
+ | * As the day progresses there's more that we can derive like a street map/USGS that encompasses the truck bounding boxes as a supplement. | ||
+ | |||
+ | |||
+ | ==== Screens and Function ==== | ||
+ | |||
+ | As I imagine it these are the screens we'll need to present information and manage trackers/projects | ||
+ | |||
+ | === Dashboard === | ||
+ | This is the main screen presenting a summary of the action and a quick way to check job state. Information I can imagine showing here is: | ||
+ | |||
+ | * Loads/Cycles - Determined by entering a load zone | ||
+ | * Average Cycle - The average of a roundtrip for all machines being tracked | ||
+ | * Average Load Time - How much time does each truck spend in the loading zone | ||
+ | * Load Ratio - The Average Load time/Average Cycle | ||
+ | * ETA - the ETA of trucks not in the load zone based on distance from job site (do we need a dump zone?). Trucks after they've left the dump zone based on avg speed and distance from job site/current location (do we allow this to be switched from current location to dump zone? They are different.) | ||
+ | * Tracker/Truck List - Order by ETA - display productivity/individual numbers/Drill down for more/Location | ||
+ | * More | ||
+ | |||
+ | === Tracker Control === | ||
+ | |||
+ | This screen allows for naming, setting projects, and potentially a way to dig deeper on performance. Naming needs to be very flexible due to the changing nature of trucks. We should think very carefully about ways we can minimize/simplify this area as both a place where mistakes can be made and lessening/smoothing the amount of work required by the foreman. License Plate/ Number/ TripTicket picture? for ID instead of name? | ||
+ | |||
+ | |||
+ | === Plan/Location Screen === | ||
+ | |||
+ | This shows us where trackers are located, paths taken, and is used to designate Load and Haul areas. It doesn't require a background ADF/KMZ/Openstreets/USGS but those would provide scale that would be helpful. | ||
+ | |||
+ | |||
+ | === Reports? === | ||
+ | |||
+ | End of day/midday reporting function. Output the kmz? | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
- | The foreman hands out trackers (in mag boxes or otherwise) to each truck at the beginning of the day and work begins. | ||