In this article we will go through the operational use of TagTrack. You should have already configured your TagNet Server instance and installed the TagTrack application on a supported device. 

TABLE OF CONTENTS

Startup Tests

There will be a TagTrack Icon on the desktop of the cab computer, click that to launch TagTrack. As the application loads, it will perform two key startup tests as shown below. This is to check if the reader is online and TagNet server connection is accessible. If both tests are successful you will green check marks as shown below. Click the [Continue] button to proceed to the main form.  If the Server Test fails then check your Wi-Fi network connection, if Reader Test fails ensure reader is powered on. 

            

Configuration

TagTrack settings are stored in Server based Client Profiles. Each TagTrack Client (i.e. each lift computer) will have a configuration profile that can be setup and maintained by the administrator via the TagNet web interface. During the TagTrack startup (above), it will pickup any changes to its TagTrack profile. Additionally the configuration can be maintained directly from the Settings menu option on the left side.  Any changes made at the client level will also update the Server profile.


Modes of Operation

TagTrack can be used in two different modes when determining when to identify the containers picked up, and when dropped. These are referred to as Operator Initiated or Sensor Initiated (full automation). Note that Containers is a generic term for any type of object picked up on the forks such as pallets, skids, packs, bundles, etc.  Location Tags can be used effectively in both modes of operation reducing driver input to make a selection for drop location.


Sensor Initiated

This is most desired deployment model as it frees the operator from doing anything other than doing their job, that is moving tagged material from location A to B.  The sensor operation is timed to start the read cycle on pickup as well as drop. At any time the operator can override the sensor in exception cases (see Operator Initiated below). Sometimes a sensor based approach is just not workable based on the type of container(s) being moved and the handling workflow. One such case is when the driver is stacking or down-stacking containers prior to, or after moving to target location as the sensor will think that each new pickup (shuffling) is another inventory move. This can be mitigated to a point as detailed further if the driver has had training and understands cause and effect with sensor approach. 


Operator Initiated

This mode requires the operator to start the read cycle by tapping the  READ  button on a pickup to identify the material and using the Mode [PUT/MOVE/PICK] button when dropping the material at its new location. This Operator initiated workflow is described below along with the TagTrack UI. 


The Driver is in control using just two buttons. When the containers are fully seated on the forks and ready to transport,   READ  is tapped.  When Load is dropped into its final resting position, then  PUT   is used.


Step 1: Selecting the Mode

Shown below is main form ready for use. Firstly, the mode needs to be set for the use case by tapping the  MODE  button to toggle through the different use cases (PUT, MOVE or PICK). The default mode is  PUT   which is the most common activity. Note: The only difference between   PUT   ,  MOVE  and  PICK  is the ability to specify different Suggested Location Rules. Once the Mode is selected it will remain set until changed by the operator. Go to Step #2.  

           

Step 2: Pickup Operation (Event Start)

During the Pickup operation, the operator will click  READ  button when the tagged container(s) are on the forks at the desired distance in front of the antenna(s). This will attempt to RFID scan all those containers and display the results in the next step.  

         

Step 3: Tags Scanned and Resolved            

You will see all the tags scanned and resolved as shown below. If there has been Suggested Locations setup, and there is a matching rule, the Suggested Location Box will be populated as shown below highlighted. If no tags are shown in the list or less than what is expected, the driver can tap  CANCEL  and start over from Step #2 after repositioning the containers on the forks.


The Suggested Location feature of TagTrack app has little benefit for Baillie drying operations. Firstly, the rules can’t possibly know what Kilns or PD zones are being loaded, and secondly if a real location tag in the floor is not scanned on pack drop, the suggested location will be used and that would not make any sense. This feature has been disabled and drivers will see a warning message on the bottom of screen and the Suggested Loc box will not be populated. In a future release there will be a setting to disable the Suggested location feature and the box will be grayed out. 



Step 4: Driving to Drop Location

As the Driver passes over/by Location Tags on the way to the drop location they will appear in the Location Tag Box highlighted with arrow. The last Location tag scanned is used during the final drop in next step.  If Location tags have not been deployed refer to section on using the Manual Location feature.


Step 5: Dropping the Load

When the Driver has reached their final put-away location and dropped their load, tapping the   PUT   button highlighted will initiate the process of moving the inventory. Note: if there has been no Location Tag scanned or Manual Loc input, the   PUT   button will not be enabled until one of them is populated. See next final Step #6.


Step 6: Transaction Summary (Event completion)

When the transaction is successful, the below screen will display the Last Transaction Summary as shown below. This is for informational purposes and will continue to display until the next pickup event in previous Step #1.


The Driver should glance at this summary and if the transaction location does not align where the packs were physically dropped, then that would indicate an workflow error and should be noted to supervisor.


Sensor Initiated Operation

This is most desired deployment model as it frees the operator from doing anything other than doing their job, that is moving tagged material from location A to Location B.  The sensor operation is timed to start the read cycle on pickup as well as submit the inventory transaction upon drop. At any time the operator can override the sensor cycle in exception cases (see Operator Initiated section above). 


Step 1: Selecting the Mode

Shown below is main form ready for use. Firstly, the mode needs to be set for the use case by tapping the  MODE  button to toggle through the different use cases (PUT, MOVE or PICK). The default mode is  PUT   which is the most common activity. Note: The only difference between   PUT   ,  MOVE  and  PICK  is the ability to specify different Suggested Location Rules. Once the Mode is selected it will remain set until changed by the operator. Go to Step #2.  

           

Step 2: Pickup Operation (Event Start)

During the Pickup operation, the sensor will detect the presence of a container on the forks and begin the RFID read countdown as shown in red box.  This countdown allows the driver to line-up/position the container(s) on the forks where the sensor can go on/off repeatability before the read cycle starts. This also allows time for the driver to back away from other close-by containers in the pickup area that might be scanned inadvertently.  Once the sensor has been solidly on for the configured countdown period (e.g. 5 secs), the assumption is that the load is securely on the forks and the read cycle will then begin as shown in the next step. Note that the Sensor detection range and the countdown period (aka GPI Dwell Time) are configurable in the Server Side setup.  Proceed to Step #3.


Understanding how the Sensor Operation is used during Pickup

There are three common scenarios when picking up material; a) clean pickup b) reposition during pickup while still on forks and c) repeated attempts to pick-up/back-away/reposition load. It is scenario c) that requires the countdown logic.

Clean Pickup- Driver picks up the load and backs away completely and does not re-approach to adjust position. Sensor goes off cleanly (once) and countdown begins and when reaching zero the transaction is submitted. ** if this scenario would happen all the time you would not need a countdown logic.

Reposition while Load on Forks - Driver places forks under load and repositions using side shifter, sensor stays on the entire time and driver does not back away/re-approach to adjust load position. Sensor goes on (once) as Driver backs away, countdown begins and when reaching zero the read cycle starts. 

Repositioning & Moving Away - Driver makes multiple attempts to position load on forks and in doing so backs up and repositions forks multiple times. Sensor goes on and off while performing these load adjustments. Sensor goes on/off repeatability with countdown restarting each time (never runs down to zero).  Sensor stays on for the final time as Driver backs away with load and countdown begins, when reaching zero the read cycle starts.


                     

Step 3: Tags Scanned and Resolved

When the Read cycle is initiated from the previous step, the container(s) tags scanned will be displayed in the list as shown below. If there has been Suggested Locations setup and there is a matching rule, the Suggested Location Box will be populated as shown below highlighted indicating to driver an available inventory slot. The sensor status now shows as   PICKUP   indicating that the driver can proceed to the drop-off location. Go to Step #4. 


Container Scanning Issues

If no tags are shown in the list or fewer containers than what is expected, the driver can tap  CANCEL  and then en  READ  to force a scan of what is on the forks. If the results are still not correct tap  CANCEL  and start over from Step #2 after repositioning the containers on the forks. Check to ensure the container tags are applied in the correct area to ensure RFID scan can take place. 


Step 4: Driving to Drop Location

As the Driver passes over/by Location Tags (if deployed) on the way to the drop location they will appear in the Location Tag Box highlighted with arrow. If Location Tags have not been deployed refer to section on using the Manual Location feature. Proceed to Step #5 for final drop.


Step 5: Dropping the Load

When the Driver has reached their final put-away location and upon dropping their container load and backing away, the sensor status will then start counting down allowing time for the driver to re-approach shift/reposition the load (which may require picking it up again). During this put-away process the sensor can go off/on repeatability and as long as the sensor does not stay off exceeding the countdown period (e.g. 5 secs). In this case the logic will still assume this is the same pickup/drop and not a new Pickup event (of the same containers). Once the sensor has been solidly off for the configured countdown period the inventory transaction will be submitted as shown in the next step. 


Understanding how the Sensor Operation is used during Drop

There are three common scenarios when dropping material; a) clean drop  b) reposition while load still attached and c) moving away with repeated attempts to reposition load. It is scenario c) that requires the countdown logic.

Clean Drop - Driver drops the load and backs away completely and does not re-approach to adjust position. Sensor goes off cleanly (once) and countdown begins and when reaching zero the transaction is submitted. ** if this scenario would happen all the time you would not need a countdown logic.

Reposition while Load on Forks - Driver drops the load to ground and repositions using side shifter, sensor stays on the entire time and driver does not back away/re-approach to adjust load position. Sensor goes off (once) as Driver backs away and countdown begins, when reaching zero the transaction is submitted. 

Repositioning & Moving Away - Driver drops the load to ground and backs away to reposition multiple times. Sensor goes off and on while performing these load adjustments. Sensor goes off/on repeatability with countdown restarting each time.  Sensor goes off for the final time as Driver backs away and countdown begins, when reaching zero the transaction is submitted.

Up-stacking & Down-stacking - Driver drops the load to ground and backs away to pickup top pack(s) for put-away to existing stack. Dependent on how long it takes Driver to re-approach the dropped load, Sensor may or may not go off while performing these re-stacking operations. If each re-stack is longer than the countdown period, there can multiple re-handling transactions to the same location.



Dropping Load with ERROR

If the Load is dropped and there has been no Location Tag scanned or Manual Loc input, the Sensor Status will show as ERROR below. In this situation the Driver has to take action as the inventory transaction cannot complete. They must either re-approach the load (Sensor goes back to  PICKUP  state) and either move around to scan a location tag or manually enter one. Then when backing away the transaction will go through.  However if this is a re-handling operation where there is no inventory location change, then this error can be ignored and  CANCEL  used to reset.  


IMPORTANT:  If a driver drops packs A & B leaving the event cycle open (those tags remain cached), then goes to pick-up packs C & D the system cannot tell the difference and you will have the first two packs A & B moved erroneously and C & D not moved. If the driver is not coming back to pickup those packs they should use  CANCEL  as above to close the event. ** In a future release there will be a setting to allow an organization to decide what method is best for them; force a re-scan of tags after timer expires or allow the event to continue (saving the countdown period to AutoID the tags).


Step 6: Transaction Summary (Event Completion)

When the transaction is successful, the below screen will display the Last Transaction Summary as shown below. This is a confirmation to Driver of the last event and will continue to display until the next pickup event in previous Step #2.


The Driver should glance at this summary and if the transaction location does not align where the packs were physically dropped, then that would indicate an workflow error and should be noted to supervisor.


Considerations when Using the Manual Location Input

The Manual Location box allows the driver to select a target (put-away) location by tapping inside the Manual Loc box  and making a selection from the drop-downs as shown below.  This is used when NO location tags (or a minimal amount) are deployed.  It is important to understand what takes precedence; if a Location Tag is scanned on the way to a drop location, that is taken as the 'truth' and overrides any Manual Loc entered by the driver. This can cause problems if driver passes over areas that have Location tags (e.g. in the ground) and the target location does not have a Location Tag (the last seen is the one used and overrides any driver input).  Why is this?  TagTrack is designed to run as automated as possible with little to no driver input, if location tags are deployed correctly the driver should not have to manually enter any values (only on exceptions). Partial deployments of Location Tags can cause confusion for drivers.


Why not allow the Driver to override?  If the Manual Loc was used as an override then a driver could mistakenly leave a selection in there (not clear it) from a previous move operation and any subsequent loads would ignore the carefully placed locations tags. This would result in containers being moved to the wrong location until the mistake is discovered, resulting in incorrect inventory.  This is why the Manual Location is considered as a default and NOT an override to a physical Location Tag. 


What can be done if Location Tags are not fully deployed?  The Location Antenna can be set to OFF thus disabling any scans of Location tags in the ground. This will require the driver to enter the correct Manual Location (and clear it when necessary).


Making a Manual Location Selection


Both Location Tag Scan and Manual Location Entered


 



TABLE OF CONTENTS