Inventory, Allocation and Logistics
Stock Structure, Bin and Ownership Setup
Defining where stock lives and who owns it. FSM 6 holds stock at a place and location, in bins, with condition and ownership, and every part movement in the product resolves to that structure.
Part Need Allocation and Backorder
Matching demand for parts to available stock, and deciding what to do when there is none. FSM 6 allocates against part needs, sources from the location the delivered rules select, and queues unfilled demand as backorder.
Replenishment and Refill Planning
Keeping stocking points supplied without overstocking them. FSM 6 refills from minimum and maximum levels, chooses a supplier by rule, and generates the transfers or purchase orders needed.
Shipment, Pick and Bill of Lading
Moving material out: picking it, packing it into handling units, raising the paperwork and dispatching it. FSM 6 groups shipments by rule and produces a bill of lading for the carrier.
Receiving and Put Away
Taking material in and getting it to the right bin. FSM 6 matches receipts against pending receipts, sets condition by rule, and generates the putaway that moves the material to its storage location.
Stock Count, Exception and Accuracy Control
Checking that the stock records match reality and correcting them when they do not. FSM 6 ships stock counting with an exception screen, and count discipline is what makes allocation trustworthy.
Requisition and Purchase Order Management
Buying what the network does not have. FSM 6 raises requisitions, converts them to purchase orders, tracks them through events and escalations, and receives against them.
Part Substitution, Alternates and Kits
Handling the fact that the part on the order is not always the part in the box. FSM 6 supports alternates with three delivered exception rules for receiving, shipping and stock, and kits for parts that are issued as a set.
Stock Analysis and Level Recommendation
Working out from history what should be stocked and where. FSM 6 ships stock analysis with ABC classification and usage views that produce minimum and maximum recommendations.
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