No, it’s a little more complex in Apps 10 now with task handling, but something similar is on the roadmap as part of the user experience features for IFS Cloud 2021R2 release.
Hi Joann,You should probably post this on the board that encompasses Projects...https://community.ifs.com/products-manufacturing-products-engineering-wadaco-40 Thanks and good luck,Jerry
Have them concentrate on giving good fault descriptions. In the future, machine learning will parse fault description for key words as well as the KPI fields such as symptom and readings to do assisted maintenance that should recommend task templates or start new ones.
It’s needs to be to the point from the overview active work orders table like the title of the book. If you want details, you have thousands of characters in the Fault Description field. You don’t need to have the book’s forward in the title. Also, think about how it looks on mobile devices where a technician would have to scroll or pop open a word wrap to juggle a list of ten jobs he’s trying to keep in mind.
Yes, this field is basically a default of what type of PM it is or if it’s a fault that needs acted on. I always used templates to just default “Repair as Required” in the field on fault reports so folks wouldn’t put the fault description here instead of in the fault field. It also picks up the Action description from PMs which would be like Action A - Annual PM, Q - Quarterly PM. So be careful how you use this field and don’t think I’d even consider increasing the character limits.
I’d have to investigate further, but it looks like it’s divided by action code. Although I’d think the maintenance org might be another varible. That’s really a weird PM you put together for fire extinguishers, but I think I see the objective for testing purposes..
If I’m following you correctly, the separation is if you put steps on a grouped and merged PM. For example, I did a quick demo where I have two NC Lathes that I want to do thorough monthly PMs on with task steps 1 through 3. This will generate two separate tasks, one for each machine. I also have three bar feeders that I just want to do visual inspect and cleaning on, so in the same Grouped and Merged PM, I don’t put task step in for them. This creates an additional task with steps for each bar feeder. See below. NC PMs have task steps: The bar feeder PMs don’t have task steps: The resulting PM work order looks like this: Does this help?
Ok, I see what you’re saying now. Maybe it can be added to active work tasks...I’ll run it by RnD.
Are you talking about wanting it to show up in the maintenance plan associated with the task to be able to prove the step was completed for auditors? What are you envisioning?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.