Passer au contenu principal
Les détails du produit sont affichés en anglais. Traductions à venir.
Scrap, Yield & Cost-of-Quality Tracker — A per-tenant Business Central extension that captures scrap, rework and yield by ope — 1/1Aperçu illustratif

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.

Qu'est-ce que Scrap, Yield & Cost-of-Quality Tracker ?

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 $999.00 USD; request a quote for a scoped proposal.

Fonctionnalités clés

Scrap and rework capture by operation and routing line, with mandatory reason codes, added via AL table and page extensions to the Output Journal and Production Order
First-pass yield (FPY) per operation calculated from good vs. total output at each routing step
Rolled-throughput yield (RTY) across the full routing, multiplying operation FPYs to expose hidden compounded loss
Cost-of-quality reporting split into internal failure (scrap, rework) and external failure (returns, warranty), valued from real item cost and routing rates
Reason-code Pareto analysis ranking the few causes behind most scrap and rework loss
Trend analysis of scrap, rework and yield over time by item, work center and shift
Yield-loss financial impact view ranking operations and products by dollars lost, not piece counts
Event subscribers on output/consumption posting so yield and loss are recorded automatically with no double entry
OData v4 / REST API endpoints exposing scrap, yield and COQ entries for Power BI, Dataverse and Power Platform
Dedicated permission set for quality engineers, plus optional Job Queue entries for scheduled COQ roll-ups
Configurable reason-code taxonomy mapped to your defect catalogue and ISO/IATF requirements
Drill-down from any COQ figure to the underlying production order, operation and ledger entry

Fait sur commande, clé en main

Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.

  1. 1

    Vous commandez

    Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.

  2. 2

    Nous développons et installons

    ECOSIRE la développe, la configure et l'installe sur votre Dynamics 365 Business Central.

  3. 3

    Mise en ligne + assistance

    Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.

À propos de ce produit

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.

Ce que vous obtenez

  • Per-tenant Business Central extension (.app) built in AL, installed on your sandbox then production environment
  • Table and page extensions wiring scrap/rework and reason codes into Output Journal, Production Order and Routing pages
  • Event-subscriber logic that records yield and cost-of-quality automatically on output and consumption posting
  • FPY, RTY and cost-of-quality report pages plus the Reason-Code Pareto and Yield-Loss Financial Impact views
  • OData/REST API endpoints and a sample Power BI report connected to your tenant for live COQ dashboards
  • Dedicated permission set, Job Queue setup, configuration of your reason-code taxonomy, and admin/user documentation

Pour qui c'est

Continuous-Improvement / Quality Engineer

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.

Plant / Operations Manager

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.

Finance / Cost Controller

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.

Comment Scrap, Yield & Cost-of-Quality Tracker se compare

CritèreÉCOSIREConstruction personnaliséeConcurrentNatif Dynamics 365 Business Central
First-pass and rolled-throughput yield per operationInclusPrise en charge partiellePrise en charge partielleNon inclus
Cost-of-quality split into internal vs. external failure, valued from real costsInclusPrise en charge partiellePrise en charge partielleNon inclus
Mandatory reason codes with Pareto and trend analysisInclusPrise en charge partiellePrise en charge partielleNon inclus
Automatic capture via event subscribers on posting (no re-keying)InclusPrise en charge partielleInclusPrise en charge partielle
Scoped to your routings, costing method and reason taxonomyInclusInclusNon inclusNon inclus
Installed and supported on your tenant by the builderInclusPrise en charge partiellePrise en charge partielleNon inclus
OData/REST API + Power BI / Dataverse integrationInclusPrise en charge partiellePrise en charge partiellePrise en charge partielle
Upgrade-safe per-tenant extension, no base-app modificationInclusPrise en charge partielleInclusInclus

Foire aux questions sur Scrap, Yield & Cost-of-Quality Tracker

How long does delivery take, and how is it installed?

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 one working week 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.

What does ongoing support and updates look like after go-live?

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.

Does this change or risk my base Business Central application?

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.

How is cost-of-quality actually calculated?

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.

Can the data feed Power BI, Dataverse or the Power Platform?

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.

Demander un devis

Scrap, Yield & Cost-of-Quality Tracker

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.

  • Scrap and rework capture by operation and routing line, with mandatory reason codes, added via AL table and page extensions to the Output Journal and Production Order
  • First-pass yield (FPY) per operation calculated from good vs. total output at each routing step
  • Rolled-throughput yield (RTY) across the full routing, multiplying operation FPYs to expose hidden compounded loss
  • Cost-of-quality reporting split into internal failure (scrap, rework) and external failure (returns, warranty), valued from real item cost and routing rates

Demander un devis

Décrivez vos besoins pour Scrap, Yield & Cost-of-Quality Tracker et nous vous enverrons les tarifs, les options de licence et une proposition sur mesure, généralement sous un jour ouvré.

Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.