FSM
One scheduling brain on two different maps.
- ROLE
- Scheduling UX · Mapping interfaces · Frontend development
- PRODUCT TYPE
- Field-service scheduling over live maps
- WHAT IT DOES
- Field-service scheduling, customer sites, and service forms on Google Maps and Leaflet
- BUILDS
- ASP.NET Web Forms 4.6 and .NET 10
- STACK
- ASP.NET Web Forms 4.6 · .NET 10 · C# · JavaScript · Google Maps JS API · Leaflet · SQL Server
- NOTE
- Confidential Xceleran work. Map data and interface details withheld — all visuals are illustrative.
AT A GLANCE
2
Builds
ASP.NET Web Forms 4.6 and .NET 10
2
Map platforms
Google Maps JS API + Leaflet
5
Form auto-fill sources
Customer, appointment, site, equipment, resource
3
Back-office integrations
Accounting sync, SMS, email
THE PROBLEM
Dispatchers think in places and times at once.
Field-service scheduling lives in two dimensions simultaneously: where the work is, and when it happens. A schedule list without geography hides travel reality. A map without time hides sequence. Dispatchers were forced to hold one of the two in their head.
FSM exists to put both dimensions on screen together — jobs plotted geographically, bound to a schedule that shows order, timing, and coverage.
The complication: two mapping technologies, one scheduling logic. The experience had to feel coherent across Google Maps and Leaflet views without pretending the underlying maps were identical.
Scheduling UX
Designing how dispatchers see jobs, order, timing, and coverage — the scheduling surface that sits alongside the map.
Mapping interfaces
Building map-driven views where markers, routes, and job states are working controls, not decoration.
Frontend development
Implementing scheduling and map views in JavaScript with the Google Maps and Leaflet SDKs on ASP.NET Web Forms pages, wired to real operational state.
FSM · Web Forms
ASP.NET WEB FORMS 4.6
Field-service management: jobs, customer sites, and technicians on Google Maps map views, with lightweight Leaflet maps where a simple location view is enough.
FSM · .NET 10
.NET 10
The same product built on .NET 10: the scheduling model, maps and service forms carried onto a modern stack.
J3 sits on the map with no route. The open 13:00 slot is visible in the same view. (Try clicking J3.)
Beyond the map
Customer sites
A customer can have many service locations, so jobs, equipment, and history attach to the right place — not just the account.
Dynamic service forms
Template-based forms auto-assigned to jobs and auto-filled from customer, appointment, site, equipment, and resource data; responses capture signatures and tips.
Connected operations
Accounting item sync, SMS and email communication, and single sign-on from the parent portal keep field and office in one flow.
Map and schedule must agree
A job moved on the schedule changes the route. A job reassigned on the map changes the timing. The two views are the same state — the interface has to behave that way.
Density without noise
Dozens of jobs on one map becomes unreadable fast. Marker hierarchy, clustering behavior, and selective detail decide whether the map is a tool or wallpaper.
Two maps, one mental model
Leaflet and Google Maps have different interaction idioms. Dispatchers moving between FSM’s Google Maps and Leaflet views should not have to re-learn what a pin, a route, or a status means.
THE APPROACH
Shared logic, adapted surfaces
Define the shared scheduling model first
Before touching either map, establish what a job, a route, and a time slot mean across both products. The model is shared; only the rendering differs.
Treat markers as controls, not illustrations
Every pin carries state — assigned, pending, conflicted — and supports action. If a marker cannot be acted on, it should not be on an operational map.
Keep the visual language consistent across both maps
Status colors, typography, and hierarchy stay identical between the Google Maps and Leaflet views, even where the mapping platforms differ. The dispatcher learns once.
Status lives on the pin
Job state is encoded directly in the map marker — not in a side panel the dispatcher has to cross-reference. The map reads at a glance because the status is where the eye already is.
The schedule is always one glance away
Map-first does not mean schedule-hidden. The time dimension stays visible alongside geography so sequence and travel stay in the same field of view.
Let each map do what it does best
Google Maps where base-map richness, places search, and markers matter; Leaflet where a light, fast location view is enough. Consistency comes from the scheduling layer and visual language, not from forcing the maps to behave identically.
BUILD
Design decisions that survive contact with two SDKs
Google Maps JS API
Map views load the Maps JavaScript API with Places and advanced markers. Scheduling state drives marker rendering — one source of truth, many presentations.
Leaflet
Lightweight maps where a quick location view is enough, such as showing where a service form response was captured.
Shared scheduling data
Jobs, resources, and time slots come from the same SQL Server scheduling database, so map and schedule can never disagree.
Consistent visual tokens
Status colors, type, and spacing shared across both products — the dispatcher learns the language once and reads it everywhere.
TAKEAWAY
Maps are working surfaces, not decoration.
The moment a map becomes a backdrop — pretty geography behind a separate workflow — it stops helping dispatchers. FSM keeps the map inside the work: every marker is state, every route is a decision, and the schedule is never more than a glance away.
Two mapping technologies, one scheduling brain, one visual language.