Cisco Spaces OS Runbook (Cisco Validated)

OVERVIEW

This Cisco Validated overview document will aid in configuring Spaces OS, ensuring a robust infrastructure that underpins a Cisco Spaces deployment.

Cisco Spaces OS serves as the foundational layer for deploying and managing intelligent location-based services within an organization. As the essential base installation, Spaces OS integrates a suite of critical components designed to streamline operations and enhance data utilization.

By onboarding data through platforms like Catalyst Center, Wireless LAN Controller (WLC), and Meraki, Spaces OS ensures seamless connectivity and comprehensive data capture. It facilitates the configuration of a unified location hierarchy and merges data from diverse sources to provide a cohesive spatial understanding. Additionally, Spaces OS supports the creation of detailed Digital Maps, offering a visual representation of spaces for better navigation and planning. With the capability to enable IoT streaming services, Spaces OS empowers organizations to leverage real-time data insights for improved decision-making and operational efficiency.

SUPPORT & ONBOARDING INFO

Please follow the link below to find out about the different ways to get support for Cisco Spaces: Support Info Link​

SPACES OS INSTALLATION

Onboarding Cisco Devices for Intaking Telemetry & Data

Overview

Onboarding data relates to the methods for connecting the telemetry data from the infrastructure to the Spaces dashboard.

Steps below should be completed for as many infrastructure stacks as available - the more data we feed into Spaces, the more valuable the outcomes can become.

Catalyst Wireless

Catalyst Wireless

Spaces Connector

In order to connect the wireless network with Cisco Spaces, Cisco Spaces Connector should be installed on a virtual machine. The Spaces Connector supports VMware ESXi 6.5 or above versions, as well as AWS AMI, Nutanix, and HyperV.

For more Connector VM options and details please review the Connector Configuration page.

The connector supports the Production configuration with the VM requirement as follows:

It is highly recommended that 8 vCPU be used when possible. Using fewer resources is possible but may restrict the ability to run certain services.

Connector Configurations

	Production
vCPU	8
Memory (GB)	16
Hard Disk (GB)	120

 

Connector Scaling

		Production
Location only	AP Count	15,000
	Client Count	150,000
	Message Rate (NMSP msg/sec)	38,000
IoT Services (Recommended Adv 1 & 2)	GRPC connection (AP count)	3,000 (hard limit)
	Client Count	30,000
	Message rate (BLE msg/sec)	170,000

For connector scaling please refer to the use cases in the table.

• Standard configuration provides scaling information for location only per the capacity details provided

• Running IoT services in addition to location services Cisco Spaces recommends the Production configuration, per the capacity details provided

Connector Scaling and Sizing Best Practices

• Start with Production and scale down as needed

• Don’t let CPU and memory go above 75%

• Adding new services will add additional load

• Keep an eye on the message rate - add mac prefix filtering as a best practice (can be done via a support case)

Tested VMware Environments

• VMware ESXi: 6.5.0 Update 2 (Build 13004031), 6.7.0 Update 2 (Build 13006603)

• VMware vSphere Client Version 6.7.0

• VMware vCenter Server Appliance 6.7.0

The Cisco Spaces Connector should be able to reach out to the Cisco Spaces endpoints for establishing data connectivity with Cisco Spaces.

For Global Setup (IO)

The Cisco Spaces Connector must be able to reach out to  https://connector.dnaspaces.io/

Primary IP Adresses: 52.20.144.155, 34.231.154.95

Disaster Recovery IP Addresses: 54.176.92.81, 54.183.58.225

For EU Setup (EU)

The Cisco Spaces Connector must be able to reach out to  https://connector.dnaspaces.eu/

Primary IP Adresses: 63.33.127.190, 63.33.175.64

Disaster Recovery IP Addresses: 3.122.15.26, 3.122.15.7

For Singapore Setup (SG)

The Cisco Spaces Connector must be able to reach out to  https://connector.ciscospaces.sg/

Primary IP Adresses: 13.228.159.49, 54.179.105.241

Disaster Recovery IP Addresses: 13.214.251.223, 54.255.57.46

 

The Cisco Spaces Connector must be able to communicate to the WLC on ports:

Normal Operations

• 16113 TCP (NMSP)

• 830 TCP (NETCONF) – only for Catalyst Controllers

• 22 TCP (SSH)

• (optional) 2003 UDP (FastLocate)

IOT Services

• 8004 TCP (TDL)

• 8184 TCP (TDL)

For IOT Services, Spaces Connector and APs must be able to communicate on the following ports:

• 8443 TCP (IOX App Install)

• 8000 TCP (gRPC and REST API calls)

The above is of particular note to customers with public/private cloud environments

For an in-depth guide into the connector please refer to our Configuration Guide.

The first steps in setting up the Connector are as follows.

It is always recommended, if not required for some outcomes, to use the latest version of the Connector available.

Click here for a video guided demo

1. Download the Cisco Spaces Connector OVA from here: Cisco Spaces OVA

2. Deploy the downloaded Cisco Spaces OVA file on a virtual machine.

3. Once the OVA is deployed, log into the VMware console using the default username and password provided in the console, username: root Password:root

4. Enter the network settings.

5. Optional: Enter NTP settings.

6. Set the password for spacesadmin user.

7. When prompted, reboot the device and open the WebUI using the address provided.

8. Log into the Cisco Spaces dashboard, click on Setup on the Menu.

9. Select Wireless Networks.

10. Click on Add New button .

11. Select Cisco AireOS/Catalyst.

12. Select via Spaces Connector, then select Continue Setup button.

13. Under step 2 Configure Spaces Connector, click on Create Connector.

14. In the Connector Name field, enter a name for the connector and click on Create.

15. On step 2 Configure Spaces Connector, click on View Connectors.

16. A list of Connectors that have been created will be seen. Select the desired Connector.

17. Click on Generate Token.

18. Copy the token that appears on the following screen of the Cisco Spaces dashboard.

19. Launch the Cisco Spaces Connector using the HTTP address provided at the OVA deployment, https://< IP-address >/. In the Cisco Spaces Connector window that opens up, enter the username and password that was configured earlier.

20. On Configure connector place the token, and click save.

It may be needed to wait a few minutes for Cisco Spaces connector to start as images may take some time to download. The wait time is dependent on the speed of the connection

The Connector setup is now complete.

This is how the Connector Dashboard and Cisco Spaces Dashboard will look like once the connector is active.

The connector can be deployed in a High Availability configuration. See the linked guide for instructions and restrictions.

Connector Dashboard

Control Channel: Health of connection between Cisco Spaces Connector and Cisco Spaces Cloud.

Data Channel: Health of connection between Cisco Spaces Connector and Cisco Spaces Cloud.

Cisco Spaces Dashboard

If a more in-depth guide is needed for granular configurations please refer to our Configuration Guide.

 

WLC

Recommended firmware versions are 17.12.4+ and 17.15.x

Now the Spaces connector is configured, WLC can be added to Spaces.

1. On the Customized Setup page step 3, click on Add Controllers

2. Select the Connector that was just created from the drop-down

3. Add the IP address of the Controller

4. Add the name of the Controller

5. Select Controller Type

6. Add details based on the controller type.
   For AireOS WLC – Select Controller SNMP version depending on the controller’s SNMP version. Read/Write permissions are needed for V2C and V3

   • For V2C SNMP, provide SNMP Community.

   • For V3 SNMP, provide username, password, select authentication Protocol and enter Privacy password.

   • Enabling the WSA tickbox is used for WIPS purposes in Spaces.

   For Catalyst WLC / Catalyst 9800 – Add the following credentials

   • Enter Netconf Username and Password.

   • Enter Enable password of the controller.

   • Verify the interface: NMSP will only be sent from the interface configured as the “wireless management interface”. Interfaces used as a service-port (e.g., gig0/0 for an appliance) cannot send NMSP traffic.

7. Click on the Test Connectivity button.

8. Click Save & Add Next Controller if needing to add another controller. If not, click Save & Close.

This is how the Spaces dashboard should look once the controller and connector are active.

For an in-depth guide into integrating wireless please refer to our Configuration Guide.

 

Catalyst Center

Integrating Catalyst Center with Cisco Spaces is the easiest way to setup Spaces for any Catalyst based deployment.

Prerequisites follow:

• Catalyst Center, Release 2.1.2.3 or higher.

• Catalyst Center must be able to connect to https://dnaspaces.io:443 for the initial activation. It may also require access to other regions depending on the Cisco Spaces account region.
  See below for more details:

  • https://dnaspaces.io:443 (IO deployments)

  • https://dnaspaces.io:443 and https://dnaspaces.eu:443 (EU deployments)

  • https://dnaspaces.io:443 and https://dnaspaces.sg:443 (SG deployments)

• Floor plans with accurately placed APs inluding heights and angles accordingly. See https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/catalyst-center/2-3-7/user_guide/b_cisco_catalyst_center_user_guide_237/m_work-with-wireless-2d-and-3d-maps.html for more details.

 

GPS markers are crucial to Spaces use cases.

It is reccomended to leverage the Network Map Calibration tool within Spaces rather than Catalyst Center for placing GPS markers.

If placing GPS markers on Catalyst Center, ensuring high accuracy is crucial for a number of use cases.  

1. Log in to Cisco Spaces, and navigate to Integrations.

2. Under Integrations > Cisco > Catalyst Center select Connect. The Catalyst Center integration will show.

3. When the window appears, click Add Instance.

4. In the dialogue box, input a new instance name and then click Generate.

5. Log in to Catalyst Center, and navigate to System > Settings >  External Services > CMX Servers/Cisco Spaces.

6. Next to Cisco Spaces, click Activate, then paste the token into the dialogue box and click Connect.
   This should now show a success notification, and the status should show as Activated.

   

    

7. Now navigate to Design > Network Settings, and select a location that should be pulled through to Cisco Spaces. Suggestion is to configure at a global level if possible.

8. Click the Wireless tab, then in the Cisco Spaces/CMX Server area, choose the service that was configured. This will now trigger a dynamic sync over to location hierarchy within Cisco Spaces.

Confirmation of this can be found in Cisco Spaces, under Setup > Locations & Maps > Recent Activity

 

For an in-depth guide into the integrating with Catalyst Center please refer to our Configuration Guide.

Meraki Wireless

Meraki Wireless

This integration enables to seamlessly connect the Meraki Account to Cisco Spaces via the Meraki Dashboard – in just a few clicks.

There will be an option to select to integrate into an existing Spaces account if you have one,or to create a new one. 

Meraki Wireless Prerequisites

• Meraki Organization admins with read/write access (SAML admins are not supported)

• One building per network

• Floor maps placed accurately against real world both in scale and location

For optimal performance and being able to use all Cisco Spaces capabilities, it is preferred that the Meraki setup have maps with APs placed on them. However, if there are no maps with APs placed on them, Cisco Spaces core analytics features and seamless onboarding features will work.

• APs placed accurately on floor maps. Follow these articles to place APs accurately

  • https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/Monitoring_and_Reporting/Placing_Devices_on_the_Map_in_Dashboard

  • https://documentation.meraki.com/Wireless/Design_and_Configure/Deployment_Guides/AP_Auto_Locate

• Meraki account must be in commercial domain (http://meraki.com). Meraki accounts with the following domains are not supported:

  • Canada = meraki.ca

  • China = meraki.cn

  • India = meraki.in

  • FedRamp = api.gov-meraki.com

• APs must be able to reach the following endpoints on port 1883

  • mqtt.dnaspaces.io (For IO deployments)

  • mqtt.dnaspaces.eu (For EU deployments)

  • mqtt.dnaspaces.sg (For SG deployments)

 

Below are some references to help complete prerequisites:

• Meraki location deployment guide

• Adding floor plans in Meraki

• AP Auto Location guide

• Meraki Integration FAQs

 

To configure the Meraki Spaces Integration

1. Log in to the Meraki dashboard, Navigate to Organization > Integrations

2. Go to Under the Browse tab, Click “Connect” on the “Cisco Spaces” tile

3. Under the Browse tab, Click Connect on the Cisco Spaces tile.

   

  

Option 1: Creating a New Spaces Account

1. To create a new Cisco Spaces account, choose the option Create a new Cisco Spaces Account and click Continue.

Administrators can remove specific networks from syncing to Spaces by using Network Tags in the Meraki dashboard. By default all Meraki networks will sync to Spaces. However the Administrator can apply ‘CiscoSpaces’ as the tag name added to a Meraki network and only networks with ‘CiscoSpaces’ as the tag name will sync to Spaces.
Creating Network tags in Meraki

2. Enter the Spaces Account Name and click on Add Integration. The Spaces Account Name is pre-filled with the Meraki Organization name and can be customized.

3. A new Cisco Spaces account with a unique tenant ID is created. This triggers an invitation email is sent from Cisco Spaces to the Org Admin email address that did the integration as well as anyone designated as a Meraki Organization Admin for the organization. This will also trigger all networks under that Meraki Organization to be synced with Spaces.

After the integration is complete it may take up to 24 hours for applications in Cisco Spaces to start populating analytics data

4. To access the newly created Cisco Spaces account, it is required to accept this invite and setup a password.

The Cisco Spaces welcome email is sent to the Meraki Org admin who triggered the Meraki Integration process. The email is valid for 5 days. The invitation email can be resent by navigating to Use this integration on the integration details page in the Meraki dashboard and clicking on Resend Invite.

5. Launch the Cisco Spaces dashboard from the integration’s details page, review admins and manage networks.

Cisco Spaces Analytics applications will start working after the Meraki Org is fully sync’d with the Spaces account, this could take up to 24 hours for everything to fully sync after the integration is completed.

Option 2: Connecting to an Existing Spaces Account

1. If a Cisco Spaces account already exists, link it to the Meraki Organization. Choose the option that states Connect to existing Cisco Spaces Account and click on Continue.

Administrators can remove specific networks from syncing to Spaces by using Network Tags in the Meraki dashboard. By default all Meraki networks will sync to Spaces. However the Administrator can apply ‘CiscoSpaces’ as the tag name added to a Meraki network and only networks with ‘CiscoSpaces’ as the tag name will sync to Spaces.
Creating Network tags in Meraki: https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/Manage_Tags#Creating_Network_tags

2. Click on Login. The browser will be redirected to Cisco Spaces login page.

3. Enter credentials and click Continue.

4. Type or Choose the respective Cisco Spaces Account to connect to the Meraki Organization from the options listed.

5. Click Select.

6. Once selected to the Spaces account permission will be asked to connect the Cisco Spaces account to the Meraki Organization.

   Check the box next to Import Meraki Administrators as Spaces Administrators and click Confirm.

7. The Spaces Account selected is now linked to the Meraki Organization. This will trigger anyone designated as a Meraki Org Admin for the organization, to be added to the Spaces account as Spaces admin. This will also cause all networks under that Meraki Organization to be synced.

After the integration is complete it may take up to 24 hours for applications in Cisco Spaces to start populating analytics data.

8. Launch the Cisco Spaces dashboard from the integration’s details page, review admins and manage networks.

Cisco Spaces Analytics applications will start working after the Meraki Org is fully sync’d with the Spaces account, this could take up to 24 hours for everything to fully sync after the integration is completed.

Removing the integration (when needed)

Removing the integration (when needed)

1. To remove the integration, in Meraki dashboard, Navigate to Organization > Integrations under the My integrations tab and select the Cisco Spaces integration.

2. From the integration details page select Remove in the top right corner.

3. Select Confirm to remove the integration.

Optional: To remove any Meraki networks from the Cisco Spaces account navigate to Location Hierarchy in the Cisco Spaces account, click the 3 dots to the right of the hierarchy and select Delete Location.

 

Once the integration is completed, navigate to Spaces>Setup>Wireless Networks. Under Connect via Meraki Integration, 1) Connect your Meraki, you should see a green icon next to your organization. Example:

Under 3) Import Meraki Networks into Location Hierarchy, verify that all of the networks (or the ones you’ve tagged with “CiscoSpaces”) have been successfully imported.

Webex Control Hub

Webex Control Hub

Integrating Webex Control Hub with Cisco Spaces allows for granular detail on room occupancy, alongside other use case such as environmental metrics.

The following is a summary of the implementation of work needed to integrate Cisco Spaces and Webex Control Hub. The rest of this section will dive into detail on each of these steps. For more information, continue through this section

Prerequisites

• Devices should be in workspaces

• Workspaces should be on floors, with locations configured with correct building names and addresses

• One building per location(The above is covered in the Location and Maps section below)

• Devices should be configured with the following details:

  • People Count Out of Call​ → ON

  • People Presence Detector​ → ON

  • Ambient Noise Estimation > Interval​ → 10

  • Ambient Noise Estimation > Mode​ → ON

• Workspace > Settings should be as follows:

  • Allow Control Hub to capture workspace metrics from device sensors → Checked

  • Enable sensor data configurations on all supported devices → Checked

• All Workspaces should have capacity set correctly

• All Workspaces should have space type set correctly

 

Below is a guide covering how to ensure your environment is configured as per best practises, and to align with the prerequisites

Intro to Locations in Webex Control Hub

Setting up the structure of Control Hub Locations and Floors is an essential part of the Cisco Spaces integration. A improper structure can add weeks to deployments, result in a degraded end user experience across various outcomes (e.g. Kiosk, Wayfinding, etc.), and cause major downtime to setup properly.

Locations in Control Hub are important for many reasons, including setting up Webex Calling, but the way they are setup and structured can impact other use cases. For example, placing all devices across a campus of multiple buildings into a single Location may result in a Floor list with multiples of Floor 1, Floor 2, etc. For use cases such as Kiosk and Wayfinding, buildings are distinct entities that must be split into separate Locations with their own unique/non-duplicate Floor numbering in order to draw paths and route end users mirroring the physical world. Splitting an existing multi-building Location in Control Hub may result in Webex Calling disruptions and/or added time for setup.

Meanwhile, there are advantages in Cisco Spaces when Control Hub Locations and Floors are setup properly. For example, when a device is organized under a Location > Floor > Workspace, connecting that device to a room becomes easier. Space Manager > Manage Rooms (Space Management) uses a combination of that organization and fuzzy string matching between the Meeting Room name (from the CAD file) and the Webex Workspace name to auto-connect them and use the device for room occupancy outcomes. This automation can save many hours or days of work.

 

Configuring Locations and Floors

Creating Locations and Floors

A Location in Webex Control Hub corresponds to a Building in Cisco Spaces.

If you haven’t created any Location in Webex Control Hub , please follow this guide to bulk create your Locations (aka Buildings): https://help.webex.com/en-us/article/ajh6iy/Locations-in-Control-Hub?dtid=osscdc000283&linkclickid=srch#Add-or-edit-multiple-locations

Floors cannot be created in bulk. Please follow the https://help.webex.com/en-us/article/ajh6iy/Locations-in-Control-Hub#Manage-locations guide to add floors to each Location.

 

Bulk assigning workspaces to floors

1. Select Workspaces (from left nav menu) then enter the Workspaces tab across the top.

2. Select all workspaces for a given floor, then click edit. A new window will appear.

3. Under Location > Location, set the location to the required building.

4. A new element called floor will appear. Select the required floor.

5. Once configuration is finished, click Next.

6. Review the configuration, then click Apply.

7. Ensure configuration took effect with no errors, the click Close.

Workspace Configurations

Enabling required global workspace settings

1. Go to Workspaces > Settings.

2. Check Allow Control Hub to capture workspace metrics from device sensors

3. Check Enable sensor data configurations on all supported devices

 

Bulk assigning capacity to workspaces

1. Select Workspaces (from left nav menu) then enter the Workspaces tab across the top.

2. Select all workspaces with the same capacity, then click edit. A new window will appear.

3. Under Workspace Settings > Capacity, set the value for capacity.

4. Once configuration is finished, click Next.

5. Review the configuration, then click Apply.

6. Ensure configuration took effect with no errors, the click Close.

Bulk assigning space types to workspaces

1. Select Workspaces (from left nav menu) then enter the Workspaces tab across the top.

2. Select all workspaces for a given type (E.G. Meeting rooms), then click edit. A new window will appear.

3. Under Workspace Settings > Type, set the type as required.

4. Once configuration is finished, click Next.

5. Review the configuration, then click Apply.

6. Ensure configuration took effect with no errors, the click Close.

Device Configurations

Bulk enabling required device settings

1. Head to Devices (in the left nav) and select all required devices.

2. Click Edit and a new right hand panel will open. Select All configurations

   

3. On the new page that appears, apply the following configuration:

   1. People Count Out of Call​ → ON

   2. People Presence Detector​ → ON

   3. Ambient Noise Estimation > Interval​ → 10

   4. Ambient Noise Estimation > Mode​ → ON

4. Once complete, click Next

5. Verify changes and click Apply

   

6. Verify that all changes have been applied and there are no errors, then click Close.

 

Integration​

This integration will allow telemetry from selected workspaces to be sent directly from Control Hub to the Cisco Spaces account. This will power room occupancy, booking status, in-room environmental metrics, etc.

 

 

1. Log in to Cisco Webex Control Hub and navigate to Workspaces > Integrations.

2. Find the Cisco Spaces app tile and click Details.

3. Scroll down to review the permissions required (i.e. xAPIs).

4. Check the box to accept the Terms and Conditions.

5. Scroll to the bottom right corner of the page and click Activate.

6. Click Copy to clipboard.

7. Navigate to Setup > Webex in the Spaces dashboard.

8. In the Connect your Webex window, click Connect.

9. In the Enter or copy-paste the Webex Token field, enter the Cisco Webex token, and click Connect.

10. This will result in a sync between Webex Control Hub and Cisco Spaces.

The Cisco Webex synchronization status will display as Active for all active users in a specific tenant (account) if at least one user successfully connected their Cisco Spaces account with the Cisco Webex account while importing the Cisco Webex networks into Location Hierarchy.

 

Configuring the Location Hierarchy

The Location Hierarchy allows businesses to organize their buildings into a recognizable and consistent structure. Cisco infrastructure and sensor telemetry will then be combined, normalized, and standardized into a structure regardless of separate hierarchies across other platforms (e.g. Catalyst Center, Prime, Meraki Dashboard, Webex Control Hub). The hierarchy can be organized based on specific brands, regions, campuses and other taxonomies that are relevant to the business.

By translating the IT network view into a business view, it can be automatically presented with a cleaner business relevant insights report. Any changes to the network topology are automatically reflected here thereby making it easy to manage.

Recommended Route

We recommend following geographical hierarchy as follows:

• Continent or bigger (e.g. Europe, EMEA, APAC)

• Country

• Region (e.g. state, county, city)

• Campus (only if multiple buildings on a single site)

• Building

• Floor

The above is the end goal. The below is the priority of sources in order to achieve this goal.

In order:

• Catalyst Center and/or Excel template

• Meraki Dashboard

• Webex Control Hub

Managing and Merging the Location Hierarchy

Spaces should have by now ingested hierarchies from all integrated platforms: Catalyst Center, Meraki Dashboard, and Webex Control Hub.

This section is designed to merge those hierarchies into a single, business focused hierarchy, to use across the Spaces platform.

1. If there is an existing location Hierarchy it can be viewed under Setup > Locations & Maps.

2. Click on Review.

3. Click on the > sign to expand and review the locations.

4. Click on the drop-down under Action.

5. Choose 'merge with’ to merge same location hierarchies that would have been previously created.

6. Choose the location that needs to be merged from the dropdown under Existing Locations.

   This configuration is hierarchal, meaning configuring this at a campus level, will also configure the same at all buildings and floors below. This can be changed manually on a per location basis as needed.

7. Click Next and Select Agree and continue once reviewed.

8. Review changes and click Merge.

Configuring Metadata

Location Hierarchy Metadata

Meta data is needed for computing accuracy of occupancy at the platform level. See the table below for elements that need configuration.

1. Login into Cisco Spaces and go to Location Hierarchy.

2. Navigate the hierarchy and select a location.

3. Select the Location Info tab

4. Click the blue Edit button next to Location Data.

5. Configure elements as needed, then click Update.

6. Click Save.

7. Continue to configure location data as needed. It is recommended to configure location data for every element within the location hierarchy.

Live Occupancy Metadata

Filtering is another element that is required for accurate occupancy data. As people typically carry multiple devices with them that connect to the network it is essential that there is a method to understand how to get an accurate count for each person, rather than each device. Look below at the table for such methods.

1. Log into Cisco Spaces and navigate to Live Occupancy > Settings.

2. Select the blue pencil next to excluded SSIDs from Live Occupancy analytics.

3. Select all SSIDs that employees do not connect to. Use the guidance below to help determine which SSIDs to select.

4. Click Save.

Digital Map Creation & CAD File Upload

Upload, process, and publish Digital Maps

Once the Location Hierarchy is created, merged, and unified across multiple sources, the next step is to upload CAD files (.dwg) or Vector PDFs to generate a Cisco Spaces Digital Map.

Prerequisites

1. License: Cisco Spaces Advantage, Premier or Premier with Collab & Wireless

2. One CAD or Vector PDF file per floor

3. Separate layers:

   1. Architectural layer

   2. Funiture layer

   3. Space names/IDs/Labels

STEP 1: Under Setup > Locations & Maps

Click on the Digital Maps tab. Either search or choose your desired building and Click Set address if no address is added, or Confirm address if the address is present but unconfirmed.

STEP 2: Set address / Confirm Address:
Provide and confirm the correct building street address using Google address autocomplete.

STEP 3: Create floors by Clicking on “Add/update floors”.

STEP 4: Click on Add new floor to add new floors

STEP 5: Add missing metadata to the floors. Enter floor details and level number. Ensure that all floors are accurately listed with their corresponding level numbers and short names, as these cannot be modified until the map has been processed and published; however, once the map is processed and published, the metadata can be modified.

Verify floor and Click “Save”

STEP 6: Click Add Digital Maps for the desired floor or multiple floors at the building level to upload your CAD or Vector PDF files.

Add Digital Maps - multiple floors at the building level

Add Digital Maps - multiple floors at the building level

Click Choose file to upload the CAD file, then click submit.

You can add new floors and edit existing floor details.

Editing is allowed only for floors that are not currently processing, and or if finished processing must be published first before editing.

Add Digital Maps - single floor

Add Digital Maps - single floor

STEP 7: Upload the CAD/Vectorized pdf file.

Click or drag file here to upload.
Edit the floor details if incorrect and add supplementary information for processing the CAD file.

Select the file from your device and click the Submit button.

Your CAD file submitted for Digital Maps processing, an AI-generated preview will be available in approximately 15 minutes. You will receive an email notifying that the AI Preview is available to review.

STEP 8: The map status is now Processing. The list view will display the status as Processing.

STEP 9: When the AI-generated preview appears, click View to display the AI preview

Sample preview of your map.

STEP 10: Once processed, Processing Status will change to ‘Review pending’. Click “Review building” or “Review floor” to view the processed Digital Maps.

STEP 11: Review building - Review all floors at once.

Add/Edit Room Labels. Once everything looks good, select “Publish”.

Review floor: Review one floor at a time.

STEP 12: The Digital Map is now published successfully

STEP 13: You can set the default map view for the published maps.

Click on “Set default view” against the building.

STEP 14: Adjust the map's center, pitch, bearing, and zoom, then save to set the default view. Use the "Apply to all floors" option to apply these settings across all floors if desired.

STEP 15: Click “Network map calibration” for the selected floor.

Network map calibration

We recommend calibrating your network map to ensure it is aligned correctly with the Digital Map & GPS Markers are placed, enabling precise calculation of client device positions. Learn more: https://runbooks.ciscospaces.io/docs/guide-to-network-map-geo-placement-and-best-practi

STEP 16: Roughly align the network and Digital Map layers to match to map orientation (does not need to be precise in this step), then click the “Next” button.

STEP 17: Click “Add markers” to place markers correlating specific points between maps, which must be exact. Then click the “Save” button to save alignments and markers.

Place at-least 3 markers at the specific points like building corners/room/starting furniture corners etc.

Delete, discard or cancel Digital Maps

Delete Digital Map

Delete Digital Map

STEP 1: Click on Delete map to remove all map versions under the building, including unpublished and published ones. This action may affect linked configurations such as Kiosks, Wayfinding, Occupancy tracking and devices on the map.

Warning: DO NOT delete Digital Maps in order to process an updated floor file. Under Setup > Locations & Maps > Digital Maps > “3 dots” menu on the location/floor list item, you can Add Digital Map to replace the existing Digital Map. The workflow is the same as initially uploading, but after processing, previous Digital Map content will be preserved if there were no structural or name/ID changes to the individual spaces/POIs. This ensure data and device assignment continuity between uploads, while only processing the differences between the CAD file versions uploaded. Deleting the Digital Map erases all database records and cannot be reversed.

STEP 2: Enter all required inputs, including the reason for deletion and additional comments, to confirm the action. Deletion is irreversible.

STEP 3: After deleting all the maps, you can upload a CAD file or Vector PDF to create a new Digital Map if needed.

Discard Digital Map

Discard Digital Map

If something appears incorrect, discard individual floor maps that have been processed but not published, then start over.

Discarding is ideal for fully processed Digital Maps that are obviously incorrect floors or missing elements that you believe are caused by a bad CAD file.

STEP 1: Click “Discard map” next to the floor whose processed maps you want to discard.

STEP 2: Enter all required inputs, including the discard reason and additional comments, to confirm. Discarding is irreversible.

STEP 3: After discarding all the maps, you can upload a CAD file or Vector PDF to create a new Digital Map if needed.

Cancel Digital Map

Cancel Digital Map

You can cancel the maps which are in progress / under processing or AI generated preview maps.

Canceling is ideal for AI Preview that are obviously incorrect floors or missing elements that you believe are caused by a bad CAD file. It is possible the AI output can be corrected by the Cisco Spaces Mapping Team, but if not, they will add a note when rejecting during QA.

STEP 1: Click “Cancel” to stop processing the Digital Maps.

STEP 2: Enter all required inputs, including the reason for cancelling and additional comments, to confirm. Cancelling is irreversible.

STEP 3: After cancelling all the maps, you can upload a CAD file or Vector PDF to create a new Digital Map if needed.

Enabling IoT Services

Now all infrastructure and hierarchy is set up and Digital Maps created, IOT Services can be enabled. IOT Services gives Cisco Spaces the functionality to scan and transmit using the BLE radio.

Catalyst Deployments

Catalyst Deployment

In this section, we will enable IOT Services for Catalyst based deployments. To do this, we will enabled IOT Services on Spaces Connector, then WLC, then required APs.

IOT Services Wizard flow (prefered)

1. Navigate to IoT Services > About and click the Activate button. The About IoT Services window will open.

2. Ensure that Wireless is selected and click Next.

3. The prerequisites will be checked automatically. If any of the prerequisites are not met, resolve this before continuing. Once complete, the IoT Services Activation page will open.

4. By default all compatible connectors, controllers and APs will be enabled for IoT Services. To proceed with this, click Activate.

   1. To customize which connectors and/or APs to deploy IoT Services to, click Click here for customization.

   2. Select the connector(s) where IoT Services will be deployed to and click Activate.

      

   3. Wait for the connector(s) to be activated, then select Activate Wireless.

      

   4. Select all APs required to deploy IoT Services, then select Next and then Activate.
      

      

5. Activation is now underway. Use the menu under IoT Services > About > View Detailed Status to monitor the status of IoT Services.

Use this Deployment Status page to help monitor IoT Services status on a regular basis.

The activation process will be completed when all of the In-Progress deployments, are shown as Success.

Investigate any failed deployments and reactivate the IoT Services.

IOT Services Manual Enablement

Spaces Connector

First, we must enable the IOT Services functionality on the connector. This creates a new container on the connector, pushed through Spaces dashboard.

Installing the IoT Wireless container will automatically enable IoT Services for all associated WLCs. This includes pushing configuration to WLCs

1. Log into Cisco Spaces and head to Setup > Wireless Networks.

2. In the Connect via Spaces Connector section, click on View Connectors, and open the connector you want to deploy IOT Services to.

3. Click on + Add Services, select IoT Wireless, then click Save.

This will begin the install of the IoT Wireless container onto the chosen connector. This will take 5 minutes or more, and will go through the stages of; Queued → In Progress → Complete.

WLC

As mentioned above, enabling IOT Services on Spaces Connector will automatically try to configure IOT Services on the WLC as well. This section will validate this has been completed, and work through common issues seen.

1. Under Setup > Wireless Networks > View Connector, open the required connector, and click the cog icon under the actions menu.

   

2. You will then be shown a list of associated WLCs for this connector, as well as the status of IOT Services configuration for each. We are looking for all WLCs to say SUCCESS.

APs

We have now enabled IOT Services on the required WLC and Connector. In this step we will enable IOT Services on the required Access Points.

Deploying IOT Services to Access Points, should not impact client serving ability of the AP, but there have been occurrences that this has happened. Reccomendation is to deploy during times of low traffic, or outage windows.

1. IOT Services > Manage, and navigate to the building you wish to deploy IOT Services to.

2. Use the checkboxes, to select required APs to deploy IOT Services to.

3. Select from the top bar Action > Manage IOx App > Install IOx App.

   

4. The Bulk IoX App Management panel will then appear. Click Install, then Confirm. This will then proceed to install IOT Services for each of the selected APs.

5. You can confirm this, by clicking on an AP MAC, then opening Request History and viewing the progress.

   

6. You can confirm the install was successfull, when Gateway Status is enabled, and IOX Channel Status is Up for all required APs.
   If this is not the case, see the section below on troubleshooting IOX Install

   

7. Repeat the above steps for all buildings required.

Troubleshooting

Troubleshooting enabling IOT Services on WLC

In the scenario they do not say SUCCESS, they will instead have an error code. You can click the WLC name to find out more information on what succeeded and what failed.

The following is also relevant if you see a WLC showing as DEGRADED, which in most cases implies IOT Services is not enabled on WLC, but is on Connector.

 

Below is the full list of operations in order when enabling IOT Services on a WLC.

1. Enable SCP Server

2. Get Trustpoint 

3. Clean CA Certificate File 

4. Clean CA Certificate Key Pair 

5. Clean CA Certificate 

6. Setup CA Certificate 

7. Finish CA Certificate 

8. Setup Streaming Token 

9. Get Profile 

10. AP Profile - Enable App Hosting 

11. AP Profile - Enable AP Sensor 

12. AP Profile - Enable GRPC Stream 

13. Update Stream setup complete

Most common scenarios for errors

• Netconf credentials are incorrect or user does not have correct privelage levels

• Required ports are not opened either between WLC and connector, or APs and connector

• In cases where IOX app fails to install, likely dont have enough storage. Reload AP or log into AP to delete flash.

After identifying and resolving any issues, you can use the 3 dots in the Action column to Enable Stream again, re-enabling IOT Services for that selected WLC.

Troubleshooting steps enabling IOT Services on AP

Most common scenarios for errors

• Don't have correct netconf credentials or correct privelage levels

• Required ports are not opened either between WLC and connector, or APs and connector. See the Spaces OS Diagram in the Appendix for more info.

• In cases where IOX app fails to install, the AP likely don't have enough storage. Reload AP or log into AP to delete flash.

Meraki Deployments

Support for Bluetooth Low Energy (BLE) devices are available on the Cisco Meraki network, in addition to the existing support on the Cisco Catalyst Wireless network.

This enhancement allows the Cisco Spaces platform to seamlessly integrate with BLE devices using Cisco Meraki. With this enhancement, Cisco Meraki BLE devices can now be accessed in various Cisco Spaces applications, including Firehose IoT Telemetry events, IoT Explorer, Signage, and Live Occupancy.

For this feature to work, you must perform specific configurations on the Cisco Meraki network to enable the data transmission to Cisco Spaces. Data flow is limited to read only, meaning Spaces can simply read the configuration and stream data from Meraki. Use cases such are limited to Scan based only, and configuration of BLE devices is not supported.

Meraki use of IOT is only supported using the Spaces Meraki OAuth integration, and not via the API key mechanism

 

1. Login to the Meraki Dashboard and navigate to Network-Wide > Configure > General. Under Location and scanning verify that the following values are selected

   1. Analytics: Analytics enabled

   2. Scanning API: Scanning API enabled

   3. For Post URL, verify that there are two entries (one for Bluetooth, one for WiFi)

If you need to configure any of these Post URLs manually, follow these steps:

Manual Configuration of Scanning API Post URLs

1. Login to Cisco Spaces and navigate to Setup > Wireless Networks > Connect via Meraki Integration > 2) Configure Meraki Integration > Post URL and click Copy next to the URL

2. Return to the Meraki Dashboard and click Add a Post URL. A new line will be created. Paste the value into the Post URL field.

3. Replace the <URLValidator> part of the URL with the Validator value shown in the field above.

4. Copy the Secret from Spaces > Setup > Wireless Networks > Connect via Meraki Integration > 2) Configure Meraki Integration > Secret Key and paste it into the Secret field next to the Post URL.

5. Select V3 for API version

6. Radio Type WiFi or Bluetooth. You should have one line for each.

7. Click Validate. A new yellow banner will appear to confirm the validation:

8. Click Save to save changes on the page.

2. Navigate to Wireless > Configure > IoT Radio Settings > Bluetooth. Set Scanning to On.

3. Repeat the process for all networks integrated with Spaces.

Meraki Dashboard APIs can be leveraged as a scalable mechanism for enabling IOT Radios. More information can be found here.

4. Navigate to Cisco Spaces > ? (at the top of the page) > Support > Configuration & Deployment Support and click Open a Case. Cisco Support Case Manager will open in a new browser tab.

   1. Copy and paste the following message template into your support case:

      1. Title: Support for MQTT broker configuration

      2. Description:
         Hi,
         We require support with the configuration of the MQTT broker. Scanning API configurations have been completed.
         Please provide the details required for the MQTT broker for the following networks: <list networks>
         Thank you.

   2. Cisco Support Team will provide you the details for the MQTT broker, including the broker password.

5. Navigate to Wireless > Configure > IoT Radio Settings > MQTT and enable MQTT telemetry streaming.

6. Configure the MQTT Broker with the details provided by the Support Team.

7. Navigate all the way down on this page and enable Bluetooth telemetry and Wi-Fi telemetry. Ensure all Additional Message fields are checked.

8. Login to Spaces and navigate to Detect & Locate. Select a location with a Meraki infrastructure and check that the number of BLE tags is non zero.

IoT Services Device Filter

After enabling IoT Services, its generally suggested to enable a device filter. This helps reduce the noise of IoT devices in the dashboard, as well as reduce the load and increase the scalability on the Connector.

To enable IoT Services Device Filter

1. Head to IoT Services > Settings.
   

   

2. Ensure the following is configured:

   1. Allow Public MACs → True

   2. Allow Random Static MACs → True

   3. Allow Random Private MACs → False

DELIVERING OUTCOMES

Now Cisco Spaces OS is complete, which sets up Spaces in the most successful way for now delivering outcomes. Most outcomes should now simply be enabled in a few clicks, and be compatible to run side by side with each other using the same infrastructure. Each outcome will have its own pre-requisites and steps on how to implement them. Use the following Outcomes Runbooks on steps to deliver.

Smart Workspaces

Cisco Spaces Smart Workspaces transforms traditional work environments into dynamic, data-driven ecosystems that enhance productivity and collaboration. By leveraging advanced location-based services, Smart Workspaces enables organizations to optimize space utilization, streamline operations, and create a more engaging workplace experience.

Asset Tracking

Lack of real-time Asset tracking solutions can add critical bottleneck to your supply chain operations and in the healthcare industry, cause life-threatening delays.

With Spaces native apps you can track all devices connected to your network in real time and with a host of partner apps & BLE devices, you can monitor and manage all critical or high value assets in your campuses.

Occupancy

Cisco Spaces provides a comprehensive platform for leveraging location-based services to enhance operational efficiency and decision-making.

The "Occupancy" outcome within Cisco Spaces is designed to monitor and analyze the utilization of physical spaces, allowing organizations to optimize their environments effectively. By integrating real-time data from connected devices and sensors, users can gain valuable insights into space usage patterns, identify trends, and ensure compliance with occupancy regulations.

This documentation will be a guide through the setup process, enabling an organization to harness the full potential of Cisco Spaces for occupancy management and drive informed decisions for space planning and resource allocation.

Captive Portal

A captive portal is the first touchpoint with your business for customers on Wi-Fi. It provides an opportunity to engage with customers who connect to Wi-Fi, offer relevant information, drive monetization, and potentially acquire customer information. Captive portals enable businesses to choose from multiple authentication mechanisms and deliver targeted experiences based on business rules. They can recognize repeat visitors and deliver customized offers, enhancing customer engagement and loyalty.

OpenRoaming

OpenRoaming enables secure, seamless, and automatic network connectivity by eliminating tedious Wi-Fi guest onboarding processes and the risk of connecting to rogue SSIDs. This is especially helpful for a mobile device user trying to access the internet because OpenRoaming removes the need to choose between multiple SSIDs, or enter insecure, shared credentials on poorly designed captive portals.

Indoor Navigation

Indoor Navigation enabled indoor and campus based wayfinding leveraging Cisco Access Points to deliver accurate positioning and routing. Indoor Navigation helps guests and staff effectively find locations within a building, saving time and effort needed.

Smart Rooms

Cisco Smart Rooms seamlessly integrate your existing Cisco Webex devices with your Building Management System (BMS) to provide demand control ventilation, optimize the experience, wellbeing, and productivity of your existing spaces when in use, and reduce energy use when spaces are not in use. 

Space Explorer Web App

The Space Explorer Web App allows flexible access with SSO login (via Webex, Microsoft, and Google Login - more details below) to authenticate end users. The Web App is complementary to the Space Explorer Kiosk app meant to be displayed on a lobby display. In addition to room occupancy and calendar status, the Space Explorer Web App adds Smart Desking functionality to Cisco Spaces workplace experience applications. It is a flexible workspace solution that allows employees to reserve dynamically allocated desks (“Hot Desks”) instead of having assigned seating. It is a key part of hybrid work models and is commonly managed through IoT, AI, and cloud-based platforms.

CAVEATS & TIPS

Placing GPS Markers

GPS Markers are utilised in Cisco Spaces, any time converting between x,y and lat,lon locations.

This function is used by the following apps today, but is likely to expand. Its recommended to implement GPS markers in all deployments of Spaces, even if these features are not used today.

• Space Manager

• Wayfinding

• Smart Workspaces

• App Center delivered use cases

1. Log into Catalyst Center, and navigate to Design > Network Hierarchy, on the left pane select a floor.

2. From the map toolbar, click the GPS Markers toggle.

3. From the map left pane, click the GPS Markers icon.

4. Use the drawing tool to place the GPS marker:

   1. Click on the map to place the GPS marker.

   2. In the Place Markers pop-up window, enter the name, latitude, longitude, x and y coordinates in the appropriate fields.

   3. Click Add GPS Marker.

5. Repeat these steps until there are three GPS markers on the floor map in a polygon-shape.

6. Click Save from the map toolbar.

Wireless Network Design Tips

Overview

The density of a wireless deployment will be a major factor in the accuracy of occupancy depending on the specific outcome needed. Occupancy using Wi-Fi may not require a dense coverage for campus and building occupancy details as it relies on devices connecting to the Wi-Fi network. Moving into an outcome where Floor and Zone level accuracy is required, a denser network deployment is highly recommended.

AP Density Assessment

APs needs to be accurately placed on network maps​ to ensure the best outcomes.

• WLC managed Aps :​

  • AP Auto Locate (preferred)​

    • Note: WLC version 17.12.2+ (required)​

  • AP placement on Catalyst Center (site survey to confirm AP location – required)​

    • GPS Markers for network map and wayfinding map geo-alignment ​

• Cloud managed Aps : ​

  • Geo-alignment of Meraki Dashboard network map​

  • Manual placement of Meraki APs on Meraki Dashboard network map​

AP Auto Locate

• AP Auto locate can provide most accurate information about AP placement​

• Here are more details : AP Auto Locate ​

Catalyst Center

4 or more (minimum of 3) GPS Markers are required, and each should be placed at least 20 meters apart from each other. This is to ensure proper scaling and orientation of Catalyst Center network maps when aligning with Digital Maps on Cisco Spaces.

More details here : GPS Markers for network map and wayfinding map geo-alignment

Meraki Cloud Managed

Please refer to the following : ​

• Geo-alignment of Meraki Dashboard network map​

• Manual placement of Meraki APs on Meraki Dashboard network map

• Additionally, the following video will help illustrate the alignment process: https://app.vidcast.io/share/f1faa92d-66e3-4da1-be78-0b6ec79e9123 ​

AP Placement

The density of AP deployment in terms of “1 AP per X sq ft” can be found by using:

(Number of APs on floor) / (Total Sq ft of the floor)

Number of APs on floor

This information is available from the Spaces Dashboard ​

Navigate to Location Hierarchy, then to the desired building and select the desired floor. On the main page select the Network Devices tab. You will see the number of APs next the Access Points section.

Total Sq ft of the floor​

• This information can be retrieved from the dashboard Location Hierarchy section as long as the manual input has been updated accurately ​

• Otherwise, estimate the floor using Google Maps by providing exact building address and using measure distance feature as shown below

  • This assumes that the floor plan matches the footprint of the building

  • The example below draws along the rooftop of the building as it matches the floor plans within the building

  • Once the points are all connected around the perimeter, Google maps will provide a square footage calculation in the window and the bottom center of the screen

Kiosk List of API Endpoints for Firewall Settings

Meraki Firewall Issues

Depending on security policies of the Meraki environment the following IP addresses may need to be added to be permitted for communication with Cisco Spaces: 

These settings are found under Organization > Settings > Login IP ranges > Allow dashboard API Access to these IP Ranges.

FAQ

Acronyms used

API - Application Programming Interface

BLE - Bluetooth Low Energy

CAD - Computer-Aided Design

DNS - Domain Name System

GPS - Global Positioning System

IoT - Internet of Things

NETCONF - Network Configuration Protocol

NMSP - Network Mobility Services Protocol

SNMP - Simple Network Management Protocol

SSID - Service Set Identifier

vCPU - Virtual Central Processing Unit

VM - Virtual Machine

WLC - Wireless LAN Controller

XREF - Cross Reference

What is Cisco Spaces OS and what are its key features?

Cisco Spaces OS is the fundamental software platform for managing and deploying location-based services within the organisation. It acts as the base installation and seamlessly integrates a suite of critical components designed to streamline operations and enhance data utilisation.

Key features include:

• Onboarding data from various sources like Catalyst Center, Wireless LAN Controllers (WLC), and Meraki for a holistic view.

• Unified location hierarchy configuration for organised network views and access point deployment management.

• Digital Map creation using uploaded CAD files for visual representation of spaces, enhancing navigation, and planning.

• Enabling IoT streaming services, allowing organisations to leverage real-time data insights for better decision-making.

How do I onboard Cisco devices and intake telemetry data into Spaces OS?

Spaces OS supports onboarding data from various Cisco platforms, including Catalyst Wireless, Catalyst Center, and Meraki. Each platform has a specific process for integration.

For Catalyst Wireless:

The Cisco Spaces Connector needs to be installed on a virtual machine, allowing communication with the WLCs. Detailed instructions on configuring the connector, adding WLCs, and establishing connectivity can be found in the Cisco Spaces OS Runbook.

For Catalyst Center:

Ensure Catalyst Center is at Release 2.1.2.3 or higher and accurately placed GPS markers. The integration process involves creating a token in Cisco Spaces, activating CMX Servers/Cisco Spaces in Catalyst Center, and configuring service selection under the Wireless tab in Network Settings.

For Meraki Wireless:

A Meraki account can be connected to Cisco Spaces via the Meraki dashboard. Options are to choose to integrate into an existing Spaces account or create a new one. Detailed steps for both options are available in the Cisco Spaces OS Runbook.

What is Location Hierarchy in Cisco Spaces OS, and how do I configure it?

Location Hierarchy enables the ability to organize the network view within Cisco Spaces based on the physical business locations and access point deployments. This hierarchy can be structured based on brands, regions, campuses, and other relevant taxonomies.

To configure:

1. Access the Location Hierarchy feature under Setup > Locations & Maps.

2. Review existing hierarchies ingested from integrated platforms like Catalyst Center, Meraki, and Webex Control Hub.

3. Merge similar location hierarchies using the 'merge with' option.

4. Configure metadata like Time Zone, Capacity, and Area for accurate occupancy computation.

Why are GPS Markers important in Cisco Spaces OS, and how do I place them?

GPS Markers play a crucial role in converting between x,y and lat,lon locations within Cisco Spaces, ensuring accurate location-based services. They are vital for apps like Space Manager, Wayfinding, and Smart Workspaces.

To place GPS Markers:

1. In Catalyst Center, navigate to Design > Network Hierarchy and select a floor.

2. Enable the GPS Markers toggle from the map toolbar.

3. Use the drawing tool to place markers on the map, providing a name, latitude, longitude, and x, y coordinates for each.

4. Place at least three markers per floor, using prominent features like building corners for accuracy.

How do I create Digital Maps in Cisco Spaces OS?

Digital Maps in Cisco Spaces provide visual representations of the spaces, enhancing navigation and planning.

To create a Digital Map:

1. Go to Setup > Locations & Maps and click the Digital Maps tab.

2. Select the desired building and click "Add Digital Map."

3. Confirm the building's street address for accurate location pin placement.

4. Add floors by clicking "Add new floor" and providing necessary metadata like level numbers and short names.

5. Upload CAD files or Vector PDFs for each floor, ensuring one file per floor.

6. Review and confirm the uploaded files, then submit for processing.

7. Once processed, review the unpublished Digital Map and add/edit room labels.

8. Publish the building to make the Digital Map available in Cisco Spaces.

What are some best practices for uploading CAD files for Digital Maps?

Please refer to the US National CAD Standard for guidance on layer details. 

There are 3 main elements for a great CAD file (.dwg) or Vector PDF with layers:  

1. Architectural layers (e.g. walls, doors, stairs, windows, etc.)  

2. Furniture layer  

3. Space names / IDs / labels

Additional best practices:

• Spaces (Space Type) marked clearly or detail provided. For example, a space with a collaboration endpoint will need a room or desk to assign it to.  

• Have clearly defined or marked POIs like stairs, bathrooms, elevators etc.  

• Room Names:

  • Should be intuitive for end-users

  • Should be made as short as possible whilst keeping readibility (i.e. don’t include building/floor/zone names, room size, room type, etc.)

  • Ideally the room names in the CAD file match the workspace name in Webex Control Hub. Without this, manual mapping of room name to Webex Control Hub workspace must be done.

  • Sometimes, a CAD or Vector PDF file can have multiple such identifiers for the same room. In this case, please leave a comment in the upload workflow with which identifier should be used as a name for the spaces.

• Provide clear layer names in CAD. For example: "A-Furn" (furniture), "Doors" (for doors), ”Windows” (for windows), etc.  

• Keep elements in separate layers. Example: walls, doors, labels in their own layers.  

• Cross Reference (XREF) layers will not be processed. “Bind” them into a single .dwg when exporting from AutoCAD or another program.

How do I export a complex CAD (.dwg) file from AutoCAD with multiple layers that I do not want to include for the Digital Map?

If the CAD (.dwg) file has as a “Layout” tab with the exact layers and objects needed:

1. Right-click on the tab (bottom of the application window on macOS)

2. Choose the “Export Layout to Model…” option

The resulting CAD (.dwg) file will only contain the layers and objects visible in that Layout.

What kind of changes can I expect when re-uploading CAD files to modify existing Digital Maps?

There are a few scenarios where intentionally or unintentionally re-upload CAD files may be necessary:

1. After uploading CAD files for the first time (before finished processing), canceling is perfectly acceptable. Canceling the processing will make it possible to choose different files (if chosen mistakenly or realizing some changes were needed in the file contents) or add/remove files from processing. Otherwise, waiting for the first round of processing (per building) is necessary before adding or removing any floors.

2. After map processing has completed and there are missing objects in the Digital Map (among other reasons - see below), re-upload the exact same file as before and a new reason, comments, and attachments modal appears inline. The reason dropdown categories are:

   1. Missing objects (e.g. walls, furniture)

   2. Missing spaces (e.g. floor space is invisible where a room or other space type should be)

   3. Missing space names/labels (e.g. wrong layer or metadata used for room names)

   4. Changed street address or GPS center-point of building

   5. Multiple reasons or Other (comment below)

Provide additional comments to help our mapping team review the AI processed maps and provide a faster/better update. Optionally include an image with annotations for a holistic picture of the corrections needed.

3. Similar to scenario 2 above, the Location Hierarchy has changed and the exact same files are used to create the same Digital Map in a new Location. Use the appropriate reason dropdown option: “Changed street address or GPS center-point of building”. This also applies to re-uploading when the Cisco Spaces mapping team has declined/rejected a CAD file because the building could not be found on the world map. Please provide additional details in the comments field to help the mapping team accurately align the Digital Map on the world map for accuracy in outcomes.

Note: a building can only exist in one place in the world and cannot be duplicated across multiple Locations in the Location Hierarchy or in multiple Cisco Spaces Tenants. Only the most recent upload will work correctly for outcomes such as Pathfinder on Space Explorer Kiosk and Indoor Navigation App Clip for turn-by-turn blue-dot wayfinding indoors.

4. After CAD files are finished processing and Published, it is safe to upload additional floor files or modify existing with new file versions. Follow the same workflow as before, but either create new floors (w/ metadata) or check the boxes for floors to update specifically to change the files.

Note: re-uploading unchanged floors is not necessary. When re-uploading, only check the boxes for the floors that need to be updated.

5. Currently, it is not possible to delete individual floor Digital Maps. Please open a TAC case to request help removing unwanted files until this feature is available in the dashboard.

6. Currently, it is not possible to process individual floors in parallel in the same Building. Either cancel a map processing job and re-upload or wait for the current process to complete and Publish. Then, proceed with the next upload. Multiple parallel floor uploads in the same Building will be possible in a future update.

Will Webex Workspaces remain connected to the Meeting Rooms after re-uploading CAD files to modify Digital Maps?

There is not currently a way to edit a Digital Map directly with new walls, rooms, or furniture after a CAD file has been processed. To make physical layout changes, upload a modified CAD file to the Cisco Spaces Digital Map platform, and it will attempt to carry forward metadata (e.g. Webex Workspace connection, Meeting Room name manual edits). Generally, metadata associations stay intact in the database as long as the internal identifiers have not changed. Typically, a furniture layout will not create new identifiers, but physically moving walls or changing a room name in the CAD file will create new entities on the backend and erase previous manual edits in the Digital Map Editor (e.g. room name). IoT Sensor associations should carry forward as well.

The Digital Map Editor (under Setup > Locations & Maps > Digital Maps) provides an interface to make lightweight, metadata changes to previously processed CAD files. For example: space names, space IDs, and space types. While it is quite easy to manually make these edits, the source CAD files do not receive those edits.

If new or moved rooms' names are close matches to their respective Webex Workspaces, auto-connecting in Space Manager > Manage Rooms should reduce manual work to associate all collaboration devices with rooms post-processing CAD files.

What do I need to keep in mind for Campus Wayfinding (i.e. indoor-outdoor and inter-building navigation)?

There are several factors that affect Campus Wayfinding and decrease time to process CAD files:

1. Campus wayfinding is performed within a single campus element in the hierarchy. Therefore navigation between buildings must be within the same campus. The campus element is defined as the immediate parent of any building.

2. A group of Buildings (i.e. Campus) MUST fit within a 100km² area (roughly 10km x 10km). To be safe, the distance between the 2 furthest buildings must be no more than 8km.

3. Geo-alignment on the world map is essential. Elements included in the CAD files (e.g. bridgeways, paths, etc.) can help align Buildings to ensure smooth transitions between Buildings in a Campus.

How do I enable IoT Services in Cisco Spaces OS?

IoT Services extend the capabilities of Cisco Spaces by enabling BLE on compatible access points and creating a telemetry stream for data.

To enable:

1. Navigate to IoT Services on the left-hand side menu.

2. Ensure all prerequisites are met and click the "Activate" button.

3. Select "Wireless" and proceed to the next step.

4. The Activation Screen shows the number of active connectors and controllers.

5. It can be chosen to activate IoT services everywhere or customize the deployment by selecting specific connectors, controllers, or APs.

What firewall settings are required for Cisco Spaces Kiosk to function correctly?

To ensure Cisco Spaces Kiosk functions properly, firewall settings might need to be adjusted to allow communication with specific API endpoints. The required endpoints vary based on the Spaces region (IO, EU, or SG).

Refer to the "Kiosk List of API Endpoints for Firewall Settings" section in the Cisco Spaces OS Runbook for the complete list of endpoints for each region. Make sure the firewall permits traffic to these endpoints to prevent connectivity issues with the Kiosk application.

If I complete AP Auto Locate in Spaces will the AP placement sync into Catalyst Center?

No this is not functionality that is available today. AP Auto Locate is planned to migrate to both Catalyst Center and Meraki, so placement is done in those platforms and passed into Spaces.

How can I confirm if netconf is enabled on my WLC?

You can SSH from connector to WLC over the netconf port number (default 830).

ssh -p 830 -s <username_configured_in_Spaces>@<controller_IP> netconf

If the user connects, this proves that connector can establish netconf to WLC using the give user.

APPENDIX

Spaces OS Diagram

Spaces OS Checklist