Getting dollars back for parts that don't meet warranty is the most obvious ROI for our services, we have many clients where we flag over $100K per month and our average is $35K. We do this by looking at 4 conditions - Days, Core Returnable, Clicks and does the cost exceed the vendor cutoff.
This alert fires within 10 minutes of when the call is marked complete, not when invoiced.
For best practice, see HERE
For crediting contract & tech, see HERE
If we are telling you about a Canon part costing $100 and you know Canon has a minimum of $300 ensure you have minimums and warranty days set at the make level, details here.
Note that Juice can help with clean up and set up of items, see here.
Keep in mind that the logic for this alert assumes that if the manufacturer covers the machine as a unit then it would be covered PERIOD (as long as it is within the warranty date). If the machine is no longer covered as a unit then you fall back to parts level, where the manufacturer only covers certain parts with lots of conditions and that's where the price (ZCJMakeWtyMinCost) would come into consideration. See these two alerts for Equipment (not Item) warranties;
ID561 New Call Opened for Equipment Still Under Warranty
ID443 Alert At The End Of The Day For Closed Calls With Equipment Still Under Warranty
We include a custom report and once set up is complete you can look back over previous years. Just because a parts is not covered under a manufacturer's program or that the 2% discount you get is supposed to cover parts under $300 does not mean you shouldn't claim. We've had lots of dealers report success in getting dollars back when they have been able to prove the part has been failing early across your fleet.
We understand this logic may not be true for every manufacturer which is why we're moving towards the model of a different version of this logic for each major manufacturer. See ID919 for Konica Minolta specific version and ID921 for Canon/HP specific version.
Sample alert looks like this:
Note: (1) Trigger Action column will explain which of the 3 triggers was used. (2) If there is no record of that item being used in the past on that equipment we will assume it was installed new with the equipment and use the (3) install date. This can cause problems if you use the install date to record when that equipment went on your contract. (4) Actual Yield % calculated is VarX times the yield per the Item Record.
This alert is meant to use as much consistent logic as possible to look at parts used on services calls and try and determine if a part is eligible for warranty either because it failed to reach the Manufacturer’s Yield Spec OR the number of warranty days. There are a lot of variables that differ between not only manufacturers, but also between types of part. The logic to determine what parts you are alerted on will look at three distinct possibilities:
Condition# 1 is met (see detail below)
OR
Condition#2 is met (see detail below)
OR
Condition#3 is met (see detail below)
The variable to drive this task are as follows:
VariableX =% of the Item Yield in e-automate to reduce the target yield (ie: .95 means if item reached 95% of the manufacturer’s yield then you don’t want that item to be flagged as within warranty). We suggest you leave this at .95.
The alert will run every 15 minutes on calls marked COMPLETED. We feel a best practice is to have the notification sent to your parts person not just the technician. We also suggest you have a policy that the technicians bring ALL parts back, have a box with each techs name that the parts person reviews daily.
There is a custom report we will also install so you can run on demand by date range and other perimeters, a great tool to use when reviewing with you manufacturer and parts that are consistently failing early.
Condition#1: Did item fall below the manufacturer’s guaranteed yield?
The Copy Yield Value in the Item must be > 0 (use alert ID189 to ensure you have yields set). To ensure all items have been reviewed we suggest adding a 2 as yield value for items that do not have any warranty. There are a set of conditions where eAuto will default to a 1 so we suggest you avoid a 1.
AND
The actual clicks between last service call item was used on for same machine, or install meter reading is < the Copy Yield Value in the Item
AND
The item’s avgcost (each) is > the Warranty Eligible Cost value specified in the Custom Property Attribute for the Make of the equipment part was used on.
(**Please note these Custom Properties must be set up with Data Type of 'numeric.):
Condition#2: Did the item reach the warranty days set in the Make custom property?
The Days Value in the equipment Model’s Make Custom Property Attribute (ex: ZCJMakeDays) must be > 0
AND
The item’s avgcost (each) is > the Warranty Eligible Cost value specified in the Custom Property Attribute for the Make of the equipment part was used on.
Condition#3: Is the item flagged as “returnable” in e-automate. That checkbox indicates the item is a “core”, something your vendor will charge you for it they don't get the old one back and should always be returned by the tech regardless of any other condition b/c you need to return that “core” to the supplier for core credit. **This condition is optional and can be excluded by updating Var1 of your subscription to NO**
Use alert ID189 to ensure you have yields set. A note on setting yields - if an item doesn't have a yield in the traditional sense (for instance boards) but you want it to be monitored by the alert set it to Yield=2. Even though it will never trigger for condition #1 (number of copies) it will still trigger if it fails to meet the number of days specified in the Custom Property on the Make.
We provide a custom report that can be run from EA, once your items are set up you can take a look back at the last few years to see which parts are failing. See here for the custom report, this is a good tool to have before meeting with your manufacturer.
We are working on manufacturer specific variations of this alert, please suggest any. See ID919 for Konica and ID921 for Canon version.
0 Comments