Configuring beacons for positioning in Crowd Connected

Owned by Tatiana Kosmida
Last updated: 13 Dec, 2024
5 min read

Please note:

  • Beacons have 3 parts to their identifiers: UUID (long number), major ID, and minor ID:
    UUID - the long code consisting of letters and numbers
    Major ID and Minor ID - shorter decimal numbers
    Note: it’s typical for the UUID and Major ID to be set as being the same for a batch, with just the Minor ID/code being unique to each beacon

  • They can be set up in batches: the UUID then doesn’t need to be entered individually every time, but rather the UUID is entered for the entire batch and then the short - minor ID - is entered for every beacon. The minor ID can be found on the beacon’s sticker. Exactly how many beacons can belong to a batch is dictated by the producer of the beacons (sometimes the entire stock used for a project can be setup as a single batch)

  • UUID and minor ID are required to complete a setup - if any of those numbers are unknown, please contact your beacon manufacturer for details

 

Beacon configuration

  1. In order to configure the beacons, first navigate to Crowd Connected’s web app and log in: https://app.crowdconnected.com/
    The Customer Success Manager assigned to the project should give you access. If you haven’t been given access to the system, contact your CSM directly.

  2. In the menu on the left, click on “Positioning Configuration” and then select “Beacons”:

     

  3. Select the Floor plan that you want to add the beacons on:

     

  4. In order to start, click on the “Place Beacon” button - it will prompt a menu to appear on the left where you can enter the beacons.

     

  5. You probably want to add beacons in batches, especially if the project is to be setup for a bigger area, so start with the “Create new Batch” section. After entering the UUID, it’s typical to set the Major to 0 and then reference the sticker on the beacon for the Minor ID:

    Please then remember to save the batch:

    This will save the batch so that you won’t need to retype the UUID everytime you configure a new beacon (as long as the beacon is confirmed to belong to the saved UUID by the manufacturer) - you will be able to select your saved batch from the drop down menu in the “Choose Batch” field. Also, when you try to place a new beacon the system will automatically remember the latest used batch:

    The system should also confirm that you have created a new batch:


NOTE: There is no mobile-friendly version of the Crowd Connected/Sail app available at the moment. It is recommended that the beacons are entered and configured on a tablet that can run the website. It is possible to launch the webapp on the mobile but it’s not in a data entry-friendly format. 

It’s best to place the beacon in an entire area (for example: a floor or a particular part of the building selected for the demo) before testing the accuracy and making sure that the calibration is accurate. Once the beacons are placed and turned on, everything should be ready for testing. The system works best with the beacons set to transmitting at the highest possible power (0 or +4 is normally the highest level, and then a minus number for the lower levels). Please note that the power level is controlled on the beacon and not in the Crowd Connected system. 

There is a possibility to filter beacons by status, so you can check if any of the beacons is not functioning properly in case of any positioning-related issues:

 

Beacon density

The density also needs to be decent (the more beacons there are the better the accuracy) - the recommendation is 1 beacon per 100 sqm, although smaller areas typically need a more dense beacon coverage so it varies from case to case. It’s important to cover the perimeter (the edge of the whole area needs to be covered reasonably) - the positioning won’t work right if someone steps out of the perimeter of the beaconed area. Covering the edges makes the system work better. 

It’s important to note that in most cases the entire area does not need to be within the perimeter as it’s unusual for customers to require full coverage of the building.

Testing

Before testing positioning in the native MazeMap app, it’s advised to check if everything is in order in the Crowd Connected test app called Sail. The test app can be downloaded from the app store - the details should be delivered by the CSM assigned to the project, but the app store link can also be accessed through a PDF that is created once “Generate replacement demo app access token” button is hit:

Please note that the credentials are going to be regenerated every time this button is hit, and the old credentials will no longer be active. The PDF and the credentials will be saved and delivered by the CSM to avoid confusion. Authentication key should ideally be only created once. If there is a need to create it again, please make sure that all team members are notified, as those credentials also need to be updated in the MazeMap configuration.