Hi Everyone,
As Lacey said, PLUSSGEOJSON field has been included to store the "point" geometry of all GIS objects in Maximo (Assets, Locations, Work Orders and Service Request). It has been delivered as an IFIX over Maximo Spatial 7.6.1, in a way to provide the map functions for Technician and Inspections applications on Maximo Mobile (https://www.ibm.com/support/pages/ibm%C2%AE-maximo%C2%AE-mobile-eam-app-overview or
https://mediacenter.ibm.com/media/IBM%20Maximo%20Mobile%20for%20EAM%20app%20overview/1_o8meukyp/205675823).PLUSSGEOJSON is populated when a Service Address or a Feature Class is associated to Maximo GIS records. It contains the position of the GIS record in GeoJson format (stored as a CLOB in database). Then this field is downloaded on Maximo Mobile as part of datasource synchronization to be available for offline use. The UI of the map component on Maximo Mobile applies the appropriate icons to these points (see screenshot attached by Lacey).
I hope this post helps. We are working to create a detailed technote.
Thanks!
Ana
------------------------------
[Ana Paula] [Brambila]
[LBS Product Architect]
[IBM Brazil Lab]
[São Paulo]
------------------------------
Original Message:
Sent: Wed April 21, 2021 11:11 AM
From: Lacey Lurges
Subject: New PLUSSGEOJSON columns in Maximo tables?
Hi! the PLUSGGEOJSON column was added to support the maps in the graphite framework which is what Maximo Mobile is built on. It contains the geometry of the points to be displayed in the graphite map.
@Ana Paula Brambila can add more details about it :)
Here is a screenshot.
------------------------------
Lacey Lurges
Original Message:
Sent: Tue April 20, 2021 11:22 AM
From: User1971
Subject: New PLUSSGEOJSON columns in Maximo tables?
Notes:
4. The PLUSSGEOJSON column is a CLOB datatype (Oracle). I learned the hard way that a CLOB can be NULL -or- empty. It seemed like I needed to query where length(plussgeojson) > 0 …instead of… where plussgeojson is null ...in order to exclude nulls.
5. I'm not sure what specific iFIx caused this this change. Here is my current build:
- IBM Maximo Spatial Asset Management 7.6.1.0-20210304-2253 Build 20200716-1706 DB Build V7610-15 HFDB Build HF7610-03
- Oracle 19.0
@Lacey Lurges
@Diego Visentin
Original Message:
Sent: Tue April 20, 2021 11:20 AM
From: User1971
Subject: New PLUSSGEOJSON columns in Maximo tables?
After a recent Spatial 7.6.1 iFix, I noticed that I now have PLUSSGEOJSON columns in my Maximo tables.
select wonum, plussisgis, plussgeojsonfrom maximo.workorderwhere plussisgis = 1
Questions:
1. What iFix was responsible for this change?
2. What is the purpose of the PLUSSGEOJSON columns? I googled "PLUSSGEOJSON" but didn't find any results.
3. What is the "search logic" behind the PLUSSGEOJSON column in the WORKORDER table? In other words, how does it determine where to position the WO? (asset vs. location vs. SA, etc.)
Notes:
4. The PLUSSGEOJSON column is a CLOB datatype (Oracle). I learned the hard way that a CLOB can be NULL -or- empty. It seemed like I needed to query where length(plussgeojson) > 0 …instead of… where plussgeojson is null ...in order to exclude nulls.
5. I'm not sure what specific iFIx caused this this change. Here is my current build:
IBM Maximo Spatial Asset Management 7.6.1.0-20210304-2253 Build 20200716-1706 DB Build V7610-15 HFDB Build HF7610-03
Oracle 19.0
#AssetandFacilitiesManagement
#Maximo
#MaximoSpatial