Maximo Open Forum

Travis Herron posted 12-28-2021 09:35

Can you elaborate on what you mean by "work order access"?  Is this read-only access to the application at all (like, until you pass initial new employee training we're not going to let you touch Maximo -- an intriguing idea. . .), read access to certain records, change status to certain statuses, only allow certain work orders to be "assigned" to people with the appropriate qualification, etc.?

Maureen Holland posted 05-24-2022 13:59

Prashant - is there any update to this?  This is the exact scenario.  Can you tell me at a high level what you did to achieve?  Thanks, Maureen

Maureen Holland posted 06-21-2022 17:01

Travis, not be allowed to COMP work orders or add Labor Transactions

Travis Herron posted 06-21-2022 17:26

Maureen,

I can think of a few scenarios where I'd think you wouldn't want it to prevent them.  Let's take two users as examples, Fred and Barney.  Fred is trained on some piece of equipment/has the qualification, Barney does not.

1. Fred and Barney work together on a job.  Fred, being more skilled, does the work while Barney does the "paperwork."  With the setup you're asking for, Barney cannot Complete the work order because he doesn't have the qualification.  He also cannot enter Labor Transactions for himself or for Fred.
2. Barney was assigned this Work Order, and Fred is specifically going with him as an IRL use-case to verify that Barney can safely operate the equipment.  Fred is acting as his trainer, and, assuming Barney demonstrates proficiency, will grant Barney the Qualification. . .or at least tell someone at the home office that Barney has passed the test and should be granted access to the equipment in the future.  Barney cannot Complete the work order or enter Labor Transactions until someone in the home office associates Barney's laborcode with the appropriate qualification.
3. Barney goes and does the job anyways.  He then tries to Complete the Work Order, but he's been restricted.  Then there's a "discussion" that follows about how he shouldn't have done that and Barney looks at you and says, "Well, it's done, so. . .how about getting that Work Order completed?"

The way we handle this kind of thing -- which may not work for your environment or use-case -- is that we have the keys to the equipment loaned out from the office, and an Automation Script that checks to make sure the person borrowing the key has the Qualification.  Following the example above, Barney can't check out the key to the equipment; Fred has to.

Nonetheless, I recommend that you put your efforts into preventing the unqualified laborer from being assigned the work in the first place.  If it gets to him and he does the job. . .he needs a place to record his time and he needs to get it off his to-do list.

Steven Shull posted 06-22-2022 11:18

It's not finished yet but I'm working on something like this for a customer and documenting the solution in a blog post: https://community.ibm.com/community/user/iot/blogs/steven-shull/2022/05/13/enforcing-qualifications-in-maximo . Again, the documentation is not finished but I hope to wrap it up over the next couple of weeks. I have a change I need to make to the scripts to support the status scenario you mentioned as this customer had the same situation where they wanted to prevent completing a WO unless they were qualified. 

On Work Order (and tasks), and job plans/tasks for crossover purposes, we support associating one or more qualifications. In the case it's assigned to the Work Order, that qualification requirement will be enforced on tasks & the work order. If it's assigned to the task, we will only enforce it if the labor transaction, assignment, or planned labor are associated to the task. 

For each qualification, you can define the "level" of the alert. You can prevent it by saying it's an error, you can allow it but warn the user entering the information, or you can say it's silent so we track that we didn't have the qualification but don't display something to the user. 

This gives the future auditability because for each transaction we can see if qualifications were required and whether they were met. We have rules in place to prevent removal of qualifications once the WO has been approved, even if going back to WAPPR, to avoid someone tricking the system.