Map Location State
Record whether each site is open and its total fixed operating cost for the scenario planning period. Each row references an existing location. Costs use the scenario currency, and a closed site has zero fixed operating cost.
When to use this¶
Use this node to import an observed footprint and its incurred fixed costs. For an optimization, enter rules through Map Location Policy instead: Network Optimization creates fresh location state and never inherits a previous run's decisions or costs.
What you need¶
One row per location, an open indicator and a nonnegative total fixed cost. An open site may carry no volume and still incur its operating 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 | Warehouse A |
Site identifier, matching a location in this scenario. | location, location_id |
| Is Open | boolean | Yes | True |
Whether the site is open during the scenario planning period; an open site may carry no volume. | is_open |
| Total Fixed Cost | number | Yes | 100000.0 |
Fixed operating cost incurred once at this site for the scenario planning period, in its currency. | total_fixed_cost |
Workflow wiring¶
Wire Import Data into this node and its records into Create Scenario, alongside Map Locations. The scenario reports fixed operating cost as its own component. Cost to Serve does not allocate this site-level component among customers or products.
flowchart LR
raw["Import Data"] --> mapping["Map Location State"]
mapping --> scenario["Create Scenario"]
places["Map Locations"] --> scenario