Use States - Revision history

Jgullickson: /* Setting Use State Based on Location or Customer */

2021-04-08T03:20:17Z

Setting Use State Based on Location or Customer

Jwolbert at 03:43, 21 June 2016

2016-06-21T03:43:09Z

Jwolbert: /* Available Use States */

2016-05-25T21:28:41Z

Available Use States

Jwolbert at 21:27, 25 May 2016

2016-05-25T21:27:57Z

Jwolbert at 18:39, 12 May 2016

2016-05-12T18:39:23Z

Eschurdak: /* How Assets Change Use States */

2015-02-23T21:10:00Z

How Assets Change Use States

Lpickett: /* Use State Validation */

2015-01-07T14:35:25Z

Use State Validation

Lpickett: /* Why use Use States? */

2015-01-07T14:33:00Z

Why use Use States?

Lpickett: /* Example of a Typical Asset Cycle */

2015-01-07T14:31:34Z

Example of a Typical Asset Cycle

Eschurdak at 19:01, 2 January 2015

2015-01-02T19:01:05Z

← Older revision		Revision as of 03:20, 8 April 2021
Line 186:		Line 186:

	To enable Location/Customer-based Default Use States for locations or customers, contact [[Contact Us\|TrackAbout Support]].		To enable Location/Customer-based Default Use States for locations or customers, contact [[Contact Us\|TrackAbout Support]].
		+
		+	===Use State Fall Backs ===
		+
		+	For some client business processes, having just one resulting Use State for an Action is insufficient. TrackAbout provides '''Use State Fallbacks''' which allow us to revert an asset's Use State back to a previous Use State that is appropriate for the asset.
		+
		+	For instance, consider a client who uses Branch Transfers. They load full and empty assets onto a Truck, setting the use state to be '''In Transit'''. When they are transferred to the recipient branch and unloaded, the Unload Truck action doesn't change an assets' Use State at all.
		+
		+	This means that all of our assets that were Loaded and Transferred, will still be in a Use State of "In Transit" when they come off the truck. However, the recipient branch will need to be able to use them! We need the assets' Use States to reflect whatever they were BEFORE the Load Truck (likely something like Full, Empty or Maintenance). Therefore, the Use State Fallback is used to revert the Use State back to what it was BEFORE the Load Truck.

	==Why use Use States?==		==Why use Use States?==

← Older revision		Revision as of 03:43, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Parent Module=Core Tracking
		+	\|Feature Description=A Use State describes the status or condition of an asset.
		+	\|Supported In=TAMobile 6 Desktop, TAMobile 6 Rugged, TAMobile Android, TAMobile iOS
		+	}}
	[[Category:TrackAbout Feature]]		[[Category:TrackAbout Feature]]
	==What are Use States?==		==What are Use States?==

@@ Line 84: / Line 84: @@
+|
 |-
+|}
 ==How Assets Change Use States==

@@ Line 72: / Line 72: @@
+|
 |-
-|}
+|Blocked
 ==How Assets Change Use States==

← Older revision		Revision as of 18:39, 12 May 2016
Line 1:		Line 1:
		+	[[Category:TrackAbout Feature]]
	==What are Use States?==		==What are Use States?==

← Older revision		Revision as of 21:10, 23 February 2015
Line 161:		Line 161:
	\|}		\|}

		+	===Setting Use State Based on Location or Customer===
		+
		+	In some cases, the location of the asset should determine what the use state of the asset is. For example, if an asset is at a certain location for maintenance, any asset that is set to that location should have it's use state set to Maintenance. This can be accomplished through the '''Location/Customer-based Default Use States''' feature. With this enabled, each location or customer can be configured to set the default use state for assets that are set to that location or customer.
		+
		+	Setting the use state based on location or customer is limited to those actions that do not typically set a use state (see table above). If an action is performed that normally does set a use state on the asset, the resulting use state of the action will override the default use state of the location or customer. For example, if a location is set to have a default use state of Empty, if a Fill is performed at that location, the use state of the assets in the fill will be set to Full or Ready for Use instead of empty.
		+
		+	To enable Location/Customer-based Default Use States for locations or customers, contact [[Contact Us\|TrackAbout Support]].

	==Why use Use States?==		==Why use Use States?==

@@ Line 184: / Line 184: @@
 [[File:Accepted Use States Example.png|center]]
-Notice that each action has a list of Use States that are allowed, and a list that are not. The asset's Use State is validated when it is scanned in the action. If the asset is in a valid Use State, it will be added to the action, if not, a warning will be given.
+Notice that each action has a list of Use States that are allowed, and a list that are not. The asset's Use State is validated when it is scanned in the action. If the asset is in a valid Use State, it will be added to the action; if not, a warning will be given.
 This feature, along with other business rules are available in the Palletization module. Contact your [[Contact Us|TrackAbout sales representative]] for more information on this module.

@@ Line 164: / Line 164: @@
 ==Why use Use States?==
-Used with the reports available in TrackAbout, use states provide another level of insight into your asset inventory by showing how many assets are in each step of the asset life cycle. In some TrackAbout modules, use states are also used to force assets to go through a specific process by by only allowing assets with certain use states to be valid for certain actions.
+Used with the reports available in TrackAbout, use states provide another level of insight into your asset inventory by showing how many assets are in each step of the asset life cycle. In some TrackAbout modules, use states are also used to force assets to go through a specific process by allowing only assets with certain use states to be valid for certain actions.
 ===Use States for Reporting===

@@ Line 82: / Line 82: @@
 In the example above, you can see that each action results in a Use State that stays on the asset until the next action occurs. Filled goes to Ready for Use, Load Truck goes to Committed for Delivery and so on. Add New and Unload Truck are different though, because they each set a Use State of "No Change" on the assets.
-Every action in TrackAbout changes some aspect about the assets scanned in the action. Some of these actions change the state of the asset, but other actions change other aspects of the asset but not its condition. For example, a Locate action changes the location of the asset, but it will not change the state of the asset, because simply moving the asset from one location to another does not change its state. In cases like this, the actions actually set a Use State of No Change, and whenever you view the asset, you will see the last Use State that was set on the asset. So if you unload an asset from a truck that is no longer ready for use, the Use State on the asset will still be Not Ready for Use In the tables below, you can see the actions that typically change the Use State on an asset, and which do not.
+Every action in TrackAbout changes some aspect about the assets scanned in the action. Some of these actions change the state of the asset, but other actions change other aspects of the asset but not its condition. For example, a Locate action changes the location of the asset, but it will not change the state of the asset, because simply moving the asset from one location to another does not change its state. In cases like this, the actions actually set a Use State of No Change, and whenever you view the asset, you will see the last Use State that was set on the asset. So if you unload an asset from a truck that is no longer ready for use, the Use State on the asset will still be Not Ready for Use. In the tables below, you can see the actions that typically change the Use State on an asset, and which do not.
 ===Actions that Typically Set a Use State===

← Older revision		Revision as of 19:01, 2 January 2015
Line 179:		Line 179:

	===Use State Validation===		===Use State Validation===
		+
		+	Use States can also be used to ensure that an asset follows a certain flow as it moves throughout the plant and back out to the customer. This is done by only allowing assets of certain Use States to be valid for particular actions.
		+
		+	[[File:Accepted Use States Example.png\|center]]
		+
		+	Notice that each action has a list of Use States that are allowed, and a list that are not. The asset's Use State is validated when it is scanned in the action. If the asset is in a valid Use State, it will be added to the action, if not, a warning will be given.
		+
		+	This feature, along with other business rules are available in the Palletization module. Contact your [[Contact Us\|TrackAbout sales representative]] for more information on this module.