A build-to-order Dynamics 365 Business Central extension that defines shift patterns, crew calendars, holidays, and per-work-center exceptions so finite scheduling and capacity planning reflect real available hours. One-time license from $249.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order Dynamics 365 Business Central extension that defines shift patterns, crew calendars, holidays, and per-work-center exceptions so finite scheduling and capacity planning reflect real available hours.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Production Calendar & Shift Capacity Manager is a per-tenant AL extension that ECOSIRE builds, installs, and supports on your Dynamics 365 Business Central environment. It closes a real gap in core BC: standard Shop Calendars and Work Center Calendar entries assume tidy, repeating working days and offer no first-class model for rotating shifts, crew-specific calendars, plant shutdowns, or one-off exception days. Planners end up hand-editing Calendar Entries or padding routing times — and APS/MRP then schedules against capacity that doesn't exist.
Reusable shift-pattern library (fixed, rotating, multi-crew, weekend) assignable per Work Center or Machine Center
Crew calendars so different teams on the same work center carry different available hours
Per-work-center and plant-wide holiday calendars with documented override precedence (shutdown beats shift beats default)
One-off exception days for overtime, extra shifts, partial closures, and planned maintenance windows
Efficiency and availability factors that convert gross shift hours into realistic net capacity hours
Net capacity in hours written to native Calendar Entries via event subscribers on BC Calendar Management — feeds Order Scheduling, Capacity Planning, and APS add-ons
This extension adds a structured layer on top of the native Capacity ledger. You define reusable shift patterns (e.g., 06:00–14:00 / 14:00–22:00 / night, weekend crews, 4-on-4-off rotations) and assign them per Work Center or Machine Center. Holiday calendars and exception days are maintained per work center or shared across the plant, with override precedence so a plant shutdown beats a normal shift. Efficiency and availability factors (planned maintenance windows, ramp-up, absenteeism allowances) reduce gross shift hours to realistic net hours.
Under the hood it ships as table and page extensions plus event subscribers on Business Central's Calendar Management codeunit, so the Calendar Entries that feed Order Scheduling, Capacity Planning, and any APS add-on reflect your real available hours — no parallel scheduling engine, no data duplication. A visual calendar editor page lets planners see and adjust the resulting working calendar per work center. Standard BC permission sets, the OData/REST API for the calendar tables, and optional job-queue regeneration of forward calendars are all included. Because it's per-tenant, it coexists cleanly with your other extensions and AppSource apps and is upgraded with your BC release cadence.
Owns finite scheduling and capacity planning. Needs Calendar Entries to reflect actual shift coverage, crews, and shutdowns so promise dates and load profiles are trustworthy instead of padded guesses.
Responsible for the BC environment and its extensions. Wants a clean per-tenant AL app with proper permission sets and telemetry that upgrades with the release ring rather than ad-hoc customizations on the base tables.
Cares that scheduling reflects reality — overtime days, plant closures, maintenance windows — so capacity utilization reporting and delivery commitments hold up to scrutiny.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Production Calendar & Shift Capacity Manager 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Production Calendar & Shift Capacity Manager,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Rotating/multi-crew shift patterns assignable per work center | ||||
| Per-work-center and plant-wide holiday/exception handling with override precedence | ||||
| Efficiency/availability factors reducing gross to net capacity hours | ||||
| Writes to native Calendar Entries (no parallel scheduling engine) | ||||
| Built, installed, and supported on your tenant with version-compatibility maintenance | ||||
| Tailored to your exact shift/exception rules without writing the AL yourself | ||||
| OData/REST API exposure of shift and calendar tables for Power BI/Power Automate |
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.
A build-to-order Dynamics 365 Business Central extension that defines shift patterns, crew calendars, holidays, and per-work-center exceptions so finite scheduling and capacity planning reflect real available hours.