@Remote Embedded

Hi,

We are using the system, I'm more than happy to help if I can.

Thanks

Richard

Great!  Thanks Richard.  Do you know

How often is meter sent from MFP to @remote server?  What determines when it is sent?  There seems to be some confusion here and it may be affecting our collection and billing procedures.

Hi,

Within the settings in the Japan GUI website, you can set the individual Cumin or Basil device with a meter reading date which you will use for meter billing. This can be seen in the 'Device Information' section and the filed named 'M/R Date'. The device starts communication 3 days before this date to account for if your chosen date falls on a Sunday and the customers machine is turned off on Friday evening.

When you then run and export the CSV meter reading report, which can be selected from the left hand menu bar, it picks the most recent meter reading it has at that time for you.

For example, we use the 24th of each month as the meter collection date for all our machines, we run/export the CSV report on the 25th, so all our meter readings are up to date, unless a customer has a communication problem lasting for more than 3 days.

By default the 'M/R Date' field is set to the 1st, if you have not altered this on the devices, even if you run your report on the 25th, you will only get meters from the 1st. If you have changed this date on some devices and on on others, you will get a mix of readings from devices which are up-to-date and some that are old.

So to sum up regarding your questions,

Q: How often is meter sent from MFP to @remote server?

A: For a three day period prior to your 'M/R Date' setting.

Q: What determines when it is sent?

A: Your 'M/R Date' setting for each device.

I hope that I have understood your issue and explained the situation well, if you have any further queries I'm more than happy to help.

Thanks

Richard 

Richard:

Thanks again.  I appreciate the information you provided, very thorough and I'm sure it took you some time to compose.  I'm going to be discussing this with our AR department.  We normally leave the default MR date at 1.  However, we have seen collections all over the month and certainly outside of 3 days from the 1st.  This seems to be creating a problem because we are getting the report each Monday and it was assumed that it was obtained that day...we are now trying to enforce that although it is pulled down from the server on that day it is not from that day.  I'm not clear on what problems this creates but I can understand that acting on this inaccurate information can certainly be problematic.  Again, your input is greatly appreciated!