Reducing Client Collisions using Asset Family Collection Reclassification Groups

The basic idea

• If there is an asset in the system with a serial number and a new asset is added with this same serial number, then TrackAbout will cause a collision. The user must decide if they are the same asset or different assets.
• Collisions are cases where the system is not smart enough to know what happened and we need a human to make a decision. With this feature we are making the system smarter and reducing the cases we show to a person.
• We can make TrackAbout smarter here by knowing which kind of assets can 'turn into' other kinds of assets.
• See this picture below. If there is a gas cylinder with serial number K104 in the system and then someone enters a new welding machine also with serial number K104 - normally TrackAbout will cause a collision. The idea here is to let TrackAbout know that these assets can not 'turn into' each other and so there is no reason to create a collision. TrackAbout should create the new welding machine asset. It is not the same as the gas cylinder.

• The gas cylinder and the welding machine will be in different "Reclassification Groups" and this is how TA knows that there is no reason for a collision. A new asset should be created instead.

Customer Setup

Several steps are require to configure your system:

1. Create new Asset Family Collection(s):
   1. Instructions: Asset_Families https://meta.trackabout.com/wiki/index.php/Asset_Families
   2. AWS Page: https://www.trackabout.com/clt/setup/listAssetFamilyCollections.aspx

Create Asset Families - Asset with compatible gases should be grouped in a family. AWS link: https://www.trackabout.com/clt/setup/listAssetFamilies.aspx Add new “Asset Family Collection Reclassification Group” (AFCRG). To associate groups with an asset family collection, use the edit page for that collection. AWS link: https://www.trackabout.com/clt/setup/listAssetFamilyCollectionTags.aspx

A Reclassification Group is a group of asset families collections that are compatible and will trigger a collision within it’s members. In other words: "Given two assets which would otherwise cause a collision, if any reclassification group tags on their associated asset families differ, the collision will not be created." If reclassification groups differ between two asset family collections, we know that the asset families within those collections are not compatible with each other and therefore the colliding serial numbers cannot possibly be referring to the same asset. (Imagine a serial number which refers to a medical oxygen cylinder as well as an acetylene cylinder - we know medical oxygen would never be filled with acetylene, thus we know the SN must be referring to different cylinders and we can avoid the collision.)

�

Example

Additional Notes - Please read

• A product code can belong to more than one Asset Family
• Asset Family Collections can belong to multiple “Asset Family Collection Reclassification Group”
• Note that if an asset family collection under consideration does not have any reclassification groups associated with it, we do not eliminate the collision. (I.e. if Asset1 is in reclassification group "RG1" and Asset2 doesn't have any reclassification groups, technically those groups differ but we don't eliminate the collision.) Each involved asset's asset family collection must have at least one reclassification group associated with it in order to be considered for collision avoidance using this logic.
• If an asset has no reclassification groups associated with its asset family collection, then TrackAbout can create a collision.
• After setup, we do not have a way to re-run the collision logic on unresolved collisions. Subha might have an idea for this