---
title: "Time Fences in IFS Cloud: Demand and Planning Time Fence"
date: 2026-10-29
description: "How the demand and planning time fences work in IFS Cloud: what each protects, who sets the values, and how master scheduling and MRP react."
author: "Dariusz Myśliwiec"
intro_image: "https://ifs-erp.consulting/images/articles/demand-time-fence-planning-time-fence-ifs-cloud-en-d15276e8.webp"
fulltext_image: "https://ifs-erp.consulting/images/articles/demand-time-fence-planning-time-fence-ifs-cloud-en-d15276e8.webp"
categories:
  - name: "How IFS Cloud ERP Transforms Business Operations Supply Chain AI and Legacy System Migration"
    url: "https://ifs-erp.consulting/ifs-cloud.md"
tags:
  - name: "IFS Cloud"
    url: "https://ifs-erp.consulting/tags/ifs-cloud.md"
  - name: "Planning"
    url: "https://ifs-erp.consulting/tags/planning.md"
  - name: "IFS Cloud Implementation"
    url: "https://ifs-erp.consulting/tags/ifs-cloud-implementation.md"
  - name: "Best Practices"
    url: "https://ifs-erp.consulting/tags/best-practices.md"
  - name: "Planning Phase"
    url: "https://ifs-erp.consulting/tags/planning-phase.md"
---

# Time Fences in IFS Cloud: Demand and Planning Time Fence

![Time Fences in IFS Cloud: Demand and Planning Time Fence](https://ifs-erp.consulting/images/articles/demand-time-fence-planning-time-fence-ifs-cloud-en-d15276e8.webp)

Independent IFS Cloud practice · Planning design

 
## Know where the plan is frozen and where the system may still change it

 The **planning time fence** and the **demand time fence** in IFS Cloud divide the planning horizon into periods in which master scheduling and MRP treat supply and demand differently. A planner who expects the system to change supply inside the planning time fence, or to accept forecasts inside the demand time fence, gets neither, and planned supply does not move when expected. This article follows the 26R1 page on [time fences for demand and planning](https://docs.ifs.com/ifsclouddocs/26r1/lang/en/MasterScheduling/AboutTimeFenceDemandAndPlanning.htm), and the 26R1 pages on [master scheduling](https://docs.ifs.com/ifsclouddocs/26r1/lang/en/MasterScheduling/AboutMasterScheduling.htm) and [material requirements planning](https://docs.ifs.com/ifsclouddocs/26r1/Planning/AboutMrp.htm).

  **Key takeaways**

 
- The planning time fence represents the cumulative lead time of the part, and the demand time fence is the shorter of the two periods.
- For Level 0 parts the system generates both values; for Level 1 parts you must specify them; a demand time fence of 0 means that no demand time fence applies.
- Inside the planning time fence, the master scheduling calculation does not create or modify any supply proposals, and planned master schedule supplies falling there become Fixed.
- As a part moves within the planning time fence, the planner must convert system-generated proposed receipts manually into manual proposals, firm planned shop orders or released shop orders.
- MRP receives demand from existing shop orders only within the demand time fence, from existing shop orders and the fixed master schedule between the fences, and from existing shop orders and the fixed and variable master schedules outside the planning time fence.
- The two documentation pages word the demand time fence differently, and this article quotes both.

  ## 1.What are the demand time fence and the planning time fence?

 The planning time fence represents the cumulative lead time of the part, that is, the length of time it would take to produce the part if none of the subassemblies were in stock. The demand time fence is the shorter of the two periods. Both are calculated using the manufacturing calendar for the manufactured parts and the distribution calendar for purchased parts, and they are counted in work days: if the demand time fence is entered as 4 and the last master schedule run date is Monday, the demand time fence extends through Thursday. The lead time definitions behind the cumulative lead time are covered in [lead times in IFS Cloud](https://ifs-erp.consulting/ifs-cloud/ifs-cloud-lead-time-purchase-manufacturing-expected).

  ## 2.How are the fences set?

 For Level 0 parts, the system generates both values automatically. For Level 1 parts, you must specify them. To calculate the planning time fence, the critical path method is used, and a demand time fence of 0 means that no demand time fence applies. The structure of Level 0 and Level 1 parts is described in [Master Production Schedule Level 1](https://ifs-erp.consulting/ifs-cloud/master-production-schedule-level-1-ifs-cloud). The Level 1 page adds that when MRP creates supplies for MS handled actual demand, both fences can be set to an equal value, and that in the supplier schedules mode both fences on the Master Schedule Level 1 Part page should be set to 0.

  ## 3.What happens inside the demand time fence?

 The time fence page says: “During the demand time fence, the master schedule is frozen, meaning that changes are extremely difficult to make.” The page on master scheduling words it differently: “Inside DTF, the production plan is considered fixed and not possible to change.” The two sentences come from two pages, and this article does not merge them into one rule; check the behaviour of your release against both.

 The master scheduling page adds that no forecasts can exist inside the DTF and, depending on settings, forecasts are either dropped or rolled out outside the DTF when passing the fence. The messages page has a matching message, “Forecast ignored within demand time-frame”: if a forecast is found inside the demand time fence, it is ignored, since only the actual demand is considered there.

  ## 4.What happens between the two fences?

 The demand falling within the planning time fence is a mixture of actual customer orders and forecasts. During the time period beyond the demand time fence but within the planning time fence, changes to the master production schedule require consideration of management trade-offs. The messages page raises “MS-plan is within the planned time-frame” when a master schedule receipt is found between the demand and planning time fence.

  ## 5.What must a planner do inside the planning time fence?

 Before a part reaches the planning time fence, it is not associated with any shop or purchase orders; the system forecasts the supply and generates master schedule proposals. As a part moves within the planning time fence, you must analyze the system-generated proposed receipts and convert them into manual proposals, firm planned shop orders or released shop orders. You must perform this step manually because, once the part is within the planning time fence, any changes you make may adversely affect lower levels of the structure.

 The master scheduling page states the calculation side: “Inside PTF, the MS calculation will not create or modify any supply proposals, since we can't make sure manufacturing is actually possible.” Planned MS supplies that fall inside the PTF become Fixed. Where you have indicated that requisitions can be created, shop order requisitions and/or purchase order requisitions are also created. Outside the PTF, the MS calculation generates Planned MS proposals, and beyond the planning time fence the master production scheduler is free to change the schedule. Fixed master schedule proposals remain in existence until the run date, but they do not affect any calculations within the demand time fence.

  ## 6.How do master scheduling and MRP treat each period?

 The 26R1 master scheduling page and the 26R1 MRP page each state a rule for the periods around the two fences.

 
| Period | Master scheduling | MRP |
| --- | --- | --- |
| Within the demand time fence | No supply proposals created or modified (inside the PTF); forecasts ignored | Only existing shop orders can generate demand |
| Between the demand and planning time fences | No supply proposals created or modified (inside the PTF); planned MS supplies become Fixed | Demand from both existing shop orders and the fixed master schedule |
| Outside the planning time fence | The calculation generates Planned MS proposals | Existing shop orders and the fixed and variable master schedules |

  ## 7.How do promising and intraday planning use the fences?

 Order promising reacts to the fences per promise method. The behaviour of Available to Promise and Unconsumed Forecast relative to the planning and demand time fences is tabulated in [Master Scheduling Available to Promise](https://ifs-erp.consulting/ifs-cloud/master-scheduling-available-to-promise-ifs-cloud), and capable-to-promise in [CTP in IFS Cloud](https://www.ifs-erp.com/en/blog/ctp-in-ifs-cloud).

 For a part with Plan Manufacturing Supply on Due Date enabled, the demand and planning time fences are shifted one day earlier when the part is master scheduled. That setting is described in [IFS Cloud intraday availability](https://ifs-erp.consulting/ifs-cloud/intraday-availability-supply-demand-ifs-cloud).

  ## 8.Who may change a fence value?

 A fence changed in one week alters what the system will touch the next. For Level 1 parts the values are specified by a person, so the planning lead decides who may enter them and records each change with the date. The review interval for the values is left to the business, because the pages state none. The person who converts proposals inside the planning time fence is named per part group, since the conversion is manual and the page warns that changes may adversely affect lower levels of the structure. The planners also agree how to read the two wordings of the demand time fence above before the first run.

  ## 9.How do you test the fences before go-live?

 Test with demand entered inside and outside each fence, and write down the expected treatment before each run.

 
| Scenario | Expected treatment | Owner |
| --- | --- | --- |
| Forecast inside the demand time fence | Forecast ignored; message “Forecast ignored within demand time-frame” | Planner |
| Master schedule receipt between the two fences | Message “MS-plan is within the planned time-frame” | Planner |
| Master scheduling calculation with a planned supply inside the PTF | No supply proposal created or modified; the planned MS supply becomes Fixed | Planner |
| Part moves into the planning time fence | Proposed receipts converted manually into manual proposals, firm planned shop orders or released shop orders | Planner |
| MRP run with a shop order and a fixed master schedule proposal in each period | Demand sources as in the period table | Planning lead |
| Demand time fence set to 0 | No demand time fence applies | Planning lead |
| Demand time fence 4, last run on Monday | The fence extends through Thursday | Planner |

  ## 10.What does a time fence checklist contain?

 The time fence set-up is ready for go-live when each check below has a record behind it.

 
1. The fence values of the Level 1 parts are entered and the person who may change them is named.
2. Level 0 parts are checked for the generated values.
3. The planners have read both wordings of the demand time fence.
4. The owner of the manual conversion of proposals inside the planning time fence is named per part group.
5. The MRP demand sources per period are written down for the planners.
6. The seven test scenarios are recorded with evidence.

  ## 11.Frequently asked questions

 What is the difference between the demand time fence and the planning time fence in IFS Cloud? The planning time fence in IFS Cloud represents the cumulative lead time of the part, that is, the length of time it would take to produce the part if none of the subassemblies were in stock. The demand time fence is the shorter of the two periods.

   How is the planning time fence calculated? The IFS Cloud planning time fence is calculated using the critical path method, with the manufacturing calendar for manufactured parts and the distribution calendar for purchased parts. It represents the cumulative lead time of the part.

   Who sets the time fence values? For Level 0 parts, IFS Cloud generates both time fence values automatically. For Level 1 parts, the values must be specified by the user. A demand time fence of 0 means that no demand time fence applies.

   What does master scheduling do inside the planning time fence? Inside the planning time fence, the IFS Cloud master scheduling calculation will not create or modify any supply proposals, and planned master schedule supplies that fall inside the planning time fence become Fixed. Where requisitions can be created, shop order and purchase order requisitions are also created.

   What does MRP do inside the demand time fence? Within the demand time fence in IFS Cloud, only existing shop orders can generate demand in MRP. Between the demand and planning time fences, MRP receives demand from both existing shop orders and the fixed master schedule.

  ## 12.About the author

 **Dariusz Myśliwiec**: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

 IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

  ## Does the plan change where your planners expect it to?

 A review of the time fence values and of the way your planners treat the fenced periods shows where the system and the planners expect different things.

 [Book a time fence review](https://ifs-erp.consulting/contact) [Read about Level 1 scheduling](https://ifs-erp.consulting/ifs-cloud/master-production-schedule-level-1-ifs-cloud)
