Skip to content

First planning workflow

The Community workflow connects a statistical forecast to a heuristic supply plan. The goal is not merely to demonstrate screens: every quantity must be traceable to the data, configuration, and scenario that created it.

Versioned workflow

The data, decisions, and criteria below describe the official Community baseline. A packaged distribution and reference dataset may be added in a later version.

Expected result

Master data + sell-out
        ↓
Statistical Demand Plan
        ↓
Network + inventory + production + policy
        ↓
Heuristic Supply Plan
        ↓
Planning Books and exception analysis

Step 1 — Prepare the foundation

Create:

Sell-out is the initial Community source because it observes the sale from a location without requiring an individual destination. Validate identifiers, calendar, units, and historical continuity before configuring a model.

Step 2 — Generate the Demand Plan

  1. Define forecast level and clusters.
  2. Configure the execution profile with historical source, frequency, and horizon.
  3. Run Demand Planning.
  4. Analyze the baseline by material-location.
  5. Record allowed adjustments in the Community Planning Book without turning visual aggregations into new physical series.

The output is a versioned Demand Plan. It must preserve the baseline and adjustment origin.

Step 3 — Complete the supply model

Add to the same materials and locations:

Open orders and other transactional families enter when the release contract declares them available. Do not replace a missing dataset with zero quantity.

Step 4 — Generate the heuristic Supply Plan

  1. Select the Demand Plan and Supply execution profile.
  2. Confirm that every item-location has a viable purchase, production, or transfer source.
  3. Run the unconstrained view first when you need to separate structural need from a bottleneck.
  4. Run the constrained plan with capacity, inventory, lead time, and policy.
  5. Analyze production, distribution, projected inventory, coverage, and shortage in the Supply Plan.
  6. Review exceptions in the Community Planning Book and preserve the base version.

The complete functional journey is documented under Supply Network Planning and Design.

Success criteria

  • backend and front identify community in the same runtime;
  • only available models and modes can be selected;
  • the Demand Plan has coherent history, baseline, and horizon;
  • the Supply Plan uses the same unit and calendar;
  • missing network, capacity, or master data produces an explainable exception;
  • no Enterprise option executes through a manually crafted payload;
  • the workflow can be repeated from the release reference dataset.

Evidence bundled with the release

The published workflow should identify:

  • release tag and compatible backend, front, and database versions;
  • reference-dataset version and integrity identifier;
  • exact preparation and execution steps;
  • expected Demand Plan and Supply Plan versions, horizon, and row-level reconciliation checks;
  • one explainable constraint or data-quality exception;
  • automated smoke-test result and the date it was reproduced.

Screenshots may illustrate the journey, but they do not replace this evidence. The roadmap changes the workflow gate only when the bundle can be reproduced from public artifacts.

When to move to Enterprise

The same data model can be extended when the process needs optimizer, process chain, advanced forecast models, detailed scheduling, Cost-to-Serve, P&L, AI, SSO, or distributed execution. Moving editions should enrich the existing workflow, not force the team to rebuild its central master data.

Return to the Community overview or read architecture and boundary.