Difference between revisions of "Reviewing Data"
m |
m (→Collisions) |
||
Line 25: | Line 25: | ||
==Reconciling Customer Audits== | ==Reconciling Customer Audits== | ||
==Collisions== | ==Collisions== | ||
+ | |||
+ | An asset collision is a condition that occurs when a barcode or serial number is scanned or keyed-in on a record, and TrackAbout cannot resolve the barcode or serial number to target exactly one asset in the system. For a variety of reasons, but usually data entry errors, there can be two or more assets in the system with the same barcode or serial number. When TrackAbout cannot find one and only one asset that matches, it instead attaches a collision to the record. | ||
+ | Collisions on records are called out on the Dashboard page and are one of the conditions that TrackAbout administrators need to be aware of and clean up on a regular basis. The collision attached to the record contains all the known information about the asset that was scanned or keyed in. The collision resolution webpage also provides additional information about the possible matches in order to help the admin resolve the collision. | ||
+ | TrackAbout will attempt to auto-resolve any collisions as they might occur by checking other properties of the two or more assets that were located, such as those assets' classifications, product codes, and physical locations. If TrackAbout can intuit that only one of the assets that matched could possibly be the asset in question, it will auto-resolve the collision, no user intervention is required, and no actual collision will be created. | ||
+ | |||
+ | [[Collisions]] | ||
+ | |||
==Mapping New Product Codes == | ==Mapping New Product Codes == | ||
Revision as of 11:25, 4 October 2016
Summary
Reviewing Data is the final phase of your Quick Start Implementation. From this page, we will lead you through some of the most helpful pages and tools on the TrackAbout website for utilizing and undertanding your data.
Reviewing Asset Data
Asset History
Records
Record Details
Editing Records
TrackAbout Administration
TrackAbout Dashboard
Sync Problems
Reconciling Customer Audits
Collisions
An asset collision is a condition that occurs when a barcode or serial number is scanned or keyed-in on a record, and TrackAbout cannot resolve the barcode or serial number to target exactly one asset in the system. For a variety of reasons, but usually data entry errors, there can be two or more assets in the system with the same barcode or serial number. When TrackAbout cannot find one and only one asset that matches, it instead attaches a collision to the record. Collisions on records are called out on the Dashboard page and are one of the conditions that TrackAbout administrators need to be aware of and clean up on a regular basis. The collision attached to the record contains all the known information about the asset that was scanned or keyed in. The collision resolution webpage also provides additional information about the possible matches in order to help the admin resolve the collision. TrackAbout will attempt to auto-resolve any collisions as they might occur by checking other properties of the two or more assets that were located, such as those assets' classifications, product codes, and physical locations. If TrackAbout can intuit that only one of the assets that matched could possibly be the asset in question, it will auto-resolve the collision, no user intervention is required, and no actual collision will be created.
Mapping New Product Codes
TrackAbout Reporting Tools
TrackAbout Activity
Current Inventory
Advanced Functionality
TrackAbout provides so much useful functionality beyond what is available through your Core Tracking Module. Review information about Modules and Features to tailor TrackAbout to your needs.
- Refer to the Module descriptions on our Corporate Site for a high level overview.
- Refer to the TrackAbout Wiki Module Overviews for more detailed and technical information about Module and Feature functionality.