Hello, I'm seeking assistance with a peculiar issue that arose a few months ago. Our company utilizes the Access-based MP2 system. While reviewing machine histories recently, I noticed that certain monthly PM's were not being completed. Upon investigation, I discovered that the Work Orders were not being generated as scheduled. Despite examining the tasks, I could not pinpoint a reason for the non-generation. After attempting to recreate one of the tasks, running a "generate work orders" command resulted in the successful generation and printing of the WO. I have since repeated this process for four other tasks, suspecting there may be more affected. Could this be a sign of database corruption? Any insights on what might be causing this issue would be greatly appreciated. Thank you. Kim
Which method is being utilized for tasks that are not being generated - fixed, floating, or duplicates? When is the next due date? If the reorder method is fixed, have you confirmed that there are no open work orders (WOs) for that specific task?
The issue has occurred with both fixed and floating assets. Upon investigation, no existing open orders were found to be causing a hindrance to the generation of a new one. Some of these occurrences were unrelated to specific equipment, ruling out any potential conflicts related to "perform when down" settings or similar factors.
One common issue causing Work Orders not to be generated is the setting of either In Service (normal use) or Out of Service (extended shutdown). Another possible reason is when another Task is shadowing. If you are experiencing this problem, please reach out to Donal Fleming at flemingtechnical.com for assistance.
If your setup is accurate, the issue you are experiencing may be due to corrupted data in your database. When you mention that the tasks are not associated with equipment, it is important to clarify that there is equipment linked to the tasks, but it is using the -? It is crucial to note that a task schedule cannot be created without a piece of equipment.
I didn't know that every task needed to be linked to equipment in MP2. I wanted to create a "tickler file" in MP2 to remind me about tasks like energy inspections and report deadlines. Although I usually use Outlook for such reminders, I thought MP2 could serve the same purpose. Thank you for your assistance.
Hi Kim, it sounds like you've done quite a thorough job investigating the issue. Given that the work orders generate successfully when you manually recreate the tasks, it could be related to how the tasks were originally set up or perhaps an issue with the scheduling parameters in the system. Database corruption is always a concern, but it might be worth checking for any updates or patches for the MP2 system, as sometimes bugs can cause glitches like this. Also, consider looking into any logs or error reports that might give more context when the work orders fail to generate automatically. Good luck!
✅ 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: 1. What could be causing work orders not to generate as scheduled in the Access-based MP2 system? - The issue could potentially be related to database corruption or a glitch in the system's scheduling process.
Answer: - One troubleshooting step could involve attempting to recreate the tasks and running a "generate work orders" command to see if it resolves the issue for individual tasks.
Answer: - If tasks are not generating work orders as scheduled, and manual intervention is required to trigger the generation, it might be a sign of underlying database corruption that needs to be investigated further.
Answer: - It is advisable to investigate potential database corruption, review the system's scheduling settings, and monitor the generation process closely to identify any patterns or recurring issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.