A per-tenant Business Central extension that captures scrap, rework and yield by operation and reason code, computes first-pass and rolled-throughput yield, and quantifies cost-of-quality so plants can target the biggest loss drivers. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A per-tenant Business Central extension that captures scrap, rework and yield by operation and reason code, computes first-pass and rolled-throughput yield, and quantifies cost-of-quality so plants can target the biggest loss drivers. Built, installed and supported by ECOSIRE.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
Scrap, Yield & Cost-of-Quality Tracker is a custom Microsoft Dynamics 365 Business Central extension that turns shop-floor scrap and rework into financial intelligence your continuous-improvement team can act on.
Business Central core captures scrap quantity on production journals and an output-vs-expected variance, but it has no first-pass yield, no rolled-throughput yield, no structured reason coding, and no cost-of-quality model. Quality engineers end up rebuilding all of that in spreadsheets. This extension closes that gap natively.
We build it in AL as a per-tenant extension (or an AppSource-style package for ISV distribution if you prefer), deployed straight onto your environment — never a copy-paste of your base app. Table and page extensions add reason codes and scrap/rework capture to your existing Production Order, Routing, and Output Journal pages. Event subscribers on output and consumption posting record yield and loss the moment work is reported, so nobody re-keys data. Calculated cost-of-quality (internal vs. external failure) flows from your real item costs and routing rates — not estimates.
A Reason-Code Pareto and trend pages surface the few drivers behind most of your loss, and a Yield-Loss Financial Impact view ranks operations and products by dollars lost, not just piece counts. Data is exposed via the OData/REST API for Power BI and Dataverse, with a dedicated permission set and optional Job Queue entries for scheduled COQ roll-ups.
Because it is build-to-order, ECOSIRE scopes it to your routings, costing method and reason taxonomy, installs it on your tenant, and supports it after go-live. Honest lead time applies — this is configured and delivered by engineers, not an instant download.
Owns scrap-reduction targets and needs FPY, RTY and a reason-code Pareto in Business Central instead of weekly spreadsheets, so they can prove which operations and defects to attack first.
Wants scrap and rework translated into dollars and trended over time, to defend capital requests and hold work centers accountable for cost-of-quality, not just unit counts.
Needs internal and external failure costs valued from the same item costs and routing rates used in the GL, so cost-of-quality reconciles to the production cost variances they already report.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| First-pass and rolled-throughput yield per operation | Incluído | Suporte parcial | Suporte parcial | |
| Cost-of-quality split into internal vs. external failure, valued from real costs | Incluído | Suporte parcial | Suporte parcial | |
| Mandatory reason codes with Pareto and trend analysis | Incluído | Suporte parcial | Suporte parcial | |
| Automatic capture via event subscribers on posting (no re-keying) | Incluído | Suporte parcial | Incluído | |
| Scoped to your routings, costing method and reason taxonomy | Incluído | Incluído | Não incluído | |
| Installed and supported on your tenant by the builder | Incluído | Suporte parcial | Suporte parcial | |
| OData/REST API + Power BI / Dataverse integration | Incluído | Suporte parcial | Suporte parcial | |
| Upgrade-safe per-tenant extension, no base-app modification | Incluído | Suporte parcial | Incluído |
This is build-to-order, not an instant AppSource download. After a short scoping call to confirm your routings, costing method and reason-code taxonomy, typical delivery is about 2 to 4 weeks depending on complexity. ECOSIRE builds the extension in AL, installs it first on your Business Central sandbox for sign-off, then publishes it to your production environment as a per-tenant extension. You receive the .app, documentation and a connected sample Power BI report.
ECOSIRE supports the extension after installation. Because it is built in AL as a versioned extension that depends only on documented Business Central objects and events, Microsoft's monthly and major (wave) updates do not overwrite it. We retest and recompile the extension against new Business Central versions and ship a patched .app if any object signature changes. Support, defect fixes and small enhancements are handled under an agreed arrangement; larger feature additions are scoped separately.
No. Everything ships as table extensions, page extensions and event subscribers in a separate extension package. We never modify Microsoft's base objects or your other ISV apps. The extension can be uninstalled cleanly, and all capture happens through supported posting events, so your existing manufacturing and costing logic continues to behave exactly as before.
Internal failure cost (scrap and rework) is valued from the same item cost and routing/work-center rates Business Central uses for production costing, captured at the operation where the loss occurs. External failure cost (returns, warranty) is captured from linked sales returns. Each figure drills down to the originating production order, operation and ledger entry, so finance can reconcile cost-of-quality to existing cost variances rather than treating it as a separate estimate.
Yes. Scrap, yield and COQ records are exposed through Business Central's OData v4 / REST API with a dedicated permission set. We deliver a sample Power BI report connected to your tenant, and the same endpoints can drive a Dataverse virtual table or Power Automate flows for alerts when FPY drops below target on a given operation.
A per-tenant Business Central extension that captures scrap, rework and yield by operation and reason code, computes first-pass and rolled-throughput yield, and quantifies cost-of-quality so plants can target the biggest loss drivers. Built, installed and supported by ECOSIRE.