Maximo 7.6: What’s New?

So, Maximo 7.6 has finally been released (On December 12, 2014, IBM Software released Maximo Asset Management 7.6…See download links below), and IBM has created a set of videos that describe a subset of the enhancements that are included in the release. These videos are short and sweet (the longest is just five minutes!) but will help to introduce you to the usability enhancements.

The videos are helpfully divided into two playlists, depending on your level of interest. The first playlist is called Overview of the usability enhancements and is aimed at anyone who wants to get a high-level summary of the enhancements. The second playlist is called Configuring the usability enhancements and is aimed at application designers, application developers and system administrators, and describe how to set up the enhancements. The videos also include links out to further information where appropriate.

Considerations to Upgrading to Maximo Asset Management 7.6
IBM Support strongly recommends that you thoroughly review the Maximo 7.5 to 7.6 Upgrade Guide at the Maximo Upgrade Resources Page. for complete upgrade details and instructions prior to starting any 7.6 upgrade effort. This upgrade information is provided for upgrading from Maximo Asset Management 7.5 deployments that include Maximo Base Services fix pack and fix pack

Reporting options change in v7.5. Existing users of Actuate Reporting and Business Objects Crystal Reports need to evaluate their reporting options in the 7.6 release. v7.6 does not include the reporting integration code specific to Actuate and Crystal Reports and existing 5/6/7.1/7.5 report delivery and configuration options must be reviewed. For additional information, please click here.

Downloading the Upgrade
IBM Maximo Asset Management 7.6 is available for download. Visit the IBM site for information regarding obtaining the update and other information.

For installation instructions, click here for WebSphere or WebLogic

Maximo Hybrid Cloud

Are you looking to use a hybrid cloud option to host your IBM Maximo instance? IBM has a few thoughts regarding this option, as reported by Payal Chakravarty.

Hybrid cloud—the combination of using public and private cloud to host your applications and infrastructure—is becoming the de facto standard for cloud adoption rather than a transitory architecture. According to several industry surveys, 70 percent of organizations are using or evaluating the hybrid cloud today. There are two distinct directions in which the move to hybrid cloud is occurring: private to public cloud and public to private cloud.

Private to public cloud
Enterprises with big IT investments in their on-premises data center are gradually moving certain workloads to the public cloud to gain efficiency, scalability and agility. Those workloads that have sporadic demands are most commonly shifted to the public cloud. Bound by privacy and security restrictions, these enterprises tend to keep their data on-premises in their private cloud.

Public to private cloud
Companies that were born in the cloud and utilized public cloud to scale without spending on an IT organization are realizing that, over time, the public cloud costs add up. It’s like your daily coffee bill. You think you are only spending four dollars every day, but when you look at the cumulative bill at the end of the year, you will be shocked to find out how much you are spending on coffee. You might as well have bought a coffee maker.

(Related: Want to build, manage and secure a hybrid cloud solution? Learn more at

Hybrid cloud applicationsAnother aspect of the move from public to private is that once user demand attains a steady state, the need for auto scaling is not significant. You can save significantly by running a private OpenStack in your own data center instead of running full scale production on a public cloud. These realizations have dawned upon several companies that have started to locate some of their workloads in-house to improve cost efficiency and gain more control over their data and resources.

The movement of workloads from private to public and vice versa is necessitating the need for a stable hybrid architecture.

With this movement, companies must investigate how to span applications across such a hybrid environment. An application typically runs on a stack that comprises:

• Front-end code, which may have dependencies on third-party services
• Middleware such as application servers, web servers, message queues and so forth
• Data sources such as SQL or NoSQL databases
• The operating system

The front end, which needs to auto scale to tune to user demand, is typically the best candidate for being hosted on the public cloud. The middleware and database can reside anywhere. However, the trend indicates databases are the most popular candidates for keeping in house.

To manage the lifecycle of a hybrid application, you need to be able to deploy, manage and monitor across the hybrid cloud. Several tools are evolving to handle this shift.

Tools like IBM Cloud Orchestrator let you define hybrid patterns to solve the deployment problem. This means you have a set of application resources and configurations that spans across your public cloud like IBM SoftLayerand your private cloud based on VMware. You can capture that mapping and configuration as a pattern and deploy that pattern in five minutes across both environments.

Additional tools like IBM Application Performance Management (APM) now let you manage and monitor your hybrid applications with stack components that reside anywhere. If your application’s front-end code is hosted on a public cloud like Amazon or IBM SoftLayer and its back end is a Tomcat server and MySQL database that resides in your own data center, IBM APM tools will discover the two and let you visualize them together in the same pane of glass so that you can see your application’s performance end to end.

Maximo Spatial Database Federation

Originally posted on the developerWorks blog.

Maximo Spatial Database Federation

Author: Rodrigo Dombrowski, Maximo Product Designer & Architect
This article describes the Maximo Spatial architecture that integrates the IBM Maximo Asset Management database with a GIS geodatabase.

All information below is valid for Maximo Spatial 7.5 version.

Maximo Spatial integrates with the GIS database using a concept called database federation, often also called database links.

Database Federation provides the following benefits:

  • No data replication needed as GIS data can be exposed and displayed on Maximo forms
  • Distributed database transactions to ensure consistency
  • Higher performance for batch read and creation of GIS records and Maximo records
  • All Maximo framework functionality and security available when displaying and editing GIS data
  • Multiple geo databases support

Documentation about how to configure Maximo Spatial to integrate with feature class tables is available in:

Documentation about how to expose GIS data to Maximo forms is available in:

The Maximo Spatial database configuration is done independently for each feature class that the client want to integrate with Maximo. This allows supporting multiple geodatabases and feature classes in any database schema. For GIS data insert and updates Maximo Spatial requires that both databases be from the same vendor. Oracle+Oracle, or DB2+DB2, or SQLServer+SQLServer.

Configuration Overview

Configuration Overview

In some cases it is not possible to have both Maximo and GIS database from the same vendor or it is not possible to configure database links.
For these cases currently there are the following options:

Option 1 – Read only mode – No database federation (database link)

  • Same configuration process, including Database Configuration steps, but without database link
  • It makes Maximo Spatial only read-only mode for GIS data
  • Map toolbar tools like selection, query by attributes and update GIS list stays working
  • No GIS record link or cron task will be available
  • No GIS geometry creation and editing from Maximo

Option 1

Option 1

Option 2 – No federation, read/write GIS data moved to local Maximo database

Example: Maximo running on DB2 and GIS data on Oracle database

  • Full Maximo Spatial functionality for the GIS data that is moved to Maximo database
  • No federation required when GIS is on the same Maximo database instance
  • GIS data that can be read only to Spatial can stay on Oracle
  • May require additional ArcSDE license
Option 2

Option 2

Help! Your Maximo Questions Answered

Are you stuck on a particular Maximo question? You can either post up at the for specific questions. But, if you are looking for more general information, IBM has a wealth of information, such as manuals and training videos.  The IBM Education Assistant, or IAE, provides training videos, educational demonstrations, tutorials and other information that is targeted toward the IT professional.

The IEA has just released several new videos:

Other topic of interest:

Maximo V7.1

Maximo v7.1.1

Maximo 7.5

Information originally posted to