Key Concepts - Revision history

Jgreco: Initial proofread pass - docs

2021-12-01T19:01:41Z

Initial proofread pass - docs

Show changes

Jgullickson: /* Retired Assets */

2020-12-16T16:44:29Z

Retired Assets

Lsilverman at 19:42, 9 May 2019

2019-05-09T19:42:57Z

Lsilverman: /* Locations vs Customers */

2019-05-09T19:41:44Z

Locations vs Customers

Eschurdak: /* Expiration Date */

2016-11-07T21:08:30Z

Expiration Date

Eschurdak: /* Retest Date = */

2016-11-07T21:04:40Z

Retest Date =

Eschurdak: /* Expiration & Retest Date */

2016-11-07T21:03:58Z

Expiration & Retest Date

Jwolbert: /* Dashboard */

2016-04-29T17:42:46Z

Dashboard

Jwolbert: /* Conduit */

2016-04-29T17:34:38Z

Conduit

Jwolbert: /* Accounting Adjustments */

2016-04-29T17:32:45Z

Accounting Adjustments

@@ Line 195: / Line 195: @@
 == Retired Assets ==
 One may retire an asset in TrackAbout, marking that particular asset as no longer in use.  Retiring an asset changes its location to the unknown location.  Once so marked, that asset will no longer be counted in the inventory of any actual location.  The history of the retired asset is retained in TrackAbout.
 == Serial Number Collection Rules  ==

@@ Line 129: / Line 129: @@
 == Locations ==
-Locations are areas where assets can be stored. Any area that is not at a Customer is considered a Location. A more detailed explanation can be read [[Locations|here]].<br>
+Locations are areas where assets can be stored. Any area that is not at a Customer is considered a Location. A more detailed explanation can be read [[Locations|here]].
 == Locations vs Customers ==
@@ Line 144: / Line 144: @@
 == Make Pack ==
-Sometimes assets are bundled together and moved in a group (example:  12-pack of cylinders, 6-pack of cylinders). Rather than scanning each individual asset each time this group moves, the 'Make Pack' feature can be used to group these assets together. Then, when this "pack" of assets moves, only the pack barcode needs to be scanned. The Pack has its own Product Code, separate from the Product Code of the assets in the Pack. Once these assets have been associated with a pack barcode, they act as 1 asset until they are broken, or 'removed' from the pack.  All records pertaining to a pack will show with a count of one, including all production and distribution records. To find the individual pack's assets, go to the Asset Search page, click on the + sign on the More Asset Search Options section, and enter the pack number in the Pack # field. When you hit the Search button, you will see all assets in that pack and will then be able to click the View link to see assets' histories.<br>
+Sometimes assets are bundled together and moved in a group (example:  12-pack of cylinders, 6-pack of cylinders). Rather than scanning each individual asset each time this group moves, the 'Make Pack' feature can be used to group these assets together. Then, when this "pack" of assets moves, only the pack barcode needs to be scanned. The Pack has its own Product Code, separate from the Product Code of the assets in the Pack. Once these assets have been associated with a pack barcode, they act as 1 asset until they are broken, or 'removed' from the pack.  All records pertaining to a pack will show with a count of one, including all production and distribution records. To find the individual pack's assets, go to the Asset Search page, click on the + sign on the More Asset Search Options section, and enter the pack number in the Pack # field. When you hit the Search button, you will see all assets in that pack and will then be able to click the View link to see assets' histories.
 More detailed information about setting up and using this feature can be found here: <br>
@@ Line 156: / Line 156: @@
 It is possible to print various actions to a Bluetooth printer from a Bluetooth handheld. Most commonly, this happens at the end of a customer delivery, after all delivered and returned assets have been scanned. However, it is possible to print other actions, as well. When this extra feature has been purchased, it must be enabled by your TrackAbout representative. It is included in Core tracking.
-== Not-Scanned Assets<br>  ==
+== Not-Scanned Assets ==
 When a barcode is unreadable or unknown, it is possible to track quantities of asset types as Not-Scanned (NS) assets. The ability to use NS assets helps to keep customer balances accurate, even when barcodes have not been scanned. There are several actions which result in NS assets being on a customer's balance. If a driver is unable to scan or read a barcode during a delivery, s/he may enter the asset type and quantity as either a delivery (DNS) or as a return (RNS.) NS assets may also be delivered/returned to/from a customer during integration if an invoice from the business system does not have a matching invoice with tracking data from a handheld.
@@ Line 164: / Line 164: @@
 Who actually owns a particular asset may be tracked as a specific attribute of any asset.  While many TrackAbout users track only their own assets, it is particularly common in the packaged gas industry to track the locations of assets rented from another distributor.
-== Product Codes<br>  ==
+== Product Codes  ==
 A product code is the same thing as your part number, SKU, or catalog ID. This is the code that is used in the business system for a delivery of an asset to a customer. This is also the code that is used for any integration with the business system.
@@ Line 183: / Line 183: @@
 == Record Editing ==
-Recording editing is how TrackAbout allows you to change records which have already been saved to the website. Changes can be made to update records or correct errors which have been made.&nbsp; A more detailed explanation can be read [[Record Editing|here]].<br>
+Recording editing is how TrackAbout allows you to change records which have already been saved to the website. Changes can be made to update records or correct errors which have been made.&nbsp; A more detailed explanation can be read [[Record Editing|here]].
 == Rental Days ==
@@ Line 196: / Line 196: @@
 One may retire an asset in TrackAbout, marking that particular asset as no longer in use.  Retiring an asset changes its location to the unknown location.  Once so marked, that asset will no longer be counted in the inventory of any actual location.  The history of the retired asset is retained in TrackAbout.
-== Serial Number Collection Rules<br>  ==
+== Serial Number Collection Rules  ==
 This feature allows for any Asset Type/Ownership combination to not require a serial number. This option is found under TrackAbout Config.
@@ Line 204: / Line 204: @@
 After saving the last delivery action, the user selects the Sign Many button from the menu. A grid displays all deliveries without signatures saved on the device. The user selects one or more deliveries from the list and hits CONTINUE. The final screen collects the signer's name and signature. Saving the "Sign Many" action actually results in saving the signature to all the selected Delivery actions. Saving a "Sign Many" action does not result in a new record in and of itself.
-== Split and Merge Asset History<br>  ==
+== Split and Merge Asset History  ==
 If there are two assets in TrackAbout which are actually the same asset, their histories in TrackAbout can be merged together during a Collision Resolution. This will cause them to be one asset in TrackAbout, thereby reflecting the reality that there really is only one asset, not two. Sometimes, two physical assets are being represented in TrackAbout by one barcode. This can be caused by TrackAbout assets being incorrectly merged together, or by a split barcode pair, whereby two assets have the same barcode. In these cases, it is possible to split the history of an asset in TrackAbout to make two unique assets.
-== Synchronization<br> ==
+== Synchronization ==
 Synchronizing is the process of updating the website with data from the handheld, and updating the handhelds based on information from the website. In addition to updating the handheld software, syncing can also update such things as user and location information.
@@ Line 221: / Line 221: @@
 [[File:TAM6 Login.png|200px]]
-== Tracking Volume/Weight<br>  ==
+== Tracking Volume/Weight  ==
 It is possible to track Asset Volume/Weight by having TrackAbout staff enable a setting. This is the primary setting required in order to do Tube Trailer tracking, and this feature can be used for other types of assets, as well. Once this setting has been enabled, it will then be possible to enable volume collection on specific product codes.
@@ Line 235: / Line 235: @@
 This refers to any screens on a computer or handheld device that allows the user (you) to control or use the TrackAbout software.&nbsp; A more detailed explanation can be read [[User Interface|here]].
-== User Roles and Permissions<br>  ==
+== User Roles and Permissions  ==
 Every user in TrackAbout needs to have a Role assigned to him/her. Different Roles can to be created for different job functions, such as System Administrator, Truck Driver, etc. After various Roles have been created, different permissions may be assigned to those roles. For example, you may not want a Truck Driver to be able to delete records, so you would not give Delete permissions to the Truck Driver Role.

@@ Line 131: / Line 131: @@
 Locations are areas where assets can be stored. Any area that is not at a Customer is considered a Location. A more detailed explanation can be read [[Locations|here]].<br>
-== Locations vs Customers<br>  ==
+== Locations vs Customers ==
 Locate actions may be used to assign assets to a location, but a Deliver action must be used to deliver and/or return assets to/from customers. It is possible to use a Deliver action to assign/remove assets to/from locations; however, they will be converted to Locate actions when the handheld syncs to the website. Another difference between Locations and Customers is that Customers may get accounting adjustments, but Locations won't. For example, if TrackAbout has a unique asset assigned to a customer and that same asset gets scanned elsewhere, TrackAbout will create an accounting adjustment to remove the asset from the customer's balance. Since Accounting Adjustments serve as reminders to adjust Customer balances in the business system, there is no need for accounting adjustments for Locations.

← Older revision		Revision as of 21:08, 7 November 2016
Line 117:		Line 117:
	Expiration Date refers to the expiration date of the product inside of an asset. There is an Expiring Assets report that shows which assets are outstanding and have expiring product in them.		Expiration Date refers to the expiration date of the product inside of an asset. There is an Expiring Assets report that shows which assets are outstanding and have expiring product in them.

		+	The expiration date is usually set in the Fill action, or in the Set Expiration Date action. This value remains on the asset until the next time the asset is filled, or the expiration date is set.

	== Full/Empty Status ==		== Full/Empty Status ==

@@ Line 117: / Line 117: @@
 Expiration Date refers to the expiration date of the product inside of an asset. There is an Expiring Assets report that shows which assets are outstanding and have expiring product in them.
 == Full/Empty Status ==
@@ Line 189: / Line 186: @@
 == Rental Days ==
 TrackAbout rental calculations are based around rental days.  Each day an asset is in the possession of the customer constitutes one rental day.  When rent is tallied, the number of billable rental days is totaled, and that number is multiplied by the applicable rental rate for that asset based on its product code.  Leases are also calculated based on rental days.  A lease for a single asset for a month is calculated by TrackAbout as 30 rental days for that asset type for that particular month. A customer who had a lease for a single asset for a month, but actually possessed 2 assets of that type for 15 days, would pay no rent.  The 30 rental days covered by the lease would entirely replace rent for that month.
 == Retired Assets ==

@@ Line 113: / Line 113: @@
 Duplicate Barcodes occur when two unique Assets being tracked in TrackAbout are attached to the same Barcode.&nbsp; This is a bad condition.&nbsp; Because Barcodes are intended to be the unique ID for an Asset, two Assets having the same barcode would be like two people with the same Social Security number.&nbsp; This can happen if a pair of Barcode labels were split and accidentally applied to two Assets, or if two Identical sets of labels were accidentally printed and used.
-== Expiration &amp; Retest Date ==
+== Expiration Date ==
-Both the gas' expiration date and the tank's retest date can be collected. They can then be reported on under Manamgement Reports. There is an Assets To Be Retested report and an Expiring Assets report.
 == Full/Empty Status ==

@@ Line 94: / Line 94: @@
 See also: [[Customer Reports]].
-== Dashboard ==
+== TrackAbout Dashboard ==
-=== New Product Codes to Map ===
+The TrackAbout Dashboard should be a staple of your daily TrackAbout Administrative activities.  The Dashboard provides information about unresolved issues pertaining to your data.  These issues includes items such as
-Some product code might have been added but not yet mapped in TrackAbout. This dashboard link allow you to easily map these product codes.
-Product code can be added either manually in the application web site, or automaticaly via system integrated with TrackAbout. <br>
+* Sync Problems
-[[Mapping New Product Codes]]
+* [[Mapping New Product Codes|New Product Codes to Map]]
 == Data Lock  ==

@@ Line 87: / Line 87: @@
 |}
 == Conduit ==
-TrackAbout Conduit is software installed on a desktop PC or laptop running Microsoft Windows. The Conduit allows your handhelds to communicate with the TrackAbout website. It is through the Conduit that handheld data gets synced to the website, and updates are sent from the website to your handhelds.
+TrackAbout Conduit is software installed on a desktop PC or laptop running Microsoft Windows for use with TAM5. The Conduit allows your handhelds to communicate with the TrackAbout website. It is through the Conduit that handheld data gets synced to the website, and updates are sent from the website to your handhelds.
 == Customers ==

@@ Line 2: / Line 2: @@
 == Accounting Adjustments ==
-An Accounting Adjustment is a record that TrackAbout creates to edit the balances in the client's main businesses system. These are called Accounting Adjustments because TrackAbout generally refers to a clients' main business system as the 'Accounting System'.
+An Accounting Adjustment is a record that TrackAbout automatically creates to edit customer balances and ensure balance information stays in sync with the client's main businesses system. These are called Accounting Adjustments because TrackAbout generally refers to a clients' main business system as the 'Accounting System'.
 Example: If Customer B returns as asset that was out to Customer A then TrackAbout will create an Accounting Adjustment to remove the asset from the balance of Customer A.
 ==Active Assets==