Differences

This shows you the differences between two versions of the page.

--- android:jobsite:jobsitestories [2014/02/26 01:06]
mjallison [Story Flow]
+++ android:jobsite:jobsitestories [2014/04/01 23:44] (current)
mjallison [Machine Configuration]
@@ Line 56: / Line 56: @@
 === 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
-==== Story Flow ====
+=== Default Machine Colors ===
-This the first use case we want to accommodate. This is very similar to what we'll need to do for Machine Control as well
+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.
-=== Example 1 - Setting up a new Project/Job ===
+| 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  |  |
-At the start of a new project, the project manager/engineer/superintendent needs to create a configuration package to be used on the job. My expectation is that the minimum he does is select the correct job file to work from and push it to the assigned machines. The configuration package can also include features like cycle lines, warning areas, suggested haul paths, and default screen views/options for Smarttrack and machine control. Note, we may wish the default screen views/options to be separate from the job features. I could see a company policy setting default views and options globally while the job portions are really specific to that particular site. Here's the steps from program start as I imagine them.
-**Question (mja):** I see 3 levels of hierarchy for settings; company, job (file), vehicle. Would it be correct to assume that settings not specified in a sub-level (e.g. vehicle) would be inherited from the super set (job, then company)?
-**Question (mja):** If settings are inherited from higher levels, is this inheritance dynamic (at the time of retrieval) or semi-static (at the time the jobsite user presses "save").
+==== Menus ====
-**Question (mja):** When superceding a set of directives (company/project-file/vehicle) does this override the directive file or does it simply replace. (I believe based on discussion in this page, it replaces it).
-**Question (mja):** When project files are deleted, directives will also be deleted if there are no more versions of the deleted project file. This is the only way to delete directives.
+=== Main Screen ===
+The main screen menu items should be
+  * File
+  * Settings
+  * View
+Access Uploader should move to a button on Settings-About
+==== Story Flow ====
+This the first use case we want to accommodate. This is very similar to what we'll need to do for Machine Control as well
+=== Example 1 - Setting up a new Project/Job ===
+At the start of a new project, the project manager/engineer/superintendent needs to create a configuration package to be used on the job. My expectation is that the minimum he does is select the correct job file to work from and push it to the assigned machines. The configuration package can also include features like cycle lines, warning areas, suggested haul paths, and default screen views/options for Smarttrack and machine control. Note, we may wish the default screen views/options to be separate from the job features. I could see a company policy setting default views and options globally while the job portions are really specific to that particular site. Here's the steps from program start as I imagine them.
 **Simplest configuration package**
@@ Line 140: / Line 175: @@
   - Load the new file and it loads.
   - A menu item called "Import Configuration" (?) exists and when pressed shows the file list window.
-  - Picking a file with configuration data reads that data and displays a checkbox list of the items it contains (cycle line, haul path, warning areas. It also contains what machines it has written to before but that doesn't need to show them on the list for selection.
+  - Picking a vehicle with configuration data reads that data and displays a checkbox list of the items it contains (cycle line, haul path, warning areas. It also contains what machines it has written to before but that doesn't need to show them on the list for selection.
   - Pressing Import brings the selected configurations into the new file.
   - 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.
+==== 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**
@@ Line 154: / Line 218: @@
 Statistics will be both graphical and numerical derived from server data. In fact it may make sense to make this a web view so it can easily used by any computer and tablet without an app.
+==== Possible Stats ====
+  * CY per hour
+  * Moving Minutes per Hour
+  * CY per day
+  * Cumulative (all machines
+  * Average Haul Path length
+  * Average cycle time

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools