A build-to-order MES layer for Dynamics 365 Business Central: operator touch terminals, real-time production order start/stop and consumption, machine and labor time capture, a drag-and-drop scheduling board, and live OEE and scrap tracking — built, installed and supported by ECOSIRE as a per-tenant AL extension on your own BC environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $599.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order MES layer for Dynamics 365 Business Central: operator touch terminals, real-time production order start/stop and consumption, machine and labor time capture, a drag-and-drop scheduling board, and live OEE and scrap tracking — built, installed and supported by ECOSIRE as a per-tenant AL extension on your own BC environment.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
You go live in about 2–4 weeks, with a post-launch support window.
Business Central ships solid manufacturing master data — production orders, routings, work and machine centers, output and consumption journals — but the shop floor still runs on paper travelers, end-of-shift batch entry, and a planner staring at a spreadsheet. This app closes that gap.
ECOSIRE builds a Manufacturing Execution System (MES) layer directly on your Business Central tenant as a per-tenant AL extension (not a generic AppSource download). Operators work from a kiosk-style touch terminal — a custom AL page optimized for tablets — where they scan or select a released production order, hit start/stop on operations, post component consumption, and record machine and labor time. Every action writes through native BC objects (Capacity Ledger Entries, Item Ledger Entries, Prod. Order Routing) via table and page extensions plus event subscribers, so your costing, inventory, and WIP stay correct with zero double entry.
Planners get a visual scheduling board that reads work/machine center load and lets you drag operations across resources and time. OEE is computed live from the same captured data — availability, performance and quality — with scrap and downtime reason codes feeding dashboards you can surface in BC or push to Power BI through the BC OData/REST API and Dataverse.
Because it's build-to-order, we scope the workflow to your plant — discrete or process, barcode or manual, single or multi-site — install it into sandbox first, validate against your real orders, then promote to production. You own the tenant; ECOSIRE owns the build, the permission sets, the job queue jobs, and the ongoing support. Honest lead times and a real human behind every update.
Owns plant throughput and on-time delivery. Wants real-time visibility into what each order and machine is doing right now, live OEE, and scrap trends — instead of reconstructing the day from paper travelers the next morning.
Sequences released orders across work and machine centers. Needs a drag-and-drop board showing true load so they can rebalance around breakdowns and rush jobs without overloading a resource or breaking BC's capacity ledger.
Runs the machines and reports the work. Needs a fast, low-friction touch terminal to start/stop operations, post consumption, scan lots and log scrap — without learning the full Business Central client.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Real-time shop-floor capture (no end-of-shift batch entry) | Included | Partial support | Included | |
| Touch-terminal operator UI tailored to your plant | Included | Partial support | Partial support | |
| Drag-and-drop visual scheduling board on live capacity | Included | Partial support | Partial support | |
| Live OEE / scrap / downtime tracking | Included | Partial support | Included | |
| Posts through native BC ledgers (costing/WIP intact) | Included | Partial support | Partial support | |
| Built, installed & supported on your tenant by the vendor | Included | Not included | Not included | |
| Workflow scoped to your exact process (discrete or process) | Included | Included | Not included | |
| Source code handover (no lock-in) | Included | Included | Not included | |
| Upgrade-safe (extension model, survives BC updates) | Included | Partial support | Included |
This is build-to-order, not an instant AppSource download. After a short scoping call we typically deliver in 3 to 6 weeks depending on plant complexity (number of work centers, barcode vs. manual capture, process vs. discrete, multi-site). We build the AL extension, install it into your Business Central sandbox first, validate it against your real production orders and routings, then promote the signed .app to your production tenant during an agreed window. You keep full ownership of the tenant throughout.
ECOSIRE supports the extension after go-live. Because it's built on table/page extensions and event subscribers rather than modifying base objects, it survives Microsoft's monthly service updates and major version upgrades cleanly. When Microsoft ships a new BC major release, we recompile and re-test the extension against the new runtime in your sandbox before it reaches production. Bug fixes during the support window are included; new features or scope changes are quoted separately. You also receive the source so you're never locked in.
No. Every shop-floor action posts through native BC manufacturing objects — Prod. Order Routing, Capacity Ledger Entries, the Consumption and Output Journals, Item Ledger Entries. The terminal is a faster front end for the same postings your accountants already trust, so standard/actual costing, WIP and inventory remain the single source of truth. We never write directly around the ledger.
Both. We scope the capture workflow to your plant during build-to-order. Discrete shops get order/operation start-stop and component scanning; process shops can capture batch consumption, yield and scrap against the same production order and routing structures. The OEE and scheduling board logic adapts to either model.
Yes. OEE, scrap, downtime and throughput are exposed through the Business Central OData/REST API and can flow into Dataverse, so you can build Power BI dashboards or trigger Power Automate flows (for example, alert a supervisor when a line's availability drops). We can deliver a starter Power BI dataset as part of the engagement if you want it.
A build-to-order MES layer for Dynamics 365 Business Central: operator touch terminals, real-time production order start/stop and consumption, machine and labor time capture, a drag-and-drop scheduling board, and live OEE and scrap tracking — built, installed and supported by ECOSIRE as a per-tenant AL extension on your own BC environment.