Emma: Right now, US manufacturing is losing something like $50 billion a year to unplanned downtime.
Ryan: It’s a staggering number. Yeah.
Emma: I mean, every single hour a critical line sits idle, it costs your average large manufacturing operation roughly $260,000. Yeah, and you know the craziest part about those numbers? The multi million dollar software running these very factories is completely blind to the fact that the machines are dying.
Ryan: It is a massive blind spot. Yeah, I mean, we’re looking at Dynamics365 Business Central today. And natively, the equipment inside that platform just has no voice.
Emma: Right. It’s totally silent.
Ryan: Exactly. You might have a critical bearing running incredibly hot. Or like a major work center quietly ticking past its 1,000 hour service interval.
Emma: Or a fleet vehicle blowing 3,000 miles past its oil chain.
Ryan: Right. The machinery knows it’s hurting, obviously, but the system running the business is just completely unaware.
Emma: Okay, let’s unpack this for you. I want you to imagine you’re driving down the highway at 70 miles an hour, but the dashboard of your car is completely blacked out.
Ryan: Oh, that’s. Yeah, that’s a good way to put it.
Emma: Right. Like no speedometer, no check engine light, no temperature gauge. The absolute only way you know your engine needs oil is when it literally bursts into flames on the interstate.
Ryan: It’s terrifying.
Emma: But that is exactly how most ERP systems treat millions of dollars worth of heavy machinery.
Ryan: It’s a highly accurate, if terrifying way to visualize it. Though we should probably clarify that this is rarely a lack of willingness from the maintenance teams themselves.
Emma: Oh, sure, yeah.
Ryan: Like those skilled millwrights and technicians, they desperately want to do proactive maintenance.
Emma: Of course they do. Nobody wants the machine to catch fire.
Ryan: Right. What we’re dealing with here is a fundamental structural disconnect between production data, you know, what the machine is actually doing on the floor, and the maintenance activities required to keep it alive.
Emma: So the software handles the business of
Ryan: making things, but it leaves the care of the machines entirely up to human memory.
Emma: Wait, I need to understand how we got here. These companies are spending absolute fortunes on cutting edge platforms, right?
Ryan: Oh, massive amounts of money. Yes.
Emma: Yeah, they are tracking every single penny in the ledger. Routing global shipments, optimizing inventory down to the specific shelf bin.
Ryan: Yeah, the precision is incredible.
Emma: But they are still using a paper binder to track when a million dollar stamping press needs an oil change.
Ryan: Natively yes. That is the actual reality on the shop floor.
Emma: Wow.
Ryan: And it sounds like a massive oversight until you look at the architecture. I mean, this isn’t a flaw in Business Central. It’s a very deliberate scope decision by the developers.
Emma: A scope decision? How so?
Ryan: Think about the mindset of an enterprise software architect. The platform is brilliantly built to manage linear flows. Raw materials in production, steps executed, finished goods out.
Emma: Right. Very logical. Step A to step B.
Ryan: Exactly. But maintenance is entropy. It is the degradation of the tools making the goods.
Emma: Oh, gosh.
Ryan: Because that doesn’t fit the linear flow. The system essentially treats maintenance as something called a capacity absence.
Emma: Meaning the system just knows the machine isn’t available to make things today. It doesn’t actually care why it’s unavailable.
Ryan: That is the core of the issue right there. Natively, you can go into the system, register a workcenter as unavailable, maybe block off some time on a calendar.
Emma: Just block it off? Like a meeting?
Ryan: Yeah, exactly. And maybe you bury a text note in a comment field somewhere.
Emma: Right.
Ryan: What you cannot do is define a recurring inspection interval based on actual usage. You cannot track runtime against a machine center.
Emma: You can’t even store a native list of spare parts. Right?
Ryan: No, not for a specific asset. And you certainly can’t hand a technician a mobile device with step by step digital work instructions.
Emma: Which totally explains the paper binders. I mean, the maintenance team has no choice but to build their own silo. Because the main platform just shut them out.
Ryan: Yep. They retreat to whiteboards, spreadsheets, physical binders, or maybe, you know, completely standalone software programs that never even talk to the main erp.
Emma: Just to keep the factory running.
Ryan: Exactly. And to give you the bigger picture, people often point out that Business Central has a fixed asset register.
Emma: Right? Right.
Ryan: And they ask, well, why isn’t that used for maintenance?
Emma: Because it’s an asset. Right. It makes sense.
Ryan: On paper it exists, sure, but it’s designed for accountants. It records the existence of your equipment so you can track its financial depreciation over time.
Emma: So it’s just about the money?
Ryan: Completely. It provides zero native mechanism to trigger a work order when a machine hits, say, 500 hours of runtime.
Emma: Okay, so the accountant knows exactly how much the machine is worth on paper, as it depreciates.
Ryan: Yes.
Emma: But the operator running the machine has no idea. The internal components are literally grinding to dust.
Ryan: That’s a perfect summary of the disconnect.
Emma: I mean, natively, that is a glaring gap. But surely companies haven’t just accepted the blacked out dashboard forever. People Must be finding ways to bridge that gap.
Ryan: Oh, they try to. The traditional approach was to go out and buy a completely separate system like an EAM platform.
Emma: Enterprise Asset Management.
Ryan: Right. You purchase this entirely separate software specifically built for maintenance, and then you attempt to bolt it onto your ERP and lemme diss.
Emma: Bolting two massive software platforms together never works as smoothly as the sales brochure promises.
Ryan: Not even close. The integration burden is massive.
Emma: I can imagine.
Ryan: You pay for extra licensing. You battle constant data syncing errors, the
Emma: APIs break every time there’s an update.
Ryan: Constantly. And you force your technicians to climb this steep learning curve to use a completely different interface that looks nothing like the rest of the company’s software.
Emma: Okay, so here’s where it gets really interesting. Because looking at the specs for a maintenance manager by InsightWorks, they approach this entirely differently.
Ryan: Very differently.
Emma: Yeah, if the old way of bolting on an EAM was like hiring a clunky translator who only half understands both languages.
Ryan: Right. Constantly dropping words and causing confusion.
Emma: Exactly. Maintenance Manager just teaches the ERP a new dialect based on words it already knows fluently.
Ryan: That’s a great way to frame it.
Emma: It’s like instead of building a fragile bridge between two separate islands, the EAM island and the ERP island, Maintenance Manager just builds a new house right on the mainland.
Ryan: Yep. It’s a CMMS that runs natively and inside Business Central.
Emma: Natively.
Ryan: That word natively is critical here. It represents a real architectural breakthrough because
Emma: they aren’t faking an integration.
Ryan: Right. They didn’t just build a parallel data structure inside the platform and cross their fingers hoping it synced up. They made one brilliantly simple design choice.
Emma: Which is?
Ryan: Maintenance Manager uses standard Business Central production orders as the foundation for its maintenance work. Orders.
Emma: Okay, I get why native is better than bolted on, but I don’t quite get the mechanics there. Sure, if Business Central wasn’t built for maintenance. Maintenance. Aren’t they just forcing a square peg into a round hole by calling a maintenance job a production order?
Ryan: It sounds like it, but think about the ripple effects of what a production order actually does. It’s a language Business Central is already a master of.
Emma: Right. It does production very well.
Ryan: Exactly. The platform knows how to pull parts for a production order. It knows how to schedule time for one and how to track the costs associated with it.
Emma: Oh, I see where this is going.
Ryan: By disguising a maintenance job as a production order, suddenly every single existing capability in the system works perfectly with maintenance right out of the box.
Emma: Meaning you don’t have to write custom code to tell the warehouse how to pick a spare part.
Ryan: Nope.
Emma: The warehouse already knows how to pick parts for production. So it just does its normal job.
Ryan: Precisely. Warehouse functions, shop floor execution, planning, worksheets, even third party ISV apps created by independent software vendors. They all instantly know how to interact with these maintenance orders. Because to the system’s core architecture, it
Emma: just looks like another standard process that is incredibly elegant. Hacking the system using its own rules, basically.
Ryan: It really is.
Emma: And because of this design, the setup is supposedly shockingly simple. Like there’s an installation wizard that applies default data and posting groups.
Ryan: Yeah, making it usable almost immediately, which is unheard of for maintenance software.
Emma: And I assume you don’t even need that fixed asset record we talked about, right?
Ryan: It solves that major headache too. With this native solution, you don’t even need a fixed asset record to track
Emma: an item, so you can track smaller stuff.
Ryan: Exactly. You can set up equipment as standard items with a maintenance designation that allows you to track maintenance on smaller tooling fleet vehicles.
Emma: Things that don’t financially qualify as depreciating assets but still need oil changes.
Ryan: Absolutely. Things that require regular maintenance to keep the business running.
Emma: Okay, so the foundation is laid. The system understands the language, but a platform doesn’t magically know a bearing is wearing out.
Ryan: Right.
Emma: Something has to feed it data. How does the system actually track the wear and tear without relying on someone typing numbers into a keyboard all day?
Ryan: Well, we have to look at how we measure degradation. Maintenance manager allows you to set intervals in four distinct ways.
Emma: Okay.
Ryan: The first is simple. Duration, weekly, monthly, annual.
Emma: The classic calendar method, like change the oil every six months, whether the machine ran for five hours or 5,000.
Ryan: Yeah, it’s a staple, but it’s highly inefficient. The next three methods are where the real power lies.
Emma: Let’s hear them.
Ryan: You can trigger by runtime, say every 500 machine hours. You can trigger by output count, like every 100,000 cycles or pieces produced.
Emma: Or distance for vehicles.
Ryan: Right, exactly. Every 10,000 miles for a fleet vehicle.
Emma: But how is it getting that data? Because if a shift supervisor has to walk around at 5 o’ clock every day with a clip that reading gauges and manually typing the runtime hours for 40 different machines into the system, we are right back to massive human error.
Ryan: That’s the best part. It eliminates the clipboard entirely. Because this is a native solution, production assets are already linked to work centers.
Emma: Right.
Ryan: The runtime and output counts update automatically whenever a production order posts against that specific Resource.
Emma: Wait, really? So the machine finishes a batch of parts, the operator logs that the batch
Ryan: has done, and the system just quietly ticks up the wear and tear counter in the background?
Emma: Yes.
Ryan: Zero manual data entry required. The production log and the maintenance log are essentially reading from the exact same source of truth.
Emma: That is huge.
Ryan: The margin of human error vanishes because the machine’s actual output is directly driving its maintenance schedule.
Emma: Okay, let’s follow that logic. The machine hits 100,000 cycles and automatically flags that it needs a new bearing. The dashboard finally lights up, but a flag in the software doesn’t physically fix the machine. If the parts cage is empty, all that beautiful data is useless.
Ryan: So true.
Emma: So what does this all mean for the person whose job it is to order the parts? Are we finally eliminating the panic of realizing a part is out of stock on the day the machine breaks?
Ryan: Historically, this is where silos caused the most financial damage. Oh, for sure, the maintenance team would know they needed a specialized part, but. But the purchasing team wouldn’t find out until a work order was slapped on their desk.
Emma: We need this tomorrow.
Ryan: Exactly. With maintenance manager. When that interval is triggered, the system generates a work order that includes a complete bom, a bill of materials for
Emma: the required spare parts, and the labor routing too, Right?
Ryan: Along with the specific labor routing. Yes.
Emma: So it basically builds a recipe. It lists exactly which physical parts are needed and what kind of mechanic is required to install them.
Ryan: And because it exists natively within the erp, those required parts instantly become live demand signals.
Emma: Oh, wow. The purchasing system sees the demand coming before the machine is even taken offline.
Ryan: Exactly. The standard automated planning run. You know, the process that constantly analyzes what the company needs to buy to fulfill its orders. It reads that maintenance order just like any other order. Right. If you do not have enough of those specific bearings in stock, the system will automatically recommend purchasing them, which gives
Emma: you plenty of lead time, often weeks
Ryan: in advance of the scheduled maintenance date.
Emma: That completely eliminates the panic buying. Ordering the parts before the machine breaks based on mathematical reality rather than a supervisor’s gut feeling.
Ryan: And consider the impact on production scheduling as well.
Emma: Right. The downtime.
Ryan: When that work order is released, the maintenance capacity is officially consumed in the master schedule. If a facility runs an automated production scheduling tool, that tool sees the maintenance window.
Emma: So it doesn’t double book the machine.
Ryan: It actively routes production around, finds the least disruptive time slot to take the machine offline automatically.
Emma: That avoids the catastrophic scenario when you are forced to break down a machine in the middle of a rush Order,
Ryan: which leads to missed customer deadlines, expedited
Emma: freight costs, massive operator overtime.
Ryan: Exactly. Treating the maintenance of the machine with the exact same respect and priority it treats a paying customer’s order.
Emma: Because, financially speaking, ignoring the maintenance costs just as much, if not more than losing a customer’s order.
Ryan: It really does.
Emma: So we have the parts sitting on the shelf. The schedule has been automatically adjusted to avoid interrupting critical production runs.
Ryan: Everything is lined up.
Emma: Now we have to talk about the shop floor itself. What happens when the actual wrench needs to to turn? Because ultimately, software doesn’t fix machines, people do.
Ryan: That’s a great point. The human element dictates the success of the entire implementation.
Emma: If it’s too hard to use, they won’t use it.
Ryan: Exactly. If the software is too cumbersome to use on the floor, technicians will bypass it, and your perfect loop of data is broken instantly.
Emma: So how does it handle the execution?
Ryan: On the execution side, technicians do not need a desk or a workstation. They access their work orders directly via the business central mobile interface, right?
Emma: On a tablet or phone or through
Ryan: a shared shop floor terminal.
Emma: It is essentially giving them the ultimate fully digitized mechanics clipboard that talks directly to the boardroom.
Ryan: That’s exactly what it is. When they pull up the job, they aren’t just seeing a vague title like Fix conveyor, right?
Emma: They see detailed work instructions.
Ryan: They have the actual equipment manuals attached, sourced directly from the document management system. They see the exact component requirements right there on the screen.
Emma: No more walking back and forth across a massive factory floor for 20 minutes just to find the physical manual for a specific belt drive.
Ryan: Time on task is optimized. And just like a production operator captures their time, the maintenance technician clocks on and off the job directly in the interface.
Emma: Just tapping a button.
Ryan: Yes. This captures the actual real world labor time against the maintenance order.
Emma: Meaning the CFO finally knows exactly how much it costs in raw labor to maintain that specific piece of equipment over its lifespan.
Ryan: The visibility changes everything. And for the supervisors managing these teams, the value of eliminating tool switching is immense.
Emma: Tool switching? You mean software tools, right?
Ryan: They gain a maintenance calendar with a drag and drop view of scheduled work. More importantly, they have a single graphical scheduler that displays maintenance orders right alongside
Emma: production orders in one unified capacity view. So they see the full picture on one screen. No guessing, no toggling between two completely different software programs trying to mentally cross reference schedules.
Ryan: It makes their job so much easier. And for the Microsoft partners too. You know, the consultants who actually install and configure business central for these manufacturing clients.
Emma: Oh, I bet they love this.
Ryan: This natively integrated approach is a massive relief. Most manufacturing and distribution clients feel this maintenance gap daily.
Emma: Sure, it’s a huge pain point, but
Ryan: they rarely articulate it as a solvable problem within their main platform. They just assume these ERP platforms don’t do maintenance.
Emma: So historically, when a client asked for maintenance tracking, the partner would have to brace them for a massive, expensive custom integration project.
Ryan: Exactly. But because Maintenance Manager runs natively and uses that brilliant production order infrastructure we discussed, the implementation conversation becomes incredibly straightforward.
Emma: Because there is no parallel system to build, no complex APIs constantly breaking every time Microsoft pushes a system update.
Ryan: And the licensing model reflects that simplicity as well.
Emma: It scales reasonably even if it’s a smaller team.
Ryan: Even if a facility just has a single maintenance administrator managing a whole team of technicians on the floor, it does not price the company out of solving the problem.
Emma: That’s fantastic. Looking back at the journey we’ve taken today, we started in a pretty dark place.
Ryan: We did a $50 billion dark place, right?
Emma: We had factories running completely blind, bleeding a quarter of a million dollars an hour to unplanned downtime. Yeah, we had massive sophisticated software systems that basically shrugged their shoulders when it came to machine maintenance, forcing everyone back into the dark ages of paper binders, whiteboards and drifting calendar estimates.
Ryan: But the shift we’ve mapped out is moving from that reactive guesswork to a connected system driven by actual reality, actual data triggering maintenance based on the exact cycles a machine is run seamlessly ordering parts weeks ahead of time, routing schedules intelligently, putting digital manuals right into the
Emma: hands of the technicians, giving the equipment a voice basically, but doing it in the exact dialect the rest of the business already speaks fluently. Perfectly set for those of you listening if you want to explore the mechanics of this further, or if you are sitting there realizing your own multimillion dollar factory is running on a dusty paper binder, you really need to check this out.
Ryan: The full product details, feature overviews and a 30 day trial are available at maintenancefordynamics.com and you should definitely reach out
Emma: to a certified Microsoft partner who can walk you through a hands on demo to see it actually running in your own business central environment.
Ryan: Seeing those maintenance triggers map directly to your specific production routing is usually the moment the concept fully clicks. For facility managers, it makes it real.
Emma: Before we wrap up this deep dive though, I want to leave you with a thought to mull over something that builds on all these facts, but looks just a bit further down the road okay, we’ve established that this native integration now tracks the exact runtime, the precise maintenance costs, the spare parts consumed and the actual labor hours required to keep the every specific machine alive.
Ryan: Right? The total cost of ownership is no longer an estimate. It becomes undeniable mathematical fact.
Emma: So here is the question. If executives finally have this proven data living right inside their financial system, how will this shift the way they decide which manufacturing equipment brands to purchase in the future?
Ryan: Oh, that’s a fascinating angle, right?
Emma: If brand X machines cost three times as much in labor and parts to maintain over five years as brand Y. But you never knew it because the data was hidden away in a siloed spreadsheet, well, you know it now.
Ryan: The data doesn’t lie.
Emma: When your equipment finally gets a voice and that dashboard lights up for the very first time, what secrets is it going to tell you about your past investments? Let that sink in. We will catch you on the next Deep Dive.
