To be notified when parts needed for a service call are available via used/returned equipment designated for parts use.
Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Overview
Overview
When a machine is removed from service the suggested practice is to remove all salvageable parts and put them into inventory at $0 for future use. Sometimes this takes a while, however, as often techs will work on it when they 'have nothing better to do.' This alert will advise you when a call is placed on hold for parts and you have equipment of the same model awaiting parts harvest. It also provides awareness of parts which can be used on multiple models. For instance if the call in question is for a C7000 and you happen to have a C6000 awaiting salvage and the two share the part in common, you will be notified to check.
Run Schedule: every 20-minutes
Type of Output: Email
* * *
Sample
Sample
* * *
Variables
Variables
Variable W: Enter Equipment Status Code(s) assigned to machines awaiting parts harvest (separated by comma or leave blank for ALL) MUST have at least one entry for either VarW or Var1
OR (please note alert will fire on equipment containting Status Code OR Condition Code per your subscription.
Variable 1: Enter Equipment Condition Code(s) assigned to machines awaiting parts harvest (separated by comma or leave blank for ALL) MUST have at least one entry for either VarW or Var1
Status and Condition Code seen here on Equipment Record:
Variable X: Enter On Hold Code(s) used for service call waiting on parts (WP is assumed, no need to list it)
Variable Y: Enter Minimum Average Cost of parts to trigger on
Variable 2: Enter Item Category(ies) to exclude from consideration (separated by comma or leave blank for ALL)
*Best used for Items you will never re-use
Variable Z: Enter Custom Property on Model Record to identify other like model (essentially the same chassis - they take all the same parts/supplies) under a different branding or with very minimal differences. Format is a drop-down list of all Models. So if, for instance, the Ricoh 7500 and Savin 7500x are the same model but listed under two different Models in eAuto you set the custom property on the 'alternate' to point to the 'primary'; however you make that determination. (If you determine that the Ricoh 7500 is the primary, then the custom property would be set on the Savin machine as "Ricoh 7500" and it would be the alternate machine) Note: the alert is also smart enough to figure out that if machine A and machine C both point to B as the primary, then a call on a C can take parts from an A carcass. Max of three alternates available.
**Please see below on how to create this Custom Property in eAuto (this alert auto installs so we do not auto create the Custom Property for you)
Variable 3: Enter Branch Numbers to trigger on (separated by comma or leave blank for ALL).
* * *
Alert Functionality
Alert Functionality
-Does not require the machine removed from service (carcass) be an active equipment record nor a host.
-Alert assumes when you designate a machine for salvage, you change its equipment Status and/or Condition. Alert considers either/or Status or Condition Code(s) you've entered in variables. It will not consider both Status and Condition be present on Equipment Record.
-If the Item is available in Tech's Warehouse or Tech's Parent Warehouse, then alert won't report on that item as there would be no need to pull off a salvaged machine. If tech as no assigned Parent Warehouse AND item is not available in Tech's Warehouse, then alert will fire on that item.
-Alert looks to the Branch on the Service Call. It considers all qualifying carcasses and does not exclude them based on the branch on the equipment record or warehouse.
* * *
Best Practices & Tips
Best Practices & Tips
-Use THIS LINK on creating these Equipment Statuses in eAutomate
-Carcass location is the warehouse, assuming it's in inventory, else the location of the Equipment Record. Best practice is for carcasses to remain in inventory until completely stripped and written off, although we have heard a couple of people argue for doing it the other way around.
Custom Property (required for VariableZ):
This alert relies on Custom Property listed in your VariableZ (defaults to ZCJ_ModelSameAs). You can name the Custom Property anything you like, just be sure your VariableZ is populated with the name you assign to the Custom Property Attribute in eAuto.
Step 1:
Create the Attribute via Lists & Codes / Attributes / New
Name = ZCJ_ModelSameAs
Description = Identifies mostly-identical models under different Model #s
Data Type = Lookup
Lookup Type = IC_Models
Step 2:
Link this Attribute to Configuration for Models
Select Configurations (custom properties) from Lists & Codes
Select Model Tracking Configuration from List
Quick Add ZCJ_ModelSameAs to Configuration List, select OK to save
You will then see Custom Property available on Model Record:
* * *
Related Alerts
Related Alerts
ID500 - Items in stock at risk of becoming Obsolete due to Model Population/Volume decrease
* * *
0 Comments