When you open HEC-HMS and assemble a Subbasin, Reach, Junction, and Reservoir, it looks like “another hydrology program with a window.” Its question is older: how does rainfall over a watershed become streamflow? The predecessor HEC-1 began development in 1967. More than half a century of accumulated ideas.
What problem does it solve?
In outline: rainfall → interception/infiltration → runoff → transformation → routing → hydrograph.
That is different from asking how deep the water gets on the floodplain. That second question is river hydraulics and usually goes to HEC-RAS.
The Hydrologic Engineering Center
HEC = Hydrologic Engineering Center, of the U.S. Army Corps of Engineers (USACE), formed in 1964. Early historical families:
- HEC-1 — watershed hydrology
- HEC-2 — river hydraulics
- HEC-3 — reservoir operation
- HEC-4 — stochastic streamflow generation
Over time several evolved into the modern generation (HEC-HMS, HEC-RAS, HEC-ResSim, HEC-FDA…).
1967–1968: HEC-1 is born
The HEC-1 Flood Hydrograph Package was originally developed in 1967 (Leo R. Beard and the HEC team). The first packaged version came out in October 1968. It unified smaller programs and aimed to model flood hydrographs — with limited memory, rigid formats, and expensive computing.
HEC-1 was revised for decades (major revisions in the 1970s and 1980s; variants such as HEC-1F, PRECIP, HEC-IFH). When HEC built the next generation, it did not throw the knowledge away: it modernized the algorithms.
NexGen and March 1998: HEC-HMS 1.0
In 1991 HEC launched the NexGen project: replace older programs with a modern architecture and a graphical interface (the program window). From that effort came HEC-RAS, HEC-HMS, HEC-FDA, HEC-ResSim…
HEC-HMS (Hydrologic Modeling System) is the heir to HEC-1. The first general version 1.0 was published in March 1998: C++, object orientation, a graphical interface, more flexibility, gridded runoff, fewer of HEC-1’s historical constraints. Arlen Feldman led the HMS project; the engine and the window were built by an HEC team plus consultants.
How a model is put together
The watershed is a network of elements (subbasins, reaches, junctions, reservoirs, diversions, sources, sinks). A typical project combines:
- Basin Model — the physical structure
- Meteorologic Model — precipitation and meteorology
- Control Specifications — dates and time interval
- Simulation Run — combines them and executes
Losses (SCS Curve Number, Green-Ampt, Initial/Constant, SMA…), transformation to a hydrograph (unit hydrographs, Clark, ModClark…), baseflow, and routing (Muskingum, Muskingum-Cunge, kinematic wave, reservoirs). There is no universal method: it depends on data, scale, and purpose.
HEC-1 lived mostly in flood events. HEC-HMS put real weight on continuous simulation (days, months, years): evapotranspiration, soil moisture, snowmelt, recovery between storms.
What you can do with HEC-HMS
Flood design
Design storm → watershed → design hydrograph for bridges, culverts, reservoirs — and then, if needed, HEC-RAS.
Flood studies (together with HEC-RAS)
Precipitation → HEC-HMS → Q(t) → HEC-RAS → depth / inundation. HMS produces the flow; RAS says what that flow does in the river and on the floodplain.
Reservoirs and spillways
Inflows, routing, extreme storms, spillway design.
Urban drainage (at watershed scale)
The impact of urbanization on runoff. For detailed sewer networks, SWMM is usually more appropriate.
Water availability and forecasting
Long series with continuous simulation; forecast tools and integration into operational systems (e.g. Corps CWMS-type ecosystems).
Grids, GIS, and calibration
Radar / gridded precipitation (ModClark and similar); DEM, watershed delineation, drainage networks. Parameter optimization (Curve Number, lag, baseflow…) against observed flows — volume, peak, timing, shape — without believing that “Optimize” replaces judgement. The modern program also has uncertainty, sediment, and water-quality capabilities; exchange goes through HEC-DSS.
Short contrasts
HEC-HMS vs HEC-RAS
HMS: how much flow does the watershed produce, and how does it change with time? Typical output Q(t). HEC-RAS: what does that flow do in the river and on the floodplain? Stage, depth, velocity, inundation. Complementary, not substitutes.
HEC-HMS vs SWMM
HMS: watershed / rainfall-runoff / hydrologic routing. SWMM: detailed urban drainage (storm/sanitary) with surfaces and in-network processes. Different scales.
Free, alive — and with limits
HEC develops HEC-HMS for USACE and distributes it at no cost. As of September 2026 the main stable download is still HEC-HMS 4.13 (July 2025); in 2026 HEC has published 4.14 betas.
Short timeline
- 1964 — HEC is formed (USACE).
- 1967–1968 — HEC-1; first publication.
- Decades of revisions and variants.
- 1991 — NexGen project.
- 1998 — HEC-HMS 1.0 (C++, graphical interface).
- Event → continuous → gridded → GIS → forecast / optimization.
- 2025–2026 — HEC-HMS 4.13 stable; 4.14 in betas.
Conclusion
HEC-1 turned rainfall-runoff into software when that was hard to do. HEC-HMS carried those ideas into a windowed, modular, more flexible platform. The central question did not change: how does a watershed respond to the water it receives? — and that question is still the starting point of a great deal of hydraulic engineering.
References
- U.S. Army Corps of Engineers, HEC. About / History.
- HEC. HEC-1 Flood Hydrograph Package (legacy).
- HEC. HEC-HMS.
- HEC. HEC-HMS Technical Reference Manual (CPD-74B); Feldman / NexGen team.
- USACE IWR. NexGen Software Development Program.
- HEC Newsletter Summer 2009 (45th Anniversary; origin of HEC-HMS / NexGen).
- HEC. HEC-HMS Downloads.
Evaluation and limitations
Treat the notes below as evaluation context, not as a verified calculation or code check.
Use it for rainfall-runoff and hydrologic routing. The Q(t) it produces is not the flood map; that question usually goes to HEC-RAS. Optimization does not replace judgement.