Independent IFS Cloud practice · Implementation
Key takeaways
Most articles about ERP business impact are written from the brochure. This one is written from the projects. I have spent seventeen years inside IFS, from Apps 7.5 through Cloud, and the pattern that repeats is not that companies pick the wrong system. They pick a capable one and then implement it in a way that throws the capability away: a template nobody reuses, an automation layer nobody trusts, reports rebuilt one for one from the old system because nobody had the authority to delete any of them.
So this is not a list of what IFS Cloud can do. It is a walk through the places where a decision taken during implementation determines whether the platform pays for itself or just replaces one kind of manual work with another. Where a topic deserves its own treatment, I have linked to the longer piece on the ifs-erp.com blog rather than compressing it into two sentences here.
Grouping sites so they share parts, defaults and process setup is sold as a speed feature. It is really a consistency feature, and the speed is a side effect. When site four inherits the purchasing parameters that sites one to three already run on, you are not just saving a week of configuration. You are removing the possibility that site four quietly does receiving differently, which is what costs you two years later when someone tries to compare performance across the group and finds the numbers are not measuring the same event.
The catch is that a cluster only helps if the template being cloned is one somebody defended. Rolling out a bad standard quickly is worse than rolling it out slowly, because a slow rollout at least gives each site a chance to object. I ask for the template to be signed off by the person who will own the process across all sites, not by the site that happened to go first. That is also where the multi-site purchasing decisions belong: whether demand consolidates centrally, and how stock moves between sites once it has.
Further reading: centralised purchasing in IFS Cloud, distribution orders between sites, and from planning to go-live.
IFS Cloud gives you three tools that cover most of what people used to write code for, and knowing which one to reach for is the whole skill. A Quick Report reads data out: a saved query for a list or an extract, with no logic. A Custom Field stores something the standard data model does not. A Custom Event reacts when a row changes, and can hand off to a Workflow that routes an approval, sends a notification, or calls out to another system.
The failure mode is predictable. Teams discover Custom Events, like them, and attach one to everything. Six months later there is an event layer nobody can explain, firing on saves that were never meant to be significant, and the business has learned to ignore the notifications it produces. The second failure mode is subtler: reaching for a Custom Event when the requirement is actually a scheduled check. An event fires when a row changes. It cannot fire because a row has not changed, which is exactly what an unconfirmed order or an untouched receipt is.
Where the requirement crosses a system boundary, the answer is usually an interface rather than an in-system automation. IFS Cloud's OData projections are the normal integration surface, and keeping the orchestration outside IFS keeps that logic out of your ERP, where it would otherwise become one more thing to retest at every release.
Further reading: Custom Events explained, Quick Reports vs Custom Fields vs Custom Events, IFS Cloud API integration, orchestrating IFS Cloud with n8n. Work that has already been built once sits in the configurations and interfaces sections of the marketplace.
IFS Cloud ships R1 and R2 every year. That cadence is the biggest single change in how you should think about customisation, and it is where legacy habits do the most damage. On Apps 9 or 10 an upgrade was an event you prepared for over months, so carrying technical debt between them felt survivable. On Cloud it arrives twice a year, and anything built outside the Extensibility Framework has to be checked, and often reworked, on that same rhythm.
The boundary is simple to state and easy to cross by accident. Extending the data model with Custom Fields, adding logic through Custom Events and Workflows, adapting screens through configuration: all inside the contract, all carried forward. Touching a core object, or building a report or an interface directly against an internal view rather than a published projection, puts you outside it. Nothing stops you at the time. The bill arrives at the next release, and at every release after that.
I have watched this go wrong in both directions. Companies that refuse all extension end up with a shadow layer of spreadsheets doing the work the system was not allowed to do, which is worse, because at least a customisation is visible. The honest position is that some extension is necessary, and the only real question is whether it is built where the platform will maintain it for you.
Further reading: update-safe extensions, the true cost of customisation, clean core in an SCM context, the upgrade tax, the upgrade readiness checklist, and what a release actually brings, with 25R2 purchasing as the worked example. Scoped modification work is listed under marketplace modifications.
Ask a buyer what goes wrong and you get something dramatic: a late shipment, a line stopped for a missing part. Look in the data and the costly problems are the undramatic ones, because nothing in the system objects to them.
| What is sitting there | Why nobody sees it | What it turns into |
|---|---|---|
| A released PO the supplier never acknowledged | The order is valid and open. No field says "ignored" | A delivery date everyone planned around that was never agreed |
| Goods received, invoice never matched | Both records are individually correct | An accrual that grows quietly until period end |
| A supplier price that moved between orders | The new price applies cleanly, exactly as configured | Margin erosion found during an annual review |
| A buyer who stopped ordering from a usual source | Every individual order is legitimate | Concentration risk, or a supplier problem nobody escalated |
All of this is detectable, and all of it is readable through standard OData projections on a read-only account. That means a monitor can look for it daily without touching a record, installing an object, or adding anything the next release has to be checked against. It is the design principle behind the SCM Automation Pack, and the reason the five-day exception scan exists as a way to see what is already in your own data before committing to anything ongoing.
On the physical side the same principle applies to warehouse work. Picking strategy and packing proposals are configuration decisions that quietly set your throughput ceiling, and they are rarely revisited after go-live.
Further reading: unconfirmed purchase orders, what unmatched receipts do at period end, supplier price changes, advanced picking strategies, the packing proposal.
Anomaly detection, demand forecasting and predictive maintenance are genuinely useful, and they all rest on the same unglamorous foundation: whether your master data is good enough for a model to learn from. A forecast built on lead times copied out of the legacy system in 2019 and never reviewed will be precise, confident and wrong, and it will be harder to challenge than a human guess because it arrives with a number attached.
The second thing the demo leaves out is what happens to the output. Detection is the easy half. The half that decides whether any of it pays off is routing: who receives the signal, how it reaches them, and what happens when they do nothing. An alert stream with no named owner and no escalation is a mailing list, and people unsubscribe from mailing lists in their heads long before they do it in the client.
That is why I design exception rules around the recipient rather than the condition. One deduplicated digest per owner per day beats forty individual notifications that are each technically correct. And a rule that cannot state in one sentence what the recipient is supposed to do about it does not ship.
Further reading: alert fatigue and exception design, the cost of missed exceptions, detecting supplier behaviour change, the data attention gap, assumed vs confirmed records, read-only OData monitoring.
Crystal Reports layouts from Apps 9 and 10 do not carry across to IFS Cloud. That is the fact that matters for your plan, whatever any vendor's support calendar says, and it is usually discovered later than it should be, because reporting gets treated as a workstream that can start once the real configuration is done.
IFS Cloud splits the job across different tools. Quick Reports handle lists and extracts: saved queries, no layout ambition, self-service for anyone who can be trusted with a data set. Laid-out business documents are produced through IFS Cloud's own report layout tooling. Analysis and dashboards belong in the reporting and analytics layer rather than in a printed report at all. Trying to recreate a 200-item Crystal inventory inside any one of these is how reporting becomes the critical path.
The work that actually saves you time is triage, and it is a business job rather than a technical one. Pull the usage data first. Most report inventories contain a long tail nobody has run in two years, a middle band that exists because one person likes the format, and a small core the business genuinely runs on. Rebuild the core properly, convert the middle band to Quick Reports or a dashboard, retire the tail. The conversation about retiring the tail is the hard part, which is why it needs to start early and needs someone senior to close it.
Further reading: when a Quick Report is the right answer, and the reports section of the marketplace.
Permission sets in IFS Cloud are capable enough to express proper segregation of duties. Whether they end up doing so is decided in the first six weeks of the project, when someone is under time pressure and the fastest way to unblock testing is to grant a broad set to a group and move on. That grant is almost never revisited, because nothing breaks. It surfaces at the first external audit, when a tester asks who can both create a supplier and approve a payment to it, and the honest answer takes a fortnight to assemble.
Design the role model against the process rather than the org chart, and build it while the process design is still fresh in everyone's head. It costs days then and weeks later. The same applies to standards work: if you operate under ISO requirements, the evidence those audits want is largely a by-product of decisions you are already taking, provided you record them as you go instead of reconstructing them afterwards.
Further reading: RBAC and segregation of duties, permission sets in IFS Cloud, ISO standards in IFS Cloud, and the security section of the marketplace. My own view on the wider ownership question sits on the data governance page.
Every implementation plan has a migration workstream, and most are optimistic by the same margin. The reason is consistent: the effort is not in loading the data, it is in deciding what the data should say. Loading is mechanical. Agreeing that these 4,000 part records are the ones worth keeping, that this status code maps to that one, and that a customer with no valid tax ID is a customer you are not going to migrate, is a series of business decisions with no obvious owner.
Two habits change the outcome. Rehearse the load more than once, on a schedule, with a defined cut of source data each time, so the failure list shrinks between rehearsals instead of being discovered on cutover weekend. And treat validation as its own deliverable with its own sign-off rather than as the last step of loading, because IFS Cloud enforces its business rules at load time: well-formed source data can still be rejected for violating application logic nobody had read.
Further reading: the data migration checklist, how FNDMIG and the Data Migration Manager fit together, and the data migration section of the marketplace.
In most of the companies I work with, a large amount of operational knowledge lives in one person's head and one person's spreadsheet. The buyer who knows which supplier actually delivers on time regardless of what the lead time field says. The planner whose workbook reconciles two things the system does not reconcile. None of this shows up in an ERP assessment, and all of it walks out of the building when that person leaves.
An implementation is the one moment when you have a mandate to surface it. Every shadow spreadsheet is a documented requirement waiting to be read: it exists because the system does not do something, and finding out what that something is tells you more about your real process than a workshop will. Some of them should become configuration. Some should become a Quick Report. A few are genuinely someone's judgement and should stay human, but at least then you know where they are.
The same logic applies to the implementation record itself. Decisions taken in month two get questioned in month eleven by people who were not in the room, and a project that cannot answer "why is it set up this way" reopens settled arguments for the rest of its life.
Further reading: shadow spreadsheet risk, knowledge loss when people leave, buyer knowledge concentration, and the implementation documentation kit if you would rather not build the templates from scratch.
I am wary of quoting percentage improvements. Published ranges come from situations you cannot inspect, with baselines nobody defined, and a number borrowed from another company's business case is not evidence about yours. What I can offer is the short list of measures that survive contact with an actual steering committee.
Further reading: ERP ROI analysis, why go-live is a load test, the implementation crisis.
If you are live on IFS Cloud and this article has described your situation rather than your plan, the order that works is roughly this. Find out what is actually in your data before redesigning anything, because the exception population usually contradicts the received wisdom about where the problems are. Then fix the governance decisions that get harder with time: the role model, the report inventory, the ownership of master data. Automation comes after that, not before, because automating a process nobody owns only makes it produce wrong answers faster.
What I do is on the offer page, the platform view is on the IFS Cloud page, and the process side sits under business process optimisation. The applications themselves, including the read-only exception monitoring described in section 4, live on ifs-erp.com.
No, but the work changes shape. Before go-live it is a design decision that costs nothing extra. After go-live it is an inventory exercise: list everything built outside the Extensibility Framework, establish what each item actually does, and decide case by case whether to rebuild it inside the contract, replace it with standard functionality, or accept the maintenance cost knowingly. The last option is legitimate. What is not legitimate is not knowing which category each item falls into, which is the usual starting position.
No. In most projects I see, the unclaimed value sits in exceptions a plain query would find: orders nobody confirmed, receipts nobody invoiced, prices that moved. That is rule-based detection rather than machine learning, and it works on data that is merely adequate. Model-driven forecasting is worth doing once master data has an owner and a maintenance routine, and worth postponing until it does.
Yes, and that is the approach I prefer for anything that only needs to read. Standard OData projections plus an integration account with read permission are enough to detect the exception patterns in section 4. Nothing is installed in IFS, nothing is written back, and there is no object for the next R1 or R2 release to break. If you want to see the output before committing to anything ongoing, the five-day exception scan produces the same report in observation mode only.
Budget the triage, not the rebuild. Pulling usage statistics and getting a decision on what to retire takes longer than rebuilding the reports that survive, because it needs business sign-off rather than developer time. Start it in parallel with configuration rather than after it, and give the retire list an owner with the authority to say no. Teams that skip this step rebuild everything one for one and carry the whole inventory forward, including the part nobody has opened since 2019.
The configuration saving is small at that scale. The consistency saving is not, and it compounds: two sites configured independently will diverge on receiving, costing and reporting definitions within a couple of years, and reconciling them later is considerably more work than agreeing a shared template now. If there is any prospect of a fourth site, an acquisition, or a group-level report, treat it as worth it.
Dariusz Myśliwiec: 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally through an independent practice.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
If you are scoping an IFS Cloud implementation, or you are already live and suspect the value case has quietly gone missing, a short call is the fastest way to work out which two or three of the eleven sections above are actually costing you something.
Independent IFS Cloud practice · Planning design
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, and the 26R1 pages on master scheduling and material requirements planning.
Key takeaways
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.
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. 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.
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.
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.
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.
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 |
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, and capable-to-promise in 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.
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.
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 |
The time fence set-up is ready for go-live when each check below has a record behind it.
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.
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.
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.
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.
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.
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.
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.
Independent IFS Cloud practice · Master scheduling design
Master Production Schedule Level 1 is the level of the IFS Cloud master schedule where you plan long-term demand for parts that are manufactured or purchased. Its calculation creates supply proposals of five kinds. If nobody described which parts are Level 0 and which are Level 1, forecasts are entered at the wrong level and the proposals are read as something they are not. The planned supply for manufactured and purchased parts then follows from a structure nobody wrote down. This article follows the 26R1 page on Master Production Schedule Level 1 and two 25R2 activity pages for the calculation and the manual update.
Key takeaways
At MS Level 1 you plan long-term demand for parts that are manufactured or purchased. The Calculate MS Level 1 activity requires that you have entered master schedule level 1 parts and registered forecasts, and the registration of level 1 parts can be handled manually or automatically from the level 0 calculation. The result is a gross demand, which forms the basis of MRP.
The parts processed in MS on level 1 do not generate supplies during MRP, unless specifically set to create supplies during MRP for actual demands of MS parts. How MRP then uses structures is covered in dynamic structures and MRP.
Level 1 parts can be considered the end items, because they are at the leaf nodes of planning structures.
| Level | Position in the structure | Forecasts |
|---|---|---|
| Level 0 | The topmost part of the planning structure, when planning is performed on an aggregated family level | Level 0 forecasts are disaggregated, and forecast information comes to Level 1 from Level 0 |
| Level 1 | Leaf nodes of planning structures | Planned directly, or received from Level 0; a part does not need a Level 0 to be planned in MS Level 1 |
The time fences of Level 0 and Level 1 parts and the lead time behind them are defined on the IFS time fence page. Lead time definitions are covered in lead times in IFS Cloud and the routing calculation in routing lead time calculation. This page states one calendar rule: when master scheduling plans are supplied, the manufacturing calendar connected to the site is used for manufactured parts and the distribution calendar for purchased parts.
The page names five kinds of objects that the master schedule proposals create when Level 1 is calculated.
The calculation considers the manufactured/acquired split, the supplier split, the standard multiple quantity and the lot sizes. Fixed proposals within the planning time fence create requisitions only if the Proposal Release field on the Inventory Part/Planning Data tab is set to Release, indicating that supply for the part is not managed by Kanban circuits. For supplier schedules, the demand time fence and planning time fence on the Master Schedule Level 1 Part page should be set to 0, because supplier schedule template rules are applied.
If component parts are planned by MS or defined as MS level 1 parts, the supply proposals for parent parts created by MS are broken down and explode demands to these MS planned components. During MS level 1 calculation, demand explosion stops when it hits an MRP planned component.
The multilevel MS Level 1 calculation will only consider consecutive MS planned parent-child relations in the product structure.
The page section Important Parameters for Level 1 Calculation names nine parameters. Three of them are described below with the page’s own wording.
| Parameter | What the page says |
|---|---|
| Rolling | In the page’s example, an excess part quantity of 100 is subtracted from the first master schedule proposal after the planning time fence |
| Minimum, Multiple and Maximum Lot Sizes | If the minimum and maximum lot sizes are set to zero (0), the lot size is unlimited |
| Rate by Period | The remaining quantity will be moved to the previous period, and the spread and leveling stop at the planning time fence, which is the lower boundary |
| Other parameters on the page | Use Planned Dependent Demand; Use Dependent Demand in Forecast Consumption; Use Abnormal Demand in Forecast Consumption; Include in Import Demand Planning Forecast; Include in Import Customer Schedule; Include Purchase Order Direct Supply |
The page has further sections for multi-site master scheduling, project master scheduling, supplier schedules, MTO DOP parts, consideration of shelf life expiration date in planning, integration with CRP, and starting the MRP process once MS completes. In a multi-site supply chain, it is up to you to determine manually the order in which master scheduling is executed for the sites. When MS is performed integrated with CRP, the shop order requisitions generated by MS are backward scheduled.
The manual update of the Level 1 master schedule requires that the master schedule calculation of level 1 has been performed. When you save the changes, the new value is evenly distributed to each workday in the period, the existing master production schedule receipt value is replaced and the status is set to Fixed. Only a fixed number of periods, the first 40, are displayed. The page gives the calculation of Available Forecast as the previous period Available Forecast value, minus Customer Forecast, minus Actual Demand, plus Work In Process, plus Level 1 Updated, and for the first period the previous period value is the quantity on hand.
The 26R1 page on master scheduling messages includes the message “Insufficient unconsumed supply to satisfy actual demand”, generated when the unconsumed supply is not sufficient to meet the actual demand. A second message, “Forecast ignored within demand time-frame”, is generated when a forecast is found inside the demand time fence, because only the actual demand is considered inside it. Promising against the master schedule is covered in Master Scheduling Available to Promise, and its relation to capable-to-promise in CTP in IFS Cloud.
A forecast appears on a part that nobody expected to receive one, and the proposals that follow have no owner who can explain them. Each of the roles below closes that gap. The planning lead defines which parts are Level 0 and which are Level 1, because the level decides where a forecast is entered and where it is disaggregated. The planner who enters or imports forecasts knows the level of each part before the entry. The planner who reviews proposals knows which of the five object kinds each part produces and which parts stop the explosion because they are MRP planned. The business sets the meeting interval of these roles; the page gives none.
Test with one forecast at Level 0 and one at Level 1, and write down the expected proposals before each calculation.
| Scenario | Expected result | Owner |
|---|---|---|
| Forecast entered at a Level 0 part | Disaggregated into Level 1 forecasts; record the quantity per Level 1 part | Planner |
| Forecast entered at a Level 1 part with no Level 0 | Planned in MS Level 1 without a Level 0 | Planner |
| Calculate Level 1 for a manufactured part, a purchased part and a part with a supplier schedule | Record which of the five object kinds each part produces | Planner |
| Parent part with an MS planned component and a part with an MRP planned component | Demand explodes to the MS planned component; explosion stops at the MRP planned component | Planning lead |
| Maximum and minimum lot size both 0 | Lot size is unlimited | Planner |
| Manual update of one period | New value distributed evenly to each workday of the period; receipt value replaced; status Fixed | Planner |
The Level 1 set-up is ready for go-live when each check below has a record behind it.
Master Production Schedule Level 1 in IFS Cloud is the level where you plan long-term demand for parts that are manufactured or purchased. When Level 1 is calculated, master schedule proposals create shop order requisitions, production schedules, purchase requisitions, supplier schedules and/or distribution orders.
A Level 1 part is a leaf node of a planning structure, an end item. When planning is performed on an aggregated family level, the topmost part of the planning structure is a Level 0 part, and its forecasts are disaggregated into Level 1 forecasts. A part does not need a Level 0 to be planned in MS Level 1.
The Level 1 calculation in IFS Cloud creates master schedule proposals that create shop order requisitions, production schedules, purchase requisitions, supplier schedules and/or distribution orders. The result is a gross demand, which forms the basis of MRP.
During the IFS Cloud MS level 1 calculation, demand explosion stops when it hits an MRP planned component. Components planned by MS or defined as MS level 1 parts receive the exploded demands from the supply proposals of their parent parts.
The IFS Cloud Calculate MS Level 1 activity requires that you have entered master schedule level 1 parts and registered forecasts. Forecast information also comes to Level 1 from Level 0 once the Level 0 forecasts are disaggregated.
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.
A review of the planning structure and the Level 1 set-up with your planners shows which parts sit at which level and what each calculation creates.
Book a master schedule review Read about Available to Promise
Independent IFS Cloud practice · Short-term planning
IFS Cloud intraday availability is the analysis of the short-term supply and demand situation for inventory parts, considering the timings within the day down to minute level. It runs on the Inventory Parts Intraday Availability page. When supply arrives after demand inside a day, projected stock can go negative within that day, and the Negative Projected Qty field is the page’s warning for it. If nobody has decided the horizon, which items count as firm and who reacts to a negative projection, the page shows a picture that nobody acts on. This article follows the 26R1 page on analyzing intraday supply and demand information and the 26R1 page on intraday planning.
Key takeaways
The activity analyzes the short-term supply and demand situation for inventory parts, considering also the timings within the day down to minute level, using the Inventory Parts Intraday Availability page. The main list shows one record per site, inventory part and configuration.
The horizon is a number of days: a value of 1 will show supplies and demands with a due date today and tomorrow. The value is not allowed to be greater than 7 days. The start quantity of the projected quantity is the usable quantity if the Include Usable Qty in Balance check box is selected, and 0 if the check box is cleared. Only shop orders, customer order lines, purchase order lines and production schedules can have a time other than 00:00.
Two check boxes decide the scope: Include Only Firm Supplies and Include Only Firm Demands. When they are selected, only firm supplies and demands are considered. When they are cleared, non-firm supplies and demands are considered as well.
| Kind | Items the page names |
|---|---|
| Firm | Customer order lines, shop order materials, purchase order lines, shop orders |
| Non-firm | MRP planned demands, MS unconsumed forecasts, shop order requisitions, purchase requisition lines |
Three fields flag an imbalance, each against a different reference.
| Field | What the page says |
|---|---|
| Demand Balance | Can be used to identify an unbalance between supplies and demands for the part within the selected time horizon |
| Forecast Balance | Can be used to identify an unbalance between the master schedule forecasted demand and the supply |
| Negative Projected Qty | Gives a heads-up if the projected development within the period goes negative at any point, also considering the time within the day |
An expanded record lists the projected stock development during the defined time period down to a minute level. The page instructs the user to use the commands to adjust the quantities and/or scheduling of the orders to avoid negative stock developments.
This page does not support planning of project connected supplies and demands.
To allow manufacturing to be planned the same day as the demand, Plan Manufacturing Supply on Due Date on the Inventory Part/Manufacturing tab should be enabled for the part.
The IFS Intraday Planning concept allows you to plan manufacturing on the same day as required by a demand. For a part with Plan Manufacturing Supply on Due Date enabled, the manufacturing lead time of the part is rounded down instead of up. When such a part is master scheduled, the demand and planning time fences are shifted one day earlier.
Using the delivery route you can define a Due Time for Delivery, and it is also possible to define a Receipt Time for Arrival. A shop order created from a shop order requisition, DOP order or similar is created with a need date time that equals the last working time on that day. The page names the activity Adjust Shop Orders Need Date to Demand for adjusting the need dates, with times, of the shop orders so that they meet the demands. The definitions of lead time itself are in lead times in IFS Cloud, and the routing calculation in routing lead time calculation in IFS Cloud.
The page lists MRP planned demands among the non-firm items that it can include, so its picture covers more than the firm items when the firm check boxes are cleared. MRP and dynamic structures are explained in dynamic structures and MRP, and the classification of reorder points in reorder point planning. Inventory management that reacts to exceptions is covered in reactive inventory management.
Three decisions need a named owner. Planning decides the horizon, which is not allowed to be greater than 7 days, and whether the firm check boxes are selected or cleared for the daily review. Planning and the warehouse decide who reacts when Negative Projected Qty warns, and whether the reaction is to adjust a quantity or the scheduling of an order. Planning decides which parts have Plan Manufacturing Supply on Due Date enabled. Project connected supplies and demands need another way of review, because the page does not support them.
Test the page with a part that has supply due after demand within one day, and write down the expected projected quantity before opening it.
| Scenario | Expected result | Owner |
|---|---|---|
| Purchase order line due after a customer order line on the same day, both with times other than 00:00 | The expanded record shows projected stock going negative between the two times; Negative Projected Qty warns | Planner |
| Horizon set to 1 | Supplies and demands with a due date today and tomorrow | Planner |
| Horizon set above 7 | Not allowed | Planner |
| Include Only Firm Supplies and Include Only Firm Demands selected, then cleared | Non-firm items such as MRP planned demands and purchase requisition lines appear only when the boxes are cleared | Planner |
| Include Usable Qty in Balance selected, then cleared | The start quantity of the projection is the usable quantity, then 0 | Planner |
| Same-day manufacturing with the part setting cleared, then enabled | Record the planned timing in each case; the page says the setting should be enabled | Planner |
| Order adjusted with the page commands | Projected quantity re-checked after the adjustment; record whether it still goes negative | Warehouse lead |
The intraday review is ready for go-live when each check below has a record behind it.
The IFS Cloud intraday availability analysis shows the short-term supply and demand situation for inventory parts, considering also the timings within the day down to minute level, on the Inventory Parts Intraday Availability page. The main list shows one record per site, inventory part and configuration.
The horizon of the IFS Cloud intraday analysis is not allowed to be greater than 7 days. A value of 1 shows supplies and demands with a due date today and tomorrow.
In the IFS Cloud intraday analysis, firm supplies and demands are customer order lines, shop order materials, purchase order lines and shop orders. Non-firm items are MRP planned demands, MS unconsumed forecasts, shop order requisitions and purchase requisition lines, and they are considered only when the Include Only Firm Supplies and Include Only Firm Demands check boxes are cleared.
The Negative Projected Qty field on the IFS Cloud intraday availability page gives a heads-up if the projected development within the period goes negative at any point, also considering the time within the day. The user can then adjust the quantities and/or scheduling of the orders to avoid negative stock developments.
The IFS Cloud intraday availability page does not support planning of project connected supplies and demands.
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.
A review of the short-term planning set-up and of how your planners use the intraday page shows which setting hides the timing.
Independent IFS Cloud practice · Order promising design
Master Scheduling Available to Promise (ATP) is a promising method in IFS Cloud that uses the master schedule (MPS) as the data source for customer order promising. A promise date from this method is only as sound as the set-up behind it: which parts are master scheduled, whether online consumption is enabled, and whether quantities are allocated to customers or markets. If nobody chose these settings, the dates given to customers do not follow from a plan the business understands. This article follows the IFS documentation page on Master Scheduling Available to Promise, which has identical text in the 25R2 and 26R1 trees.
Key takeaways
Available to Promise uses the master schedule (MPS) as data source for customer order promising, hence the parts must be master scheduled.
The page describes two principles for the availability evaluation. One works against unconsumed forecast. The other, against unconsumed supply, looks at actual existing supplies and at how much of them can be promised after existing demands have been deducted. The page adds that within the planning time fence there can be a significant difference to unconsumed forecast.
The page lists three order promising tools: Availability Check, Capability Check and Available to Promise. It is not recommended to use more than one order promising tool for the same part at the same time. Order promising from the plan is covered in high-fidelity discrete order promising in IFS Cloud, and capable-to-promise in CTP in IFS Cloud.
To use this promising method, Online Consumption on Inventory Part must also be enabled. The page lists the events that count in online consumption:
For sales quotation lines, the Release for Planning option must be enabled on the sales quotation line.
The generic check tests whether the part is available at all on a certain date. In addition to it, another check can be performed to see whether the part is available according to the allocated quantity for an entity of a customer dimension.
A customer dimension could be customer, customer stat group, market, region, district or country. The period could be week or month. The business decides for each part whether it is promised against the generic check only or also against an allocation, and for which dimension and period.
The page names the settings in the table below, with the definition or condition it gives for each and its possible values.
| Setting | What the page says | Values |
|---|---|---|
| Promise Method | Defines if available quantity is evaluated against unconsumed supply or unconsumed forecast | Unconsumed Forecast; Available to Promise (Unconsumed Supply) |
| Forecast By | Defines if ATP should also cover customer dimension based availability and which dimension is used for aggregation per time period | Part, Customer, Customer Stat Group, Region, Market, District, Country |
| Unallocated Supply Distribution | When Forecast By is not Part, controls how the allocation of non-specifically defined customer dimensions will be allowed to use | Free, Restricted |
| ATP Allocation Period Unit | The period unit of the allocation | Month, Week |
| ATP Allocation Method | Method of the allocation | First Come First Served, Forecast Ratio, User Defined Ratio, Fixed Quantity Limit |
The settings list of the page says Promise Method, and a later passage says Promised Method in the MS Level 1 Part page. Treat both as the same setting and check the label in your release.
With the promise method Available to Promise, you can only enter or change a Customer Order or Quotation Line if the sum of the stock on hand plus open supply, that is the total supply, exceeds the demand quantity. The condition applies to that method only, and the page ties it to the planning time fence (PTF).
The two methods behave as follows relative to the PTF and the demand time fence (DTF), in the words of the page.
| Promise method | Planning time fence (PTF) | Demand time fence (DTF) |
|---|---|---|
| Available to Promise | Wanted receipt date inside the PTF: error message. Beyond the PTF: an information message, and the record can be saved | You are not restricted by the DTF |
| Unconsumed Forecast | The check goes for the entire horizon, also outside the PTF | You are restricted by the DTF |
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, and a demand time fence of 0 means that no demand time fence applies.
The IFS page on time fences states that the planning time fence is calculated with the critical path method, and that the values are calculated using the manufacturing calendar for manufactured parts and the distribution calendar for purchased parts. The lead time definitions behind a promise date are covered in lead times in IFS Cloud for purchased and manufactured parts, and the planning run that feeds the schedule in dynamic structures and MRP.
Three decisions need a named owner. Planning decides which parts are master scheduled and which single promising tool each part uses. Planning and sales together decide whether a part is promised against the generic check only or also against an allocation, and for which customer dimension and period. Sales decides what a customer service agent does when the system returns an error or an information message on a line. The order flow that surrounds the promise is described in customer order types in IFS Cloud. Reservation of stock for the line is a separate mechanism with its own rules, described in reservation rules in IFS Cloud.
Test promising with scenarios that cover each condition the page names, and write down the expected result before each one.
| Scenario | Expected result | Owner |
|---|---|---|
| Part that is not master scheduled | Record the result; the page requires master scheduled parts | Planner |
| Online Consumption disabled on the inventory part | Record the result; the page requires it for this method | Planner |
| Available to Promise, wanted receipt date inside the PTF, total supply not above demand | Error message | Sales |
| Available to Promise, wanted receipt date beyond the PTF | Information message; the record can be saved | Sales |
| Unconsumed Forecast, line inside the DTF | Restricted by the DTF | Sales |
| Forecast By set to a customer dimension, one entity | Availability is evaluated against the quantity allocated to that entity | Planner and sales |
| Increase, decrease and cancel an existing line | Each event is listed on the page as online consumption; record the consumed quantity before and after | Planner |
The promising set-up is ready for go-live when each check below has a record behind it.
Available to Promise in IFS Cloud Master Scheduling is a promising method that uses the master schedule (MPS) as data source for customer order promising. Online Consumption on Inventory Part must be enabled to use it.
Only master scheduled parts can be promised with Available to Promise in IFS Cloud, because the method uses the master schedule (MPS) as data source. The documentation does not recommend using more than one order promising tool for the same part at the same time.
The generic check in IFS Cloud Available to Promise tests whether a part is available at all on a certain date. The customer-dimension check is an additional test of whether the part is available according to the allocated quantity for an entity of a customer dimension, for example one customer or one market.
An ATP allocation in IFS Cloud can use customer, customer stat group, market, region, district or country as customer dimension, and the period can be week or month. The dimension is selected with the Forecast By setting, whose values are Part, Customer, Customer Stat Group, Region, Market, District and Country.
Online Consumption on Inventory Part must be enabled to use Available to Promise in IFS Cloud. Online consumption is triggered by entering a new line, increasing or decreasing the quantity of an existing line, changing data that affects the due date, and cancelling a line.
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.
A review of the promising set-up against your planning method shows which settings were chosen and which were left as they came.