Skip to end of banner
Go to start of banner

Stock and Test Clusters

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Main principles

  • 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)​

ZON Tree structure

Additional Fleets

For every organization, 2 fleets 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 Fleet

    • Store units that are shipped

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

    • Standby stock before installations

  2. Name of the fleet is not editable

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

  4. Units under STOCK fleet are not chargeable

  5. Server throws units’ transmissions under this fleet, 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 list 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 fleet (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 Fleet

    • Test units before installations

    •   Units for POC’s

    • Temporarily removed

  2. The name of the fleet is not editable

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

  4. Limited amount of units - 20 (Default)

  5. Units under TEST fleet are not chargeable

Commitment Date & Commitment Period fields

The purpose of the Commitment date field is to support Leasing and Pay as You Go contracts, where charges should apply no matter where the unit is located on the ZON Tree.

Commitment date field – the first activation date of a unit that is committed to a period of time

Commitment Period field – number of months the unit is committed to.

  • Location of the fields – next to Activation Date in the Edit Unit view:

  • 3 options to use these fields:

    • Shipping PAYG units – setting this in the file uploaded to the server

    • Manually – Galooli entity -> end customer

    • Backward – previously Leasing and PAYG units sold

  • Authorization to modify this field – Administrators only

  • A unit that includes a commitment date that is ahead of the current date – cannot be removed from the ZON.

  • If a Commitment Date is entered manually, the Commitment Period shall be 36 months as a default but can be changed by Administrators.

  • The commitment date is mandatory to enter only if the plan is LE.

  • On LE plans, if the commitment date is empty, once the unit is the first time on a commercial fleet, the commitment date shall be automatically filled. The server shall fill the commitment dates once a week for all units. This way, if a unit shall move back to STOCK before the scan, the commitment date shall not be filled.

Billing types

The Billing Type field is presented in the Edit Unit view.

Only Administrators are allowed to modify this field.

If a unit is added to the Tree manually (and not from the SHIPPED Excel), the default Billing Type is MO.

The following billing types are available:

Monthly (MO)

  • Billing types - MO, MO2…MO10

  • HW - one-time fee

  • SW & Service - monthly fees

  • No commitment

  • If a unit is on an active fleet on the tree for 2 days and up during a month - it is billed

  • Commitment Date & Commitment period fields should be zero, but even if there is a value there - it will be ignored in the Billing days count.

Pay As You Go (LE)

  • Billing types - LE, LE2…LE10

  • HW - monthly fees

  • SW & Service - monthly fees

  • Mandatory fields

    • Commitment date - future date to activate the unit (if commitment date is left blank, the day the unit moves from STOCK fleet to an active fleet, the commitment date shall be generated automatically and unit shall be activated).

    • Commitment period - the number of months the unit is committed to

  • The unit is billed during the commitment period, even if it is located in STOCK or TEST fleets

Annual/Cyclic (AN)

  • Billing types - AN, AN2…AN10

  • HW - one-time fees

  • SW & Service - monthly fees

  • Mandatory fields

    • Commitment date - future date to activate the unit (if commitment date is left blank, the day the unit moves from STOCK fleet to an active fleet, the commitment date shall be generated automatically and unit shall be activated).

    • Commitment period

      • the number of months for the billing cycle.

      • Bill shall be issued for the month of the commitment date, every X months set in the commitment period.

      • Bill is for the period in advance

  • Commitment Date & Commitment period fields are mandatory fields but If the unit is located in STOCK or TEST fleets, it will be ignored in the Billing days count (unless within the commitment period of the cycle).

Hybrid (HB) - Not in use!

 

Billing Method 2022 Flow

  • No labels