# What Is a Planning Cluster in Infor LN? > Source: https://netray.co/erp-help/infor-ln-planning-cluster-explained > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In Infor LN Enterprise Planning, a cluster groups planning entities, such as plants or warehouses, so that planning can be run, viewed and controlled as one unit. It is a structural setting that determines what is planned together, which is why a wrong cluster setup produces missing or surprising planned orders. ## Kind how-to ## System infor-ln ## Erp Infor LN ## Module Enterprise Planning ## Query infor ln planning cluster ## Alternate Queries - what is a planning cluster in infor ln - infor ln service resource planning session - infor ln enterprise planning cluster setup ## Applies To Infor LN 10.x with Enterprise Planning. Session names and some terms vary by version and by whether Service planning is also in use. ## Steps ### Set up and verify a planning cluster **Items:** - Decide the planning scope: which plants, warehouses and items should be planned together and which independently. - Define the cluster in Enterprise Planning master data and assign the planning units to it. - Check items are assigned to planning in that cluster, with the right planning parameters such as order policy and lead times. - Define supply and demand relationships between entities, for example which plant supplies which warehouse. - Run a planning pass for a small item set and review planned orders, messages and exceptions. - Compare results with expectations. If demand in one entity is not covered, check whether it belongs to the cluster and its supply relationships. - Roll the setup out to the rest of the items, with a planner review of the first full run. ## Sections ### What a cluster is for **Body:** Planning needs a boundary. Without one, a single plan could span your entire company, and you could not run or schedule parts of it independently. A cluster is that boundary: it defines the set of entities whose supply and demand are netted and planned in one run. Bigger clusters give a more global optimum but longer runs and more cross-site dependency. Smaller clusters run faster and isolate problems but require explicit transfers between them. ### Cluster design choices **Body:** Group by how material really moves. Plants that share components and exchange goods belong together. Sites that operate as separate businesses with arm's-length supply often do not. Also consider who owns the plan: one planner team per cluster is easier to run than shared ownership. Review the cluster design whenever you open a warehouse, change a sourcing route or merge businesses. ### Service resource planning **Body:** Searches for an LN service resource planning session relate to planning service work, such as technicians and equipment, against service orders and calendars. It is a separate planning area from item planning, with its own resources and horizons, though it may use shared calendar and organisation data. Use the Service module documentation for your version to find the exact sessions. Do not assume item-planning cluster settings apply to service resources. **Code:** Planning sanity checklist - Every demand entity is in a cluster - Every item has planning data in that cluster - Supply relationships defined for cross-entity sourcing - Calendars and lead times present - First run reviewed by a planner ## Pitfalls - Leaving a warehouse outside any cluster, so its demand is never planned. - One giant cluster that makes every planning run slow and fragile. - Missing supply relationships between plants, producing unmet demand messages. - Changing cluster membership with open planned orders and not re-running the plan. - Confusing item planning clusters with service resource planning. ## Ai Angle Planners lose time asking why an item was or was not planned. A private assistant over your LN planning data can explain, read-only, which cluster the item sits in, what demand and supply it saw and why no order was proposed, with all data staying on your servers. Planners keep decision authority. ## Faq ### What is a planning cluster in Infor LN? **Answer:** It is a grouping of planning entities in Enterprise Planning, such as plants and warehouses, that are planned together in one run. It sets the boundary within which supply and demand are netted. ### How do I create a planning cluster? **Answer:** Define the cluster in Enterprise Planning master data, assign planning units to it, set item planning data and supply relationships, then run a limited planning pass to verify. Check session names against your LN version. ### Why is my demand not planned in LN? **Answer:** Check that the demanding entity belongs to a cluster, the item has planning data there and supply relationships exist for sourcing. Missing membership is a frequent cause. ### Is service resource planning the same as item planning? **Answer:** No. Service resource planning schedules technicians and equipment for service work, while item planning nets supply and demand for materials. They are separate areas with different settings. ## Search terms infor ln planning cluster, infor ln enterprise planning, infor ln planning unit, infor ln service resource planning, ln cluster definition, infor ln mrp cluster, infor ln supply relationship, baan enterprise planning --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json