ID# | Description | Purpose | Links | Recommended | % Subscribed | Output Status | Output Type |
---|---|---|---|---|---|---|---|
106 | Process to be able to see in e-automate the accounts running FMAudit (In Development) | REQUIRES FMACENTRAL TO BE RUNNING LOCALLY ON YOUR INTERNAL SERVER! In an effort to easily identify within E-Automate which customers have FMAudit installed. The easiest way to do this so that it was viewable from e-automate was to create a specific model and then create an equipment record using this special Model for each customer that has FMAudit running. Then your users can just run an equipment list from within e-automate for Model = FMAudit . This process requires: 1) You create a Model called FMAudit 2) You create an equipment record in e-automate for that model 3) You maintain that Active status accurately for that model (If for some reason the account no longer is serviced by you..or you are not running FMAudit for example at the account..then you need to mark that equipment record for the account InActive ! | LinkedIn Documentation |
0 | 0.0152 | ||
118 | New Account(s) added to FMAudit today | To alert your FMAudit administrator of new accounts created within FMAudit that might need to be linked to e-automate and/or to your CRM system. (<span style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:11px;white-space:pre-wrap;background-color:#ffffff;">Only onsite installations of FMAudit Central are supported, as we need to be able to have direct access to the database.)</span> | LinkedIn Documentation |
0 | 0.0265 | ||
120 | FMAudit Accounts not linked to E-Automate or CRM system | This is to notify the appropriate person of all Accounts in FMAudit that are not linked to either E-Automate or your CRM solution. This alert is only applicable if your are linking FMAudit data to a CRM solution (Saleslogix / Goldmine / Compass /MS CRM). If you are not linking FMAudit to any CRM solution then this alert will not work as designed. | LinkedIn Documentation |
0 | 0.0096 | ||
122 | Closed Service Calls for FMAudit Installations | Installation of FMAudit in new accounts is the most critical part of implementing that system. Dealers who are having the most success with FMAudit have embraced the challenges of installing and maintaining the software in their accounts and use the dispatch system to create calls for their techs for installation. They do this creating specific calls for a specific problem code (FMInstall for example) so that they have a specific closed call as evidence that the software was installed and tested. They then can notify the appropriate personnel that FMAudit is in an account so that others can continue with their part of the process (linking the FMAudit records to e-automate, to their CRM, etc). This alert is only useful for dealerships who embrace the idea of a separate FMAudit call for the tech for the installation, and this alert is only for completed calls. There is a second alert to list all the FMAudit installs that failed. In order for these Contra alerts to work..how you setup the Problem codes for call resolution are critical. For example, they should all start with FM ...and you should have only one that is used to indicate a successful Install (FMInstall) for example..and you might have multiples to indicate problems that prevented the succesful install (FMPCProb, FMCustDecline, so on and so on for the level of detail you want to track ). | LinkedIn Documentation |
0 | 0.0278 | ||
123 | FMAudit Calls where installation was not successful | This is the contra alert for ID122 (Succesful FMAudit installs). ID122 works by reporting all the calls with the Problem code you specify in VariableW for that event, and that problemcode should indicate the successful installation. This alert is to report all the un-successful installations, so instead of listing all the possible reasons different dealerships might want to track, we use some logic around your Problem Codes. You would need to have all your FMAudit problem codes start with FM for example..and have only one of those problem codes indicate success...while all the others would be reasons why the install was not successful (pc issues, customer declined, firewall issues, etc..). Some Examples we've seen used are: FMREFUSE: FM AUDIT REFUSAL FROM THE CUSTOMER FMRDSI | LinkedIn Documentation |
0 | 0.0200 | ||
130 | Checks for FMAudit accounts to be linked to Eauto or SLX | <p>Checks for FMAudit accounts to be linked to Eauto or SLX </p> | LinkedIn Documentation |
0 | 0.0076 | ||
131 | Checks for FMAudit Accounts for an FMAudit Equipment record in eAutomate running FMAudit Onsite | <p>This alert looks directly into your FMAudit DB to determine which customer locations have a functioning FMAudit installation and comparing that to the Equipment Records for those installations inside eAutomate. The alert will report any customer location being monitored in FMAudit that does not have a corresponding Equipment Record. For this purpose an ‘FMAudit Equipment Record’ is simply an Active Equipment Record assigned to that location and of a specific Model. All the other details are at your discretion and may by modified to suit your individual business practice. </p><p>The installer will need to be informed of the dummy ‘Model’ in eAutomate that you are using to create these Equipment Records, that value will be hardcoded into the alert logic and is not something that can be controlled from the subscription on our website. The alert will not function, and in fact cannot be turned on, until we have that information coded in.</p> | LinkedIn Documentation |
0 | 0.0100 | ||
390 | Problems with meter collection software | To help monitor when a problem might be occurring with one of the meter capture tools. Alert to notify that VariableX meter readings are the exact same within VariableY days, where meter source is in VariableW list. (Separate the metersources in VariableW with a comma if you want multiple sources ie: PrintFleet, FMAudit. | LinkedIn Documentation |
0 | 0.0800 | ||
456 | Competitive device on network (in development) | Tools like FM Audit can track when new devices appear on your customer's network and perhaps identify a competitor installing equipment, especially if your equipment drops off and the competitor's equipment appears at the same IP address. We can look in the CRM to see the salesperson and notify them and managers immediately. Currently this alert is just for the local version of FM Audit but chase those guys to work with us if you want something else. | LinkedIn Documentation |
0 | 0.0800 | ||
925 | Toner not used in MIF (in Development) | <p>Most of the monitoring software can tell you when a unit has a new toner installed and lots of these same software promote shipping a new toner as soon as one is used. Most times toner goes on a shelf and not straight into a copier and a big concern is ensuring it goes into a machine on YOUR contract. Shipping too much toner is a bigger problem than not getting timely toner out. This process would look at all toner shipped on that contract, consider the multiple models on that contract that could take that toner, then look at what your monitoring software says was used by all the models under contract with you that could take that toner. Highlight the problems. </p><p>**Direct access (locally hosted) to you DCA required. </p> | LinkedIn Documentation |
0 | 0.0817 | ||
937 | Equipment no longer monitored by DCA | Keeping track of meters not reported by DCA (Data Collection Agent, i.e. FMAudit, PrintFleet) can be a labor intensive process for your staff and can easily be pushed down on the "to do" list, which means less revenue for your organization. This alert will show which equipment records that had previously been collected by DCA (or other automation pushing data into eAutomate) but are no longer being pushed in (they have 'fallen off' monitoring). (This alert runs Monday AM) | LinkedIn Documentation |
0 | 0.4682 | ||
949 | FM Audit Accounts and Devices Not Reporting (In Development) | <div style="text-align:left;"><p>To notify you when an Account in FMAudit has not reported in Variable1 days...and a second list of Devices that have not reported in Variable2 days . </p><p>The device list is important as it's intended to help you identify devices in FMAudit that show as 'managed', but the device has not reported in say 45 days. The list also indicates if that device is under an eautomate contract as well. Since you pay FMAudit for 'managed' devices, it's up to you to update FMAudit at least quarterly and turn off any devices that you no longer have under contract so that FMAudit will not bill you for those devices.</p></div> | LinkedIn Documentation |
0 | 0.0591 | ||
968 | Insert Meter Readings from External Sources | <p>Tools like FM Audit, Print Audit & Print Fleet have a lot of useful data but getting it filtered and to the correct people can be a challenge. We also see clients where the meter table size is out of control as various tools import all meters for all devices they monitor. </p><p>This process pushes meters from various DCAs as well as our other processes that import meters (ID398 for meters emailed for devices and ID311 for meters from MPSMonitor or HPSDS Action Center), reviews your variable Billing and Date Limiter settings, then only pushes to eAutomate those needed for billing, vastly reducing your meter table size. </p> | LinkedIn Documentation |
0 | 0.1953 |