Stopped Assets - Revision history

Sdigon at 15:53, 14 March 2022

2022-03-14T15:53:59Z

Sdigon: /* Recall */

2022-03-14T15:22:40Z

Recall

Sbecker at 21:47, 29 July 2020

2020-07-29T21:47:20Z

Jwolbert at 03:42, 21 June 2016

2016-06-21T03:42:09Z

Jwolbert at 18:55, 12 May 2016

2016-05-12T18:55:02Z

Jwolbert: /* Register Complaint/Recall/Block for Cylinders */

2016-03-31T19:17:41Z

Jwolbert: /* Block */

2016-03-31T18:29:33Z

Block

Jwolbert: /* Use States */

2016-03-31T17:42:42Z

Use States

Jwolbert: /* Use States */

2016-03-31T17:42:10Z

Use States

Jwolbert at 17:41, 31 March 2016

2016-03-31T17:41:50Z

@@ Line 16: / Line 16: @@
 * If a cylinder is marked as complaint/stopped and the record was saved wirelessly, the cylinder will not be eligible for delivery.
 * When a driver scans a stopped cylinder as a return on a delivery, we show the driver an alert message to let him/her know that the cylinder should go to maintenance.
 ==Complaint ==
 This is a feature available to operators during the handheld Proof of Delivery process.  Operators can act on specific cylinders by associating a customer complaint with the asset.
 The operator will only be permitted to proceed if assets have already been scanned onto the record as returns.  Otherwise, an error message will show and the operator will not be allowed to continue.
@@ Line 35: / Line 34: @@
 In each action, the operator will be required to select a reason before the action can be completed and saved.
 ==Block==
@@ Line 57: / Line 57: @@
 ===Loading Blocked Assets through integration===
 This feature is available to clients using basic delivery and not POD.  To use this feature, se expose an API endpoint to manage this data. (You need to be signed in to TrackAbout to access API endpoint information)
 ==Recall==
 Recall functionality is useful in cases such as Lot/Batch recalls.  In these scenarios, assets may be spread across your organization and out to customers.  This functionality allows you to update those assets so that they can come back from customers but they won't be permitted for most actions.
 When a driver scans an asset in a "Recall" status, they will be alerted that the asset should go straight to maintenance.
 Recalls can only be set from the website. See the section on [[Stopped_Assets#Register_Complaint.2FRecall.2FBlock_for_Cylinders|Register Complaint/Recall/Block ]]
@@ Line 89: / Line 85: @@
 •Complaint ¬– use state of Complaint
 •Recall – use state of Recall.  Assets that have a Recall use state, when picked up from a customer, will alert the driver that the asset being picked up has been blocked, but can still be returned
 == Removing a Complaint / Block / Recall ==
 The Clear Complaint / Block Maintenance sub-actions are used to return "Stopped" assets to circulation.

@@ Line 77: / Line 77: @@
 *You can add assets by entering a Barcode or by Serial Number
-[[File:Register Complaint AWS.png|400px]]
+[[File:Register Complaint Recall Block.PNG|400px]]
 When you submit this page by clicking the Save button, a new Complaint/Recall/Block Action record will be created based upon the selected stop reason and you will immediately link to the record's page

@@ Line 52: / Line 52: @@
 The asset is not registered in the system
 The asset is in an invalid Use State for block (such as it is already "Blocked")
-The asset is know to be part of a bundle or pack
+The asset is known to be part of a bundle or pack
 [[File:Block Asset Validation.png|400px]]

← Older revision		Revision as of 03:42, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Parent Module=Core Tracking
		+	\|Feature Description=The Block, Recall, and Complaint (Empty and Full) actions are all used as a way to "stop" an asset from being used by most TrackAbout actions.
		+	\|Supported In=TAMobile 6 Desktop, TAMobile 6 Rugged
		+	}}
	[[Category: TrackAbout Feature]]		[[Category: TrackAbout Feature]]
	==Stopped Assets==		==Stopped Assets==

← Older revision		Revision as of 18:55, 12 May 2016
Line 1:		Line 1:
−		+	[[Category: TrackAbout Feature]]
	==Stopped Assets==		==Stopped Assets==

@@ Line 68: / Line 68: @@
 This page allows you to register a Complaint/Recall/Block for one or more assets in the TrackAbout system
-You may override the Date & Time of the record you are creating.  Otherwise, the record will be created with the current Date & Time
+*You may override the Date & Time of the record you are creating.  Otherwise, the record will be created with the current Date & Time
-You can add assets by entering a Barcode
+[[File:Register Complaint AWS.png|400px]]
 When you submit this page by clicking the Save button, a new Complaint/Recall/Block Action record will be created based upon the selected stop reason and you will immediately link to the record's page
-Operators are required to select a reason for why the asset is being marked as '''Complaint/Recall/Block'''
+[[File:Complaint Record.png|400px]]
 For clients using asset Use States:
 Depending on the reason selected, the use state of the asset will be changed as follows:
-•	Block – use state of Blocked
+•Block – use state of Blocked
-•	Complaint ¬– use state of Complaint
+•Complaint ¬– use state of Complaint
-•	Recall – use state of Recall.  Assets that have a Recall use state, when picked up from a customer, will alert the driver that the asset being picked up has been blocked, but can still be returned
+•Recall – use state of Recall.  Assets that have a Recall use state, when picked up from a customer, will alert the driver that the asset being picked up has been blocked, but can still be returned
 == Removing a Complaint / Block / Recall ==

@@ Line 33: / Line 33: @@
 ==Block==
 The Block action is used to identify assets with issues and prevent them from being used in TrackAbout processes such as Filling, Sorting and Delivery.  Blocked assets must go through the maintenance process before returning to regular service.
 [[File:Block Assets Flow.png|400px]]
-===Block Asset Validation ===
+====Block Asset Validation ====
 The Block Assets actions can include wireless lookups. This means, when an operator scans an asset, TrackAbout will look for information specific to that asset and make sure it's valid for the action.
@@ Line 49: / Line 50: @@
 [[File:Block Asset Validation.png|400px]]
 ==Recall==

← Older revision		Revision as of 17:42, 31 March 2016
Line 91:		Line 91:
	[[File:Retired Use State.png\|400px]]		[[File:Retired Use State.png\|400px]]

−	Once in a Status of ''~~Retired~~'', the asset will not be permitted for use in most TAM6 handheld actions.	+	Once in a Status of ''Complaint'' or ''Blocked'', the asset will not be permitted for use in most TAM6 handheld actions.

@@ Line 85: / Line 85: @@
 * The system can also be configured to allow the user to select the resulting Use State for that asset.
-=== Use States ===
+== Use States ==
 For clients tracking asset [[Use_States|Use States]], upon completion of the Complaint or Block process, asset Use States will be updated to either '''Complaint''' or '''Block''' status

@@ Line 25: / Line 25: @@
 The asset will still be included in the Return record.  However, once saved to the website, the use state for the asset will change to Complaint and will not be permitted for use in most other processes until the Complaint is removed
 ==Block==
@@ Line 52: / Line 57: @@
 Recalls can only be set from the website. See the section on [[Stopped_Assets#Register_Complaint.2FRecall.2FBlock_for_Cylinders|Register Complaint/Recall/Block ]]
 ===Register Complaint/Recall/Block for Cylinders===