WorksManager

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

Hello Hufford,

Currently, WorksManager does not support reassigning a work order from one data collector to another.

This functionality is not available at this time.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

Transferring work orders is the only reason I still use TCC.  We need the ability to share/move work orders in WorksManager before TCC is retired.

Hello Hufford,

Currently, WorksManager does not support reassigning a work order from one data collector to another.

This functionality is not available at this time.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

I'm not sue of the official recommended way, but we do one of the following:

• Using TCCexplore, we move all the work orders to the new controller.  Make sure the new controller is assigned in WM and has performed an initial sync.   Work orders should always be moved and not duplicated and should remain unique to each controller.
• In field using USB stick if both controllers are present.  This is done by our data prep team remotely using TeamViewer.
• Without a USB stick this can be done in TeamViewer through its file transfer feature.

The new features Vijay mentioned will be a great improvement.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

Why share WO#s?  I interested to see why there is a need to share WO#s.  

I'm not sue of the official recommended way, but we do one of the following:

• Using TCCexplore, we move all the work orders to the new controller.  Make sure the new controller is assigned in WM and has performed an initial sync.   Work orders should always be moved and not duplicated and should remain unique to each controller.
• In field using USB stick if both controllers are present.  This is done by our data prep team remotely using TeamViewer.
• Without a USB stick this can be done in TeamViewer through its file transfer feature.

The new features Vijay mentioned will be a great improvement.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

That would be a slightly different question from this thread, which would like to move work orders from device to device.   To answer your question about sharing work orders, it would be helpful, for example, in tracking as-builds if there was an option to make the work order collaborative so that all grade checkers can see the work of others.  Right now we have to make sure that all "remedial shots" are taken on the same rover.  It makes it easier to post process in the office when you don't have to chase shots all over different work orders and different controllers.

Why share WO#s?  I interested to see why there is a need to share WO#s.  

I'm not sue of the official recommended way, but we do one of the following:

• Using TCCexplore, we move all the work orders to the new controller.  Make sure the new controller is assigned in WM and has performed an initial sync.   Work orders should always be moved and not duplicated and should remain unique to each controller.
• In field using USB stick if both controllers are present.  This is done by our data prep team remotely using TeamViewer.
• Without a USB stick this can be done in TeamViewer through its file transfer feature.

The new features Vijay mentioned will be a great improvement.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?

Collaborative work orders would be top-notch! We have been mentioning it to Trimble for years, but I've never heard Trimble seriously consider the concept.

That would be a slightly different question from this thread, which would like to move work orders from device to device.   To answer your question about sharing work orders, it would be helpful, for example, in tracking as-builds if there was an option to make the work order collaborative so that all grade checkers can see the work of others.  Right now we have to make sure that all "remedial shots" are taken on the same rover.  It makes it easier to post process in the office when you don't have to chase shots all over different work orders and different controllers.

Why share WO#s?  I interested to see why there is a need to share WO#s.  

I'm not sue of the official recommended way, but we do one of the following:

• Using TCCexplore, we move all the work orders to the new controller.  Make sure the new controller is assigned in WM and has performed an initial sync.   Work orders should always be moved and not duplicated and should remain unique to each controller.
• In field using USB stick if both controllers are present.  This is done by our data prep team remotely using TeamViewer.
• Without a USB stick this can be done in TeamViewer through its file transfer feature.

The new features Vijay mentioned will be a great improvement.

What is the correct way to reassign a work order from one data collector to another in a WorksManager project?