Supply Chain · S2

Supply Chain Planning

7
Processes
302
Details worked out
43
Execution steps
7
Diagrams
S2.01

Supply Chain Master Data & Network Modeling

Establishes the master data and network topology that underpins supply chain planning in IFS Cloud: multi-site part connections, supplier-for-purchase-part links, sourcing rules, and supply chain parameter matrices (site-to-site, site-to-customer, supplier-to-site) that define lead times, distances and delivery modes across the network.

IFS Supply Chain Management
39 details
diagram
S2.02

Multi-Site Planning

Plans a network of sites together as an internal supply chain. Multi-site planned parts are planned simultaneously across all sites in a planning network; requirements pass to internal supplier sites and are executed via distribution orders, expanding single-site BOM planning with multi-site part structures.

IFS Supply Chain Management
39 details
diagram
S2.03

Available-to-Promise / Capable-to-Promise (ATP/CTP)

Order-promising capability determining whether and when a customer order or quotation line can be fulfilled. IFS Cloud offers three tools: Availability Check (plannable qty within lead time), Capability Check (multilevel material and capacity check, also for configured/MTO, i.e. CTP), and Available to Promise (uses the master schedule with online forecast consumption).

IFS Supply Chain Management
42 details
diagram
S2.04

Supply & Distribution Planning

Turns forecasts and actual demand into time-phased supply and distribution plans. Master Scheduling converts forecasts into MS proposals (becoming shop order or purchase proposals per time fences), MRP explodes dependent demand, and internal distribution is executed via distribution orders; make-to-order demand is handled through Dynamic Order Processing (DOP).

IFS Supply Chain Management
41 details
diagram
S2.AM65

Last-Time-Buy Planning

Plans and executes the final purchase of a component or service part that a supplier is discontinuing, so that a manufacturer can honour its aftermarket support commitments for the remaining life of the installed base. The process converts an end-of-life or product change notice into a quantified remaining demand estimate, evaluates the alternatives to buying (alternate part, redesign, brokered supply), and releases the LTB Purchase Order before the supplier last order date. In IFS Cloud the sized quantity is held as Inventory Part stock with a restricted issue policy and the burn-down is monitored against the support horizon.

ProcurementManufacturing Aftermarket
49 details
diagram
S2.R67

Parts Planning & OEM Procurement

Decides what spare parts to hold, where, and in what quantity, then converts that plan into Purchase Requisitions and consolidated Purchase Orders on OEM and aftermarket suppliers. Planning parameters are set against the OEM actual delivery performance rather than quoted lead times, because spare parts supply reliability is a documented pain point across the equipment rental industry. The period inventory health review - obsolescence, surplus and branch imbalance - closes the loop and protects working capital.

ProcurementEquipment Dealers & Rental
46 details
diagram
S2.T21

Rollout Material Planning & Site Kitting

Plans and stages the physical materials needed for each network rollout site - radios, antennas, fibre, cabinets, cabling and consumables - so that build crews mobilise with a complete, verified kit. In IFS Cloud the site is modelled as a Project with a WBS of Project Activities; material demand is netted against Inventory Part stock, covered by Purchase Orders or sub-contract orders, then picked, kitted and issued to the site. The process removes the single largest cause of failed builds - missing material on the day - and gives programme controllers one view of committed rollout material cost.

Project ManagementTelecommunications
46 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it