To all,
I discussed this with Krishna Dhantam, and it seems that the core application (ASSET, LOCATION and WOTRACK) are hard coded. @Andrew Jeffery already raised a PMR for this, and a more dynamic resolution will be part of the first fix that is delivered after the MAS8.11 GA. This does not only solve the issue I described, but also the challenge when add-ons like HSE, SP, TR, CI are installed (same problem regarding the hard coded core applications).
------------------------------
Jan-Willem Steur
Jan-Willem
------------------------------
Original Message:
Sent: Fri September 01, 2023 01:37 AM
From: Jan-Willem Steur
Subject: IBM Maximo Application Suite Health Standalone - how to change the connection to customer MX / Manage applications?
HI,
We are currently implementing MAS8 Health Standalone as logical follow-up for the deprecated Maximo (7.6) MAHI solution that is currently implemented. Some context:
The client is using Maximo 7.6.1.2 in combination with MAHI 7.6.1.1. There are no plans yet to lift and shift to an entire MAS8 Manage & Health environment, since the client's enterprise architect isn't sure if Maximo as EAM system will be replaced by another system. Having said this, the maintenance and reliability engineering department is full against this decision / plan and disagree the decision taken by the enterprise architect. In the time being the Maintenance and RE department is continuing their setup and innovations to extend MAHI and decided to repacle MAHI by MAS8 Health Standalone (HSA)
The challenge we are facing now it that when opening MAS8 HSA and go the the source record (via the action menu), it is opening the default Asset (ASSET), Location (LOCATION) or Work Order (WOTRACK) application in Maximo 7.6. The client however is using developed clones of the original "Out of the Box" application (e.g. XXWOTRACK, XXASSET or XXLOCATIONS). we have overlooked the system properties, object structures and even the HSA graphite shell (via MAF-TOOLS / Docker), but can't find any entrance / code / setting where we can change this.
What we want to achieve is that it is possible to easily refer to the applications used by the client (regardless whether this is an OOTB or cloned application in the EAM Source environment (in this case MX76)
Who can help me out with a solution / alternative?
Regards,
------------------------------
Jan-Willem Steur
Jan-Willem
------------------------------