Differences

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

--- windows:trackwork:trackwork [2009/05/01 16:58]
mikeclapp
+++ windows:trackwork:trackwork [2014/10/03 17:05] (current)
mikeclapp [Trackwork Revamp 2014]
@@ Line 1: / Line 1: @@
-[[main|Main Page]]
+[[:start|Main Page]]
 ====== Trackwork ======
@@ Line 7: / Line 7: @@
 ===== Feature Requests (General) =====
+=== 2.06 ===
    - Timeline labeling: Having the track name displayed at the left side of the timeline window would make it much easier to correllate tracks to machines. The added colors help but don't really convey the message.
-   - Track Update: Rather than downloading the entire track each day, it would be nice if we could allow streaming updates (at a set interval (5 minutes if the trackers are set that way). One suggested interface is to add a "Track Update" command to the Edit window. Selecting displays the update rate in the text box and a checkbox enabling the updates.
+  - Setting a Work Day Clip window - This would be an easy way to clip all the tracks down to measure the paid hours. Using the warmup time in the morning messes up the minutes per hour calc. We could show it visually as a thin line in medium gray(?) to show that it turned on but that we aren't using it. Display the work day time range under the Haul, Grade, Transfer radio buttons of the Trackwork Analysis window.
-  - Change the download of server data to close the Import window and show the tracks drawing as they come in rather than waiting until they all come and then showing. I realize this could be major and probably affects the calculations done on the line. It might (probably) take longer to show an hour of each machine's data, then the next hour, etc. but the net effect for the user and the demo is a feeling of progress the bar at the bottom doesn't give. Right now, with a lot of data, the delay is painful as you do a soft-shoe waiting for it all to come in.
+  - Treat days as a Pane of information rather than scaling the data microscopically to fit. Right now we don't really have a good way to show multiple days on a job. Ideally, you could have all the job data present but move from day to day easily. JF suggestion was to allow two on the screen arranged vertically that you could scroll through.
-   - Speedometer - If you hit play and have 1 track highlighted it would report the speed below the time and date on the timeline as the track played through its cycles.  This would allow the customer to easily note the speeds during loading, spreading, hauling, return, uphill and downhill slopes.
+    * Placeholder for Idea. Implementation cost unknown. Set default colors in the vehicle association so the color is consistent for the vehicle no matter when it is shown.
+  - Simulator Export (Haul Planning) - Matthews and I started talking about a track simulator for sales demos, etc. What we'll need out of the haul planning part of Trackwork (GradeModel) is an export of the haul path line in lat-long, the specifications of speed, time, and distance as well as the haul path line broken into their distinctive segments. Perhaps a variation of KMZ since we're already writing out similar files that way? The simulator portion will take that information, create multiple offset tracks based on the user specs (day, # machines, time) and generate TMM like data to the server in the background.
+=== 2.06B ===
+  - Speedometer - If you hit play and have 1 track highlighted it would report the speed below the time and date on the timeline as the track played through its cycles.  This would allow the customer to easily note the speeds during loading, spreading, hauling, return, uphill and downhill slopes.
+  - Import Window Basic Revamp
+  * Increase size of tracks window
+  * Remove Google Earth window, controls, and calendar
+  * Add right click option on tracks - Show in Google Earth, writes temp KMZ file with just track and opens Google Earth to it.
+  * Allow creation of bounding box for project with the perimeter of an aligned (lat-long) job.
+  * PDF/PNG import as background for Tracks. This may be in there and specifically turned off. I believe Mark prototyped this with Earthwork 4D.
+=== 3.0 ===
    - No Data Concept - within a day we currently represent idle time and moving time. There needs to be a third state of no data within a day. The need for this is that if we have a gap in data within a day the idle time looks the same as no data. (note: edited to reflect new server behavior MC) Basic rules:
              * Must be some data within that day
@@ Line 18: / Line 37: @@
              * Don't show icons (circles) when the machine has no data. Tracks are probably ok.
              * anything else?
-   - Setting a Work Day Clip window - This would be an easy way to clip all the tracks down to measure the paid hours. Using the warmup time in the morning messes up the minutes per hour calc. We could show it visually as a thin line in medium gray(?) to show that it turned on but that we aren't using it.
+    - Allow creation of bounding box for project with the perimeter of an aligned (lat-long) job.
-  - Allow creation of bounding box for project with the perimeter of an aligned (lat-long) job.
+   - Track Update: Rather than downloading the entire track each day, it would be nice if we could allow streaming updates (at a set interval (5 minutes if the trackers are set that way). One suggested interface is to add a "Track Update" command to the Edit window. Selecting displays the update rate in the text box and a checkbox enabling the updates.
-  - Treat days as a Pane of information rather than scaling the data microscopically to fit. Right now we don't really have a good way to show multiple days on a job. Ideally, you could have all the job data present but move from day to day easily. JF suggestion was to allow two on the screen arranged vertically that you could scroll through.
+  - Change the download of server data to close the Import window and show the tracks drawing as they come in rather than waiting until they all come and then showing. I realize this could be major and probably affects the calculations done on the line. It might (probably) take longer to show an hour of each machine's data, then the next hour, etc. but the net effect for the user and the demo is a feeling of progress the bar at the bottom doesn't give. Right now, with a lot of data, the delay is painful as you do a soft-shoe waiting for it all to come in.
   - Related to the one above. Job Playback for multiple days.
-  - Morphing Progress (we're really getting out there now)
+  - AGTEK Access File Import
-  - Simulator Export (Haul Planning) - Matthews and I started talking about a track simulator for sales demos, etc. What we'll need out of the haul planning part of Trackwork (GradeModel) is an export of the haul path line in lat-long, the specifications of speed, time, and distance as well as the haul path line broken into their distinctive segments. Perhaps a variation of KMZ since we're already writing out similar files that way? The simulator portion will take that information, create multiple offset tracks based on the user specs (day, # machines, time) and generate TMM like data to the server in the background.
+  - Aggregating Haul Reports (from multiple files/hauls). Derived from spreadsheet design TBD
+=== Beyond 3.0 ===
+ - Morphing Progress (we're really getting out there now)
@@ Line 90: / Line 116: @@
   - Add second Tree/File windows to lower portion of File tab. Separate from local and label AGTEK Access.
   - When file is selected, and Ok pressed, prompt for a save location.
+====== Trackwork Revamp 2014 ======
+===== Story 1 ====
+  * De-ProfUIS
+  * Remove unneeded elements (CAD, etc)
+  * Allow haul planning using surfaces other than just Design/Subgrade, Existing/Stripped
+  * Shaders rehab
+  * Rework Import window
+  * Enable Network Operations by default
+  * Create 4D look and feel
+===== Story 2 ====
+  * Improve Reporting
+     * Multiple equipment details and summary
+     * Multiple days
+     * Multiple equipment types
+  * Saving cycle lines, summary statistics to server
+  * Support Machine types
+    * Color shades (ie; Scrapers are shades of green)
+====== State Data saved for the Trackwork System ======
+Brain Dump, needs organization
+The Trackwork system is a collection of programs and sensors unified . Trackwork as is does not save analysis work or statistics in any way that can be save either locally and through AGTEK Access tracks. It also does not read data entered from other sources like SmartTrack. The state data to save/reload for a track is:
+  * Cycle lines
+  * Avg Load
+  * Breaks
+  * Ignore segments
+  * Analysis Areas (polygon x,y) applies to grade hauls only
+      * Coverage
+      *- Avg Width
+      *- Fwd (boolean on whether to only count forward motion tracks)
+      *- Cycles
+      *- Avg Length
+      *- Avg Move time
+      *- Typical Stops (seconds)
+      *- Typical Cycle Time
+      *- Travel
+      *- Avg Move Speed
+      *- Cycle Hours
+      *- Minute per hr
+      *- Cost Hours
+  *- Statistics Area
+      *- Track Number
+      *- Avg Length
+      *- Avg Move Speed
+      *- Avg Idle Time
+      *- Stops (length of time)
+      *- Avg. Stop Time
+  *- Warning Areas
+  *-
+  *- - **Vehicle data**
+      *- Tracker Associations
+      *- Volume per cycle
+      *- Machine Type
+      *- Friendly Name
+      *- Color
+      *- Suggested Haul Paths
+==== Saving Plan Numbers from Trackwork for Comparison ====
+Scratchpad idea
+Part of what can be done in Trackwork is planning the hauls before the work is done. The customer tries to estimate for a given boundary:
+   * How much dirt needs to be moved
+   * The optimum haul path based on centers of mass
+   * The avg length of a haul
+   * The time in seconds to make a single haul broken out into 4 distinct phases (Load, Haul, Unload, return) each with it's own speed that makes up the total cycle time)
+   * The number of total cycles required to complete the dirt movement
+   * Average yds per machine (does it make sense to have some sort of machine assignment database from the server since we already use it for SmartTrack.)
+This information can go to the field as a comparison to actual or even as guideline to the superitendent.
+===== Haul/Progress thoughts =====
+We currently create a balance area and calculate hour estimates based on moving that entire amount of dirt (Stockpile is an exception). Another way to think of this is estimating and showing how far we'll be done at a specified interval (Day, week, etc.) I think this also translates into other forms of construction completion like paving or pipe.
+Another expansion of this is creating the intermediate progress surfaces as additional surfaces within the same file rather than saving off each as a separate file. The benefits are easier visualization over time, progress to compare against in the field, better presentation, and less file proliferation.
+From a presentation perspective imagine a Google Earth file showing expected progress at a day or week along with actual as collected by trackers.
+===== Trackwork for Materials/Phasing =====
+Trackwork has traditionally been about dirt. A significant part of more complicated projects is the phasing and Trackwork has the opportunity to handle this aspect of the job site as well. Features might be:
+  * Read Materials and earthwork files
+  * Allow assignment of completion times and order to phases
+  * Easier and better phasing after the fact.
+  * Time bar display of times by completion
+  * KMZ export for presentation

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools