Maximo Security – Simplifying the UI and Creating / Maintaining Roles

Chris Winston, VP of Strategic Alliances, Projetech
February 21, 2023

Maximo Security is important for license compliance, but that is only the beginning. Security allows you to establish roles to address your business rules, and it is the first step to simplifying Maximo by providing access in line with those roles, removing the extra modules, applications AND actions that are not needed. Maximo Application Suite grows a bit, so there is even more work to do. If you get this done in Maximo 7, the changes migrate forward to Application Suite.

Maximo is huge, having over 150 applications, over 1,000 tables, over 15,000 attributes / fields and so much more. Should every user have access to this? No. Not even every Authorized user. License rules will help to dramatically decrease the number of applications one can see, but that is not enough.

Express level access in general, only allows update to work orders assigned and perhaps do some status changes elsewhere, but that probably means they primarily access 2 applications. Simplifying access for the Express user is not too dramatic, and a sample effort is available here: https://www.youtube.com/watch?v=y2NTdfWM-9g. But remember, Express access goes away with Maximo Application Suite. The least amount is Limited, which allows updates to applications across no more than 3 modules.

As the skin of the user interface continues to change, the vertical spacing and fonts have made it harder to see the actions you have access to without scrolling. As you move to Application Suite, the option to push heavily used actions to the toolbar and remove them from the side navigation is no longer available, so the impact is magnified even further. Many of the heavily used applications have 30 – 40 actions the user can access, with Inventory having over 50 and Work Order Tracking having almost 90. Even with the action menus, the list gets harder and harder to navigate, and when you throw in users using laptops with no external screen and increasing the magnification as well, it can be a little frustrating. ‘Find navigation’ can help, but it is easier to remove what no one uses.

MAS Manage vs 7.6 Skins

Consider removing actions that no one needs first and move on to those that are limited to a select few who are likely admins anyway. For example:

Table

There are many more to potentially remove, and this will not be easy, but in the long term, it removes distractions. Having a demo available for someone to explore is a great way to keep production safe.

Share this post
Chris Winston, VP of Strategic Alliances, Projetech
February 21, 2023
Maximo as a Service

More Blogs

Navigating Maximo v.7.6.1.x End of Support

Navigating Maximo v.7.6.1.x End of Support

On April 12th, 2022, IBM announced the end of support for Maximo v7.6.1.x effective September 30th, 2025. This means no further updates or technical support will be provided. For users not ready to upgrade to the Maximo Application Suite, options include transitioning to MAS AppPoint licenses or obtaining extended support through Projetech’s MaaS solution or IBM’s Extended and Sustained Support, ensuring continued usage and support until a mandatory upgrade by 2027 or later.
Read post
Discovering Maximo IT: Revolutionizing IT Service Management

Discovering Maximo IT: Revolutionizing IT Service Management

Maximo IT revolutionizes IT service management by enhancing efficiency and innovation. Originally the IBM Control Desk, it offers a user-friendly interface, seamless integration, and ITIL-aligned processes, ensuring comprehensive management of IT services, assets, and problems. Key features include efficient reporting, enhanced staff productivity, policy-based automation, and advanced analytics. Maximo IT promises rapid deployment, data management excellence, and cloud deployment options through Projetech's Maximo as a Service, showcasing its adaptability and robustness for modern IT needs.
Read post
Add Validation on Change Status with Automation Scripts

Add Validation on Change Status with Automation Scripts

This blog explores using automation scripts in Maximo to enforce business logic, particularly for validating field requirements upon status changes. It contrasts simpler methods, like Application Designer and data restrictions, highlighting automation scripts' ability to handle complex logic and provide clear, custom error messages. The blog covers practical examples, including required fields for asset status changes and mandatory specifications for operating assets, showcasing how automation scripts improve data integrity and user guidance in Maximo.
Read post

Become a part of our thriving community with over 4,000 Maximo users.

MORE offers users a platform to discover valuable resources and engage in insightful discussions surrounding the intricacies of Maximo software. Connect with peers and experts to explore the depths of possibilities and enhance your expertise.