+0.00m / ZONE CS-01
Deployment profiles
What we have built, at what scale, and how it works — published while the customer decides whether to be named. A full case study needs outcomes measured against a baseline, and we say plainly where we do not have them yet.
+0.00m / EXHIBITION & CONVENTION
A national-scale exhibition campus
Our first national-scale deployment: a multi-building convention campus running a major industry exhibition, mapped end to end and opened by visitors from a link rather than an app.
- 7
- Buildings
- 8
- Floors
- 997
- Points of interest
- 156
- Booths, live event
Measured September 2026 · first-party figures from this one venue, not a platform-wide total
What was mapped
- Exhibition halls with every stand drawn as its own place, not a block of colour
- Convention halls and seminar rooms across two levels, with their seating
- Entry gates, registration desks and the walkways between buildings
- Amenities visitors actually search for — food, restrooms, medical, parking
- A walkable navigation graph spanning all seven buildings, with the vertical links between floors
What stayed live
- Booths render from the booking records, so a stand that re-sells on the Tuesday is correct on the Wednesday
- Exhibitor names and partner tiers come from the contract, not a spreadsheet somebody re-keyed
- Sessions and their halls come from the agenda
- A change reaches the visitor portal, the kiosks and the website embed together — there is no export step to forget
Nothing published without passing its checks
Before the venue could go live it had to clear three passes — mapping, navigation, then publish. Disconnected corridors, places not linked to the walkable graph, routes crossing walls and unreviewed AI proposals each block a publish and each name the tool that fixes them.
The plans were not clean, and did not need to be
The campus came in as the drawings that existed, not as a survey commissioned for the purpose. AI proposed the geometry it could recognise and an operator accepted, redrew or rejected every piece of it.
No app, on purpose
Visitors opened the venue from a link or a QR code in the browser they already had. For a show where most attendees arrive once and never return, an install step is the whole adoption problem.
What this profile does not yet have
- The customer's name, until they give written permission to use it
- Deployment time from plan received to map live
- Measured outcomes against a pre-deployment baseline — wayfinding enquiries at the info desk, time to find a stand, or similar
- What did not work, and what we changed because of it
Until those exist this is a profile, not a case study. We would rather publish the gap than a number nobody measured.
Checked against the shipping product on
+0.00m / THE STANDARD
What a Mapnyx case study will state
A case study here will always name a real customer, with written permission, and carry real numbers from the deployment. This is the bar, kept on the page so it can be held against us.
- — The venue: size, floors, industry, and what was mapped
- — The data: which systems feed the map, which records stay live, both directions or one
- — Deployment time from floor plan received to map live
- — Measured outcomes with the baseline they are measured against
- — What did not work, and what we changed
+0.00m / EXIT
Want to be the first named study?
Early deployments get disproportionate engineering attention. That is the honest trade.