يتم عرض تفاصيل المنتج باللغة الإنجليزية. الترجمات قريبا.
حقائق سريعة
- السعر
- $249.00 USD
- إصدارات أودو
- —
- وقت الإعداد
- 30 دقيقة
- الترخيص
- مرة واحدة دائمًا
- اللغات
- 11 لغات
شراء لمرة واحدة
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.
$249.00USD
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
الميزات الرئيسية
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
عن هذا المنتج
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.
لماذا تختار Scrap, Yield & Cost-of-Quality Tracker
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
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.
ما تحصل عليه
- 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
لمن هذا
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.
نظرة عامة على التثبيت
تحميل من ECOSIRE
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة Scrap, Yield & Cost-of-Quality Tracker ZIP من لوحة تحكم حسابك.
تحميل إلى أودو
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتثبيت الوحدة
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن Scrap, Yield & Cost-of-Quality Tracker، ثم اضغط على تثبيت.
تكوين الإعدادات
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
التحقق والبدء في البث المباشر
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
كيف يقارن Scrap, Yield & Cost-of-Quality Tracker.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| First-pass and rolled-throughput yield per operation | متضمنة | دعم جزئي | دعم جزئي | |
| Cost-of-quality split into internal vs. external failure, valued from real costs | متضمنة | دعم جزئي | دعم جزئي | |
| Mandatory reason codes with Pareto and trend analysis | متضمنة | دعم جزئي | دعم جزئي | |
| Automatic capture via event subscribers on posting (no re-keying) | متضمنة | دعم جزئي | متضمنة | |
| Scoped to your routings, costing method and reason taxonomy | متضمنة | متضمنة | غير متضمنة | |
| Installed and supported on your tenant by the builder | متضمنة | دعم جزئي | دعم جزئي | |
| OData/REST API + Power BI / Dataverse integration | متضمنة | دعم جزئي | دعم جزئي | |
| Upgrade-safe per-tenant extension, no base-app modification | متضمنة | دعم جزئي | متضمنة |
الأسئلة المتداولة حول 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 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.
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.
الوحدات ذات الصلة
طلب عرض سعر
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