IoT Configuration Overview
Understand the IoT Configuration workspace, its systems of record, and its recommended workflow.
Choose the capabilities you need #
Monitoring and IoT intent are independent, optional capabilities. A tenant can monitor operational health without defining desired configuration, manage and remediate IoT configuration without scheduling monitoring, use both, or use neither. Tenant onboarding does not create either capability automatically.
| Tenant setup | Result |
|---|---|
| Monitoring, no IoT intent | Operational health and data-quality monitoring only; configuration-intent comparisons are skipped. |
| Intent profile and monitoring, no published AP intent | Configuration-aware monitoring uses the effective live profile as an alert-only fallback. |
| Published AP intent and monitoring | Exact revision-scoped comparison; automated remediation may be eligible when every safety requirement is met. |
| IoT deployment, no monitoring | Configuration, comparison, publication, and manual remediation without scheduled monitoring. |
Sources of state #
| System | Role |
|---|---|
| WaSense local intent | The desired, reviewable configuration managed by this portal. |
| Cisco Spaces | Observed IoT, AP, floor, and beacon state used for import, comparison, and remediation. |
| Pointr | Indoor-navigation floor mapping and draft beacon state used for comparison and synchronization. |
Publishing a WaSense revision changes the local source of intent. External systems change only when a remediation or synchronization action is explicitly run.
Recommended workflow #
From observed state to verified intent
- Select a supported building-equivalent scope.
- Create the tenant default intent profile if this tenant will use IoT configuration or configuration-aware monitoring.
- Optionally create a named reusable profile and assign it to the building or network.
- Create intent by loading from Spaces, generating a managed set, or importing CSV.
- Review the effective intent profile, AP rows, battery beacons, and floor assignments.
- Compare the working revision against current Cisco Spaces state.
- Publish the local draft when it represents the approved desired state.
- Preview and run only the required Cisco Spaces or Pointr remediation actions.
Supported assignment scope #
IoT intent profiles and monitoring configurations may be assigned to a building or building-equivalent network. They cannot be assigned directly to a floor. Monitoring collects building-level EDM data, then groups reporting and calculations by the floors below that scope.