Versions Compared

Version Old Version 1 New Version 2
Changes made by

Tatiana Kosmida

Tatiana Kosmida

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Asset Tracking (or Asset Locator, which is the name used in DNA Spaces) is a part of the Cisco portfolio. It is a tool that makes it possible to administrate assets and where the assets are located. All assets are connected to the Cisco infrastructure in some way, either through WIFI or BLE, which forwards location coordinates and potentially other relevant information to DNA Spaces. The customer needs to structure the assets in the Asset Tracking administration tool. There are many options and it is possible to have sub groups and categories with screenshot examples below:

...

  1. ACT license in Cisco Spaces is required for Asset Tracking

  2. You need a working Asset Tracking system, such as Cisco Spaces with an API

  3. Cisco Spaces/MazeMap Partner Tenant ID (note: if there was one generated for positioning already, there’s no need to create a separate one for asset tracking).

  4. Proxy LIPI, but please note it’s required only if you want the dynamic position of the assets to be visualized and it’s not required for static assets. If you already have a proxy LIPI set up for your campus for positioning there’s no need to setup a new one. For reference, here’s a documentation on how to set up the proxy LIPI: Proxy-LIPI (DNA Spaces) Installation Guide

  5. You need to confirm the z-levels of the floors on the campus (it needs to be clarified if the z-levels differ between buildings), otherwise the assets might not show on the correct floors after the setup is complete

  6. You need to send the API token needed to communicate with Asset tracking API to the MazeMap Customer Success Manager assigned to the project (instructions on how to get the API token can be found below)

  7. Customer Success Manager will complete the configuration on MazeMap’s side (Map Editor)

  8. MazeMap Engineering will complete the setup on MazeMap side, communicating internally with the CSM

  9. SSO: Can Optional (please consult your CSM first): SSO can be set up by doing SSO setup as described here:

    1. Setting up SAML 2.0 SSO integration with MazeMap (Customer self-help article link incoming)

    2. MazeMap Engineering must complete the configuration after receiving a confirmation from the CSM

...