Jvargo at 20:01, 11 May 2017

2017-05-11T20:01:45Z

Jwolbert at 04:08, 21 June 2016

2016-06-21T04:08:16Z

Jwolbert: Created page with "== 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 asse..."

2013-08-22T15:56:10Z

Created page with "== 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 asse..."

New page

== 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:
#Added by driver
##Cylinders loaded onto a truck without barcodes
##Drivers pick up cylinders with no barcodes
##Label is damaged or unreadable
#Added to existing record by admin from site – usually done during verifications
#When there is no scanning data we create entire records of NS from the accounting info import of deliveries
#Loading legacy balances

← Older revision		Revision as of 04:08, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Parent Module=Core Tracking
		+	\|Feature Description=A feature to allow assets without tags/barcodes to be tracked for particular processes such as Production and Distribution
		+	}}
	== Summary ==		== 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.		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.

@@ Line 3: / Line 3: @@
 |Feature Description=A feature to allow assets without tags/barcodes to be tracked for particular processes such as Production and Distribution
 }}
-== Summary ==
+==Overview==
 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.
+===Why You Need It===
 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:
+===When to use===
-#Added by driver
+Not scanned assets can be created intentionally by added them to a record, or can be created as a result of a balance correction/adjustment
-##Cylinders loaded onto a truck without barcodes
+Below are a some examples of why NS assets might be used and how they would be applied to the scenario
-##Drivers pick up cylinders with no barcodes
+#Added by driver - manually attached to delivery/return action
-##Label is damaged or unreadable
+##Cylinders loaded onto a truck without barcodes - manually attached on Load Truck action
-#Added to existing record by admin from site – usually done during verifications
+##Drivers pick up cylinders with no barcodes - manually attached to delivery/return action
 #When there is no scanning data we create entire records of NS from the accounting info import of deliveries
 #Loading legacy balances

Not-Scanned Assets - Revision history

Jvargo at 20:01, 11 May 2017

Jwolbert at 04:08, 21 June 2016

Jwolbert: Created page with "== 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 asse..."