The Rail Wear Trend Chart and Rail Replacement Forecast Report use average measurements for each run and track segment that are precalculated and stored in the database. The use of precalculated averages greatly increases the speed of producing charts and reports.
Averages should be calculated for a run after editing is complete: i.e. any bad profiles have been deleted, and profile location has been corrected. In addition, track segments must have been correctly entered into the database.
If you need to recalculate measurements, delete profiles, or correct locations for a run after averages have been calculated, you should recalculate averages afterwards! Failure to do so will result in incorrect trend charts and reports.
If the boundaries of a track segment are significantly changed, average measurements for the segment will be automatically deleted from the database! If you change track segment boundaries, you should recalculate averages for all runs that include the mileage range of the updated segments!
Logically, calculating averages is the last step in editing your rail wear data, before you generate reports.
Recognizing that some data collection runs are better than others, Rangecam provides a way of excluding selected runs from wear trend calculations. This feature is used to isolate a run containing data that is not trusted, perhaps because the measurement system was in poor calibration, without requiring you to delete the run from the database. Averages are not calculated for a run if No Averaging is checked in the Run Table Maintenance Dialog.
To recalculate averages, choose Calculate All... from the Run menu. See the section Calculate All - Batch Operations.
Note: Rail inventory and averages are not imported from Access. After joining runs in Enterprise, the Calculate All function should be used to calculate Inventory and Averages for imported profile runs.