MRP Time Fences: Frozen, Slushy, and Open Planning Zones Explained

If you have ever watched an MRP system generate 200 rescheduling messages overnight because a few sales orders shifted by a week, you have experienced MRP nervousness firsthand. The planners look at the message queue, shake their heads, and go back to their spreadsheets. The system ran. Nobody acted on what it said.

Time fences are the mechanism that prevents this. By establishing zones where the plan is frozen, partially adjustable, or fully open to change, time fences transform MRP from a noise generator into a planning tool planners actually use.

After 35 years helping manufacturers implement and stabilize MRP at companies like GE, Cummins, and BAE Systems, User Solutions has set up time fences in environments ranging from 2-person machine shops to 3,000-employee defense contractors. The logic is universal even though the numbers differ.

For full MRP context, start with our complete MRP guide.

What Is MRP Nervousness?

MRP nervousness describes the system's tendency to react to every input change by rescheduling planned orders—and then react to those reschedules with further messages. The cascade effect means that a 50-unit demand increase on a single customer order ripples backward through the BOM, triggering messages on sub-assemblies, purchase requisitions, and work orders for items that may be due in three days.

Three conditions drive nervousness:

1. No frozen zone: Without a frozen zone, MRP will reschedule anything, at any time, in response to any demand change.
2. High replanning frequency: Daily MRP runs on volatile demand data amplify noise. Every day's small demand shifts get treated as signals requiring action.
3. No demand filtering: MRP that treats a 3-unit demand change on a 500-unit item the same as a 200-unit change generates messages that aren't worth acting on.

Time fences solve condition 1. Replanning frequency and demand filtering address conditions 2 and 3. Together, they separate signal from noise.

The Three Planning Zones

Zone 1: The Frozen Zone

The frozen zone covers the period closest to today—typically matching or slightly exceeding your longest manufacturing lead time. Within this zone, the plan is locked. MRP does not automatically reschedule, cancel, or add planned orders based on demand changes.

Inside the frozen zone:

• Firm planned orders cannot be auto-rescheduled by MRP
• Released work orders are not touched by the planning engine
• Purchase orders in transit are not cancelled or modified
• Exception messages may still appear, but they require human authorization before any action is taken

The frozen zone represents your operational commitment. You have already purchased materials, allocated capacity, and made supplier commitments based on this plan. Automatically disrupting it in response to demand noise costs more than absorbing the noise—which is almost always transient.

What can change in the frozen zone? Only what a planner or manager explicitly authorizes after reviewing the exception message. A customer cancels a major order in the frozen zone? That warrants manual review and possible action. A sales order shifts by 10 units? The frozen zone filters that out.

Zone 2: The Slushy Zone (Firm Zone)

The slushy zone—sometimes called the firm zone or the planning time fence zone—sits between the frozen zone and the open zone. Here, MRP can suggest changes but cannot execute them automatically. Every suggestion requires planner review and explicit approval.

The slushy zone typically spans from the end of the frozen zone to your cumulative material lead time: the time needed to procure the longest-lead raw material used anywhere in your product structure. This is the zone where you still have options—you can still place new purchase orders if needed—but you need to think carefully before committing capacity.

Inside the slushy zone:

• MRP generates rescheduling and quantity-change recommendations
• Planners review each recommendation and decide to act or not
• New planned orders can be created, but require approval before becoming firm
• Supplier communication is possible but should reflect actual intentions, not noise

The slushy zone is where good planners earn their pay. They are not blindly accepting MRP messages or blindly ignoring them—they are making judgment calls about whether demand signals are real, whether capacity exists, and whether supplier commitments are feasible.

Zone 3: The Open Zone

Beyond the cumulative material lead time, the open zone is MRP's natural domain. Demand here is forecast-driven and inherently uncertain. MRP can freely create, modify, and cancel planned orders in response to demand changes because no real commitments have been made yet.

Inside the open zone:

• MRP automatically generates and modifies planned orders
• New planned orders are created based on demand minus available inventory
• Supplier capacity reservations (not firm POs) may exist but are not binding
• The plan is a working hypothesis, not a commitment

The open zone is where capacity planning happens. Rough-cut capacity planning (RCCP) uses the open zone's planned orders to identify future overloads and underloads on key resources—so planners can adjust capacity (overtime, subcontracting, demand leveling) weeks or months before the problem becomes a crisis.

Setting Fence Lengths: The Key Variables

Use Cumulative Lead Time, Not Product Lead Time

The most common time fence mistake: setting the frozen zone to the finished goods lead time without accounting for the cumulative lead time of the purchased components inside it.

Example: You build a machined assembly in-house in 2 weeks. That sounds like a 2-week frozen zone. But the key raw material—a specialty alloy bar—has a 10-week supplier lead time. If your frozen zone is 2 weeks, MRP will reschedule planned orders for the alloy based on demand changes—orders that are already placed with a supplier who needs 10 weeks. The reschedule messages are useless. Worse, MRP may cancel a planned purchase order for material you actually need.

The frozen zone should be at least equal to your cumulative lead time: the total time from first material release to finished goods completion through the longest path in your BOM.

Calculate Cumulative Lead Time for Your Product Families

1. Pull your top 10 product families by revenue.
2. For each, identify the longest-lead purchased component anywhere in the BOM.
3. Add: supplier lead time + receiving/inspection + manufacturing lead time (sub-assembly + final assembly).
4. That sum is the minimum frozen zone for that product family.

A job shop making custom machined parts from 6061 aluminum might calculate:

• Aluminum bar stock: 2-week lead time
• Machining: 1 week queue + 3 days run
• Assembly: 2 days
• Total: ~4 weeks cumulative lead time → 4-week frozen zone minimum

A medical device manufacturer with a regulated casting sub-assembly might calculate:

• Casting from specialty supplier: 14 weeks
• Incoming inspection (sterilization validation): 2 weeks
• Final assembly: 1 week
• Total: ~17 weeks cumulative lead time → the frozen zone for that product line needs to be at least 17 weeks

Setting the Slushy Zone

The slushy zone spans from the end of the frozen zone to approximately 1.5–2x the frozen zone length. It represents the window where planning decisions are still possible but require judgment.

Practically, many manufacturers set the slushy zone as a second time fence—the planning time fence—and define their MRP behavior differently inside it:

• Within the frozen zone: no auto-replanning, all changes require explicit override
• Between frozen and planning time fence (slushy): MRP messages generated but not auto-executed, planner must approve
• Beyond planning time fence (open): MRP runs freely, planned orders generated and modified automatically

Time Fence Examples by Manufacturing Type

High-Mix Job Shop (Custom Machined Parts)

A job shop producing 200 unique part numbers with lead times of 1–4 weeks:

• Frozen zone: 3 weeks (matches the 90th percentile of manufacturing lead times)
• Slushy zone: 3–8 weeks (enough to place raw material orders if needed)
• Open zone: 8+ weeks

The shop runs MRP weekly (not daily) to reduce noise. Demand changes under 10% within the slushy zone require planner discretion but no management approval. Changes over 10% or any change inside the frozen zone require the operations manager sign-off.

Flow Shop (Consumer Goods, Make-to-Stock)

A consumer goods manufacturer running 8 high-volume SKUs on dedicated lines:

• Frozen zone: 2 weeks (most components are stocked; longest lead time is packaging at 3 weeks, so technically packaging's fence is 3 weeks while finished goods is 2)
• Slushy zone: 2–6 weeks
• Open zone: 6+ weeks

This shop runs MRP daily because demand is relatively stable and the frozen zone is short. They use a demand filter: MRP ignores demand changes less than 5% of the weekly plan within the slushy zone—only larger swings generate exception messages.

Mixed-Mode Defense/Aerospace Manufacturer

A defense contractor making both standard MRO parts (make-to-stock) and complex assemblies (make-to-order, 12–26 week lead times):

• Standard parts, frozen zone: 4 weeks
• Complex assemblies, frozen zone: 14 weeks (matches cumulative lead time including long-lead castings)
• Slushy zone for complex assemblies: 14–26 weeks

The key insight here: these product families need separate fence configurations. A global time fence would either be too short for complex assemblies (causing nervousness) or too long for standard parts (preventing legitimate replanning).

Human Processes Around Fence Management

Time fences only work if the organization respects them. The software can enforce fence logic, but planners need to understand why the fence exists—otherwise they will override it constantly, defeating the purpose.

Who can override the frozen zone?

Define this explicitly. A common policy:

• Planners can authorize changes inside the slushy zone independently
• Changes inside the frozen zone require the Planning Manager's approval
• Changes inside the frozen zone that require customer communication (short shipments, delays) require Sales Director involvement

Weekly fence review meeting

Most manufacturers with effective time fence management run a weekly planning meeting that reviews:

1. Exception messages inside the frozen zone: what are they, and do they require action?
2. Capacity alarms in the slushy zone: are there emerging overloads that need to be addressed now?
3. Open zone demand changes: are any large demand changes building that will enter the slushy zone soon?

This meeting is typically 30–60 minutes and replaces the daily firefighting that characterizes plants without fence discipline.

Fence violations as a KPI

Track how often the frozen zone is overridden, and why. A high override rate means either the fence is too long (it is protecting too much of the schedule) or the business is genuinely volatile (in which case the answer is better demand management, not shorter fences). A zero override rate over many months suggests planners are either ignoring legitimate exceptions or the fence is too short to catch anything meaningful.

How Time Fences Interact With Capacity and Demand Changes

Time fences are not demand filters—they are planning stability mechanisms. They do not make demand changes disappear. They create a structured process for deciding what to do about those changes.

When a major customer calls to expedite a large order:

• If the order ships in the open zone: MRP adjusts automatically on next run, planners are notified of resulting capacity changes
• If the order ships in the slushy zone: MRP flags it as an exception, planner reviews capacity and supplier availability, makes a call
• If the order ships in the frozen zone: the fence triggers an override workflow. Planner reviews what would have to move to accommodate the expedite, calculates the cost, and escalates if the decision is significant

This is the fundamental shift time fences enable: from reactive firefighting to structured exception management.

Connecting Time Fences to MRP Output Quality

When time fences are properly set and respected, MRP output quality improves dramatically:

• Exception message volume drops by 60–80% within the first month
• Planners start reading and acting on the remaining messages because they are now meaningful
• Supplier relationships improve because order changes become less erratic
• Schedule attainment (the percent of work orders completed on time) typically improves 10–20 percentage points within a quarter

The improvement is not because the demand got less volatile. It is because the planning process got structured enough to absorb demand variability without constantly disrupting the execution plan.

---

---

Struggling with MRP exception message overload? Contact User Solutions to learn how RMDB implements time fence logic that matches your actual manufacturing environment. Trusted by GE, Cummins, BAE Systems, and manufacturers across North America for 35+ years.