windows:trackwork:trackwork
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
windows:trackwork:trackwork [2012/10/10 16:40] 127.0.0.1 external edit |
windows:trackwork:trackwork [2014/10/03 17:05] (current) mikeclapp [Trackwork Revamp 2014] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[main|Main Page]] | + | [[:start|Main Page]] |
| ====== Trackwork ====== | ====== Trackwork ====== | ||
| Line 116: | Line 116: | ||
| - Add second Tree/File windows to lower portion of File tab. Separate from local and label AGTEK Access. | - 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. | - 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 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
windows/trackwork/trackwork.1349887217.txt.gz · Last modified: 2012/10/10 22:08 (external edit)
Page Tools
