Is there a solution to accurately show the total hours required for a Multitask in the Work Order Projection report on MP2? Currently, the report only displays a fraction of the actual time needed for multiple machines on one Preventive Maintenance task. For example, a task that takes 1.5 hours across 10 machines shows as only .15 hours on the report. When multiplied by 16 similar tasks, MP2 incorrectly shows a total of 19 hours instead of the accurate 76 hours. This discrepancy makes it challenging to distribute the workload evenly across three shifts until the end of the year.
Do you know which version of MP2 you have installed? How have you configured your Task? I recently set up a Task that involves 3 pieces of equipment and estimated it would take 3 hours to complete. After running the projection report, it accurately displayed the 3-hour timeframe.
To enhance your efficiency, consider enhancing a routine task by incorporating three new pieces of equipment. Alternatively, create a new task, adjust the time parameters, and verify its printing accuracy. It is important to establish a suitable averaging period for optimal results.
I successfully updated the task with additional equipment, completed and closed it, and adjusted the hours accordingly, leading to an accurate Projection Report. I'm uncertain about your reference to the average period.
When it comes to forecasting, inputting a timeframe for Task Duration and Estimated Labor Hours is key. For a project manager overseeing 7 machines, entering TD = 0 and EL = 4 results in a projection report showing .8 hours. Adjusting the values to TD = 3 and EL = 7 yields a projection of 1.4 hours. Alternatively, changing the inputs to TD = 3 and EL = 3 gives a task projection of .6 hours. Any insights or suggestions on improving these projections are welcomed.
I utilize this feature to optimize time allocation for multiple machines. By releasing a task as a single unit, the system averages the time and distributes it accordingly. Alternatively, by separating the time into individual releases, it assigns the total time to each machine. This method enhances efficiency and productivity in managing machine workloads.
I've encountered this issue with MP2 as well. While there's no one-size-fits-all solution, a workaround I have been using is to make an Excel file with two columns: one for the Multitask and one for its actual duration. From there, I'd export the Work Order Projection report to the Excel file and use a VLOOKUP function to replace the duration with the accurate number from my created table. I agree that the software should do a better job at calculating this, but until it gets fixed, this workaround might help you distribute the workload more accurately.
From my experience with MP2, I believe the application records tasks independently and does not account for a single task spanning multiple assets. To counter this, a workaround could be to list each machine as a separate task within the preventive maintenance job. Although this would increase the number of entries, it would accurately capture the total hours you need across all machines. That being said, it'd be truly beneficial if Infor adds a feature in future updates allowing multi-asset task time capturing to save us this trouble. It'll not only streamline planning but also improve the efficiency of resource allocation across shifts.
This seems like a limitation within MP2's reporting module, and I agree it can certainly impact accurate resource allocation. You may have to use a workaround for now, like manually calculating the total hours and adjusting your schedules accordingly. However, it would be beneficial to report this to your software vendor - they can either propose a solution or include it as a feature request in the software's next update. Sometimes software developers aren't really aware of these specific use-cases until users like us bring it up to them.
It sounds like you're facing a significant challenge with the hour reporting in MP2. It might be worth looking into whether there are any customizable settings or report configurations that could help aggregate total hours more accurately across multiple tasks. Another option could be to create a manual workaround, like using a spreadsheet to calculate the actual hours and then incorporating that data into your planning. In the meantime, have you reached out to the support team for MP2? They might have insights or updates on how to handle this more effectively, especially if other users have reported similar issues.
It sounds like you’re dealing with a frustrating reporting issue in MP2! One possible workaround could be to manually adjust the hours in your projections based on the actual time each task requires, although that can be tedious. It might also be worth reaching out to the software support team to see if they have any updates or enhancements in the pipeline to address this reporting limitation. If multiple users are experiencing the same problem, it could prompt them to prioritize a solution. In the meantime, keeping a detailed log of estimated versus actual time for each task could help in managing the workload more effectively across your shifts.
I totally understand the frustration with the Work Order Projection report showing those inaccurate hours; that kind of misleading information can really complicate workload distribution. One possible solution could be to create a custom report or utilize a more detailed task breakdown that reflects the total time required for each machine within the multitask, rather than averaging it out. It might also be worth reaching out to the MP2 support team to see if they have any updates or tools that could help address this issue, as accurate data is crucial for planning effectively.
It sounds like a frustrating issue with the MP2 reporting functionality! One potential workaround could be to manually aggregate the total hours for those multi-machine tasks before inputting them into the system, or perhaps creating a custom report that captures the accurate hours by summing them up outside of MP2. It might also be worth reaching out to the software support team to see if this is a known limitation or if they can suggest a patch or update that could better handle total hours for multitasks. If enough users express this concern, it might encourage them to prioritize a fix in future updates!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The report currently shows only a fraction of the actual time needed for multitask activities, leading to discrepancies in total hours displayed.
Answer: Answer: At present, there might not be a direct solution within MP2 to accurately depict total hours for multitask activities. You may need to explore workarounds or contact technical support for assistance.
Answer: Answer: The discrepancy in hours displayed can make it challenging to evenly distribute the workload across different shifts, affecting overall operational planning until the end of the year.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.