A civil engineer can receive a geocellular tank schedule that looks complete: module type, footprint, depth, and storage objective are all present. Difficulties begin at the edges. Inlets carry sediment. The membrane meets penetrations. Cover and pavement transfer load. Groundwater creates external actions. Inspection risers compete with services. A controlled outlet has to remain reachable after the site is handed over, under the actual surface use and through the planned maintenance route.
These interfaces determine whether the underground asset behaves as intended. Crate selection is important, but the cell is not an independent structure floating outside the drainage, geotechnical, pavement, water-quality, and maintenance designs. Treating selection as a datasheet exercise can leave critical responsibilities between packages.
A better method is to coordinate the geocellular tank as a system boundary. Start with hydraulic routing, then test the structural envelope, wrap, pretreatment, access, outlet, construction sequence, and handover evidence against one another. The StormTank module can then be selected within a buildable arrangement rather than used as a shortcut around unresolved design work.
Draw the complete water path
Draw every design interface along the water path: how runoff reaches the tank, what happens before entry, how water occupies the storage block, where it leaves, and what occurs when the normal path is unavailable. Coordinating these design interfaces lets the civil engineer see whether the system is an infiltration geocellular tank, a lined attenuation arrangement, a detention system, or another documented configuration on stormmanage.com.
Storm Manage describes its geocellular tank as an assembly that can use a geotextile wrap where water infiltrates or a geomembrane lining where water is held and released under flow control. Its infrastructure guidance also places silt management and inspection access upstream of the storage block, emphasizing that the modules provide storage rather than water-quality treatment.
A water-path drawing should include pretreatment, inlet distribution, storage zones, connections between cells, outlet control, bypass or overflow, and the receiving route. If a combined function is intended, the operating logic must be explicit. A tank cannot be assumed to infiltrate, attenuate, and harvest simultaneously merely because each term appears in a product range.
Hydraulic review should also test the usable configuration, not just gross geometric volume. Solid fraction, levels, outlet position, residual water, sediment allowance, and the approved modelling approach can affect performance. The manufacturer supplies module data. The project designer decides how that data enters the accepted hydraulic model.
Coordinate load through the cover and surrounding ground
A load rating in isolation does not define a buried system. Traffic type, pavement, cover depth, construction plant, lateral support, backfill, ground movement, and installation quality all influence how action reaches the modules. The civil and structural review must use the selected model’s properties within the actual site build-up.
Storm Manage’s highway and car-park guidance connects module grade and height with cover depth, traffic class, ground conditions, bedding, membrane, silt management, and inspection components. This is the correct systems perspective: a StormTank module contributes to the load path, while the completed buried construction depends on coordinated material and site inputs.
Construction loading deserves separate attention. The final pavement may distribute service loads, while an excavator or compaction operation acts on a partially completed build-up. The method statement should define exclusion zones, backfill sequence, compaction approach, and the point at which traffic is permitted. A design that is adequate in service can still be damaged before handover if temporary conditions are ignored.
Groundwater introduces both geotechnical and envelope questions. External water may create uplift or pressure when the tank is empty. The response may involve level changes, restraint, drainage, mass, or another project-specific measure. It should not be hidden inside a generic note that the module is suitable underground.
Make the membrane and penetrations a designed interface
Choosing between geotextile wrap and geomembrane lining follows the water path, but execution depends on details. Corners, protection layers, joints, pipe penetrations, inspection risers, bases, and transitions must be coordinated with the selected materials and installer’s method. A neat schematic cannot substitute for a buildable detail.
For infiltration, the separation layer must keep surrounding fines from migrating into the void while allowing the intended movement of water. For attenuation, the sealed envelope must retain water around a modular shape with multiple penetrations and interfaces. In both cases, the design should establish inspection and repair expectations before backfill makes the system inaccessible.
Name responsibility explicitly. Does stormmanage.com provide lining materials, installation guidance, or only compatibility information? Who designs the penetration? Who installs and tests the lining? Who accepts it before backfill? Without explicit ownership, the highest-risk detail can sit between the drainage package and the tank supply order.
Protect storage with pretreatment and maintainable access
Sediment consumes volume quietly. Debris can obstruct controls. Hydrocarbons and other catchment pollutants may require treatment that the storage block cannot deliver. A civil engineer should coordinate the treatment train using land-use risk, local requirements, and the selected discharge route, then make its interfaces visible in the tank layout.
Philadelphia Water’s subsurface detention guidance calls for inspection of controls and storage areas, cleaning of catch basins and pretreatment components, removal of sediment and debris, protection against outlet clogging, and continuing maintenance records. It also recognizes that specialist equipment or professional support may be needed. The lesson travels well: access must be designed around real tasks, not inserted as a symbolic chamber.
Map every component that needs observation or intervention. Then test whether the proposed access point provides a safe and practical route to it. Consider the future surface, parked vehicles, landscaping, security, confined-space implications, and the equipment likely to be used. The operator should be able to understand the asset without reconstructing the designer’s intent from scattered drawings.
Use an interface responsibility matrix
A responsibility matrix prevents the project from treating package boundaries as physical boundaries. It should identify the information exchanged, the party that designs the interface, the party that supplies it, and the evidence required before closure.
Geocellular tank interface responsibility matrix
| Interface | Coordination question | Closeout evidence |
|---|---|---|
| Hydraulic routing | Does the inlet, storage, outlet, and exceedance path match the accepted model? | Coordinated drawing and calculation reference |
| Structural envelope | Are module data, cover, pavement, soil, groundwater, and temporary works aligned? | Design check and installation sequence |
| Membrane system | Who owns joints, penetrations, protection, testing, and acceptance? | Approved detail and pre-backfill record |
| Pretreatment and access | Can the operator inspect and maintain every critical component? | Maintenance plan, access drawing, and asset record |
Review the matrix whenever the tank footprint, module grade, pavement, discharge basis, or service layout changes. Its value lies in showing the knock-on effect. A shifted riser may affect access; a changed outfall may alter storage; a deeper tank may change groundwater and structural checks.
Procure the coordinated system, not the isolated cell
The enquiry package should include the project water path, accepted storage basis, module layout constraints, load and cover information, groundwater context, envelope type, connections, pretreatment, access, outlet control, required drawings, test evidence, packing, installation support, and exclusions. Suppliers can then respond to the same interface set.
Using the Storm Manage modular storage platform does not remove the need for civil, hydraulic, structural, geotechnical, and operational coordination. It gives the project a configurable StormTank module family and a source of model-specific information. The final design remains a system assembled by the project team.
A geocellular tank succeeds at its boundaries. Water must arrive in a condition the system can manage. Loads must move through the cover without damaging the cells. The envelope must perform at joints and penetrations. Controls must remain accessible. Operators must inherit records that explain the asset. Once those interfaces are treated as the main design work, crate selection becomes easier, more transparent, and far less likely to conceal a missing responsibility.