Skip to main content

Introduction

Scalable Systems Group helps you monitor hyper-weight containers from anywhere in the world. The following is a quick introduction to some concepts

The Client Application​

Accessible at client.scalable-systems.io, the client application is the central area to get all information about your BinBar

Data Organization​

To help organize data and installations, we have a hierarchy of concepts

Account​

This is your account that you access with your email. To setup a new account, please see account setup.

An account allows you access to your company's data.

account dialog

Service Location​

A service location should correspond to a physical grouping of installations of containers. For example, if your company services 10 containers at Acme Factory and another 5 containers at Bob's Mall, you may want to create a service location Acme Factory and Bob's Mall.

service location creation

A service location contains 1 or more Container Sites

The more accurate you are with Service Locations, the better analytics we can eventually offer you.

Do you organize your Container Sites differently? Let us know!

Container Site​

A container site should correspond to a single physical location where you have a container and a BinBar.

For example, in Acme Factory, if there is a section where aluminum scrap is collected, and another where organic waste is collected, you would create 2 Container Sites, named Aluminum Scrap and Organic Waste respectively.

container sites

A container site should have a consistent container size, type, and contents. Additionally, container sites go through a calibration period where Scalable Systems Group automatically pairs weight tickets with BinBar measurements to learn the unique characteristics of the site and improve accuracy.

A Container Site contains 1 or more Container Cycles

Have ideas for interesting container site analytics reports? Let us know!

Container Cycle​

A container Cycle is a rotation of a specific container. At a typical site, a container will be (1) dropped off, (2) collect contents, (3) be picked up, (4*) a weight ticket is generated. Container Cycles track this process. A single container cycle corresponds with a single weight ticket.

For the best container site weight accuracy, you should pair weight tickets to container cycles.

Container cycles are automatically generated by BinBar for monitored Container Sites, and are in active development