Skip to main content

Project analysis results

Project-level results give you the rolled-up view of every PES → ES pair Siter evaluated, with violations and governing distances surfaced for review. This lesson covers reading the project results panel and translating its summaries back to the calculator-style breakdown you saw in Module 1.

Learning objectives

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

  • Open the project results panel and read its sections
  • Drill from the project view into a single PES → ES pair
  • Map a project-level summary back to the calculator-style hazard breakdown

What "project results" means​

When you click Calculate, Siter first runs a "spatial analysis" to identify features that are within the search zone for the project. The search zone is based on the project's set "expected max NEQ" value and is usually based on the most conservative exposure type for the criteria plus a margin of error. Siter uses this distance to build a list of encumberances, the PES → ES pairs that generate the analysis relationships. It then passes all of these encumberances to the QD Engine, receives the resulting required distances, and builds qd arc shapes based off the feature. The project results panel rolls those calculations up into a single view: how many pairs, how many violations, governing distances per pair, and entry points to drill in.

It is the "bird's-eye view" — useful for triaging where to focus, but rarely the place where you finish a diagnostic. For that, you switch to the feature dashboard and use its own Calculations tab for the specific facility involved.

How the panel is organized​

The project results panel surfaces every analysis result in a filterable table, with per-row detail when you expand a row. The view defaults to Governing Distances — the answer most users want first — but several other views surface different slices of the same underlying data.

Filter views​

ViewWhat it shows
Governing DistancesOne row per PES Face → ES Face pair: the bottom-line Required distance and which hazard governed
Required DistancesRequired distance split per Exposure Type (IBD, PTRD, ILD, IMD, etc.)
All DistancesEvery per-hazard distance — Blast, Frag, Thermal — alongside Required
ViolationsOnly the pairs where actual < required
Planning DistancesFixed planning distances independent of NEW
DQ ResultsPer-pair allowable NEW values (the inverted view — see DQ analysis)
All ResultsEverything — every result type for every pair
Selected ResultsOnly rows you've selected, useful for building drawings
Dimensioned ResultsOnly rows that have a dimension line attached

Pick the view that matches what you're doing — triage uses Governing or Violations; building a deliverable drawing uses Dimensioned or Selected.

Columns​

Each row captures both identity and value:

  • Criteria — which criteria set produced the result (DCMA, DESR, NATO, ATF)
  • PES / ES — the two facilities in the pair
  • PES Face / ES Face — which segment of each (front, rear, side, perimeter)
  • PES Layer / ES Layer — for filtering by working area
  • Explosive — the hazard division (1.1, 1.2.1, etc.)
  • Exposure — the Exposure Type (IBD, PTRD, ILD, IMD)
  • Result — what the value represents (Required, Blast, Frag, DQ, etc.)
  • Distance (ft) / Distance (m) — the value, in both unit systems

Sorting any column reorders the table; filters narrow the visible set.

Per-row detail​

Expanding a row reveals how that single result was produced — the same diagnostic surfaces covered in Module 1, reached in Siter for any specific result:

  • Zoom To — buttons to center the map on the result, the PES, or the ES
  • Criteria Version — the criteria-engine version that produced the value (useful when comparing to historical data)
  • Governing Criteria — the specific criterion entry credited with the value
  • Criteria Path — the formal-citation list (see Criteria path)
  • PES Analysis Path / ES Analysis Path — the side-level paths that resolved the analysis codes
  • Analysis Path — the per-result narrated walkthrough (see Tracing analysis paths)
  • Dimension Line + Dimension Text — annotation controls for drawings
  • Adjust Arc Precision — fine-tune the polygon density of the arc on the map and in drawings

This is where you typically finish a diagnostic — a single expanded row carries everything you need to defend the result, build a deliverable, or escalate a problem.

Per-feature results​

In addition to the project-level panel, every feature's dashboard exposes its own Calculations tab — the same project results table, filtered to just the results where this feature is the PES. Use it when you have a specific facility in question and want to see only the analyses it drove, without the noise of the rest of the project. The columns, filter views, and per-row detail are identical to the project-level view; only the row set is narrower.

Spatial Analysis (encumbrances)​

Where Calculations shows engine output, the Spatial Analysis tab on a feature shows engine input: the encumbrances the spatial-analysis pass built before any QD math ran. Each row represents one PES → ES face pair within the project's search zone, with the measured actual distance between them.

Encumbrance columns include:

  • Criteria — the criteria set the encumbrance applies under
  • PES / ES — the two facilities
  • PES Face / ES Face — the segment pair
  • PES Layer / ES Layer
  • Distance (ft) / Distance (m) — the measured actual distance

The encumbrance list is what the QD engine consumes; project results are what it produces. Inspecting it directly is useful for sanity-checking the spatial-analysis pass — if a PES → ES relationship you expected to see in results is missing entirely, it may be missing from the encumbrance list (typically because the pair sits outside the search zone, the ES is on a background layer, or one feature is missing required inputs).

How project results map to calculator results​

Every row in the project results panel is the output of a calculation that, in isolation, would look exactly like a calculator analysis. The project view aggregates and sorts; the per-pair detail is the single-analysis view from Module 1, with the same Required / Blast / Frag / governing structure.

This is the practical payoff of the calculator-first arc: once you can read a calculator result, you can read any row in project results.

Try it​

In a project that has been analyzed, open the project results panel and:

  1. Note the totals — features, pairs, violations
  2. Find a single violation and click into it to open the pair detail
  3. Identify the Required, Blast, and Frag values, and the governing hazard
  4. Open the analysis path and walk the trace from inputs to verdict

This sequence — bird's-eye → pair detail → analysis path — is the canonical diagnostic flow for a violation.