Your premier resource for building code knowledge.
This forum remains free to the public thanks to the generous support of our Sawhorse Members and Corporate Sponsors. Their contributions help keep this community thriving and accessible.
Want enhanced access to expert discussions and exclusive features? Learn more about the benefits here.
Ready to upgrade? Log in and upgrade now.
Correct, Not a Rebar replacementretire09 said:According to the ESR, it sounds like it is only allowed in nonstructural slabs or plain concrete footings with no reinforcement required.
ACI 318-14 1.10 is ACI's catch all for this, "Approval of special systems of design , construction, or alternative construction materials" - The data linked previously, along with project specific calculations, are always supplied to the EOR and building official for their approval.This is the sort of thing that should go through the code adoption process. In this case I would expect ACI to produce a report addressing the product and if appropriate the product would be referenced in an ACI standard which ultimately be adopted into the building code.
This process allows for a thorough review by uninterested parties. On the other hand ESR's have an inherent bias in favor of the manufacture because ICC is influenced by the money they can charge the manufacturer.
Other proprietary products have found their way into the building code. They create a performance standard.Can't (or won't) comment on what "should" happen, whether codes intended to promote innovation are "abused" or not, or any other opinion based commentary.
Sticking to the facts, and the topic of the original question, yes the ICC has certified that Helix Steel meets the code requirements set down by both IBC and ACI to directly replace traditional rebar in foundations. The test data, calculation process, and design methods are published and publicly made available. Neither the IBC or the ACI will ever specifically mention a proprietary product - this is the purpose of the independent evaluation reports.
I was thinking the same thing with the metal reacting to water, and how much "wicking" there might be. The strands are supposed to interlink to provide structure so I wonder how much how much that could lead to loss of integrity over time, especially over long periods of time in areas where the slab is wet year round.I have no experience with steel strands in concrete but I do have experience with fiberglass strands in concrete. The strands will stick out of the concrete and I suppose they are worn away over time...or perhaps the strands are removed. Does the same thing happen with steel? What about rusting?
Yes, PE designs are absolutely necessary - Helix replaces rebar, not engineering. The process for almost all projects is that structural drawings with rebar specs will be submit, and the Helix team will provide equivalent dosages or a hybrid rebar/Helix design. The EOR reviews the calc package, and approves (or rejects) Helix as an alternate.Its main use appears to be for temperature & shrinkage reinforcement. It requires a PE design for other applications and for footings other than seismic categories A, B & C.
As its steel, a laser screed, vibrating screed, or just decent bull float gets all the Helix under the surface. And because the product is discontinuous, any potential rusting at joint cuts won't travel throughout the slab (although the product is zinc plated). Happy to talk more directly.I have no experience with steel strands in concrete but I do have experience with fiberglass strands in concrete. The strands will stick out of the concrete and I suppose they are worn away over time...or perhaps the strands are removed. Does the same thing happen with steel? What about rusting?
So ok without PE design in a plain residential footing A,B, or C (though not sure IRC actually requires rebar in those) but what about in grouted cells of a block foundation wall?Yes, PE designs are absolutely necessary - Helix replaces rebar, not engineering. The process for almost all projects is that structural drawings with rebar specs will be submit, and the Helix team will provide equivalent dosages or a hybrid rebar/Helix design. The EOR reviews the calc package, and approves (or rejects) Helix as an alternate.
You're not wrong, and I'm not trying to say that either of the reports are constitute code change. The reports are saying that Helix meets the performance standard already set for rebar, as an alternative, and only in certain applications. Helix may not be strictly defined in ACI or IBC, but it is certainly allowed - EOR and building official do still need to sign off. Some engineers and building officials won't.Other proprietary products have found their way into the building code. They create a performance standard.
Strictly speaking ICC reports have no legal standing. It is the building official that needs to make a decision regarding whether it is an alternate means of compliance. A building official cannot automatically defer that decision to ICC.
When considering an alternate means of compliance the building department should require the test and other data be submitted. Product manufacturers use the ICC evaluation reports as a way to hide that information. ICC claims that information is proprietary. This shows that ICC's loyalty is to the manufacturer and not to the members of ICC. There is an exception to this non disclosure if you will go to the ICC office the building department can view the data but who is going to go to the ICC office. So from a practical point of view manufacturers use ICC evaluation reports to hide the data.
Regardless of the intention of product manufacturers, and ICC the only way to modify the building code is for the legislative body to formally adopt a code change. In California it is recognized that alternate means of compliance can be approve individually by the building official on a case by case basis. Such approvals need to be formally recorded. A building department would be justified in charging an additional fee to cover the additional work. What ICC and manufacturers promote is the idea that an ICC ESR is a defacto code change.
Manufacturers of new product should go through the code adoption process. If they will not we should ask what they are trying to hide.