- Organization sizes / types
- Provincial or municipal governments, city-level digital governance offices
- Large state-owned enterprises or city operators (transportation, utilities, parks) responsible for cross-domain coordination
- Industries and verticals where adoption is most applicable
- Smart city, digital government, smart park, smart construction, tourism/attraction management, public safety/municipal policing. Public customer names were not published on the vendor's accessible English-language product page.
- Roles and personas
- Decision makers
- City CIO / Digital Government director
- Public safety or command center leadership
- Smart city program office / urban planning leadership
- End users
- Dispatch and incident response operators
- Urban operations center analysts
- Transportation and utilities operations teams
- Pain points and challenges the product addresses
- Fragmented city data across departments and systems
- Lack of a unified 3D operational view for incidents and asset management
- Need for scenario-based workflows (geofencing alerts, route analysis, resource visualization)
- Qualification criteria: indicators of a strong fit
- The organization already has (or can fund) reliable sources of geospatial and operational data (imagery, BIM/utility models, live IoT/video)
- The organization can commit to ongoing data maintenance and governance rather than a one-off model build
- The organization seeks pre-packaged smart-city applications, not only a visualization layer
- Deal disqualifiers: indicators of a poor fit
- Small municipalities without budget for continuous data/model maintenance
- Organizations that only require basic 3D visualization (these may be better served by lighter stacks)
- Organizations with strict privacy regulations or policies that prohibit biometric processing or pervasive surveillance