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.

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.

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.

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.

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.

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.

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

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.

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.

------------------------------
Shaune Dorron
------------------------------

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.

------------------------------
Shaune Dorron
------------------------------

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
------------------------------

Original Message:
Sent: 05-29-2024 21:15
From: Shaune Dorron
Subject: TBC Slow to Import Data

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.

------------------------------
Shaune Dorron
------------------------------