Build-to-order Odoo module to track tools, dies, molds & fixtures by shot-count life, maintenance & custody — prevent line stoppages. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.
アプリマニフェスト
あなたのワークフローに合わせて構築
Build-to-order Odoo module to track tools, dies, molds & fixtures by shot-count life, maintenance & custody — prevent line stoppages.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
Injection-molding, stamping, and die-casting shops live or die by their tooling. A worn cavity, a die that blew past its refurbishment interval, or a mold nobody can locate can halt a production line for a full shift — and standard Odoo has no concept of a "tool" that wears out shot by shot. This is a build-to-order module that ECOSIRE designs, builds, installs, and supports specifically for your plant; it is not an off-the-shelf apps.odoo.com download, and there is no instant-download link. After purchase we run a short discovery, then deliver a production-ready module for Odoo 17, 18, or 19 (Community or Enterprise) in 2–4 weeks.
At the core is a new ecosire.tooling.asset model (models.Model) that treats every tool, die, mold, and fixture as a first-class asset with its own registry record — owner, physical location, cavity/impression count, associated products, and life status. Life tracking is driven by real usage: a stored, computed remaining_shots field uses @api.depends on the rated shot life and the accumulated shot/cycle count so the number is always live and query-able. Usage can be posted manually, imported from your MES/press counters via XML-RPC or JSON-RPC, or rolled up from Manufacturing Orders when a tool is linked to a BoM operation. When a tool crosses its warning threshold, an Odoo automated action (server action on a scheduled ir.cron) raises an activity and emails the tool-room supervisor before the tool fails on the line.
Everything is built the Odoo-native way so it fits your existing database instead of bolting on beside it: proper models/ORM with related and computed fields, list/form/kanban/calendar views (XML, with OWL components where an interactive counter or dashboard adds value), row-level security via ir.model.access.csv plus record rules so tool-room staff, operators, and maintenance each see the right scope, and QWeb PDF reports for tool history cards, custody logs, and maintenance certificates. Maintenance and refurbishment tie into Odoo's Maintenance app so a shot-count trigger can auto-create a maintenance request, and check-in/check-out gives you a full custody chain of who has each mold and where it physically sits. The result: fewer surprise stoppages, tooling you can actually find, and a defensible service/refurbishment history for every die in the shop.
Owns the physical crib of molds, dies, and fixtures. Needs a live registry, custody tracking, and shot-life visibility so no tool goes to a press already past its rated life — and so customer-owned tooling is auditable.
Runs the presses and cannot afford surprise stoppages. Wants remaining-life alerts and tool-to-work-center linkage so scheduling accounts for refurbishment windows before a die fails mid-run.
Responsible for servicing and rebuilding tooling. Needs shot-count-triggered maintenance requests, a per-cavity service history, and certificates to prove work was done and life was reset.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Shot/cycle-count life tracking with remaining-life alerts | Built-in: stored computed remaining-life field + `ir.cron` threshold alerts | Possible but you design and maintain the model yourself | Rare; most generic asset apps track calendar dates, not shots | |
| Tool-to-product and tool-to-work-center linkage | Native links to product and work-center, usable in planning | Buildable with in-house dev time | 部分的なサポート | |
| Check-in/check-out custody chain | Full custody tracking with history via chatter | You build the workflow and audit trail | 部分的なサポート | |
| Fit to your exact tool-room roles (security) | Tailored `ir.model.access.csv` + record rules to your roles | Fully custom but on your team's clock | Fixed access model you must adapt to | |
| Odoo 17 / 18 / 19 + Community & Enterprise | Delivered for your exact version and edition | Depends on your team's version expertise | Often lags new versions; check listing per version | |
| Refurbishment history + QWeb audit reports | Per-cavity history + branded QWeb certificates/logs | Report templates built from scratch | 部分的なサポート | |
| MES/press-counter integration (XML-RPC / JSON-RPC) | Wired to your counters as part of delivery | You implement and maintain the integration | 含まれていない | |
| Ongoing support, fixes, and upgrade path | Support window + optional retainer from the builder | Falls on your internal team | Vendor-dependent; varies by publisher |
No — this is a build-to-order module, not an apps.odoo.com download, so there is no instant-download link. After purchase we run a short discovery on your tooling, roles, and shot-data sources, then build, install, and hand over a production-ready module in a typical lead time of 2–4 weeks depending on integration scope (MES/press-counter feeds and legacy-registry imports add time).
You receive the module source with your Odoo instance and a post-go-live support window for bug fixes and minor adjustments. Because the code lives in your database, you are not locked into a subscription to keep using it. We also offer an optional ongoing retainer for enhancements, new reports, and compatibility maintenance when you upgrade Odoo versions.
We build for Odoo 17, 18, or 19, on Community or Enterprise. The module ships with a clean `__manifest__.py` and version-aware views. Enterprise adds nicer studio-style dashboards and tighter Maintenance-app integration, but the core registry, shot-life tracking, and custody features work fully on Community.
Whichever fits your plant. If your presses or MES expose counts, we connect them to Odoo's XML-RPC or JSON-RPC API so shot counts post automatically. If a tool is linked to a work-center operation, counts can roll up from Manufacturing Orders. Manual entry (per shift or per run) is always available as a fallback or for smaller shops.
Yes. Each tool can be linked to its owning `res.partner`, flagged as customer-owned on reports, and restricted via record rules so consignment tooling is only visible to the right users. The module is multi-company and multi-plant aware, with per-location record rules so each site sees its own crib when you need that separation.
Odoo Maintenance treats equipment on a calendar/breakdown basis and has no concept of shot- or cycle-count life, cavity-level refurbishment history, or tool-to-product linkage. This module adds a purpose-built tooling asset with computed remaining life, threshold-driven automated actions, custody check-in/out, and QWeb tooling reports — then feeds triggers back into Maintenance where that app is the right home for the work order.
Build-to-order Odoo module to track tools, dies, molds & fixtures by shot-count life, maintenance & custody — prevent line stoppages.