What You Actually Deal With When Seaworks Shows Up on Your Desk
Seaworks is a coastal engineering software package originally developed by GeoDense and later acquired by Bentley Systems. It's used primarily for designing and analyzing retaining structures along shorelines, sheet pile walls, riprap slopes, and other maritime infrastructure elements. The program handles limit equilibrium stability analysis, seismic assessment, and bearing capacity calculations. Engineers pull it out when a project involves soil-structure interaction near water, and they need something faster than building a custom spreadsheet for every variation. That phrase sounds like something pulled from a marketing brochure, but underneath it is a fairly grounded set of capabilities. Seaworks decodes coastal engineering problems by letting you model soil stratigraphy, apply hydrostatic and wave loads, run Factor of Safety checks, and generate output plots that can go straight into a report. It does not do everything. It won't model tsunami inundation or give you hydrodynamic flow patterns. Those tasks belong to other tools. Seaworks lives in the geotechnical design lane. Here's how I actually use it day to day. I start with a borehole log or a set of CPT data points. I input the soil layers, assign unit weights, cohesion, friction angle, and permeability values. Then I define the structure geometry, whether that's a cantilever sheet pile wall or a gravity retaining structure with riprap armor. After that I set the load cases. Groundwater table position matters enormously. A two-meter shift in the water table can drop a Factor of Safety from 1.6 down to 1.1 in certain clay profiles, and the software will show you exactly where that crossover happens if you set up the case properly.
I remember one project off the Gulf Coast where the client insisted the existing seawall had a factor of safety well above 1.5. The original design reports were vague about the groundwater conditions behind the wall. I modeled the wall with different phreatic line positions, and at a headwater of just 1.2 meters behind the sheet pile, the FoS dropped to 1.08 on the circular failure surface. The client's maintenance crew had been pumping stormwater into the backfill area through French drains that were clogged. Fixing the drainage brought the FoS back above 1.3 within a week. Seaworks didn't find the problem by itself, but it made the sensitivity obvious fast enough to justify the repair budget. The interface hasn't changed dramatically in years. It opens, it loads projects, and it spits out reports. The learning curve is manageable if you already understand limit equilibrium methods and Mohr-Coulomb failure criteria. You don't need to be a theorist, but you do need to know what the numbers mean when the output comes back. A Factor of Safety below 1.0 doesn't automatically mean the wall has failed. It means the model found a failure surface that is theoretically possible under the loads you specified. If your input parameters are wrong, the FoS is wrong too, and no amount of tweaking the geometry will fix that. Common pitfalls I see people make. The first is assuming the default search radius for the critical slip surface is adequate. Seaworks uses a grid search algorithm, and the default settings will find the most likely failure surface for standard geometries. But when you have a composite failure path involving a weak clay lens at depth beneath a granular backfill, the default grid can miss it. I learned this the hard way on a barrier island restoration project where the critical surface ran through a buried peat layer at roughly twelve meters depth. The default search returned an FoS of 1.42. I widened the search envelope and added a targeted fine grid around the peat interface, and the actual critical FoS came back at 1.11. That difference determined whether we needed a batter pile reinforcement scheme or could stick with a simpler toe weight addition.
Another thing that catches people is the treatment of seismic loads. Seaworks offers pseudo-static analysis and simplified dynamic methods, but the acceleration coefficients you plug in come from regional seismic hazard maps and site-specific ground response studies. If you're assigning a peak horizontal acceleration based on a general zone map without doing a site amplification check, your results will be either non-conservative or wastefully conservative depending on your soil profile. Soft sediments amplify seismic waves. Hard rock does not. The software won't tell you that. You have to know it before you type the number in. There's also the matter of output documentation. Seaworks generates report files that contain your input data, analysis results, and cross-section plots. These are useful for internal review but often need significant editing before they satisfy a reviewing authority. Many agencies want to see the load combinations explicitly listed, the soil parameter sources cited, and the factor of safety values for multiple failure mechanisms, not just the critical one. I typically export the data and rebuild the tables in a format the permitting engineer expects rather than trying to force the built-in report into compliance. The software has real limitations. It does not integrate with hydrodynamic modeling tools. If your project involves wave overtopping volumes or scour depth estimates around a revetment, you're going to need separate software for that. Seaworks can accept wave forces as applied loads in a simplified way, but the pressure distributions it uses are based on older analytical solutions that don't capture the complexity of modern CFD-based wave modeling. For routine design work at typical coastal structures, the simplified approach is acceptable. For unusual geometries or extreme events, it becomes a source of uncertainty that you should document in your report.
Get the Full Details
Riprap design in Seaworks follows standard procedures like the USACE riprap manuals and FHWA guidelines. The software will calculate required stone size based on velocity and depth for channel applications or wave height and slope for coastal revetments. The outputs are reasonable for preliminary sizing. But I've seen engineers use the riprap module results as final design without checking against site-specific stone availability and placement tolerance. The calculated D50 might be 18 inches, but the nearest quarry only stocks 15 and 24 inch stone. That gap matters. The software doesn't know your local supply chain. Another bottleneck is the lack of modern file import formats. You can bring in some geotechnical data from CSV and basic GIS shapefiles, but if your site investigation data lives in a proprietary logger format or a comprehensive geotechnical database, you're going to spend time manually entering or converting data. On a recent waterfront redevelopment project, I spent about three hours converting borehole data from a GeoStudio output format into the Seaworks input format. The conversion worked but was tedious. If your firm does this kind of work regularly, building a simple conversion script saves significant time compared to manual entry. For anyone getting started, I'd suggest working through the built-in examples first. They cover the main analysis types and give you a reference point for what reasonable input looks like. Then pick a simple cantilever sheet pile wall problem and model it both by hand and in Seaworks. Compare the results. If they diverge, figure out why. Most divergence comes from differences in how the software models the active and passive earth pressure coefficients, the depth of embedment, or the treatment of surcharge loads. Once you understand where those differences come from, the tool becomes much more useful.
The software runs on Windows and requires a Bentley Systems license manager. If your office already has a Bentley environment, adding Seaworks is straightforward. If not, the licensing cost and the dependency on a specific network infrastructure may be a factor worth considering alongside competing tools. There are alternatives like PLAXIS for more detailed finite element analysis, or even open-source options for basic slope stability, but those come with their own learning curves and tradeoffs. Seaworks occupies a middle ground that works well for routine coastal geotechnical design when you need speed and familiarity with industry-standard methods. I use it because it gets the job done for the kinds of projects I'm typically assigned. It's not elegant. The interface feels dated. The help documentation is sparse. But for a seawall stability check, a sheet pile deflection estimate, or a riprap size calculation on a tight timeline, it delivers results you can stand behind. Just pay attention to your inputs, check the sensitivity of your key parameters, and don't let the software's output create a false sense of precision. The numbers are only as good as the soil data you put in front of them.
