Reflections on MIMS data synchronization

Editor’s note: Originally published by SSP Innovations under SSP MIMS. Updated by the 3-GIS Team with the current product name, 3-GIS | MIMS, and other revisions. 

Mobile technology has reshaped how utilities operate, and the ArcGIS platform has evolved alongside it to support mobile workflows. One of the most common GIS-enabled mobile applications in the utility sector is inspections. 

A brief history of the inspection process 

Early mobile inspection workflows were built on ArcGIS for Windows Mobile.¹ Utilities created configurable inspection forms that field technicians used to document the condition of gas distribution assets while working in the field.

As inspection programs grew, utilities needed more than simple data collection. They needed a way to interpret results and determine what should happen next.

That led to the development of an inspection management solution that automated how inspection data was processed inside the enterprise GIS. The system handled two core tasks:

• Interpret inspection results and determine the next action based on configurable business rules. 

• Create the next inspection, assigning a due date based on inspection results and compliance requirements. 

The system was designed to be highly configurable so utilities could adapt as requirements changed. New inspection types, updated compliance rules, and evolving workflows could be supported by adjusting configuration settings rather than rewriting the application.

But over time, that flexibility created its own challenges.

Configuration logic became difficult to interpret and maintain. Source code frequently referenced configuration settings, making the application harder to follow. And some behaviors still required development work even though they appeared configurable, which created confusion about what could truly be adjusted without coding.

Taking the next step 

Technology platforms eventually reach their limits. As mobile GIS platforms evolved, the inspection solution needed to evolve with them. 

A new approach emerged with 3-GIS | MIMS, built on ArcGIS Runtime. MIMS uses sync-enabled feature services to provide both online and offline access to inspection data. Field crews can capture information directly on mobile devices, while enterprise systems maintain a consistent, up-to-date record of inspection activity.

Because these services have specific data requirements, inspection data is often stored in a dedicated database designed to support mobile workflows. Inspections can then be accessed and synchronized directly through feature services, simplifying how field and office systems share information.

MIMS supports the broader goal of connecting field crews with the enterprise system of record so inspection data is captured once and available everywhere.

The new inspection manager 

With the transition to MIMS, the inspection management process also needed to be redesigned.

The updated system retrieves inspection data from feature services, synchronizes results to the enterprise geodatabase, and automatically schedules follow-up inspections based on defined rules.

Lessons from earlier systems shaped the new architecture. The goal was to keep configurability while making the system easier to understand and maintain.

The solution was built using a C# plugin framework. The framework provides base classes with common methods for processing inspection types, such as querying REST services for completed inspections and identifying the related assets.

Configuration still plays a central role. Feature services, object class names, key fields, and inspection intervals can all be adjusted without modifying code. Many inspection workflows can be managed entirely through configuration.

The key difference is how more advanced logic is handled.

Using reflection, the application dynamically loads configurable plugins at runtime. The configuration file defines which methods should run for each inspection type, along with the required parameters. The system then calls the appropriate plugin automatically.

This architecture delivers several benefits:

• Flexible and extensible – complex behaviors can be coded as plugins and added with minimal effort. 
• Easier to maintain – logic is clearly separated between configuration and code. 
• Faster to test and deploy – new plugins can be added without changing the core application. 
  

Conclusion 

The result is a system that balances configurability with clarity.

Utilities can adapt inspection workflows as regulations, infrastructure, and operational needs change, without turning the system itself into a maintenance problem.

With 3-GIS | MIMS utilities gain a practical way to standardize mobile inspection workflows while still supporting the flexibility field operations require.

Ready to simplify your mobile tools? Contact us. 

Citations

¹ Esri. ArcGIS for Mobile. 2012. https://www.esri.com/~/media/files/pdfs/library/brochures/pdfs/arcgis-for-mobile.pdf