...
ACT license in Cisco Spaces is required for Asset Tracking
You need a working Asset Tracking system, such as Cisco Spaces with an API
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).
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
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
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)
Customer Success Manager will complete the configuration on MazeMap’s side (Map Editor)
MazeMap Engineering will complete the setup on MazeMap side, communicating internally with the CSM
Optional (please consult your CSM first): SSO can be set up by doing SSO setup as described here:
Setting up SAML 2.0 SSO integration with MazeMap: Instructions for setting up SAML 2.0 SSO Integration with MazeMap
MazeMap Engineering must complete the configuration after receiving a confirmation from the CSM
...
If new icons are required, especially if you have an asset category that we don’t have a good existing icon for yet, please notify your Customer Success Manager. The CSM will request new icons to be uploaded by the UX Lead.
Please note: In order for MazeMap to be able to visualize the data, we need the following to be configured and ready in Cisco Spaces (under Asset Locator):
Tags (configured by MAC address)
Asset (please note that assets need to have tags assigned to them)
Categories (those organize the assets in a coherent way in the system, for example: Computer, Phones, Desktops, Pumps, etc.)
...