Product ยท Manufacturing Execution System

B2MES. The Plant Runs On It.

B2MES is the on-premises platform that runs our MES at the plant. It is installed on an edge server so production keeps running whatever happens to the wider network, it gives every MES module the same plant model, users, workflows and integrations, and it syncs natively to B2MDL, the Manufacturing Data Lake, so the enterprise sees every plant in one place.

Why on premises

Production cannot wait for a network.

A line confirms an operation, weighs a batch, prints a label and records a downtime reason many times a minute. Those transactions cannot depend on a link to a distant server. B2MES runs on an edge server at the plant so the MES is always there, at line speed, and the plant keeps its record even when the wider network is not available. For regulated plants it also keeps electronic records, signatures and the validated system under the site's own control.

When the link is up, B2MES syncs to B2MDL. When it is not, the plant keeps running and the sync catches up. The enterprise record is complete either way.

  • Line speedConfirmations, weighing, labelling and alarms happen at the workstation.
    Served from the edgeNo round trip to a remote server for every transaction.
  • Network outageThe plant cannot stop because the link did.
    Plant keeps its recordProduction continues locally; the sync to B2MDL catches up.
  • Machines and devicesPLCs, scales, printers and readers live on the plant network.
    OT integration on siteConnected where they are, with the data captured at the point of work.
  • Regulated recordsBatch records, e-signatures and audit trails are inspected at the site.
    Under the plant's controlRecords stay on a server the site owns, retention and residency follow site policy, and the validated system changes only when the plant schedules an upgrade.

Platform services

What every MES module gets from the platform

The modules differ; the foundations do not. Each one runs on the same plant model, the same users and roles, the same workflow engine and the same integrations, which is why a plant can start with one module and add the next without re-implementation.

Plant model

Sites, areas, lines, machines and equipment in one hierarchy that every module, and B2MDL, works from.

Users, roles and access

Role-based permissions down to the plant entity, with sign-in through the plant's directory.

Workflows and approvals

Configurable, role-based workflows for approvals, checklists and tasks, shared by every module.

Electronic signature and audit trail

Signed approvals and a who-did-what history for regulated records.

Alarms and notifications

Alarms from machines and processes raised, acknowledged and shelved against the asset, with notifications to the right people.

Labelling and printing

Batch, pallet and product labels designed once and printed from production data on the plant's printers.

OT and device integration

Machines, PLCs, scales, readers and other devices connected on the plant network, with values captured at the point of work.

ERP and enterprise integration

Orders, materials, confirmations and inventory movements exchanged with ERP and other enterprise systems.

Native sync to B2MDL

Production, performance, quality, energy and asset data pushed to the Manufacturing Data Lake for enterprise reporting; enterprise data brought back to the plant.

Standalone native AI connector

B2MES carries its own native AI connector, independent of B2MDL. The AI platform you choose connects to plant data directly at the plant, to detect, predict and optimize on what the line measures, and you decide what is exposed.

Native mobile app with device management

A native mobile app for operators, supervisors and technicians at the point of work, with device management so plant devices are enrolled, controlled and kept current.

Information security by design

Built to comply with information security standards. Your enterprise-level information security standards are met, for better governance of the plant platform.

What runs on it

The MES modules

B2MES hosts the MES solution and its modules.

Deploy only what your business needs. Every MES module runs on its own. Based on your business needs, a single module can be deployed without deploying everything, and each module you add later works with the ones already in place, with no re-implementation.
  • Production Execution: work orders, operator workflows, consumption and output.
  • Weighing and Dispensing: material preparation, with weighed and dispensed quantities recorded against the batch.
  • Performance: utilization, downtime reasons and shift performance.
  • Quality (shop floor): in-process checks, line clearance, deviations and batch release, to specifications released by QMS on B2MDL.
  • Energy: readings per line, machine and batch, with cost and carbon views.
  • Maintenance and Asset Health: condition monitoring and alarms, feeding Asset Management on B2MDL.
  • Inventory, Traceability, Labelling, Reporting: the supporting modules described on the MES page.
  1. Machines and devicesConnected on the plant network
  2. B2MESEdge server at the plant: MES modules and platform services
  3. B2MDLManufacturing Data Lake: every plant consolidated, enterprise solutions, AI
  4. ERP and enterprise systemsOrders in, confirmations and movements out

Licensing

Yearly or perpetual, and always per module

B2MES is licensed on the term you choose, yearly or perpetual (version specific, one time), and the MES modules you deploy on it are licensed individually. You pay only for the modules you use and add licences as you add modules. There is no lock-in, no tying-in and no bundled licensing agreement.

  • Yearly or perpetual: renewed each year with support and updates included, or a one-time licence for a specific version with an annual support agreement and per-version upgrades.
  • Per module: the B2MES product licence plus one licence per module you deploy, added when you add the module.
  • No lock-in, tying-in or bundles: you are never asked to buy, or keep, modules you do not use.
  • Talk to an expert for a licence proposal matched to the modules you plan to deploy, or read how licensing works.