If you do not already know what rail weights are found in the territory you are about to process, the field crew's notes should tell you. Also check for anything unusual in system calibration, mile stamping, or odometer calibration, or conditions affecting visibility of the rail base, such as high ballast or snow.
If importing from the Rangecam Field System, you have already ensured that your Office System database is compatible with the Field System database used during data collection.
You have chosen Modeling Options that are appropriate for the rail types you expect to see. Having done that, reading runs into the database is in most cases largely a batch process, which can proceed unattended.
Sometimes there are difficulties in importing run data. Two rails may be too similar for the software to distinguish easily. Profile data may contain errors resulting from bright sunlight, leaves or other debris on the track. High ballast may cover part or all of the base of the rail. Rangecam has processing options to help deal with those difficulties. In problem areas, it is sometimes necessary to delete a run and re-read it with different options, perhaps more than once. When you find a set of options that works in such a case, it may be useful to save them in named files, which you can use again the next time you need to process a run from the same territory.