As described in this topic, ArcGIS includes several patterns for integrating with IBM.
ArcGIS supports the creation and use of enterprise geodatabases in the IBM Db2 relational database offering. Db2 can be used to store spatial datasets, non-spatial tables, and a variety of other data types.
With each software release, Esri works to support the latest versions of the Db2 database software, as explained in this support matrix.
Connections to Db2 databases can be configured as registered data stores with ArcGIS Server sites, and publishers can then create dynamic services that reference data in that database. Query layers can also be created from Db2 databases and published in services or used in ArcGIS Pro workflows.
Maximo Spatial Asset Management is a module in the IBM Maximo platform that allows users within Maximo to spatially view and manage assets, locations, service requests, and work order on a map. It extends Maximo functionality by integrating with ArcGIS through REST feature services.
Maximo Spatial is included with the Maximo Application Suite (MAS) but requires a separate installation, deployed from the application catalog. Maximo Spatial is a separate add-on product for the Maximo Asset Management system that is installed on the administration server.
After Maximo Spatial is installed, an administrator uses the Map Manager application to configure the map and then assign it to the Maximo site. The map is created in ArcGIS Enterprise or ArcGIS Online with referenced feature services. The map is embedded within the Maximo application interface. The version of ArcGIS supported will be dependent on the version of Maximo and Maximo Spatial installed.
Users who have been given privileges to access the map in ArcGIS and in Maximo can click on a map tab from any of the applications that are spatially enabled such as Assets, Locations, Work Order Tracking, and Service Request. Users then select a record that has been linked to a map feature or has a service address with location data.
Maximo Spatial uses the Maximo integration framework (MIF) with ArcGIS Server REST APIs. The MIF uses object structures and communication channels to manage the data exchange between Maximo and external systems such as GIS.
Attributes are added to the GIS feature class tables and the Maximo Manage database tables to create a logical linkage between the GIS tables and the Maximo database tables. The GIS feature classes are published to feature services with the GIS attributes. Cron jobs use the attributes to identify new features and synchronize them to Maximo. Maximo Spatial uses the ArcGISDataSync cron task to manage the synchronization of data between Maximo and ArcGIS. The integration can be configured for one-way or two-way data flow.
The Maximo Mobile app needs to configure the map provider, Map Manager, in order to consume maps and data from an ArcGIS environment. The Map Manager application in Maximo configures and manages the connection to the ArcGIS environment. Maximo Spatial can integrate with other ArcGIS tools such as Field Maps and Survey123 through workflow-based links and URLs. See Integrate through cross-app workflows for additional details.
Maximo Spatial supports offline access so that users can access GIS data when disconnected. ArcGIS feature classes need to be enabled for replica tracking and the ArcGIS Server services need to be published with the synch capability enabled.
When integrating Maximo Spatial with ArcGIS, consider the following best practices.
Always use supported versions of ArcGIS Enterprise, Maximo, and Maximo Spatial.
Configure ArcGIS services to handle the load and use load balancers or Web Adaptors to distribute ArcGIS service calls and provide high availability.
To improve testing and reduce risk of implementing in production have separate environments for development, test, and production. Ideally the test environment should be set up like the production environment.
On both ArcGIS and Maximo servers enable SSL certificates for secure and trusted communication.
Set up ArcGISDataSync cron task to automate record creation from GIS feature services.
Where possible, reduce data duplication by displaying related GIS features on maps without storing the data in Maximo.
Configure map tips to provide additional information about features without leaving the map view.
To isolate processing load from core Maximo services, deploy Maximo Spatial services on a dedicated cluster/JVM.
Up through ArcGIS Enterprise 11.5, use cached services for rendering large polygon features like grids, pressure zones, subdivisions, feeder zones, or substations.
To reduce data errors, use domain validation in JSON mappings.
To improve map performance:
Follow ArcGIS best practices for improving feature service performance by limiting layers and related data to only what is essential, simplifying symbology, limiting use of dynamic or calculated attributes, and utilize minimum and maximum scales for feature layers when publishing.
Apply filters in the JSON integration configuration to restrict feature datasets.
If you are not generating Service Requests, Work Orders, or Assets from the GIS map layer within Maximo, disable auto-create actions.
Use dedicated resources for the Maximo Spatial feature services.
For view-only access, disable Geometry Services.
Limit use of geocoding services to address validation during Service Request creation.
The IBM TRIRIGA Application Suite includes a Location Service for Esri offering which adds additional spatial capabilities to TRIRIGA systems, such as use of indoor positioning systems or Indoor GIS space management.
See the TRIRIGA Application Suite Location Service for Esri documentation for additional details.
IBM has created a connector for the i2 Analyst’s Notebook software experience, which can be used to show maps in the Notebook experience, conduct simple spatial analysis, and integrate layers from ArcGIS Enterprise data sources or public data layers.
For more detailed information, see the IBM documentation for the i2 Analyst’s Notebook Connector for Esri. Note that support for this connector is provided by IBM, not Esri.