No-code automation between Maximo and ArcGIS.
Workflows move data between IBM Maximo and Esri ArcGIS based on rules you build visually. A field inspection in Survey123 or Field Maps can create a work order in Maximo, notify the right people, and write the work order number back to the map.
No developers required. Your field crews keep the Esri apps they already use.
Why choose Naviam GIS Workflows?
No code required
Maximo and GIS administrators build integrations themselves by connecting nodes on a canvas.
Esri mobile apps, Maximo results
Crews capture data in Field Maps or Survey123. Workflows turns it into Maximo records.
Geo-enabled logic
Intersections, buffers, proximity, and geocoding are built in, powered by ArcGIS.
Runs when data changes
Webhooks start a workflow the moment a record is saved. Schedules and manual runs are also supported.
Round trip, both systems
Create records in Maximo, then write the result back to GIS so the field sees it on the map.
Extensible connectors
Maximo and ArcGIS over REST, plus email (SMTP), text messaging, and ServiceNow.
Built from nodes
Every workflow is a chain of simple building blocks. Color tells you what each one does: inputs are green, conditions are pink, outputs are blue.
Start
Kicks off the workflow by webhook, schedule, or manual run.
Input
Reads inbound records from a Maximo object structure or an ArcGIS layer.
Switch
If-then logic. Routes each record down a different path based on its values.
Geo
Buffers, intersections, and geocoding against your ArcGIS data.
Mapper
Matches fields in ArcGIS to fields in Maximo, with set or append values.
Output
Creates or updates work orders, routes, features, emails, and texts.
Formatter
Converts data types, including GIS epoch dates to Maximo dates.
Queue, logger, variable
Throttle throughput, see exactly what broke, and share values across every node.
A hydrant inspection, start to finish.
Firefighters inspect hydrants on an iPad. They never think about a work order. Their job is to make the big yellow dots small.
1
Inspect in Field Maps
The inspector taps a hydrant, records poor paint and deteriorated bonnet bolts, and submits.
2
Workflow starts
The new inspection record reaches the input node, ready to process.
3
Switches decide
Deteriorated bolts create a corrective work order at priority 3. Poor paint creates a paint work order.
4
Results flow back
Maximo creates both work orders. The team gets an email. The inspection and hydrant update in GIS with the work order numbers.
GIS and Maximo data on the same dashboard.
Inspection results come from the field in ArcGIS. Repair status comes from Maximo. Workflows keeps them connected, so an ArcGIS dashboard shows what passed, what failed, and what has been repaired.
Every map becomes something your teams operate from, not just look at.
What customers automate
Work management, asset management, and compliance.
Work management
- Generate work orders from field inspections
- Show work order status on a map
- Assign work by area or availability
- Capture labor in the field
Asset management
- Leak reports from Survey123
- Fleet inspections by barcode scan
- Update GIS features from Maximo
- Create routes in Maximo
Compliance
- Hydrant inspection programs
- Email and text notifications
- Pass, fail, and repair tracking
- Full run logs for every record
Organized, scoped, and easy to monitor.
Workspaces. Group workflows in folders and control who can access each one.
Connections. Limit each Maximo connection to specific object structures.
Summary view. See which workflows are enabled, which use webhooks, and when each last ran.
Independent. Workflows runs separately from Maximo and ArcGIS, so changes never touch your core systems.
Flexible deployment. Cloud or on-premises.
Workflows automates the processes around your assets.
PowerSync keeps assets and locations aligned. MapEngine puts Maximo work on the map. Workflows handles everything in between.
Frequently Asked Questions
What is Naviam GIS Workflows?
A no-code process automation web application for ArcGIS and Maximo. It reads, transforms, and writes data between the two systems using rules you build on a visual canvas.
Who builds the workflows?
Usually a Maximo administrator, GIS administrator, or systems analyst with access to both. No developer is needed. Naviam can also build and maintain workflows for you.
How does a workflow start?
Three ways: a webhook fires when data changes in Maximo or ArcGIS, a schedule runs it at set times, or a user runs it manually.
Which systems does Workflows connect to?
IBM Maximo and Esri ArcGIS over their REST APIs, plus email over SMTP, a text messaging platform, and ServiceNow. New connectors can be added.
Does Workflows replace Naviam mobile solutions?
No. It fills the gaps. Many organizations have small teams with specialized processes that fit Esri's map-centric apps better. Workflows brings that data into Maximo.
How do I troubleshoot a workflow?
Logger nodes show the data each step receives and any errors. You can test an input to preview waiting records before you run anything.
Where does Workflows run?
In the cloud or on-premises. It operates independently of Maximo and ArcGIS, so you can update workflows without affecting either system.
Can Workflows run large batches?
Yes. Run in real time or schedule batch jobs. Queue nodes throttle high volumes so Maximo and ArcGIS keep pace.
Power your workflows without writing code.
Power your workflows without writing code.
Connect Maximo, ArcGIS, and more with real-time automation using Naviam GIS Workflows. Streamline operations, eliminate manual steps, and scale your efficiency—starting today.
.avif)
