To provide occupancy analytics through Wi-Fi infrastructure, 12CU requires access to location and presence information from either Cisco Spaces or HPE Aruba ALE. The network and firewall requirements differ based on the selected platform.
Cisco CMX 10/11 Requirements
Infrastructure Requirements
Cisco CMX 10/11 is a standalone installation hosted by the customer either:
- On-premises.
- In a private cloud environment.
The connectivity will likely be through a VPN to the customer network. Floorplans must be configured for all locations that are to be analyzed.
Firewall Requirements
Firewall should allow access to port 443 on the CMX.
Required Access
- A CMX API user account needs to be created on the CMX CLI.
- Additional CMX read-only (non-API) user to access the GUI is recommended but not strictly required. It may assist us with troubleshooting.
HPE Aruba ALE Requirements
Infrastructure Requirements
Aruba ALE is deployed as a virtual appliance hosted by the customer either:
- On-premises.
- In a private cloud environment.
The environment must provide:
- Sufficient compute resources for the ALE virtual machine.
- Reliable connectivity between Aruba infrastructure and the ALE server.
Access Point Configuration
Access points must be configured to send analytics and RTLS data to the ALE appliance. This applies to:
- Aruba Central managed APs.
- Aruba Instant APs.
Aruba AirWave must have floorplans configured for all locations that are to be analyzed.
Firewall Requirements
Access to the port 443 on the ALE server is needed. On the ALE, 2 "local ports" must be configured.
Lastly, we will provide the customer a "Remote endpoint URL". The customer would need to configure it in the ALE for us to receive data.
Required Access
An ALE account with API access permissions must be created and provided for the 12CU integration.
Location Accuracy Considerations
Occupancy accuracy depends on:
- Access point density
- Floor plan configuration
- Location calibration
- Wireless coverage quality