Business Central & APICS/ASCM for Manufacturers: A Field Guide for Consultants and Plant Managers

Reading Time: 4 minutes

After 30 years in ERP, 15 of them implementing Business Central and NAV across factories in the UK and Europe, I’ve come to one pretty solid conclusion: the consultants who actually manage to turn around struggling implementations are the ones who speak APICS.

A lot of the BC guides out there either skip APICS (now ASCM) entirely or treat it like some dusty university theory. Both approaches are a huge mistake. APICS isn’t just theory; it’s the exact language your planners and production managers are already using to run the floor, whether they have the official CPIM certification or not. When you set up reordering policies in BC without understanding APICS terminology, you end up with configurations that look flawless on paper, but cause absolute chaos on the shop floor.

This guide is basically the “APICS-to-Business Central” translator I wish someone had handed me twenty years ago. No fluff, no textbook definitions. Just how you actually map these concepts to the software without making the planners hate you.

Does Business Central Actually Speak APICS?

Honestly, yes, and surprisingly well. If you look at the ASCM SCOR model (Plan, Source, Make, Deliver, Return), Business Central can handle the heavy lifting right out of the box.

For the Plan and Source sides, BC’s Planning Worksheet is incredibly robust, whether you’re running regenerative MPS/MRP or just daily net changes. You can easily map out your reordering policies, time buckets, and safety stocks. For Make and Deliver, the core manufacturing data is all there: BOMs, routings, work center calendars, and warehouse bin structures.

But BC isn’t perfect. There are real gaps. Standard BC will keep your plans feasible with Capacity-Constrained Resources, but if a client needs advanced finite scheduling, visual Gantt chart sequencing, or complex changeover matrices, I don’t try to hack the standard system. I point them straight to an APS add-on like NETRONIC VAPS or Insight Works. Similarly, if they are doing deep process manufacturing with shifting chemical potencies or strict regulatory co-products, they’ll likely need a specialised ISV. Knowing when not to use standard BC is just as important as knowing how to configure it.

The Three Flavours of Manufacturing (and where things go wrong)

You really have to look at what they are making before you touch the setup. Standardising everything is a recipe for disaster.

1. Discrete Manufacturing: The Comfort Zone

If your client is making custom engine components, you’re in BC’s sweet spot. This is all about countable units. You rely on strict, certified Production BOMs and detailed routings.

The setup: I usually set the reordering policy to Order (for MTO) or Lot-for-Lot with short time buckets. You’ll want to use Backward (or Pick+Backward) flushing tied directly to your operations via Routing Link Codes. This way, as the engine block moves through the work centers, the system consumes the exact parts automatically. And absolutely use Order Promising (ATP/CTP) so your sales team stops giving clients impossible delivery dates.

2. Process Manufacturing: The Danger Zone

Think mixing industrial cleaning chemicals or food processing. This is where I see most implementations crash and burn. People try to set it up exactly like a discrete process, and it falls apart immediately.

The setup: Here, you have to obsess over batch integrity. You need Item Tracking Codes that enforce Lot tracking and strict Expiration Calculations. Your warehouse must be set up for FEFO (First-Expired, First-Out) picking. The biggest headache is always units of measure. Getting the conversions from litres to kilograms right on the BOM is critical. Finally, make sure you stage your raw materials correctly; use To-Production bins and Internal Picks so the blenders aren’t waiting around for ingredients.

3. Repetitive Manufacturing: The Flow

This is high-volume, standardised production. Think churning out thousands of the exact same smartphone charger on a dedicated assembly line. Here, you want the ERP to completely get out of the way.

The setup: You don’t want people clicking buttons all day. Leave your Released Production Orders open for the whole week. Rely heavily on Pick+Backward flushing, and mark your bottleneck machines as Capacity Constrained. For components, set up a supermarket pull system right at the line: use the Fixed Reorder Qty policy with tight reorder points so that the warehouse only brings materials to the line when they are actually needed.

Making JIT Work in the Real World

Everyone asks for Just-in-Time (JIT) because they read about Toyota, but very few have the discipline for it. It absolutely works in BC, but it requires a methodical rollout. I always insist on starting with just one pilot product family to test the waters. Here is the blueprint I use:

Phase 1: Fix the Foundation (Master Data)

Before you even think about pull signals, you have to clean up the data. Garbage vendor lead times will kill a JIT setup on day one. Ensure your UoMs, on-hand balances, and work center capacities reflect reality, not an ideal world.

Phase 2: Choke the Inventory (Planning Parameters)

Go into your Item/SKU cards and make pull the default. Set the Replenishment System to Production Order for your finished goods. Change the Reordering Policy to Order or Lot-for-Lot with very short Time Buckets. The scariest part for most planners: drop the Safety Stock and Safety Lead Time down to zero (or as close to it as you dare).

Phase 3: Tighten the Warehouse Flow

JIT dies if materials can’t move fluidly. Enable Bin Mandatory on your locations. Define specific “Open Shop Floor” bins for line staging, and use Internal Picks to move components exactly when the line needs them, not a day before.

Phase 4: The Daily Discipline

You can’t run JIT with weekly planning meetings. Your planners need to run the Planning Worksheet with Calculate Net Change Plan daily, sometimes twice a day. Review the action messages and carry them out immediately. If your suppliers are integrated with Blanket POs to handle the frequent, small-batch requests, your cycle times will plummet.

What 15 Years on BC (and 30 in ERP) Has Taught Me

Business Central is a highly capable, APICS-aligned system. In most cases I see, proper, thoughtful configuration beats expensive custom coding every single time.

The difference between a factory that runs smoothly on BC and one that fights the software daily almost always comes down to three things: master data quality, getting the planning parameters right for your specific manufacturing type, and building solid daily habits on the shop floor. If you understand the operational theory behind what your planners need, those BC setup screens suddenly become a lot less intimidating.