INTEGRATING BEACONS IN YOUR BUSINESS


In order to integrate and enable proximity detection for your App or solution, there are steps that affects all the project lifecycle phases.

The design and implementation and live rollout of BeaconZone enabled not only to validate the platform as such, but also to set up and finalize an approach and environment that is required to create an beacon solution in general.

BeaconZone runs and serves 25 locations and covers a variety of proximity detection use cases that are not just focusing on retail but also covers other areas such as museums and tourism.

In terms of corporate integration, besides the underlying concepts, a proven environment is crucial not only for a rollout but also and in particular in the analysis phase.


AGILE APPROACH


The concepts and implementation of Beacon detection is easy and straightforward for the simple case but in order to apply it in on a larger corporate solution, there are important steps to consider.



BEACON STARTER

is a package of consulting services combined with a flexible iBeacons management environment platform and a generic IOS APP that offers the required facilities to validate and analyze iBeacons and proximity detection for your company projects and teams.

The approach has been successfully applied to build and finalize in just 2 months BEACONZONE, a live iBeacons solution serving to date more than 20 locations in Zurich.

We use our platform allowing to simulate and finalize typical detection use case situations before we inject the results in our productive Application.

In addition, the platform is a very efficient environment for Workshops or Seminars allowing also not technical oriented users to have a pragmatic and practical view and understanding on how this technology is working.
Stacks Image 2554
Stacks Image 10871

MULTI IBEACONS USE CASES


A use case is a set of one or more allocations of iBeacons to a service or content (Web, Microsite or media file) combined with a specific individual iBeacon proximity detection configuration.

Beside being ideal for Workshops and seminars, the backend infrastructure enable to use/reuse and test via the BEACON STARTER generic IOS mobile App the same set of physical iBeacons but under different use cases and configurations at the target locations and areas.

The mobile APP enables to select (switch) on the fly the use cases configured in the backend system as reported in the following diagram:
Stacks Image 10891
The advantages of such an approach lies at different levels:

For example :

  • Different vendors can be directly compared on site. By deploying at a particular region iBeacons coming from different vendors, and by switching on site the related use cases, it is possible to verify, compare and validate live how these will perform. We can for example create a "Shop Use Case Vendor A" and "Shop Use Case Vendor B" and see directly the results in terms of detection and/or performance
  • Different iBeacons topologies and/or individual detection parameters (such as retention time, immediate, near or far detection) can be also configured and allocated to different use cases and compared on the field.
  • We can simulate different user profiles behaviors by creating dedicated use cases.

FLEXIBLE AND PRAGMATIC APPROACH


BEACON STARTER is a cloud platform written in Java (Vaadin) and can be thus extended and adapted to particular customers needs during the evaluation and design phase of your project.

IBeacons projects have the characteristic to be very easy in terms of strict detection, but may hide a number of additional tasks , such as management and system integration, that often are not apparent at first glance.

By offering months of pre-development and experience combined with an environment that can be re-used and or seen as a starting point for projects, BEACON STARTER can let customer save time and start with a solide and proven base infrastructure.

VENDOR INDEPENDENT


BEACON STARTER has not the aim to replace existing vendors solutions, but rather to offer an independent facility to concretely finalize the requirements, get hands on with proximity detection and finally opt for a development strategy.

No matter if you are planing to buy a solution, extend your existing mobile app to support iBeacons or write a brand new system. BEACON STARTER is an ideal choice to quickly and better carry on the design and proof of concepts phase.

IDENTIFY PROXIMITY REQUIREMENTS

In order to integrate proximity, we need to analyze, design and validate different layers.

We can read a lot about iBeacons seen from a technical perspective. In practice, at least to our experience, the real work will start in modeling and adapting location based events and orchestrate these within corporate data and services. In the diagram, iBeacons provide low level proximity event information to a physical detection layer. The objective are therefore to map proximity detection events with business data and processes or , in other words, to match proximity events with business workflow events.

The proximity detection modeling layer must cope with topologies constellations that are often target location specific. There is therefore a requirement to implement a flexible abstraction level allowing to ensure a proper localization and proximity detection processing. The need for such a flexibility is in practice often underestimated.

The proximity detection layer plays also the role of an integration interface with the business workflow and process models.


Stacks Image 6009
who we are
BTC Business Technology Consulting offers high level services since 1998

Large consulting expertise in Analysis, Design and Implementation at large customer site.
contact

Fabio Trentini
Email: info@btconsulting.ch
Linkedin Xing


What we do
Consulting services and project coaching for IT-Architectures and Strategy in the Web Mobile and Business Service integration areas