What works today, and what comes next.

See it: Network cockpit in the demo, running the deterministic planning engine on a six-plant network. A plant with late orders also shows its load by production day, with the backlog carried forward, which explains how a plant under 100% on the 10-day average still has orders late (display only).

Today: Runs on one fixed demo snapshot. Load is a total over 10 production days; each move’s due date is checked by replaying the receiving plant’s run sequence day by day, but there is no full finite-capacity schedule yet. It never moves an order onto a machine shown down, but load and timing still count a down machine as running (the cockpit flags it), and recorded production is not reflected in timing. Conversion rates per operation, customer plant approvals, the die and plate transfer cost and the value of a late order-day are draft demo assumptions. Make-ready cost, interplant sheet supply, board grade checks, overtime and outsourcing are not modelled in the balancer yet, and it does not see a plant’s frozen window. Lane transit times are a draft from road miles and shipment size, and the balancer prices a less-than-truckload order at the truckload freight rate, so its freight is understated.

See it: Methods links on every screen of the hosted demo, "How calculated" panels in the network cockpit, and the run summary above the proposed moves.

Today: Domain rules are drafts until validated by a plant subject-matter expert.

See it: Approve and Reject on each move in the network cockpit, saved as you decide, with a reason required to reject. For roles that see costs, a relief move’s Reject prompt says what keeping the order at its plant would need: no overtime, or a draft overtime range beside the move’s estimated contribution.

Today: Demo tenants only. Overtime rates are drafts, and the effect of overtime on late orders is not modelled.

See it: In the hosted demo, a planner saves a balancing proposal, approves each move or rejects it with a reason, applies it, and re-runs; rejected orders stay held.

Today: Demo tenants only. A change since the run that affects its moves (to a moved order, or new or changed work at a plant a move leaves or goes to) stops Apply until you re-run, and the proposal says why; an order made, shipped or held elsewhere does not. If the book has changed and a move’s overload or late orders are gone, Apply warns that the move may no longer be needed (a warning only). A re-run carries an approval over only where it proposes the same move, and lists the ones it could not. Moved orders’ promise dates are not recalculated. Nobody is notified of orders a move back makes late. Work moved back stays on the receiving plant’s Shift board until the plant acknowledges the pull-back, but its Machine queue and shift log do not show it.

See it: In the hosted demo, an applied move appears on the receiving plant’s shift board, and on its machine queue on the day it runs, as moved from Atlanta and approved by the planner; a supervisor acknowledges it, with role and time recorded.

Today: Demo tenants only. A move does not recalculate the order’s promise date: the due date stays fixed. The balancer does not see the frozen window, so its moves, contribution and late counts are as it planned them; a receiving supervisor cannot yet accept a move into the window, and each plant’s window length is a draft. Each move says where its die and plates should be, by a draft rule; tooling is not tracked.

See it: Exceptions inbox in the hosted demo, opened from the menu or the network cockpit with a count, the guest login included (read only); sorted by urgency, days late or age; a login tied to plants opens on its own plants and can pick All plants.

Today: Read-only: an exception cannot be acknowledged or assigned to a person yet, and nobody is notified. How long an order has been late or at risk is not recorded, so late rows sort by days late and show no age; in the demo, quote approvals show no age either. An order flagged to arrive early is not taken off the truck automatically.

See it: Behind the blank size and cost build-up on the Estimating screen in the hosted demo.

Today: Allowances are drafts until validated by a plant expert.

See it: Estimating screen in the hosted demo: save a box spec, see its blank, and estimate it at a plant for several quantities, with freight on the same draft load plan a booked order uses; the plant comparison says which plants cannot make it and why, and itemises the cost differences.

Today: Cost standards (waste, machine rates and other allowances) are draft demo assumptions, and every line and total that uses one is labelled draft or placeholder. Reusing tooling is a draft rule, and demo order-book designs have no design code, so they never count as on file. The plant comparison is not saved: the recommendation compares plants at the estimate’s one price, quoting at another plant needs an estimate there, and its promise dates are not reservations.

See it: In the hosted demo, New order compares a promise date from every capable plant side by side, with a "how calculated" panel for each.

Today: Timing comes from the simulated plant floor: no overtime or outsourcing, sheet plants assume a fixed 3-day sheet lead, new printed designs and dies get no lead time for plates or tooling, and down machines and recorded production are not reflected yet. A promise is not a reservation; it is checked again when the order is saved, and a draft quote’s promise again when it is sent or approved. The ceiling is the default 95%, not a planner’s chosen one. Rules are drafts.

See it: In the hosted demo, an order’s Earliest possible section lists each capable plant’s date; a plant whose approval would refuse says why instead of offering a request; a sales rep sends a pull-in request with a reason, and a planner approves or declines it under Pull-in requests.

Today: Demo tenants only. Nobody is notified of a new request yet. Dates come from the simulated plant floor, with the same limits as quoted promise dates. An approved pull-in promises the earlier date and the plan is held to it; the customer’s due date and delivery window stay, and on-time-in-full is judged against them, so an order that misses its promise but arrives inside the window reads late on the plan yet counts as on time. Nothing checks that the customer can take delivery that early.

See it: Quotes screen in the hosted demo: a quote made from a saved estimate is sent and accepted, and the order it creates links back to the quote and is worth the quoted value to the cent.

Today: Demo tenants only. One quantity per quote, quoted at the estimate’s plant; a quote at a plant the customer has not qualified says so and cannot be accepted; the promise is re-checked at acceptance and a moved date must be confirmed. The quote’s cost model and plant standard rates are not yet one: the order shows both, with the difference by cost group, and both are drafts.

See it: Customers and Orders screens in the hosted demo, on desktop and phone; a customer’s page shows its delivery window, early arrivals and on-time-in-full, and a sales rep also sees its average price per MSF by grade.

Today: Open orders only, one line per order. Orders change only through New order and approved pull-in requests.

See it: In the hosted demo, a QA login records a pass or fail against a job on a tablet screen, and it is still there on later visits. A failed check shows who owes a decision on it (awaiting QA, held, retest due, released or scrapped) and stays on the Shift board until it is decided.

Today: Demo tenants only. Checks are stored durably per company, but not yet in the main database.

See it: In the hosted demo, QA places a hold with a reason code; shipping the held order is refused with the hold and its reason, Shipments books it no carrier or ETA, and releasing it, citing the passing retest if there is one, frees the quantity.

Today: Holds are stored durably per company, but not yet in the main database.

See it: Shipping screen, or the job’s Machine queue card on the floor, in the hosted demo: record production complete for an order and its finished goods are on hand, ready to ship.

Today: Demo tenants only. Production is entered by hand, not counted by the machines, and the overs/unders tolerance is a draft setting. Committed versus free stock is not modelled yet.

See it: Shipping screen in the hosted demo: a shipping login ships an order from finished goods, marks it delivered, and sees its line measured on time and in full.

Today: Demo tenants only. The bill of lading starts from the simulated load plan, with one bill of lading, trailer and seal per planned truck under one master; no carrier or yard system checks it. The load plan flags same-day orders for the same customer and ship-to that could share a truck (checked in pairs) but still plans and costs each order’s own trucks. Freight terms start from the customer’s draft terms. Trailer, seal, carrier and freight terms (a draft list) are required to release the trucks unless the dock confirms releasing them incomplete, and can be corrected in transit with a reason; a seal that differs at receipt is not recorded. The FOB point is optional and names a default carrier claimant; no carrier claim is filed from it. Delivery windows are drafts (by default from two calendar days before the due date to the due date), and an early arrival counts as not on time; an order the floor finishes early is held so it ships to arrive inside the window. Delivery dates are entered by hand once the delivery has happened (a later date is refused), with no proof-of-delivery capture; there is no carrier or shipping-system connection.

See it: Customer issues screen in the hosted demo.

Today: Issues are stored durably per company, but not yet in the main database. Owner and deadline rules are drafts, and nothing notifies the owner or the plant yet.

See it: Invoices screen in the hosted demo: draft an invoice from a shipment at the order price and issue it with the customer’s payment terms and a due date; a shipment can be invoiced only once.

Today: Demo tenants only. Payment terms and the remit-to address are drafts; freight terms come from the shipment’s bill of lading; tax, credits and ERP posting are out of scope. Invoices show revenue only, not margin.

See it: Estimated contribution change per move and in total in the network cockpit. For roles that see costs, each move’s detail reconciles the estimate with the order’s own cost build-up, component by component (a move whose build-up freight differs from the estimate’s lane freight by more than the larger of $50 and 25% is flagged), and a saved proposal shows revenue and estimated contribution by plant, leaving and arriving, with the shift in fixed-cost absorption kept apart as not cash, and a draft transfer price that splits the contribution between the selling and producing plants and nets to zero for the network.

Today: Compares freight, variable conversion and a draft die and plate transfer cost only, and treats price and material cost as unchanged. The order page’s change comes from the order’s own cost build-up, with simulated loads, make-ready and tooling, so it differs from the estimate; both are shown, with each part of the difference. Conversion rates per operation and their variable shares are draft demo assumptions. Setting a proposal’s moves against overtime and outsourcing is a draft what-if at seed rates an admin can change: overtime is a range, and no outsourcing price is assumed until an admin enters one.

See it: Estimate vs actual in the hosted demo: the order page and a network roll-up, with a "how calculated" for every driver, and orders shipped short or over outside the overs and unders tolerance flagged.

Today: Realized contribution counts variable cost only, from what was recorded; fixed costs, overheads and plant EBITDA are not in it. By plant, a balancer move’s cost sits on its own Network row, a draft attribution for Finance to confirm. Actuals that were not recorded are labelled "standard assumed" or "not measured". Shown only to roles that see cost.

See it: TCO calculator screen in the hosted demo.

Today: A customer-entered estimate, not a quote: nothing is prefilled, including our price and run cost. Inputs stay in your browser. The headline, break-even and net present value count hard cash only unless you choose to include soft savings, and a soft saving you leave blank reads “not entered”. Legacy upgrade projects fall in the year you enter for each, or spread evenly over five years if you leave the years blank; one due while some plants still run the legacy system is pro-rated by the share still on it unless you choose to pay it in full or count it as avoided.

See it: The hosted demo requires sign-in.

Today: Accounts are created by us (no self sign-up). Two-step sign-in with an authenticator app is optional for every user, and each company can require it for the roles it chooses (a login without an app is sent to set one up after its password). A prospect login is a login in one of our demo sandboxes (the live demo or a prospect sandbox), other than an administrator we set up there without an expiry. Prospect logins are never asked for two-step sign-in. Every other login is asked when its company requires it for its role, including a login with an expiry in your own company (a contractor).

See it: In the hosted demo, sales roles see prices but not cost or contribution, and guest and floor roles see no money, on every screen including the network cockpit.

Today: Roles are fixed groups today; per-field rules you configure yourself are on the roadmap.

See it: In the hosted demo, an administrator opens Demo access, Audit log: sign-ins, refused requests, reads and changes from the last 30 days, filtered by date, action and user, newest first, and downloadable as one CSV file for the whole filtered window.

Today: Administrators only. A new entry can take a few seconds to appear. The app shows the last 30 days; older entries are kept for a year but not shown in the app. Recording a QA check and entering an order are not in that log yet, records do not carry their own change history (apart from an issue’s timeline and an order’s promise history), and the log cannot yet be sent to your own security tools.

See it: Demo access in the hosted demo: an administrator invites people, sets when each login expires, disables leavers and starts the company over from its starting snapshot. Prospects see the role behind each approval or record, never a person’s name or email.

Today: We set up each evaluation in one of a few prepared demo companies; a new company for each prospect on demand is not built yet. Starting over clears everything entered in it.

See it: The balancer behind the network cockpit; its tests run on every change.

See it: The hosted demo shows its version, deploy time and known limitations.

See it: Open the hosted demo on a phone: navigation and screens adapt, in light or dark.