In injection molding, stamping and die-casting shops, the most expensive production assets are often invisible to ERPNext. A hardened steel mold or progressive die represents tens of thousands of dollars and a finite life measured in shots or cycles, yet stock ERPNext has no native concept of "this tool is rated for 1,000,000 shots and has 40,000 left." Teams end up tracking tool life in spreadsheets that nobody reconciles against actual production, so a cavity cracks mid-run, a fixture wears out of tolerance, or a preventive refurbishment is missed and a customer order stalls. ERPNext's Asset and Maintenance doctypes cover depreciation and calendar-based schedules, but they do not count shots, tie usage to the Work Order that produced it, or fire a "replace this insert now" alert at a threshold.

ECOSIRE builds a proper Frappe app — its own module, not a pile of customizations — that adds a Tool Asset registry DocType for every mold, die, jig and fixture, each with make/cavity/serial identification, a lifetime limit, and running counters for shots and cycles. A Tool Usage Log DocType records consumption, and a hooks.py on_submit doc event on ERPNext's Job Card / Work Order increments the counter for the assigned tool by the produced quantity, so usage accrues automatically from real production rather than manual entry. A scheduler event (scheduler_events in hooks.py, running daily) evaluates every active tool against its life limit and a configurable warning band, raising life-limit-approaching and replacement-due alerts as ToDos, email notifications, or dashboard indicators. When a tool needs attention, a Tool Maintenance DocType spawns refurbishment and repair work — servicing, re-polishing, insert replacement — with parts consumed against ERPNext stock and cost captured back onto the asset.

Technically it stays inside ERPNext conventions so your team and any future developer can maintain it. Tools link to Workstation and to the Item they produce, giving you both a tool-to-workstation and a tool-to-item view; role profiles and DocType permissions gate who can adjust a lifetime limit versus who can only log usage. Selected server-side actions are exposed as @frappe.whitelist() methods and over the standard Frappe REST API, so a shop-floor tablet, an MES, or a press PLC can post shot counts programmatically. Client scripts add on-form validation and quick-actions (reset counter after refurbishment, flag out-of-tolerance), and all reporting is built with native Query/Script Reports and dashboard charts — remaining life, tools due this month, cost per shot — rather than an external BI bolt-on. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is a shrink-wrapped download. We start with a short scoping call to map your tool categories, how you measure life (shots, cycles, hours, strokes), and how usage should flow from your existing Work Order or Job Card process. We then build against a documented scope, deliver to a staging site for UAT, and go live with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope depending on integration complexity. You receive the full source code and git repository for your version, so you are never locked to us.