When working with small deployments, app interaction can easily be managed through programming for beacons individually based on information present on the beacon e.g. beacon with an Instance ID of six triggers interaction six. As deployments expand, are shared with other apps and for more use cases, app interaction is best triggered from general beacon context i.e. allow mobile betting anytime the device is in a betting zone.
In the BlueCats Platform, context or beacon meta-data is added to beacons in two ways: through beacon specific information i.e. data transfer capability and through hierarchical information assigned to a beacon through categories, zones or sites.
Beacon specific information is provided by the BlueCats platform. Examples of this include the mode of the beacon i.e. Secure or Eddystone-URL, recent temperature readings and battery status.
Beacon hierarchical information is provided by you through the placement and tagging of your beacon within Teams, Zones, Sites, and Categories. These elements can be used to trigger different beacon interactions and organize beacons for analytics purposes.
A Team is the topmost identifier in the BlueCats hierarchy. Teams can be used to separate beacons by client, brand, or into non-related beacon networks. Every team has an owner with advanced management capabilities over the team.
Other than Teammates, all entities in the BlueCats platform belong to a specific team. Information can be shared across teams in a variety of ways, but entities such as Sites and Categories are contained within a particular team.
Android, iOS, and API client applications are represented by Apps. Every app is assigned an app token or client ID to associate it with a particular BlueCats Team. Create an app for every application that will be accessing your beacon network. Beacon insights are sortable by app and network access can be granted to specific apps from other teams.
Teammates are BlueCats management system users. Teammates can act as contributors or consumers. Contributors can manage beacon settings, create and alter categories, sites, and beacons, and invite other teammates. Consumers have limited access rights to view Insights and update beacons with BlueCats Reveal.
Groups of beacons that share a common geo-location are located in a single site. Sites can contain a postal address or GPS coordinates and maps. Sites can contain custom values and can be used to trigger store entry and store exit notifications.
Sites within BlueCats can be marked private or public. Beacons in private sites can only be used by apps in your team or by other teams which you have granted access explicitly. Beacons in private sites are accessible to other BlueCats platform users.
Categories are used to add context to beacons with a similar context across an entire team. They can be used to notify your app of valuable location information such as 'Entrance', 'Endcap', or Menswear' and can used to define zones that span across an entire team.
Zones are dynamic groupings of beacons that can be composed of multiple categories, sites or individual beacons. Zones are used to trigger entry, exit, and dwell time events within a site across your entire team.
Maps are layouts or floor plans assigned to a site. Maps can be used for deployment mapping, rendering user location and heat mapping. Beacons are added to maps via the web app and can help when configuring beacon settings by estimating beacon range and the number of beacons needed to cover a location.
Regions define the available iBeacon and/or Eddystone-UID values that are available to your beacons. Regions can be used for organization or to enhance beacon detection in iOS when a app is closed.
Beacons are...beacons! Beacons are assigned to a single site, team and map, but can be assigned multiple categories and be within multiple zones