Large-screen Andon dashboards and call-for-help signaling that surface line status, takt vs actual pace, and stoppage alerts directly from ERPNext. Build-to-order: ECOSIRE designs, builds, installs, and supports it against your Work Orders and Job Cards. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

Large-screen Andon dashboards and call-for-help signaling that surface line status, takt vs actual pace, and stoppage alerts directly from ERPNext. Build-to-order: ECOSIRE designs, builds, installs, and supports it against your Work Orders and Job Cards.
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
On most shop floors the real production status lives in someone's head, on a whiteboard, or three clicks deep inside a Work Order that nobody on the line can see. ERPNext Manufacturing tracks the transactional truth — Work Orders, Job Cards, operations, and Material Requests — but it has no full-screen Andon board, no physical call-for-help signaling, and no live takt-versus-actual pace indicator. When a machine stops or a line runs out of material, the clock keeps running while someone walks to find a supervisor. That reaction gap is exactly where lean visual management is supposed to win, and it is where ERPNext core runs out of road.
Full-screen Andon board as a Frappe web page/workspace, auto-refreshing per-line and per-cell status without manual reload
New DocTypes (`Andon Station`, `Andon Call`, `Andon Escalation Rule`) that model your floor without forking ERPNext core
Color-coded state engine — green running-to-takt, amber open call, red confirmed stoppage — driven by client-script logic
Andon call buttons for material, quality, and maintenance, each routed to the right responder role
Takt time computed from Work Order planned qty and shift calendar; actual pace read live from Job Card time logs and completed qty
Whitelisted REST endpoints (`@frappe.whitelist()`) so wall tablets and hardware buttons can raise, acknowledge, and resolve calls
We build a proper Frappe app — say ecosire_andon — that installs cleanly onto your existing ERPNext v15 or v16 bench without forking core. It ships new DocTypes such as Andon Station, Andon Call, and Andon Escalation Rule, plus a full-screen board rendered as a Frappe web page / workspace that reads live from your Work Order, Job Card, and Workstation records. Operators raise calls from a wall-mounted tablet or a hardware button (via a whitelisted REST endpoint), and the board recolors in real time — green for running to takt, amber for a raised call, red for a confirmed stoppage. Takt time is computed from the Work Order planned quantity and shift calendar; actual pace comes off Job Card time logs and completed-qty updates, so the board shows whether the cell is ahead or behind without anyone keying in a number.
Under the hood it is standard, upgrade-safe Frappe engineering. hooks.py doc events on Job Card and Stock Entry update station state on submit; server scripts and whitelisted methods (@frappe.whitelist()) expose the call, acknowledge, and resolve actions to the buttons and tablets; client scripts drive the auto-refresh and color logic on the board; and a scheduler event walks open Andon Call records every minute to fire escalation timers — routing a notification (email, ERPNext notification, or webhook to Slack/Teams/an SMS gateway) up the chain when a call is not acknowledged inside its SLA. Access is governed by ERPNext role profiles and permissions, so operators, line leads, and maintenance each see and act on only what their role allows, and every call, acknowledgement, and resolution is a queryable record for later Pareto and MTTR analysis rather than a lost event.
Because this is build-to-order, nothing is generic. We start from a short scoping call, map it to your line and cell layout, your stoppage reason codes, your escalation chain and shift patterns, then build against a copy of your data. You get the installable source for your version of the app, deployed and configured on your bench, with UAT on a staging site before anything touches production.
Delivery typically runs 2 to 4 weeks from confirmed scope — not an instant marketplace download, because we are building and validating this against your actual manufacturing setup. You receive the git repository, technical and user documentation, a training session for supervisors and operators, and a post-go-live support window so the boards are trusted and used from day one.
Runs daily visual management and wants line status, takt-vs-actual, and open calls on a wall screen instead of chasing updates. Needs the board to reflect real ERPNext Work Order and Job Card state so standup decisions are made on live data.
Owns throughput and downtime KPIs across multiple lines. Wants escalation SLAs enforced automatically and every stoppage captured as a record for Pareto, MTTR, and OEE follow-up rather than anecdotes.
Responds to Andon calls and needs the right alert to reach the right person fast, with escalation if a call goes unacknowledged. Wants a clean history of call type, response time, and resolution.
Maintains the bench and cares that anything added is upgrade-safe. Wants a proper app using DocTypes, hooks, and whitelisted methods — no core patches — and a git repo the team can maintain across v15/v16 upgrades.
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Andon & Real-Time Production Display Boards uygulamasının ZIP dosyasını indirin.
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Andon & Real-Time Production Display Boards yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Full-screen Andon board | Purpose-built live board, color-coded per line/cell | Possible but you design and build it from zero | Generic board, rarely matches your floor layout | |
| Takt vs actual pace | Auto-computed from Work Order plan and Job Card logs | Depends entirely on your in-house build | Often manual entry or a fixed target | |
| Call-for-help signaling | Material/quality/maintenance buttons via whitelisted REST | Build endpoints and UI yourself | Basic calls, limited routing | |
| Escalation timers | Per-minute scheduler with SLA-based routing | You implement and test scheduler logic | Fixed or absent escalation | |
| ERPNext fit | Native DocTypes, hooks, permissions — no core forks | Quality varies with your team's Frappe depth | May patch core or lag on version support | |
| Fit to your floor | Built to your lines, reason codes, and chain | Fully bespoke but slow and costly to reach | One-size-fits-all configuration | |
| Support and upgrades | Post-go-live window + v15/v16 upgrade support | Self-supported unless you staff it | Vendor-dependent, often generic | |
| Time to value | 2-4 weeks from confirmed scope, UAT on staging | Months of internal development | Fast install, slow to fit your process |
No. This is a build-to-order product. ECOSIRE designs, builds, installs, and supports it against your ERPNext setup — your line layout, reason codes, escalation chain, and shift patterns. There is no instant download; you receive the installable source for your version once it is built and validated.
Typically 2 to 4 weeks from confirmed scope. The timeline depends on the number of lines and cells, how many stoppage reason codes and escalation tiers you need, and any hardware-button or external-notification integrations. We confirm a firm timeline after the scoping call, then build against a copy of your data with UAT on staging before go-live.
Frappe/ERPNext v15 and v16. The app is packaged as a versioned Frappe app installable via `bench get-app` and is built to be upgrade-safe — it uses new DocTypes, `hooks.py` doc events, whitelisted methods, and scheduler events rather than patching core.
No manual entry. Takt time is derived from the Work Order planned quantity and the shift calendar, and actual pace is read live from Job Card time logs and completed-quantity updates via doc events. The board recolors automatically as operations are submitted in ERPNext.
Through whitelisted REST endpoints (`@frappe.whitelist()` methods). A wall-mounted tablet, browser, or a hardware button wired to a small controller posts to those endpoints to raise, acknowledge, or resolve an Andon call. A per-minute scheduler event handles escalation timers, so unacknowledged calls climb the chain automatically.
Every engagement includes a post-go-live support window for fixes and tuning once the boards are live. Because you receive the full git repository, your team can extend the app themselves, or you can retain ECOSIRE for ongoing changes, v15-to-v16 upgrade support, and new-line rollouts under a separate support arrangement.
Yes. Escalation routing is configurable per call type and tier — ERPNext in-app notifications, email, and outbound webhooks to Slack, Microsoft Teams, or an SMS gateway. We wire the specific channels and chain you use during the build.
Large-screen Andon dashboards and call-for-help signaling that surface line status, takt vs actual pace, and stoppage alerts directly from ERPNext. Build-to-order: ECOSIRE designs, builds, installs, and supports it against your Work Orders and Job Cards.