The Integrate Intelligently Podcast

Jenn Claridge has been at Sabre Limited since 2008, and the support call she gets most often opens with the same words: MRP is broken. She wrote a blog and recorded a video answering it. The short version is that the software did what it was told.
In this first of three conversations, Jenn walks Jeff Brickler and Scott Brickler through how she got here (a soccer park, an Infor Visual migration, a filing cabinet and an Excel sheet) and what 18 years of manufacturing implementations taught her about Business Central's planning engine. It is, in her words, dumb and dutiful. It produces a different result only when a person gave it a different input.
The practical half is what to do with that. Turn less on and pilot the combinations training sessions skip: dates in the past, negative inventory in a location, a fixed reorder policy with no reorder point, a maximum order quantity set below the minimum. Then treat the item card as the engine, and let Copilot find the silly things in your data before MRP does.
What you'll take from it
The two complaints behind almost every "MRP is broken" call: too much noise, and suggestions that look wrong because a planning parameter was never understood
Why people, process, and technology are three different failure modes, and which one is actually the easy part
The set-less, pilot-more approach to planning parameters, and why lot accumulation periods and dampeners exist
Where AI helps with data cleanliness and where it doesn't replace a person looking at the data
About the guest Jenn Claridge is Vice President of Operations at Sabre Limited, a Business Central partner in Cambridge, Ontario focused on manufacturers. She came up through production, inventory control, and reporting at a manufacturer before joining Sabre in 2008.
Sabre Limited: sabrelimited.com
Jenn on LinkedIn: https://www.linkedin.com/in/jennclaridge/
Scott Brickler is CEO of CADTALK, which moves engineering data from CAD into the ERP so the bill of material MRP depends on is accurate before planning ever runs.
Part 1 of 3. Next: the manufacturers who do this well, and why an ERP is a forever project. Then: the manufacturing knowledge gap and why lingo is the first-phase problem.

In this clip, Stephanie Clark of Elliott Clark Consulting joins Jeff Brickler and Scott Brickler to unpack what actually happens after an ERP go-live and why so many manufacturers rush to planning and scheduling before their data is ready. Stephanie explains why bill of materials accuracy and inventory counts have to come first, why routings should start simple, and why chasing "just in case" data slows teams down instead of helping them. She closes with her core framework for manufacturing ERP success: process, technology, automation — in that order. Key
Takeaways
🧱 Foundation first. Planning and MRP are worthless if inventory accuracy and BOM data aren't right — fix the foundation before adding sophistication.
🎯 Keep routings simple. Don't overcomplicate routings out of the gate. Start with basic time standards and build detail once the team has adopted the process.
🚫 Beware "just in case" data. Capturing excessive detail "in case we need it later" usually just delays implementation and increases inaccuracy.
✈️ Course-correct, don't wait for perfect. Like a flight autopilot constantly correcting course, budgeting and process improvement work best when you start imperfectly and refine as you go.
🤝 You're not behind — you're normal. Every manufacturer has data and process gaps. The difference is being willing to find them and fix them.
Best Quote "I'm gonna go back to my three things again: process, technology, automation, in that order. Get your process and your data cleaned up first... and then use technology to do it better, and lastly use automation to do it faster." Stephanie Clark, Elliott Clark Consulting

A bill of materials that's off by a little slips right past Business Central. No error, no warning. It just feeds wrong costs into every report downstream, and the system keeps handing you clean-looking numbers built on bad math.
In part 2 of 3, Business Central consultant Stephanie Clark, who came up as a cost accountant, follows a sloppy BOM all the way to a margin that doesn't match the bank account. She gets into why the data problems that hurt most are the ones the system never flags, what actually stops teams from getting BOMs clean, and why entering the same part into CAD, PLM, and ERP by hand is, in her words, death.

Beyond the Software: Business Central Done Right If your ERP implementation didn't deliver the results you expected, the problem probably wasn't the software. Host Jeff Brickler sits down with CADTALK founder & CEO Scott Brickler and Stephanie Clark, founder of Elliott Clark Consulting and Microsoft Business Central expert, to talk about why process comes before technology — every single time. Stephanie brings decades of hands-on ERP experience, from end user to consultant to firm owner, and she doesn't hold back on what actually goes wrong in manufacturing ERP projects.
🔑 Key Takeaways • Process, technology, automation — in that order. Automating a broken process doesn't fix it. It just makes bad outcomes happen faster. Getting the business process right before touching the software is non-negotiable. • "Lift and shift" implementations fail. Moving your old paper-based or legacy process directly into a new ERP without reimagining the workflow is one of the most common and costly mistakes manufacturers make. • Software doesn't fail — misalignment does. When clients say "the software doesn't work," it's almost always a process or data issue underneath, not a software defect. • Data quality is the foundation of everything. Costing, planning, production orders — none of it works right without clean, accurate data. Start with the 20% of items that drive 80% of your business. • User adoption is just as important as configuration. Low-cost, fast implementations can miss the hand-holding that drives real adoption. Setting users up for success takes intentional effort.
💬 Best Quote "If you try to automate a really bad process, you're just gonna have bad data and a bad process that's faster." — Stephanie Clark, Elliott Clark Consulting
⏱ Timestamps
• 0:00 – Welcome & guest introduction
• 1:00 – Stephanie's origin story: from manufacturing manager to ERP consultant
• 2:19 – Starting Elliott Clark Consulting and doing things differently
• 3:45 – Process, technology, automation — in that order
• 6:17 – The lift-and-shift trap: why copying old processes into new software doesn't work
• 7:48 – The "second opinion" service: what's really wrong when ERP feels broken • 9:07 – User adoption, low-cost implementations, and the risks of moving too fast
• 11:57 – Data quality: why you have to get your data right before you go live
📎 Connect With Us
💼 LinkedIn:
CADTALK: https://www.linkedin.com/company/cadtalk
Stephanie Clark: https://www.linkedin.com/in/stephclark/
🌐 Website:
CADTALK: www.cadtalk.com
Elliott Clark Consulting: https://www.clarkelliottconsulting.com/

If you've ever confused PLM with PDM — or wondered whether your company even needs a PLM system — this episode is for you. Host Jeff Brickler sits down with CADTALK founder & CEO Scott Brickler and Mike Halladay, Solution Consultant at Arena PLM (a PTC product), to cut through the acronyms and get practical about what Product Lifecycle Management actually does, who needs it, and how AI is starting to change the game.
________________________________________
🔑 Key Takeaways
• PLM ≠ PDM. PDM manages CAD files. PLM is your single source of truth for the entire product record — mechanical, electrical, software, packaging, documentation, and more.
• PLM and ERP serve different purposes. ERP is a transaction system built around what you're producing today. PLM manages all work-in-process as your product evolves from one producible revision to the next.
• Change control is where PLM earns its keep. A formal revision control process ensures that only approved, complete product definitions make it into production — protecting manufacturers from costly errors.
• Regulated and complex-product industries benefit most. Medical device, defense, high-tech, and any company managing multi-department product records will find the highest ROI in PLM.
• Even ETO companies can benefit. If you're reusing subsystems across engineered-to-order projects, PLM keeps those subsystems well-managed and revision-controlled.
________________________________________
💬 Best Quote
"PLM is the system you use for all of your work in process — as you go from the last producible revision of your product to the next." — Mike Halladay, Arena PLM
________________________________________
⏱ Timestamps
• 0:00 – Welcome & guest introductions
• 1:27 – PDM vs. PLM: What's the actual difference?
• 3:01 – Where PLM fits vs. ERP (and why ERP isn't enough)
• 4:46 – Revision control: PLM's core superpower
• 6:31 – PLM for configure-to-order & engineer-to-order manufacturers
• 9:53 – The engineering change process: when does it cross from PLM to ERP?
• 15:38 – Which industries and company profiles benefit most from PLM?