Amendment in Existing Software for Breakdown History Sheet and Management of Preventive Maintenance -- 2
Budget: ₹12,500 – ₹37,500 INR
I already run an in-house application that handles basic equipment data; now I need it to go further. The goal is to bolt three tightly-connected capabilities onto the existing codebase without disturbing what’s working today.
• Breakdown history tracking – every incident should be logged with date, asset, root cause and corrective action, then surfaced through a searchable, filterable screen as well as exportable reports.
• Preventive maintenance scheduling – the system must let me define recurring tasks by time, runtime hours or any other meter we already capture, generate the schedule automatically and show upcoming work in a calendar view.
• Automated alerts and notifications – email—or, if simpler, in-app pop-ups—should warn us of overdue jobs, imminent PMs and repeated breakdown patterns.
The current database schema and UI are available, and I will share a sample data set plus screenshots so you can see how things fit together. If integrations with an ERP, CMMS or live sensor feeds streamline any of the above, I’m open to your recommendations, but they aren’t mandatory for this phase.
Please keep the existing look-and-feel consistent, comment your code clearly and provide a concise change log so my internal team can maintain it afterwards.
• Breakdown history tracking – every incident should be logged with date, asset, root cause and corrective action, then surfaced through a searchable, filterable screen as well as exportable reports.
• Preventive maintenance scheduling – the system must let me define recurring tasks by time, runtime hours or any other meter we already capture, generate the schedule automatically and show upcoming work in a calendar view.
• Automated alerts and notifications – email—or, if simpler, in-app pop-ups—should warn us of overdue jobs, imminent PMs and repeated breakdown patterns.
The current database schema and UI are available, and I will share a sample data set plus screenshots so you can see how things fit together. If integrations with an ERP, CMMS or live sensor feeds streamline any of the above, I’m open to your recommendations, but they aren’t mandatory for this phase.
Please keep the existing look-and-feel consistent, comment your code clearly and provide a concise change log so my internal team can maintain it afterwards.