Map Production Policy

Map raw rows into the scenario's production policy table: the rule for production. It says where a recipe from Map Bill of Materials can be run, at what per-unit conversion cost, and up to what capacity.

This is the input side of production. Pair it with Map Production State for the quantity produced and the cost realized.

When to use this

• Your network makes products and you want Network Optimization to decide how much to produce where
• You have a per-unit conversion cost, and optionally a capacity, for each production site

What you need

• A Map Bill of Materials node defining each recipe
• An upstream Import Data node with one row per (location, recipe) the site can run
• A per-unit production cost column, and optionally a capacity

Field mapping

Auto-detection is all or nothing. With no explicit mapping on the node, every field is matched against the headers listed below, case-insensitively, and a space in your header reads as an underscore, so Site Name matches site_name. Set even one field explicitly and detection switches off for the whole node: only the fields named in the mapping are filled, and the rest arrive empty.

Set mappings in the node's panel. Connect an upstream table and select the mapping node to see automatic matches. Choosing a column saves all displayed matches as an explicit mapping. Use Use automatic detection to return to header detection. Required fields without a match are marked in the panel.

Field	Type	Required	Example	What it is	Auto-detected headers
Location	text	Yes	Berlin Assembly Plant	Where production happens (the plant/assembly site). Must match a Location name.	location, loc, name, id, location_id, loc_id
Bom Name	text	Yes	City Bike BoM	Recipe to produce here. Must match a bom_name on the BoM table.	bom_name
Unit Production Cost	number	No	40.0	Cost to produce one unit of the BoM's output product (labour/overhead beyond component cost), in the scenario currency. Blank = production adds no conversion cost.	unit_production_cost
Capacity	number	No	500.0	Maximum units of the output product produceable here — the optimizer's upper bound. Blank = unconstrained. Its unit goes in Quantity Unit.	capacity, max_flow, max_quantity, max_volume, quantity
Quantity Unit	text	No	bike	Unit that capacity is expressed in (the output product's unit).	quantity_unit, qty_unit, unit, uom
Emissions per Unit	number	No	3.0	Emissions produced per output unit manufactured. Blank = production emissions are not modelled.	emissions_per_unit, co2_per_unit, carbon_per_unit, emission_rate

How it works

Network Optimization adds a production decision for each (location, recipe). Producing a unit of the output consumes its components, which creates derived demand for them, and pays the per-unit conversion cost, bounded by capacity.

Workflow wiring

flowchart LR
    n1["Import Data (bom.csv)"] --> n2["Map Bill of Materials"]
    n4["Import Data (production.csv)"] --> n5["Map Production Policy"]
    n2 --> n3["Create Scenario"]
    n5 --> n3

Common mistakes

• No matching recipe. The Bom Name must match a recipe on the bill of materials table, or there is nothing to produce.
• Putting the produced quantity here. That is an outcome, and it belongs on Map Production State.