Correct — this is build-to-order. After a short scoping call to confirm your work/machine centers, routings, shift calendars and OEE definitions, typical delivery is about one working week. We build and validate in a sandbox first, then install the per-tenant extension on production with you. Lead time depends on how many resources and how much downtime-reason structure you need; we confirm dates in writing before starting.

ECOSIRE supports the extension on your tenant: bug fixes, adjustments to OEE formulas or reason codes as your processes change, and compatibility updates for Business Central's twice-yearly major releases (so it keeps installing cleanly when Microsoft updates your environment). We can run a support retainer or handle changes per request — your choice. You also receive the full AL source code, so you are never locked in.

Yes. It is delivered as a per-tenant extension and works on Business Central Online and on supported on-premises versions. On Online we install it directly to your environment; on-prem we deploy the .app and coordinate with your IT team. We confirm your exact version during scoping to ensure object ranges and APIs match.

No. The extension reads your existing output, consumption and capacity data and adds its own tables and fields via extension objects and event subscribers. It does not modify base application code or overwrite standard tables, which is exactly how Microsoft expects extensions to behave — so your manufacturing posting and reporting stay intact and upgrade-safe.

Yes. We expose the OEE and downtime metrics through a custom OData/REST API page, so Power BI can pull live data on a schedule and Power Apps/Power Automate can read it without CSV exports. If you want, we deliver a starter Power BI report against that API as part of the engagement.