- Venue
- ?
- Buildings
- ?
- Floors
- ?
- Area
- ?
- Kiosks
- ?
- Signage
- ?
- Languages
- ?
- Hosting
- ?
- Plans
- ?
AWhat we would set up
- A Studio workspace with the industry pack for your kind of building: its categories, search synonyms, kiosk home tiles and privacy defaults.
- Every floor brought in from the floor plans you have. Rooms, doors, lifts, stairs and the walking routes between them, with six routing profiles and a strict step-free route.
- Kiosks registered in Studio and placed on the plan facing the right way, each with its own “You are here” point, QR hand-off to phones and a 60-second reset for the next visitor.
- Signage screens showing the DigiMaps signage page or directory board, on any player that opens a web page, with live notices included.
- The languages your visitors need, up to 24 per venue, with right-to-left layout for Arabic.
- Our cloud or your own server. We help you decide before the scope is fixed.
- Live operations with your team: closures that re-route visitors within seconds, scheduled notices, and emergency mode on every screen.
- Anonymous statistics from the first day: what visitors search for, where they go and what they cannot find.
- Training for your operators and administrators, with the operator guides and admin manuals.
BWhat you provide
- Floor plans for each floor in the format you have. DXF works best; PDFs and images are fine.
- Names of the places visitors look for, with opening hours where they apply.
- Where each kiosk stands and which way it faces, and what it runs: an Android signage board (Android 9 or later, 2 GB of memory), a Windows kiosk PC or ChromeOS, with Chromium or WebView 111 or newer and WebGL 2.
- The make and model of each signage player, and whether it can open a web page or read an RSS feed.
- Your approved exit information, if emergency mode should show visitors the way out.
- A named person for each job: editing the map, posting notices, and approving releases.
CPhases and typical steps
- 1Plans inWe receive your plans, set the scale, bring in each floor, and agree with you what the map must show.
- 2Map and contentRooms, names, hours, routes and your brand theme, built in Studio. Your team reviews the draft.
- 3ScreensKiosks pointed at DigiMaps, registered with their own device tokens and placed on the plan. Signage players set to open the DigiMaps signage page or directory board.
- 4Check and publishPre-publish checks, review and approval, then the first release. We walk the main routes from each kiosk with your team.
- 5Run the pilotYour team posts closures and notices and watches the statistics. The pilot closes with a review of what a full rollout would take.
How long each phase takes depends on your plans, your screens and how quickly approvals come back. We agree the timeline with you.
DOpen questions
- What kind of building is it? The answer picks the industry pack.
- How many floors does the pilot building have?
- What floor plans do you have: DXF, DWG, PDF, images, or none?
- How many kiosks, and are they already installed?
- Which languages do your visitors need?
- Can visitor data leave the site, and is there internet at the kiosks? The answers decide between our cloud and your own server.
- What date are you working to: a go-live, a tender deadline or a budget cycle?
Draft from the DigiMaps pilot planner. It is not a quote or a contract: scope, price and timeline are agreed with you in writing.