Warning
WARNING: The TrackAbout MetaWiki has been deprecated and is no longer being updated.

Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.

Not-Scanned Assets

From TrackAbout MetaWiki
Revision as of 00:08, 21 June 2016 by Jwolbert (talk | contribs)
Jump to navigation Jump to search
TrackAbout Feature
Feature Name: Not-Scanned Assets
In Module: Core Tracking
Short Description A feature to allow assets without tags/barcodes to be tracked for particular processes such as Production and Distribution
Available In:
← Back to list


Summary

When a driver scans assets as s/he’s delivering and returning them, life is good! Accurate and complete data is captured allowing us to know exactly which assets are in which locations.

In the real world, assets don’t always get scanned. Perhaps the barcode has fallen off. Maybe the barcode is unreadable. Sometimes the driver forgets to scan. Whatever the reason, TrackAbout’s unique features will help you catch and correct incomplete information.

DNS – Delivered Not Scanned Assets and RNS – Returned Not Scanned Assets occur when unique asset information does not get entered into the TrackAbout system. Usually this occurs when the barcode is not scanned by the driver.

However, if a driver did not scan a barcode, this does not always result in a DNS or an RNS. If a driver is unable to scan a barcode, s/he can enter the barcode information manually into the handheld device. When the handheld is synchronized with the TrackAbout system, that barcode information will go into TrackAbout as a unique asset, not as a DNS or an RNS.

Not Scanned Assets can be created several ways:

  1. Added by driver
    1. Cylinders loaded onto a truck without barcodes
    2. Drivers pick up cylinders with no barcodes
    3. Label is damaged or unreadable
  2. Added to existing record by admin from site – usually done during verifications
  3. When there is no scanning data we create entire records of NS from the accounting info import of deliveries
  4. Loading legacy balances