Most first 3D data map projects fail for a reason nobody puts in the business case: the map gets built, the dashboards look impressive in the steering committee meeting, and then nobody changes a single operational decision because of it. The sensors were fine. The visualisation was fine. What was missing was a clear answer to the question "who does what differently when this number changes?" If you are planning your first spatial data project, that question — not hardware selection — is where the budget risk actually sits.
This guide walks through how to start 3D building data visualisation in a way that produces action within the first quarter, not a proof of concept that quietly expires. It draws on patterns from real deployments across malls, retail portfolios and mixed-use buildings, including what Vemco Group has seen across 2,000+ customers in 95+ countries since 2005.
The instinct on a first project is to scope for the full estate to justify the investment. Resist it. A single asset — one mall, one flagship building, one high-traffic floor — gives you a contained environment where you can validate zone definitions, test alert thresholds against real behaviour, and build the internal case study you will need when procurement asks why phase two deserves funding. Rolling out a proven configuration to ten buildings is a logistics exercise. Debugging a flawed configuration across ten buildings is a career problem.
Choose the asset where operational pain is already visible and measurable: the mall with recurring weekend congestion complaints, the building where cleaning schedules are pure guesswork, the food court where tenants argue about whether footfall justifies their rent. Existing pain gives you a before-and-after story, and before-and-after stories are what keep budgets alive.
Here is a practitioner observation from the field: the zones drawn by the analytics vendor or the IT team almost never match the zones the operations team actually thinks in. A facilities manager does not think "sensor coverage area 4B." They think "the west restroom corridor," "the escalator landing where queues back up," "the section of the food court that fills first." If the zones on your 3D map do not match the mental map of the people responding to alerts, every notification requires translation — and translated alerts get ignored.
So run the zone-definition workshop with operations, security and cleaning leads in the room, not just the project owner. Walk the floor plan together. Name zones the way staff already name them on the radio. This session typically takes half a day and saves months of "what does this alert actually mean?" confusion later.
Alert fatigue kills spatial data projects faster than bad data does. The disciplined approach is to launch with three or four alerts, each mapped to a pain the operations team named themselves. In practice, the strongest first candidates are:
The delivery channel matters as much as the threshold. An alert that lands in a dashboard nobody has open is a report; an alert that reaches the duty manager's phone in map context is an instruction. Platforms like Vemco's deliver alerts via app, email, WhatsApp, SMS, webhook and MQTT, with roughly two-second latency — which means the notification arrives while the situation is still actionable, not after it has resolved itself.
A common budgeting error is assuming a 3D visualisation project requires a new sensor estate. It usually does not. If your building already has people counters or occupancy sensors from Xovis, Milesight, Elsys, Hikvision, Axis or Irisys, a sensor-agnostic platform can typically reuse them — Vemco's does — which shifts your budget from hardware toward configuration, training and change management, where it earns more.
And if your venue is already a Vemco or Mappedin customer, the interactive 3D map with overlaid data is already available inside the Vemco platform. In that case your first project is not a procurement exercise at all — it is the zone workshop and alert configuration described above, which you can run in weeks.
On accuracy: be honest with stakeholders about what counting data can promise. A serious vendor will contract a minimum — Vemco contracts 96% — with typical real-world performance of 98–99% when lighting, layout and visitor behaviour allow. Any vendor quoting a flat guaranteed figure regardless of conditions is telling you what you want to hear.
The 3D map becomes genuinely useful when multiple data types share the same spatial frame. Footfall and sales data (Vemcount), live occupancy (Vemspace) and leasing information (Vemlease) rendered on the same map turn abstract spreadsheets into arguments you can point at: this corridor carries this traffic, this unit converts at this rate, this vacancy sits next to this footfall stream. For mall management teams heading into lease negotiations, that spatial framing changes the conversation. Vemco processes over 85 million counts per day across its customer base, so the underlying data volume is not the constraint — the constraint is always whether it reaches the right person in a form they can act on.
One principle should govern every scoping decision: data on a 3D map only creates value when someone acts on it, and the probability of action rises dramatically when the information arrives in the right spatial context. "Restroom zone west, level 2, threshold exceeded" pinned to the exact location on the map gets a response. A row in yesterday's report does not. Judge every proposed feature, alert and dashboard against that test, and cut anything that fails it.
Expand only after the first asset proves the loop: alert fires, person acts, outcome improves, outcome is documented. That documentation is your phase-two business case, written for you by your own building.
If you are scoping a first 3D data map project and want a straight answer on what your existing sensors can support, which zones and alerts make sense for your building, and what a realistic first-quarter rollout looks like, talk to the Vemco Group team at vemcogroup.com/contact-us — bring your floor plan and your three biggest operational pains, and leave with a concrete starting configuration.