Skip to main content
Dogeartech

LOMR Scheduling: HEC-RAS Version Rules, Review Cycles and Model Checks

LOMR schedules hinge on matching the effective study’s HEC-RAS version and avoiding review cycles; solver speed is often a smaller factor.

LOMR Scheduling: HEC-RAS Version Rules, Review Cycles and Model Checks

FEMA name and U.S. Department of Homeland Security seal on the exterior of a federal office building.

For a riverine Letter of Map Revision (LOMR), the HEC-RAS version can shape the schedule before any calculations begin. FEMA’s MT-2 instructions generally call for revised conditions to use the version behind the effective study, unless the entire modeled reach is being revised. That constraint can outweigh the time saved by running a model on a newer engine: review cycles, model coordination and version problems are more likely to set the calendar.

The practical point is straightforward: identify the effective model and its version early, then plan the revised analysis around it. A model that solves quickly still needs to tie back to the published study and withstand technical review.

Accepted programs and version choice

FEMA accepts computer programs used to perform the analysis, identified by program and version. The same framework applies across NFIP submittals, including restudies, physical map revisions, CLOMRs and LOMRs. Under 44 CFR 65.6(a)(6), a program used for a map revision must be reviewed and accepted by an appropriate body, documented with materials such as source code and user manuals, and available to FEMA and affected parties.

FEMA maintains a list of accepted numerical models. HEC-RAS, developed by the U.S. Army Corps of Engineers Hydrologic Engineering Center, appears on its hydraulic models list. The relevant choice is therefore not simply which interface a modeler prefers: the calculation must use an accepted program version suited to the submittal.

For a partial-reach revision, MT-2 Form 2 says to run revised conditions with the same model version as the effective study, unless the entire modeled reach is being revised. FEMA gives the reason: reducing discrepancies outside the revised reach. Opening an effective model in a newer release and recomputing it may change results beyond the area under revision, complicating comparisons with the effective study.

There can be circumstances where another approach is appropriate, including a revision of the entire modeled reach or an approach allowed by FEMA guidance. If a proposed project cannot meet the applicable floodway criterion, a CLOMR may be needed before construction, followed by a LOMR to revise the map. That sequence affects both design coordination and the timing of map changes.

When a CLOMR comes before a LOMR

A LOMR revises the current NFIP map to show changes to floodplains, regulatory floodways or flood elevations. A CLOMR addresses a proposed project in advance, commenting on whether it would meet minimum NFIP standards if built as proposed. In practical terms, the CLOMR addresses the proposal before construction; the LOMR reflects qualifying changes afterward.

The applicable encroachment test depends on the mapped condition. For an adopted regulatory floodway, 44 CFR 60.3(d)(3) says development must be prohibited unless analysis shows the encroachment would not increase flood levels. Where a floodway has not been designated, paragraph (c)(10) applies. For AE/A1-30 areas without a designated floodway, the cumulative effect must not increase the base flood elevation (BFE) by more than 1 ft. If a proposal exceeds the applicable criterion, a conditional map revision may be required.

Mapped conditionCriterion described in the source
Adopted regulatory floodwayEncroachment must not increase flood levels.
AE/A1-30 area without a designated floodwayCumulative effect must not increase BFE by more than 1 ft.
Increase beyond the applicable criterionA conditional map revision may be required before the later map revision.

Submittal routing also varies. Some states and regional bodies review map revisions under agreements with FEMA; the source names North Carolina, Alabama, Illinois and the Urban Drainage and Flood Control District in metro Denver. Check the routing list in the current MT-2 instructions before assembling the package.

Why model coordination takes calendar time

A LOMR analysis may need several model conditions, each with a distinct role:

  • Duplicate effective: a copy of the analysis used for the effective Flood Insurance Study.
  • Corrected effective: an effective model with errors fixed or cross sections added, without a physical change.
  • Existing or pre-project: conditions reflecting changes in the floodplain since the effective study.
  • Revised or post-project: the conditions submitted for the proposed revision.

These models have to remain consistent with one another and with the published study. At transitions, 44 CFR 65.6(a)(2) requires revised and unrevised BFEs to match within 0.5 ft. FEMA’s flood risk analysis and mapping guidance describes another useful check: post-project BFEs at revision limits should generally match pre-project BFEs within 0.1 ft. These figures serve different purposes. The 0.5 ft criterion applies at the specified transitions against effective study elevations; the 0.1 ft comparison is a modeling check at the limits of revision, subject to applicable exceptions.

Managing four sets of conditions across separate folders invites mismatched geometry, flow data or terrain. Keeping them together in one project can make comparisons easier and reduce the chance that a result is carried forward from the wrong plan. Floodway determinations add another round of iteration as encroachment stations are adjusted to meet allowable rise criteria. Immediate feedback on rise, width and velocity can help the modeler evaluate each change.

The review process can dominate the schedule

FEMA’s published MT-2 sequence allows up to 90 days for review comments, up to 90 days for the requester to address them, and up to 90 days for the revision to be issued, followed by a 4.5-month appeal period. Those are maximum periods in the stated process, not a prediction that every submittal will take that long. They do show why a technically clean package can still spend months in review and related steps.

Each avoidable warning or inconsistency can prompt additional questions or rework. The cost is measured in review time and staff effort, while a faster solver may save only part of a model run. A duplicate effective model that matches the study, clearly documented comparisons, and consistent plans help reviewers follow the analysis without needing to reconstruct the modeler’s choices.

More processor cores do not guarantee faster runs

HEC-RAS performance depends on the model and the computer’s processor configuration. The HEC-RAS User’s Manual reports that, in testing on a computer with 8 logical processors, gains were maximized for models using 4 cores. Small models slowed as more cores were added, and hyper-threading can also reduce performance.

USACE’s 2016 computer performance guidance stresses processor speed over a large core count. Time step and mesh resolution can have a greater effect on run time, but changing either can affect accuracy. For a floodway determination, reducing resolution or changing time steps just to shorten a run is a poor schedule shortcut if it compromises the analysis.

HEC-RAS 7.0 arrived on April 17, 2026, followed by version 7.0.1 on June 2. Version 7.0 added a “Run Multiple Plans” option to compare run times across processor counts and distinguishes performance cores from efficiency cores. Those tools can help tune computation. They do not change the version guidance for a LOMR: forward compatibility lets a newer engine open an older project, but it does not make the newer version interchangeable with the one used for the effective study.

Where workflow improvements can help

Some software interfaces run the unmodified USACE HEC-RAS engine while adding tools around it. GeoHECRAS, for example, lets users select an engine version and manage model data through a graphical interface. The calculation remains the selected HEC-RAS engine’s result; potential time savings come from organizing plans and iterations, rather than changing the underlying computation.

  • Choose and record the engine version. The described software supports versions from 7.0.1 back to 3.0.1 and can lock a version for imported models. Keeping the effective study’s version available may simplify compliance with the MT-2 instruction.
  • Check processor selection against the model. Automatic core selection can favor performance cores, with a manual override. “All Available” cores do not necessarily produce the fastest run.
  • Keep condition models together. A shared project can hold each plan’s geometry, flow data and terrain, and batch analysis can recompute selected plans without manual repetition.
  • Make floodway iteration visible. Tracking rise, width and velocities as encroachment stations change gives the modeler feedback during the determination. The source also describes a copy step from a Method 4 solution to explicit Method 1 stations, which some state reviewers require.

Civil & Environmental Consultants reported cutting model development time by 50 percent, with model building and calibration falling from about half of the project budget to a quarter. That is a company-reported result, not a general performance guarantee. Modelers still need to review terrain-derived sections where the terrain is inaccurate, apply engineering judgment to land-cover roughness, and take responsibility for the submitted analysis.

Checks to complete before submitting

FEMA’s cHECk-RAS tool reads HEC-RAS data files and checks Manning’s n values and transition losses, cross sections, floodway, structures and profiles. Run it before submitting, then resolve warnings or document why any remaining warning does not indicate a problem.

  1. Confirm the engine version. Check it against the effective study and state the version clearly in the report.
  2. Document the duplicate effective comparison. Show how it ties back to the study and identify which elevation checks apply.
  3. Verify transition elevations. Confirm revised and unrevised BFEs meet the 0.5 ft criterion where required, and assess the 0.1 ft post-project to pre-project check at revision limits under the applicable guidance.
  4. Review cHECk-RAS results. Resolve flagged issues or provide a clear explanation for each warning that remains.
  5. Confirm the submission destination. Use the current MT-2 routing information for the project location.

The schedule gains in a LOMR are most likely to come from fewer rebuilt models, fewer version surprises and fewer rounds of review. Solver time matters, but it is one piece of a process whose technical comparisons and review steps can stretch across months.

Source: Kshitij Shah · www.civilgeo.com

Filed alongside