Welcome back! This is part 2 of our series on implementing Maximo Spatial 7.6. In the first post, we talked about how Maximo communicates with Esri and, in this edition, we’re going to talk about the improvements in the user experience – with the primary focus on administration of the Spatial configuration. Let’s dive in!

At Starboard, when we introduce someone to Maximo Spatial 7.6, we start with reviewing the Map Manager Application, then JSON Mapping and then, finally, the Cron Task Setup. The logic behind this is that, when we’re configuring the system, this is the sequence of the apps we need. Let’s chat about the Map Manager first.

Maximo Spatial ApplicationsMaximo Spatial Applications


The map manager application can be found under the Administration parent menu.

Once we’ve opened the Map Manager application, there are a few different options at the top of the page: We can enable or disable a map, adjust the unit of measure and set Maps for specific sites.

We often get questions about setting up Spatial to use ArcGIS Online or Portal. As you can see, both can be configured in the Map Manager record.

The Map Manager application is also where we can configure Esri Token-Based security.

Finally, the Map Manager application is where we configure Map Services for our map. We can configure a name, the URL for the Map Server, the order it should be drawn on the map, the transparency, and whether the layer is visible by default.

Once the service layer is configured, you will notice (at the bottom of the screen) an area that allows you to enter the JSON mapper for the inbound and response mapping, along with the outbound mapping.

JSON Map Names


Let’s move on to the JSON Mappings Application where these mappings are created.


Under the Integration menu, you will see the JSON Mapping application.


When creating a new JSON mapping, we can name it, provide a description, identify whether the JSON mapping is for an inbound or outbound message, and select the object structure.

JSON Mapping

Under the Properties tab, we define how the available fields on the Map Service map to the Maximo object.

JSON Mapping Properties


Once the maps are registered and the mapping configured, it’s time to establish the schedule for onboarding GIS data.  For this, we are going to look at the Cron Task Setup.


For situations where we want GIS to regularly feed Maximo with new assets, locations, or service addresses, we need to configure the ArcGISDataSync Cron task. The out-of-the-box Cron looks as follows. As you can see, the “Duplicate” button makes it easy to reproduce the out-of-the-box Cron Instance.


If you’re looking for more details on configuring Maximo Spatial, you can check out the following blog post from our friends at IBM.

Look for our future blog posts as we cover the remainder of these 5 points:

  1. How Esri and Maximo Communicate
  2. 7.6 Administrative improvements
  3. Getting your GIS ready for Spatial
  4. How Spatial extends to IBM Mobile
  5. Tips and TricksS

As always, we are also available anytime to answer any questions you may have on Spatial, Maximo, or Starboard! See you next time when we discuss getting your GIS ready for Spatial

Sign up for a recording of our June 6th webinar:  Maximo Spatial, GIS, & Mobility!

Written by: Butch Berlemann, Starboard Consulting Maximo Developer