Pre-designed executive and supervisor dashboards for ERPNext that put OEE, throughput, scrap, on-time delivery and WIP into one cockpit. ECOSIRE builds, installs and supports it after we confirm your scope. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

Pre-designed executive and supervisor dashboards for ERPNext that put OEE, throughput, scrap, on-time delivery and WIP into one cockpit. ECOSIRE builds, installs and supports it after we confirm your scope.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Plant directors running ERPNext have the raw data — Work Orders, Job Cards, Stock Entries, Delivery Notes and Quality Inspections all sit in the database — but no single screen that turns it into decisions. ERPNext ships a generic Dashboard, Number Cards and Dashboard Charts, but out of the box there is no OEE calculation, no scrap-rate trend, no WIP aging, and no shift-versus-shift comparison. Executives end up exporting to spreadsheets every Monday, and by the time a bad trend is visible the batch has already shipped. This is where ERPNext native runs out of road: OEE (availability × performance × quality) is not a stored field, schedule adherence has to be derived from planned versus actual Work Order dates, and rework cost lives across Stock Entry and Job Card records that no standard report joins.
Plant-level executive cockpit showing OEE (availability × performance × quality) computed server-side from Work Order and Job Card data, not a manual chart
OEE broken into its three components per work center so supervisors can see whether losses are availability, performance or quality driven
Throughput dashboards (produced quantity vs planned) sourced from submitted Work Orders and Stock Entries over selectable date ranges
Scrap and rework cost trends joining Job Card scrap, Stock Entry material consumption and Quality Inspection rejects into one costed view
First-pass yield and quality-rate trend lines derived from Quality Inspection pass/fail records
On-time delivery and schedule-adherence metrics comparing Work Order planned vs actual start/end and Delivery Note dates against Sales Order commitments
ECOSIRE builds a proper Frappe app — a versioned module installed on your bench, not a pile of manual chart configs — that ships the cockpit as code. We add lightweight computed DocTypes (for example a Manufacturing KPI Snapshot) populated by scheduler_events (hourly and daily hooks in hooks.py) plus on_submit/on_cancel doc events on Work Order, Job Card and Stock Entry, so OEE, throughput, scrap quantity, first-pass yield and WIP value are calculated server-side and stored, not recomputed live on every page load. On top of that data layer we assemble Frappe Dashboard Charts, Number Cards and a purpose-built cockpit workspace: a plant-level executive view and drill-down supervisor views for work centers, shifts and operators. Heavy aggregations are exposed through @frappe.whitelist() server methods and the standard Frappe REST API, so the same KPIs can feed a wall-mounted TV, a mobile view, or an external BI tool. Client Scripts add the interactive filters (date range, work center, item group) and role-aware defaults.
Access is governed by ERPNext permissions and Role Profiles — a Plant Director sees company-wide rollups while a Shift Supervisor is scoped to their work centers — with all logic driven by roles and permission queries rather than hard-coded user checks. Everything targets ERPNext / Frappe v15 and v16, follows Frappe app conventions (fixtures for the dashboards and number cards so they install cleanly), and is delivered as a git repository you own.
Because this is build-to-order, nothing is a black-box download. We start with a short scoping call to confirm which KPIs matter to your plant, your shift model, and how OEE should be defined for your equipment. You approve a written scope, we build against a staging copy of your ERPNext, you sign off during UAT, and then we install on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and every deployment includes a training session, documentation, a post-go-live support window, and full handover of the source repository.
Wants one screen every morning showing OEE, throughput, scrap and on-time delivery across the plant, with the ability to drill from a red number into the responsible work center or shift — without waiting for a Monday spreadsheet.
Needs a scoped view of their work centers and shift: which Work Orders are aging, where scrap is spiking, and how their operators compare, so they can intervene during the shift rather than after it.
Owns the ERPNext instance and wants the cockpit delivered as a clean, versioned Frappe app with fixtures, documented calculations and a git repo — not a fragile pile of manually configured charts that break on the next migration.
Tracks first-pass yield, scrap and rework cost trends over time to target improvement projects and measure their impact, using data pulled straight from Quality Inspection and Job Card records.
Compre la licencia en ecosire.com y descargue la aplicación ZIP de Manufacturing Dashboards & KPI Cockpit desde el panel de su cuenta.
Extraiga el ZIP en la carpeta de aplicaciones de su banco o ejecute `bench get-app` con la ruta a la aplicación extraída.
Ejecute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench migrar` para instalar Manufacturing Dashboards & KPI Cockpit y aplicar su esquema.
Abra la configuración de licencia de ECOSIRE en su sitio y active su clave de licencia. Requiere las aplicaciones gratuitas ecosire_connect y ecosire_license_client.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| OEE calculation | Availability × performance × quality computed server-side and stored, tuned to your equipment | Possible but you specify and build the whole formula yourself | Often a fixed OEE definition you cannot change | |
| Data freshness | Scheduler events + doc events keep stored KPIs incrementally fresh | Whatever refresh logic you write and maintain | Usually recomputed live, can be slow at scale | |
| WIP & work-order aging | Aging buckets and WIP value dashboards out of the box for your build | Build the joins and buckets yourself | Rarely included; focus is usually OEE only | |
| Fit to your plant | Scoped on a call — your shifts, KPIs and definitions | Fully yours, but from a blank sheet | Generic; you adapt to its assumptions | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, UAT on staging | Months of in-house dev and QA | Instant install but generic fit | |
| Access control | Role-Profile scoping (director vs supervisor) configured for you | You implement permission queries | Basic role gating, often coarse | |
| Ownership | Full git repository handover — you own and extend it | You own it entirely | Vendor-controlled, closed or licensed | |
| Support | Post-go-live support window + training + docs | Your own team supports it | Vendor support tiers, variable responsiveness |
No. It is build-to-order. ECOSIRE builds, installs and supports the cockpit for your specific plant after we confirm scope on a short call. There is no instant Frappe Cloud Marketplace download — we assemble the Frappe app, tune the KPI calculations to how your equipment and shifts actually run, and hand over the source.
Typically 2–4 weeks from confirmed scope. The timeline starts once you approve the written scope from the scoping call — which KPIs, how OEE is defined for your equipment, and your shift model. Larger plants with unusual data or many work centers sit at the upper end of that range.
We compute OEE as availability × performance × quality, server-side, from your Work Order and Job Card time logs, planned vs actual run data, and Quality Inspection results. The exact definition (what counts as planned time, ideal cycle time, and a quality reject) is agreed with you during scoping and documented, then stored in a computed KPI snapshot DocType refreshed by scheduler events.
Yes. We target Frappe/ERPNext v15 and v16 and follow standard app conventions — DocTypes, hooks.py doc events, scheduler_events and fixtures for the dashboards and number cards — so it installs deterministically and migrates cleanly. We build and test against a staging copy of your instance before touching production.
Every deployment includes a post-go-live support window for defect fixes and tuning of KPI definitions. Because you receive the full git repository, your own team can also extend the app. Longer-term maintenance, new KPIs, or version upgrades can be arranged as a separate engagement.
Yes. Each KPI is exposed through whitelisted server methods and the standard Frappe REST API, so the same stored aggregates can drive a shop-floor wallboard, a mobile view, or an external tool like Power BI, without hammering ERPNext with live recomputation.
No — access is governed by ERPNext permissions and Role Profiles. A Plant Director sees company-wide rollups; a Shift Supervisor is scoped to their work centers via permission queries. We configure the role-aware defaults and filters as part of the build.
Pre-designed executive and supervisor dashboards for ERPNext that put OEE, throughput, scrap, on-time delivery and WIP into one cockpit. ECOSIRE builds, installs and supports it after we confirm your scope.