Question 1

What exactly is Bodhee?

Accepted Answer

Bodhee is the Adaptive Scheduling product family for process manufacturing. Three coordinated schedulers — Bodhee Production Scheduling, Bodhee Quality Control Scheduling, and Bodhee Maintenance Scheduling — work against a live Process Digital Twin (PDT) of your plant. Where a traditional plan is set weekly and re-worked manually, Bodhee re-plans continuously as orders, materials, assets, quality results, and labour change in the real world.

Question 2

What problem does Bodhee solve in plain English?

Accepted Answer

Plans that survive contact with reality. In most process plants, the schedule the planner builds on Monday is broken by Tuesday — a delayed material, a quality hold, an unplanned breakdown, a rush order. Today, planners and supervisors absorb the disruption with phone calls, whiteboards, and overtime. Bodhee replaces that firefighting with a schedule that re-adapts in minutes against the same constraints a human would apply, and shows the planner why.

Question 3

Where does Bodhee live in our stack — between MES and ERP?

Accepted Answer

Yes. Bodhee orchestrates above MES and below planning. It consumes orders and master data from ERP (typically SAP S/4HANA or ECC, Oracle, or any other ERP), live execution events from MES and historian, quality results from LIMS, and asset events from CMMS. It then pushes back a feasible, optimised, re-adapting schedule that MES executes and ERP confirms.

Question 4

What is "Adaptive Scheduling" and how is it different from APS?

Accepted Answer

APS (Advanced Planning & Scheduling) is built to optimise a plan once — typically weekly — against a snapshot of demand and capacity. Adaptive Scheduling is built to re-plan continuously against the live state of the plant. APS answers "what is the best plan for next week?"; Adaptive Scheduling answers "given everything that has changed in the last hour, what is the best plan for the next 24 hours, and which orders are now at risk?"

Question 5

What is the Process Digital Twin?

Accepted Answer

The Process Digital Twin (PDT) is the live representation of your plant that Bodhee reasons against — products, recipes, asset, materials, labour, quality holds, and the constraints that connect them. It is not a 3D model; it is a decision model. Every Bodhee recommendation traces back to a specific state of the PDT, which means every recommendation is explainable.

Question 6

What does it schedule — the lab, the samples, or both?

Accepted Answer

Both, plus the production batches awaiting release. Bodhee Quality Control Scheduling plans sample arrival, test execution, analyst allocation, instrument capacity, and release sequencing for batches blocked by pending results. It treats the lab as a constrained shop floor — because that is what it is.

Question 7

How does it reduce release cycle time?

Accepted Answer

By pulling three levers at once:

• Priority sequencing — release-blocking and deadline-critical samples are sequenced first.
• Equipment-level optimisation — the sample mix on each instrument is optimised against sample arrival times, required-by dates, and instrument capacity.
• Lab–production coordination — the lab schedule is aligned with the production release plan, so finished batches are not waiting on tests that could have run earlier.

The scheduler knows which finished batches are blocked, by which test, on which instrument, and by which analyst — and sequences accordingly. The visible outcomes are shorter lab turnaround time and fewer batches waiting on release.

Question 8

Does it integrate with our LIMS?

Accepted Answer

Yes — with major LIMS vendors including LabWare, STARLIMS, and LabVantage. Bodhee Quality Control Scheduling reads sample registration and test status from the LIMS. Custom LIMS deployments are supported through the standard integration adapter. Writing the test schedule back from Bodhee into LIMS is technically feasible, but the recommended approach is to use Bodhee's data exports / API connectivity to integrate into LIMS outside the Bodhee environment.

Question 9

How does it handle stability / regulatory testing?

Accepted Answer

As constrained queues alongside release testing, with their own priority and pull-date logic. The scheduler respects pull-date windows for stability protocols and ensures regulated tests are not starved by higher-volume release tests.

Question 10

Can it handle micro / chem / physical labs separately?

Accepted Answer

Yes. Each discipline is modelled as a distinct resource pool with its own instruments, analysts, certifications, and SOPs. A single deployment can manage a microbiology lab, a chemistry lab, and a physical-testing lab on different floors or sites under one schedule.

Question 11

Does it reduce sample backlog?

Accepted Answer

Customer outcomes show consistent reductions in sample backlog and lab turnaround time. Named results are published in the [case-study library](/case-studies/). Reference customers are made available after qualification stage.

Question 12

Does it help with analyst workload balancing?

Accepted Answer

Yes. The scheduler schedules around analyst skill, certification, shift, and current workload. Senior analysts are not over-allocated to routine work, and certifications are honoured automatically. Using the Bodhee side-task functionality, the lab can keep a buffer of pre-planned work (for example, a daily 9 AM status call or ad-hoc training for an analyst) ready to slot into analyst downtime without needing a new approval or re-prioritisation.

Question 13

Does Bodhee replace our APS?

Accepted Answer

No. APS systems plan at weekly / monthly cadence against forecast and capacity assumptions. Bodhee adapts at daily / shift cadence against live plant state. They are complementary: APS sets the boundary conditions and the production targets; Bodhee adapts the schedule inside those boundaries as the plant runs.

Question 14

Cloud-native, on-prem, or both?

Accepted Answer

Bodhee is a SaaS product, deployed on Google Cloud Platform (GCP) and operated by Neewee. Customers do not host, install, or operate the product themselves. Bodhee is not offered for installation on customer-managed infrastructure or inside a customer's own cloud account.

The SaaS model is deliberate: continuous releases, managed security operations, observability, and incident response all stay inside one team that understands the product end-to-end — which is materially safer and faster than a fleet of customer-managed installs. Data residency is configurable across GCP regions (see [Q 9.3](#q-9-3)), each customer runs in a single-tenant data plane, and customer-managed encryption keys are available for customers who require key isolation (see [cluster 11](#cluster-11) for the full security and compliance posture).

Question 15

Does Bodhee integrate with SAP (S/4HANA, ECC, PP, PM, QM)?

Accepted Answer

Yes — through productised connectors for the most common SAP scenarios (S/4HANA, ECC, PP, PM, QM, MM) and a custom integration path for non-standard configurations. SAP integrations follow a documented data-flow pattern (orders + master data in; schedule + confirmations out). We capture process orders, material master, inventory data, factory and holiday calendars, BOMs, goods receipts (for QC scheduling against raw materials), recipes (where available), equipment and resource master data, and shift-level crew data. Data connectivity uses REST, SOAP, Pub/Sub, or file import / export.

Question 16

Which LIMS?

Accepted Answer

Bodhee Quality Control Scheduling is LIMS-vendor-agnostic by design. Data exchange uses the integration pattern the customer's LIMS already supports — REST, SOAP, file import / export, or direct database read — through Bodhee-managed connectors. The scheduler reads sample registration and test status from the LIMS (and ERP for raw-material goods receipts).

Question 17

What certifications does Bodhee hold?

Accepted Answer

Bodhee is operated under an information-security programme aligned to ISO 27001. Customers under NDA can request the latest ISO 27001 certificate.

Question 18

How long does a typical Bodhee deployment take?

Accepted Answer

First measurable value usually lands in weeks; full module rollout typically lands in months. Exact timeline depends on data readiness, integration scope, and the number of sites in scope. A typical pattern is pilot in 12 weeks, full single-site rollout in 20 weeks, multi-site expansion thereafter.

Question 19

How is Bodhee priced?

Accepted Answer

Pricing combines a per-site, per-module licence with a usage component sized to plant scope (assets, lines, lab benches, work-order volume). The exact model is shaped to the customer's deployment topology — we walk through it in detail during evaluation.

Question 20

What ROI should we expect?

Accepted Answer

Outcome bands depend on the module, the starting state of the operation, and the scope of deployment. Typical published outcomes range from low-double-digit improvements in adherence or throughput at well-run sites, to step-change improvements (30 %+) at sites where manual scheduling has been the bottleneck. The honest answer for any specific customer comes out of a baseline assessment during evaluation.

A lemaradástólaz áttörésig.

A labor az a szűk keresztmetszet, amellyel senki sem számol.

A QC-ütemezés négy konkrét ponton hibás.

Táblázatalapú, eseményvak

Az analitikusi és műszerképesség nincs modellezve

A módszerek várakozási idejét puha célnak veszik

Elszakadva a felettes termeléstől

Építse újra a labortervet a nulláról, minden ciklusban.

Constraint-aware.

Natívan integrált.

Újraépítve, nem foltozva.

Mit csinál a Bodhee QC Scheduling.

Laboresemények és LIMS-integráció

Analitikusi és műszer-törzsadatok

Natív mintatípusok

Újraépítés a nulláról

Termelési események integrációja

Mit hoz a Bodhee QC Scheduling.

Bemenetek → Motor → Kimenetek.

Négy szerepkör a QC-laborban, mindegyiknek megvan a maga oka.

QC-analitikus / vezető

Minőségbiztosítási vezető

QA és szabályozói megfelelés

Digitális és IT-vezetők

Három fázis az élő laborterv felé.

Felmérés

Konfigurálás

Élesítés

Három ok, amiért ez nem egy LIMS-modul.

Natív integráció a felettes termeléssel.

Minden ciklusban a nulláról épül újra.

Szabályozott laborokra készült. Nem köti egyetlen LIMS sem.

Kérdések, amelyeket a QC-csapatoktól hallunk.

Mi pontosan a Bodhee?

Milyen problémát old meg a Bodhee, közérthetően?

Hol helyezkedik el a Bodhee a rendszereink között, a MES és az ERP között?

Mi az „Adaptive Scheduling”, és miben tér el az APS-től?

Mi az a digitális folyamatiker?

Mit ütemez: a labort, a mintákat, vagy mindkettőt?

Hogyan csökkenti a felszabadítási ciklusidőt?

Integrálódik a LIMS-ünkkel?

Hogyan kezeli a stabilitási és szabályozói vizsgálatokat?

Tudja külön kezelni a mikrobiológiai, a kémiai és a fizikai labort?

Csökkenti a mintalemaradást?

Segít az analitikusi terhelés kiegyenlítésében?

Leváltja a Bodhee az APS-ünket?

Felhőnatív, helyben telepített, vagy mindkettő?Hosszú válasz

Integrálódik a Bodhee az SAP-pal (S/4HANA, ECC, PP, PM, QM)?Hosszú válasz

Mely LIMS-rendszerek?

Milyen tanúsítványokkal rendelkezik a Bodhee?Hosszú válasz

Mennyi ideig tart egy jellemző Bodhee-bevezetés?Hosszú válasz

Hogyan árazzák a Bodhee-t?Hosszú válasz

Milyen megtérülésre számíthatunk?Hosszú válasz

Gyorsabb felszabadítás. A tudomány rövidítése nélkül.

A lemaradástól
az áttörésig.