Map Production State

Map raw rows into the scenario's production state table: the outcome of production. It records how many units of each recipe were produced at each site, and the conversion cost realized.

This is the observed side of production. Pair it with Map Production Policy for the rule.

When to use this

• You have a baseline of what was produced and want Cost to Serve to roll production cost into finished goods
• You're importing observed manufacturing volumes rather than optimizing them

Network Optimization writes this table itself from its production decision. Map it only when you have an observed baseline to load.

What you need

• A Map Bill of Materials node defining each recipe
• An upstream Import Data node with one row per (location, recipe) that was produced
• A produced-quantity column, and optionally the realized conversion cost

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 occurred. Must match a Location name.	location, loc, name, id, location_id, loc_id
Bom Name	text	Yes	City Bike BoM	Recipe that was produced. Must match a bom_name on the BoM table.	bom_name
Produced Quantity	number	No	300.0	Units of the output product actually produced in the recorded baseline. Its unit goes in Quantity Unit.	produced_quantity
Quantity Unit	text	No	bike	Unit that produced quantity is expressed in (the output product's unit).	quantity_unit, qty_unit, unit, uom
Realized Cost	number	No	12000.0	Total production conversion cost actually incurred in the baseline (not per-unit; excludes component cost).	realized_cost, supply_cost, handling_cost, total_supply_cost, production_cost, total_handling_cost
Realized Emissions	number	No	900.0	Total emissions actually produced by manufacturing in the baseline. Its unit goes in Emissions Unit.	realized_emissions, emissions, co2, carbon, ghg, carbon_emissions
Emissions Unit	text	No	kg CO2	Unit for realized emissions (e.g. kg CO2).	emissions_unit, co2_unit

How it works

Each row records production at a site. Cost to Serve reads the produced quantity to size component consumption, then rolls the components' cost plus the realized conversion cost up into the finished good's cost to serve.

Workflow wiring

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

Common mistakes

• Putting the per-unit rate here. Realized Cost is the total incurred. The per-unit conversion rate belongs on Map Production Policy.
• No matching recipe. The Bom Name must match a recipe on the bill of materials table.