Most maintenance teams end up running their equipment on a whiteboard, a spreadsheet, and a chat group — while the assets, purchase orders, and spare-parts stock they depend on already live in ERPNext. Stock-out Item shortages stall a repair, breakdowns get logged nowhere, and nobody can answer the two questions a plant manager actually cares about: how often does this machine fail, and how long does it take to get it running again. ERPNext ships an Asset DocType and a basic Asset Maintenance schedule, but it stops well short of a real CMMS — there is no meter-driven triggering, no spare-parts BOM per job, no technician mobile checklist, and no MTBF/MTTR analytics. That is exactly the gap this build fills.

ECOSIRE builds a proper Frappe app — a versioned preventive_maintenance module with its own DocTypes rather than a pile of customizations bolted onto core. The core objects are an Equipment (asset) registry with parent/child hierarchy and Meter Reading child tables, a Maintenance Plan that spawns jobs on either a calendar cadence or a usage threshold (e.g. every 500 operating hours), a Maintenance Work Order for both preventive and corrective/breakdown jobs, and a Spare Part Consumption table that links to standard ERPNext Item and Stock Entry so every part used is a real inventory movement. Scheduling is driven by Frappe scheduler_events (a nightly cron that reads meters and calendar due-dates and auto-creates the next work order), and business rules are enforced in hooks.py doc events — on_submit of a work order posts the material issue, validate blocks closing a job with an open safety checklist. Technicians work from mobile-friendly checklist client scripts and, where wanted, a whitelisted REST endpoint (@frappe.whitelist()) so field apps can submit readings and photos. Access is governed by ERPNext role profiles (Maintenance Manager, Technician, Store Keeper) with row-level permission rules, and the whole thing targets Frappe/ERPNext v15 and v16.

On top of the transactional layer we build the reporting that justifies the system: query reports and dashboard charts for MTBF, MTTR, planned-vs-unplanned ratio, schedule compliance, and spare-parts cost per asset, all reading from the same DocTypes so the numbers are always live. Because everything is native ERPNext, a breakdown that consumes three bearings shows up in stock valuation, a maintenance job can raise a Material Request when a part is below reorder level, and asset downtime is available to the same reporting stack your finance and production teams already use — no external CMMS to reconcile.

This is a build-to-order product, not an instant download. You request a quotation, we run a short scoping call to confirm your asset hierarchy, meter types, checklist content, and role model, and we hand back a fixed scope and timeline. Typical delivery is 2–4 weeks from confirmed scope. We develop against your v15/v16 target, validate on a staging bench, run UAT with your maintenance lead, then install to production with a rollback plan and hand over the git repository. You own the source for your version.