Loop Sizings
What the arithmetic said the card count should be, against what it is — with the inputs kept, because "why do we have eleven cards on this part" is otherwise unanswerable a month later.
Where to find it
- Module: Manufacturing
- Group: Plan
- Section: Kanban
- Screen: Loop Sizings
Address in the console: /mfg/kanban-sizings
Read-only list · 11 columns · 1 action
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Loop | Code | loop_no |
| Item | Code | item_no |
| From | Date | window_from |
| Demand/day | Number | observed_daily_demand |
| Lead (days) | Number | observed_lead_days |
| Variability % | Number | demand_variability_pct |
| Now | Number | current_cards |
| Should be | Number | recommended_cards |
| Delta | Number | delta_cards |
| What it says | Text | verdict |
| Applied | Text | applied |
What you can do here
Apply primary
Asks for confirmation: Change the loop to the recommended card count? Cards still have to be issued or retired on the floor — raising the count alone changes nothing there.
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.