SimWell built a unified optimization model in anyLogistix that integrated cutting constraints directly into the supply chain network, connecting sourcing, production allocation, customer assignment, and distribution decisions with the physical reality of what each facility could actually produce. Cutting logic was not added as a downstream check. It was embedded as a core constraint within the network optimization itself, so that every recommendation the model produced had already been validated against real machine capabilities and real material physics.
The technical foundation required generating thousands of feasible cutting combinations per facility, based on each plant's machine specifications. Consider a single parent roll: depending on the machine it runs on, it can be cut into dozens of different width combinations, each yielding a mix of primary product, usable by-products, and a waste fraction. SimWell modeled every combination as a bill of materials, assigned full cost to the parent roll, and penalized waste as consumed raw material with no matching demand. For the first time, trim loss became visible to the network optimizer as a real cost that varies with every allocation decision.
This changed which answers the model produced. A plant might accept slightly higher waste on one order if doing so freed capacity for a higher-margin product elsewhere in the network. Another plant might take on orders it would never have received under proximity-based logic because its machine configuration made it the lowest-waste producer for that particular width. A third facility might be revealed as structurally unprofitable once cutting losses were accounted for. Information that proximity and capacity models had never surfaced.
It also changed how planning decisions were made. Before the model, production allocation was driven by capacity and geography, then validated informally against what operators knew they could run. With cutting embedded in the optimization, the planning team could evaluate scenarios (a facility shutdown, a shift in customer mix, a demand surge in a specific product width) and know that every answer the model returned was executable. The conversation shifted from “can we do this?” to “which option is most profitable?”
The entire pipeline was designed for permanence. ERP data feeds automatically into the optimization engine, flows through post-processing, and surfaces in dashboards that production planners use directly. The model runs on a regular cadence, integrated with the client's forecasting and planning cycle. It does not require a dedicated analytics team to operate. As demand shifts, capacity changes, or customer portfolios evolve, the optimization updates with them.