Database indexing and overall health is very important to a GIS system in general, and especially important when you’re integrating your GIS system. Tasks like rebuilding indexes and statistics can greatly affect your overall system performance. (Look for a future blog that covers suggestions for your database platform’s best practices.) Starboard does advise you to invest time in understanding your system’s vendor-recommended best practices for database health or find a resource with expertise in your platform.
Finally, most organizations have some form of versioning in place and want to know if Maximo Spatial will support versioning. The answer is yes, Maximo Spatial does support versioning, but we do recommend that some form of automated practice be put in place to manage your geodatabase versioning. The logic behind automating your versioning process is two-fold. First, versioning does add to database management overhead but a geodatabase with a well-managed versioning process will make little if any impact to system performance. The second reason is that most versioning strategies do not intend for Maximo to update the default version and instead use a version dedicated to Maximo. A dedicated Maximo version is a sound approach but without reconciling and posting your Maximo edits, GIS users may never see the fruits of your GIS integration.
When it comes to Maximo Spatial 7.6, there are two things you need and two things you should be aware of. For Maximo Spatial 7.6 you need a unique value that will not change on the source system and the ability to create and/or update GIS data via a REST call. You should also be aware that database indexing/health is critical to GIS performance and versioning is supported but an automated process is recommended. Stay tuned for our next post where we will discuss some tips and tricks around Maximo Spatial 7.6.
Contact firstname.lastname@example.org at Starboard Consulting to maximize your asset management technology.
Written by: The Starboard Consulting Team