The Interloc Solutions 100% Maximo Blog

A while ago, I wrote an article on my personal blog on how Use Ant to Deploy Automation Scripts. In the article, I walked through configuring a Publish Channel to export and an Enterprise Service to import Script and LaunchPoint information. I then provided an Ant script that could post data to the Enterprise Service.

The reason for this script is to make it easy to deploy Automation Scripts from a source control repository like SVN or Git. While Migration Manager make it easy to migrate changes from one environment to another, it does not integrate nicely with a source control tool.

I recently needed to diagnose out of memory problems with Maximo.  There is some information in the Maximo logs that can help.  Maximo can display mbo counts and free memory information.  Maximo will also log the number of active users and when crons execute.

We’ve all seen the dreaded “Record has been updated by another user. Refetch and try again.”  It can happen when the record has been updated by another user, but it can also happen when the record is updated by the same user more than once.

In memory, an MboSet owns zero or more MBOs.  Each of those MBOs can have zero or more MboSets which in turn own zero or more MBOs.  Naturally, if your MboSets contain zero MBOs you won’t have problems with records updated by another user.  Problems will arise if two different MBOs reference the same database record and both MBOs attempt to update data.  In memory, these MBOs will be represented as separate Java objects and will be owned by different MboSets.  If only one MBO is updated, it won’t be a problem.  If both MBOs are updated, the first will update the database record and change the ROWSTAMP value.  The second will attempt to update the record but will fail because the ROWSTAMP doesn’t match.  This will trigger an MXRowUpdateException.

When deciding to expand Maximo usage to a mobile deployment, one of the primary considerations is ensuring the system will be both scalable and secure. Delivering data updates securely is important. Mobile Informer uses TLS transport encryption end to end. Supporting a complete offline experience requires supporting all of the Maximo business rules and supporting data by preemptively synchronizing all relevant data.

As we head into the fall season, Interloc continues our dedication to sponsoring these Maximo User Group Events and also our first Federal Industry Mobile Computing Summit rounding out the year.  These events are your opportunity to speak with Interloc’s Industry and Technical Experts and see Interloc's Mobile Informer in person to demo all its Apps, including our NEW Inventory Management!

At my current client, we use a Change Request approach to Maximo changes.  A Change Request is created describing the new functionality desired.  Developers work on these changes in separate Subversion branches.  Change Requests are chosen for a Release, then merged together, tested, and deployed.  The merged changes are then merged back into our Trunk and the process repeats.  Change Requests are not necessarily deployed during the next Release.  It can be several Releases before a Change Request is deployed.

Maximo's Start Center is populated with a number of different portlets.  They provide KPI data, Favorite links, the user's Inbox, among other things.  While it is possible to create custom portlets in Maximo, out of the box functionality does not permit saving them in a Start Center template.

Having looked into how Start Center templates are managed, I have created some extensions that permit saving custom portlets in a Start Center template.  Using these customizations "simplifies" custom portlet design to 10 easy steps.  They are:

Maximo has traditionally been a very powerful maintenance management tool, born from the need to manage downtime and to create work orders against assets, capturing history of work done.

Fast forward to 2016.  Competition has driven maintenance management far beyond the creation of work orders in response to failing equipment.  In most industries, the analysis and ongoing improvement of maintenance effectiveness is just as important as the creation of the product or service in the first place.

In his third post in the series, Greg Hoile, VP of US Operations, Interloc Solutions, explains why Maximo HSE is truly the hidden gem of Maximo

The Maximo Health, Safety, Environment (HSE) add-on was originally built for Oil and Gas industry requirements, but the new release now provides function that provides solutions to industries well beyond Oil and Gas.

In our latest post, Greg Hoile, VP US Operations, Interloc Solutions, shares his thoughts on why every industry should be taking a second look at the "new" Maximo HSE Solution. Read on to see how your business can benefit.

Mobile Informer continues to outperform at GTC.

At the recent MUWG, GTC validated that Mobile Informer continued to be a "game changer" for their Maximo organization.    Read on to find out the latest update from this long-time Mobile Informer client!.