Skip to main content

Forms

A submittal form is a per-feature, per-criteria document that pulls project data and analysis output into a layout the destination authority expects. Each form covers one focal feature (the PES being sited) and reports its analysis against every facility in the project that participated in an encumbrance with it. For the click-by-click flow, see Submittals → How to generate a submittal. The supported standards are listed in Submittals → Supported standards.

Learning objectives

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

  • Generate a form for a specific feature under a chosen criteria set
  • Read the three sections of a typical DCMA-style submittal form
  • Recognize the dual-direction reporting and the inline criteria citations
  • Print a form cleanly

What's on a form​

A submittal form opens with a toolbar and three table sections.

Toolbar. Pick the Facility (the feature the form is about) and the Criteria set (DCMA, NATOCV1, etc. — only criteria the project is configured for show up). A Print Form button generates the printable view.

1. General Information. Installation, Location, Date (YYYYMMDD), and Engine Info (e.g., DCMA-0.13.0) — the version of the criteria engine that produced the analysis. Useful when comparing forms across time.

2. Data on Facility to be Sited. A single row covering the focal feature:

  • Facility name and description (type code + display name)
  • RQD IBD with the 110% inclusion-zone distance computed inline (e.g., 1,250 (ft) 110%: 1,375 (ft))
  • RQD PTRD
  • Per-hazard NEW columns: 1.1, 1.2.1 + MCE, 1.2.2, 1.2.3 + MCE + (xx), 1.3, 1.4 — note the supporting weights surface alongside NEW for divisions that need them (see Calculator: Explosives → Supporting weights)

3. PES/ES Paired Relationships. One row per encumbrance involving the focal feature, with these columns:

  • Facility — the other feature's name plus the Exposure Type tag (e.g., AGM IMD, Feature 005 IBD)
  • Facility Description — type code + display name + optional per-pair note
  • Relationship — packs Act: X (ft) - Req: Y (ft), PES Face: ..., ES Face: ..., the relationship code (unrelated, sameline, etc.), the analysis-code pair (AGSU-AGSU, AGSB-ECM7FB), the Reverse direction analysis-code pair, and the Exposure Type
  • Per-HD columns (1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.4) — required distance, the inline criteria citation (e.g., Table AP2.T6., Table AP2.T14., Note 2), the reverse-direction distance, the allowable NEW (DQ), and supporting weights (MCE, (XX)) where the division uses them

Dual-direction reporting​

When the ES in the encumberance is also a PES, the relationships table includes both directions. The forward direction is the focal feature acting as PES against the other; the Reverse: line shows the same pair with roles swapped. The two directions can produce different required distances and even different governing analysis codes when the two features have asymmetric attributes or different segment-aware analysis codes (e.g., AGSB-ECM7FB forward, ECMFU-AGSB reverse).

Read both directions when interpreting a row — a pair that's compliant in one direction can violate in the other.

Violation flagging​

Rows where the actual distance is less than the required distance are visually flagged on the form, typically with a (violation) marker beside the facility name and a red color treatment on the row. Violations are surfaced inline in the same table — there is no separate violations section.

Inline criteria citations​

Each per-HD cell carries the criteria citation that produced the value (e.g., Table AP2.T6., C5.18.13.5.). The citation is the form's audit trail — when the form is reviewed by an external authority, every required-distance value can be traced back to its source criterion. This is the same data the criteria path carries on a calculator-side analysis, surfaced inline in the form for compliance use.

Printing the form​

The form is HTML rendered for the browser, which means Print Form sends it to the browser's print dialog. A note on the form itself reminds users:

Turn off Headers/Footers in your browser print window for a clean form.

Browser-injected headers and footers (URL, timestamp, page numbers) clutter the printed output if left on. Disable them in the browser's Print → More settings → Headers and footers before saving the PDF or printing.

warning

Siter is not intended to be a documentation management platform. Forms are ephemeral and are not saved within the project.

Try it​

In an analyzed project with at least one explosive-bearing feature:

  1. Open the submittal form for that feature, picking DCMA as the criteria
  2. Confirm the General Information section populates from project metadata
  3. Spot-check the focal feature's row in the Data on Facility section — confirm the NEW values match what you entered
  4. Pick one row in the PES/ES Paired Relationships table and verify the Reverse: direction tells a coherent story (same pair, roles swapped, possibly different required distance)
  5. Click Print Form and observe the browser's print dialog. Toggle off Headers and footers and confirm the printed output is clean