Skip to content

Inside Insights · Season 3, Episode 49

Reach Robotics replaces spreadsheets with Business Central

How does a manufacturer of underwater robots keep planning and traceability on track when its back office runs on spreadsheets? This episode follows Reach Robotics, a 50-person manufacturer in Sydney, as it moves to Business Central and Insight Works apps with partner Dynamic Aspect. It covers multi-level bills of materials, planned versus actual labor time, serial-level traceability for defense work, and 35 to 45 percent less manual processing.

October 19, 2026 · 20 min

In this episode

  • Replacing spreadsheets with Business Central at a robotics manufacturer
  • Planning and procurement in one worksheet view
  • Comparing planned and actual labor time on routings
  • Serial-level traceability for defense and marine contracts
  • Results in manual processing, inventory, and ERP payback
Read the transcript

Ryan: So I want you to picture the most advanced high pressure underwater environments on Earth. Right. The kind of places where we use incredibly complex robotic manipulation arms just to inspect things.

Emma: Yeah, we’re talking cutting edge hardware.

Ryan: Exactly.

Emma: Stuff that has to be flawless.

Ryan: Exactly. But here is the wild part. Until very recently, the company building those literal marvels of engineering was managing their operations using administrative tech from like the 1980s. I am talking about manual disconnected spreadsheets.

Emma: I mean, it really is a jarring contrast. You have these brilliant engineers designing autonomous systems for marine science and defense on one side of the campus. Right, right. And then on the exact same campus, you’ve got an operations team basically fighting with broken Excel formulas just to figure out if they actually have enough screws in stock to finish a build.

Ryan: It sounds so stressful. And that specific friction is exactly what today’s deep dive is focused on. We are unpacking a case study about Reach Robotics.

Emma: Right. Based in Sydney, Australia.

Ryan: Yep, Sydney. And they are an advanced manufacturing company operating with a pretty tight team of about 50 people. So our mission today is to figure out how this mid sized company managed to bridge that massive gap between their 21st century robotics and their totally outdated back office systems.

Emma: It’s a huge leap to make.

Ryan: It really is. We are going to look at why those manual systems were breaking down. The exact mechanics of how they rebuilt their digital foundation without halting production, and the data that shows what happens when a company finally synchronizes its physical and digital realities.

Emma: And you know, this analysis really goes beyond just upgrading software. It’s fundamentally a story about scale.

Ryan: Oh, absolutely.

Emma: It explores what happens when those human workarounds, like the little favors and manual checks teams do for each other when they can no longer support the weight of a company’s commercial success. It’s a super common and honestly very dangerous bottleneck for businesses.

Ryan: So I want you to keep that in mind as we go through this material today. Think about the workflows that you navigate every day. Have you ever felt like your team or your organization is doing incredibly sophisticated work out in the world, but the systems holding it all together behind the scenes are basically held together with duct tape?

Emma: A lot of duct tape and a prayer.

Ryan: Right. If that sounds familiar, you are definitely going to relate to the baseline reality of where Reach Robotics started out.

Emma: Well, let’s establish that baseline. So Reach Robotics is headquartered in Glebe, New South Wales, but they actually maintain sales operations spanning North America and Europe.

Ryan: Okay, so a global footprint.

Emma: Exactly. And they do not manufacture standard consumer electronics. Their hardware goes into maritime infrastructure, law enforcement, mining and autonomous robotics, which are

Ryan: highly regulated, high stakes environments. I mean, if a robotic system fails during a maritime infrastructure inspection is not a minor inconvenience, you know, it is a massive liability.

Emma: A huge liability. And as they took on more of these really complex defense and industrial programs, their internal administrative load just grew exponentially.

Ryan: The spreadsheet creep.

Emma: Yeah, exactly. The breakdown here wasn’t some sudden catastrophic crash. It was a slow, steady creep of inefficiency. So, for example, production tracking and labor times were being recorded entirely manually in spreadsheets.

Ryan: I want to pause on that point for a second because relying on spreadsheets sounds annoying, sure, but maybe not fatal to a business.

Emma: Right? Lots of people use them.

Ryan: But if we really think about the mechanics of a fast moving manufacturing floor, a spreadsheet is technically obsolete the exact second you hit save.

Emma: Oh, totally.

Ryan: By the time an engineer manually types in that, say, a specific titanium joint is finished, the physical robot on the shop floor has already moved two stages down. Down the assembly line.

Emma: Exactly. And that delay creates a complete lack of real time visibility. And then you have to factor in version control.

Ryan: Oh, no. Version control in shared spreadsheets.

Emma: It’s the worst in a manual system. Just consider the butterfly effect of a single human error. Like a typo in a cell regarding the inventory of a specialized motor housing.

Ryan: Just one fat finger mistake.

Emma: Yep, that one keystroke error propagates through the entire company. Planners think they have parts, they don’t. Or, or procurement orders. Incredibly expensive parts they already have sitting in a corner somewhere.

Ryan: Okay, let’s unpack this. It makes me think of like a high end restaurant where the wait staff is taking orders on paper, the prep cooks only read French, and the person buying the groceries is operating on a two week delay.

Emma: That’s a great way to look at it.

Ryan: Right? Like the final dish going out to the table might be Michelin star quality, but the kitchen itself is in a constant state of controlled chaos because absolutely nothing is synchronized.

Emma: And that lack of synchronization meant planning and procurement were complete, divorced from the physical reality of the shop floor. I mean, the people buying the raw materials and the people actually building the robots were operating in different realities.

Ryan: Which is terrifying for accounting.

Emma: Exactly. Because these workflows were disconnected, the finance data and the operations data rarely matched up.

Ryan: The source material actually notes that at the end of a reporting Cycle. Someone actually had to sit down and manually reconcile all these disparate ledgers, which

Emma: took days, days of manual work. Yeah, it’s a massive operational risk.

Ryan: It really is. But honestly, this is where I get stuck on the strategy side. Because upgrading a core software system for a 50 person company while they are actively fulfilling complex defense contracts, I mean, that sounds like trying to change a car’s engine while it is driving down the highway.

Emma: It really does.

Ryan: How does a business actually execute a transition like that without grinding operations to a complete halt?

Emma: Well, it is arguably one of the highest risk projects a mid sized company can undertake. I mean, if an erp, an enterprise resource planning, planning implementation is botched, it can literally stop a company dead.

Ryan: Like you can’t even operate.

Emma: Right. You cannot ship products, you cannot invoice clients, you cannot purchase raw materials. Everything stops. Reach Robotics recognized this risk and realized they needed a system that offered a unified platform. But they also knew they needed outside expertise to orchestrate the transition without blowing up their daily output.

Ryan: Okay, so the case study indicates they partnered with a Microsoft partner called Dynamic Aspect to actually manage the implementation. And they used Microsoft Dynamics 365 Business Central Online as the foundational platform.

Emma: Yeah, that was the core.

Ryan: But reading through the specifics, a standard out of the box business platform isn’t robust enough for the highly nuanced requirements of building complex robotic hardware, right?

Emma: No, and that is a crucial distinction. A core ERP handles finance and general operations really well. But Reach Robotics required specialized tools explicitly designed for the manufacturing floor.

Ryan: So how did they solve that?

Emma: So to solve this, Dynamic Aspect integrated two specific applications from an independent software vendor called Insight Works, which develops specialized manufacturing and productivity solutions.

Ryan: Okay.

Emma: And they tackled the most glaring bottleneck first, which was planning and procurement. They utilized an application called the Enhanced Planning Pack.

Ryan: The sources mentioned that about 15 staff members use this specific tool every single day. It pulls supply, demand, vendor lead times and current inventory into a single interface. The Enhanced Planning Worksheet.

Emma: Right, which just makes logistical sense.

Ryan: Totally. On a basic level. The buyer doesn’t have to tab through three different software systems to figure out if they need to order more wiring harnesses for next month’s production run.

Emma: Exactly. It’s all right there.

Ryan: But the case study heavily emphasizes their reliance on two specific features here. The Multi-Level BOM Viewer and Routing Analysis. Now, Multi-Level BOM Viewer sounds like serious corporate jargon. What is the actual mechanic here?

Emma: It sounds a bit dry, I know.

Ryan: Is this just about middle management having nicer dashboards, or does this Fundamentally change how the company operates.

Emma: Oh. It fundamentally alters their entire procurement and scheduling strategy. So BOM stands for bill of materials. You can think of it as the recipe for the robot.

Ryan: Okay, the recipe. I like that.

Emma: But in advanced hardware engineering, it is not a flat list of ingredients. A robotic arm has a sub assembly for the gripper. That gripper has a sub assembly for the motor housing. The motor housing has a sub assembly for the internal wiring.

Ryan: Wow. Okay, so it is literally a recipe made out of other recipes. It is a deeply nested hierarchy.

Emma: Exactly. And that nested hierarchy is the multi level aspect of the viewer. It allows a planner to visually map the dependencies across the entire build.

Ryan: So they can see everything connected.

Emma: Right. So if there is a delay in shipping, say, a tiny microchip that sits at the very bottom level of that nested recipe.

Ryan: A part that costs like $2.

Emma: Yeah, exactly. The planner can instantly see how that delay will impact the final delivery date of the entire robotic system at the top level.

Ryan: Okay, that makes a lot of sense for the physical materials. What about the Routing Analysis then? I assume routing refers to the actual physical path the robot takes through the factory stations.

Emma: Almost. It refers to time sequence and human labor. Routing is the specific sequence of operations required to build a product from start to finish. The analysis tool allows planners to compare the planned time for a specific task against the actual time it took an engineer to complete it.

Ryan: Oh, interesting. Let’s walk through the mechanics of how that actually prevents a problem. Say the digital plan allocates two hours for an engineer to assemble a motor housing, but the Routing Analysis consistently shows it takes four hours.

Emma: Okay. Yeah.

Ryan: How does the software intervene to prevent a massive scheduling pileup downstream?

Emma: Well, think about their previous spreadsheet system. A two hour discrepancy goes entirely unnoticed until Friday afternoon when a milestone is missed and everything is suddenly late.

Ryan: Right. Fire drill mode.

Emma: Exactly. But with the integrated Routing Analysis, the system identifies that variance dynamically. It allows planners to adjust the schedule for the next production run based on empirical data.

Ryan: Oh, I see.

Emma: So if step A now takes four hours instead of two, the system flags that step B needs to be pushed back. It can automatically recommend reallocating machine time or even delaying a raw material order for step C, preventing those downstream bottlenecks before they actually manifest on the floor.

Ryan: Wow. So the digital plan is constantly correcting itself based on the physical reality of the factory.

Emma: Yeah, it’s alive, essentially.

Ryan: But. And here’s the catch. A dynamic self correcting digital plan is only as good as the raw Data being fed into it by the human beings doing the work. If the engineers are still typing their hours into a shared spreadsheet, the whole system still fails. Right.

Emma: You’re totally right. Bridging that final gap between the planner’s digital screen and the engineer’s physical workbench was the next necessary step. This is where the second application, Shop Floor Insight, was implemented.

Ryan: Okay. This appears to be the point where the physical work connects directly to the digital ecosystem. The production staff transitioned to using mobile devices and barcode scanning to record their progress.

Emma: Yeah, consider the shift in daily workflow for the staff, rather than an engineer jotting down their labor time on a

Ryan: piece of scratch paper or trying to remember it later.

Emma: Right. Or logging into a terminal at the end of a 10 hour shift and trying to estimate how many hours they spent on three different sub assemblies. Now they simply scan a barcode when they begin an assembly assembly and they scan it again when they finish.

Ryan: It’s so much simpler. It captures labor time, production progress, and quality events as they happen in real time. Yeah, but the feature that stands out the most regarding their specific industry is how this application captures lot and serial numbers at the exact point of production. We are talking about defense and marine science contracts here.

Emma: The stakes are incredibly high.

Ryan: Let’s play out a hypothetical scenario to understand those stakes. Say a highly advanced robotic manipulation arm fails while operating on a defense submersible 5,000ft underwater. What actually happens next from a compliance standpoint?

Emma: Well, the client, which is likely a government or military entity. They will demand an immediate and exhaustive investigation. Naturally, they need to know exactly why the system failed. Was it a fundamental design flaw? Was it human error during assembly? Or was it a faulty raw material from a third party vendor?

Ryan: Any of their old spreadsheet system in that old system?

Emma: Finding that answer would require a team of people spending days digging through paper records, cross referencing disjointed Excel files and just hoping the data was entered correctly. Months ago.

Ryan: What a nightmare. And under the new barcode scanning system,

Emma: the process is instantaneous. They can pull up the serial number of that specific failed robotic arm and trace its entire lineage just from one scan. Yep. They can see that the point of failure was a specific titanium screw. The system shows them that this screw came from lot number 456 provided by a specific vendor on a specific date. Furthermore, they can see that engineer A installed that exact screw on a Tuesday afternoon. And the Routing Analysis shows the installation took 15 minutes.

Ryan: That level of forensic detail is absolutely crucial for survival in that industry. It’s what compliance officers refer to as traceability.

Emma: Traceability is the non negotiable foundation of working in aerospace, defense or deep sea technology.

Ryan: You just can’t operate without it.

Emma: If a company cannot unequivocally prove the provenance, handling and installation history of every single component, they simply cannot bid on those contracts. By capturing those serial numbers with a quick barcode scan while the part is actively being installed on the floor, Reach Robotics integrated compliance seamlessly into the daily workflow.

Ryan: It stopped being this heavy administrative burden at the end of the month and became an automatic byproduct of just building the robot.

Emma: Exactly.

Ryan: Executing a transition of this magnitude without halting the company’s output is so impressive. The strategy the implementation partner used was to structure the rollout to deliver what they called early operational value.

Emma: That’s a key strategy, right?

Ryan: They mapped the workflows to the new platform and rolled out features that solved immediate pain points quickly, rather than waiting for some massive company wide launch a year down the road.

Emma: Taking a phased approach is how you build momentum and trust among a staff. When leadership asks a team of highly specialized engineers to change how they have worked for years, they need to see the practical benefits quickly.

Ryan: Otherwise they just push back.

Emma: Exactly. And the measurable results of this implementation were substantial. According to the case study, Reach Robotics achieved a full return on their ERP investment in under 12 months.

Ryan: An infrastructure overhaul paying for itself in under a year points to an incredible amount of hidden friction and wasted capital in their previous setup.

Emma: Oh, for sure.

Ryan: And the metrics back that up. The case study highlights a 35 to 45% drop in manual processing across the board.

Emma: That single metric represents a massive shift in how a company utilizes its human capital.

Ryan: Oh, absolutely.

Emma: Think about the daily psychology of a highly skilled manufacturing engineer or a senior procurement officer. Their actual value to the company is in their problem solving, their technical ability and their strategic thinking, not data entry. Right before this transition, they were spending effort hours re keying data from a piece of paper into a computer or manually trying to reconcile mismatched ledgers. Automating that data entry removes a layer of mundane friction that just drags down morale and productivity.

Ryan: It also directly impacts the velocity of the business. Reporting cycles went from taking days of manual data wrangling to taking just hours.

Emma: Which means leadership finally had current reliable information to base their strategic decisions on.

Ryan: But the metric that is most impactful from a business health perspective is on the materials side. They optimize their inventory by 15 to 25%.

Emma: That optimization is the direct Measurable result of the Enhanced Planning Pack.

Ryan: How so?

Emma: Well, when a company operates on disconnected systems, procurement teams naturally become defensive. If a buyer does not trust the data telling them what they have in stock, their instinct is to over order,

Ryan: of course, just in case.

Emma: Yeah. They buy extra components as a buffer because running out of a part means production grinds to a halt, which is the ultimate failure for them.

Ryan: Wait. Optimizing inventory by up to 25% is a massive shift in capital allocation. In the context of advanced robotics, we aren’t talking about storing a few extra boxes of generic bolt or office supplies.

Emma: No, not at all.

Ryan: These are highly specialized, very expensive components. Optimizing inventory by that much fundamentally changes a company’s cash flow. It frees up heavy amounts of capital that was otherwise trapped on a warehouse shelf gathering dust.

Emma: Millions of dollars, potentially.

Ryan: Right. They can reinvest that cash into research, development, or hiring new talent.

Emma: When an operations team establishes rigorous real time discipline, and they know with certainty that their digital system accurately reflects their physical inventory, they can run a much leaner, more aggressive operation.

Ryan: They purchase exact exactly what is required precisely when it is needed.

Emma: Exactly. Nathan King, the head of operations at Reach Robotics, summarized the outcome perfectly in the source material. He stated that the solution delivered a platform capable of providing accurate real time visibility across finance, manufacturing, supply chain and operational planning.

Ryan: All while supporting the stringent governance expectations of the defense industry.

Emma: Exactly.

Ryan: That concept of establishing a single source of truth is incredibly powerful for organizational alignment. When the finance team looks at a budget number, when procurement looks at a supply number, and when the engineers on the shop floor look at a production number, they are all looking at the exact same real time data set.

Emma: There is no longer a localized debate over whose department spreadsheet is the accurate one.

Ryan: What this case study ultimately illustrates is that scaling a hardware business requires more than just innovative product engineering.

Emma: Reach Robotics was already designing world class autonomous systems. But to truly grow their market share, a company must build an operational foundation that matches the sophistication of its products.

Ryan: You can’t have a modern robot running on a vintage spreadsheet.

Emma: Exactly. Transitioning away from fragmented spreadsheets to a unified platform allowed them to reclaim thousands of hours of labor, optimize their working capital, and secure their position in highly demanding, heavily regulated markets.

Ryan: They successfully aligned their back office with their bleeding edge technology. Think about the business, the team, or the specific projects you were involved in right now. Reach Robotics was forced to rebuild their entire digital nervous system so it could keep up with the physical reality of the complex machines they were building.

Emma: It’s a great lesson for anyone scaling up.

Ryan: It really is. Take a hard look at your own organization. What are the hidden spreadsheets in your workflow? What are the manual disjointed workarounds that your team has duct taped together just to get through the week that are currently bottlenecking your ability to truly scale? Sometimes to see how fast the machine can really run, you have to be willing to tear out the outdated engine while it is still moving. Thank you for joining us on this deep dive. We’ll catch you on the next.