Operating Routine and Frequently Asked Questions

Use this routine to keep planning current without reviewing every product. The workspaces move from freshness, to exceptions, to approved execution.

Daily routine

1. Open Inventory Control Tower. Confirm the update time and choose the workflow lens.
2. Review Exceptions and Setup Blockers before broad execution.
3. Use Inventory Risk, Buying Plan, and Rebalancing with the required horizon, bucket, filters, and grouping.
4. Open the decision drawer for exceptions; use row or group selection for eligible bulk work.
5. Open Planning Overview for portfolio status and execution progress.
6. Create draft RFQs and internal transfers only after quantities, timing, and blockers are approved.

Weekly routine

• Review explicit Planner Purchase Quantities and changed system suggestions.
• Review stockout-affected, availability-unknown, demand-review, donor-protection, route, and horizon queues.
• Review upcoming vendor/profile order windows and purchase schedules.
• Correct missing vendors, rules, UoMs, transfer routes, and stale manual dates.

Monthly routine

• Analyze receipt lead times and review suggestions; applying one updates Planning Rules, not vendor master data silently.
• Review rules, profiles, networks, exclusions, replacements, and known demand events.
• Review mature Inventory & Service, Forecast Quality, and Planning Impact evidence.

Common questions

• Does Niyu place purchase orders automatically? No. It creates draft RFQs when an authorized user requests it.
• Does it complete transfers? No. It can create and confirm an internal picking; warehouse users execute the physical movement.
• Does a new sale update the plan instantly? No. It appears after the next forecast sync.
• Does opening Demand History use a refresh? No. It reads the stored snapshot.
• Can Planner Purchase Quantity be zero? Yes. It remains until reset.
• Why is purchase quantity different from forecast demand? Stock, dated supply, transfers, timing, safety, planner decisions, UoMs, and supplier constraints also apply.
• Why did an Ordering Profile change nothing? A matching Planning Rule must link it.
• Can forecasts be decimal? Yes. Executable RFQs and transfers respect UoM precision.
• Does stockout adjustment delete sales? No. It may only add conservative demand to supported zero-sales stockout days.
• How many runs does an anomaly need? A known event created before sync needs one run. An automatically detected anomaly needs the discovery run, planner review, then one follow-up run.

Escalation sequence

1. Read the Action Line explanation and blocker.
2. Confirm the winning Planning Rule and Ordering Profile.
3. Reconcile demand, stock, dated supply, transfers, dates, and UoMs.
4. Check Demand Events and explicit planner overrides.
5. Open the Forecast Run and Demand History snapshot.
6. Collect the Troubleshooting evidence before escalating.