This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| windows:trackwork:trackwork [2014/07/26 00:40] mikeclapp [State Data saved for Trackwork (and other programs) Track API needs] | windows:trackwork:trackwork [2014/10/03 17:05] (current) mikeclapp [Trackwork Revamp 2014] | ||
|---|---|---|---|
| Line 118: | Line 118: | ||
| ====== Trackwork Revamp 2014 ====== | ====== Trackwork Revamp 2014 ====== | ||
| + | |||
| + | ===== Story 1 ==== | ||
| * De-ProfUIS | * De-ProfUIS | ||
| * Remove unneeded elements (CAD, etc) | * 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 | * Improve Reporting | ||
| * Multiple equipment details and summary | * Multiple equipment details and summary | ||
| * Multiple days | * Multiple days | ||
| - | * Multiple equipment types | + | * Multiple equipment types  | 
| - | * Allow haul planning using surfaces other than just Design/Subgrade, Existing/Stripped | + | |
| - | * Shaders rehab | + | |
| * Saving cycle lines, summary statistics to server | * Saving cycle lines, summary statistics to server | ||
| * Support Machine types | * Support Machine types | ||
| * Color shades (ie; Scrapers are shades of green) | * Color shades (ie; Scrapers are shades of green) | ||
| - | * Rework Import window | ||
| - | |||
| ====== State Data saved for the Trackwork System ====== | ====== State Data saved for the Trackwork System ====== | ||
| Line 185: | Line 191: | ||
| * 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 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 | * 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 from the server. | + | * 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. | 
| Line 200: | Line 206: | ||
| From a presentation perspective imagine a Google Earth file showing expected progress at a day or week along with actual as collected by trackers. | 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 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||