Assets - Revision history

Jgullickson: /* Asset Classification */

2022-07-14T17:00:50Z

Asset Classification

Jgreco: Proofread - greco

2021-11-12T17:32:56Z

Proofread - greco

Yrobinet at 14:16, 25 October 2011

2011-10-25T14:16:43Z

Tfusco at 16:51, 30 September 2009

2009-09-30T16:51:53Z

Tfusco: /* Product Code */

2009-09-30T16:51:09Z

Product Code

Lsilverman at 20:08, 10 January 2009

2009-01-10T20:08:24Z

Lsilverman at 20:06, 10 January 2009

2009-01-10T20:06:13Z

Lsilverman at 20:03, 10 January 2009

2009-01-10T20:03:20Z

Lsilverman: New page: Asset Classifications (Category, Group, Type) Product Codes and Product Code Mapping Asset Families Serial Number Collection Rules Volume/Weight Collection Rules

2009-01-10T19:09:31Z

New page: Asset Classifications (Category, Group, Type) Product Codes and Product Code Mapping Asset Families Serial Number Collection Rules Volume/Weight Collection Rules

New page

Asset Classifications (Category, Group, Type)

Product Codes and Product Code Mapping

Asset Families

Serial Number Collection Rules

Volume/Weight Collection Rules

@@ Line 6: / Line 6: @@
 == Asset Classification ==
-TrackAbout requires that you categorize each tracked asset into a three-level hierarchy.
+TrackAbout requires that you categorize each tracked asset into a four-level hierarchy.
 :Category
 ::Group
 :::Type
 Product codes must be mapped to a Type. Whenever new product codes are introduced to TrackAbout, such as through various integration points to your back office systems, the new product codes must be mapped to Types.
 The mapping of product codes to types allows TrackAbout to understand the information that comes in from your back office system, and properly categorize assets.
 ==[[Adding Asset Classes and Product Codes]]==

@@ Line 1: / Line 1: @@
 == What Is an Asset? ==
-An asset is any physical object that you wish to track using TrackAbout.  TrackAbout uses a globally unique identifier to individually track each and every asset.  Typically, this unique identifier is either a barcode label or an RFID tag.
+An asset is any physical object that you wish to track using TrackAbout. TrackAbout uses a globally unique identifier to individually track each and every asset. Typically, this unique identifier is either a barcode label or an RFID tag.
 == Product Code ==
@@ Line 11: / Line 11: @@
 :::Type
-Product codes must be mapped to a Type.  Whenever new product codes are introduced to TrackAbout, such as through various integration points to your back office systems, the new product codes must be mapped to Types.
+Product codes must be mapped to a Type. Whenever new product codes are introduced to TrackAbout, such as through various integration points to your back office systems, the new product codes must be mapped to Types.
 The mapping of product codes to types allows TrackAbout to understand the information that comes in from your back office system, and properly categorize assets.

← Older revision		Revision as of 14:16, 25 October 2011
Line 20:		Line 20:
	:::Type		:::Type
	::::Product Code		::::Product Code
		+
		+	==[[Adding Asset Classes and Product Codes]]==

← Older revision		Revision as of 16:51, 30 September 2009
Line 20:		Line 20:
	:::Type		:::Type
	::::Product Code		::::Product Code
−
−	~~== Asset Families ==~~
−
−	~~== Serial Number Collection Rules ==~~
−
−	~~== Volume/Weight Collection Rules ==~~

@@ Line 3: / Line 3: @@
 == Product Code ==
-A product code is the same thing as your part number, SKU, or catalog ID.
+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.
 == Asset Classification ==

@@ Line 7: / Line 7: @@
 == Asset Classifications ==
 TrackAbout requires that you categorize each tracked asset into a three-level hierarchy.
-# Category
+:Category
-# Group
+::Group
-# Type
+:::Type
-This hierarchy provides for richer reporting and tracking within TrackAbout.
+Product codes must be mapped to a Type.  Whenever new product codes are introduced to TrackAbout, such as through various integration points to your back office systems, the new product codes must be mapped to Types.
 == Asset Families ==