Texas State Fire Marshal Rules (28 TAC Chapter 34, Subchapters C, E, F and G)
Subchapter G: fire sprinkler rules (34.701 to 34.725) – Texas State Fire Marshal Rules (28 TAC Chapter 34, Subchapters C, E, F and G)

Texas State Fire Marshal Rules (28 TAC Chapter 34, Subchapters C, E, F and G) 34.721: Yellow tags for non-compliant, unmaintained or recalled-equipment sprinkler systems short of an emergency impairment, with written notice within five business days

What does 34.721 require?

Where a sprinkler system is found not to comply with the applicable NFPA standards, not to be tested or maintained to the adopted standards, or to contain manufacturer-recalled equipment, but without an emergency impairment, a completed yellow tag goes on each system riser where it can be inspected without hampering operation, to show that correction is needed; the service person's or inspector's signature certifies the listed conditions. Within five business days of attaching it, the service person or inspector notifies the building owner or representative and the local authority in writing (postmarked, emailed, faxed or hand delivered) of all non-compliant conditions. Only an authorised employee of a registered firm, or a regulator, may take the tag off, and only after a service tag certifying the fix is on; the local authority hears within five business days of its removal or revision. Yellow tags match service tags in size, may be printed for several years, and carry the do-not-remove inscription, the firm's name, address, telephone number and certificate number, the RME's licence number, the printed name and signature of the service person or inspector, the punched date, the owner's or occupant's name and address, the building or system identifier, and the list of items not compliant with the NFPA standards.

Maintained by Gerard Blokdyk

Other controls in Subchapter G: fire sprinkler rules (34.701 to 34.725) – Texas State Fire Marshal Rules (28 TAC Chapter 34, Subchapters C, E, F and G)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.