Collisions - Revision history

Jgreco: Proofread - greco

2021-11-18T20:04:30Z

Proofread - greco

Lpickett: /* Resolving Collisions */

2018-03-13T12:56:18Z

Resolving Collisions

Jwolbert at 03:59, 21 June 2016

2016-06-21T03:59:02Z

Jwolbert: /* Resolving Collisions */

2016-03-03T13:13:31Z

Resolving Collisions

Jwolbert: /* Resolving Collisions */

2016-03-03T13:09:14Z

Resolving Collisions

Yrobinet: /* Reducing Client Collisions using Asset Family Collection Reclassification Groups */

2013-12-31T15:01:10Z

Reducing Client Collisions using Asset Family Collection Reclassification Groups

Yrobinet: /* The basic idea */

2013-12-31T14:55:54Z

The basic idea

Yrobinet: /* Collision Rules */

2013-12-31T14:39:02Z

Collision Rules

Jwolbert at 14:21, 17 September 2013

2013-09-17T14:21:19Z

Jwolbert: /* Resolving Collisions */

2012-09-20T19:45:24Z

Resolving Collisions

@@ Line 8: / Line 8: @@
-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. <br>
+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 caused by 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. <br />
 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. <br>
-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.
+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 on its own with no user intervention, and no actual collision will be created.
-==Collisions as a part of daily Trackabout Maintenance==
+==Collisions as a part of daily TrackAbout Maintenance==
-Resolving Collisions should take place as a part of regular daily Trackabout maintenance.
+Resolving Collisions should take place as a part of regular daily TrackAbout maintenance.
-Client personnel responsible for Trackabout administration should regularly monitor the Trackabout Dashboard to address any outstanding issues that may exist in the system.
+Client personnel responsible for TrackAbout administration should regularly monitor the TrackAbout Dashboard to address any outstanding issues that may exist in the system.
-[[File:TAmenu.jpg|thumb|left]] Access the Trackabout Dashboard through the Menu on the Homepage under '''Regular Maintenance --> Trackabout Dashboard'''.<br>
+[[File:TAmenu.jpg|thumb|left]] Access the TrackAbout Dashboard through the Menu on the Homepage under '''Regular Maintenance --> TrackAbout Dashboard'''.<br />
-It is important to start on issues listed at the top of the dashboard and work your way down.  Often resolving particular issues will have a ripple effect which will result in resolving other issues.  Collisions are listed under the “Location-Dependent” Items. <br>
+It is important to start on issues listed at the top of the dashboard and work your way down. Often resolving particular issues will have a ripple effect which will result in resolving other issues. Collisions are listed under the “Location-Dependent” Items. <br />
-<br>
+<br />
-Click on the blue link called “View Collisions”.  You can also get to the collisions page through the JumpTo Box and type Collisions, or use the URL:
+Click on the blue link called “View Collisions”. You can also get to the collisions page through the JumpTo Box and type Collisions, or use the URL:
 https://www.trackabout.com/clt/reconciliation/unresolvedProblems.aspx <br>
 [[File:CollisionsOnDashboard.jpg|center|500px]]
 ==Resolving Collisions==
-'''NOTE:  It’s important to understand the asset on the record which caused the collision will not have the asset attached until the collision is resolved – TrackAbout doesn’t know what to do with it.  This is why it is imperative to make sure collisions are resolved'''
+'''NOTE: It’s important to understand the asset on the record which caused the collision will not have the asset attached until the collision is resolved – TrackAbout doesn’t know what to do with it. This is why it is imperative to make sure collisions are resolved'''
 [[File:SearchingForCollisions.jpg|left|border|300px]]
-From the collisions page, you may choose a particular location and/or date range, or you may search for all existing collisions by leaving the Location parameter set to “All Locations” and leave the date range blank.
+From the Collisions page, you may choose a particular location and/or date range, or you may search for all existing collisions by leaving the Location parameter set to “All Locations” and leave the date range blank.
-Now you will see a list of collisions that could not be auto-verified by the system.  From that page, click on the Resolve Selected Collisions ('''all collisions should be checked'''). This will take you to each collision, one screen at a time, and display the issue, offering a way to resolve.
+Now you will see a list of collisions that could not be auto-verified by the system. From that page, click  Resolve Selected Collisions ('''all collisions should be checked'''). This will take you to each collision, one screen at a time, and display the issue, offering a way to resolve.
@@ Line 46: / Line 44: @@
-After clicking “Resolve Selected Collisions”, a new box will pop up.  The Collision resolution screen will be divided into three basic parts:
+After clicking “Resolve Selected Collisions”, a new box will pop up. The Collision resolution screen is divided into three basic parts:
@@ Line 59: / Line 57: @@
-'''NOTE:'''If the users chooses multiple assets, the system will display a warning to ensure the user understands those assets and their histories will be merged.
+'''NOTE:''' If the users chooses multiple assets, the system will display a warning to ensure the user understands those assets and their histories will be merged.
@@ Line 65: / Line 63: @@
 #Create and Attach a New Asset - You have determined that the asset in the action which caused the collision, as shown in the top section of the page, is not any of the Potential Asset Matches which have been presented. The asset shown at the top of the page is, in fact, a brand new asset. Choosing this option will create a new asset.
-#Delete the Collision Permanently - You have determined that the action which caused the collision, as shown in the top section of the page, should not have happened to the asset. If this was the only asset on the action, choosing this option will remove the action as though it never happened. If there are other assets on the action, then choosing this option will detach the asset which caused the collision, as though that asset had never been on the action.
 #Do Nothing at this time - Choosing this option will leave the collision. It is common to choose this option when you're not sure what the truth is, and you need to do some more research before determining what the correct course of action should be. While it is important to resolve collisions quickly so that your data is correct and more collisions aren't caused, it is also important that collisions be resolved accurately. This option will allow you to come back to this collision later when you have more information.
@@ Line 80: / Line 80: @@
 There are a series of rules that may get applied depending on the record properties. The main rules that get applied are as follows:
-*If we find assets that match on the Serial Number only, but the Asset Type, Barcode and location do not match, the they are ignored and not considered as a match.
+*If we find assets that match on the Serial Number only, but the Asset Type, Barcode, and location do not match, the assets are ignored and not considered a match.
 *If both the Barcode and Serial Number were entered by the user, and there is exactly one asset that matches both the Barcode and the Serial Number, then other asset matching on just the Barcode or just the Serial Number are ignored.
 *If multiple assets are found having the same Barcode, we try to merge them together provided they do not have conflicting properties for Serial Number, Ownership, Custom Asset Info, etc.

@@ Line 64: / Line 64: @@
 *The bottom section gives three alternatives to selecting one or more of the Possible Asset Matches.
-#Create and Attach a New Asset
+#Create and Attach a New Asset - You have determined that the asset in the action which caused the collision, as shown in the top section of the page, is not any of the Potential Asset Matches which have been presented. The asset shown at the top of the page is, in fact, a brand new asset. Choosing this option will create a new asset.
-#Delete the Collision Permanently
+#Delete the Collision Permanently - You have determined that the action which caused the collision, as shown in the top section of the page, should not have happened to the asset. If this was the only asset on the action, choosing this option will remove the action as though it never happened. If there are other assets on the action, then choosing this option will detach the asset which caused the collision, as though that asset had never been on the action.
-#Do Nothing at this time
+#Do Nothing at this time - Choosing this option will leave the collision. It is common to choose this option when you're not sure what the truth is, and you need to do some more research before determining what the correct course of action should be. While it is important to resolve collisions quickly so that your data is correct and more collisions aren't caused, it is also important that collisions be resolved accurately. This option will allow you to come back to this collision later when you have more information.

← Older revision		Revision as of 03:59, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Parent Module=Core Tracking
		+	\|Feature Description=This automated feature helps prevent duplicated information in your system.
		+	}}
	[[Key Concepts\|<< Back to Key Concepts]]		[[Key Concepts\|<< Back to Key Concepts]]

@@ Line 32: / Line 32: @@
 '''NOTE:  It’s important to understand the asset on the record which caused the collision will not have the asset attached until the collision is resolved – TrackAbout doesn’t know what to do with it.  This is why it is imperative to make sure collisions are resolved'''
 [[File:SearchingForCollisions.jpg|left|border|300px]]
 From the collisions page, you may choose a particular location and/or date range, or you may search for all existing collisions by leaving the Location parameter set to “All Locations” and leave the date range blank.
@@ Line 37: / Line 38: @@
 Now you will see a list of collisions that could not be auto-verified by the system.  From that page, click on the Resolve Selected Collisions ('''all collisions should be checked'''). This will take you to each collision, one screen at a time, and display the issue, offering a way to resolve.
-[[File:SelectingCollisions.jpg|right|500px]]
 After clicking “Resolve Selected Collisions”, a new box will pop up.  The Collision resolution screen will be divided into three basic parts:
-[[File:Collsion_Top.jpg|left|300px]]<br>
 * The middle section shows any possible asset matches and gives the option to merge the asset history/histories with the asset which caused the collision.
 '''NOTE:'''If the users chooses multiple assets, the system will display a warning to ensure the user understands those assets and their histories will be merged.
-*The bottom section gives options other than selecting one or more of the Possible Asset Matches. <br>
 [[File:Collision Options.png|300px]]

← Older revision		Revision as of 13:09, 3 March 2016
Line 49:		Line 49:

	'''NOTE:'''If the users chooses multiple assets, the system will display a warning to ensure the user understands those assets and their histories will be merged.		'''NOTE:'''If the users chooses multiple assets, the system will display a warning to ensure the user understands those assets and their histories will be merged.
		+
	*The bottom section gives options other than selecting one or more of the Possible Asset Matches. <br>		*The bottom section gives options other than selecting one or more of the Possible Asset Matches. <br>
		+
		+	[[File:Collision Options.png\|300px]]

← Older revision		Revision as of 15:01, 31 December 2013
Line 68:		Line 68:

	==Reducing Client Collisions using ''Asset Family Collection Reclassification Groups''==		==Reducing Client Collisions using ''Asset Family Collection Reclassification Groups''==
−	~~===~~The basic idea~~===~~	+	The basic idea is that we can make TrackAbout smarter by knowing which kind of assets can 'turn into' other kinds of assets. Only assets of the same type should be causing collisions. More about this feature on this page [[Reducing Client Collisions using Asset Family Collection Reclassification Groups]].
−	*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~~.
−	[[~~File:Same_SN_different_asset_type.png\|600px\|Serial number K104~~]]
−	*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.

@@ Line 73: / Line 73: @@
 *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.
+[[File:Same_SN_different_asset_type.png|600px|Serial number K104]]
 *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.

← Older revision		Revision as of 14:39, 31 December 2013
Line 66:		Line 66:
	*For an Action where both the Barcode and the Serial Number were entered for the asset causing the collision, and if there is just one match in the past and it matches the Serial Number and the Asset Type (if entered) AND there is just one match in the future and it matches the Barcode, then the assets will be merged together and the collision auto-resolved.		*For an Action where both the Barcode and the Serial Number were entered for the asset causing the collision, and if there is just one match in the past and it matches the Serial Number and the Asset Type (if entered) AND there is just one match in the future and it matches the Barcode, then the assets will be merged together and the collision auto-resolved.
	*If only one asset is found matching the Barcode, but the Barcode is not the current Barcode of the asset, it causes a collision.		*If only one asset is found matching the Barcode, but the Barcode is not the current Barcode of the asset, it causes a collision.
		+
		+	==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.
		+
		+	[[File:XXX.png\|thumb\|none\|right\|IMAGE COMING SOON]]
		+
		+	*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.

← Older revision		Revision as of 14:21, 17 September 2013
Line 55:		Line 55:

	Note: TrackAbout support has a way to bulk hide collisions. 'Hidden' collisions don't go away, but they are no longer shown on the Collisions page or on the counts on the Dashboard. You'd still find them if you went directly to the records that have the collisions on them.		Note: TrackAbout support has a way to bulk hide collisions. 'Hidden' collisions don't go away, but they are no longer shown on the Collisions page or on the counts on the Dashboard. You'd still find them if you went directly to the records that have the collisions on them.
		+
		+	== Collision Rules ==
		+
		+	There are a series of rules that may get applied depending on the record properties. The main rules that get applied are as follows:
		+
		+	*If we find assets that match on the Serial Number only, but the Asset Type, Barcode and location do not match, the they are ignored and not considered as a match.
		+	*If both the Barcode and Serial Number were entered by the user, and there is exactly one asset that matches both the Barcode and the Serial Number, then other asset matching on just the Barcode or just the Serial Number are ignored.
		+	*If multiple assets are found having the same Barcode, we try to merge them together provided they do not have conflicting properties for Serial Number, Ownership, Custom Asset Info, etc.
		+	*For a Replace Barcode action, if there is just one match in the past and it matches on the Old Barcode AND there is just one match in the future and it matches on the New Barcode , then the collision will be auto-resolved, merging the two assets together.
		+	*For an Action where both the Barcode and the Serial Number were entered for the asset causing the collision, and if there is just one match in the past and it matches the Serial Number and the Asset Type (if entered) AND there is just one match in the future and it matches the Barcode, then the assets will be merged together and the collision auto-resolved.
		+	*If only one asset is found matching the Barcode, but the Barcode is not the current Barcode of the asset, it causes a collision.