Upgrade from IBM Control Desk (ICD 7.6.1.5 to Maximo IT

Previously known as IBM Control Desk, Maximo IT is now an add-on to Maximo Manage, now part of the Maximo Application Suite (MAS), featuring new and improved capabilities.

Overview of Maximo IT in Maximo Application Suite

IBM Control Desk has been rebranded as Maximo IT, now available as one of the many add-ons to the Manage application within the Maximo Application Suite. The Maximo Application Suite is an integrated suite of applications built on the Red Hat OpenShift environment, offering multi-cloud portability and support for hybrid cloud and on-premises deployments.

The suite leverages the Red Hat OpenShift deployment model, a platform-as-a-service system centered on containerization and Kubernetes-based orchestration.

After the upgrade to Maximo IT, user licenses are managed directly within the Maximo Application Suite

What's changed in Maximo IT

Maximo IT, formerly IBM Control Desk, was once an independent product. It is now integrated into the Maximo Application Suite, where processes previously managed at the product level are now overseen at the suite level.

Let' see what changes in Maximo IT

• Changes in Licensing Model: Maximo Application Suite uses a new licensing model that leverages AppPoints to track application usage, runtime, and user access. AppPoints are allocated based on your organization’s license entitlement, and you can configure your environment to enforce these allocations. For more information, visit our section on Administering Licenses and AppPoints Usage.?
• Integration Framework: The integration framework in Maximo IT within Maximo Manage enables seamless data exchange with both internal and external applications. It includes predefined content and a toolkit that allows for extending this content to new integration points. Additionally, the framework supports message providers and abstracts messaging queuing features, making Maximo IT independent of specific messaging models such as JMS or Kafka.?

• Changes in Architecture and Deployment: In Maximo Application Suite, installation, configuration, deployment, and upgrades are managed by the Red Hat OpenShift operator. The entire deployment process is built on the Red Hat OpenShift platform, ensuring scalability, flexibility, and efficient management across environments.
• Changes due to Containerization: Containerization is the packaging of software code with just the operating system (OS) libraries and dependencies that are required to run the code to create a single lightweight executable package that is infrastructure-agnostic. As a result of containerization, system properties, integration, and customization processes will differ when upgrading from IBM Control Desk to Maximo IT. This shift to containerized architecture brings changes in how these components are managed and deployed.
• IBM Control Desk Service Portal replaced by Self-Serve: The IBM Control Desk Service Portal has been replaced by the Self-Serve application in Maximo IT. Self-Serve enables users to log service requests, raise tickets, explore solutions and offerings, and interact with service agents to resolve issues. Self-Serve is designed to support only the user persona, unlike the Service Portal, which supported agent and administrator personas as well.?

Click here to learn more about Changes in technology

Architecture and deployment models

The architecture of Maximo Application Suite (MAS) is significantly different from that of IBM Control Desk, as Maximo Application Suite is deployed on the Red Hat OpenShift Container Platform. This technological shift leads to different deployment models for IBM? Maximo IT and IBM Control Desk (ICD)

• Maximo IT Deployment Model: Maximo IT is deployed within Red Hat OpenShift clusters, leveraging the benefits of containerized environments.
• IBM MAS Architecture: IBM Maximo Application (MAS) Suite enhances operational resiliency and reliability. It provides a comprehensive suite of applications, add-ons, and industry solutions that enable teams to unify operations across the enterprise and maintain business continuity.

Migrating of ICD Data to Maximo IT

You can migrate all your IBM Control Desk data to Maximo IT during the upgrade process. Before starting the upgrade, ensure you meet all the prerequisites. It is highly recommended to test the upgrade in a staging environment before proceeding to production.

The migration process includes the following:

• All data
• Customizations
• Workflow processes
• Escalations
• Data validations

Process Overview : The migration from IBM Control Desk to Maximo IT involves a test deployment followed by a production deployment after successful testing. The process includes installing and configuring Maximo Application Suite, creating a customization archive if needed, and then deploying and activating Maximo Manage.

Planning the Upgrade

When upgrading from IBM Control Desk to IBM Maximo IT, it's important to keep several considerations in mind to ensure a smooth transition. Carefully review all pre-upgrade tasks and prerequisites before proceeding with the upgrade.

Upgrade Checklist Before upgrading from IBM Control Desk to IBM Maximo IT, refer to the checklist below.

Upgrade Prerequisites Verify your IBM Control Desk version and prepare your environment by configuring your Red Hat OpenShift cluster for the upgrade.

Testing the Upgrade Before performing the upgrade in the production environment, it’s recommended to validate the upgrade process on multiple testing environments.

Upgrade Process

Upgrading to Maximo IT involves careful planning, preparation, execution of key tasks, and troubleshooting. Allowing sufficient time for each phase of the process ensures a seamless transition. The upgrade process includes the following steps:?

1. Determine the Upgrade Timing: Assess the best time for upgrading to ensure minimal disruption and maximum readiness.?
2. Planning the Upgrade: Create a comprehensive upgrade plan, outlining tasks and timelines for each phase.
3. Performing Pre-Upgrade Tasks: Complete essential preparations such as system backups and compatibility check before starting the upgrade.
4. Upgrading in a Test Environment: Implement the upgrade in a test environment to identify potential issues and ensure compatibility.
5. Troubleshooting Your Test Upgrade: Address any issues found during the test upgrade to ensure a smooth transition to production.
6. Upgrading Your Production Environment: Execute the upgrade in the production environment, ensuring everything functions optimally and efficiently.

Upgrading from IBM Control Desk to Maximo IT represents a significant step forward in the way IT services are managed. With a fully integrated platform, enhanced functionality, and a modernized architecture, Maximo IT empowers organizations to deliver better service, improve efficiency, and scale operations with ease. By carefully planning and executing the upgrade process, you can ensure a seamless transition to Maximo IT, unlocking the full potential of your IT service management.?

For additional details ICD to Maximo IT, click here

If you’d like to learn more about our how to upgrade from ICD to Maximo IT, don’t hesitate to contact Pragma Edge Team at [email protected]