User's Manual

Table Of Contents

Draft

RT 1000 v1.0 24 Deployment Guide R00.f

Demobilization

6.1 Overview

xxx

6.2 Process

xxx

As soon as the Event Manager tool has determined that a WRU is no longer

needed at that location, it will change color on the basemap. The Observer will

need to consider the possibility of reshooting source points, which could

happen if some recording failure is discovered later. Assuming no such

reshoots, the Observer can undeploy the WRU or the entire rib. There will be

no detrimental effect to either the ground electronics or the CSS database if

the pick-up crew starts picking up the line before the Observer has undeployed

it (e.g. if the backhaul is interrupted), as long as the Observer manually

removes the picked-up WRUs from the deployed list at a later date. However,

the preferred procedure for accurate asset tracking is to deploy from the CSS

before physical pick-up.

Another option is for an LTU technician to undeploy a rib using the HRA while

connected into the LTU/BSU. This can only be done when the rib has finished

all recording operations. This requires that a message indicating which WRUs

have been undeployed be sent to the CSS after this action.

Undeployment user action in the CSS can be either from the basemap or from

a spreadsheet listing within the CSS application. An “are you sure” pop-up

should be considered, especially for large numbers of WRUs and certainly for

WRUs that haven’t been cleared by the Event Manager.

Once a WRU or rib is undeployed by the Observer through the CSS, it is up to

the staging manager to ensure the physical pickup and asset tracking of the

ground electronics. At the end of the project, the primary need the Observer

has of the CSS is to ensure that all positional and trace data has been stored,

backed up, and delivered properly. He will then need to power everything

down and secure all hardware for transport.