Product documentation

01. Hardware Components and Requirements

A Favendo intallation is made of:

  • Favendo asset tracking backend services: A set of servers that host the whole Favendo software stack.
  • Beacon trackers: Fixed receivers that are mounted either on the ceilling or on the wall, and that listen to the beacon signals before sending then to Favendo’s backend.
  • Beacons: Small mobile sender that is mounted on the object or person to track.

01. Favendo asset tracking backend services

Favendo requires, at a minimum, 3 VMs with the following configurations:

NumberPurposeRequirementDescription
1 xMain server
  • Quad Core (3.2 GHz)
  • 64GB RAM
  • 500 GB SSD
  • Ubuntu 20.04
  • main spring-boot application (zircon API)
  • 5 spring-boot microservices to manage side functionalities (ex: event management, adapters, …)
  • AMQP Broker (RabbitMQ)
  • Redis cache server
  • 3 postgres dbs
  • 2 Elasticsearch nodes
  • 1 nginx load-balancer
  • Web applications.
  • 1 xAsset tracking
  • Quad Core (3.2 GHz)
  • 32 GB RAM
  • 100GB SSD
  • Ubuntu 20.04
  • 1 xMonitoring
  • Quad Core (3.2 GHz)
  • 32 GB RAM
  • 100GB SSD
  • Ubuntu 20.04
  • Graylog instance
  • Elasticsearch instance (used by graylog)
  • mongo db instance (used by graylog)
  • spring-boot-admin microservce.
  • 02. Beacon trackers

    The following beacon trackers are compatible with Favendo’s solution:

    • Favendo’s own beacon tracker Relay Compact
    • HPE Aruba Access Points with BLE module
    • Extreme Networks Access Points with BLE module

    03. Beacons

    Every beacon using the iBeacon protocol should be compatible with Favendo’s solution.

    Ask the Favendo Team if you want to know which beacons have been tested and approved by Favendo.