Trimble Business Center

I have been using a TBC job to process daily jobs (from TSC5) from a field crew for about 9 months now however the imports keep getting slower to the point where it can take an hour to import a new daily job with only a dozen points in the file. Is this a limiation of TBC with how it handles importing the daily job (such as converting .job to .jxl) or has anybody else encountered the same thing?

Most of my processing (such as stringing services ascons etc) is done in this file however only reference design surfaces from other projects and file is sitting at 12mb.

I have opened a blank project and imported same file in and it takes seconds to import so nothing wrong with the job files.

I have tried deleting the history log and made no difference (it was asitting around the 1.1gb mark!)

Im aware of the all the meta data assigned with each point that gets imported however find it very useful when processing or looking back over data.

All data sits in onedrive/sharepoint and have tried pausing sync and even disconnecting interenet to see if this is casuing and issues.

Are you "drag and dropping" your jxl / job, or are you importing from Sync Manager / Connected Community? 

P.S. We have a different work flow. Each job/jxl gets imported to blank project, gets redrafted, corrected... whatever has to happen. Then VCL is exported (containing only reviewd, quality data) and that VCL is imported into "master" TBC project.

Tried importing through import script and also dragging and dropping from onedrive.

Try to avoid your method by keeping everything in one TBC project as a one stop shop for field data.

Copy.

I haven't run into any issues drag and dropping from local drive or importing *.job from connect.

Never tried the one drive route.

Yes,

It just took me over an hour to import a 500 meg xml surface. Yesterday it took about half hour just to import 22 pdfs

Yes,

My TBC 2024.00 is now getting very slow - especially importing any Survey Jobs with Photos as either Attributes or Tagged,

Taking up to 20 minutes for 30 points - very frustrating

Couple of suggestions. First, make sure that you are NOT using a network drive. Second, ideally you have a SSD that's not your C drive. Third, in the TBC options, make sure to type 100 in the RAM allocation field within the point clouds tab. Even if you aren't using tbc with point clouds. Also, make sure that your dedicated video card is being used in lieu of an integrated GPU. Lastly, I wouldn't even consider using TBC without a middle of the road i7 CPU and at least 32GB of RAM. TBC will/can only use up to 50% off the total ram.

------------------------------
Zach Edwards
------------------------------

Having the same issue. Importing and exporting the simplest of files is taking an hour or more. I've moved projects to my local drive, no help. It's to the point TBC is worthless to me unless it's a project with only 1 field day in it. We don't have projects like that. Most of our work is many days/weeks of work on the same job that must stay together. I've gone back 1 version and am not experiencing any issues at all. It's something embedded in the latest version.

------------------------------
Keith Ludwig
------------------------------