The planning cycle

The same approach works for a factory, a fleet or a shift team. The vocabulary and the rules change; the cycle stays the same.

Connect → Model → Propose → Decide → Replan
                     ↑                  │
                     └── each incident ─┘

1. Connect

The starting data comes from Excel, the ERP or the systems you already use: orders, inventory, fleet, staff, calendar. The import shows what it will create before creating it.

2. Model

The problem is described with resources, tasks, orders, constraints and objectives. The model uses your vocabulary: parts, assets, shifts or whatever you use.

3. Propose

PlanifAI computes one or more proposals. Each one meets the rules and carries its indicators: due dates, cost, utilisation, availability. If a rule cannot be met, the proposal says so: which rule, where and by how much.

4. Decide

You compare the proposal with the current plan, see what changes and accept it. What is accepted becomes everyone’s plan. See Proposals and current plan.

5. Replan

When an incident occurs (a breakdown, an absence, an urgent order), what is already running is fixed and the engine looks for the alternative that moves the least. See Replanning.

Forecasting, before the cycle

When demand or consumption is uncertain, forecasting gives scenarios (P50, P80, P90) to size stock, purchasing and capacity before planning.