Planning that answers what if, and shows its working

Graph-based planning

Demand, supply, bills, routings, vendors and sites are one connected graph. A recommendation is pegged to its demand, a shortage is followed to its cause, and a change at one node ripples to every order it touches.

Pegging on every row

Trace any recommendation to the sales order, forecast bucket or work order that caused it, and any demand to the supply that covers it.

A time-phased drawer

Open a row to see the item at that site: projected balance by period, supply and demand against it, consumption of the forecast, and a timeline of what arrives when.

Part substitutes

A short component does not stall the build. The engine takes the approved substitute on the bill, and the plan says which part it used and why.

Firm means firm

A firm purchase order nets on its own date and is never put up to move, reduce or cancel. A shortage it leaves gets a new planned order, and a firm order past its date is still reported past due.

One request, one transaction

Every studio gesture is one request that carries the fresh rows back, and a bulk release is one transaction: every order exists afterwards, or none does.