A bearing is running hot. A work center is quietly approaching its 1,000-hour service interval. A fleet vehicle is 3,000 miles past its last oil change. Nobody in Business Central knows any of this because, out of the box, Business Central has no structured way to track it.
Why Does Maintenance Fall Through the Cracks in Business Central?
The gap is not a software flaw; it is a scope decision. Business Central is built to manage production, inventory, purchasing, and finance. Maintenance is treated as a capacity absence at best: you can register a work center as unavailable, block off time on a calendar, and bury a note in a comment field. What you cannot do natively is define a recurring inspection interval, track runtime against a machine center, store parts requirements for a specific asset, or give a technician a mobile job card with attached manuals and step-by-step work instructions.
The result is familiar. Maintenance lives in spreadsheets, paper binders, or a standalone CMMS with no connection to the production schedule. Across U.S. manufacturing alone, unplanned downtime costs an estimated $50 billion annually, with the average large manufacturing operation losing roughly $260,000 for every hour a critical line sits idle. The underlying problem is rarely a lack of willingness to do proactive maintenance. It is that the ERP provides teams with no practical mechanism to connect maintenance activities to production data. Business Central’s fixed asset register can record the existence of your equipment and track depreciation, but it provides no native way to assign maintenance intervals, build service bills of materials, or trigger work orders when a runtime counter hits a threshold.
Closing that gap has traditionally required a separate enterprise asset management (EAM) platform, which adds its own integration burden, licensing costs, and a learning curve your millwrights and maintenance technicians have to climb.
How Does Maintenance Manager Solve the Problem?
Maintenance Manager by Insight Works is a computerized maintenance management system (CMMS) that runs natively inside Business Central. Rather than building a parallel data structure, it uses production orders as its foundation for maintenance work orders. That one architectural decision means every existing Business Central capability, including warehouse functions, shop floor execution, planning worksheets, and third-party ISV apps, works with maintenance orders exactly the same way it works with production orders.
How Does Maintenance Manager Work in Practice?
Setup is intentional in its simplicity. An installation wizard applies default data, numbering series, and posting groups, so the system is usable almost immediately. Equipment items are created as standard Business Central items with a maintenance designation and can be linked to existing fixed assets or set up independently for tooling, vehicles, or any asset that does not require a fixed asset record. Each piece of equipment is assigned maintenance tasks with intervals defined by duration (weekly, monthly, annual), runtime (every 500 machine hours), output count (every 100,000 cycles), or distance (every 10,000 miles). For production assets linked to work centers or machine centers, runtime and output count updates automatically whenever a production order posts against that resource. No manual data entry, no separate collection step.
When maintenance is due, the planning worksheet generates work orders complete with bills of materials for spare parts and labor routings. Those parts become live demand signals in Business Central, so the standard planning run will recommend purchasing them if stock is insufficient. When a work order is released for a production asset, that capacity is consumed in the schedule. If you are running an automated production scheduling tool, it routes production around the maintenance window, finding the least disruptive time slot rather than blocking out a fixed slot regardless of production needs.
On the execution side, technicians access their work orders via the Business Central mobile interface or a shared shop-floor terminal. They see work instructions, attached manuals sourced from document management, and component requirements. They clock on and off the job, capturing actual labor time against the maintenance order, just as production operators capture time against production runs. A maintenance calendar provides a drag-and-drop view of scheduled work, and the graphical scheduler shows maintenance orders alongside production orders in a single capacity view so supervisors can see the full picture without switching tools.
Why Does This Matter for Partners and End Users?
For end users, particularly production supervisors, maintenance managers, and facility teams, Maintenance Manager replaces the guesswork of reactive maintenance with a system directly connected to how the plant actually runs. Intervals are triggered based on what the equipment has actually done, not a calendar estimate that drifts further from reality each month. Technicians arrive at a job with documentation in hand. Spare parts are on the shelf because the planning run knew they would be needed weeks in advance.
For Microsoft Partners, Maintenance Manager addresses a gap that most manufacturing and distribution clients feel but rarely articulate as a solvable ERP problem. Because it runs natively in Business Central and leverages production order infrastructure, the implementation conversation is straightforward: no integration project, no parallel system to maintain, and a licensing model that scales reasonably for a single maintenance administrator managing multiple technicians.
Where Can You Learn More?
Full product details, a feature overview, and a 30-day trial are available at MaintenanceForDynamics.com. To see Maintenance Manager running in your own Business Central environment, reach out to a certified Microsoft Partner who can walk you through a hands-on demo and discuss implementation options for your operation.