Tetrapods, dolosse, accropodes, xblocs, core-locs and the rest of the cast concrete armor family exist because of one problem: on a large breakwater exposed to ocean waves, the rock big enough to stay put may not exist in any quarry within reach.
The answer was to manufacture armor units with shapes that interlock, so a unit is held not only by its own weight but by its neighbours. It works, it is well proven, and on a major breakwater it remains the correct system.
What the cast unit family requires
The engineering is sound. The logistics are the constraint:
- A casting yard within reasonable distance, with forms for the specified unit and size
- Curing time before any unit can be handled, and longer before it is placed
- Storage area for the units while they cure and wait
- Handling and transport of individually heavy, awkwardly shaped items
- Heavy marine plant to place them, often to a specified placement pattern and density
- Placement supervision, since interlocking armor depends on how it is laid, not only on what it is
For a project placing tens of thousands of units on a kilometre of breakwater, every one of those is amortised and none of it is a problem. The casting yard is set up for the job and it is a line item like any other.
For a project placing a few hundred units at a port entrance or a headland, the same requirements are the dominant cost, and they are what a comparison should actually be about.
Where the interlocking unit is right
- Large breakwaters exposed to ocean wave climates
- Design wave heights beyond what available rock will hold
- Long structures where the casting operation is amortised
- A specified armor layer design with defined placement density and packing
- Where the structure is the project, not an element of a larger one
If your project is a new harbour arm facing the open Atlantic, this article is not for you and cast units are the answer.
Where the economics change
The case shifts as scale drops and as the duty moves away from open-ocean wave attack:
Smaller coastal works. Revetment along a stretch of shoreline, protection at a headland, repair of a section of an existing structure.
Port and harbour interiors, where the loading is berth-related — propeller wash, vessel-generated waves, current — rather than ocean swell.
Repair and remediation. Where an existing armor layer has lost units and the requirement is to restore a section rather than build a structure. Casting a small number of matching units is disproportionate, and often the original forms no longer exist.
Remote locations. Where there is no casting yard, no aggregate supply for concrete, and no realistic prospect of establishing either — but there is rock.
Compressed schedules. A cast unit programme has a critical path through casting and curing. Bagged armor becomes armor when it is filled.
What you trade
Being straightforward about it: rock bags do not do what an interlocking cast unit does.
No interlock. A cast armor unit derives a large part of its stability from engaging its neighbours in a designed pattern. Bagged units are stable through weight, friction, and packing, but they do not interlock in the engineered sense.
No comparable published hydraulic stability framework. Cast armor units come with established stability coefficients from decades of physical model testing, which lets a coastal engineer size an armor layer against a design wave with confidence. We publish which test methods back which claims and do not publish measured values, and we are explicit in when not to use rock bags that we hold no citable physical model test results for wave stability. On a project where the design has to demonstrate armor stability against a design wave through an accepted method, that is a real gap and the honest answer is that cast units have something we do not.
Less geometric consistency. A designed armor layer has a specified porosity, thickness, and packing density. Bagged armor gives a rougher, less uniform layer.
Where bagged armor genuinely competes
Given all that, the cases are specific:
- Local rock available, armor stone or casting infrastructure not
- Small scope where mobilising a casting operation is disproportionate
- Toe protection and scour control at a structure, rather than the primary wave armor layer
- Repair and infill within an existing armor system
- Placement in water without a dry working area
- Temporary or phased works, where recovery is foreseeable
- Irregular geometry around existing structures
Note how many of those are secondary duties around a main structure rather than the main armor layer itself. That is an accurate reflection of where bagged armor fits on a large coastal project: toe, scour, transitions, and repair rather than the primary armor.
The question to ask
If cast units and bagged armor are both on the table for the same scope, the design wave condition is the question that separates them. Where a design wave governs and stability has to be demonstrated by an accepted method, cast units have the framework and we do not. Where the duty is scour, current, toe protection, or repair, the comparison is genuinely open and the logistics usually decide it.
Where to go next
- Coastal and shoreline applications for the coastal case
- Marine and ports for berth and harbour duties
- When not to use rock bags for the wave-stability limitation stated plainly
- Materials, testing, and service life for what our test programme does and does not cover
- The comparison hub for the rest of the field
Send the design wave condition, water depth, and scope through the quote form, and if the answer is that cast units suit the duty better, we will say so.