Skip to main contentSkip to footer

IFS Cloud Project Governance: Five Questions to Answer

Five questions every IFS Cloud steering group asks, where the answers should come from, and how a register-based tool such as Implementer helps.

Independent IFS Cloud practice · Project governance Five questions a steering group asks, and where the answers should come from Key takeaways Every IFS Cloud steering group asks the same five questions about versions, approvals, readiness, updates and evidence. If the answer to one of them takes an afternoon, the…

Read more

Time Fences in IFS Cloud: Demand and Planning Time Fence

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.

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…

Read more

Master Production Schedule Level 1 in IFS Cloud Explained

How Master Production Schedule Level 1 works in IFS Cloud: Level 0 and Level 1 parts, the proposals it creates, dependent demand and time fences.

Independent IFS Cloud practice · Master scheduling design Describe the Level 0 and Level 1 structure before planners read the proposals 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…

Read more

IFS Cloud Intraday Availability: Supply and Demand Timing

How IFS Cloud analyses short-term supply and demand down to the minute: the horizon, firm or non-firm items, balance fields and projected quantity.

Independent IFS Cloud practice · Short-term planning Check projected stock down to the minute for the next days 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…

Read more

Master Scheduling ATP in IFS Cloud: How Promising Works

How Master Scheduling Available to Promise works in IFS Cloud: the master schedule as data source, generic and customer-dimension checks, and set-up.

Independent IFS Cloud practice · Order promising design Decide what the master schedule promises before customer orders depend on it 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…

Read more

IFS Cloud Material Requisition: Statuses, Reserve, Issue

How IFS Cloud material requisition works for internal demand: statuses, reservation before issue, partial issue and closing a line.

Independent IFS Cloud practice · Internal demand design Decide who reserves, who issues and who closes before requisitions pile up An IFS Cloud material requisition is the document through which material is requested for internal demand, and it runs through its own flow: request, reservation, issue and closure. If the…

Read more

IFS Cloud Routing Lead Time: Fixed, Variable and Overlap

How IFS Cloud routing lead time is calculated: fixed and variable time, standard lot size, parallel operations and overlap, with worked examples.

Independent IFS Cloud practice · Manufacturing planning design Check your routing data against the calculation that produces the planned lead time IFS Cloud routing lead time is the lead time of a manufactured part calculated from its routing, and the page states that MRP and Master Scheduling use it. If the…

Read more

IFS Cloud Email Customer Documents: Set-Up Rules

IFS Cloud email customer documents: how the contact is found, what each of invoice, quotation and order confirmation needs, and the invoice lock.

Independent IFS Cloud practice · Sales output design Check the contact, the document and the event before customers say they never got the invoice To make IFS Cloud email customer documents reach customers, each document needs its own set-up: an invoice, a quotation and an order confirmation each have their own page…

Read more

IFS Cloud Lead Time: Purchase, Manufacturing and Expected

IFS Cloud lead time: how purchase, manufacturing and expected lead time are defined, where each is calculated and which one MRP reads.

Independent IFS Cloud practice · Planning data design Know which lead time a function reads before you fill the fields IFS Cloud lead time lives in several fields, and each field has its own meaning. If purchase, manufacturing and expected lead time are filled without knowing which one a function reads, planned dates…

Read more
Abstract illustration on a navy background with the article title: “IFS Cloud Site Clusters: Setup, Usage, and Business Impact”

Introduction

In IFS Cloud, a site cluster is a business structure that groups multiple sites under one administrative umbrella. It simplifies mass creation of inventory parts, ensures consistent defaults across sites, and accelerates multi-site rollouts. Unlike a technical Kubernetes cluster, which manages servers and infrastructure, the site cluster exists for business process efficiency.


What Is a Site Cluster?

A site cluster provides a hierarchical grouping of sites. Nodes represent regions, countries, or divisions. Each node can hold several sites, and cluster-level defaults cascade down to individual sites.

Key benefits:

  • Mass creation of parts across multiple sites

  • Standardization of sourcing, sales, and purchasing defaults

  • Faster onboarding of new sites and acquisitions

  • Reduced manual setup errors


How to Use Site Clusters

Practical applications include:

  • Mass part creation: Define an assortment once and replicate it across all sites in the cluster.

  • Administrative control: Defaults defined at cluster level are inherited by connected sites.

  • Process automation: Streamline procurement, distribution, and warehousing setups across regions.

  • Governance: Reduce risk of fragmentation by enforcing consistent part master data.


How to Configure a Site Cluster

1. Create the Cluster Structure

  • Navigate to Site Cluster in IFS Cloud.

  • Define the root node (e.g. “Europe Operations”).

2. Add Levels and Nodes

  • Add levels to reflect hierarchy (Region → Country → Site).

  • Each node inherits settings from its parent.

3. Connect Sites

IFS Cloud Documentation

  • Connect existing sites via Query Sites or manual entry.

  • Note: Sites must already exist; clusters cannot create them.

4. Link Assortments

Site Cluster _ IFS Community

  • Ensure an assortment structure is active and connected to the part catalog.

  • Parts in the assortment will be created across all connected sites.

5. Apply Defaults

  • Set supplier links, sourcing rules, and sales/​purchase part flags in the assortment.

  • Defaults cascade automatically.

6. Validate Permissions

  • Confirm sites are “user-allowed” for the operator running the process.

7. Run Mass Part Creation

  • Open Parts by Assortment and Site Cluster.

  • Select cluster and assortment, then run creation.

Automatic checks include:

  • Sales parts only created if the Do Not Create Sales Part flag is cleared.

  • Purchase parts created only for non-manufactured parts.

  • Supplier parts created if allowed by the flags.


Business Impact

Implementing site clusters delivers measurable value:

  • Speed: Shortens rollout cycles for new sites.

  • Consistency: Standardized part data across the enterprise.

  • Compliance: Enforced defaults for sourcing and supplier rules.

  • Cost savings: Fewer manual errors, less rework, and faster master data setup.


Example Hierarchy

A manufacturer opens new sites in Europe.

Cluster structure:

Site Cluster Schema

When the “Standard Bearings” assortment is applied to “Europe Operations,” all three plants receive identical part numbers, suppliers, and defaults at once.


Visual Guides

Diagram 1: Site Cluster Hierarchy

Site Cluster Hierarchy

Diagram 2: Mass Part Creation Flow

Mass Part Creation Flow


Rollout Checklist

Pre-flight

  • Confirm part catalog and assortment are active

  • Define cluster naming standards

  • Confirm sites and user access

Build the Cluster

  • Create cluster root and levels

  • Add nodes for regions/​countries

  • Connect sites to nodes

Defaults and Rules

  • Apply supplier and sourcing defaults

  • Set sales/​purchase part flags

  • Record defaults in change log

Mass Creation Run

  • Test run first, review logs

  • Fix errors, rerun in production

  • Monitor execution results

Governance

  • Assign business and data owners

  • Weekly drift detection

  • Periodic audit of created parts

Validation After Go Live

  • Verify part attributes in sample sites

  • Check supplier links and pricing

  • Confirm warehouse and planning defaults

Rollback

  • Export created part IDs per site

  • Maintain rollback scripts

  • Keep backup references


Quick Reference for Training

Roles

  • Data steward runs assistants

  • Business lead approves defaults

  • IT monitors logs

KPIs

  • Time to enable a new site

  • Error rate during mass creation

  • Number of mismatched attributes found in audits


Conclusion

The site cluster is more than a configuration tool. It’s a strategic enabler that helps enterprises scale faster, enforce consistency, and govern master data effectively. Used properly, it turns what used to be tedious, error-prone setup work into a streamlined, controlled process that grows with the business.

×
Need Expert Guidance?
We've helped hundreds of businesses succeed. Get a free consultation to discuss your project requirements.
Get Free Consultation
17Years Experience
50Implementations
PRINCE2Certified
100%Success Rate

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.