Maximo Spatial

Expand all | Collapse all

New PLUSSGEOJSON columns in Maximo tables?

  • 1.  New PLUSSGEOJSON columns in Maximo tables?

    Posted Tue April 20, 2021 11:21 AM
    Edited by User1971 Tue April 20, 2021 11:22 AM
    After a recent Spatial 7.6.1 iFix, I noticed that I now have PLUSSGEOJSON columns in my Maximo tables.

    select
        wonum,
        plussisgis,
        plussgeojson
    from
        maximo.workorder
    where
        plussisgis = 1


    List of tables with PLUSSGEOJSON column:

    select
        *
    from
        all_tab_columns
    where
        column_name = 'PLUSSGEOJSON'
        and owner = 'MAXIMO'
    order by
        table_name


    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.)



  • 2.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Tue April 20, 2021 11:22 AM
    Edited by User1971 Tue April 20, 2021 11:24 AM

    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





  • 3.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Wed April 21, 2021 05:07 AM
    Hi,
    the very last ifix Spatial7610_ifixes.20210412-1005 adds this new field
    It is for the "GeoJSON representation of the record geometry" (geoJSON | Documentation | ArcGIS Developers)
    I found no documentation about it, so need to be investigated ;-)

    ------------------------------
    Diego Visentin
    EAM BU Director
    Tempestive S.p.A.
    Pordenone
    ------------------------------



  • 4.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Wed April 21, 2021 11:12 AM
    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
    ------------------------------



  • 5.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Thu April 22, 2021 07:55 AM
    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]
    ------------------------------



  • 6.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Fri May 14, 2021 11:26 AM
    Edited by Diego Visentin Fri May 14, 2021 11:32 AM

    Hi,
    In a recently migrated system, I am encountering an error related to this new field.
    When saving a new asset with an associated location that is not "spatialized" (PLUSSGEOJSON is null), the attribute class tries to parse the JSON but being empty it throws an exception:

    [5/14/21 14:49:36:856 CEST] 000007da SystemOut     O 14 May 2021 14:49:36:856 [ERROR] [MAXIMOUI2] [] Expecting '{' on line 1, column 0 instead, obtained token: 'Token: EOF'
    java.io.IOException: Expecting '{' on line 1, column 0 instead, obtained token: 'Token: EOF'
          at com.ibm.json.java.internal.Parser.parseObject(Parser.java:90)
          at com.ibm.json.java.internal.Parser.parse(Parser.java:58)
          at com.ibm.json.java.internal.Parser.parse(Parser.java:47)
          at com.ibm.json.java.JSONObject.parse(JSONObject.java:79)
          at com.ibm.json.java.JSONObject.parse(JSONObject.java:91)
          at psdi.pluss.app.PlusSFldGeoJSON.initValue(PlusSFldGeoJSON.java:73)
          at psdi.mbo.MboValue.initValue(MboValue.java:410)
          at psdi.mbo.MboValue.isNull(MboValue.java:520)
          at psdi.mbo.MboSet.setBindValueAsClob(MboSet.java:9924)
          at psdi.mbo.MboSet.setBindValue(MboSet.java:9562)
          at psdi.mbo.MboSet.insertMbo(MboSet.java:8331)
          at psdi.mbo.MboSet.saveTransaction(MboSet.java:7736)
          at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:221)
          at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
          at psdi.mbo.MboSet.save(MboSet.java:7540)
          at psdi.mbo.MboSet.save(MboSet.java:7464)
          at psdi.webclient.system.beans.AppBean.save(AppBean.java:642)
          at psdi.webclient.beans.asset.AssetAppBean.save(AssetAppBean.java:807)
          at psdi.webclient.system.beans.AppBean.SAVE(AppBean.java:1357)
          at psdi.webclient.beans.asset.AssetAppBean.SAVE(AssetAppBean.java:413)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
          at java.lang.reflect.Method.invoke(Method.java:508)
          at psdi.webclient.system.session.WebClientSession.defaultHandler(WebClientSession.java:1510)
          at psdi.webclient.system.session.WebClientSession.handleEvent(WebClientSession.java:1403)
          at psdi.webclient.system.session.WebClientSession.processRequestEvent(WebClientSession.java:6219)
          at psdi.webclient.system.session.WebClientSession.handleClientSideQueueRequest(WebClientSession.java:6175)
          at psdi.webclient.system.session.WebClientSession.handleRequest(WebClientSession.java:892)
    	  ...

     



  • 7.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Fri May 14, 2021 11:39 AM
    A very new ifix has been available that includes the updated class ... so, cross my fingers ;-)

    ------------------------------
    Diego Visentin
    EAM BU Director
    Tempestive S.p.A.
    Pordenone
    ------------------------------



  • 8.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Fri May 14, 2021 01:36 PM
    I don't have a lot of expertise in this area.
    But I did hear about someone talk about "removing that PLUSSGEOJSON field from the ARCGISASSET object structure" as a possible fix.

    Would something like that help you at all?
    Assuming that you won't be using the PLUSSGEOJSON field in the near future (it's intended for Maximo Mobile), is there a way to just turn off that field? (or the functionality that comes with it?)




  • 9.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Fri May 14, 2021 02:26 PM
    Thank you but my problem was not related to the MIF but to the simple saving of a new asset from the UI.

    PS:
    if you need to exclude the field from an object structure, you can follow these instructions:
    https://www.ibm.com/docs/sk/cdfsp/7.6.0?topic=structure-excluding-persistent-fields-from-object

    ------------------------------
    Diego Visentin
    EAM BU Director
    Tempestive S.p.A.
    Pordenone
    ------------------------------



  • 10.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Wed June 16, 2021 10:23 PM
    Edited by User1971 Thu June 17, 2021 08:39 PM

    FYI

    I had a similar problem where users couldn't save their WOs after using the Spatial/desktop map, due to what we called a "re-fetch" issue.

    BMXAA8229W: Record WORKORDER : Site=SERVICES Work Order=WO21964 has been updated by another user. Your changes have not been saved. Refresh the record and try again.

    We didn't think it was possible that the PLUSSGEOJSON field class would be causing this issue. But, as a last-ditch effort, we disabled the field class for that field, applied config changes/restarted the server, and low and behold, it seems to have fixed that issue.
    We can't seem to reproduce the issue anymore. So that's promising.

    -----------------------------------------------------------------------------------------------

    FYI - Here's a description of the problem:

      

     Details:

     

    1.    Steps:
    The issue happens in multiple applications (WOs, SRs, Assets, & Locations) when the user navigates from the main tab of the application to the map tab.

    a.    The map tab automatically makes an edit to the record behind the scenes.

    b.    Then Maximo wants the user to save the record. But, when the user tries to save the record, it fails:


    2.    Problem Details:

    a.    If the user didn't make any edits to the record, then the error ends up being an inconvenience, but no data is lost. The user can exit the application (without saving), then re-open the record and continue what they were doing.

    b.    However, if the user did make edits to the record, then there is a more serious problem. The user could lose any edits they made since the last successful save - depending on #3 below.

    3.    Partial Workaround:

    There seems to be two scenarios:

    a.    The user can click OK in the error message and hit save again. On the second try, the record will hopefully save successfully.

    b.    Unfortunately though, sometimes when the user tries to save again, it doesn't work. Even after a second or third attempt to save, the user still gets the error message and can't ever save the record. There's not much the user can do at this point other than to exit and re-do their edits to the record.


    Ultimately, until the issue is fixed, our suggestion is to:

    Save the record before -and- after using the map tab…to ensure that the map doesn't prevent saving edits.

     

     

     



  • 11.  RE: New PLUSSGEOJSON columns in Maximo tables?

    Posted Fri May 21, 2021 05:30 PM
    Edited by User1971 Mon June 07, 2021 01:03 PM