Skip to main content

Barricading in Siter

Barricading in Siter is a flag, not a map feature. Siter does not have a "barricade" feature type, and the mapping tool does not auto-detect barricades from geometry. Instead, you assert "this is barricaded" by setting a barricaded flag in one of two places. The criteria-side rules from the calculator still apply: a flagged barricade only earns a reduction when the criteria path allows it (sameline relationship, ILD-family Exposure Type, etc. — see Calculator: Barricading).

Learning objectives

By the end of this lesson you should be able to:

  • Set barricaded status at the segment level (broad) or per-pair (targeted)
  • Predict how a per-pair Segments, Yes, or No value combines with the segment flags
  • Pick the right flag location for what you're modeling
  • Diagnose the most common mistake: a barricaded flag that earns no reduction because the criteria path doesn't support it

Two places to set barricaded status​

LocationScopeWhen to use
Feature dashboard → Segments tabPer segment of a feature, applies to every pair where that segment participatesThe segment is always physically barricaded — there is a real, permanent barricade on that side of the facility (e.g. there is a barricade in front of an ECM)
Feature editor → Relationships tab, or All Relationships in edit mode (per-pair Barricaded dropdown)One specific facility pair, both directionsThe barricade applies between this specific pair only — typically a sited berm, a structural intervening building, or a relationship-specific shielding feature

The segment-level flag is the broad brush; the per-pair flag is the precise one. Use whichever matches reality.

How the two combine​

The per-pair Barricaded dropdown has three values: Segments, Yes, and No.

  • Segments (the default) — no per-pair override. A PES/ES face pair is barricaded when either face, the PES face or the ES face, is flagged on its facility's Segments tab
  • Yes / No — overrides the segments for that pair, in both directions and for every criteria

The analysis and the submittal forms apply the same rule, so the form's (B) Barricaded / (U) Unbarricaded line matches what the engine used for that row. Because the segment rule is per face, two rows for the same pair of facilities can differ when only one face is flagged.

note

Per-pair barricade values are not relationship codes: the relationship build never adds, changes, or removes them, so they survive every rebuild without being marked as user overrides. Reset All Relationships does delete them, returning every pair to Segments.

What the flag does (and doesn't)​

The flag tells the engine "consider the barricaded variant of the criteria path for this pair." It does not:

  • Create a feature on the map
  • Get auto-detected from geometry
  • Override the criteria's other conditions for the reduction

The engine still walks the same conditional logic from Calculator: Barricading:

  • The relationship code must be sameline (under DCMA)
  • The criteria path must support a barricaded variant — typically ILD, not IBD or PTRD
  • The criteria must allow the reduction for the active hazard division

If any of those conditions fails, the flag has no effect. The result will not change, and the analysis path will show the engine walked the unbarricaded branch.

Diagnosing a no-effect barricade​

When you've flagged a barricade and the analysis didn't change:

  1. Confirm the relationship code on the pair is one that can apply barricaded criteria
  2. Confirm the analysis is on an ILD or IMD Exposure Type, not IBD or PTRD
  3. Confirm the flag is on the right segment (or the right pair) and not on a different one. A per-pair No overrides a barricaded segment; set the pair back to Segments to follow the segment flags again
  4. Open the analysis path for the pair and locate the step where the engine decided whether to apply the barricaded variant

The first two are by far the most common — they are the same calculator-side pitfall the Barricaded related vs barricaded sameline exercise demonstrates.

Try it​

For a worked walkthrough that combines relationships and barricading end-to-end, see Mitigating violations via relationships.