Maximo Application Suite
Customer-managed

Deploying IBM Maximo Health and Predict - Utilities

Maximo Health and Predict - Utilities supports maintenance, operations, and performance of assets and networks for energy and utility companies.

Before you begin

Deploy Maximo Health before you deploy Maximo Health and Predict - Utilities. For more information, see Deploy Maximo Health

Note: Complete all steps to deploy and activate Maximo Health and enable asset investment optimization. If Maximo Health is not deployed as a part of Maximo Manage, do not complete the system integration or use the data loader until after Maximo Health and Predict - Utilities is deployed and activated. Maximo Health and Predict - Utilities uses the same database as Maximo Health.

The following components must be configured before you deploy Maximo Health and Predict - Utilities:

IBM Watson® Studio on Cloud Pak for Data.: Create at least one project and add the notebook asset type to the project. For more information, see Installing Watson™ Studio.
Maximo Scheduler Optimization.: Maximo Scheduler Optimization is required for asset investment optimization, which you enable as part of deploying the Maximo Health dependency. You do not need to configure the optimization.mofapi or optimization.mofui system properties after you deploy and activate Maximo Scheduler Optimization . However, if you enable asset investment optimization and you are using the limited version of Maximo Scheduler Optimization, all other active models in that Maximo Scheduler Optimization instance are disabled.

If you load data into Maximo Health and Predict - Utilities by using App Connect from Maximo Application Suite 8.8, App Connect 12.0.4 or later, it is supported. The App Connect dashboard must use an App Connect Enterprise Production license. Install App Connect in the Red Hat® OpenShift® Container Platform cluster. For more information, see Configuring IBM® App Connect.

If you use App Connect to load data, in the App Connect Dependencies section,, click Configure. Then, specify the App Connect dashboard URL and user.

Note:

If App Connect is used to load data, before you deploy Maximo Health and Predict - Utilities, configure App Connect.

Set spec.UseCommonServices to false. Ensure that there are no API keys or credentials in the App Connect dashboard. If any API keys or credentials exist, delete them from App Connect, enable authentication, and add them back. For more information, see Editing the settings for a deployed integration server and Configuration reference.

After deployment and activation are complete for Maximo Health and Predict - Utilities, to enable the authentication option, set the spec.UseCommonServices to true.

About this task

Note:

Starting in Maximo Application Suite 8.11, Maximo Health and Predict - Utilities is no longer available as a separate industry solution. The information that is provided is applicable only to Maximo Application Suite 8.10 and earlier versions. For more information, see Upgrading IBM Maximo Application Suite. Before you upgrade to Maximo Application Suite 8.11, deactivate and delete Maximo Health and Predict - Utilities.

The Maximo Models for Electrical Distribution accelerator replaces Maximo Health and Predict - Utilities in Maximo Application Suite 8.11. For more information, see Accelerators and Installing IBM Maximo Models for Electrical Distribution.

The following steps are specific to the Maximo Health and Predict - Utilities industry solution. Complete the predeployment and deployment steps before you activate the industry solution. After you activate the industry solution, you must grant users access to it.

Procedure

In Maximo Application Suite, from the side navigation menu, click Catalog and then select Industry solutions. Click the tile.
On the Maximo Health and Predict - Utilities catalog page, verify the information.
Click Continue.

Note: If insufficient AppPoints are available to deploy this application, you can still complete the application configuration. The application is automatically deployed when the required number of AppPoints are available.
Determine how you want to keep the industry solution up to date.

Attention: Starting in Maximo Application Suite 8.10, the manual deployment for applications that use the installation script for Maximo Application Suite is discontinued. To upgrade Maximo Application Suite and its applications, you must run a conversion script to use a subscription method and subscribe to the upgraded channel. For more information, see Converting IBM Maximo Application Suite from manual deployment to channel subscription.
Click Deploy. After you click Deploy, the deployment process starts in Red Hat OpenShift. The estimated deployment time is an estimate of the time that it takes to configure and deploy the industry solution. The time includes both processing and configuration.

What to do next

Track the deployment process on the Details page or as an administrator, log in to the Red Hat OpenShift web console and from the Red Hat OpenShift cluster, in the navigation menu, click Workloads > Pods. Ensure that you are reviewing either all projects or only the Maximo Health and Predict - Utilities, which is named mas-instance name-hputilities. The Maximo Health and Predict - Utilities operator supports single namespace deployment.

Login to the Red Hat OpenShift cluster. Next, check the Maximo Health and Predict - Utilities deployment status by running the Red Hat OpenShift client command line.

oc get hputilitiesapp -n {{mas-instance name-hputilities}}

The following output shows an example of the status:


NAME        VERSION     STATUS     AGE
devtest     8.5.0       Ready      2d1h

Maximo Health and Predict - Utilities uses the Ready condition reason code of the custom resource to indicate progress. The following reason codes are used:

Ready: The Health and Predict Utilities workspace or application Operator custom resource is up to date and ready to use.
CompatabilityCheckFailure: The operator version is not compatible with Maximo Application Suite or the Maximo Health version.
AppPointReservationFailed: Failed to reserve the app points.

As the industry solution is deployed, the following processes happen in the following order in the Red Hat OpenShift:

The ibm-mas-hputilities-operator-string pod is created, and the status changes to Running.
A instance name -hputilities-entitymgr-ws-string pod is created. You can open the logs for these pods to monitor the deployment. The status changes to Running.
Three instance name -hputilities-model-engine-string pods are created, and the status changes to Running.

The strings are randomly generated sets of numbers and letters.

After the status of all pods is Running, the industry solution is ready to be activated. Activate Maximo Health and Predict - Utilities to configure a workspace and give users access to the industry solution.