android:jobsite:jobsitestories
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
android:jobsite:jobsitestories [2014/03/17 18:13] mjallison [Story Flow] |
android:jobsite:jobsitestories [2014/04/01 23:44] (current) mjallison [Machine Configuration] |
||
|---|---|---|---|
| Line 56: | Line 56: | ||
| === Warning Area entry === | === Warning Area entry === | ||
| - | Warning areas are a new idea. The thought is a method for letting site management designate visible locations where the operator should take extra care not to hit something. It may be powerlines, existing manholes, survey control. (TBD) | + | Warning areas are a new idea. The thought is a method for letting site management designate visible locations where the operator should take extra care not to hit something. It may be powerlines, existing manholes, survey control. |
| + | |||
| + | **Warning Entry Interface** | ||
| + | |||
| + | - Tap the warning area icon. It goes into a down state button. | ||
| + | - Tap the screen for the center of the warning area. A marker appears and displays a transparent red colored circle that's 10 foot diameter by default (this diameter seems an optimal minimum since it's right at autonomous accuracy). The circle can then be dragged out to the desired diameter. (is there a place to display the radius while dragging?). | ||
| + | - Pressing the warning area icon closes the warning entry. | ||
| + | |||
| + | ** Deleting Warning Areas ** | ||
| + | |||
| + | Up for suggestions on this one. Maybe toggle on warning area entry and then press and hold over an area and ask for deletion confirmation. | ||
| + | |||
| + | |||
| + | |||
| Line 91: | Line 104: | ||
| * | * | ||
| + | {{:android:jobsite:machinesettings.png?300|}} {{:android:jobsite:machineedit.png?300|}} | ||
| - | + | ==== Machine Configuration ==== | |
| - | === Machine Configuration === | + | |
| Load from Server, Color, Name, Yards, Clear settings, Customize Settings | Load from Server, Color, Name, Yards, Clear settings, Customize Settings | ||
| + | |||
| + | === Default Machine Colors === | ||
| + | |||
| + | This is a pass at default colors by machine type. The user can set them however he likes. We may experiment later with applying patterns to the tracks as a method of differentiation and by using transparency on the background. For some colors it's not possible to find 10 discrete colors so I've tried to use the colors that do with the most likely equipment types. | ||
| + | |||
| + | | Scraper | Green | #00BF00 | #00DF00 | #009F00 |#00FF00 | #80FF80 | #BFFFBF | #006000 | #DFFFDF | #004000 | | ||
| + | | Truck | Red | #FFBFFF | #FF9595 | #FF6A6A | #FF4A4A | #FF0000 | #D50000 | #B50000 | # 950000 | #6A0000 | #4A0000 | | ||
| + | | Blade | Yellow | #FFFF95 | #FFFF00 | #D5D500 |#B5B500 | #959500 | #757500 | #555500 | #353500 | | | ||
| + | | Paver | Gray | #E9E9E9 | #D4D4D4 | #BFBFBF |#A4A4A4 | #949494 | #7F7F7F | #5F5F5F | #4A4A4A | #252525 | #000000 | | ||
| + | | Dozer | Purple | #E6D5FF | #CCAAFF | #AC75FF |#8C40FF | #6600FF | #4800B5 | #330080 | | | | ||
| + | | Excavator | Blue | #D6EAFE | #ABD5FE | #76BAFE |#7976FE | #4040FF | #0000FF | #0000BF | #00006A | | | ||
| + | |||
| + | |||
| + | |||
| + | ==== Menus ==== | ||
| + | |||
| + | |||
| + | === Main Screen === | ||
| + | |||
| + | The main screen menu items should be | ||
| + | |||
| + | * File | ||
| + | * Settings | ||
| + | * View | ||
| + | |||
| + | Access Uploader should move to a button on Settings-About | ||
| + | |||
| + | |||
| + | |||
| + | |||
| ==== Story Flow ==== | ==== Story Flow ==== | ||
| Line 136: | Line 179: | ||
| - The user can change and desired items ans when he goes to the machine screen, any machines set by this configuration previously are automatically selected but can be overridden by the user. | - The user can change and desired items ans when he goes to the machine screen, any machines set by this configuration previously are automatically selected but can be overridden by the user. | ||
| - The changes can then be pushed to any designated machines. | - The changes can then be pushed to any designated machines. | ||
| + | |||
| + | ==== Trackers vs. Machines ==== | ||
| + | |||
| + | The key to making Job Manager work is associating individual trackers with machines. That said, we can't even depend on that. At worst, we have the equivalent of a G-Ray tracker with no machine association and at best we have a correctly associated tracker to machine where the operator has a perfect, full configuration. | ||
| + | |||
| + | === Methods of Association === | ||
| + | |||
| + | **No Association** | ||
| + | This should mostly be a first setup problem or for the chronically lazy. The tracker has a valid login to get into SmartTrack but bypasses any assignment of a machine. We still need to collect tracks but we don't know what project it's in because there's no job file. | ||
| + | |||
| + | |||
| + | **Picked or Scanned from SmartTrack** | ||
| + | The first opportunity for a new tracker to be in the system is at startup. The user needs to be able to | ||
| + | |||
| + | * Pick from a list of known machines | ||
| + | * Create a new machine (if allowed as company policy) | ||
| + | * Cancel and just be an unassociated tracker. In this case we would need to create something like an unknown machine. This implies that having just a name for a machine and no other information is ok. | ||
| + | |||
| + | |||
| + | Note: This graphic is for SmartTrack but is included here for reference. | ||
| + | |||
| + | {{:android:jobsite:startupmachineselection.png?300|}} | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | **Picked from Jobsite Manager** | ||
android/jobsite/jobsitestories.1395079998.txt.gz · Last modified: 2014/03/17 18:13 by mjallison
Page Tools
