Three kinds of questions fill the day of a stock, production and planning manager: what is running low, what is tying up too much, and what is late. The answers exist in Logo, but in different modules and different reports. In iyibir Mind these questions are asked in Turkish or run as ready-made commands by typing / in the question box; the result is drawn onto the board as cards. This article lists the commands that match the questions this role asks most often.
What is running low: critical stock and safety stock
"Hangi ürünlerin stoğu kritik seviyenin altında?" (Which products are below their critical stock level?) is one of Mind's ready-made analyses: it gives items below the critical level with warehouse, on-hand quantity, critical level and purchasing in transit. The command for the same topic is /critical-stock, which shows critical stock and replenishment need. To look at a single warehouse you add a filter: /critical-stock ambar Merkez.
/safety-stock-coverage goes a step further: it shows items below safety stock and how many days of stock are left. /replenishment-risk gives replenishment risk based on demand and stock level, and /material-shortage gives the material shortages affecting production and orders.
What is tying up too much: overstock, dead stock, turnover
- /overstock: stock above the maximum level and the value tied up.
- /dead-stock: stock that hasn't moved for a long time.
- /stock-aging: how long stock has been waiting, in age groups.
- /stock-turnover: stock turnover rate and slowing items.
- /inventory-valuation: stock cost, quantity and total value.
The overstock question is often a value question. /overstock shows it as the value tied up along with the quantity; /stock-aging separates how long the same stock has been waiting into age groups.
Expiry dates and count variance
/expiring-lots lists lots whose expiry date has passed or is approaching. /inventory-count-variance shows count surplus and count shortage by warehouse and item; after a year-end count it is a direct starting point for "where did the difference add up?". Both can be narrowed to a single warehouse: /inventory-count-variance ambar Merkez.
Time and scrap in production
- /production-lead-time: time from opening to completion of production orders and deviation from plan.
- /production-order-performance: production orders against plan and actual.
- /work-in-progress: quantity, cost and waiting status of ongoing production.
- /production-scrap: production scrap, loss and scrap rates.
- /material-consumption: planned and actual material consumption.
- /capacity-utilization: production capacity, utilization and bottleneck.
In the lead-time question, deviation from plan comes as separate information: besides how long an order took, how far it deviated from the planned time is on the card too.
Time and delay in supply
/supply-lead-time gives the days from purchase order to goods receipt by supplier and item. /open-purchase-orders shows incomplete orders, and /supplier-delivery-risk shows late and risky supplier deliveries. The ready-made analysis "Açık satınalma siparişleri" (Open purchase orders) is the question form of the same topic: it gives orders not yet fully received with supplier, expected delivery, amount and status.
Warehouse and dispatch
/warehouse-stock gives stock quantity, value and critical level by warehouse; /warehouse-transfers gives the status of transfers between warehouses; /order-to-ship-cycle gives the days from order to dispatch and the late ones. /delivery-otif shows the on-time, in-full delivery rate.
Building a stock board
Before the month-end meeting, running five of these commands one after another is enough: /critical-stock, /overstock, /expiring-lots, /production-lead-time, /supply-lead-time. The cards accumulate on the same conversation's board. If you name the board and share it, the relevant people in your company see it read-only and continue on their own copies with "Bu panodan başla" (Start from this board). On the morning of the meeting you can redraw each card with current data using "Yenile" (Refresh).
Things to keep in mind
Planning: requirements, plan adherence and bottlenecks
- /mrp-overview: the material requirements plan and suggested movements.
- /demand-planning: demand forecast and planned requirements.
- /plan-adherence: adherence between planned and actual production and supply.
- /planned-order-suggestions: suggested production and purchase orders.
- /capacity-bottleneck: capacity bottlenecks that put the plan and delivery at risk.
Planning commands link the production and supply sides: which order a material shortage affects, which purchase order comes out as a suggestion, how closely the plan is followed. The commands work with the data kept in Logo; if a part isn't in Logo, the card says so openly.
Using the same data for different questions
- Warehouse manager: /critical-stock, /overstock, /expiring-lots, /inventory-count-variance.
- Production manager: /production-lead-time, /production-scrap, /work-in-progress.
- Planner: /material-shortage, /safety-stock-coverage, /plan-adherence.
- Purchasing specialist: /open-purchase-orders, /supply-lead-time, /supplier-delivery-risk.
In a meeting where these four roles come together, four people can add their own questions to the same board; when the board is shared, the others see it read-only.
Questions in Turkish
- "Hangi ürünlerin stoğu kritik seviyenin altında?" (Which products are below their critical stock level?)
- "Açık satınalma siparişleri neler?" (What are the open purchase orders?)
- "Bekleyen satış siparişleri neler?" (What are the pending sales orders?)
These three are ready-made analyses and are asked without typing a command; Mind picks the right analysis, gives a short answer in the chat and draws the card onto the board. All three accumulate side by side on the same conversation's board.
Not every command is equally complete; the menu shows a status next to each. When a command runs partially, the missing part is stated on the card in one sentence. For the source of the figures, open the card's "Nereden?" panel: there you see which Logo tables were read and the date the data is as of.