Follow

ID968 - Advanced Meters & DCA Data Overview & Sample

Import meters from various DCAs as well as our other processes that import meters (ID398/ID386), store them in a temp table then only import to eAutomate the ones needed for billing, vastly reducing your meter table size.

Jump to Overview | Variables | Sample | API Details | App | Validating Meters | OnDemand SSRS 

Click to subscribe

*  *  *

Overview

Overview

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. 

This process will import meters from various DCAs as well as our other processes that import meters (ID398/ID386), store them in a temp table then only import to eAutomate the ones needed for billing, vastly reducing your meter table size. 

We will only push in meters that are due to bill per your Contract Record, devices not due to bill will not be listed on our reporting. Process also considers your eAuto meter buffer validation setting.

In addition, as predictive data become available in software like HP Smart Device Service we have the potential to review the error code and meter on a device needing service, predict what part is needed and check that the assigned tech has that part in their stock. We can filter supply orders and create sales orders with a specific hold code if the customer is using too much toner. We can evaluate service data that suggest a service call is needed and email the last person who placed a service call on that device to confirm it's really a problem. We can add a link to a video showing how to repair so the tech sees it in Remote Tech.

We can also support additional DCAs like EKM Insight, KPAX, FMAudit, and MPSMonitor (use ID311), giving you the same experience regardless of the DCA. 

To start the DCA process please subscribe to alert ID968 (be sure to list at least one email recipient so we know who to contact) and collect needed API details. We will initially ask for a list of meter types to map to what we see in the DCA but we are about to release an App to allow you to update yourself.

 

**Requires MINIMUM .Net version 4.7 on server for CEO Juice.**

*  *  *

Variable

Variables

ALL_Variables.png

 

Variable8: Select which DCA Platform you are using (KPAX or EKM), use drop down to select:

Var8.png

Variable2: Filter the import to only a specific Dealer Account (REQUIRED FOR FMAudit and OPTIONAL for KPAX and EKM)

for FMAudit, this is the Account Name all of your accounts fall under that you wish for us to push meters for:

Account_Name.png

Variable12: Indicate eAuto Meter Source to be assigned to meters entered into your eAuto

Variable1:  Custom Property Control to turn this integration OFF at either Equipment or Customer Level. We build this Custom Property for you and default to ON so this process is effectively ON for everything. You can set the exceptions to OFF at either Equipment or Customer Record level, as needed. Please note, setting to OFF at Customer Level will turn off for all Equipment Records showing that customer as Main Customer. For example, if Equipment Custom Property is set to ON and Customer Custom Property is set to OFF, the alert will NOT consider any of the equipment. 

THESE TWO VARIABLES SHOULD BE CLOSELY CONSIDERED AND REVIEWED:

VariableHidden2: Date Limiter - Do not import a new meter read unless it has been VariableHidden2 days since last Valid meter read (set to -2 to completely suppress since-last-read functionality and use ONLY due-to-bill per VariableW)

VariableW: Billing Limiter - Import meter reads if no read in last VariableW days AND meter is inside a Billing window (due to bill soon per the Billing Tolerance settings in e-automate). Set to -2 to suppress this functionality and use only days-since-last-read functionality in VariableHidden2 above. 

 

*  *  *

 

Sample

Sample

Two Worksheets:

Action Items - shows devices we could not push the meter into eAuto for, their eAuto meter info,  and why:

ID968ActionItems.PNG

 

No Action Needed - shows devices we did push meter readings in for along with the meter details:

ID968NoActionNeeded.PNG

*  *  *

 

API 

API Details

We need your API Details entered by you on our website as shown below. The user entering on our website will need 'Customer Admin' security role - ask us at help@ceojuice.com if you need to know who has.

Please enter credentials on our website (https://www.ceojuice.com/CustomerAdmin/Integrations) via Profile / Integrations:

13.PNG

ALL_Integrations.png

 

Please use these links for instructions on creating API Details needed based on DCA type:

 

KPAX: https://support.ceojuice.com/hc/en-us/articles/360053613371-KPAX-API-Integration-ID968-

FMAudit: https://support.ceojuice.com/hc/en-us/articles/4405289640084-FMAudit-Account-Info-Integration-ID968-

 

*  *  *

APP

APP

You will need to tell our app which eAuto Meters correspond to the DCA Meters, so we know which meters to insert where in eAuto.

Go to your CEO Juice apps (if you don't know the URL use http://localhost:8888)

Select model-mapping-and-key-services:

 

ID968a.PNG

The two hyper links at top take you to

(1) Metertypes 

(2) Meter Mappings

2.PNG

Metertypes shows the DCA Meter Type names and eAuto Meter Type names, indicating if mapped and/or if ignored for mapping:

3.PNG

To get started go to Meter Mappings to start mapping your MP Monitor or HP Action Center (DCA) Meter Types to eAuto Meter Types:

Once you have mapped all your meters, the app can determine which meters to insert into eAuto.

4.PNG

 

When you select Add Mapping you will need to select the EA Metertype to be mapped to DCA Metertype:

5.PNG

The 'Fallback DCA Metertype (optional)' is only needed when the same EA Metertype applies to more than one DCA Metertype.

For example:

B\W only device has DCA Metertype of Total Meter which needs to be mapped to EA Metertype of B\W. But a color device has DCA Metertypes of Total Total Meter, Total B\W, and Total Color. You don't want DCA Metertype of Total Meter to go into eAuto as Total B\W clicks. 

So you want the DCA Metertype = Total B\W and the Fallback DCA Metertype = Total Meter

Essentially you are telling the app, if Total B\W from DCA does NOT exist, then use DCA Metertype of Total Meter for my eAuto B\W meter.

 

IF you have any questions or need changes on what DCA Metertypes are being pushed in, please contact your DCA support team directly as they can help you set which meters report.

 

*  *  *

 

Validating Meters

Validating Meters

est vs. Live Mode

Test vs. Live Mode

While in Test Mode, we will consider EVERY device regardless of your variable settings for Billing and Date Limiter (Variables Hidden2 and W). This is to provide you as many devices for mapping meters as we can to help ensure your mapping is as completed as can be. (Test mode looks back 45-days in DCA for meters to report on.)

Once process is running live, then we will only report daily on those meters qualified for consideration based on your variable settings for Billing and Date Limiter (Variables Hidden2 and W).

Billing and Date Limiter

Billing and Date Limiter

These variables effect whether a device's meter is considered by our process. When alert is running live, any device not meeting your Billing and Date Limiter settings, will NOT show on your daily report BUT will still go to your processed folder.

VariableHidden2: Date Limiter - Do not import a new meter read unless it has been VariableHidden2 days since last Valid meter read (set to -2 to completely suppress since-last-read functionality and use ONLY due-to-bill per VariableW)

VariableW: Billing Limiter - Import meter reads if no read in last VariableW days AND meter is inside a Billing window (due to bill soon per the Billing Tolerance settings in e-automate). Set to -2 to suppress this functionality and use only days-since-last-read functionality in VariableHidden2 above. 

3-days

3-Days Limitation

Once running live, this process ignores meter reads received more than 3 days ago and they will not show on your daily report. This limitation is in place because users were seeing meters with errors persisting on the report for far too long with basically ‘unsolvable’ problems, or at least problems no one was interested in solving. Now meters will show on the report for three days throwing their error and then they go away unless we have a newer read for that meter, one which hopefully there are no problems with. This function does NOT interact with the VariableW Billing Delimiter at all – the meter won’t have a chance to be considered for billing (or for Hidden2 non-billing Delimiter) once the three days are up.

Required Meters and Considering Valid:

Required Meters and Considering Valid:

Our integration will only consider meters set as required on Equipment Record AND due for billing today or past due per Contract Record.

ID311a.png

We then use your eAuto Meter Validation Buffer to check the meter is valid:

This can be seen via Tool / Options / Equipment:

7.PNG

 

 

Devices with more than one meter:

Devices with more than one meter:

We look for the serial number in eAuto and the meters required to compare what DCA meters are being pushed in. IF at least one of the required meters is greater than previous, we will push in ALL meters. If all meters are less than previous, NONE of the meters will push into eAuto.

 

Mapping Errors Explained:

Mapping Errors Explained:

Negative value indicates mapping not found: the DCA meter has not been mapped to an eAuto meter. Use the MeterType Mapping App to set.

read Invalid due to less or equal to previous: the meter from DCA is less than or equal to the previous meter in eAuto. 

read Invalid due to validation buffer: reading failed validation buffer test by eAuto per your eAuto validation buffer %. 

read Invalid due to other missing required reads: indicates a required meter (per eAuto Equipment Record) is either not mapped or not being pushed in from the DCA.  

read Invalid due to other Invalid reads in required set: indicates there are required meters for this device that are invalid (for one of the reasons above)

Actual updated based on previous Meter Reset Invalidated by Native Sanity Check: this is two different flags which almost always appear together. 'Actual updated based on previous Meter Reset' means that there is a meter reset somewhere in the past, which means EA will calculate a true 'Actual' to the best of its ability. 'Invalidated by Native Sanity Check' means exactly that, because parts of the sanity check rely on the Actual meter and it usually takes a long while after a reset before the historical data looks solid enough for the sanity check to give it a pass.

 

 

If you have a DCA meter that is older than current day of meters being pushed in, then this indicates the device has fallen off monitoring, meaning no new meters coming in. But our integrations always considers the most recent record available:

a.PNG

 

 

Custom Property

Custom Property

Use Custom Property to turn this integration OFF at either Equipment or Customer Level. We build this Custom Property for you and default to ON so this process is effectively ON for everything. You can set the exceptions to OFF at either Equipment or Customer Record level, as needed. Please note, setting to OFF at Customer Level will turn off for all Equipment Records showing that customer as Main Customer. For example, if Equipment Custom Property is set to ON and Customer Custom Property is set to OFF, the alert will NOT consider any of the equipment. 

Creating the Custom Property if you are missing in eAuto:

Step 1:

Create Custom Property Attribute via Tools / Lists & Codes / Attributes:

Attribute name = ZCJ_DCAMeterImport

Description = ZCJ_DCAMeterImport for ID311/ID968

Data type =  User-Defined Lookup

Lookup List = On / Off

CP1.PNG

Step 2:

Add Custom Property Attribute to both your Customer and Equipment Record Configurations via Tools / Lists & Codes / Configurations (custom properties):

Select New for Group Customer Properties:

Image__2_.png

Search Available attribute(s) for ZCJ_DCAMeterImport, check off Default value and select ON, then select QuickAdd - don't forget to hit OK to save:

Image__3_.png

Do the same for Group Equipment Properties:

Image__4_.png

Now you have this Custom Property available on Customer Record:

Image__6_.png

and Equipment Record:

Image__5_.png

 

*  *  *

OnDemand SSRS Report

OnDemand SSRS Report

You also have an On Demand SSRS Report to review what has pushed in that day and what has had errors that day. This is essentially a duplicate to the daily email sent to those emails listed on your ID968 subscription.

ID968SSRS.PNG

 

Report shows on Page 1, any meters unable to push into eAuto due to error indicated:

ID968ActionItems.PNG

 

Page 2 shows what meters have been pushed into eAuto:

ID968NoActionNeeded.PNG

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk