We are happy to announce the release of Change for Maximo, the next step in our quest to improve and complement Maximo and SmartCloud Control Desk.
Organizations spend significant amounts of money in the maintenance of Maximo itself, which is definitely a good practice, but we realized that the purpose of many of the tasks that ended up in the hands of Maximo technical experts could be completed by the users themselves in a fraction of the time… if only Maximo enabled them to do so. Likewise, we found that many customization projects could be significantly shortened in both time and resources by making Maximo more flexible in certain areas.
So we started building Change for Maximo, which currently covers two areas: classifications and renaming. Let me mention just some of the most relevant features in these areas.
Classifications and specifications are powerful. With them you can add structured information to records without changing the definition of the objects, and associate and organize records based on a logical hierarchy. While by default Maximo lets you classify a limited set of objects (assets, locations, items, work orders, etc.), Change for Maximo enables you to make any object classifiable (including custom objects) and to add a Specifications tab to any application in order to leverage the power of classifications and specifications.
In this same area, we noticed that the three value fields in all specifications were a source of clutter and confusion for must users, so we introduced a unified value field that supports ALN, NUMERIC and TABLE values. We are already working on exciting new features for this unified field, but we’ll talk about them when they are ready.
Additionally, we introduced a Reclassification Assistant that will help you resolve conflicts in the specifications when moving a record from one class to another one. This will help keep the data quality up and prevent data loss.
The other area is renaming. We included tools to change the name or id of any object. Your computer lab
COMPLAB03 is now a conference room? No problem: rename it to
CONFROOM01 without losing all the maintenance history and assets associated to the location. This is the type of changes that renaming will help you with. There are other tools in the marker that allow you to do just that, but we made sure our product was unique and had all the batteries included. These are some of the exclusive features we built:
- Rename any Maximo object. Yeah, ANY object, even custom ones.
- Batch rename. Use the command line to rename based on your own logic.
- Keep a history of all renaming operations. We make renaming easy, but it’s still a good idea to know when a rename operation occurred, who started it and what records were affected.
- Organization, site and set awareness. The renaming engine is aware of the organization, site and set of the target record and will take this into account when changing the database.
- Dynamic renaming. Manage from Maximo itself how the renaming engine should behave when dynamic fields (those that may reference multiple objects) have to be renamed. For example, the record key in the
RELATEDRECORDtable can be either a ticket or a work order.
In order to protect you and as a warranty we have build Change for Maximo in such a way that you can at any time disable some or all of its features and go back to the standard functionality. As a further warranty, we provide email and phone support as well as unlimited upgrades for a yearly fee.