With a deep background in applying advanced technologies like AI and machine learning to solve real-world industrial challenges, Dominic Jainy is uniquely positioned to discuss the operational friction points in modern manufacturing. He has a keen interest in how integrated systems can transform core processes, and today he joins us to dissect a common but costly problem: the conflict between production and maintenance scheduling within Microsoft Dynamics 365 Business Central. Our conversation will explore why this conflict exists, the innovative approach of treating maintenance like a production job, how dynamic scheduling tools can optimize uptime, the shift from calendar-based to usage-based maintenance triggers, and the crucial integration of spare parts planning to prevent costly downtime.
The article states that Business Central doesn’t natively separate maintenance from production, creating conflicts. Besides scheduling clashes, how does this visibility gap typically impact shop floor communication, and what kind of reactive, inefficient workflows have you seen result from it?
The impact on the shop floor is palpable; it creates a constant, low-level tension between planners and technicians. Imagine a planner who just scheduled a high-priority customer order on a key machine, feeling confident they’ll meet the deadline. Then they walk out to the floor and see that same machine completely disassembled by a technician doing a quarterly service. The planner sees a missed deadline; the technician sees essential upkeep. This immediately devolves into a reactive, firefighting mode. The workflow becomes a chaotic scramble of phone calls, hurried meetings to reschedule everything, and authorizing overtime to try and catch up. It’s the opposite of a lean operation; it’s a system that breeds inefficiency and blame simply because two critical departments are working from two different, invisible plans.
You propose treating maintenance like production. Using the “lathe oil change” example, could you walk me through the key steps for creating that maintenance order, linking it to the work center, and ensuring its capacity is correctly blocked from production planners?
Absolutely. It’s about teaching the system a language it already understands: the language of production orders. First, within Business Central, we’d use a solution like the Maintenance Manager app to create a “released maintenance order” for that lathe oil change. This order isn’t just a note; it has a defined routing and a duration, say, two hours. The most critical step is linking this order directly to the lathe’s specific work center in the system. The moment we assign a start and end time to that order and link it to the work center, Business Central treats that two-hour block as consumed capacity. For a production planner using any scheduling tool, from the free Graphical Scheduler to the more advanced MxAPS, that machine now appears unavailable. It’s no longer invisible; it’s a clear, scheduled event that the system must plan around, just like any other production job.
Beyond just avoiding conflicts, the text mentions that MxAPS dynamically places maintenance in low-impact slots. Based on this, what specific metrics—like reduced overtime, improved OEE, or schedule adherence—have companies seen when moving from fixed, calendar-based maintenance to this automated approach?
The shift from a fixed to a dynamic approach creates a powerful ripple effect on key metrics. The most immediate and noticeable improvement is a sharp reduction in unplanned overtime. When maintenance is automatically scheduled between jobs or during other planned downtime, you stop creating those self-inflicted fire drills that require a crew to stay late to catch up. This directly improves schedule adherence because you’re no longer derailing the production plan for routine service. Over the long term, this leads to a significant and measurable improvement in Overall Equipment Effectiveness (OEE). You are fundamentally increasing asset availability by servicing equipment without sacrificing valuable production hours, ensuring that both uptime and throughput are optimized.
Triggering maintenance from real usage, like a forklift’s runtime or output count, is a key feature. How does this automatic data capture improve accuracy versus manual logging, and what are the first steps a company should take to implement these usage-based counters?
The difference in accuracy is night and day. Manual logging is fundamentally flawed; it relies on someone remembering to write down hours or cycles on a clipboard at the end of a busy shift. It’s prone to errors, omissions, and pure guesswork. Automatic data capture, on the other hand, is flawless. Every time a transaction is posted against that forklift—like completing a production put-away—its runtime counter in minutes or its output count is updated within Business Central automatically. The data is a direct byproduct of the work being done. The first step for a company is to analyze its assets and determine the most logical usage trigger for each one. For a press, it might be the cycle count; for a vehicle, it’s runtime hours. Then, using an integrated tool, they simply configure these interval types on the asset’s item card. The system handles the rest, turning standard production posting into an effortless maintenance data feed.
The article notes that visible maintenance orders create demand for spare parts in the planning system. Can you elaborate on how this prevents shortages and share an example of how this integration between maintenance and purchasing kept a critical asset online?
This integration is the final piece of the puzzle that prevents a planned event from becoming an unplanned disaster. Without it, a technician might start a job only to find a critical filter is out of stock, taking a machine offline for days. When a maintenance order is treated like a production order, it has a bill of materials that lists all necessary components—filters, bearings, fluids. The moment that order for a future service is created, the system flags those parts as future demand. I saw this in action where a scheduled overhaul for a primary press was on the books for three weeks out. The system, through the Enhanced Planning Worksheet, immediately recognized the need for a specific, long-lead-time bearing set. It prompted purchasing to order it right away. The parts arrived a week before the maintenance was scheduled, the job was completed smoothly, and the press was back online without a single minute of extra downtime. That’s the power of making maintenance visible to your entire supply chain.
Do you have any advice for our readers?
My advice is to stop treating maintenance as a separate, disruptive force and start viewing it as an integrated, strategic part of your production plan. The daily friction you experience isn’t a flaw in your people; it’s a flaw in a system that makes maintenance invisible to planning. Start by quantifying the real cost of that disruption—the overtime, the express shipping fees for parts, the delayed customer orders. Once you see the numbers, the value of a fully integrated solution becomes undeniable. The technology exists today, right within Business Central, to make maintenance predictable, optimized, and visible. By bridging that gap, you transform maintenance from a source of chaos into a competitive advantage.