1.1.2 MPact Server .......................................................................................................................................................1-3
1.2 Browser Support ............................................................................................................................................................1-4
Chapter 2 MPact Server Installation and Setup
2.1 Server Installation and Login .........................................................................................................................................2-2
2.1.1 Server Login .........................................................................................................................................................2-3
2.2 Server Configuration ......................................................................................................................................................2-4
2.3 Tree Setup .....................................................................................................................................................................2-7
2.4 Floor Plan Setup .............................................................................................................................................................2-9
2.5.0.1 Category Creation and Modification ........................................................................................................2-12
2.5.0.2 Category Value Creation and Modification .............................................................................................2-13
2.6 Beacon Place Holder Setup and Configuration ...........................................................................................................2-15
2.6.1 Place Holder Manual Setup ...............................................................................................................................2-16
2.6.2 Beacon Place Holder CSV File Import Setup .....................................................................................................2-19
Chapter 3 MPact Toolbox Installation and Setup
3.1 Toolbox System Requirements ......................................................................................................................................3-2
A.1 Beacon Battery Life ...................................................................................................................................................... A-2
A.2 Beacon Part Number: MPACT-T1B20-000-WR (Model # ATLS-T1B) .......................................................................... A-3
A.3 Beacon Part Number: MPACT-T1B10-000-WR (Model # ATLS-T1B) .......................................................................... A-4
A.4 Beacon Hardware Regulatory Information .................................................................................................................. A-6
Appendix B Customer Support
ABOUT THIS GUIDE
DRAFT 2B - 12 June 2014
This section is organized into the following sections:
Using the Documentation
•
• Motorola Solutions, Inc. End-User License Agreement
6
!
DRAFT 2B - 12 June 2014
Using the Documentation
The following sections provide information about the document and notational conventions used in the guides, and provides a
list of related documentation.
Intended Audience
This document is written for Motorola Solutions Partners and Product Managers.
Document Conventions
The following conventions are used in this manual to draw your attention to important information:
NOTE: Indicates tips or special requirements.
CAUTION: Indicate
WARNING! Indicates a condition or procedure t
injury or equipment damage.
Notational Conventions
The following notational conventions are used in this document:
• Italics are used to highlight specific items in the general text, an
documents
• Bullets (•) indicate:
• lists of alternatives
• lists of required steps that are not necessarily sequential
• Motorola Solutions MPact Location & Analytics So
& Analytics Deployment Guide
ftware Development Kit
About this Guide7
DRAFT 2B - 12 June 2014
Motorola Solutions, Inc.
End-User License Agreement
BY INSTALLING AND/OR USING THIS PRODUCT, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT,
UNDERSTAND IT AND AGREE TO BE BOUND ITS TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT,
MOTOROLA SOLUTIONS IS NOT WILLING TO LICENSE THE PRODUCT TO YOU, AND YOU MUST NOT USE OR INSTALL THIS
PRODUCT.
1. LICENSE GRANT. Motorola Solutions grants you ("Licensee
nonassignable, no cost license to use the software and documentation (“Product(s)”) subject to the terms and conditions of
this Agreement. You shall use the Products only for your internal business purposes, exclusively to support Motorola
Solutions’ MPACT solution. Any use of the Products outside of the conditions set forth herein is strictly prohibited and will
be deemed a breach of this Agreement resulting in immediate termination of your License. In the event of a breach of this
Agreement, Motorola Solutions will be entitled to all available remedies at law or in equity (including immediate injunctive
relief and repossession of all Products unless Licensee is a Federal agency of the United States Government).
2. LICENSE RESTRICTIONS. You shall not distribute, sublicense, rent, loan, le
cause to be exported, re-exported, resold, shipped or diverted, directly or indirectly, the Products under this Agreement. You
shall not, and shall not permit others to: (i) modify, translate, decompile, bootleg, reverse engineer, disassemble, or extract
the inner workings of the Products, (ii) copy the look-and-feel or functionality of the Products; (iii) remove any proprietary
notices, marks, labels, or logos from the Products; (iv) rent or transfer all or some of the Products to any other party without
Motorola Solutions’ prior written consent; or (v) utilize any computer software or hardware which is designed to defeat any
copy protection device, should the Products be equipped with such a protection device.
3. INTELLECTUAL PROPERTY; CONTENT. You shall no
or divert or cause to be exported, re-exported, resold, shipped or diverted, directly or indirectly, the Products under this
Agreement. You shall not, and shall not permit others to: (i) modify, translate, decompile, bootleg, reverse engineer,
disassemble, or extract the inner workings of the Products, (ii) copy the look-and-feel or functionality of the Products; (iii)
remove any proprietary notices, marks, labels, or logos from the Products; (iv) rent or transfer all or some of the Products to
any other party without Motorola Solutions’ prior written consent; or (v) utilize any computer software or hardware which
is designed to defeat any copy protection device, should the Products be equipped with such a protection device.
Title to all copies of Products will not pass to Licensee at any time and remains vested exclusively in Motorola Solutions.
llectual property developed, originated, or prepared by Motorola Solutions in connection with the Products remain
All inte
vested exclusively in Motorola Solutions, and this Agreement does not grant to Licensee any intellectual property rights.
Portions of the Products are protected by United States patent an
applicable laws. Therefore, you must treat the Products like any other copyrighted material (e.g., a book or musical
recording) except that you may make one copy of the Product solely for back-up purposes. Unauthorized duplication of the
Products constitutes copyright infringement, and in the United States is punishable in federal court by fine and
imprisonment.
t distribute, sublicense, rent, loan, lease, export, re-export, resell, ship
" or "you") a personal, nonexclusive, nontransferable,
ase, export, re-export, resell, ship or divert or
d copyright laws, international treaty provisions, and other
4. LOCATION INFORMATION. The Product enables you to collect location
may allow you to track the actual location of those client devices. Motorola Solutions specifically disclaims any liability for
your use or misuse of the location-based data. You agree to defend, indemnify and hold harmless Motorola Solutions and
its affiliates, officers, agents, and employees from any claim, suit or action arising from or related to your use of the
location-based data, including any liability or expense (including litigation costs and attorneys’ fees) arising from claims,
losses, damages, suits, and/or judgments.
5. DISCLAIMER. MOTOROLA SOLUTIONS MAKES, AND YOU RECEIVE, NO WARRANTIES OF ANY KIND, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. MOTOROLA SOLUTIONS SPECIFICALLY DISCLAIMS ANY
WARRANTY INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A
PARTICULAR PURPOSE. THE PRODUCTS ARE PROVIDED "AS IS." MOTOROLA SOLUTIONS DOES NOT WARRANT THAT THE
PRODUCTS WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE PRODUCTS WILL BE UNINTERRUPTED
-based data from one or more client devices which
8
DRAFT 2B - 12 June 2014
OR ERROR FREE, OR THAT DEFECTS IN THE PRODUCTS WILL BE CORRECTED. MOTOROLA SOLUTIONS MAKES NO
WARRANTY WITH RESPECT TO THE CORRECTNESS, ACCURACY, OR RELIABILITY OF THE PRODUCTS. Some jurisdictions
do not allow the exclusion of implied warranties, so the above exclusion may not apply to you.
6. LIMITATION OF LIABILITY. THE TOTAL LIABILITY OF MOTORO
SHALL NOT EXCEED THE FAIR MARKET VALUE OF THE PRODUCTS LICENSED UNDER THIS AGREEMENT. IN NO EVENT
WILL MOTOROLA SOLUTIONS BE LIABLE IN ANY WAY FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL OR
PUNITIVE DAMAGES OF ANY NATURE, INCLUDING WITHOUT LIMITATION, LOST BUSINESS PROFITS, OR LIABILITY OR
INJURY TO THIRD PERSONS, WHETHER FORESEEABLE OR NOT, REGARDLESS OF WHETHER MOTOROLA SOLUTIONS HAS
BEEN ADVISED OF THE POSSIBLITY OF SUCH DAMAGES. Some jurisdictions do not permit limitations of liability for
incidental or consequential damages, so the above exclusions may not apply to you. This Limitation of Liability provision
survives the termination of this Agreement and applies notwithstanding any contrary provision in this Agreement. Licensee
must bring any action under this Agreement within one (1) year after the cause of action arises.
7. MAINTENANCE. Unless provided for in a separate agreement, Motorola So
or field service of the Products.
8. HIGH RISK ACTIVITIES. The Products are
as on-line control software in hazardous environments requiring fail-safe performance, such as in the operation of nuclear
facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons
systems, in which the failure of the Products could lead directly to death, personal injury, or severe physical or
environmental damage ("High Risk Activities"). Motorola Solutions and its suppliers specifically disclaim any express or
implied warranty of fitness for High Risk Activities, and if you elect to use the Products in any High Risk Activities, you agree
to indemnify, defend, and hold Motorola Solutions harmless from and against any and all costs, damages, and losses
related to that use.
9. U.S. GOVERNMENT. If you are acquiring the Products on behalf of any unit or agency of the U.S. Government, the following
shall apply. Use, duplication, or disclosure of the Products is subject to the restrictions set forth in subparagraphs (c) (1) and
(2) of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless
being provided to the Department of Defense. If being provided to the Department of Defense, use, duplication, or
disclosure of the Products is subject to the restricted rights set forth in subparagraph (c) (1) (ii) of the Rights in Technical
Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. Products may or may not include a
Restricted Rights notice, or other notice referring specifically to the terms and conditions of this Agreement. The terms and
conditions of this Agreement shall each continue to apply, but only to the extent that such terms and conditions are not
inconsistent with the rights provided to you under the aforementioned provisions of the FAR and DFARS, as applicable to
the particular procuring agency and procurement transaction.
not fault-tolerant and are not designed, manufactured or intended for use or resale
LA SOLUTIONS UNDER THIS AGREEMENT FOR DAMAGES
lutions shall not be responsible for maintenance
10. GOVERNING LAW. This Agreement shall be governed by the laws of the United States of America to the extent that they
app
ly and otherwise by the laws of the State of New York without regard to its conflict of laws provisions.
11. COMPLIANCE WITH LAWS. Licensee will comply with all ap
regulations of the United States. Licensee will not, without the prior authorization of Motorola Solutions and the
appropriate governmental authority of the United States, in any form export or re-export, sell or resell, ship or reship, or
divert, through direct or indirect means, any item or technical data or direct or indirect products sold or otherwise furnished
to any person within any territory for which the United States Government or any of its agencies at the time of the action,
requires an export license or other governmental approval. Violation of this provision will be a material breach of this
Agreement, permitting immediate termination by Motorola Solutions.
12. THIRD PARTY SOFTWARE. The Products may contain one or more items of Third-Party Software. The terms of this
Agreem
INCLUDED, IN WHICH CASE YOUR USE OF THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE
THIRD-PARTY LICENSE.
13. OPEN SOURCE SOFTWARE. The Products may contain one or more items of Open Source Software. Open Source Software
is software covered by a publicly available license governed solely under Copyright law, whereas the complete terms and
obligations of such license attach to a licensee solely through the act of copying, using and/or distribution of the licensed
ent govern your use of any Third-Party Software UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS
plicable laws and regulations, including export laws and
About this Guide9
DRAFT 2B - 12 June 2014
software, such obligations often include one or more of attribution obligations, distribution obligations, copyleft
obligations, and intellectual property encumbrances. The use of any Open Source Software is subject to the terms and
conditions of this Agreement as well as the terms and conditions of the corresponding license of each Open Source
Software package. If there is a conflict between the terms and conditions of this Agreement and the terms and conditions
of the Open Source Software license, the applicable Open Source Software license will take precedence. Copies of the
licenses for the included Open Source Software, if any, as well as their attributions, acknowledgements, and software
information details, are provided in the electronic copy of this Agreement, which is available in the Legal Notices or
README file associated with the Product. Motorola Solutions is required to reproduce the software licenses,
acknowledgments and copyright notices as provided by
14. the authors and owners, thus, all such information is provide
translation.
15. Depending on the license terms of the specific Open Source So
and review the entire Open Source Software information to identify which Open Source Software packages have source
code provided or available. For instructions on how to obtain a copy of any source code made publicly available by Motorola
Solutions related to Open Source Software distributed by Motorola Solutions, you may send your request (including the
Motorola Solutions Product name and version, along with the Open Source Software specifics) in writing to: Motorola
Solutions, Inc., Open Source Software Management, 1301 E. Algonquin Road, Schaumburg, IL 60196 USA.
d in its native language form, without modification or
ftware, source code may not be provided. Please reference
10
DRAFT 2B - 12 June 2014
CHAPTER 1 MPACT OVERVIEW
DRAFT 2B - 12 June 2014
The Motorola Solutions MPact accurately locates Bluetooth® SMART 4.0 mobile client devices using distributed Bluetooth
Low Energy
modes; Battery Saving, iBeacon or MPact. Battery Saving mode is optimized to save battery life. The iBeacon mode is
configured to Apple’s iBeacon specification. MPact mode is a modified iBeacon mode that includes battery information.
(BLE) beacons and displays their location on a site’s floor plan. The beacon can be configured to be in one of three
The Bluetooth radio is low energy, and its signal does not propagate v
an MPact beacon, the device recognizes the beacon’s emission using its Bluetooth radio. Data from the beacon is forwarded
to a back-end MPact Server, which displays the location of each individual MPact beacon and the movement of the store’s
customer as they walk about the store shopping. This data is used for analysis at a later date.
MPact is a real-time micro locationing system, designed and position
scenarios. As an example, using MPact, retailers know the specific aisle a customer is located and the shelf they are currently
viewing. This allows administrators to track customers with standard
products and services based on a customer’s movement and location. RTLS applications enable administrators to target
coupons and product information where they are most likely to be leveraged based on a customer's exact store location.
This document provides a logical arrangement of processes that are essential to a successful MPact Server and Toolbox
deployment.
ery far. When a Bluetooth 4.0 smartphone or tablet nears
ed for high-level accuracy in a wide range of deployment
real time locationing services (RTLS) and customize
The MPact architecture is comprised of the following:
•
MPact Beacons
• MPact Server
• MPact Toolbox
• MPact Client SDK
Figure 1-1 MPact Typical Topology
1.1.1 MPact Beacons
MPact beacons are small, battery powered Bluetooth Low Energy (BLE) devices. Beacons are strategically placed in retail
environments where customer locationing is wanted. Beacons can be placed on existing retail shelving or mechanically
secured. MPact beacons utilize a Bluetooth 4.0 radio that periodically emits a signal over the course of at least two years (the
battery’s maximum lifespan). Depleted beacon batteries are easily replaced. A beacon’s Bluetooth beacon contains the
beacon’s ID and remaining battery life of the beacon to assist the administrator in managing the deployment area.
NOTE: Battery information is not available if using iBeacon mode. This guide assumes
the beacon is in
Beacon placements can be adjusted within a deployment floor plan, and depending on the mode selected, their battery life can
be tracked over time. Administrators can cursor over a beacon to assess the beacon’s remaining battery life. For more
information on Active View, refer to the
Battery Saving or MPact mode.
Motorola Solutions MPact Locations & Analytics Server Reference Guide.
1.1.2 MPact Server
DRAFT 2B - 12 June 2014
The MPact Server, a location and analytics system can be installed on the Linux platform (Debian 7.3). It provides an interface
to install and maintain MPact beacon positions throughout a deployment site.
MPact Overview1 - 3
The MPact Server receives its beacon data from customer’s devices moving
(beacon’s ID) is compared to other pre-configured beacon identifiers mapped to a specific location (the UUID is used to
distinguish one store from another and is set within the MPact management UI). When a match occurs, the MPact Server can
either place the mobile customer within a store or place the mobile customer in close proximity to specific products. The
customer’s location, the beacon’s proximity to specific products and the beacon’s remaining battery life are all stored on the
MPact Server’s local database for administrative retrieval and analysis.
The MPact Server application manages the MPact infrastructure and administrative
configure the site floor plans required for beacon placement and locationing, manage the association of beacons with specific
products, support beacon deployment and maintenance, and provide the visualization and analytics needed for both mobile
customer devices and beacons.
1.1.3 MPact Toolbox
The MPact Toolbox is an iPad application designed for easy beacon deployment and management. During a typical MPact
installation, an iPad is carried within a retail area to scan each beacon’s barcode during deployment. The handheld can also
validate existing beacon functionality at any time. Beacon deployments are administrated from the MPact Server (consisting
of beacon place holders and other attributes). An administrator user can add, modify or delete beacons and beacon place
holders from a site’s floor plan residing and displaying on the Installer. An administrator can add beacons or flash beacons as
their beacons are recognized. Beacon updates are stored on the MPact Server.
1.1.4 MPact Client SDK
The MPact Client SDK is a client library and is available in both IOS and Android versions. The client SDK integrates directly
into a partner application and allows it to listen for BLE emissions. Upon receiving a beacon emission, the client library sends
relevant information to the MPact Server. If the client receives data from more than one beacon within a given interval, the
utilized beacon is based on a beacon selection algorithm distributed between the client and the server. Communication
between the client library and the MPact Server is secured through SSL.
System Configuration for the administration of beacon settings defined globally on the MPact Server. The beacon
settings are then pushed to selected beacons as their respective configurations warrant. Beacon configuration settings must
be set accurately in the MPact Server before they can be provisioned to an MPact Toolbox supported iPad.
To administrate the system configuration:
1. Select
2. Modify the System Configuration parameters as required.
System Configuration under the Configuration main menu item.
Figure 2-3 MPact Server System Configuration - System Configuration
Figure 2-4 MPact Server - System Configuration
MPact Server Installation and Setup2 - 5
DRAFT 2B - 12 June 2014
3. Refer to the following table to modify the Beacon Configuration parameters:
Beacon ModeSet the mode defining how beacons are emitted from MPact beacons. Supported modes
include
The
beacon as small as possible (the beacon contains the minimal amount of information needed
to support MPact server functions). An MPact beacon contains the Motorola Solutions
registered manufacturing ID, beacon ID and a single byte representing the percentage of
battery life remaining (0-100%).
The
7.0). There are three data fields Apple has made available to iOS applications, a UUID for
device identification, a Major component for device class and a Minor component for more
refined information like product category.
The
could be the same for each device on the first floor or a particular department store (0-65525).
The
If the major or minor values display in red, they have been pre-set from the MPact Server and
do not require modification, they just need to be pushed to the device.
The
been defined so MPact data can be conveyed as being compatible with the MPact server. No
input is required.
Battery Saving, iBeacon and MPact.
Battery Saving format, the default setting, is optimized for battery life by making the
iBeacon format was created by Apple for use in iOS devices (beginning with iOS version
Major field is a 2 byte field for identifying the device class. For example, the Major value
Minor field is a 2 byte field for more refined information, like product category (0-65535).
MPact beacon format uses the iBeacon format, however, the Major and Minor fields have
UUID (16 bytes)16 byte hex character string that defines the purpose of the device. The UUID classification is
meant to be broad. For example, a UUID could identify a beacon was owned by Starbucks.
Beacon Power
(-23 dBm to O dBm)
Beacon Channel
(1 to 7)
Beacon Interval
(100 ms to 1000 ms)
Uploaded Version
Last Uploaded
Firmware
Beaconing output power is set from -23 to 0 dBm.
Channel mask is set from 1-7 to apply an operation channel restriction to beacon
transmissions.
From 100ms to 1000ms in 100 ms increments for a beacon's emission. The default is 600ms.
The shorter the interval, the shorter the beacon's battery life. However, shorter intervals result
in increased accuracy.
Either blank or lists the firmware version last utilized for beacon uploads by the MPact server
(for example, broadcaster-1.0.0.0-00xD.bin.
Either blank or lists the date and time the most recent firmware version (the version listed in
the Uploaded Version field) is pushed to the beacons.
Place the cursor inside the field to browse to the latest beacon firmware file. Choose Select
to launch a screen for navigating the system for a target firmware file for subsequent
File
beacon uploads. Once selected, the complete relative path for the file displays.
Note: Some beacon models do not allow for any changes in firmware.
4. Select Save to commit these beacon configuration settings for subsequent download to beacons.
5. Set the Network Proxy Settings to define how MPact server event subscribers receive their defined notifications over
the MPact server.
HTTP Proxy SettingsSet the Web domain location for the destination of uniquely defined subscriber event
notifications (for example, www.hostname-example.com).
PortUse the spinner control to set the virtual port integer for the connection between the MPact
server and the defined proxy or IP address.
Bypass ProxyOptionally, bypass a proxy Web domain by providing a numerical IP address for the recipient
server receiving event notifications on behalf of the subscribers.
6. Select
Save to commit these subscriber notification connection settings to the MPact server.
NOTE: If the uploaded version does not change after saving the configuration, try logging
out and re-login to MPact UI or repeating the configuration steps.
MPact Server Installation and Setup2 - 7
DRAFT 2B - 12 June 2014
2.3 Tree Setup
Use
Tree Setu p to build the tree hierarchy for each store site location on a global map. A tree hierarchy is built from a global
site location down to each floor in a building, including floor plans for each floor in a building. After the tree is saved,
configurations are added to the system for beacon deployment on the floors of each site.
To administrate the MPact tree setup:
1. Select
2. From the System drop-down menu, select Add Child and drag the cursor over to the node to add the required node. Build
T
ree Setup
the hierarchy for
Keep the following in mind when creating the tree:
• You do not have to create a
• At the end of every tree setup there must be a
under the Operations main menu item.
Figure 2-5 MPact Server UI Tree Setup
Country, Country Region, City, Campus, Site, Area and Floor, as needed.
Coun
before creating a Site.
try
Floor.
Figure 2-6 MPact Server UI Tree Setup - Adding Tree Nodes
NOTE: When building the tree hierarchy, the following characters are invalid:
-q- $ * < > # ~. All other characters, including space, are valid.
Loading...
+ 47 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.