Introduction: Why Every Shop Floor Needs a Real-Time Maintenance Map
Imagine your maintenance team responding to faults with instant geospatial insights, pinpointing assets, visualising active work orders and routing engineers along the best path. A real-time maintenance map does exactly that. It combines live data, AI-driven analytics and intuitive mapping so you slash response times and boost productivity across shifts.
This guide walks you through building your own solution using Microsoft Fabric Maps, Azure Maps and iMaintain’s AI-first maintenance intelligence. You’ll ingest streaming work orders, display them live on a dynamic map layer, compute optimised routes and fine-tune the visuals for clarity. Along the way you’ll see how iMaintain bridges reactive maintenance and predictive capability, adding context-aware decision support right at the engineer’s fingertips. Ready to explore what a real-time maintenance map can do for your factory? Explore our real-time maintenance map with iMaintain – AI Built for Manufacturing maintenance teams
Understanding the Foundations: What Is a Real-Time Maintenance Map?
A real-time maintenance map is more than dots on a screen. It’s a live representation of:
- Ongoing work orders and asset faults
- Geospatial clustering of high-priority issues
- Optimal crew routing based on traffic, distance and asset criticality
By visualising streaming data on a map, dispatchers gain a continuous spatial overview. Engineers receive clear guidance, supervisors monitor progress and reliability teams gather analytics for root-cause studies. In essence, you transform siloed CMMS records, spreadsheets and tribal knowledge into actionable geospatial intelligence.
Key benefits include:
- Faster response: crews see the nearest jobs first
- Reduced repeat faults: historic fixes attach to each asset
- Knowledge preservation: location-based context stored for every repair
- AI augmentation: suggestions surface proven solutions at the point of need
With iMaintain’s document and CMMS integration, you don’t rip out existing systems. Instead you layer AI and mapping on top, unlocking maintenance maturity without disruption.
Prerequisites: What You Need Before You Start
Before diving in, make sure you have:
- An Azure subscription with an Azure Maps account and subscription key
- A Microsoft Fabric-enabled workspace (capacity assigned)
- Permission to create Lakehouse, Eventstream, Eventhouse, Notebooks and Maps
- Basic familiarity with Fabric Lakehouse, Kusto (KQL) and notebooks
With those ready, let’s design your streaming pipeline and map visualisation.
Step 1: Create Your Lakehouse and Ingest Sample Work Order Data
First, you’ll simulate your real-time source by uploading a CSV of work order locations into Fabric Lakehouse:
- In your Fabric workspace, select New item → Lakehouse and name it
WorkorderLocationsLakehouse. - Upload
WorkorderLocations.csv(containing WorkorderID, Latitude, Longitude). - In Explorer, open the file, set First row as header and verify the records.
This static file stands in for your actual CMMS or IoT telemetry. Later, a notebook will read and stream it into Eventstream.
Step 2: Stream Work Order Data with Fabric Eventstream
Next, build an event-driven flow:
- New item → Eventstream, name it
WorkordersEventstream. - Choose Use custom endpoint, then add an Eventhouse destination called
WorkordersEventhouse. - Configure ingestion: JSON format, Event processing before ingestion, and publish the stream.
- In the SAS Key Authentication settings, copy the Event Hub name and connection string for your notebook.
Now you have a pipeline that can ingest streaming work orders into a Kusto database in near real time.
Step 3: Simulate Ingestion and Visualise Work Orders on the Map
Use a notebook to simulate events:
- New item → Notebook, name it
WorkorderLocations. - Connect to your lakehouse and install the Azure Event Hub SDK (
%pip install azure-eventhub). - Paste and run Python code that reads the CSV, rounds coordinates, wraps each row in JSON and sends batches to the Event Hub with a 100ms delay.
Once events flow into WorkordersEventhouse.Workorders, create a Kusto function:
.create-or-alter function WorkordersFunction()
{
Workorders
| project Latitude, Longitude, WorkorderID
}
Now build your live map:
- New item → Map, name it
WorkordersMap. - In Explorer, add the KQL database
WorkordersEventhouse. - Locate
WorkordersFunction, choose Show on map, set Latitude/Longitude columns and a 5-minute refresh interval.
Instantly, active work orders appear on the map. Dispatchers can see hot spots and adjust crew assignments on the fly.
To see how iMaintain’s AI layer integrates seamlessly, feel free to Book a demo.
Step 4: Compute an Optimised Route Using Azure Maps Route Directions API
Mapping jobs is great, but optimised routing saves miles and minutes:
- Create a new notebook, connect to the same lakehouse and Eventhouse.
- Query
WorkordersFunction()to pull current work order points. - Build a GeoJSON request body with all waypoints and set
optimizeWaypointOrder=True. - POST to
https://atlas.microsoft.com/route/directions?api-version=2025-01-01, passing your subscription key. - Transform the response so each
Waypointfeature carries anoptimizedIndex. - Write the resulting
OptimizedRoute.geojsonback to the lakehouse.
Back in your WorkordersMap, add the lakehouse file:
- In Explorer, select Lakehouse →
WorkorderLocationsLakehouse→OptimizedRoute.geojson→ Show on map. - Toggle off the original work order layer to focus on the recommended path.
At this point you have a fully automated real-time maintenance map that not only shows jobs but also guides crews along the fastest sequence. If you’re eager to try this in your own plant, Try iMaintain’s real-time maintenance map for modern factories.
Step 5: Customise Your Maps for Clarity
A clutter-free view helps field teams:
- Rename layers to something memorable (e.g.
Optimised Route). - In Map settings, untick Labels at the basemap level so only your data labels stand out.
- For the route layer, enable Data label settings and choose
optimizedIndexwith white text, black stroke, size 20.
Now each stop on the route is clearly numbered. Engineers just follow the sequence without second-guessing.
Need more detail on the workflow? Check out How it works.
Real-World Impact: Why iMaintain’s AI-Driven Map Beats Traditional CMMS
Traditional CMMS platforms manage work orders but lack spatial intelligence. Many AI solutions promise predictive magic but forget the knowledge you already hold: past fixes, asset context, human experience. iMaintain fills that gap:
- It layers on top of your existing CMMS, documents and spreadsheets.
- It captures every repair, builds a shared intelligence base and surfaces proven solutions during troubleshooting.
- The AI assists engineers, it doesn’t replace them, preserving critical know-how as people move roles or shifts.
- Mapping and routing are just one part; every map event, route adjustment and completion enriches your data for future analytics.
The outcome? Downtime drops, repeat issues vanish and your team gains confidence in data-driven decision-making. To see how iMaintain can transform your maintenance operation, Discover the real-time maintenance map – iMaintain AI for manufacturing teams.
Throughout this tutorial, you learned how to:
- Ingest and stream work order data with Fabric Eventstream
- Create real-time Kusto functions and dynamic map layers
- Compute and visualise optimised multi-stop routes
- Tailor your map’s appearance for maximum clarity
This pattern extends beyond maintenance routing to fleet tracking, incident response and asset monitoring. By combining live events, KQL analytics and Fabric Maps, you turn raw telemetry into actionable geospatial insights. And with iMaintain’s human-centred AI bridging the gap, you’re on a clear path from reactive fire-fighting to proactive reliability.
Still curious about ROI? Read our case studies to see how manufacturers Reduce machine downtime and empower their teams. When you’re ready to elevate your maintenance workflow, let iMaintain guide the way.