Description:
A series of questions regarding the logic our systems follow in order to bill the objects our clients have in their accounts.
This information is confidential.
Conditions for billing start:
Object is created in LCM>Objects. Then:
Object is synchronized to ERP TrustTrack objects database (see ERP>SIM&RENT>TrustTrack objects) (synchronisation runs every 30 minutes) Then:
Object sends first data to the server OR 60 days pass. Then:
ERP object VISIBLE checkbox is checked (example below) <BILLING STARTS HERE!!!
Conditions for month X billing :
ERP object has VISIBLE checkbox checked at any point during X month.
Conditions for billing end:
Object visible checkbox is unchecked in LCM>Objects (DO NOT USE THIS OPTION)
Object is synchronized to ERP TrustTrack objects database (see ERP>SIM&RENT>TrustTrack objects) (synchronisation runs every 30 minutes) Then:
ERP object VISIBLE checkbox is unchecked (example below) <BILLING ENDS HERE!!!
OR
Object is deleted in LCM>Objects
Object is synchronized to ERP TrustTrack objects database (see ERP>SIM&RENT>TrustTrack objects) (synchronisation runs every 30 minutes) Then:
ERP object VISIBLE checkbox is unchecked (example below) <BILLING ENDS HERE!!!
On ERP side, is billing based on each IMEI or on each Object ID?
On object ID, this means it is possible that if the same IMEI 123 with object name 123_X was deleted from client X and recreated on client Y with object name 123_Y during month A, it will appear twice in the invoice and be charged twice for the A month.
Billing would like something like:
Object name | IMEI | Client |
123_X_deleted | 123 | X |
123_Y | 123 | Y |
What is the effect of LCM Delete button?
Object coordinates will stop being processed.
Object is archived for 30 days, when it can be restored.
Object will no longer appear in TT2 front-end.
Object will be checked as not Visible in ERP.
After 30 days, object settings and history is completely deleted.
What is the effect of "Is external object" checkbox?
No ACK will be sent to object. No records processing in TT2. Only FW and CFG update packages will be processed.
What is the effect of inputting a fake IMEI?
Fake or not fake imei, there is no difference billing wise. However, TT2 will not accept coordinates coming from a fake IMEI.
What is the effect of "Object state" in object settings?
No effect on either visibility or billing.
Client wants to keep object history but does not want to get new data nor be billed, what are his options?
OBJECT SHOULD BE BILLED!!! ALL OBJECT SHOULD BE BILLED!!! WE ARE PAYING FOR ALL OBJECT DATA STORAGE, PROCESSING, ADDRESSES, MAPS ETC. THERE IS NO BIG DIFFERENCE IF OBJECT IS ACTIVE OR NO.
No other option. Only delete object.
Information was provided in this consultation: https://ruptela.atlassian.net/browse/GUI-29537