(III) — PLAN2 min read

Plan supply from demand

Creating a generates demand for its materials and capacity. provide confirmed demand, while forecasts represent expected demand that is not yet ordered.

Carbon plans against both sources and applies each part's replenishment policy.

Demand forecasting

Under Production, open Projections and enter expected weekly quantities. In this example, demand for SAT-1000 increases from two units per week to four by week six, with corresponding demand for ADCS-001 and EPS-001. adds these quantities to the plan without creating sales orders.

Confirmed orders (weeks 1–3) plus forecasted demand (weeks 4–5), the full picture Carbon plans against.
Entering projected weekly quantities from the sales pipeline: the SAT-1000 bus at 2, 2, 3, 3, 4, 4 over the first six weeks, with ADCS-001 and EPS-001 alongside it.

Reordering policy

Each part has a that controls when and how much Carbon proposes to replenish:

  • Manual Reorder: Carbon creates no proposal; a planner decides when and how much to order.
  • Demand-Based Reorder: replenish net demand, grouped by the configured demand-accumulation period.
  • Fixed Reorder Quantity: when on-hand reaches the , propose the configured reorder quantity.
  • Maximum Quantity: when on-hand reaches the reorder point, propose enough to reach the maximum inventory quantity.
Reorder point in action: on-hand falls to the trigger, and an order tops it back up.
BUY OR MAKE

The policy decides how much; the replenishment system decides what kind of order.

The policy determines quantity. The replenishment system determines the document: Buy creates a , while Make creates a job. Reorder, minimum, and maximum quantities adjust the proposed quantity to an orderable amount.

A part's Reordering Policy, Reorder Point, and Reorder Quantity that drive every suggestion.

Into jobs & POs

Carbon nets order and forecast demand against on-hand inventory, open jobs, and open purchase orders. Production planning proposes jobs for manufactured parts; purchasing planning proposes purchase orders for purchased parts.

Demand in, plan out: production planning suggests jobs, purchasing planning suggests POs.

Purchasing planning applies to translate inventory units into purchasing units. A proposal becomes a job or purchase order only after confirmation.

BY LOCATION

Demand and planning can differ by location.

Run plans by location. The same part can use different replenishment settings at different sites.

Suggested jobs for the parts you make, with the weekly shortfall that triggered each one.
The same view for the parts you buy: suggested purchase orders, ready to confirm.

Receiving

When a purchase order arrives, create a . Carbon initializes the Draft receipt from the order and validates its quantities. the receipt adds the goods to on-hand inventory.

For a item, record the batch number on the receipt line. The conversion factor converts the purchased quantity to the inventory quantity. Carbon retains the batch identity for later genealogy queries.

A conversion factor reconciles units: one purchased box of ten lands as ten stocked Each.
Receiving a batch-tracked battery-pack shipment against PO000001, batch LOT-BAT-2609 captured on the line.
Was this page helpful?
No
Edit on GitHub