Manufacturing & OperationsGlossary

What Is Planning Time Fence?

Also known as: time fence, demand time fence, DTF, PTF, planning fence

Definition

A planning time fence is a number of days from today inside which MRP will not automatically create or change planned supply. Changes in that window need planner approval, which keeps near-term production stable while the outer horizon remains flexible.

Planning Time Fence Explained

Close to today, the shop floor has already purchased material, scheduled machines and set up tooling, so large automated reschedules are disruptive. A time fence marks that stable window. Inside it, MRP either suppresses new planned orders or only issues action messages. Beyond it, MRP is free to create, delete and move planned orders.

Two fences are commonly distinguished. The demand time fence is the horizon in which forecast is ignored and only firm customer orders drive planning, so noisy forecasts do not trigger rebuilds. The planning time fence is the horizon in which the planning engine will not change supply on its own. In some systems the two are set separately per item, in others they are combined with a single frozen period.

Setup is per item or per item and site. SyteLine exposes planning fence settings on the item and item warehouse planning data, Infor LN uses time fences in its planning parameters, and SAP uses planning time fence and the planning strategy on the MRP views of the material master. The fence length is typically tied to cumulative lead time or the frozen period of the master schedule.

The tradeoff is responsiveness against stability. A fence that is too long makes the plant slow to react to real demand changes. A fence that is too short lets MRP churn orders the shop is already running.

Why It Matters

  • It is the primary defence against schedule nervousness in the weeks the plant is actively building.
  • It decides who is in control near term: the engine or the planner.
  • A mismatch between fence length and real lead time causes either late supply or constant reschedules.
  • Fences interact with master schedule freeze periods, so they need to be set together to avoid contradictory rules.

In Practice

Example: an assembly has a 20 day cumulative lead time and a planning time fence of 15 days. A new sales order arrives for delivery in 10 days. Inside the fence, MRP does not create a planned order for it. It raises an action message and the planner decides whether to expedite, split an existing job or tell sales the earliest date.

Frequently Asked Questions

What is the difference between demand and planning time fences?

The demand time fence controls which demand MRP uses, typically actual orders only, while the planning time fence controls whether MRP may change supply. They are often set to different lengths for different items.

How long should a planning time fence be?

A common starting point is somewhere between the item's own lead time and its cumulative lead time, adjusted for how stable demand is. Review it against actual expedite and reschedule frequency.

What happens to orders created inside the fence?

They have to be created or changed manually, usually guided by action messages. This keeps the plan stable but puts the work on the planner.

Working with Planning Time Fence in a live environment? Our engineers do this every day - and our AI agents automate most of it.

Try it here, free

MRP Planning Time Fence Calculator

Open full tool

Derive a demand time fence and planning time fence from your lead times and see how much of the horizon is frozen.

Get ERP alerts and new tools

Support deadlines, release changes and new free tools for the ERP you run. A couple of emails a month at most.

Free. Unsubscribe with one click from any email.

ArchRay builder
Design the on-prem AI stack: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP