Trimble Business Center

Hello,

We are using
TBC 5.81
Access 2022.10

We have had a number of situations where the results from Access at the end of the day don't match the results within TBC once we import the Access .job file.  Usually this is some oddity and hierarchy understanding within TBC that we can make sense of, become aware of and look out for, even if we don't like it.

We had a situation like this happen that I don't think I can explain or would have known to look out for.

A field crew was in the process of doing rounds and in the process had not updated the foresight prism after Access turned to backsight, prism was switched to backsight prism, then turned to foresight and the same prism and height was used and not updated.  The process played out to the close of the rounds and the field crew, party chief, had noticed the blunder and before storing the foresight point, updated the prism and height.  When the point was stored in Access the raw data for the mean angle reports the correct prism and height, although the individual measurements do not, they report the blundered prism and height.  To be sure of the process the party chief did the exact same process again, with no blunders this time, and stored a unique point.  In the field these two points have almost the exact same coordinate location, minus very little difference due to variations in measurements, inherent error.

The .job file is then imported into TBC and the blundered point coordinate is no longer correct based on TBC's reduction of the raw data.  How did we catch this?  Luckily the party chief measured this twice, even though he was given the opportunity to correct this in the field, and the office technician so the delta between the two points and did further review.  The technician and I then pulled out all the data and reviewed and found out what was going on.

I am wondering if anyone else has seen this before and has recommendations for how to stop it, or input on what our team is doing incorrectly.  I uploaded the survey report from the day of work and an Excel spreadsheet that has the point comparison.  I wasn't able to upload .jxl or .job.

I really struggle with the idea that we export our data from TBC to Access, then do a day of field work and input that Access back into TBC and somehow when we have exported coordinate files from both Access and TBC they don't exactly match up.  I would love to work in a business model where we were able to double check each and every movement we make, and in some cases with TBC and Access together I feel like we need to triple check, but there isn't a profitable model there.  Oh whoops, soap boxing.  Full stop.

Thank you for all the help.

Attachment(s)

Survey Report.pdf   168 KB 1 version

Point Comparison.xlsx   15 KB 1 version

Hi Clayton,

did you ever find a resolution for this?

I've encountered a very similar issue whereby when I import certain .job files in TBC a number of as-staked points, seemingly random, differ in position from where they had been recorded in Access. They're obvious because they're as-staked positions which, as you'd expect wouldn't have been recorded unless they fell within the requisite spec' (in these instances +/- 5mm).

I'm running TBC v5.90 and Access was on a hired but brand new (as of late 2024) TSC5 running with a S7 instrument.

Fingers crossed you found a simple fix that I can apply because I'm left with 31 job files that I can't reliably use and my brain is now fried...