A few years ago, Maximo introduced Inspection Forms as part of the Work Center capabilities. Inspection forms are quite powerful when utilized appropriately and can simplify and streamline your inspection process. With this capability, Inspections can now be Preventative Maintenance (PM) driven, with the Inspection and results able to be stored within a work order.
Anyone that’s ever worked with Maximo for any amount of time has almost certainly interacted with a Start Center in some way, shape or form. Extend your Maximo interaction timeline out a little bit, and you’ve probably worked with them a lot. Maybe you’ve read some other blog about “Start Center Best Practices”. What most people seem skip over, or maybe just gloss over, is what NOT to do with a Start Center. Often times, it’s easy to get caught up in creating something for a Start Center that sounds great on paper, but then rapidly starts to diminish the Start Center’s inherit value. What is that “inherit value” you might ask? It’s always going to be quick access to relevant data for the users. Always… Anything that is not “quick” and “relevant” should be looked at as not adding value to the user and avoided.
On July 24, 2020, IBM Software released Feature Pack 126.96.36.199 for Maximo Asset Management. After upgrading to Maximo 188.8.131.52, the Informer Administration Maximo application will remain available, but Informer Developer will simply show a blank page. When this occurs, the system logs may include complaints about License errors and/or ClassNotFoundExceptions.
On August 13, 2020, Interloc Solutions released the Mobile Informer Server 5.8.6 Product Update. This update is recommended for all customers planning an upgrade to Maximo 184.108.40.206 now or in the future. Informer 5.8.6 works on all supported versions of Maximo, and a proactive upgrade of Informer during or in advance of a Maximo upgrade will prevent compatibility issues. Once the Informer upgrade is applied, no further action is necessary during Maximo upgrade.
Introduction I recently ran into an integration where the requirements led me to developing a design where an invocation channel was the best route to synchronously accessing an external financial Mitchell Humphrey web service. The requirements included:
Automation script pseudo-code instruction. I first ran across this about forty years ago when working in a Fortran environment. My team was working on a military contract and to meet a documentation requirement, we were told to use a template for our Fortan code to allow automatic extraction of comments to supply to the customer as part of a way to meet the mil-std 1679 project requirements. One of the gurus there developed the process and program(s) required to do the work and the rest was, in a sense, history.