Turn Business Central into a full EAM / CMMS.
Thirty-three modules covering the entire Enterprise Asset Management surface — asset register, work orders, scheduling, condition monitoring, predictive maintenance, reliability, calibration, safety, warranty, fleet, energy and a Claude-powered assistant. Module Registry switches features on or off per company. No Azure IoT dependency.
- 33 modules · one Module Registry · per-company toggles
- Claude routing: Haiku / Sonnet / Opus per task
- Azure-IoT-free: REST / webhook / file ingestion
- Predictive maintenance with reasoning · never auto-creates
- 8 role-based permission sets + role centres
- Mobile & field execution on the standard BC client
Built on infrastructure your maintenance team already trusts
Asset-heavy businesses on Business Central deserve a real CMMS — not a spreadsheet.
Most BC customers managing physical assets fall back to Excel for maintenance because the AppSource alternatives are either too narrow, too expensive, or too dependent on a separate IoT stack. We built the deepest EAM/CMMS extension in the BC ecosystem — 33 modules, native AL, designed for asset-heavy verticals, with Anthropic Claude doing the work that humans should not have to.
Full EAM/CMMS surface under one Module Registry. Activate the modules your business needs; the rest stay invisible.
Work-request triage, predictive maintenance, NL assistant, reliability reasoning, document extraction — routed across Haiku, Sonnet and Opus.
Telemetry via REST, webhook, file or manual entry. Plays with Azure IoT if you have it; doesn't require it.
Six verticals where SPM earns its keep on day one.
We did not build a generic CMMS and then call it vertical-specific. The Module Registry makes vertical-specific configurations a checkbox, not a code branch.
Manufacturing
Production-line equipment, utility infrastructure, captive workshops. Tight integration with Production Orders to plan downtime around scheduled runs.
Fleet & Logistics
Vehicle fleets, telematics-driven service intervals, tyre/battery rotation, fuel/hour-based PMs. Module M22 ships fleet-specific UI.
Facilities & Real Estate
Multi-site portfolios with hierarchical functional locations, HVAC + electrical + plumbing strategies, lease/contract integration.
Utilities & Energy
Distributed asset registers, condition monitoring, SCADA integration via REST, regulatory audit trail through Module M33.
Mining, Quarries, Heavy Civil
Mobile + fixed plant, rotable component tracking, safety/permit-to-work enforcement, contractor & visitor management.
Process industries
Calibration management with ISO traceability, batch-context maintenance, FMEA/RCM for safety-critical assets, energy & sustainability tracking.
Grouped by what they do, not the order they were built.
Each module registers in the central Module Registry. Activate per company; deactivate the rest. Inactive modules hide their UI and skip their background jobs entirely — no clutter, no idle cost.
Foundation
Setup Wizard · Module Registry · AI Gateway · Health Check · Asset Register · Functional Locations · BOM / Spare-Parts · Module Activation
Plan & schedule
Maintenance Strategies · Job Plans / Task Lists · Scheduling & Planning Board · Labour & Crews · Meters / Counters · Requests / Notifications
Execute
Work Orders · Spares · Procurement & Subcontracting · Rotable / Repairable Spares · Tools & PPE · Mobile & Field Execution
Monitor & predict
Condition Monitoring · Predictive Maintenance (Claude) · Reliability / FMEA · Calibration · Energy & Sustainability
Compliance & cost
Safety / Permit-to-Work · Warranty · Contracts / SLA · Fleet · Costing & Finance · Audit / Security · Contractor & Visitor
AI & integration
AI Maintenance Assistant (Claude) · Documents & Knowledge · Notifications / Workflow · Reporting / Dashboards / KPIs · Integration & API Framework
Five concrete AI features. Routed by task class.
All five go through one central AI Gateway codeunit — model routing, prompt construction, retry, token budgets and audit logging in one place. ZDR header on every call.
Work-request triage
Claude classifies incoming requests, predicts the likely asset, proposes priority and craft. Planner accepts or overrides; either way the audit trail captures who confirmed what.
Predictive maintenance
Pattern analysis over meter readings, vibration trends and historical failures. Generates preventive work order suggestions with explicit reasoning — never auto-creates.
Maintenance assistant
Natural-language Q&A inside BC. Ask 'what's pending on pump P-1042 next week' or 'how many overdue PMs in plant B' and get answers with the underlying records linked.
Reliability / FMEA reasoning
Multi-asset reliability and failure-mode analysis. Aggregates failure history across similar assets, proposes RCM recommendations with rationale. Opus tier for depth.
Auditor-grade by construction.
EAM data goes to regulators (calibration certificates, safety permits, energy reports). The architecture assumes someone will eventually trace every line.
AI fails closed
Token budget per company per month. Over-budget calls return a friendly message; no surprise spend. Master AI toggle short-circuits every codeunit when disabled.
ZDR on every Claude call
Anthropic `anthropic-no-data-retention: true` header on every prompt. Anthropic retains nothing for training or logging. Visible in Setup; on by default.
Keys in Isolated Storage
Claude API key lives in BC Isolated Storage (Company scope), encrypted at rest, scoped to module. Set via Setup action; value never echoed back to UI or logs.
AI Log per invocation
Every Claude call is logged to SPM AI Log with task class, model, latency, tokens, ZDR flag and the user who confirmed any resulting action. Auditor-ready.
8 role-based permission sets
Read · Admin · Planner · Technician · Storekeeper · Fleet · Reliability · Safety. Each role lands on a focused BC role centre so users see only what they need.
Azure-IoT-free ingestion
Condition monitoring via REST, webhook, file or manual entry. Optional Azure IoT integration if you have it — but never required, so the product works without an existing IoT investment.
Activate what you need. Pay for what you use.
You almost certainly don't need all 33 modules on day one. Module Registry makes that the default position:
- Each module registers its name, version, dependencies and default permission set with the central registry on install.
- Per-company activation — a single company can run a 6-module deployment while another runs all 33.
- Inactive modules hide their UI from menus, role centres and search; their background jobs skip; their tables stay empty.
- Reactivate any module later without re-deploying the extension. No migration ceremony, no schema upgrade.
M02 Asset Register [✓] M03 Functional Locations [✓] M07 Maintenance Requests [✓] M08 Work Orders [✓] M09 Job Plans [✓] M28 Notifications [✓] M29 Reporting [✓] ───────────────────────────────── M15 Condition Monitoring [ ] M16 Predictive Maintenance [ ] M17 Reliability / FMEA [ ] M22 Fleet [ ] ... 21 more inactive
Company A runs basic CMMS today. Activate M15 / M16 / M17 when telemetry sources are wired up; activate M22 when fleet ops onboard. No re-deploy.
Phased rollout. Steady-state in 3 months.
We do not try to ship 33 modules at once. Phase 1 + 2 land basic CMMS in three months. Phases 3 + 4 unlock advanced features once the foundation is working and your team has real operational data to inform decisions.
Per-Tenant Extension on your BC tenant. No external middleware to license, monitor or upgrade.
1
Asset inventory walk-through. Existing maintenance process audit. Module shortlist (you do not need all 33 on day one). Statutory and safety requirements.
2
Setup Wizard, Asset Register, Functional Locations, Work Orders, Job Plans, Notifications. Train Planner and Technician roles. Go-live on basic work-order flow within 4-6 weeks.
3
Maintenance Strategies + Meters + Scheduling + Spares + Procurement linkage. Maintenance team sees a planning board with auto-generated due work. 4-8 weeks.
4
Condition Monitoring, Predictive Maintenance, Reliability/FMEA, Calibration, Safety/Permits. AI features activated with budget caps. 6-10 weeks depending on telemetry sources.
5
Fleet, Energy, Mobile rollout, Contracts/SLA. Most customers reach steady-state on Phases 1 + 2 within three months and decide Phase 3/4 scope based on operational data.
Frequently asked questions
Business Central v25 and above, both SaaS and On-Premises. AL 13 runtime, Cloud target. Distributed as a Per-Tenant Extension (not AppSource) — installed via Extension Management with the signed `.app` from SourceForge. Object range 54000-54999. Depends only on the Microsoft System Application 27.0; no other third-party dependencies.
Show us your asset list. We will configure it live.
A 60-minute working session, not a sales pitch. Bring a slice of your asset register and the maintenance pain you want to solve first. We bring up a BC sandbox, import your assets, configure work orders + a maintenance strategy, and show you the Calculation Trace for the first generated PM.
- Live import of a real asset list
- First work order generated from a maintenance strategy
- Honest answer on whether you need Phase 3 / 4 modules now
- Written proposal within 48 hours