Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Set emails for notification delivery once an event is triggered. Please note, clients are required to set up an email server to send emails via the Galooli web solution.

  • Destination e-mail(s) - Emails will receive notifications when an event is triggered in one or more units belonging to the cluster.

  • To separate the e-mail addresses use a comma or enter.

Note

Only Galooli users can get email notifications

Destination SMS

Set phone numbers for notification delivery once an event is triggered. Please note, that clients are required to sign with an SMS delivery provider before sending SMS messages.

...

  • Credit plan - Galooli offers two credit plans. A monthly bundle or a one-time bundle

  • SMS limit - Limit the number of SMS messages to be sent monthly per cluster

  • Cost Per Liter - Add the current cost per liter for fuel. Based on the cost, the system can present the overall fuel costs for your cluster in dashboards and reports. Please keep the figure updated so the system can display the proper costs

  • Currency - Option to select the relevant currency. It will appear in dashboards that have financial data (savings/waste, etc.) and in calculated financial fields in the reports

  • Time Offset (GMT) - Local timeAll groups and units under that cluster will be set to that local time. It is possible for the cluster time set to be different from the organizational time set that has been established in the organization's preferences. Preferences

  • Allowed Units - Maximum number of units that can be added

...

It is not possible to clone or move the clusters.

Stock and Test Clusters

Galooli's billing topics are regulated by its Stock and Test Clusters in front of its customers. Galooli sets up both clusters in each and every organization

Main Principles

  • Units that have been moved to the "Stock" cluster will be automatically disconnected from the server without the user receiving any notification about them.

  • The basis for the monthly billing is the units tree in the system. The customer pays for whatever is on the tree of units

  • The customer is responsible for activating/de-activate units just by moving them into and out of the system tree

  • Every system organization is billing in one currency only (no more than one currency for the same customer/organization). Supported currencies - USD, Euro, UGX, NGN, KEN

  • Billing is per connected assets (units) & per customer’s services (reports, SMS, addresses, … - future)​

  • A unit cannot be deleted from the organization tree if its billing type is LE (Leasing)

Organization Tree structure

Additional Clusters

...

 

For every organization, 2 clusters and 1 group are added at the bottom of the tree, automatically, with no ability to remove, available for managers and up only:

STOCK Cluster

  1. Purposes of the cluster

    • Store units that are shipped

    • Store removed units from customers (move them from commercial clusters)

    • Standby stock before installations

  2. The name of the cluster is not editable

  3. No limitation on adding Groups and Units according to the regular authorization module

  4. Units under the STOCK cluster are not chargeable (unless under commitment)

  5. The server throws units’ transmissions under this cluster, so practically even if they transmit they will not be active in the system

SHIPPED (group under STOCK)

  1. Purposes of the group

    • Make available all lists of units shipped to a customer prior to installation

    • Ease of use (instead of adding the units manually one by one)

    • Ensure units under commitment (Leasing etc.) shall be billed even if not installed

  2. Once shipping units or add drop shipping stock, our admin will add the list of units and their commitment date (if any) to a file, with a group name. This file will automatically be uploaded to a new group in the STOCK cluster (needs to specify with R&D the format).

  3. This group can be modified freely according to user authorization

TEST Cluster

  1. Purposes of the cluster

    • Test units before installations

    •   Units for POCs

    • Temporarily removed

  2. The name of the cluster is not editable

  3. No limitation on adding groups according to the regular authorization module

  4. Limited amount of units - 20 (Default)

  5. Units under the TEST cluster are not chargeable (unless under commitment)