Products & BOM
Upload Excel/CSV using the template or start from scratch. Connect each part to the parent assembly that directly uses it.
You do not need to configure every module on day one. Start with product structure, dated demand and materials. Add work-cell standards and shift control when you want the same view to extend into execution.
This is the shortest path to value. Once these are in place, Runway can calculate shortages and show which build milestones are covered.
Upload Excel/CSV using the template or start from scratch. Connect each part to the parent assembly that directly uses it.
Add finished-unit quantities and due dates. This sets the demand Runway will test.
Enter on-hand stock, reserved quantity, safety stock, stock unit and conversion where needed.
Add expected receipts, optional PO numbers and due weeks aligned to build-plan milestones.
Use production outlook, readiness Gantt and highest-impact risks to decide what needs action first.
Click through the four operating perspectives below. Each one shows the part of Runway that role is expected to maintain.
Every BOM needs one finished-product row. Each child item points to the part number one level above it. Quantity per parent means the quantity used by one parent, not the total requirement across the full build.
Create the work area, assign its owner, define standard steps and attach its controlled references. Once those standards exist, supervisors can use them for operator balance and dated shift records.
A practical daily rhythm is to review the production outlook, open constraints, work-cell status and the latest shift record, then update supply or roadblock ownership as conditions change.
Look first at what is controlling the next build milestone.
Use downtime and output records to keep the execution picture current.
Assign ownership, preserve context and resolve flags when the constraint is genuinely cleared.
That is enough to see how Runway turns product structure, stock and incoming supply into a production-readiness decision.