Edge, IoT & Compute · Module
Maps & Location
One location model for territories, beats, routes and verified visits
Maps & Location is planned to give every One3 app geocoded places, geofences, territories, beats, routing and visit verification. It stores geography only: customers stay in the shared party and address records, jobs stay in Field Service and account ownership stays in CRM.
What it does
Maps & Location gives every One3 app one location model and the operations built on it. Maps render with MapLibre over self-hosted OpenStreetMap-derived tiles or a licensed provider. Geocoding and routing sit behind pluggable providers, so Indian address quality can come from Indian providers where their terms allow.
Territories that change ownership properly
Territories can be drawn, imported from GeoJSON, KML or PIN-code CSV, or generated, in a zone → region → territory hierarchy with owners, effective dates and overlap detection. Balancing proposals weigh account count, CRM potential, visit effort and travel time. Publishing a territory version does not overwrite CRM: it proposes account-owner changes through CRM Actions with approval and a dated cut-over, with extra approval when high-value open deals are affected. Published versions are immutable.
Routes, beats and visits
The module plans multi-stop routes with time windows, skills, capacity, breaks and depots, and returns them as proposals to Field Service dispatch and Fleet. Beat planning builds day-of-week outlet visits by outlet class. Visit verification tests check-in proximity against the location, flags mock locations and records time and accuracy. Unverified visits are never auto-rejected, and no pay or incentive is reduced automatically.
Privacy for people who move
Live field tracking runs only on shift, after notice and an acknowledgement or recorded lawful basis, and stops at shift end even offline. Individual traces are visible only to roles with tracking permission, every trace view is logged, and managers see aggregates. Customer tracking links show rounded positions and expire.
What is different
Most location tools are generic APIs wired in by an integrator. Here territories, beats and routes sit on the same records as CRM, Field Service, Fleet and Expenses, so mileage from verified routes can become expense lines and a geo question in Copilot respects row-level permissions.
Features
What Maps & Location includes
Base maps
MapLibre rendering on web and mobile with a tile source per tenant region, India boundary layer for India tenants, attribution, and light, dark and high-contrast styles.
Geocoding and address quality
Provider plug-ins with per-tenant fallback order, match level and confidence, batch geocoding, PIN-code validation, locality normalisation and a low-confidence queue.
GeoLocation registry
Points and polygons for parties, sites, assets and outlets with source, accuracy radius and history.
Object maps
Map any permitted list (accounts, leads, outlets, jobs, technicians, devices) with clustering, heatmaps and a list-view alternative; permissions applied before rendering.
Geofences
Circle and polygon fences with entry, exit and dwell events from mobile, telematics or IoT; each fence has a purpose and retention.
Territories and balancing
Hierarchies with owners and effective dates, overlap detection and side-by-side balancing proposals.
Territory publish to CRM
Account-owner changes proposed through CRM Actions with approval and a dated cut-over.
Routing, ETA and optimisation
Distance and time matrices by vehicle profile, multi-stop optimisation with time windows, skills, capacity and breaks.
Beat planning
Outlet beats and day-of-week visit plans by outlet class, with coverage gaps shown.
Live field tracking
On-shift sampling with notice, interval policy, battery awareness and automatic stop at shift end.
Visit verification
Proximity check-in with mock-location flag, time and accuracy, optional geo-time stamped photo.
Geo layers and catchments
Import GeoJSON, KML, Shapefile or CSV layers; drive-time isochrones and density inside catchments.
Mileage, offline packs and tracking links
Mileage lines to Expenses from verified routes, offline region tile packs, and time-boxed 'technician on the way' links over portal or WhatsApp.
Copilot geo questions
Ask 'customers within 5 km of the Pune depot with open tickets' and get a permitted query with map and list.
Workflow
Territory design to CRM ownership
- 1
Import or draw territories
- 2
Validate overlaps and unknown PIN codes
- 3
Review a balancing proposal with metrics
- 4
Sales head approves the version
- 5
Publish with a cut-over date
- 6
CRM owner-change proposals created through CRM Actions, with extra approval for high-value open deals
- 7
Owners notified; beats and dashboards updated
Workflow
Route optimisation for dispatch
- 1
Dispatcher selects date, technicians and jobs in Field Service
- 2
Maps sends windows, skills and capacity to the routing engine
- 3
Routes and unassigned jobs return as a GeoRoute proposal
- 4
Dispatcher approves or edits
- 5
Assignments go out through Field Service Actions
- 6
Technician check-ins feed visit verification
AI
AI skills and Digital Employees
Address standardisation
Parses Indian addresses, normalises locality and PIN, ranks provider candidates and explains low-confidence matches.
Territory balancing with rationale
Proposes balanced territories and explains the trade-off with the metrics used. Publishing is never done by an agent.
Route optimisation with constraint explanation
Lists unassignable jobs with the binding constraint in plain words.
Beat plan generation
Day-wise outlet sequences per rep from frequency class, travel time and coverage gaps.
Visit anomaly explanation
Explains why a visit was marked unverified (accuracy radius, mock location, clock skew) and the remedy.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Which map and geocoding providers will it use?
Providers are pluggable per tenant: self-hosted OpenStreetMap-derived tiles or a licensed provider, and India-capable geocoders such as MapmyIndia Mappls or Google Maps Platform where their terms allow. Provider terms are recorded and verified before build.
Will it track my field staff all day?
No. Tracking runs only on shift for roles whose policy enables it, after notice, and stops at shift end even offline. Individual traces are restricted and every view is logged.
Can visit verification cut a rep's incentive?
No. Unverified visits are never auto-rejected and no pay or incentive is reduced automatically from verification results.
Does publishing a territory change CRM owners directly?
It proposes owner changes through CRM Actions with approval and a dated cut-over. This module never writes CRM tables.
See Maps & Location in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.