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)
  • 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 dashboard → Relationships tab (per-pair edit)One specific PES → ES relationshipThe 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.

warning

Marking a relationship as barricaded on the Relationships tab is a per-pair edit, which means it is flagged as a user override. User overrides survive the next relationship build instead of being overwritten by the matrix.

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
  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.