Licensing
Yearly or Perpetual. Always Per Module.
Both products are licensed on the term you choose, yearly or perpetual, and always per module, so you pay only for the modules you use. There is no lock-in, no tying-in, no bundled licensing agreement, and no subscription to a shared service. As your deployment grows, you add module licences, one at a time.
Licence term
Yearly or perpetual: you choose the term
The same product and the same modules are available on either term. The choice is about how you prefer to budget and how you take support and upgrades, not about what you get.
Renewed each year
Yearly licence
The product and each module you deploy are licensed for a year at a time and renewed each year. Suited to operating budgets and to deployments that expect to change shape as modules are added.
- Renewed yearly, per product and per module.
- Add or drop module licences at renewal as your needs change.
- Support and updates included: technical support and every product update released during the licensed year.
Version specific · One time
Perpetual licence
A one-time licence for a specific version of the product and of each module you deploy, with no renewal. Suited to capital budgets and to plants that standardize on a validated version.
- Paid once, for the version you deploy.
- No renewal; add module licences at any time on the same basis.
- Support: an annual support and maintenance agreement, renewed each year, covers technical support, fixes and minor updates within the licensed version.
- Upgrades: the licence is version specific, so a newer major version is licensed as an upgrade to that version rather than as a new licence, and your module licences carry over.
Per module
Pay only for the modules you use
Whichever term you choose, licensing is per module. You license the product and then only the modules you deploy on it, and you add a licence when you add a module. Nothing is pre-bundled, and no module depends on buying another.
- Product licence: the platform and the services every module shares: the plant model or data model, users and roles, workflows, electronic signature, integration and the native AI connector.
- Module licences on B2MES: the MES modules, such as Production Execution, Weighing and Dispensing, Performance, Quality, Energy, Maintenance and Asset Health.
- Module licences on B2MDL: the enterprise solutions and their modules: QMS, NPD, Supply Chain, EHS, Asset Management and any module added later.
- Grow in steps: start with one module and add licences as you add modules.
In practice
Licences follow the modules, step by step
Three ways an organization typically grows, and what is licensed at each step. Every path starts with a single module, on the term you choose.
One plant, one module
- B2MES product licence for the plant.
- One module licence, for example Production Execution.
- Add Performance or Quality later with one more module licence each.
Enterprise quality first
- B2MDL product licence for the enterprise deployment.
- QMS module licences for the QMS modules you deploy.
- Add EHS or Asset Management later, module by module.
Multi-plant, one record
- B2MES product licence per plant, with each plant's own modules.
- B2MDL product licence for the enterprise, consolidating every plant.
- Enterprise solution modules on B2MDL, only the ones you use.
What you will not find
No lock-in. No tying-in. No bundles. No shared-service subscription.
Four things are deliberately absent from the model, because each would make you pay for what you do not use or stay for reasons other than value.
- No lock-in. Your data stays in your database, on your infrastructure; a licence never holds it hostage.
- No tying-in. Licensing one module never obliges you to license, or keep, another.
- No bundled licensing agreements. Modules are never packaged so that taking one forces you to take others.
- No shared-service subscription. B2MDL is not offered as a shared or multi-tenant service; it is licensed and deployed for your enterprise on your infrastructure.
- A proposal, not a price list. Licences are proposed against the term you prefer and the modules you plan to deploy. Talk to an expert to receive one.