This is a build-to-order extension, not an instant AppSource download. After a short scoping call to confirm your work centers, shift patterns, and exception rules, typical delivery is about 2–4 weeks: we build the AL extension against your BC version, install and validate it in your sandbox, then schedule the production install during a maintenance window. Complex rotating-crew rules or many work centers can extend the timeline, and we confirm the exact lead time in writing before you commit.

No. ECOSIRE builds it and installs it as a per-tenant extension directly on your Business Central environment. There is no public AppSource listing to click-install. This keeps the app tailored to your shift and calendar rules while still being a proper signed AL extension that coexists with your other apps and upgrades with your release cadence.

Each engagement includes a support window for bug fixes and configuration help. Critically, because BC ships major updates twice a year, we provide version-compatibility maintenance: we recompile and re-validate the extension against new BC releases so it keeps working through upgrades. Support and update terms (duration, response targets) are set out in your order; renewal or a maintenance retainer is available afterward.

No. It writes net available hours into Business Central's native Calendar Entries through event subscribers on the standard Calendar Management codeunit. Order Scheduling, Capacity Planning, and any APS add-on continue to read the same native data — there's no parallel engine and no duplicated capacity ledger. If you ever uninstall, BC reverts to its standard calendar behavior.

Yes. The shift-pattern, holiday, and computed-calendar tables are exposed via Business Central's OData v4 / REST API, so Power BI, Power Automate, and external systems can read available capacity. We document the endpoints and entity fields as part of delivery, and can extend the API surface to specific fields you need during the build.