Integrations / ERP / IFS Cloud
Does IFS Cloud Have Finite Capacity Scheduling? Shop Order Scheduling, MSO and SkyPlanner APS
IFS Cloud schedules shop orders and Capacity Requirements Planning (CRP) against infinite capacity. Finite scheduling exists, but as a separate capability: Manufacturing Scheduling and Optimization (MSO) on the IFS PSO engine, or the older Advanced Planning Board (APB). Plants that want every constraint scheduled finitely without adding MSO run SkyPlanner APS beside IFS Cloud.
How IFS Cloud plans capacity, step by step
1. Work centers and resources
Capacity lives on the Work Center and its Work Center Resources, a machine or a physical location. Each work center carries a Calendar, Utilization, Efficiency and Validity Periods. A field called Scheduling Capacity is set to Finite or Infinite.
Capacity is calculated with the Calculate Work Center Resource Capacity dialog. People are modeled as Labor Classes with labor class persons. Tools are Manufacturing Tools with tool instances and tool groups. (source)
2. Product structures and routings
The bill of material is the Product Structure, with a structure header, structure alternates and structure lines. The Routing has routing alternates and Routing Operations. IFS: “All time information entered for operations (such as setup time, move time, and efficiency) affects operation scheduling.” (source)
3. MRP, CRP and shop orders
MRP and master scheduling create planned Shop Orders. A shop order moves through statuses such as Planned, Released, Reserved, Started and Closed. Each Shop Order Operation holds machine and labor setup and run times, labor crew size, a Preferred Resource, operation overlap and operation blocks.
CRP shows the load these orders put on work centers. It does not limit it. IFS is explicit: “Operations scheduled with CRP and shop order are always scheduled infinite.” (source)
4. The shop order Infinite Scheduler
The Infinite Scheduler dates every operation. It works with the work center calendar, utilization, operation and resource efficiency, queue and transport time, overlap, parallel operations and the Preferred Resource. It schedules forward or backward and picks “the least loaded resource for the work center.”
It “always treats each shop order as if it is the only one in the system, with few constraints on resources and capacity.” (source) Two shop orders can land on the same machine at the same hour.
5. Finite option one: MSO and the Smart Manufacturing Planning Board
MSO “is a solution designed to generate finite production schedules by optimizing the use of manufacturing resource constraints.” It “leverages the IFS PSO (Planning, Scheduling, and Optimization) engine.” (source) It treats work centers, labor classes and tools as scheduling constraints, and it schedules an operation only when the required material quantity is available. It also considers part-specific setup times, shop order priorities, resource calendars and maintenance work. In Automatic mode it reschedules whenever required, for example when a new shop order is created.
Setup in brief:
| Setting | What it does |
|---|---|
| Finite Scheduling Basic Data | Enables the site; “the dataset must be activated” |
| Mode | Manual or Automatic scheduling |
| Time Horizon (Days), Scheduling Start Time | The window MSO schedules |
| Use Setup Matrices for Scheduling | Part-specific setup times |
| Exempt Labor, Exempt Tools, Exempt Shop Order Types | Constraints MSO ignores |
| MSO Advanced Parameters | A standard template with validated defaults; changes “For modification by PSO/MSO SMEs only” |
On the shop order, Need Date sets the tardiness target, Earliest Start Date is “a hard time constraint”, and Priority Category feeds the MSO priority score. Planners work in the Smart Manufacturing Planning Board, with Resources and Operations Gantt pages, drag and drop, operation split and selective optimization. (source)
6. Finite option two: the Advanced Planning Board
The APB, familiar from IFS Applications 10, uses Constraint Based Scheduling (CBS). It “allows you to perform finite scheduling of shop orders on sites that have enabled the use of the APB in scheduling basic data.” (source)
What stays with the planner
- Infinite by default. Shop order scheduling and CRP never check capacity across orders. Finite needs MSO or APB set up separately (AboutWorkCenter).
- MSO needs separate access. It “is available for customers with access to Manufacturing Scheduling and Optimization.” Hybrid or hosted sites need an IFS.ai Activation Pass. Cloud sites need “PSO sizing and purchase of PSO Cloud Service” (26R2 MSO).
- On IFS.ai platform services, MSO is manual and metered. “Automatic scheduling mode is not available for users on the IFS.ai-based platform services.” Users “must have a number of dedicated tokens on hand to do a finite schedule or to do a simulation in MSO” (26R1 MSO). Automatic mode is not available on hybrid or hosted sites that use an IFS.ai Activation Pass (26R2 MSO).
- Advanced parameters are for specialists. IFS ships a standard template and strongly advises keeping its defaults. Changes are reserved for PSO and MSO subject matter experts.
- Documented MSO limits. “MSO schedules the first operation on a work center using a setup matrix without a setup time.” “Parallel shop order operations are not considered for optimization in a compressed manner.” With Exempt Labor, “operations that have only labor time and no machine time will remain untouched.”
- Short horizon. IFS positions MSO for detailed short-term scheduling and points to CRP, MRP and master scheduling for longer horizons.
- The APB plans only what is loaded. It “only considers the constraints placed by shop orders and resources that are actually loaded to the APB at a given time.”
In practice, plants on standard scheduling live with overlapping operations, manual resequencing and a shadow plan in Excel exported from IFS.
When IFS Cloud’s native scheduling is enough
Standard shop order scheduling plus CRP does the job when:
- The shop has spare capacity and real bottlenecks are rare.
- Routings are short and stable, and you plan weekly.
- A supervisor sets the sequence at the machine.
- Shared tools, crews and material arrival do not decide the order of work.
MSO fits a site that buys MSO access and its PSO or IFS.ai deployment, and schedules a short-term horizon inside IFS.
When you need a finite capacity scheduler
You have outgrown standard scheduling when several of these are true:
- Promised dates slip even though CRP looked fine.
- Changeover time depends on which product ran before.
- People, shifts and absences limit the plan as much as machines do.
- Molds, dies or fixtures are shared between machines.
- Material availability decides which shop order can start.
- Rush orders and breakdowns force a replan several times a week.
What to look for
- All resources finite at once, not a subset loaded into a board.
- A setting time matrix: sequence-dependent, asymmetric changeover times between products, used to minimize total setup.
- Tools as finite shared resources, so one mold is never on two machines at once.
- Multi-operator jobs: a job needing several people gets them, each with their own shift.
- Material-aware scheduling that checks stock and incoming purchase orders.
- Automatic rescheduling when production progress or orders change, with no token budget per run.
- A clean write-back to IFS through IFS’s own OData projections, with clear ownership of operation dates.
The options fall into four groups:
- IFS Cloud standard scheduling dates shop orders infinitely inside IFS.
- IFS MSO schedules machines, labor, tools and material finitely, as a separately accessed module on the PSO engine.
- Enterprise APS suites are connected through an implementation project and run by a planning team.
- Cloud APS with shop-floor execution, where SkyPlanner sits, schedules every resource automatically beside IFS Cloud and puts the schedule in operators’ hands.
Where SkyPlanner fits
SkyPlanner APS fills these gaps. Every workstation is finite, and all shop orders compete for the same capacity. The Arcturus AI engine builds the operation-level schedule in seconds and sequences it by your priorities and due dates.
Its setting time matrix holds the changeover time between each pair of products in both directions, and the engine picks the order with the least setup. Tools are finite shared resources, and a job can need several operators at once. When a machine or person is unavailable, the engine moves the work to the alternatives you define.
Material-driven scheduling simulates future inventory from stock and incoming purchase orders, so work is planned only when material is there. Running Time Lock keeps running jobs in place.
Autopilot reschedules automatically when production changes, within your locks and priorities. Planners adjust jobs on an interactive Gantt timeline, and operators log work on phone or tablet with Mobile Confirmations.
Choose SkyPlanner over IFS MSO when you are moving off spreadsheets and want a finite schedule that runs itself:
- Shop orders overlap on shared machines and CRP only shows the overload after the fact.
- Changeovers, shared tools or multi-operator jobs decide what can run next.
- The plan must replan on every change. Autopilot does it automatically, with no token budget per run and no manual-mode restriction.
- Sales needs finite dates months ahead, beyond MSO’s short-term focus.
- You want every constraint in one engine at a published price, without adding MSO access, a PSO Cloud Service or an IFS.ai Activation Pass, and without parameters reserved for PSO specialists.
You see your own shop orders scheduled finitely within the trial and go live within weeks after onboarding starts.
Start with an Excel export of your shop orders in the 30-day free trial (up to 20 workstations, no credit card). Pricing is from 199 € per month with 5 workstations included, billed monthly. The integration is quoted up front for your process and needs, so you see the full cost before you start.
SkyPlanner integrates with IFS Cloud in both directions over IFS’s OData projections. The SkyPlanner team configures it during onboarding and supports it after go-live. See the SkyPlanner for IFS Cloud page, the IFS Cloud integration guide, or other systems in the ERP integrations hub.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
98%delivery reliability, up from about 50%
“SkyPlanner plays a decisive role in maintaining our delivery reliability.”
Hannu Lahtinen, Managing Director
KJH-Comp · Sheet-metal mechanics and contract manufacturing
Delivery reliability rose from around 50% to as high as 98%, and scheduling now needs one supervisor instead of two.
100%delivery reliability since 2021
“SkyPlanner gives us visibility into capacity and makes planning predictable.”
Dan Berglund, COO/CFO
Opes Corporation · Chemical and food manufacturing
Delivery reliability has been 100% for the entire time SkyPlanner has been in use, since 2021.
FAQ
What is the difference between IFS MSO and PSO?
PSO (Planning and Scheduling Optimization) is IFS’s scheduling engine, also sold for field service scheduling. MSO (Manufacturing Scheduling and Optimization) is the manufacturing scheduler that runs on the PSO engine. In 26R2 docs it is called IFS.ai Manufacturing Scheduling and Optimization.
Is MSO included in IFS Cloud?
IFS documents MSO as available to customers with access to it. Deployment needs an IFS.ai Activation Pass on hybrid or hosted sites, or PSO sizing and a PSO Cloud Service purchase in the cloud. On IFS.ai platform services, MSO runs in manual mode and consumes tokens.
Can IFS Cloud schedule labor and tools finitely?
In MSO, yes: it treats work centers, labor classes and tools as scheduling constraints, unless Exempt Labor or Exempt Tools is set. Standard shop order scheduling does not limit labor classes or tools across orders. SkyPlanner schedules people, shifts, absences and shared tools finitely on every run.
Does IFS Cloud handle sequence-dependent setup times?
MSO can, through setup matrices, although it schedules the first operation on a work center without a setup time. Standard scheduling uses the setup time on the routing operation. SkyPlanner’s setting time matrix stores changeovers between product pairs, such as blue to red 30 minutes and red to blue 60.
Can I test SkyPlanner before integrating it with IFS Cloud?
Yes. Export open shop orders, operations and work centers from IFS Cloud to Excel, import them during the 30-day trial and compare the schedule with your current plan. See pricing, start the trial or talk to sales.
