A build-to-order ERPNext application that turns your molds, dies, jigs and fixtures into tracked assets with shot-count and cycle-count usage, life-limit alerts, and maintenance work orders. ECOSIRE scopes, builds, installs and supports it for your Frappe/ERPNext v15/v16 site. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext application that turns your molds, dies, jigs and fixtures into tracked assets with shot-count and cycle-count usage, life-limit alerts, and maintenance work orders. ECOSIRE scopes, builds, installs and supports it for your Frappe/ERPNext v15/v16 site.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
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.
`Tool Asset` DocType registry for molds, dies, jigs and fixtures with make, serial, cavity count, material and location fields
Shot-count and cycle-count counters maintained per tool, with configurable unit of life (shots, cycles, strokes, machine-hours)
Automatic usage accrual via a `hooks.py` `on_submit` doc event on Work Order / Job Card that increments the assigned tool by produced quantity
`Tool Usage Log` DocType giving a full auditable history of every increment, adjustment and reset
Life-limit and warning-band configuration per tool with a daily `scheduler_events` job that evaluates remaining life
Replacement-due and life-approaching alerts raised as ToDos, email notifications and dashboard indicators
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.
Owns the tool crib in an injection molding or stamping shop and is accountable for tool life. Needs a single registry with accurate remaining-life counters and early replacement-due alerts so a cavity never fails mid-run.
Runs the presses and schedules jobs. Needs usage to accrue automatically from Work Orders and to know which tools are approaching end-of-life before committing a customer order to a given press.
Executes refurbishment, re-polishing and insert replacement. Needs maintenance work tied to the specific tool, parts consumed against stock, and counters reset correctly after a rebuild.
Owns the ERPNext deployment and wants the capability inside the existing system with clean DocTypes, permissions and REST access — not another disconnected spreadsheet or standalone tool-management product.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der Tooling, Mold & Fixture Lifecycle Management-App von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um Tooling, Mold & Fixture Lifecycle Management zu installieren und sein Schema anzuwenden.
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Shot/cycle life tracking | Purpose-built counters with per-tool life limits and units | Possible but you design the whole life model yourself | Often generic asset counters, not molding-specific | |
| Automatic usage from production | Work Order / Job Card `on_submit` doc event increments counters | You must build and maintain the hook logic | Usually manual entry or CSV import | |
| Replacement-due alerts | Daily scheduler evaluates thresholds, raises ToDos and emails | Build your own scheduler and alerting | Basic calendar reminders, rarely usage-based | |
| Refurbishment workflow | `Tool Maintenance` DocType with parts consumed and counter reset | Bespoke build, timeline and cost uncertain | Varies; often no counter-reset semantics | |
| Integration (REST / API) | Whitelisted methods + Frappe REST for tablets, MES, PLCs | You design and secure every endpoint | Limited or closed integration surface | |
| Fit to your process | Scoped to your tool categories and life units before build | Fully bespoke but higher cost and longer timeline | Fixed feature set, adapt your process to it | |
| Code ownership | Full source + git repository handover for your version | You own it, but you fund all of it | Typically licensed, source not handed over | |
| Total cost & timeline | Fixed scope, 2–4 weeks, built and supported by ECOSIRE | Highest cost, longest and least predictable | Low upfront but limited fit and lock-in |
No. It is build-to-order. ECOSIRE scopes, builds, installs and supports a version tailored to how your shop measures tool life and how usage flows from your Work Orders. You get the full source and git repository for your version, but there is no instant marketplace download.
Typically 2–4 weeks from confirmed scope, depending on integration complexity (for example, whether we also wire shot counts from press PLCs or an MES). We agree the scope on a short call first, then build against it, deliver to staging for UAT, and go live with a rollback plan.
Usage accrues automatically. A `hooks.py` doc event on the ERPNext Work Order / Job Card `on_submit` increments the assigned tool's counter by the produced quantity. You can also post counts directly from a shop-floor tablet, MES or press controller through a `@frappe.whitelist()` method or the Frappe REST API, and log manual adjustments when needed.
We build for Frappe/ERPNext v15 and v16, packaged as a standard installable Frappe app. If you are on an older version we will confirm feasibility and any upgrade prerequisites during scoping.
Every engagement includes a post-go-live support window for bug fixes and adjustments. Beyond that we offer ongoing support and enhancement retainers. Because you receive the full git repository, your own team or any Frappe developer can also maintain and extend the app.
Yes. It complements them rather than replacing them. ERPNext Asset still handles acquisition value and depreciation; this app adds the shot/cycle life model, threshold alerts and tool-to-workstation/tool-to-item linkage that core ERPNext does not provide, and it can reference your existing Asset records.
Through native Frappe role profiles and DocType permissions. Typically shop-floor roles can log usage and raise maintenance requests, while only tooling managers or admins can change lifetime limits or edit the tool master. We tailor the permission matrix to your roles during the build.
A build-to-order ERPNext application that turns your molds, dies, jigs and fixtures into tracked assets with shot-count and cycle-count usage, life-limit alerts, and maintenance work orders. ECOSIRE scopes, builds, installs and supports it for your Frappe/ERPNext v15/v16 site.