Bodhee is the product family for process manufacturing. Three coordinated schedulers — Bodhee Production Scheduling, Bodhee Quality Control Scheduling, and Bodhee Maintenance Scheduling — work against a live () 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.
Bodhee Maintenance Scheduling
Uptime
by Design.
Bodhee Maintenance Scheduling sits on top of your existing CMMS and clusters downtime windows — then coordinates with production and quality in real time. Fewer shutdowns. Higher first-time-right. Same CMMS of record.
Complements SAP PM, IBM Maximo, and Infor EAM. No rip-and-replace.
Industry context
Maintenance is 20–30% of controllable cost — scheduled by hand.
20–30%
Of total operating cost in asset-intensive industries
ARC Advisory Group
30–50%
Of planned PMs deferred into compliance risk
Typical CMMS audit
2–3×
Downtime windows created vs. what's strictly needed
Un-clustered scheduling
<40%
First-time-right execution rate on complex shutdowns
Industry directional
Figures are directional industry benchmarks — not Neewee customer outcomes.
The problem
CMMS is a system of record — not a scheduler.
SAP PM, Maximo, Infor EAM are excellent at what they were built for. Scheduling isn't it.
01
PMs scheduled by calendar, not by opportunity
A monthly PM hits whether or not a natural window just opened. The schedule ignores the plant state.
02
Task duration is a single number
CMMS stores “4 hours.” The reality is shutdown + LOTO + task + qualification + restart — each with its own dependency.
03
Windows aren't clustered
Three PMs on adjacent equipment get scheduled in three separate windows. Each with its own shutdown overhead.
04
Compliance deferrals invisible
A deferred PM becomes a red flag in next month's audit — the scheduler never sees the cascading compliance exposure.
05
Disconnected from production & QC
Campaign transitions that could absorb a PM go unused. OOS investigations that open an equipment window go unexploited because maintenance planning updates too slowly.
Meet Bodhee Maintenance Scheduling
A scheduling layer on top of your CMMS — not a replacement.
Sits on top of your CMMS.
Bodhee reads work orders from SAP PM, IBM Maximo, or Infor EAM and writes scheduled start-times back. The CMMS remains the system of record.
Clusters windows.
Periodic work orders are clustered into the fewest possible downtime windows — cutting shutdown and LOTO overhead in half or better.
True-duration modelling.
Each task is modelled as shutdown → LOTO → task → qualification → restart — with the dependency graph that actually governs execution.
The five pillars
What Bodhee Maintenance Scheduling does.
Pillar 01
CMMS Integration
Read work orders. Write scheduled times.
- SAP PM, Maximo, Infor EAM connectors
- Bi-directional sync
- CMMS remains system of record
Pillar 02
True-Duration Modelling
Maintenance as it actually happens.
- Shutdown + LOTO + task + qualification + restart
- Dependency graph per work order
- Crew skill & tool requirements
Pillar 03
Window Clustering
Fewer shutdowns. Higher yield.
- Adjacent-equipment co-scheduling
- Shared-utility opportunity detection
- Campaign-transition window capture
Pillar 04
Compliance-Aware Prioritisation
Regulatory risk, scheduled first.
- Regulatory PM due-dates honoured
- Deferral cascade visualisation
- Audit-ready exception trail
Pillar 05 · Lead differentiator
Cross-Functional Coordination
Real-time with production & quality.
- Captures opened windows from Production events
- QC OOS investigations → maintenance opportunity
- Bodhee Production absorbs downstream impact
Measurable outcomes
What Bodhee Maintenance Scheduling delivers.
Ranges observed across asset-intensive deployments. Outcomes vary by CMMS maturity and asset complexity.
0–50%
Downtime windows created
through tighter clustering of related work
0–20 pp
First-time-right execution
with true-duration tasks and dependencies modelled upfront
0–25%
PM compliance rate
by protecting maintenance windows before they drift
Hours → Minutes
Window re-plan cycle
when campaigns shift or urgent work lands mid-week
−15–25%maintenance labour overhead
Based on Neewee deployment observations in process manufacturing.
How it works
Inputs → Engine → Outputs.
Bodhee connects into your existing stack, runs the optimisation, and publishes schedules and events back out.
Inputs · 7
Source systems feeding the engine.
- SAP PM / Maximo / Infor EAM
- HRMS Crew skills
- Spare-parts inventory
- SCADA / Historian health
- Compliance calendar
- Bodhee Production events
- Bodhee QC events
Engine · 5
Five internal capabilities.
- Task decomposition & dependency graph
- Window-clustering optimisation
- Crew & tool matching
- Compliance-weighted prioritisation
- Event-driven rescheduling
Outputs · 5
What Bodhee publishes back.
- Scheduled start-times → CMMS
- Clustered downtime windows
- Crew rosters & work packs
- Compliance dashboard
- Events → Bodhee Production / QC
Who it's for
Four roles. Four reasons.
Primary user
Maintenance Planner / Scheduler
“I need to cluster PMs into real windows and stop chasing campaign transitions by phone.”
Work-order scheduling effort drops. Windows cluster automatically. Campaign transitions are captured.
Economic buyer
Maintenance Manager / Reliability Lead
“My compliance report and my uptime report should be the same report. Today they aren't.”
PM compliance rises 15–25%. Unplanned downtime falls. One view instead of two.
Operational
Maintenance Crew & Contractors
“Give me an accurate work pack — with the right spare parts on site and a window that won't move at the last minute.”
First-time-right execution rises 10–20 pp. Crew utilisation improves. Fewer late-change callouts.
Technical buyer
Digital / IT Leaders
“We're not replacing SAP PM. We need a scheduling layer that reads and writes — not another system of record.”
Deployed on top of existing CMMS. Bi-directional sync. Weeks to deploy, not years.
Customer journey
Three phases to scheduled maintenance.
1
Assess
CMMS maturity review. Asset hierarchy and criticality map. Compliance calendar inventory.
2
Configure
Task decomposition, crew skill matrix, spare-parts linkage, bi-directional CMMS integration, Bodhee Production & QC event feeds.
3
Go Live
Parallel run by asset class. Calibrate. Expand scope area-by-area. Ongoing tuning with the reliability team.
How Bodhee Maintenance Scheduling is different
Three reasons this isn't a CMMS upgrade.
01
Scheduling layer, not system of record.
SAP PM, Maximo, and Infor EAM stay exactly where they are. Bodhee adds the optimisation layer they were never designed to provide.
02
Captures production and QC windows in real time.
Campaign transitions and OOS investigations open unplanned maintenance opportunities. Bodhee is the only scheduler that sees them — because it shares the Digital Twin.
03
True-duration modelling out of the box.
Shutdown, LOTO, task, qualification, restart — with the dependency graph. Not a single number for task duration.
Frequently asked questions
Questions we hear from maintenance teams.
A focused subset of the full Bodhee FAQ — answers for the questions maintenance heads, reliability engineers, and planners ask before a pilot.
01
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.
Yes. Bodhee orchestrates above and below planning. It consumes orders and master data from (typically SAP S/4HANA or ECC, Oracle, or any other ERP), live execution events from MES and historian, quality results from , and asset events from . It then pushes back a feasible, optimised, re-adapting schedule that MES executes and ERP confirms.
02
(Advanced Planning & Scheduling) is built to optimise a plan once — typically weekly — against a snapshot of demand and capacity. 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?"
03
The () 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.
06
All three. Bodhee Maintenance Scheduling plans the work-order backlog, technician and crew capacity, planned shutdowns, and opportunistic maintenance windows that open up when production is paused or running below capacity. The output is a maintenance plan that fits the actual production calendar instead of fighting it.
The maintenance scheduler reads the production schedule directly from Bodhee Production Scheduling — or from your existing scheduler if Bodhee Production Scheduling is not yet deployed — and finds the least-cost maintenance windows. When the two run together, the system co-plans production and maintenance jointly, which routinely surfaces "free" maintenance opportunities the manual process misses.
No. Bodhee Maintenance Scheduling is a scheduling product; it does not provide condition-based or predictive maintenance models and features.
Yes — bidirectionally with SAP PM, IBM Maximo, Infor EAM, and eMaint. Bodhee Maintenance Scheduling reads work-order data, asset hierarchies, and technician availability from the , and writes scheduled execution windows and completion confirmations back.
As a hard constraint. The scheduler will not schedule a work order without confirmed parts availability, and it surfaces parts-driven schedule delays explicitly so procurement can act. Spare-parts availability is read as a flag from the . When parts arrive, opportunistic re-plan brings the work order forward.
07
No. 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.
09
Bodhee is a product, deployed on Google Cloud Platform () 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), 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 for the full security and compliance posture).
10
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.
Bodhee Maintenance Scheduling is -vendor-agnostic by design. Data exchange uses the integration pattern the customer's CMMS already supports — REST, SOAP, file import / export, or direct database read — through Bodhee-managed connectors. The scheduler reads work-order data, asset hierarchies, and technician availability, and writes scheduled execution windows and completion confirmations back.
11
Bodhee is operated under an information-security programme aligned to . Customers under can request the latest ISO 27001 certificate.
12
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.
14
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.
15
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.
More uptime. Same CMMS.
A 30-minute tour of Bodhee Maintenance Scheduling — window clustering, cross-functional coordination, and how it fits your CMMS.